| To: | Ken McDonell <kenj@xxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | QA temporaries |
| From: | Nathan Scott <nathans@xxxxxxxxxx> |
| Date: | Wed, 27 Nov 2013 17:08:41 -0500 (EST) |
| Cc: | PCP <pcp@xxxxxxxxxxx> |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <1626967316.19041413.1385589559423.JavaMail.root@xxxxxxxxxx> |
| Reply-to: | Nathan Scott <nathans@xxxxxxxxxx> |
| Thread-index: | +iLR0xWTyvgepEXFYXkTBisfJk7tzw== |
| Thread-topic: | QA temporaries |
Hi, I'm finding quite a few tests fail to cleanup temporaries and its fairly painful to try work out which ones after a full QA run. As a result, I'm thinking of tagging temporaries with a test sequence number for diagnosis, e.g.... qa$ diff common.rc common.rc.newtmp 85a86 > [ "X$seq" != X ] && tmp=/tmp/$seq.$$ There is test output filtering work to be done as a result of this kind of change, but I need to do something as my /tmp is starting to look like a dogs breakfast. Is there a better way you know of to trace these files back to the culprit test? cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [pcp] rpm pmda, Stan Cox |
|---|---|
| Next by Date: | RE: QA temporaries, Ken McDonell |
| Previous by Thread: | Re: [pcp] rpm pmda, Stan Cox |
| Next by Thread: | RE: QA temporaries, Ken McDonell |
| Indexes: | [Date] [Thread] [Top] [All Lists] |