<snip/>
> Is the status of PQM jobs available to non-core folks so we don't
> have to pester you guys? I found the queue page at
> http://pqm.bazaar-vcs.org/, but it doesn't list completed jobs,
That's because you don't refresh it often enough[1], if you are very very
lucky you may able to catch the number of failures and if you are even
more lucky you can get the name of the failing test(s).
> nor offer a link to a page that does.
None exists.
> All I knew from Launchpad and email was that it had been sent, and
> then no further status,
...
> just silence.
Yeah, the painful silence usually means something went wrong :-(
This is certainly one of the worst feedback you could get for a test
failure...
First steps of defense:
- run the full test suite locally,
- run make check | subunit2pyunit locally,
- run make check with python2.4 locally
If they all pass, bangs your head on the desktop (find a soft desktop if
you repeat the later too often) and nag the patch pilot :-/
If you've reached a high enough pain threshold, you can file a bug.
[1]: That's a painful joke if you didn't notice :)
<snip/> pqm.bazaar- vcs.org/, but it doesn't list completed jobs,
> Is the status of PQM jobs available to non-core folks so we don't
> have to pester you guys? I found the queue page at
> http://
That's because you don't refresh it often enough[1], if you are very very
lucky you may able to catch the number of failures and if you are even
more lucky you can get the name of the failing test(s).
> nor offer a link to a page that does.
None exists.
> All I knew from Launchpad and email was that it had been sent, and
> then no further status,
...
> just silence.
Yeah, the painful silence usually means something went wrong :-(
This is certainly one of the worst feedback you could get for a test
failure...
First steps of defense:
- run the full test suite locally,
- run make check | subunit2pyunit locally,
- run make check with python2.4 locally
If they all pass, bangs your head on the desktop (find a soft desktop if
you repeat the later too often) and nag the patch pilot :-/
If you've reached a high enough pain threshold, you can file a bug.
[1]: That's a painful joke if you didn't notice :)