-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor(pytest): make test more robust and easier to debug #598
Conversation
tiagolobocastro
commented
Jan 9, 2025
•
edited
Loading
edited
bors try |
tryBuild failed: |
Change a lot of return Nones for exceptions which aids debugging by failing at the point of failure Reduce verbose logging when install/upgrades takes some time due to cpu or network constraints Remove extra logging Allow using kubectl plugin from path I think the tests are currently broken for release branches as its asserting for develop. Also we're modifying the chart itself, which is not ideal. todo: improve this Signed-off-by: Tiago Castro <tiagolobocastro@gmail.com>
f82d8b0
to
be41609
Compare
When deploying a kind cluster, ensure we allocate the requested hugepages. Signed-off-by: Tiago Castro <tiagolobocastro@gmail.com>
Ensure install is properly completed Ensure upgrade is properly completed Compare against v-next and not v-next since there's no current way of knowing which version is the current helm chart. This may get addressed if we start building the images and the chart as v-next from the outset. Signed-off-by: Tiago Castro <tiagolobocastro@gmail.com>
d647b79
to
cadbe0c
Compare
Signed-off-by: Tiago Castro <tiagolobocastro@gmail.com>
Signed-off-by: Tiago Castro <tiagolobocastro@gmail.com>
4b6ec90
to
10d1a92
Compare
Allows the bdd tests to run and setup the vnext chart on their own We can still pre-deploy the kind cluster on CI for time tracking Signed-off-by: Tiago Castro <tiagolobocastro@gmail.com>
10d1a92
to
3fe353c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lot of work!
afe85fb
to
9299752
Compare
Still missing is "forking" the chart, I'll leave that for another PR since requires modifying dependencies release script to allow for custom args in order to select non-custom location for the chart |
598: refactor(pytest): make test more robust and easier to debug r=tiagolobocastro a=tiagolobocastro refactor(nix): make shell nix depend on other shells Signed-off-by: Tiago Castro <tiagolobocastro@gmail.com> Co-authored-by: Tiago Castro <tiagolobocastro@gmail.com>
bors cancel |
Canceled. |
9299752
to
3c132b1
Compare
bors merge |
🕐 Waiting for PR status (GitHub check) to be set, probably by CI. Bors will automatically try to run when all required PR statuses are set. |
598: refactor(pytest): make test more robust and easier to debug r=tiagolobocastro a=tiagolobocastro refactor(nix): make shell nix depend on other shells Signed-off-by: Tiago Castro <tiagolobocastro@gmail.com> Co-authored-by: Tiago Castro <tiagolobocastro@gmail.com>
This PR was included in a batch that successfully built, but then failed to merge into develop. It will not be retried. Additional information: Response status code: 422
{"message":"Required status check \"helm-chart-test\" is expected.","documentation_url":"https://docs.github.com/articles/about-protected-branches","status":"422"} |
When pushing tags (annotated?), github's event.base_ref may not be set. When this happens, we can figure out the released branch ourselves, by inspecting all branches containing the tag, and ensuring it's the tip and it's the current HEAD. Signed-off-by: Tiago Castro <tiagolobocastro@gmail.com>
3c132b1
to
0561331
Compare
Some weird github actions thing... I made only bors a requirement, since it pulls in the others anyway... |
Build succeeded: |