This seems good. We've now seen:
* the manual test case passing on raring * lots of builds running normally with the upgraded login package on saucy * a build being terminated correctly on saucy (https://launchpadlibrarian.net/146338663/buildlog_ubuntu-saucy-i386.llvm-toolchain-3.3_1%3A3.3-3ubuntu1_FAILEDTOBUILD.txt.gz) * builds running normally with the upgraded login package on raring (e.g. https://launchpadlibrarian.net/146376863/buildlog_ubuntu-raring-i386.whoopsie_0.2.15.1_UPLOADING.txt.gz) * a build being terminated correctly on raring (https://launchpadlibrarian.net/146386974/buildlog_ubuntu-raring-i386.hello_2.8-3ppa1_FAILEDTOBUILD.txt.gz)
This seems good. We've now seen:
* the manual test case passing on raring /launchpadlibra rian.net/ 146338663/ buildlog_ ubuntu- saucy-i386. llvm-toolchain- 3.3_1%3A3. 3-3ubuntu1_ FAILEDTOBUILD. txt.gz) /launchpadlibra rian.net/ 146376863/ buildlog_ ubuntu- raring- i386.whoopsie_ 0.2.15. 1_UPLOADING. txt.gz) /launchpadlibra rian.net/ 146386974/ buildlog_ ubuntu- raring- i386.hello_ 2.8-3ppa1_ FAILEDTOBUILD. txt.gz)
* lots of builds running normally with the upgraded login package on saucy
* a build being terminated correctly on saucy (https:/
* builds running normally with the upgraded login package on raring (e.g. https:/
* a build being terminated correctly on raring (https:/