Random crud left behind by aborted TAP tests

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-hackers(at)postgreSQL(dot)org
Subject: Random crud left behind by aborted TAP tests
Date: 2015-12-04 16:09:11
Message-ID: 31848.1449245351@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Yesterday I was fooling around with the TAP tests, and at least once
I changed my mind and control-C'd out of a run. Today I find:

[postgres(at)sss1 pgsql]$ git status
On branch master
Your branch is up-to-date with 'origin/master'.

Untracked files:
(use "git add <file>..." to include in what will be committed)

src/bin/scripts/tmp_testGvBC/

nothing added to commit but untracked files present (use "git add" to track)
[postgres(at)sss1 pgsql]$ ls src/bin/scripts/tmp_testGvBC
archives/ backup/ pgdata/

"make distclean" doesn't get rid of it either; I'll have to remove it
manually.

Judging by the subdirectory names, this is "_basedir" of some PostgresNode
instance. Should this not have been put inside "tmp_check/" so that
existing make clean/distclean rules could take care of it?

regards, tom lane

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2015-12-04 16:10:19 Re: Re: In-core regression tests for replication, cascading, archiving, PITR, etc.
Previous Message Andres Freund 2015-12-04 16:08:42 Re: atomic reads & writes (with no barriers)