xtrabackup test suite leaves xtrabackup.mysql.sock and xtrabackup_port_lock files behind in /tmp

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

Bug Description

run xtrabackup test suite (run.sh), on success or failure it leaves xtrabackup.mysql.sock and xtrabackup.mysql.sock behind in /tmp for each test started.

Alexey Kopytov (akopytov) wrote :

I think they should be removed with recent XtraBackup versions. Is this still repeatable?

Changed in percona-xtrabackup:
status: New → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for Percona XtraBackup because there has been no activity for 60 days.]

Changed in percona-xtrabackup:
status: Incomplete → Expired
Alexey Kopytov (akopytov) wrote :

I think I've found why and when this can happen while implementing some test suite cleanups.

Alexey Kopytov <email address hidden> writes:
> I think I've found why and when this can happen while implementing some
> test suite cleanups.

I've found this too - hopefully we found the same thing and there
weren't two bugs :)

Fixed in
https://code.launchpad.net/~stewart/percona-xtrabackup/test-combinations/+merge/171012

Specifically:
http://bazaar.launchpad.net/~stewart/percona-xtrabackup/test-combinations/revision/615
and then
http://bazaar.launchpad.net/~stewart/percona-xtrabackup/test-combinations/revision/619

as the first go wasn't really complete.

--
Stewart Smith

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

Other bug subscribers