-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
roachtest: add failure message to test if post validations fail #98366
Comments
cc @cockroachdb/test-eng |
Post validations are done during
The validation failures should still show up in the artifacts as a @aliher1911 just confirming that you expect to see some indication that a post validation failed in test.log, and not just the presence of the failure.log |
Ideally all I want is not to chase errors. In vanilla test failure case I see the error in test log and I can go to the source to see what failed. If there was some remote command involved, I can go to artifacts and find one that failed to see the actual output. With new post validations, there would be no test failure to go to. So I need to look through artifacts to find which one of the failed commands is the real failure. There could be more than one because recovery tests fail some things in successful test runs. From my point of view having validators in test.log is a good idea as teardown.log is the last place I would go to when trying to fix broken test. But I don't have a big picture. |
Epic: none Fixes: cockroachdb#98366 Release note: None
Epic: none Fixes: cockroachdb#98366 Release note: None
103946: roachtest: categorise post-test assertions separately r=smg260 a=smg260 roachtest: categorise post-test assertion errors separately 1. Simple change to mark failures that occur in post-test validation (teardown), so that we can more clearly report a test that has experience a failure after its execution has ended. 2. Every test, unless opted-out, runs various post validations such as node liveness and consistency checks. These checks have been moved to their own function, and failures that occur here are now logged to a separate file, and indicated as such in github when an issue is created.\ \ Previously, these checks were done during teardown and logged to the teardown.log. Epic: none Fixes: #98366 Release note: None Co-authored-by: Miral Gadani <[email protected]>
Epic: none Fixes: cockroachdb#98366 Release note: None
In #96949 we added post-test validations for roachtests.
When validation fails GH task is created with an error like
but linked test log in artifacts end with
indicating that test was successful.
It would be helpful to have this failures consistent with "normal" test failures and be visible in artifacts.zip.
Example failure: #97912
Jira issue: CRDB-25228
The text was updated successfully, but these errors were encountered: