-
Notifications
You must be signed in to change notification settings - Fork 103
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
Wrap test_linux_network_stacksmash_64
in a flaky rerunner (3 runs)
#103
Conversation
@twizmwazin how do you feel about this temporary solution? |
I don't really love it, but having the CI constantly fail is also bad. If this doesn't add a significant amount of time to a CI run its acceptable. |
I have no idea how much time this adds... how can I check?
…------- Original Message -------
On Friday, September 8th, 2023 at 4:57 PM, Kevin Phoenix ***@***.***> wrote:
I don't really love it, but having the CI constantly fail is also bad. If this doesn't add a significant amount of time to a CI run its acceptable.
—
Reply to this email directly, [view it on GitHub](#103 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AFCW3IAOX6RYHUQSZKFHCHLXZOWFFANCNFSM6AAAAAA4Q3WPXE).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
I would just look at how long that particular test took to execute and determine if adding 2x that is going to be a big deal overall. If it's under a minute it's probably not the end of the world. The test is failing to import right now though. |
Can we use https://github.com/box/flaky instead? |
I’m ok with that @ltfish as long as @twizmwazin is ok with a new dependency on this project |
Yes that's fine |
test_linux_network_stacksmash_64
in a flaky rerunner (3 runs)
The test case
test_linux_network_stacksmash_64
is constantly failing on runs inside the CI, whether people touch Rex-related components or not. Normally, I'd opt to remove this test altogether, but in lieu of that, I propose to rerun this single test multiple times.