[06:57] <flag> LocutusOfBorg: hi, did you have any chance to look at virtualbox-dkms and jammy/hwe-6.8?
[08:12] <LocutusOfBorg> flag, asked again on vbox-dev yesterday
[08:12] <LocutusOfBorg> I can patch it but I prefer the fix to come from upstream
[08:12] <LocutusOfBorg> and also, they are half on VAC, so there might be some delay
[09:33] <flag> LocutusOfBorg: i see
[09:33] <flag> LocutusOfBorg: while here, the sync of bpftrace from debian has some regressions
[09:34] <flag> LocutusOfBorg: it's stuck in proposed ATM, and these are the failing tests:
[09:34] <LocutusOfBorg> I know flag help is appreciated
[09:34] <flag> [  FAILED  ] 3 tests, listed below:
[09:34] <flag> [  FAILED  ] basic.defines work
[09:34] <flag> [  FAILED  ] probe.kprobe_offset_fail_size
[09:34] <flag> [  FAILED  ] usdt.usdt quoted probe name
[09:34] <LocutusOfBorg> how did you find which test failed?
[09:34] <flag> LocutusOfBorg: i manually built bpftrace, and run runtime-tests.sh manually
[09:35] <LocutusOfBorg> why autopkgtest can't show them?
[09:35] <flag> LocutusOfBorg: that's a great question...
[09:35] <LocutusOfBorg> :)
[09:35] <LocutusOfBorg> that was the reason for the delay
[09:35] <flag> LocutusOfBorg: do you want a patch to disable the failing tests?
[09:35] <LocutusOfBorg> and it's on top of my priorities since I want llvm-toolchain-18 migration happen
[09:36] <LocutusOfBorg> flag, I would have also appreciated the disable of the already inside patch to disable failing tests
[09:36] <LocutusOfBorg> I have the feeling some of them are fixed upstream
[09:36] <LocutusOfBorg> and also is the CI=true variable helping?
[09:36] <flag> LocutusOfBorg: yeah, lumping all disabled test in a single patch is a good thing
[09:37] <flag> LocutusOfBorg: not sure about the CI=true thing
[10:05] <LocutusOfBorg> if you can do a double check it would be nice
[10:05] <LocutusOfBorg> because some tests are known to be failing under CI, so exporting looks a smart thing to do
[10:09] <rbasak> enr0n, juliank: any news on bug 2061128 please?
[10:09] -ubottu:#ubuntu-devel- Bug 2061128 in software-properties (Ubuntu) "`add-apt-repository --pocket` doesn't work on Noble (Deb822?)" [Medium, Confirmed] https://launchpad.net/bugs/2061128
[10:10] <rbasak> This makes it much more difficult to guide users into verifying SRUs on Noble, of which are many :-(
[10:12] <flag> LocutusOfBorg: i'm not sure how to test the impact of CI=true, besides
[10:12] <flag> LocutusOfBorg: https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest-oracular/oracular/amd64/b/bpftrace/20240711_071533_0ba1f@/log.gz
[10:12] <flag> LocutusOfBorg: 853s autopkgtest [07:08:27]: test command1: make -C $(find -name obj-*-linux-gnu)/ test
[10:13] <flag> LocutusOfBorg: was that skipped?
[10:16] <rbasak> For all those waiting on the SRU team for something: I could REALLY use some help with testing and sorting out the autopkgtests for bug 2072811. Most of the work here doesn't require the SRU team. I am doing it because nobody else is stepping up. This is consuming all of my available SRU review time.
[10:16] -ubottu:#ubuntu-devel- Bug 2072811 in apparmor (Ubuntu Oracular) "Apparmor: New update broke flatpak with `apparmor='DENIED'`" [High, Triaged] https://launchpad.net/bugs/2072811
[12:02] <rbasak> georgiag: ^ I'm getting test failures running the qa-regression-script, but I'm unfamiliar with it. Please could you take a look?
[12:04] <rbasak> georgiag: here's my attempted run: https://pastebin.ubuntu.com/p/HmMdY2b7Rt/
[12:07] <georgiag> rbasak: looking
[12:13] <slyon> @pilot in
=== ChanServ changed the topic of #ubuntu-devel to: Archive: open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Focal-Noble | Patch Pilots: juliank, slyon
[12:14] <slyon> juliank: are you still piloting?
[12:25] <rbasak> didrocks: FYI the adsys tests see flaky on arm64: https://autopkgtest.ubuntu.com/packages/a/adsys/noble/arm64
[12:25] <rbasak> seem
[12:29] <rbasak> georgiag: rerunning after installing pyflakes it eventually failed again with another missing dependency. Do you have a complete list of test dependencies somewhere? I used the ones listed in the comment in the test script and that seems deficient. How were you running this before?
[12:30] <georgiag> rbasak: I might have forgotten to add them to QRT, my bad. I'm double checking
[12:37] <juliank>  @pilot out
[12:37] <juliank> @pilot out
=== ChanServ changed the topic of #ubuntu-devel to: Archive: open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Focal-Noble | Patch Pilots: slyon
[12:37] <juliank> slyon: I have not been piloting since Thursday, not that anything happened that day or since then lol
[12:37] <juliank> slyon: Thanks
[12:38] <slyon> hehe, yw
[12:51] <enr0n> rbasak: it is in my backlog but is not a high priority. I will keep it mind for planning upcoming pulses
[12:52] <rbasak> enr0n: if deb822 was high enough priority then so should the regression it created :-(
[12:53] <enr0n> rbasak: thanks for your input. As I said, I will keep it in mind
=== d1b is now known as Guest5229
=== d1b_ is now known as d1b
[13:18] <perkelix> howdy!  is there any way to make pinentry beep when it's called to sign packages at the end of the build?
=== matttbe4 is now known as matttbe
[13:45] <ravikant_> Hi, any idea if udd is up to date? https://udd.debian.org/cgi-bin/ubuntu-sponsorships.cgi?render=html&sponsor=&sponsor_search=name&sponsoree=*ravi%20kant*&sponsoree_search=name
[13:45] <ravikant_> for example - this upload is missing https://launchpad.net/ubuntu/+source/linssid/3.6-8ubuntu1
[13:51] <rbasak> ravikant_: the last upload lists in the ubuntu_upload_history table in UDD is from 11 June, so yes, it seems that it has stopped updating.
[13:51] <rbasak> ravikant_: it's an entirely Debian service. https://wiki.debian.org/Services/UDD has some details. I guess we (you?) need to contact them.
[13:52] <rbasak> We use it on the DMB quite a lot. I'm not sure how I would consider an application without it :-(
[13:52] <ravikant_> rbasak: thanks for the confirmation. I'll contact them.
[13:54] <rbasak> Ah: https://udd.debian.org/udd-status.cgi
[13:54] <rbasak> psycopg2.errors.UniqueViolation: duplicate key value violates unique constraint "ubuntu_upload_history_pkey"
[13:54] <rbasak> DETAIL:  Key (source, version)=(edubuntu-meta, 24.10.01) already exists.
[13:57] <rbasak> georgiag: https://paste.ubuntu.com/p/3rPRVyqr5v/ is my lastest attempt. Looks like it doesn't like my virt environment. I think another task for you then please is to document exactly how to reproduce an environment in which this works, for the future apparmor SRU re-attempt.
[13:58] <rbasak> georgiag: FTR, the dependencies I had to add were pyflakes3, python3-notify2, python3-psutil
[13:58] <georgiag> rbasak: that's weird. did you run the install-packages script that comes with QRT? sudo ./install-packages test-apparmor.py
[14:00] <rbasak> georgiag: I did not. The SRU bug linked directly to https://git.launchpad.net/qa-regression-testing/tree/scripts/test-apparmor.py, which has instructions in the comments, and those are the instructions I followed, which do not mention your install-packages script.
[14:00] <georgiag> that doesn't explain the failures with posix_ipc userns which is what I'm currently investigating
[14:01] <georgiag> rbasak: I'm so sorry I didn't include that :(. I'm just so used to it that it slipped my mind. I'll make sure to include it next time
[14:01] <georgiag> the install-packages script reads all those QRT-Packages and Alternates and installs it for you
[14:03] <rbasak> I also thought that I could just run the script, so that's what I did. It didn't work because it depended on things from the repository, so that's when I realised I was expected to check out the whole repository.
[14:04] <rbasak> I appreciate it's difficult to test your own steps, hence my feedback above. This is a perfect example of why the test plan must be clear and unambiguous, and when following the test plan yourself, you should try to follow exactly what is written and not what is in your head :-/
[14:10] <georgiag> rbasak: thanks, I appreciate your feedback. I will definitely improve it
[14:31] <didrocks> rbasak: it seems that one of them is, I’ll have a look
[14:32] <rbasak> Thanks!
=== didrocks999 is now known as didrocks
[15:00] <lvoytek> @pilot in
=== ChanServ changed the topic of #ubuntu-devel to: Archive: open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Focal-Noble | Patch Pilots: lvoytek, slyon
=== pushkarnk1 is now known as pushkarnk
[16:16] <rbasak> When are upgrades from Jammy to Noble expected to be enabled? Is that typically done after the .1 release?
[16:17] <JanC> somewhere after the .1 release, yes
=== root is now known as Guest5299
[18:44] <sudip> thanks for sponsoring lvoytek, but just a confusion. usb-modeswitch does not have an autopkgtest, which is why I did not ask anyone here to trigger it for me
[18:45] <lvoytek> sudip: Ah yeah that's correct, guess the test was trivial then, still everything looked good to me :)
[18:47] <sudip> thanks for that lvoytek.. I started thinking there is some secret and hidden autopkgtest for main packages :)
=== pushkarnk1 is now known as pushkarnk
[18:58] <lvoytek> @pilot out
=== ChanServ changed the topic of #ubuntu-devel to: Archive: open | Devel of Ubuntu (not support) | Build failures: http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of Focal-Noble | Patch Pilots: slyon
=== ejat is now known as fenris
=== pushkarnk1 is now known as pushkarnk
=== matttbe2 is now known as matttbe