Jenkins valgrind configurations stop after 10 errors

Bug #894324 reported by Laurynas Biveinis
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Released
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.,Host=ubuntu-natty-32bit/console :

Too many failed: Failed 10/827 tests, 98.79% were successful.

This test report graph confirms the Valgrind test coverage getting poorer and poorer:

Changed in percona-projects-qa:
importance: Undecided → Critical
Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

It seems that this is true not only for valgrind, but for all configs (!). Fixing.

Changed in percona-projects-qa:
assignee: nobody → Laurynas Biveinis (laurynas-biveinis)
status: New → In Progress
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.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.