-
Notifications
You must be signed in to change notification settings - Fork 66
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
common: treat code compiled with coverage as debug #570
Conversation
since there are some slowdowns with coverage enabled binary we temporary treat it as debug, so all test that were tuned down for debug in dtest, would be have the same as they do for debug.
feel free to take it for a ride in jenkins I've test this locally run test_bulk_round_trip_with_timeouts x30 in parralell
before this change 80% of the runs would fail, after it all of them passed |
LGTM, but now I'm rethinking if we need to run in CI both this and the regular dtest. |
The assumption the coverage doesn't slow down anything, is probably wrong, and you'll still have this issue even if we'll move this part into dtest and do that for specific places |
There was not such assumption, the assumption is that the tests should handle or be able to run on any machine, slow or fast. |
@fruch seems like it works for |
so the direction should be not to change the mode, but to this this code/logic into dtest, and do it for the specific tests |
@benipeled move this code into dtest, closing |
since there are some slowdowns with coverage enabled binary we temporary treat it as debug, so all test that were tuned down for debug in dtest, would be have the same as they do for debug.