[Piuparts-devel] Bug#920758: piuparts.d.o: more input for britney

Holger Levsen holger at layer-acht.org
Mon Jan 28 19:08:17 GMT 2019


package: piuparts.debian.org
severity: wishlist
x-debbugs-cc: debian-release at lists.debian.org, piuparts-devel at lists.alioth.debian.org

Hi Ivo & Niels,

On Sat, Jan 19, 2019 at 06:34:19PM +0100, Ivo De Decker wrote:
> > > > currently britney uses piuparts regressions comparing testing vs. sid to
> > > > block migrations. That's fine, since we should have few false positives
> > > > in sid nowadays.
> > > > It would be nice if we could use a similar scheme like autopkgtests uses
> > > > to delay migration for other tests, like sid-strict or testing2sid.
> > > > As in "if your package leaves files after purge, you don't get the
> > > > migration reduction from 5 to 2 days"
> > > > and for testing2sid (or stable2sid) there may be more false positives
> > > > caused by other packages, so it would be great to at least delay
> > > > migration by a few days as well, to allow manual inspection of the
> > > > failure, I several times didn't manage to file a bug within 2 days of
> > > > upload to prevent migration of a buggy package to testing ...
> > > 
> > > sounds like a splendid idea to me!
> > > 
> > > How can we get this going?
> > > 
> > > 
> > 
> > At its essence, it is a question of updating the PiupartsPolicy in
> > Britney[1] along with adding relevant test cases (either in "tests/" or
> > in britney2-tests[2]).
> > 
> > Once that is done, we can merge the code and update the britney wrapper
> > to fetch the relevant summary.json files from piuparts.d.o.
> > 
> > Hints as to the actual steps:
> > 
> >   * PiupartsPolicy.initialise should load the relevant summary files.
> >     (Difficulty level: copy-paste + rename things)
> > 
> >   * PiupartsPolicy.apply_src_policy_impl should analyse the new files
> >     and determine which delay to apply if any.  If a age delay is to be
> >     applied then the method should now call:
> >       excuse.add_penalty('piuparts', <delay-in-days-goes-here>)
> > 
> >   * TestPiupartsPolicy should be updated to include a case for it.  It
> >     might make sense to have PiupartsPolicy include a note in the
> >     policy_info so the test case can rely on that (rather than having
> >     to setup an AgePolicy as well for verification).
> > 
> > We have a ".gitlab-ci" on the git repo that runs all the basic test
> > cases for you on push to salsa.  Alternatively, have a look at the
> > ci/gitlab-ci-runner for how to run the tests manually.
> 
> On a related note:
> 
> - It would be nice to have detailed information about the binaries tested in
> the export, this would allow britney to use this information for binNMUs.
> Piuparts already tests binNMUs, but the info in the export only lists the
> source, not the binary (or the binary version), so that info isn't available
> yet. This would probably mean an incompatible change to the export (which
> can exist side by side with the current one). Do you have an idea about what
> services are processing this file? I know at least britney, tracker, udd and
> the old PTS have info from piuparts.
> 
> If the export is changed anyway, it could contain more detailed information
> about what tests failed and the severity of the failures. This might allow
> an easier implementation of the diversified result (block, delay, ...)

putting this into the BTS so this doesnt get forgotten.

> - Currently, it looks like buster-proposed-updates isn't tested by piuparts
> (which isn't a big deal, as there are no packages in there yet). Could this
> be added as a suite (together with buster2proposed)?

this is trivial and just needs a 3 line patch or so. Someone should do
something. Soon.


-- 
tschüß,
	Holger

-------------------------------------------------------------------------------
               holger@(debian|reproducible-builds|layer-acht).org
       PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/piuparts-devel/attachments/20190128/d293952a/attachment.sig>


More information about the Piuparts-devel mailing list