autopkgtest.ubuntu.com - User Page
Greetings! We have a new feature for autopkgtest - in the Release Management team we recently finished working on our new "User Page". This page can be reached at: https://autopkgtest.ubuntu.com/user// Or by logging in, and clicking on your username in the navbar. This page lists all of your currently queued and running tests, as well as all of your test results. There's a navigation section where you can choose to view only queued, only running, or only previous test results. The previous test results has pagination and you can go back as far as you need :) A disclaimer - PPA test results aren't supported on this page. Big thanks to Simon Chopin for requesting this new feature! We hope you all like it and if you run into any issues, please contact us on #ubuntu-quality on IRC. Thanks! Tim Andersson, Paride Legovini, Florent (Skia) Jacquet & Brian Murray -- [image: Canonical-20th-anniversary] *Tim Andersson* Software Engineer (Canonical Ubuntu Release Management) Email: tim.anders...@canonical.com Location: United Kingdom canonical.com ubuntu.com -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
autopkgtest.ubuntu.com - all-proposed in retries, running page and results pages
Hi all! We recently made some quality of life changes to autopkgtest.ubuntu.com, and thought we'd share them with you all. Up until now, when requesting a test with "all-proposed=1" via the webpage, you could never see on the results or running pages whether a test was requested with or without "all-proposed=1" (for those wondering what this means in practice, it just means that when installing packages on the testbed, *all* of them are installed from the proposed pocket, rather than just the specified triggers). This is now amended (fixing [1]). We added a new column to the results page, titled "env", in which you can see "all-proposed=1" if the test was requested with this additional param (nothing will be displayed if it wasn't). You will also now start seeing "all-proposed: 1" on the /running page for tests that were requested with this additional param. Additionally to this, when retrying a test by clicking the retry button on the results page, "all-proposed=1" is now preserved when retrying. For those wondering why we titled the column "env" and not "all-proposed", we intend to use this "env" column for additional features in the future. If you run into any issues regarding this feature or any others, please contact us on IRC in the #ubuntu-quality channel. Regards, Tim [1] https://bugs.launchpad.net/auto-package-testing/+bug/1999163 -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Duplicate Requests in autopkgtest-cloud
Hi Athos, Sorry, we overwrote the hotfix the other day with a deployment, sorry. I've reinstated it now. Please let me know if you have any issues! Regards, Tim On Wed, 16 Aug 2023 at 16:54, Athos Ribeiro wrote: > On Fri, Jul 28, 2023 at 10:01:50AM +0100, Tim Andersson wrote: > >Hi Steve, > > > >This is something I missed in the initial implementation, but there's now > >an MP for a fix ready to go into master. Right now, however, I've hotfixed > >prod so that if you pass `all-proposed`, the duplicate request check is > >disabled. I made this quick change to unblock ginggs > > Hi Tim, > > is the hotfix still up? > > I just got a request with all-proposed blocked because a request without > it was queued. > > > > >On Fri, Jul 28, 2023 at 5:19 AM Steve Langasek > > >wrote: > > > >> Hi Tim, > >> > >> On Thu, Jul 27, 2023 at 11:10:05AM +0100, Tim Andersson wrote: > >> > Hi all, > >> > >> > In the Ubuntu QA team we recently made and deployed a change which now > >> > makes it impossible to queue duplicate requests. > >> > >> > If a request is currently in the queue, or is currently running, and > you > >> > request the same test, you will be taken to an error page which tells > you > >> > the test details and whether it is currently queued or currently > running. > >> > It looks like this: > >> > ``` > >> > > >> > You submitted an invalid request: > >> > > >> > Test already queued: > >> > > >> > release: lunar > >> > > >> > pkg: gzip > >> > > >> > arch: arm64 > >> > > >> > triggers: gzip/1.12-1ubuntu1 > >> > > >> > ``` > >> > This is to try and ease the load on autopkgtest-cloud. > >> > >> > If you experience any bugs or unexpected functionality, please file a > bug > >> > against `autopkgtest-cloud` and let us know. We expect it to work > >> > seamlessly but always expect the unexpected right :) > >> > >> Does the code also properly distinguish between tests queued with > >> proposed=1 > >> and those without, so that it's possible to queue both ways in parallel? > >> > >> Thanks, > > -- > Athos Ribeiro > > -- > ubuntu-devel mailing list > ubuntu-devel@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel > -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Duplicate Requests in autopkgtest-cloud
Hey Utkarsh, Thanks for reporting this! Yeah we've recently become aware of this. It takes a few seconds for a request to hit the queue, so if you spam refresh or re-queue you can queue multiple times. Not really sure how to amend this just yet, but we'll look to amend it in the future. Thanks, Tim On Tue, Aug 8, 2023 at 3:50 PM Utkarsh Gupta wrote: > Hi Tim, > > On Thu, Jul 27, 2023 at 4:01 PM Tim Andersson > wrote: > > In the Ubuntu QA team we recently made and deployed a change > > which now makes it impossible to queue duplicate requests. > > Super, this is great stuff! > > However, this isn't working as advertised. Or perhaps I've gotten it > wrong. But I wanted to trigger 'livecd-rootfs/23.10.12' for > mantic/ppc64el and I did but just to try the whole duplicating thing, > I did another time, and it did again. On the third time, however, it > said it's already queued. Upon checking > https://autopkgtest.ubuntu.com/running, I can confirm that the > autopkgtest is running twice, triggered 9 seconds apart. Is that > anyhow expected? > > > - u > -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Duplicate Requests in autopkgtest-cloud
Hi Steve, This is something I missed in the initial implementation, but there's now an MP for a fix ready to go into master. Right now, however, I've hotfixed prod so that if you pass `all-proposed`, the duplicate request check is disabled. I made this quick change to unblock ginggs Regards, Tim On Fri, Jul 28, 2023 at 5:19 AM Steve Langasek wrote: > Hi Tim, > > On Thu, Jul 27, 2023 at 11:10:05AM +0100, Tim Andersson wrote: > > Hi all, > > > In the Ubuntu QA team we recently made and deployed a change which now > > makes it impossible to queue duplicate requests. > > > If a request is currently in the queue, or is currently running, and you > > request the same test, you will be taken to an error page which tells you > > the test details and whether it is currently queued or currently running. > > It looks like this: > > ``` > > > > You submitted an invalid request: > > > > Test already queued: > > > > release: lunar > > > > pkg: gzip > > > > arch: arm64 > > > > triggers: gzip/1.12-1ubuntu1 > > > > ``` > > This is to try and ease the load on autopkgtest-cloud. > > > If you experience any bugs or unexpected functionality, please file a bug > > against `autopkgtest-cloud` and let us know. We expect it to work > > seamlessly but always expect the unexpected right :) > > Does the code also properly distinguish between tests queued with > proposed=1 > and those without, so that it's possible to queue both ways in parallel? > > Thanks, > -- > Steve Langasek Give me a lever long enough and a Free OS > Debian Developer to set it on, and I can move the world. > Ubuntu Developer https://www.debian.org/ > slanga...@ubuntu.com vor...@debian.org > -- > ubuntu-devel mailing list > ubuntu-devel@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel > -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Duplicate Requests in autopkgtest-cloud
Hi all, In the Ubuntu QA team we recently made and deployed a change which now makes it impossible to queue duplicate requests. If a request is currently in the queue, or is currently running, and you request the same test, you will be taken to an error page which tells you the test details and whether it is currently queued or currently running. It looks like this: ``` You submitted an invalid request: Test already queued: release: lunar pkg: gzip arch: arm64 triggers: gzip/1.12-1ubuntu1 ``` This is to try and ease the load on autopkgtest-cloud. If you experience any bugs or unexpected functionality, please file a bug against `autopkgtest-cloud` and let us know. We expect it to work seamlessly but always expect the unexpected right :) Thanks, Ubuntu QA -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Timestamps added to logs in autopkgtest and autopkgtest-cloud
Hey there, Recently in Canonical Ubuntu QA we made some changes to autopkgtest which went into both upstream and ubuntu-devel which preprends timestamps to the logs. The timestamps are in seconds and are measured since the beginning of all the tests when you run autopkgtest against a package. We hope that this can make it easier to extract valuable information from log files when reading logs from the autopkgtest-cloud environment. It can help with determining where tests are hanging, for instance. A log snippet can be seen below: ``` 0s autopkgtest [18:59:38]: starting date and time: 2023-06-12 18:59:38+0100 0s autopkgtest [18:59:38]: git checkout: a2cc92d Merge branch 'add_timestamp_to_logs' into 'master' 0s autopkgtest [18:59:38]: host duckstation7; command line: runner/autopkgtest -o /home/andersson123/tests/ mawk -- qemu --ram-size=1536 --cpus 2 /home/andersson123/canonical/images/autopkgtest-lunar-amd64.img 13s autopkgtest [18:59:51]: testbed dpkg architecture: amd64 17s autopkgtest [18:59:55]: testbed running kernel: Linux 6.2.0-20-generic #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 6 07:48:48 UTC 2023 17s autopkgtest [18:59:55]: apt-source mawk 19s Get:1 http://archive.ubuntu.com/ubuntu lunar/main mawk 1.3.4.20200120-3.1 (dsc) [1,776 B] 19s Get:2 http://archive.ubuntu.com/ubuntu lunar/main mawk 1.3.4.20200120-3.1 (tar) [469 kB] 19s Get:3 http://archive.ubuntu.com/ubuntu lunar/main mawk 1.3.4.20200120-3.1 (diff) [14.1 kB] 19s gpgv: Signature made Fri 17 Jun 2022 04:38:22 PM BST 19s gpgv:using RSA key 406220C8B8552802378CCE411F5C7A8B45564314 19s gpgv:issuer "b...@debian.org" 19s gpgv: Can't check signature: No public key 19s dpkg-source: warning: cannot verify inline signature for ./mawk_1.3.4.20200120-3.1.dsc: no acceptable signature found 19s autopkgtest [18:59:57]: testing package mawk version 1.3.4.20200120-3.1 19s autopkgtest [18:59:57]: build not needed 20s autopkgtest [18:59:58]: test mawktest: preparing testbed 22s Reading package lists... 22s Building dependency tree... 22s Reading state information... 22s Starting pkgProblemResolver with broken count: 0 22s Starting 2 pkgProblemResolver with broken count: 0 ``` It does not prepend the timestamp to stdout, just to the log file itself. You will soon start seeing this in all logs in autopkgtest-cloud soon. Let us know if you run into any issues. If you use autopkgtest from source (both ubuntu-devel and from debian) and update your master branch, you will also start to see this in your log files. *Ubuntu QA* (Brian Murray, Paride Legovini & Tim Andersson) *The upstream MP can be seen here:* https://salsa.debian.org/ci-team/autopkgtest/-/merge_requests/229 *The change fixes this debian bug from a little while ago:* https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977037 -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
