Hardcoded absulute path in the xb_export test
Bug #733811 reported by
Alexey Kopytov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Fix Released
|
Medium
|
Valentine Gostev | ||
Bug Description
xb_export.sh uses a hardcoded absolute path to create a temporary backup:
backup_
Today I ran into a problem when there was a directory with the same name left from another test run by someone else. It was a shared machine and I didn't have root access, so there was nothing I could do to fix that. I think we should never use absolute paths in the tests, all directories and files must be created in the test root directory ($topdir).
Related branches
lp:~percona-dev/percona-xtrabackup/port_to_latest
- Vadim Tkachenko: Approve
-
Diff: 2595 lines (+558/-499)16 files modifiedMakefile (+4/-0)
fix_innodb_for_backup51.patch (+53/-53)
fix_innodb_for_backup55.patch (+83/-84)
fix_innodb_for_backup_5.1_plugin.patch (+59/-59)
fix_innodb_for_backup_percona-server.patch (+74/-74)
test/inc/common.sh (+10/-1)
test/run.sh (+1/-1)
test/t/xb_export.sh (+12/-10)
test/t/xb_incremental.sh (+10/-5)
test/t/xb_incremental_compressed.sh (+8/-7)
test/t/xb_part_range.sh (+10/-5)
test/t/xb_partial.sh (+4/-2)
utils/build.sh (+178/-179)
utils/debian/rules (+3/-3)
utils/xtrabackup.spec (+4/-4)
xtrabackup.c (+45/-12)
| Changed in percona-xtrabackup: | |
| status: | New → Fix Committed |
Revision history for this message
| Stewart Smith (stewart) wrote | #1 |
| Changed in percona-xtrabackup: | |
| importance: | Undecided → Medium |
| assignee: | nobody → Alexey Kopytov (akopytov) |
| milestone: | none → 1.7 |
Revision history for this message
| Valentine Gostev (longbow) wrote | #2 |
| Changed in percona-xtrabackup: | |
| assignee: | Alexey Kopytov (akopytov) → Valentine Gostev (longbow) |
| Changed in percona-xtrabackup: | |
| status: | Fix Committed → Fix Released |
Revision history for this message
| Shahriyar Rzayev (rzayev-sehriyar) wrote | #3 |
To post a comment you must log in.
I'm guessing this is in for 1.7... if not, please correct.