glibc/eglibc: proposed promotion to security/updates

[Martin Pitt]

Hello all,ll

Steve Langasek [2016-05-25 11:26 -0700]:
>  - Tests that we know were buggy, as of release.  We have a way to mark
>    these tests as bad, it's a "force-badtest" proposed-migration hint; we
>    use these hints routinely for the devel series, but we haven't been
>    carrying them over to the stable releases despite having the
>    infrastructure for it (e.g.:
>    lp:~ubuntu-sru/britney/hints-ubuntu-trusty/ has a hints file, and all the
>    others are empty).  So first, we should copy over badtest hints when we
>    make a new stable release so we have reasonable baseline data.

We can still do this after the fact, and branch off hints-ubuntu at
the appropriate revision.

>  - Tests that regressed due to infrastructure changes.  We try to keep the
>    testbed unchanged throughout the lifecycle of a release, but it's a
>    complex system and regressions can happen; including regressions
>    introduced by SRUs of "unrelated" packages that thus evaded detection.  I
>    think we should address these by periodically resetting the baseline for
>    tests in the stable release - rerunning all autopkgtests for
>    release+updates, and capturing this as the new baseline against which
>    test regressions are measured.  If we could do this, say, once every 3
>    months, it should cut down on the busywork of chasing false positives.
>    Martin, is this something that would be possible to implement?

They are simple enough to launch, they will just take effing long. But
we often have some quiet times such as during freezes, when we can use
the infra for these purposes. I would implement a "low priority" queue
for that though, so that they won't starve "real" test requests from
-proposed.

We can run them without a trigger and a special test request option,
so that we can mechanically identify them in the results.

However, with proper hints we should already get most of the effect.
Until now I had actually assumed that hints-ubuntu applied to all
releases simultaneously. That's why I recently implemented [1] as I
was hoping that this was the reason for the false regressions in SRUs.

Thanks,

Martin

[1] http://bazaar.launchpad.net/~ubuntu-release/britney/britney2-ubuntu/revision/595


-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/ubuntu-release/attachments/20160526/970e4bf9/attachment.pgp>