/srv/irclogs.ubuntu.com/2021/09/15/#ubuntu-devel.txt

=== genii is now known as genii-core
didrocksslyon: hey, about the adsys MIR, 0.7 contains vendor/gopkg.in/yaml.v{2,3}/NOTICE. I was wondering how you got the lintian warning about them missing?07:40
didrocksslyon: ack, I got it in pendantic mode only, I can maybe patch debian/rules to include it. I’m looking for the PIE warning now07:49
slyonack07:53
didrocksslyon: I can’t see the PIE warning on impish and latest lintian, even with pedantic mode, how did you get it?08:04
slyondidrocks: I get it by running "adsys-0.7$ lintian ../adsys_0.7_amd64.changes" after having it built via "sbuild -dimpish ."08:08
didrocksslyon: ack, problably an upstream 1.17 vs distro 1.16 thingy as I didn’t have this warning. However, running with -buildmode=pie explicitely in GOFLAGS works and enables PIE \o/ Thanks for spotting it!08:41
didrockssarnold: FYI ^08:41
didrocksslyon: and integration tests fixed (just removing sudo which was a leftover of zsys), I’ll update 0.7.1 soon, but still, feel free to post your review once ready and I’ll answer :)08:56
slyonvery good! Thank you08:59
slyondidrocks: I sent my review to https://pad.lv/1936907 I'd like to assign ~ubuntu-security so we can move on with that review as well, but somehow I'm not allowed to change the assignee (probably because I'm not yet part of ~ubuntu-mir). Could you assign ~ubuntu-security for me?09:24
ubottuLaunchpad bug 1936907 in adsys (Ubuntu) "[MIR] ADSys" [Undecided, New]09:24
didrocksslyon: sure, doing09:26
blucaddstreet, laney,slyon: we have a problem with the github/autopkgtest integration for the systemd upstream CI and cpaelzer suggested pinging here12:17
blucait seems jobs are running fine, but since yesterday there are no reports back on the PRs on github12:17
blucaeg, top job on https://autopkgtest.ubuntu.com/running#pkg-systemd-upstream is https://github.com/systemd/systemd/pull/20744 but there's no status report12:17
ubottuPull 20744 in systemd/systemd "udev: use netlink more aggressively" [Open]12:17
ddstreetbluca hmm...laney was running autopkgtest infrastructure before, but he's left canonical...not sure who took that over12:18
slyonjuliank: could you help with that ^ ?12:18
blucathe github interface settings shows webhooks are working without errors12:18
blucaany idea?12:18
blucathere's an ERROR 500 every now and then12:19
juliankbluca: we'll have to talk to xnox, I think error reports go to him, as it's his token12:19
blucabut most http posts work12:19
blucathank you12:19
laneycheck logs on the web units12:19
laneyif it's failing to post the result back to github it should say something there12:19
bluca10% of webhooks call fail with error 50012:20
blucathe rest suceeds12:20
blucathere's nothing else other than error 500 in the github webhook interface12:20
juliankI see multiple 401 Unauthorized per second12:21
laneyafter the test is running the webhook is not the problem any more12:21
laneyit's only used to dispatch it12:21
laneythen it's up to autopkgtest-cloud to submit the result back to github to be recorded on the PR12:21
laneycould be a problem with the token being used, or something else, logs should give a clue12:21
laney(401 sounds like a token issue)12:21
blucais that the same token as the webhook? or a diff one?12:22
julianklaney: I'm digging, it's complaining about http://10.24.0.23:8080/v1/AUTH_... urls12:22
laneyswifT?12:22
juliankSeems like swift storage is messed up?12:22
laneylike downloading the results on the web side to decide what to post back is failing?12:23
laneycheck if they uploaded ok on the cloud worker ...12:23
laneylike see what the job said when it finished, confirm with swift list12:23
juliankIt started 10 minutes after I ran mojo run12:25
juliank:D12:25
laneyD:12:26
juliankcloud worker seems happy12:28
laneytry curling the url it's complaining about?12:32
juliankI don't care right now, I see that github-status-credentials.txt has reverted to the old one12:32
laneyso it's not complaining about swift urls then12:34
laneyand the creds weren't updated on wendigo properly, so mojo run reset them12:34
juliankI updated them in ~proposed-migration12:35
juliank~prod-proposed-migration12:35
juliankseems they need to be updated in /srv/mojo/mojo-prod-proposed-migration/focal/ROOTFS/srv/mojo/mojo-prod-proposed-migration/focal/production/local/github-status-credentials.txt12:35
juliankaka /srv/mojo/LOCAL/mojo-prod-proposed-migration12:35
juliankduplicate files are confusin :D12:36
juliankbluca: should be working again now/future PRs12:37
blucafab, thank you!12:37
blucaany chance the reports can be retriggered for existing PRs?12:37
blucaotherwise they are kinda flying blind12:37
blucait's ok if it's not possible, I can then ask to force push12:39
julianknot easily, let's see what happens to the ones running right now, I don't know what is normal12:39
laneyit should sort itself out12:39
laney(for the ones that got triggered)12:40
julianklaney: So hooray because despite logging the swift urls, the 401s are gone now, so it logged the wrong url I guess12:40
juliankbluca: Yeah, so I see feedback on 2074412:40
juliankbluca: focal-s390x — autopkgtest finished (success)12:40
laneyjuliank: I guess it means: I tried to report this result but I got a 401 from github12:41
juliankprobably :D12:41
blucafab, thank you for the quick fix12:41
laneystill need a centralised logging place :-)12:41
laneythis incident should have caused alerts12:41
=== JanC_ is now known as JanC
=== genii-core is now known as genii
keithcquestion regarding bug#194203116:12
bdmurrayand what's the question?16:15
keithc gnome-shell crash on impish-indri daily with unreportable reason invalid core dump:"/tmp/apport_core_whctskr4" is not a core dump: file format not recognized is this the same bug#1942031?16:15
bdmurraykeithc: Do you have anything in /var/log/apport.log ?16:18
keithcyes16:20
keithc5 errors16:24
keithcdo you need me to list the errors?16:27
bdmurraycould you pastebin the log somewhere? Are you using a live session?16:29
keithcyes16:30
keithcapport.log is at https://pastebin.com/g0pkCyL116:43
keithcanother potential bug question bdmurray16:46
bdmurraythat looks the same based off the executable path16:46
keithcok thanks16:46
keithcI looked in the Defects summary but did see a bug for the cheese application. The  problem I encountered on my laptop was cheese did not show an image when first opened but would display an inage after being reopened the second or third try.16:50
bdmurraykeithc: you could report a bug about cheese using 'ubuntu-bug cheese'16:53
keithcThanks again16:54
keithcbdmurray: I reported the bug about cheese it is bug#194375218:40
krytarikOnce deployed, the pattern used above will also be suitable for bug snarfing btw.18:49
dbungertMay I get a retest click?  The test failure is a known issue on casper and is unrelated to squashfs-tools LP: #1938325 https://autopkgtest.ubuntu.com/request.cgi?release=impish&arch=amd64&package=casper&trigger=squashfs-tools/1%3A4.4-2ubuntu221:16
ubottuLaunchpad bug 1938325 in casper (Ubuntu) "adt failure: '/cdrom not ext4 with todisk'" [Undecided, New] https://launchpad.net/bugs/193832521:16
bdmurrayclicked21:24
=== genii is now known as genii-core

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!