-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Replace t.Fatal with require package in tests-e2e #6782
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
Replace t.Fatal with require package in tests-e2e #6782
Conversation
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.
Thanks, this is awesome!
Could you rebase please? |
There are more files left in test/e2e left so I will do it in different PR. One of the files have like 273 appearances so do you want me to have a separate PR for just one file or multiple files in one PR? I am fine both ways. @simonpasquier |
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.
Thanks!
The merge-base changed after approval.
The merge-base changed after approval.
The merge-base changed after approval.
The merge-base changed after approval.
Hi @AshwinSriram11, looks like there are some conflicts again 😕. Do you mind rebasing the PR? |
Head branch was pushed to by a user without write access
569861e
to
72efe8b
Compare
I think I need to rebase it again after your PR #6804 gets merged. |
Correct, sorry for the trouble 😞 |
No problem 🙂 |
72efe8b
to
ee1eb2b
Compare
Head branch was pushed to by a user without write access
Description
Continuation to #6749, #6690, #6683, #6680
Type of change
What type of changes does your code introduce to the Prometheus operator? Put an
x
in the box that apply.CHANGE
(fix or feature that would cause existing functionality to not work as expected)FEATURE
(non-breaking change which adds functionality)BUGFIX
(non-breaking change which fixes an issue)ENHANCEMENT
(non-breaking change which improves existing functionality)NONE
(if none of the other choices apply. Example, tooling, build system, CI, docs, etc.)Verification
Please check the Prometheus-Operator testing guidelines for recommendations about automated tests.
Changelog entry
Please put a one-line changelog entry below. This will be copied to the changelog file during the release process.