-
Notifications
You must be signed in to change notification settings - Fork 3
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
Flapping tests #1
Comments
this test checks actual temporal behavior of cache eviction, and is inherently racy and problematic. I'll try and make it more robust by pacing it differently. In any case, I do not think that these test failures are a sign of regressions in rakudo, they are simply a terrible test. Not sure how to make it better though... Out of interest: were you running these on a very slow or heavily loaded system? I can't get them to fail even with extra load on mine... |
That's correct, I never said they were :) The reason this ticket is linked from rakudo/rakudo#2047 is because this module showed up (because of flapping tests) when we were hunting for regressions.
Yes, toaster runs tests of a bunch of modules simultaneously, so that's heavy loaded for sure. But I was also able to reproduce it locally in a loop (took quite a bit, but it happened). |
right, I had another look but can't find a good way to make these tests truly stable in the presence of a loaded system. I have doubled the margins, given that they previously only failed for you sometimes, I guess that makes it quite unlikely now. I'll close the issue for now, but if anyone sees these flapping again then please let me know and I'll try to tune them further. |
When running the tests in a loop like this:
Sometimes I get this output:
The text was updated successfully, but these errors were encountered: