| To: | "Frank Ch. Eigler" <fche@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] pcp updates, pcpfans.git fche/dev |
| From: | Nathan Scott <nathans@xxxxxxxxxx> |
| Date: | Thu, 30 Oct 2014 16:54:29 -0400 (EDT) |
| Cc: | pcp developers <pcp@xxxxxxxxxxx> |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <20141030203255.GA1913@xxxxxxxxxx> |
| References: | <20141030203255.GA1913@xxxxxxxxxx> |
| Reply-to: | Nathan Scott <nathans@xxxxxxxxxx> |
| Thread-index: | LyJOVqJ5A8PSJKAqWVzWbZ+5Gb2sHQ== |
| Thread-topic: | pcp updates, pcpfans.git fche/dev |
----- Original Message ----- > [...] > commit 0aeeb740dfcc1c21460e62a648fd4299b57c41f1 (HEAD, origin/fche/dev, > fche/dev) > Author: Frank Ch. Eigler <fche@xxxxxxxxxx> > Date: Wed Apr 9 13:28:14 2014 -0400 > > pmmgr testing: quicken, avoid some granularity-edge races > > After concerns, the time taken by the pmmgr 666 test case are now > reduced to about 6 minutes. Hmmm, sorry, I thought you said you were going to fix this? Couple releases back, most recently ... http://www.pcp.io/pipermail/pcp/2014-August/005374.html So, I've been waiting on that - 6 minutes is still far longer than any other test of course (more than double?) - even though it is down from the original 20 minutes, which is great. Those other long running tests (in the 2-3 minute range) are already a problem & need to be improved too if we can. thanks. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | pcp updates, pcpfans.git fche/dev, Frank Ch. Eigler |
|---|---|
| Next by Date: | Re: [pcp] rpm-based build failures .. moved to python code, Nathan Scott |
| Previous by Thread: | pcp updates, pcpfans.git fche/dev, Frank Ch. Eigler |
| Next by Thread: | Re: [pcp] pcp updates, pcpfans.git fche/dev, Ken McDonell |
| Indexes: | [Date] [Thread] [Top] [All Lists] |