Bug #48316 Extra backup tests are not run for various reasons.
Submitted: 26 Oct 2009 15:29 Modified: 28 Oct 2009 10:58
Reporter: Rafal Somla Email Updates:
Status: Won't fix Impact on me:
None 
Category:Tests: Backup Severity:S3 (Non-critical)
Version: OS:Any
Assigned to: CPU Architecture:Any

[26 Oct 2009 15:29] Rafal Somla
Description:
Backup tests which are not part of the regression test suite (daily/weekly tests, unittests) are not run or not correctly reported in PB. This bug is not about failures in these tests, but about ensuring that they are run as planned and that failures in them are correctly reported. This concerns the following tests:

- mysql-6.0-backup.daily collection.
- mysql-6.0-backup.weekly collection.
- unittests in unittest/backup directory.

Here are some related issues already reported as bugs:

BUG#43956 - Run RQG collections tests in PB2
BUG#48282 - restore_stress test: mysql-stress-test tool can't find mysqltest 
            utility in PB2
Bug#47827 - PB2: perl test exits with code 1, but test is not reported as failed
Bug#45873 - Can't run unittests in PB
BUG#47540 - Backup unit tests errors on Solaris

How to repeat:
1. See pushbild results for daily tests in mysql-6.0-backup tree. Most of the tests are skipped, others fail.

2. I can't see any trace of weekly tests being run (maybe I don't know where to look).

3. I don't see any trace of backup unit tests being run (maybe I don't know where to look).

Suggested fix:
Make sure that all problems which stop these tests from being run are reported as bugs and fixed.
[28 Oct 2009 10:58] Rafal Somla
This bug was replaced by WL#5153.