Bug #48529 mysqltest: --exec print on failure
Submitted: 4 Nov 2009 11:52 Modified: 4 Nov 2009 11:59
Reporter: Jørgen Austvik Email Updates:
Status: Verified Impact on me:
Category:Tools: MTR / mysql-test-run Severity:S4 (Feature request)
Version:5.1+ OS:Any
Assigned to: CPU Architecture:Any

[4 Nov 2009 11:52] Jørgen Austvik
Today --exec prints STDOUT (and STDERR?) to console and fail the test if exit code != 0.

We sould like to have a "--exit-print-on-failure <cmd>" "--exec print_if_failure <cmd>", "--exec-test <cmd>" or similar that behaves like --exec today, but prints STDERR and STDOUT on exit code != 0.

We would use this in e.g. suite/ndb/ndb_jtie.test for running JUnit tests from MTR. Today we redirect all output to a file, but this makes it somewhat difficult to diagnose what is going on for somebody that does not know about the special files for this test.

How to repeat:
feature request

Suggested fix:
Implement it :)
[10 Nov 2009 19:16] Sergei Golubchik
why don't you create a script to reformat junit output to tap ? then all your tests would be picked up automatically by 'make test-unit'
[11 Nov 2009 8:26] Jørgen Austvik
Because this was how Magnus suggested it.

I didn't know anything about "picked up automatically by make test-unit". Do you have any pointers to where this is documented?