Jenkins valgrind configurations stop after 10 errors
Bug #894324 reported by
Laurynas Biveinis
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
percona-projects-qa |
Fix Released
|
Critical
|
Laurynas Biveinis |
Bug Description
Even though --force seems to be specified, it always stops after 10 errors and consequently a big part of tests is never run.
Too many failed: Failed 10/827 tests, 98.79% were successful.
This test report graph confirms the Valgrind test coverage getting poorer and poorer:
http://
Changed in percona-projects-qa: | |
importance: | Undecided → Critical |
Changed in percona-projects-qa: | |
status: | In Progress → Fix Committed |
Changed in percona-projects-qa: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
It seems that this is true not only for valgrind, but for all configs (!). Fixing.