[08:27] I'm no longer able to access my PPAs' autopkgtest results, https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-nteodosio-ubuntu-pro/?format=plain. [08:27] Gives simply "AccessDenied". [08:27] Could that be related to the infrastructure migration? [09:40] andersson123: morning - how's the firewall taming proceeding? any luck? [10:11] bluca: on it. I made a firewall change before and it turns out what we needed was supposedly a proxy config change [10:11] waiting on an MP for that change to go through, I'll ping you when you can try trigger a test [10:11] cool, thank you [12:52] bluca: when you have a moment, feel free to trigger a test and report back to me if it works. [13:58] andersson123: I see triggers are working again on PRs now, thanks! [13:59] Awesome, sorry it took so long! [14:00] no worries at all [14:00] manual triggers via the script are also working, excellent [14:10] Issue with autopgktest results went away. Thanks, whoever worked on that. [15:10] o7 [15:11] if you have an issue with logs (weird download encoding, "NoSuchKey" or a 404), know these issues are slowly being fixed in long running scripts in some tmux sessions. If you have an issue and you need your logs asap, ping me and I'll amend for you [15:12] just know *eventually* they'll all be back to normal :) [15:41] andersson123: mmh it seems job results are not being reported back? [15:41] for example this PR shows all 4 jobs as pending: https://github.com/systemd/systemd/pull/30033 [15:41] but 3 of them have completed and disappeared from https://autopkgtest.ubuntu.com/running#pkg-systemd-upstream [15:42] (if you search for 30033 in the status page) [15:48] bluca: what are the specific jobs? I'll take a look [15:50] I don't know how to check that, as they have disappeared from the status page [15:50] PR number 30033 is the example [15:55] hm, I'm not massively familiar with github UI. Do you have a link to the logs of the CI that requests and monitors autopkgtest? [15:55] there isn't any [15:55] autopkgtest calls back into github [15:55] when the job is finished, and reports the status [15:56] and it just hangs or w/e with no response on the status? [15:56] gotcha [15:57] yes there's no answer [15:57] so for example, for PR 30033 the autopkgtest trigger got: GITHUB_STATUSES_URL=https://api.github.com/repos/systemd/systemd/statuses/6565b9d0b1bc6074a3b66abd14679fa7bd601fc3 [15:57] as a parameter when started [15:58] and autopkgtest infra would use that URL to report back the status [17:12] maybe you just (or will have) an update upstream soon bluca [17:14] thank you, I'll keep an eye on things