Bug#708184: collab-qa/cloud-scripts/masternode: Add support for specifying output directory

2013-05-13 Thread Nathaniel Harrison Handler
Package: qa.debian.org Severity: wishlist Currently, when the masternode script is run, logs are copied to /tmp/logs automatically. It would be nice to support specifying an alternate directory for the logs. This would allow multiple instances of masternode to run simultaneously on the same mac

Re: archive rebuilds, step 2

2013-05-13 Thread Lucas Nussbaum
On 13/05/13 at 22:24 +0200, David Suárez wrote: > Hi, > > You can find the Failure logs at https://gist.github.com/deiv/5570248 > > Im going for the bonus task. Excellent! > By the way, the same logic that do 'fetch-and-process-results-aws' can not > be > replicated with the -r argument of c

Re: archive rebuilds, step 2

2013-05-13 Thread David Suárez
Hi, You can find the Failure logs at https://gist.github.com/deiv/5570248 Im going for the bonus task. By the way, the same logic that do 'fetch-and-process-results-aws' can not be replicated with the -r argument of cqa-scanlogs, something like 'cqa-scanlogs -r Failed' ? (assuming we will onl

Re: archive rebuilds, step 2

2013-05-13 Thread Lucas Nussbaum
Hi, So, Step 2. I described it as: Scan the logs (that's done automatically), generate list of failures. Also upload the logs to some public place At the end of Step 1, we have all the logs on EC2 in /tmp/logs. In Step 2, we will: - scan the logs to identify failed builds. For that, we wi