quest-autopkgtests.py and
> display-filtered-autopkgtests-results-summary.py.
>
> Example use case:
>
> ./request-autopkgtests.py ppa:ubuntu-mozilla-security/ppa firefox 81
> # after all the tests have completed (check periodically at
> http://autopkgtest.ubuntu.com/running)
&g
tests have completed (check periodically at
http://autopkgtest.ubuntu.com/running)
./display-filtered-autopkgtests-results-summary.py
ppa:ubuntu-mozilla-security/ppa firefox bionic 20200916
I use those scripts daily and they're a big time saver.
Suggestions and improvements welcome, and I'm
On Tue, Sep 15, 2020 at 03:53:01PM +0200, Lukas Märdian wrote:
> * Upload your package (incl. debian/tests/*) to your PPA
> * Get a core-dev/MOTU to trigger the test for you, via this URL scheme:
> https://autopkgtest.ubuntu.com/request.cgi?release=RELEASE&arch=ARCH&package=SRCPKG
> *&ppa=LPUSER/PP
On Wed, Sep 16, 2020 at 12:02:48PM +0100, Dimitri John Ledkov wrote:
> Are we using PAM today already? Cause on riscv64 builder I started to see
>
> E: PAM error: Authentication token is no longer valid; new one required
> Chroot setup failed
> E: Error creating chroot session: skipping openssl
s
On Wed, Sep 16, 2020 at 1:07 PM Lukas Märdian
wrote:
>
> Hello all,
>
> I'm currently working on a problem where an autopkgtest works fine in local
> autopkgtest testrunners (QEMU based), but it fails in different ways on the
> real Ubuntu autopkgtest infrastructure [0] (networking related issue
Hello all,
I'm currently working on a problem where an autopkgtest works fine in local
autopkgtest testrunners (QEMU based), but it fails in different ways on the
real Ubuntu autopkgtest infrastructure [0] (networking related issues).
Some developers use Bileto [1] to reproduce tests in such situ
On Wed, 16 Sep 2020 at 11:35, Colin Watson wrote:
>
> On Wed, Sep 16, 2020 at 10:22:05AM +0100, Dimitri John Ledkov wrote:
> > chroot builders do call ~= `sudo chroot` at some point.
>
> The main work is done by sbuild, which uses schroot, not "sudo chroot".
>
> (We used to use sbuild's sudo sessi
On Wed, Sep 16, 2020 at 10:22:05AM +0100, Dimitri John Ledkov wrote:
> chroot builders do call ~= `sudo chroot` at some point.
The main work is done by sbuild, which uses schroot, not "sudo chroot".
(We used to use sbuild's sudo session mode, but I changed that to
schroot in 2017.)
> would chang
On Wed, 9 Sep 2020 at 23:25, Steve Langasek wrote:
>
> On Wed, Sep 09, 2020 at 10:33:00AM +0100, Dimitri John Ledkov wrote:
> > > Failing that, can somebody advise on whether there's an appropriate way
> > > to configure this in an image without having to maintain a fork of
> > > systemd? The wor
