Rule #2 should die

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2015-06-04 05:42 PM, Martin Packman wrote:
> Currently juju-reports has a rule matching on failures where our
> CI harness interrupted the test because it took too long:
> 
> <http://reports.vapour.ws/releases/rules/2>
> 
> This seems too generic a symptom, generally if a test is not 
> completing within the time we've allocated for it, there's another 
> indication in the log, often the final `juju status` output, that 
> makes it clearer why juju never finished its work.

> That all the recent matches for the timeout rule have more useful
> and specific matches (some unfortunately needing to look at other
> log files for all the details), suggests we want those as rules
> rather than this.

I agree.  Now that we can see which attempts matched an issue, we can
see that
http://reports.vapour.ws/releases/2571/job/hp-upgrade-trusty-amd64/attempt/2878
was the first match, and probably motivated the rule.

In that case, there's no greater indication in the main log of what
went wrong.

But I would be happy to change the rule to handle that narrow case.
Something like:

Bootstrapping Juju machine agent\nTraceback \(most recent call
last\):(\n|.)*KeyboardInterrupt

What do you think of that?

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJVcasgAAoJEK84cMOcf+9hwMYH/13Ky/MWQgzBHQvQlM/tjjZs
ZZ7tqZTlEJv6mfEVoRGKLfeC8ktHh4J4VYB2nNVMkxovHTNB3LAZQmrnNtQLCrbU
rk3hc5VmLefsNAcUoct3E9OPBJJZRiW4p2mPJ1rId65bkTOKI9MW43WcQsgO58Ai
0/CO21DO2GbQY9IeZZqybiSGPTQqoEFwFq+3ODvlqhin/PgsX/kTCG2Qh0FeseRv
zaM6niHEjfW3bi9zZCy982p1nVWB9UssUf9CQPHsOIfzWfqAR0FCZXdhDtGF0Xaw
PSpGkmsmQOd0c9TntGGKbbj95Kip1p2svl1akYx8LhJY7uVR698P/mPLbGR5eKU=
=hF6+
-----END PGP SIGNATURE-----