CTRL-C or kill run.sh only terminates current test, not entire run

Bug #1097434 reported by George Ormond Lorch III on 2013-01-08
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraBackup
Wishlist
Alexey Kopytov
2.0
Wishlist
Alexey Kopytov
2.1
Wishlist
Alexey Kopytov

Bug Description

When running the test suite, using <ctrl-c> or kill SIGTERM only terminates the currently running test. run.sh will continue on to the next test in the series rather then cleaning up and terminating entirely.

Related branches

lp:~stewart/percona-xtrabackup/2.0-parallel-test
Alexey Kopytov (community): Approve on 2013-01-09
lp:~stewart/percona-xtrabackup/2.1-parallel-test
Alexey Kopytov (community): Approve on 2013-01-10
lp:~akopytov/percona-xtrabackup/test-suite-cleanups-2.0
George Ormond Lorch III: Approve (g2) on 2013-07-09
Stewart Smith: Pending requested 2013-07-04
lp:~akopytov/percona-xtrabackup/test-suite-cleanups-2.1
George Ormond Lorch III: Approve (g2) on 2013-07-09
Stewart Smith: Pending requested 2013-07-04

This is fixed in parallel test branch, where ctrl-c properly goes and
kills everything (I made sure of that).
--
Stewart Smith

Stewart -

That is great. Can you link this bug to those branches?

Alexey Kopytov (akopytov) wrote :

It's still has to be fixed in the test suite, rather than just in the parallel runner. For example, I may only want to use testrun.sh (in the parallel test branch) when I need to run the test suite locally. And that will still have the same problem with Ctrl-C.

What needs to be changed in the test suite is to have tests handle SIGINT and return a non-zero exit code.

Alexey Kopytov (akopytov) wrote :

Setting to Triaged as the linked branch contains only a partial fix.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers