[pilot] Summary September 2nd

[John Arbash Meinel]

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

On 09/05/2011 09:29 AM, vila wrote:
> Hi,
> 
> My name is vila and I've been your Patch Pilot this week.
> 
> The week was intense:
> 
>   http://webnumbr.com/.join%28bzr-active-reviews,bzr-pqm-queue-length,bzr-merged-reviews.derivative%29
> 
> Our landings were slowed down significantly and the consensus was that
> our pqm bot was suffering from fdatasync fallouts (from 1h and 1/2 to
>> 3h, also 2h seem to be the average and spikes have been observed on the
> 2.3 branch), all in all: weird stuff)... which jam addressed
> (https://code.launchpad.net/~jameinel/bzr/2.4-disable-selftest-fdatasync-837293/+merge/73757)
> for the 2.4 branch (hopefully he'll merge that to trunk soon).

Landed on trunk. I'm sprinting with the U1 guys this week (who shared
the PQM box). It seems our fdatasync stuff was impacting there test
suite to the point that it was failing 8 times out of 10 or so.
Apparently twisted defaults to having an explicit timeout on each test,
and the load/sync/whatever was causing tests to timeout enough that they
couldn't land their branches.

So they currently set up Tarmac on Canonistack, and originally just had
it running on someone's local machine.

I mentioned elsewhere some limitations for *us* with Tarmac for bzr.
Bits like "the full stderr + stdout is posted to Launchpad for a failing
test", and "there is minimal visibility into the test suite run".

I believe they handled the visibility issue by copying stderr/out to a
temp file, and then exporting that via an HTTP service.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk5mEDgACgkQJdeBCYSNAAMdNACfaNt45xRuqzzh6Kij+iH1RIlh
BrMAoMKcNS/30DoTu/QuOcpbVMIWFopq
=MSy2
-----END PGP SIGNATURE-----