On 10/02/15 00:40, Martin Pitt wrote: > Hey Matthias, > > Matthias Klose [2015-02-06 14:31 +0100]: >> A test rebuild of Vivid Vervet was started this week for all >> architectures, and is finished for the main component. >> >> Results can be found at >> >> http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20150202-vivid.html > > Thanks! > > This looks a bit confusing, though. E. g. the pygobject-2 "→ Log" link > just points back to the same overview page, and the "i386 (F)" link > leads to > https://launchpad.net/ubuntu/+archive/test-rebuild-20150202/+build/6833261 > which has no build log at all. So while having an indication that a > build failed is already useful, having the actual logs would be very > helpful (and we did have them in the past). > > Were they removed because of the other test build that's currently > going on?
A failed build without a log means that something went catastrophically wrong, so there was no log that could be provided. Usually it means the build took the builder down, or there was a network fault. In this case there was a librarian glitch preventing the builder from downloading the dsc. I've retried the build.
signature.asc
Description: OpenPGP digital signature
-- ubuntu-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
