touch-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

Uploading gcc already triggers (e)glibc, binutils, linux, and pretty
much every single other autopkgtest, so there's nothing to change here.
The mutual rebuilding has worked quite well, aside from the fact that
glibc's autopkgtest has never succeeded (so it's not taken into
account). Ironically the obsolete eglibc autopkgtest still succeeds.

** Changed in: gcc-4.7 (Ubuntu)
       Status: Confirmed => Invalid

** Changed in: auto-package-testing
       Status: Triaged => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1081500

Title:
  Add autopkgtest for mutual rebuild-testing amongst glibc, linux-libc-
  dev, gcc, and binutils

Status in Automated Testing of Ubuntu Packages:
  Won't Fix
Status in “binutils” package in Ubuntu:
  Fix Released
Status in “eglibc” package in Ubuntu:
  Fix Released
Status in “gcc-4.7” package in Ubuntu:
  Invalid
Status in “linux” package in Ubuntu:
  Fix Released

Bug description:
  Adam just suggested the following:

  infinity        pitti: I'd suggest (since things like "try to rebuild the whole archive" would be pointless) they their tests should consist of each one triggering a rebuild test of the other two.
  infinity        pitti: If upgrading any of those three manages to keep the testsuite of the others passing, that's a win.
  infinity: i. e. the test script woudl more or less be "apt-get build-dep binutils; apt-get source -b binutils", right?
  infinity        pitti: (This came up today after I just spent hours fixing a regression in glibc due to the new gcc, and the inverse happens all the time too)
  infinity        pitti: Yeahp.
  infinity        pitti: Oh, and linux-libc-dev (so, the linux source package) should also trigger those three to a rebuild test, same reason.
  infinity        pitti: If linux-libc-dev's headers survive the GCC and glibc testsuites, they're good enough for regular users. :P
  infinity        (And if they break regular users but not the toolchain, I'd humbly suggest the users are wrong)
  infinity        Definitely would have been nice to know when gcc and the kernel were uploaded (so, a couple of weeks ago) that they broke glibc, instead of finding out today while I was uploading for other reasons.
  infinity        pitti: To cut down on the pain, we could potentially refine the tests to do something like only build a single pass of libc6 and run the tests, only build a single kernel, etc.  Most of these things take so effin' long cause they build 4 times.

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1081500/+subscriptions