Re: [Canonical-ubuntu-qa] [Merge] ~hyask/auto-upgrade-testing-specifications:skia/ubuntustudio into auto-upgrade-testing-specifications:main
Thanks Brian for bringing up the discussion here, it will be easier to refer to it in the future than on a Matrix room. I've pushed an update with what was said, focal->jammy seems to be working on my machine, but I'd like to avoid testing all of them on my poor laptop, so I'll go ahead and merge this to check on Jenkins how it goes (we don't seem to have the ability to deploy these jobs on a custom branch like some other stuff) -- https://code.launchpad.net/~hyask/auto-upgrade-testing-specifications/+git/auto-upgrade-testing-specifications/+merge/460594 Your team Canonical Platform QA Team is requested to review the proposed merge of ~hyask/auto-upgrade-testing-specifications:skia/ubuntustudio into auto-upgrade-testing-specifications:main. -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Merge] ~hyask/auto-upgrade-testing-specifications:skia/ubuntustudio into auto-upgrade-testing-specifications:main
The proposal to merge ~hyask/auto-upgrade-testing-specifications:skia/ubuntustudio into auto-upgrade-testing-specifications:main has been updated. Status: Needs review => Merged For more details, see: https://code.launchpad.net/~hyask/auto-upgrade-testing-specifications/+git/auto-upgrade-testing-specifications/+merge/460594 -- Your team Canonical Platform QA Team is requested to review the proposed merge of ~hyask/auto-upgrade-testing-specifications:skia/ubuntustudio into auto-upgrade-testing-specifications:main. -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Merge] ~andersson123/autopkgtest-cloud:fix-install-section-web-systemd-units into autopkgtest-cloud:master
Tim Andersson has proposed merging ~andersson123/autopkgtest-cloud:fix-install-section-web-systemd-units into autopkgtest-cloud:master. Requested reviews: Canonical's Ubuntu QA (canonical-ubuntu-qa) For more details, see: https://code.launchpad.net/~andersson123/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/460675 -- Your team Canonical's Ubuntu QA is requested to review the proposed merge of ~andersson123/autopkgtest-cloud:fix-install-section-web-systemd-units into autopkgtest-cloud:master. diff --git a/charms/focal/autopkgtest-web/units/cache-amqp.service b/charms/focal/autopkgtest-web/units/cache-amqp.service index d7aa53d..4ba15f0 100644 --- a/charms/focal/autopkgtest-web/units/cache-amqp.service +++ b/charms/focal/autopkgtest-web/units/cache-amqp.service @@ -6,3 +6,6 @@ Type=oneshot User=ubuntu StateDirectory=cache-amqp ExecStart=/home/ubuntu/webcontrol/cache-amqp + +[Install] +WantedBy=autopkgtest-web.target diff --git a/charms/focal/autopkgtest-web/units/delete-old-github-requests.service b/charms/focal/autopkgtest-web/units/delete-old-github-requests.service index e4bec05..5ec856b 100644 --- a/charms/focal/autopkgtest-web/units/delete-old-github-requests.service +++ b/charms/focal/autopkgtest-web/units/delete-old-github-requests.service @@ -5,3 +5,6 @@ Description=Delete github requests older than 1 day Type=oneshot User=ubuntu ExecStart=/home/ubuntu/webcontrol/delete-old-github-requests + +[Install] +WantedBy=autopkgtest-web.target diff --git a/charms/focal/autopkgtest-web/units/indexed-packages.service b/charms/focal/autopkgtest-web/units/indexed-packages.service index e518740..3b1b904 100644 --- a/charms/focal/autopkgtest-web/units/indexed-packages.service +++ b/charms/focal/autopkgtest-web/units/indexed-packages.service @@ -4,3 +4,6 @@ Description=Get index of packages [Service] Type=oneshot ExecStart=/home/ubuntu/webcontrol/indexed-packages + +[Install] +WantedBy=autopkgtest-web.target diff --git a/charms/focal/autopkgtest-web/units/publish-db.service b/charms/focal/autopkgtest-web/units/publish-db.service index 1c9c282..873e439 100644 --- a/charms/focal/autopkgtest-web/units/publish-db.service +++ b/charms/focal/autopkgtest-web/units/publish-db.service @@ -5,3 +5,6 @@ Description=publish autopkgtest.db Type=oneshot ExecStart=/home/ubuntu/webcontrol/publish-db TimeoutSec=300 + +[Install] +WantedBy=autopkgtest-web.target diff --git a/charms/focal/autopkgtest-web/units/update-github-jobs.service b/charms/focal/autopkgtest-web/units/update-github-jobs.service index 687ea73..641d427 100644 --- a/charms/focal/autopkgtest-web/units/update-github-jobs.service +++ b/charms/focal/autopkgtest-web/units/update-github-jobs.service @@ -8,3 +8,6 @@ Group=www-data TimeoutStartSec=10m EnvironmentFile=/home/ubuntu/public-swift-creds ExecStart=/home/ubuntu/webcontrol/update-github-jobs + +[Install] +WantedBy=autopkgtest-web.target -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 2051939] Re: [SRU exception] backport 5.32 to Jammy and Mantic
No, I've not considered anything like this, since I've started to test this new version on the staging infrastructure, and it already fixes the `unknown restriction` issue. See this log for a run with this setup: https://autopkgtest.staging.ubuntu.com/results/autopkgtest-noble/noble/amd64/a/autopkgtest/20240208_171155_dd558@/log.gz To add some precision to what is needed on the "autopkgtest runners", this is a branch based on this SRU, with some additional patches required for the infrastructure: https://salsa.debian.org/ubuntu-ci-team/autopkgtest/-/tree/ubuntu/5.32+prod?ref_type=heads It's not deployed with a deb, but with a `git clone`, that allows a bit more flexibility for the infra. Still, we try to keep the diff as small as possible, but this hasn't been keeping up with upstream for a while, hence this big diff in SRU. We expect to roll this branch out in production in the not so distant future, when we'll have tested it a bit more on staging, and when the queues will be shorted, and I'll go back to investigate and fix those tests at that moment. We've already some Jira cards opened for that, so we clearly have that in our radar. -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to autopkgtest in Ubuntu. https://bugs.launchpad.net/bugs/2051939 Title: [SRU exception] backport 5.32 to Jammy and Mantic Status in autopkgtest package in Ubuntu: New Status in autopkgtest source package in Focal: Won't Fix Status in autopkgtest source package in Jammy: In Progress Status in autopkgtest source package in Mantic: In Progress Bug description: [Impact] This release contains both bug fixes and new features and we would like to make sure all of our developers have access to these improvements. It's a version bump from 5.28 to 5.32, so that's a big upstream upgrade with lots of improvements, but here are the most notable ones for developers: * Overall improved riscv64 support - QEMU fixes - Better timeouts by default * Add --cpus to buildvm-ubuntu-cloud tool: this improves speed when building images * Bump default QEMU ram size to 2048 (Debian #1059840), making a lot of tests work better by default See the changelog entry below for a full list of changes and bugs. [Test Plan] autopkgtest contains a test suite that is run using the SRU package for each release. This test suite's results are available here: Jammy (https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-hyask-autopkgtest-jammy/) Logs: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-hyask-autopkgtest-jammy/jammy/amd64/a/autopkgtest/20240206_130746_30768@/log.gz As expected, the tests failed, but they've been forever failing on this release (see https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/a/autopkgtest/20240202_151346_e0140@/log.gz for example). However, with the current ongoing effort to fix them, we see an improvement with the `schroot` test being now PASS, and only `unshare` being FAIL. Most of the rest is now marked as SKIPPED instead of uncontroled FAIL, which also helps in the road to a green status. Mantic (https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-hyask-autopkgtest-mantic/) Logs: https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-hyask-autopkgtest-mantic/mantic/amd64/a/autopkgtest/20240206_155746_00441@/log.gz Unexpectedly, the tests are green on this release, which is a big improvement compared to the previous version (https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/a/autopkgtest/20240202_225722_a9ed0@/log.gz). As for Jammy, not everything is PASS, but the failures are under enough control to be marked as SKIP when needed. Additionally, the following PPAs should be tested manually at least under normal development conditions to ensure users will only be impacted by corner-case issues, should they arise: https://launchpad.net/~hyask/+archive/ubuntu/autopkgtest-mantic/ https://launchpad.net/~hyask/+archive/ubuntu/autopkgtest-jammy/ Please take a particular attention to test the cross-arch feature, as there is no automated tests for this. Here is the documentation on this feature: https://wiki.ubuntu.com/ProposedMigration#How_to_run_cross-architecture_autopkgtest_locally_using_QEMU Be knowledgeable that the `mawk` is particularly well suited for these kind of tests. [Where problems could occur] Given the size of the changelog, there may be corner-cases that aren't covered by the automated testsuite. Also, with the differences in Python version, some library interfaces could have changed in untested code, leading to crashes. Given that this tool is mainly used by developers, users are likely to find workarounds or report bugs when they find them. [Changelog] autopkgtest (5.32ubuntu2) noble; urgency=medium * Fix traceback in cross-arch testing (LP: #2051593)
[Canonical-ubuntu-qa] [Merge] ~andersson123/autopkgtest-cloud:cloud-worker-tmp-cleanup into autopkgtest-cloud:master
Tim Andersson has proposed merging
~andersson123/autopkgtest-cloud:cloud-worker-tmp-cleanup into
autopkgtest-cloud:master.
Requested reviews:
Canonical's Ubuntu QA (canonical-ubuntu-qa)
For more details, see:
https://code.launchpad.net/~andersson123/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/460680
--
Your team Canonical's Ubuntu QA is requested to review the proposed merge of
~andersson123/autopkgtest-cloud:cloud-worker-tmp-cleanup into
autopkgtest-cloud:master.
diff --git a/charms/focal/autopkgtest-cloud-worker/config.yaml b/charms/focal/autopkgtest-cloud-worker/config.yaml
index 7f0ef60..bcb9996 100644
--- a/charms/focal/autopkgtest-cloud-worker/config.yaml
+++ b/charms/focal/autopkgtest-cloud-worker/config.yaml
@@ -110,3 +110,6 @@ options:
description: Submit all metrics with this as the "context" tag,
to differentiate staging vs. production submissions
type: string
+ worker-tmp-cleanup-config:
+default: ""
+description: config for periodic cleanup of /tmp directory
diff --git a/charms/focal/autopkgtest-cloud-worker/reactive/autopkgtest_cloud_worker.py b/charms/focal/autopkgtest-cloud-worker/reactive/autopkgtest_cloud_worker.py
index 2e8f376..ea41165 100644
--- a/charms/focal/autopkgtest-cloud-worker/reactive/autopkgtest_cloud_worker.py
+++ b/charms/focal/autopkgtest-cloud-worker/reactive/autopkgtest_cloud_worker.py
@@ -567,6 +567,16 @@ def fix_tmp_permissions():
@when_any(
+"config.set.worker-tmp-cleanup-config",
+"config.changed.worker-tmp-cleanup-config",
+)
+def write_worker_tmp_cleanup_config():
+cleanup_cfg_str = config().get("worker-tmp-cleanup-config")
+with open("/etc/tmpfiles.d/tmp.conf", "w") as f:
+f.write(cleanup_cfg_str)
+
+
+@when_any(
"config.changed.influxdb-hostname",
"config.changed.influxdb-port",
"config.changed.influxdb-username",
diff --git a/mojo/service-bundle b/mojo/service-bundle
index e6b6a1f..ab1c173 100644
--- a/mojo/service-bundle
+++ b/mojo/service-bundle
@@ -75,6 +75,7 @@ applications:
<<: *common-options
nova-rcs: include-base64://{{local_dir}}/novarcs.tar
worker-setup-command2: /CHECKOUTDIR//setup-commands/setup-testbed
+worker-tmp-cleanup-config: e /tmp 1777 root root 30d
{%- if stage_name == "production" %}
net-name: net_prod-proposed-migration
worker-default-flavor: autopkgtest
--
Mailing list: https://launchpad.net/~canonical-ubuntu-qa
Post to : canonical-ubuntu-qa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa
More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Merge] ~andersson123/autopkgtest-cloud:fix-install-section-web-systemd-units into autopkgtest-cloud:master
The proposal to merge ~andersson123/autopkgtest-cloud:fix-install-section-web-systemd-units into autopkgtest-cloud:master has been updated. Status: Needs review => Work in progress For more details, see: https://code.launchpad.net/~andersson123/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/460675 -- Your team Canonical's Ubuntu QA is requested to review the proposed merge of ~andersson123/autopkgtest-cloud:fix-install-section-web-systemd-units into autopkgtest-cloud:master. -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 2051046] Re: ubuntu_fan_smoke_test, ubuntu_lxc and ubuntu_lxc test failures on b/linux-gcp-5.4 on c3a-standard instance
Found on Jammy linux 5.15.0-97.107, security cycle s2024.01.08. -- You received this bug notification because you are a member of Canonical Platform QA Team, which is subscribed to ubuntu-kernel-tests. https://bugs.launchpad.net/bugs/2051046 Title: ubuntu_fan_smoke_test, ubuntu_lxc and ubuntu_lxc test failures on b/linux-gcp-5.4 on c3a-standard instance Status in ubuntu-kernel-tests: New Bug description: Bionic linux-gcp-5.4 fails on new c3a-standard instance due to connection issues, see below. Running './ubuntu_fan_smoke_test.sh 172.17.0.0/16' [stdout] Testing Fan Networking (pre-0.13.0 API) [stdout] docker pull --platform linux/arm64 ubuntu: PASSED [stderr] Illegal instruction (core dumped) [stdout] enable disable fan test: PASSED [stderr] Illegal instruction (core dumped) [stdout] fanctl show test: PASSED [stderr] Illegal instruction (core dumped) [stdout] fanctl check bridge config test: PASSED [stderr] W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/jammy/InRelease Connection failed [IP: 185.125.190.39 80] [stderr] W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/jammy-updates/InRelease Connection failed [IP: 185.125.190.39 80] [stderr] W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/jammy-backports/InRelease Connection failed [IP: 185.125.190.39 80] [stderr] W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/jammy-security/InRelease Connection failed [IP: 185.125.190.36 80] [stderr] W: Some index files failed to download. They have been ignored, or old ones used instead. [stderr] E: Unable to locate package iputils-ping [stdout] fanatic docker test(--dns=169.254.169.254): FAILED: (docker run returned 100) [stderr] Illegal instruction (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2051046/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 2051352] Re: posix_ipc test from test_regression_testsuite of ubuntu_qrt_apparmor failed with F-aws-5.15 T3A (could not mq_notify: Connection timed out)
Found on Jammy linux 5.15.0-97.107, security cycle s2024.01.08. -- You received this bug notification because you are a member of Canonical Platform QA Team, which is subscribed to ubuntu-kernel-tests. https://bugs.launchpad.net/bugs/2051352 Title: posix_ipc test from test_regression_testsuite of ubuntu_qrt_apparmor failed with F-aws-5.15 T3A (could not mq_notify: Connection timed out) Status in QA Regression Testing: New Status in ubuntu-kernel-tests: New Bug description: Issue found on AWS AMD 64 instance t3a.2xlarge with: * F-aws-5.15.0-1053.58~20.04.1 * J-aws-5.15.0-1053.58 This is reproducible, 4 out of 4 attempts on F-aws-5.15.0-1053.58~20.04.1 There is no such issue on t3a.2xlarge with F-aws-5.15.0-1052.57~20.04.1 nor J-aws-5.15.0-1052.57. Therefore it appears to be a possible regression. The posix_ipc test in test_regression_testsuite will fail with: Error: posix_mq_rcv failed. Test 'POSIX MQUEUE (confined receiver root - unconfined sender : mq_notify)' was expected to 'pass'. Reason for failure 'FAIL - could not mq_notify: Connection timed out' Test log: ubuntu@t3a:~/testlibp8PXk0/source/focal/apparmor-2.13.3/tests/regression/apparmor$ sudo bash posix_ipc.sh Error: posix_mq_rcv failed. Test 'POSIX MQUEUE (confined root - mqueue : mq_notify)' was expected to 'pass'. Reason for failure 'FAIL - could not mq_notify: Connection timed out' xpass: POSIX MQUEUE (confined root - mqueue label 1) xpass: POSIX MQUEUE (confined root - mqueue label 1 : mq_notify) xpass: POSIX MQUEUE (confined root - mqueue label 1 : select) xpass: POSIX MQUEUE (confined root - mqueue label 1 : poll) xpass: POSIX MQUEUE (confined root - mqueue label 1 : epoll) xpass: POSIX MQUEUE (confined root - mqueue label 2) xpass: POSIX MQUEUE (confined root - mqueue label 2 : mq_notify) xpass: POSIX MQUEUE (confined root - mqueue label 2 : select) xpass: POSIX MQUEUE (confined root - mqueue label 2 : poll) xpass: POSIX MQUEUE (confined root - mqueue label 2 : epoll) Error: posix_mq_rcv failed. Test 'POSIX MQUEUE (confined 1001 - mqueue : mq_notify)' was expected to 'pass'. Reason for failure 'FAIL - could not mq_notify: Connection timed out' Error: posix_mq_rcv failed. Test 'POSIX MQUEUE (confined receiver 1001 - unconfined sender : mq_notify)' was expected to 'pass'. Reason for failure 'FAIL - could not mq_notify: Connection timed out' xpass: POSIX MQUEUE (confined 1001 - mqueue label 1) xpass: POSIX MQUEUE (confined 1001 - mqueue label 1 : mq_notify) xpass: POSIX MQUEUE (confined 1001 - mqueue label 1 : select) xpass: POSIX MQUEUE (confined 1001 - mqueue label 1 : poll) xpass: POSIX MQUEUE (confined 1001 - mqueue label 1 : epoll) xpass: POSIX MQUEUE (confined 1001 - mqueue label 2) xpass: POSIX MQUEUE (confined 1001 - mqueue label 2 : mq_notify) xpass: POSIX MQUEUE (confined 1001 - mqueue label 2 : select) xpass: POSIX MQUEUE (confined 1001 - mqueue label 2 : poll) xpass: POSIX MQUEUE (confined 1001 - mqueue label 2 : epoll) To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/2051352/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 2051046] Re: ubuntu_fan_smoke_test, ubuntu_lxc and ubuntu_lxc test failures on b/linux-gcp-5.4 on c3a-standard instance
Found on Mantic linux 6.5.0-21.21, security cycle s2024.01.08. -- You received this bug notification because you are a member of Canonical Platform QA Team, which is subscribed to ubuntu-kernel-tests. https://bugs.launchpad.net/bugs/2051046 Title: ubuntu_fan_smoke_test, ubuntu_lxc and ubuntu_lxc test failures on b/linux-gcp-5.4 on c3a-standard instance Status in ubuntu-kernel-tests: New Bug description: Bionic linux-gcp-5.4 fails on new c3a-standard instance due to connection issues, see below. Running './ubuntu_fan_smoke_test.sh 172.17.0.0/16' [stdout] Testing Fan Networking (pre-0.13.0 API) [stdout] docker pull --platform linux/arm64 ubuntu: PASSED [stderr] Illegal instruction (core dumped) [stdout] enable disable fan test: PASSED [stderr] Illegal instruction (core dumped) [stdout] fanctl show test: PASSED [stderr] Illegal instruction (core dumped) [stdout] fanctl check bridge config test: PASSED [stderr] W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/jammy/InRelease Connection failed [IP: 185.125.190.39 80] [stderr] W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/jammy-updates/InRelease Connection failed [IP: 185.125.190.39 80] [stderr] W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/jammy-backports/InRelease Connection failed [IP: 185.125.190.39 80] [stderr] W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/jammy-security/InRelease Connection failed [IP: 185.125.190.36 80] [stderr] W: Some index files failed to download. They have been ignored, or old ones used instead. [stderr] E: Unable to locate package iputils-ping [stdout] fanatic docker test(--dns=169.254.169.254): FAILED: (docker run returned 100) [stderr] Illegal instruction (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2051046/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 2051352] Re: posix_ipc test from test_regression_testsuite of ubuntu_qrt_apparmor failed with F-aws-5.15 T3A (could not mq_notify: Connection timed out)
Found on Mantic linux 6.5.0-21.21, security cycle s2024.01.08 (AWS + Azure Standard_A2_v2 instance). -- You received this bug notification because you are a member of Canonical Platform QA Team, which is subscribed to ubuntu-kernel-tests. https://bugs.launchpad.net/bugs/2051352 Title: posix_ipc test from test_regression_testsuite of ubuntu_qrt_apparmor failed with F-aws-5.15 T3A (could not mq_notify: Connection timed out) Status in QA Regression Testing: New Status in ubuntu-kernel-tests: New Bug description: Issue found on AWS AMD 64 instance t3a.2xlarge with: * F-aws-5.15.0-1053.58~20.04.1 * J-aws-5.15.0-1053.58 This is reproducible, 4 out of 4 attempts on F-aws-5.15.0-1053.58~20.04.1 There is no such issue on t3a.2xlarge with F-aws-5.15.0-1052.57~20.04.1 nor J-aws-5.15.0-1052.57. Therefore it appears to be a possible regression. The posix_ipc test in test_regression_testsuite will fail with: Error: posix_mq_rcv failed. Test 'POSIX MQUEUE (confined receiver root - unconfined sender : mq_notify)' was expected to 'pass'. Reason for failure 'FAIL - could not mq_notify: Connection timed out' Test log: ubuntu@t3a:~/testlibp8PXk0/source/focal/apparmor-2.13.3/tests/regression/apparmor$ sudo bash posix_ipc.sh Error: posix_mq_rcv failed. Test 'POSIX MQUEUE (confined root - mqueue : mq_notify)' was expected to 'pass'. Reason for failure 'FAIL - could not mq_notify: Connection timed out' xpass: POSIX MQUEUE (confined root - mqueue label 1) xpass: POSIX MQUEUE (confined root - mqueue label 1 : mq_notify) xpass: POSIX MQUEUE (confined root - mqueue label 1 : select) xpass: POSIX MQUEUE (confined root - mqueue label 1 : poll) xpass: POSIX MQUEUE (confined root - mqueue label 1 : epoll) xpass: POSIX MQUEUE (confined root - mqueue label 2) xpass: POSIX MQUEUE (confined root - mqueue label 2 : mq_notify) xpass: POSIX MQUEUE (confined root - mqueue label 2 : select) xpass: POSIX MQUEUE (confined root - mqueue label 2 : poll) xpass: POSIX MQUEUE (confined root - mqueue label 2 : epoll) Error: posix_mq_rcv failed. Test 'POSIX MQUEUE (confined 1001 - mqueue : mq_notify)' was expected to 'pass'. Reason for failure 'FAIL - could not mq_notify: Connection timed out' Error: posix_mq_rcv failed. Test 'POSIX MQUEUE (confined receiver 1001 - unconfined sender : mq_notify)' was expected to 'pass'. Reason for failure 'FAIL - could not mq_notify: Connection timed out' xpass: POSIX MQUEUE (confined 1001 - mqueue label 1) xpass: POSIX MQUEUE (confined 1001 - mqueue label 1 : mq_notify) xpass: POSIX MQUEUE (confined 1001 - mqueue label 1 : select) xpass: POSIX MQUEUE (confined 1001 - mqueue label 1 : poll) xpass: POSIX MQUEUE (confined 1001 - mqueue label 1 : epoll) xpass: POSIX MQUEUE (confined 1001 - mqueue label 2) xpass: POSIX MQUEUE (confined 1001 - mqueue label 2 : mq_notify) xpass: POSIX MQUEUE (confined 1001 - mqueue label 2 : select) xpass: POSIX MQUEUE (confined 1001 - mqueue label 2 : poll) xpass: POSIX MQUEUE (confined 1001 - mqueue label 2 : epoll) To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/2051352/+subscriptions -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 2051939] Re: [SRU exception] backport 5.32 to Jammy and Mantic
The autopkgtests for autopkgtest are known to fail and have been failing for some time, fixing them is the team's long term plan, but their failure right now will not block the package from migrating from -proposed. -- You received this bug notification because you are a member of Canonical's Ubuntu QA, which is subscribed to autopkgtest in Ubuntu. https://bugs.launchpad.net/bugs/2051939 Title: [SRU exception] backport 5.32 to Jammy and Mantic Status in autopkgtest package in Ubuntu: New Status in autopkgtest source package in Focal: Won't Fix Status in autopkgtest source package in Jammy: In Progress Status in autopkgtest source package in Mantic: In Progress Bug description: [Impact] This release contains both bug fixes and new features and we would like to make sure all of our developers have access to these improvements. It's a version bump from 5.28 to 5.32, so that's a big upstream upgrade with lots of improvements, but here are the most notable ones for developers: * Overall improved riscv64 support - QEMU fixes - Better timeouts by default * Add --cpus to buildvm-ubuntu-cloud tool: this improves speed when building images * Bump default QEMU ram size to 2048 (Debian #1059840), making a lot of tests work better by default See the changelog entry below for a full list of changes and bugs. [Test Plan] autopkgtest contains a test suite that is run using the SRU package for each release. This test suite's results are available here: Jammy (https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-hyask-autopkgtest-jammy/) Logs: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-hyask-autopkgtest-jammy/jammy/amd64/a/autopkgtest/20240206_130746_30768@/log.gz As expected, the tests failed, but they've been forever failing on this release (see https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/a/autopkgtest/20240202_151346_e0140@/log.gz for example). However, with the current ongoing effort to fix them, we see an improvement with the `schroot` test being now PASS, and only `unshare` being FAIL. Most of the rest is now marked as SKIPPED instead of uncontroled FAIL, which also helps in the road to a green status. Mantic (https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-hyask-autopkgtest-mantic/) Logs: https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-hyask-autopkgtest-mantic/mantic/amd64/a/autopkgtest/20240206_155746_00441@/log.gz Unexpectedly, the tests are green on this release, which is a big improvement compared to the previous version (https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/a/autopkgtest/20240202_225722_a9ed0@/log.gz). As for Jammy, not everything is PASS, but the failures are under enough control to be marked as SKIP when needed. Additionally, the following PPAs should be tested manually at least under normal development conditions to ensure users will only be impacted by corner-case issues, should they arise: https://launchpad.net/~hyask/+archive/ubuntu/autopkgtest-mantic/ https://launchpad.net/~hyask/+archive/ubuntu/autopkgtest-jammy/ Please take a particular attention to test the cross-arch feature, as there is no automated tests for this. Here is the documentation on this feature: https://wiki.ubuntu.com/ProposedMigration#How_to_run_cross-architecture_autopkgtest_locally_using_QEMU Be knowledgeable that the `mawk` is particularly well suited for these kind of tests. [Where problems could occur] Given the size of the changelog, there may be corner-cases that aren't covered by the automated testsuite. Also, with the differences in Python version, some library interfaces could have changed in untested code, leading to crashes. Given that this tool is mainly used by developers, users are likely to find workarounds or report bugs when they find them. [Changelog] autopkgtest (5.32ubuntu2) noble; urgency=medium * Fix traceback in cross-arch testing (LP: #2051593) * Update cross-arch patchset from latest snapshot -- Paride Legovini Mon, 29 Jan 2024 22:46:58 +0100 autopkgtest (5.32ubuntu1) noble; urgency=medium * Merge with Debian unstable (LP: #2049737) Remaining changes: - Add support for cross-architecture testing. -- Paride Legovini Tue, 23 Jan 2024 12:00:37 +0100 autopkgtest (5.32) unstable; urgency=medium [ Florent 'Skia' Jacquet ] * d/t/schroot: better use of existing variables * d/t/schroot: allow running behind a proxy [ Simon McVittie ] * testarchive: Fix a pycodestyle warning * Standards-Version: 4.6.2 (no changes required) * qemu: Use 4M OVMF images if available [ Stefano Rivera ] * Testbed: Kill with SIGKILL if SIGTERM doesn't do the job in 10 seconds (Closes: #1059444) [ Paul Gevers ] * tests: increase sleep in test_timeout() for lxd test (Closes: #1020634) * autopkgtest-virt-qemu: rais
[Canonical-ubuntu-qa] [Merge] ~andersson123/autopkgtest-cloud:dont-check-huge-tests-for-duplicate-queued-items into autopkgtest-cloud:master
Tim Andersson has proposed merging ~andersson123/autopkgtest-cloud:dont-check-huge-tests-for-duplicate-queued-items into autopkgtest-cloud:master. Requested reviews: Canonical's Ubuntu QA (canonical-ubuntu-qa) For more details, see: https://code.launchpad.net/~andersson123/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/460711 -- Your team Canonical's Ubuntu QA is requested to review the proposed merge of ~andersson123/autopkgtest-cloud:dont-check-huge-tests-for-duplicate-queued-items into autopkgtest-cloud:master. diff --git a/charms/focal/autopkgtest-web/webcontrol/request/submit.py b/charms/focal/autopkgtest-web/webcontrol/request/submit.py index 72d493b..760f53e 100644 --- a/charms/focal/autopkgtest-web/webcontrol/request/submit.py +++ b/charms/focal/autopkgtest-web/webcontrol/request/submit.py @@ -642,6 +642,8 @@ class Submit: "triggers": sorted(req_triggers), } for test_type in data: +if test_type == "huge": +continue for release in data[test_type]: for arch in data[test_type][release]: packages = data[test_type][release][arch] -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
Re: [Canonical-ubuntu-qa] [Merge] ~andersson123/autopkgtest-cloud:sqlite-db-backup into autopkgtest-cloud:master
Review: Needs Fixing
Added a few comments -- my biggest issue is that the script is VACUUMing the
database, and locking it to do so. I'm generally of the opinion that VACUUM is
misunderstood and over-utilized, but here the ultimate purpose of this script
is to backup the database. In this case, VACUUM INTO would be *vastly*
preferable as it'd require no locks at all and would still result in a
minimally sized backup image (even though the original db would still be
oversized, but this is a non-issue).
Anyway, I've left some more extensive commentary in the diff.
Diff comments:
> diff --git a/charms/focal/autopkgtest-web/webcontrol/db-backup
> b/charms/focal/autopkgtest-web/webcontrol/db-backup
> new file mode 100755
> index 000..e636334
> --- /dev/null
> +++ b/charms/focal/autopkgtest-web/webcontrol/db-backup
> @@ -0,0 +1,262 @@
> +#!/usr/bin/python3
> +"""
> +This script periodically backs up the sqlite3 db to swift storage
> +and clears up old backups
> +"""
> +
> +import atexit
> +import configparser
> +import datetime
> +import gzip
> +import logging
> +import os
> +import shutil
> +import sqlite3
> +import sys
> +import time
> +
> +import swiftclient
> +from helpers.utils import init_db
> +
> +DB_PATH = ""
> +DB_COPY_LOCATION = ""
> +DB_NAME = ""
> +CONTAINER_NAME = "db-backups"
> +MAX_DAYS = 7
> +SQLITE_DUMP_CMD = 'sqlite3 /home/ubuntu/autopkgtest.db ".backup
> autopkgtest.db.bak"'
> +DB_BACKUP_NAME = ""
> +DB_BACKUP_PATH = ""
> +
> +
> +def db_connect() -> sqlite3.Connection:
> +"""
> +Establish connection to sqlite3 db
> +"""
> +global DB_PATH
> +global DB_NAME
> +global DB_BACKUP_NAME
> +global DB_BACKUP_PATH
> +cp = configparser.ConfigParser()
> +cp.read(os.path.expanduser("~ubuntu/autopkgtest-cloud.conf"))
> +DB_PATH = cp["web"]["database"]
> +DB_NAME = DB_PATH.split("/")[-1]
> +DB_BACKUP_NAME = "%s.bak" % DB_NAME
> +DB_BACKUP_PATH = "/tmp/%s" % DB_BACKUP_NAME
from pathlib import Path
#...
DB_PATH = Path(cp['web']['database'])
DB_BACKUP_PATH = Path('/tmp') / (DB_PATH.name + '.bak')
In all seriousness, pathlib is well worth a look; one of the best things to
happen to the stdlib in a lng time.
> +
> +db_con = init_db(cp["web"]["database"])
> +
> +return db_con
> +
> +
> +def is_db_locked(db_con: sqlite3.Connection) -> bool:
> +"""
> +Check if sqlite3 db is locked, if not, continue with rest of script
> +"""
> +c = db_con.cursor()
> +try:
> +c.execute("BEGIN IMMEDIATE")
> +except sqlite3.OperationalError as e:
> +if "database is locked" in str(e):
> +logging.info(
> +"Database is locked, full error: %s\nsleeping..." % str(e)
> +)
> +time.sleep(5)
This is a slightly weird call; I wouldn't expect a function called
"is_db_locked" to pause in its implementation, just to immediately return
False/True and for the caller to handle any wait-state required. In other
words, the while..pass down in the main body to have the sleep rather than this
call.
Actually, I'd much rather have a function that just handles acquiring a lock on
the database, returning when it had done so (or raising an exception if it
times out). But I wouldn't worry about fixing this, because I'm also going to
question the need for a lock at all here ...
> +return True
> +elif "database disk image is malformed" in str(e):
> +logging.info(
> +"Database is corrupted! Exiting! Full error: %s" % str(e)
> +)
> +sys.exit(1)
Yikes! No, don't go parsing exception messages which are subject to translation
and change to determine serious things like database corruption. Worse still,
database corruption doesn't appear as an OperationalError, it's a DatabaseError
(https://github.com/python/cpython/blob/fbb016973149d983d30351bdd1aaf00df285c776/Modules/_sqlite/util.c#L60).
Regardless, don't do this.
Unfortunately, Python's rather weak DB-API provides no good mechanism for
determining the precise error of a given engine (some interfaces return the
error as a value on the exception, but sqlite3 doesn't). However, I wouldn't
worry overly about this because (as mentioned) I don't think a lock is
necessary at all here.
> +else:
> +logging.info("Locking db failed: %s" % str(e))
> +time.sleep(5)
> +return True
> +c.execute("END")
> +return False
> +
> +
> +def backup_db(db_con: sqlite3.Connection):
> +global DB_BACKUP_PATH
> +db_backup_con = sqlite3.connect(DB_BACKUP_PATH)
> +with db_backup_con:
> +db_con.backup(db_backup_con, pages=1)
> +db_backup_con.close()
> +
> +
> +def db_checkpoint(db_con: sqlite3.Connection):
> +c = db_con.cursor()
> +try:
> +c.execute("checkpoint")
> +except sqlite3.OperationalError as e:
> +logging.info("checkpoint failed: %s" % str(e))
> +sys.exit(1)
> +
> +
[Canonical-ubuntu-qa] [Bug 1951227] Re: ubuntu_ltp_kernel_misc / tpci causes test interruption, hang or machine crash
Found on Bionic linux 4.15.0-222.233, security cycle s2024.01.08.
--
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/1951227
Title:
ubuntu_ltp_kernel_misc / tpci causes test interruption, hang or
machine crash
Status in ubuntu-kernel-tests:
New
Bug description:
Found on:
- 2021.11.08/impish/linux-oracle/5.13.0-1010.12 (instances: VM.DenseIO2.8,
VM.Standard.E3.Flex-4c.8m, VM.Standard2.1)
- 2021.11.08/impish/linux-aws/5.13.0-1007.8 (some instances, e.g. m5a.large,
i3en.24xlarge; c3.xlarge shows few first tpci tests but then fails)
- 2021.11.08/impish/linux-kvm/5.13.0-1006.6 on amd64
Same in previous cycle.
The ubuntu_ltp_kernel_misc test log is cut shortly after starting
tpci:
02:24:05 INFO | STARTubuntu_ltp_kernel_misc.tpci
ubuntu_ltp_kernel_misc.tpcitimestamp=1637115845timeout=1200
localtime=Nov 17 02:24:05
02:24:05 DEBUG| Persistent state client._record_indent now set to 2
02:24:05 DEBUG| Persistent state client.unexpected_reboot now set to
('ubuntu_ltp_kernel_misc.tpci', 'ubuntu_ltp_kernel_misc.tpci')
02:24:05 DEBUG| Waiting for pid 52606 for 1200 seconds
02:24:05 WARNI| System python is too old, crash handling disabled
---
R E S U L T S
---
+ rsync -ar -e 'ssh -o StrictHostKeyChecking=no -o
UserKnownHostsFile=/dev/null -o LogLevel=quiet'
ubuntu@3.135.201.81:kernel-test-results/
/home/aws/workspace/impish-linux-aws-aws-amd64-5.13.0-m5a.large-ubuntu_ltp_kernel_misc
rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
rsync error: unexplained error (code 255) at io.c(235) [Receiver=3.1.2]
++ python --version
Python 2.7.17
+ [[ '' = *3.5.* ]]
+ /var/lib/jenkins/autotest/client/tools/glue_testsuites
'/home/aws/workspace/impish-linux-aws-aws-amd64-5.13.0-m5a.large-ubuntu_ltp_kernel_misc/*.xml'
** Warning: The requested file
(/home/aws/workspace/impish-linux-aws-aws-amd64-5.13.0-m5a.large-ubuntu_ltp_kernel_misc/*.xml)
does not exist.
Traceback (most recent call last):
File "/var/lib/jenkins/autotest/client/tools/glue_testsuites", line 51, in
main(sys.argv[1:])
File "/var/lib/jenkins/autotest/client/tools/glue_testsuites", line 43, in
main
content = file_load(fname).split('\n')
AttributeError: 'NoneType' object has no attribute 'split'
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1951227/+subscriptions
--
Mailing list: https://launchpad.net/~canonical-ubuntu-qa
Post to : canonical-ubuntu-qa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa
More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [Bug 2054154] [NEW] b/linux: kvm_smoke_test fails on metal/kernel02
Public bug reported: The test started to fail with bionic/linux 4.15.0-222.233. 16:08:24 ERROR| [stderr] + uvt-kvm wait bjf-test --insecure --ssh-private-key-file /home/ubuntu/.ssh/id_rsa 16:11:22 ERROR| [stderr] uvt-kvm: error: timed out waiting for ssh to open on 192.168.122.148. 16:11:22 ERROR| [stderr] + cleanup 16:11:22 ERROR| [stderr] + uvt-kvm destroy bjf-test 16:11:23 ERROR| [stderr] + '[' s390x = ppc64el ']' 16:11:23 ERROR| Exception escaping from test: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/ubuntu_kvm_smoke_test/ubuntu_kvm_smoke_test.py", line 64, in run_once self.results = utils.system_output(cmd, retain_output=True) File "/home/ubuntu/autotest/client/shared/utils.py", line 1268, in system_output verbose=verbose, args=args).stdout File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run "Command returned non-zero exit status") CmdError: Command failed, rc=1, Command returned non-zero exit status * Command: sudo -u ubuntu /home/ubuntu/autotest/client/tests/ubuntu_kvm_smoke_test /the-test s390x Exit status: 1 Duration: 189.442286968 This might be related to the changes merged for https://bugs.launchpad.net/uvtool/+bug/2039441 main_wait_remote() in uvtool/wait will now enforce the timeout (default 120 seconds) when waiting for the remote to be ready, while previously before these changes, it did not. The remote-wait.sh script in uvtool does not enforce the timeout. Looking at the failed test run, uvt-kvm wait time outs after running approximately 3 minutes. The previous successful run of the test on the same machine (in s2023.10.30) takes about 8 minutes for uvt-kvm wait to return: 07:30:51 ERROR| [stderr] + uvt-kvm wait bjf-test --insecure --ssh-private-key-file /home/ubuntu/.ssh/id_rsa 07:38:53 ERROR| [stderr] ++ uvt-kvm ip bjf-test 07:38:53 ERROR| [stderr] + ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -i /home/ubuntu/.ssh/id_rsa ubuntu@192.168.122.47 uname -a 07:39:37 DEBUG| [stdout] Linux bjf-test 4.15.0-194-generic #205-Ubuntu SMP Fri Sep 16 19:53:54 UTC 2022 s390x s390x s390x GNU/Linux 07:39:37 ERROR| [stderr] ++ cut '-d ' -f 2 07:39:37 ERROR| [stderr] +++ uvt-kvm ip bjf-test 07:39:38 ERROR| [stderr] ++ ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -i /home/ubuntu/.ssh/id_rsa ubuntu@192.168.122.47 lsb_release -c 07:40:19 ERROR| [stderr] + RESULT=bionic 07:40:19 ERROR| [stderr] + '[' bionic '!=' bionic ']' 07:40:19 ERROR| [stderr] + cleanup 07:40:19 ERROR| [stderr] + uvt-kvm destroy bjf-test 07:40:20 ERROR| [stderr] + '[' s390x = ppc64el ']' 07:40:21 INFO | GOODubuntu_kvm_smoke_test.kvm_smoke_test ubuntu_kvm_smoke_test.kvm_smoke_testtimestamp=1706082021localtime=Jan 24 07:40:21 completed successfully If my suspicion is correct, the timeout for waiting for the machine to be ready to log in via ssh is reached, but it is not a regression. ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New -- You received this bug notification because you are a member of Canonical Platform QA Team, which is subscribed to ubuntu-kernel-tests. https://bugs.launchpad.net/bugs/2054154 Title: b/linux: kvm_smoke_test fails on metal/kernel02 Status in ubuntu-kernel-tests: New Bug description: The test started to fail with bionic/linux 4.15.0-222.233. 16:08:24 ERROR| [stderr] + uvt-kvm wait bjf-test --insecure --ssh-private-key-file /home/ubuntu/.ssh/id_rsa 16:11:22 ERROR| [stderr] uvt-kvm: error: timed out waiting for ssh to open on 192.168.122.148. 16:11:22 ERROR| [stderr] + cleanup 16:11:22 ERROR| [stderr] + uvt-kvm destroy bjf-test 16:11:23 ERROR| [stderr] + '[' s390x = ppc64el ']' 16:11:23 ERROR| Exception escaping from test: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/ubuntu_kvm_smoke_test/ubuntu_kvm_smoke_test.py", line 64, in run_once
[Canonical-ubuntu-qa] [recipe build #3684224] of ~canonical-platform-qa-jenkins utah-production in focal: Failed to upload
* State: Failed to upload * Recipe: canonical-platform-qa-jenkins/utah-production * Archive: ~canonical-platform-qa-jenkins/ubuntu/canonical-platform-qa-jenkins-prod * Distroseries: focal * Duration: 2 minutes * Build Log: https://launchpad.net/~canonical-platform-qa-jenkins/+archive/ubuntu/canonical-platform-qa-jenkins-prod/+recipebuild/3684224/+files/buildlog.txt.gz * Upload Log: https://launchpad.net/~canonical-platform-qa-jenkins/+archive/ubuntu/canonical-platform-qa-jenkins-prod/+recipebuild/3684224/+files/upload_3684224_log.txt * Builder: https://launchpad.net/builders/lcy02-amd64-056 -- https://launchpad.net/~canonical-platform-qa-jenkins/+archive/ubuntu/canonical-platform-qa-jenkins-prod/+recipebuild/3684224 Your team Canonical Platform QA Jenkins is the requester of the build. -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [recipe build #3684226] of ~canonical-platform-qa-jenkins utah-production in mantic: Failed to upload
* State: Failed to upload * Recipe: canonical-platform-qa-jenkins/utah-production * Archive: ~canonical-platform-qa-jenkins/ubuntu/canonical-platform-qa-jenkins-prod * Distroseries: mantic * Duration: 2 minutes * Build Log: https://launchpad.net/~canonical-platform-qa-jenkins/+archive/ubuntu/canonical-platform-qa-jenkins-prod/+recipebuild/3684226/+files/buildlog.txt.gz * Upload Log: https://launchpad.net/~canonical-platform-qa-jenkins/+archive/ubuntu/canonical-platform-qa-jenkins-prod/+recipebuild/3684226/+files/upload_3684226_log.txt * Builder: https://launchpad.net/builders/lcy02-amd64-115 -- https://launchpad.net/~canonical-platform-qa-jenkins/+archive/ubuntu/canonical-platform-qa-jenkins-prod/+recipebuild/3684226 Your team Canonical Platform QA Jenkins is the requester of the build. -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [recipe build #3684225] of ~canonical-platform-qa-jenkins utah-production in jammy: Failed to upload
* State: Failed to upload * Recipe: canonical-platform-qa-jenkins/utah-production * Archive: ~canonical-platform-qa-jenkins/ubuntu/canonical-platform-qa-jenkins-prod * Distroseries: jammy * Duration: 3 minutes * Build Log: https://launchpad.net/~canonical-platform-qa-jenkins/+archive/ubuntu/canonical-platform-qa-jenkins-prod/+recipebuild/3684225/+files/buildlog.txt.gz * Upload Log: https://launchpad.net/~canonical-platform-qa-jenkins/+archive/ubuntu/canonical-platform-qa-jenkins-prod/+recipebuild/3684225/+files/upload_3684225_log.txt * Builder: https://launchpad.net/builders/lcy02-amd64-114 -- https://launchpad.net/~canonical-platform-qa-jenkins/+archive/ubuntu/canonical-platform-qa-jenkins-prod/+recipebuild/3684225 Your team Canonical Platform QA Jenkins is the requester of the build. -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
[Canonical-ubuntu-qa] [recipe build #3684227] of ~canonical-platform-qa-jenkins utah-production in noble: Failed to upload
* State: Failed to upload * Recipe: canonical-platform-qa-jenkins/utah-production * Archive: ~canonical-platform-qa-jenkins/ubuntu/canonical-platform-qa-jenkins-prod * Distroseries: noble * Duration: 3 minutes * Build Log: https://launchpad.net/~canonical-platform-qa-jenkins/+archive/ubuntu/canonical-platform-qa-jenkins-prod/+recipebuild/3684227/+files/buildlog.txt.gz * Upload Log: https://launchpad.net/~canonical-platform-qa-jenkins/+archive/ubuntu/canonical-platform-qa-jenkins-prod/+recipebuild/3684227/+files/upload_3684227_log.txt * Builder: https://launchpad.net/builders/lcy02-amd64-073 -- https://launchpad.net/~canonical-platform-qa-jenkins/+archive/ubuntu/canonical-platform-qa-jenkins-prod/+recipebuild/3684227 Your team Canonical Platform QA Jenkins is the requester of the build. -- Mailing list: https://launchpad.net/~canonical-ubuntu-qa Post to : canonical-ubuntu-qa@lists.launchpad.net Unsubscribe : https://launchpad.net/~canonical-ubuntu-qa More help : https://help.launchpad.net/ListHelp
