date:20240318

[Canonical-ubuntu-qa] [Bug 2051378] Re: cpuhotplug failures on google n2d-standard-4.sev_snp VMs

2024-03-18 Thread Po-Hsu Lin

With jammy/linux-gcp-6.5/6.5.0-1017.17~22.04.1 on n2d-standard-4.sev_snp, 
ubuntu_ltp.cpuhotplug:cpuhotplug02 has passed:
 INFO: Test start time: Sat Mar 16 03:10:32 UTC 2024
 COMMAND:/opt/ltp/bin/ltp-pan -q  -e -S   -a 422515 -n 422515  -f 
/tmp/ltp-KBfVFAlKgT/alltests -l /dev/null  -C /dev/null -T /dev/null
 LOG File: /dev/null
 FAILED COMMAND File: /dev/null
 TCONF COMMAND File: /dev/null
 Running tests...
 Name:   cpuhotplug02
 Date:   Sat Mar 16 03:10:33 UTC 2024
 Desc:   What happens to a process when its CPU is offlined?
 
 CPU is 1
 cpuhotplug02 1 TPASS: turned off CPU 1, process migrated to CPU   0
 INFO: ltp-pan reported all tests PASS
 LTP Version: 20230929-406-gcbc2d0568
 INFO: Test end time: Sat Mar 16 03:10:45 UTC 2024


But ubuntu_ltp.cpuhotplug:cpuhotplug03 cause the crash this time.

** Tags added: sru-s20240205

-- 
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/2051378

Title:
  cpuhotplug failures on google n2d-standard-4.sev_snp VMs

Status in ubuntu-kernel-tests:
  New

Bug description:
  Testing on n2d-standard-4.sev_snp and possibly other sev_snp enabled
  instances unexpectedly reboot during  cpuhotplug operations. This is
  known to happen during the following tests:

  ubuntu_ftrace_smoke_test.ftrace-smoke-test
  ubuntu_kernel_selftests.cpu-hotplug:cpu-on-off-test.sh
  ubuntu_kselftests_ftrace.ftrace:test.d--00basic--basic2.tc
  ubuntu_ltp.cpuhotplug:cpuhotplug02

  The VM will reboot in most cases interrupting the test. From the
  console logs we see messages like:

  ...
  Jan 25 19:22:13 j-lgcp-gcp-5-15-n2dstd4-sev-snp-u-ftrace-smk-test kernel: [  
192.364513] mmiotrace: Disabling non-boot CPUs...
  Jan 25 19:22:13 j-lgcp-gcp-5-15-n2dstd4-sev-snp-u-ftrace-smk-test kernel: [  
192.403578] smpboot: CPU 1 is now offline
  Jan 25 19:22:13 j-lgcp-gcp-5-15-n2dstd4-sev-snp-u-ftrace-smk-test kernel: [  
192.425028] mmiotrace: CPU1 is down.
  Jan 25 19:22:13 j-lgcp-gcp-5-15-n2dstd4-sev-snp-u-ftrace-smk-test kernel: [  
192.447485] smpboot: CPU 2 is now offline
  Jan 25 19:22:13 j-lgcp-gcp-5-15-n2dstd4-sev-snp-u-ftrace-smk-test kernel: [  
192.464986] mmiotrace: CPU2 is down.
  Jan 25 19:22:13 j-lgcp-gcp-5-15-n2dstd4-sev-snp-u-ftrace-smk-test kernel: [  
192.483908] smpboot: CPU 3 is now offline

  then the VM starts booting again.

  This has been seen on at least linux-gcp 5.15 and 6.5 kernels since
  we've started testing on these n2d-standard-4.sev_snp VMs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2051378/+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] [Merge] ~andersson123/autopkgtest-cloud:lxd-armhf14-lxd-armhf10-replacement into autopkgtest-cloud:master

2024-03-18 Thread Tim Andersson

Tim Andersson has proposed merging 
~andersson123/autopkgtest-cloud:lxd-armhf14-lxd-armhf10-replacement 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/462575
-- 
Your team Canonical's Ubuntu QA is requested to review the proposed merge of 
~andersson123/autopkgtest-cloud:lxd-armhf14-lxd-armhf10-replacement into 
autopkgtest-cloud:master.
diff --git a/mojo/service-bundle b/mojo/service-bundle
index 934a4e3..104e519 100644
--- a/mojo/service-bundle
+++ b/mojo/service-bundle
@@ -154,11 +154,11 @@ applications:
 10.44.124.165: 3  # lxd-armhf7  @ krusha
 10.44.124.216: 3  # lxd-armhf8  @ swirlix29
 10.44.124.246: 3  # lxd-armhf9  @ krusha
-10.44.124.249: 3  # lxd-armhf10 @ jojora
+10.44.124.252: 3  # lxd-armhf10 @ jojora
 10.44.124.25:  3  # lxd-armhf11 @ krusha
 10.44.124.223: 3  # lxd-armhf12 @ jojora
 10.44.124.24:  3  # lxd-armhf13 @ krusha
-10.44.124.240: 3  # lxd-armhf14 @ krusha
+10.44.124.217: 3  # lxd-armhf14 @ krusha
 10.44.124.151: 3  # lxd-armhf15 @ krusha
 10.44.124.170: 3  # lxd-armhf16 @ jojora
 10.44.124.26:  3  # lxd-armhf17 @ krusha
-- 
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:lxd-armhf14-lxd-armhf10-replacement into autopkgtest-cloud:master

2024-03-18 Thread mp+462575

The proposal to merge 
~andersson123/autopkgtest-cloud:lxd-armhf14-lxd-armhf10-replacement into 
autopkgtest-cloud:master has been updated.

Status: Needs review => Merged

For more details, see:
https://code.launchpad.net/~andersson123/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/462575
-- 
Your team Canonical's Ubuntu QA is requested to review the proposed merge of 
~andersson123/autopkgtest-cloud:lxd-armhf14-lxd-armhf10-replacement 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 2058074] Re: invalid PPA sucessfully queued?

2024-03-18 Thread Tim Andersson

This bug should be fixed by this MP:
https://code.launchpad.net/~ubuntu-release/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/462535

The ppa is valid, we're just retrieving the PPA in an invalid way,
basically :)

-- 
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to Auto Package Testing.
https://bugs.launchpad.net/bugs/2058074

Title:
  invalid PPA sucessfully queued?

Status in Auto Package Testing:
  New

Bug description:
  I was looking at the amd64 log files, a favorite Friday afternoon
  activity, and noticed the following lines multiple times:

   409s Purging configuration files for cloud-init 
(23.4.4-0ubuntu0~22.04.1) ...
   410s dpkg: warning: while removing cloud-init, 
directory '/etc/cloud/cloud.cfg.d' not empty so not removed
   410s Processing triggers for rsyslog 
(8.2112.0-2ubuntu2.2) ...
   410s invoke-rc.d: policy-rc.d denied execution of 
try-restart.
   410s Reading package lists...
   411s Building dependency tree...
   411s Reading state information...
   411s linux-generic is already the newest version 
(5.15.0.100.97).
   411s 0 upgraded, 0 newly installed, 0 to remove and 
0 not upgraded.
   411s ERROR: 'dviererbe:dotnet6-0-128-ppa2' is not a 
valid ppa format
   422s autopkgtest [22:05:26]: ERROR: testbed failure: 
testbed setup commands failed with status 1

  If this `is not a valid ppa format` how did it get queued? I don't
  have a scooby - probably because I haven't looked. As a first step we
  should grep the apache2 log files on the web servers to see what the
  actual request was.

  Here's the entry from the json file:

   $ grep dotnet6 queues.json
  "dotnet6 {\"ppas\": [\"dviererbe/dotnet6-0-128-ppa2\"], 
\"requester\": \"dviererbe\", \"submit-time\": \"2024-03-15 20:54:19\", 
\"triggers\": [\"dotnet6/6.0.128-0ubuntu1~23.10.2~ppa1\
  "], \"uuid\": \"4aee6b9c-d8ef-4c5a-80d2-dc0848fe90f6\"}",

  Here's the queue entry which I yanked:

  2024-03-15 22:21:37,071 - queue item: b'dotnet6 {"ppas":
  ["dviererbe/dotnet6-0-128-ppa2"], "requester": "dviererbe", "submit-
  time": "2024-03-15 20:54:19", "triggers":
  ["dotnet6/6.0.128-0ubuntu1~23.10.2~ppa1"], "uuid":
  "4aee6b9c-d8ef-4c5a-80d2-dc0848fe90f6"}' (deleting)

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/2058074/+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 2058062] Re: amd64 workers shouldn't abort after i386 test bed failures

2024-03-18 Thread Tim Andersson

I'm going to look into this bug today.

--
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to Auto Package Testing.
https://bugs.launchpad.net/bugs/2058062

Title:
amd64 workers shouldn't abort after i386 test bed failures

Status in Auto Package Testing:
New

Bug description:
I was looking at the results of i386 tests today and noticed a pattern
like the following:

Mar 15 05:43:57 juju-7f2275-prod-proposed-migration-environment-2
/home/ubuntu/autopkgtest-cloud/worker/worker[3291087]: ERROR: Three tmpfails in
a row, aborting worker. Log follows:
...
320s Creating nova instance
adt-jammy-i386-libxml-parser-perl-20240315-051351-juju-7f2275-prod-proposed-migration-environment-2
from image adt/ubuntu-jammy-amd64-se>
320s autopkgtest [05:43:56]: ERROR: testbed
failure: Can't resolve build dependencies on testbed

Not being able to resolve build dependencies for i386 is a common
occurrence and my concern here is how much time are we losing by
aborting the worker. Is it down for 5, 10, 15 minutes until it gets
restarted again? Any amount of downtime for this is wasteful.

Additionally, retrying two more times is also wasteful because they
aren't likely to get sorted.

Finally, the ideal solution would probably involve not running tests
where the build-deps are gonna fail at all but that seems a lot
harder.

I think we should look at the FAIL_STRINGS stuff here and try to
adjust it for i386.

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/2058062/+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] [Merge] ~andersson123/autopkgtest-cloud:i386-no-retry-on-build-dep-failure into autopkgtest-cloud:master

2024-03-18 Thread Tim Andersson

Tim Andersson has proposed merging 
~andersson123/autopkgtest-cloud:i386-no-retry-on-build-dep-failure into 
autopkgtest-cloud:master.

Requested reviews:
  Canonical's Ubuntu QA (canonical-ubuntu-qa)
Related bugs:
  Bug #2058062 in Auto Package Testing: "amd64 workers shouldn't abort after 
i386 test bed failures"
  https://bugs.launchpad.net/auto-package-testing/+bug/2058062

For more details, see:
https://code.launchpad.net/~andersson123/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/462584
-- 
Your team Canonical's Ubuntu QA is requested to review the proposed merge of 
~andersson123/autopkgtest-cloud:i386-no-retry-on-build-dep-failure into 
autopkgtest-cloud:master.
diff --git a/charms/focal/autopkgtest-cloud-worker/autopkgtest-cloud/worker/worker b/charms/focal/autopkgtest-cloud-worker/autopkgtest-cloud/worker/worker
index f1bbac5..82a6a14 100755
--- a/charms/focal/autopkgtest-cloud-worker/autopkgtest-cloud/worker/worker
+++ b/charms/focal/autopkgtest-cloud-worker/autopkgtest-cloud/worker/worker
@@ -114,6 +114,10 @@ TEMPORARY_TEST_FAIL_STRINGS = [
 "OSError: [Errno 28] No space left on device",
 ]
 
+I386_NO_RETRY_STRINGS = [
+"Can't resolve build dependencies on testbed"
+]
+
 # If we repeatedly time out when installing, there's probably a problem with
 # one of the packages' maintainer scripts.
 FAIL_STRINGS_REGEX = [
@@ -1134,6 +1138,10 @@ def request(msg):
 )
 if s in contents
 ]
+if release.lower() == "i386":
+for I386_FAIL_STRING in I386_NO_RETRY_STRINGS:
+if I386_FAIL_STRING in contents:
+temp_fails = False
 if temp_fails:
 logging.warning(
 "Saw %s in log, which is a sign of a temporary failure.",
-- 
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 2058062] Re: amd64 workers shouldn't abort after i386 test bed failures

2024-03-18 Thread Launchpad Bug Tracker

** Merge proposal linked:
   
https://code.launchpad.net/~andersson123/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/462584

-- 
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to Auto Package Testing.
https://bugs.launchpad.net/bugs/2058062

Title:
  amd64 workers shouldn't abort after i386 test bed failures

Status in Auto Package Testing:
  In Progress

Bug description:
  I was looking at the results of i386 tests today and noticed a pattern
  like the following:

  Mar 15 05:43:57 juju-7f2275-prod-proposed-migration-environment-2 
/home/ubuntu/autopkgtest-cloud/worker/worker[3291087]: ERROR: Three tmpfails in 
a row, aborting worker. Log follows:
  ...
320s Creating nova instance 
adt-jammy-i386-libxml-parser-perl-20240315-051351-juju-7f2275-prod-proposed-migration-environment-2
 from image adt/ubuntu-jammy-amd64-se>
320s autopkgtest [05:43:56]: ERROR: testbed 
failure: Can't resolve build dependencies on testbed

  Not being able to resolve build dependencies for i386 is a common
  occurrence and my concern here is how much time are we losing by
  aborting the worker. Is it down for 5, 10, 15 minutes until it gets
  restarted again? Any amount of downtime for this is wasteful.

  Additionally, retrying two more times is also wasteful because they
  aren't likely to get sorted.

  Finally, the ideal solution would probably involve not running tests
  where the build-deps are gonna fail at all but that seems a lot
  harder.

  I think we should look at the FAIL_STRINGS stuff here and try to
  adjust it for i386.

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/2058062/+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 2058062] Re: amd64 workers shouldn't abort after i386 test bed failures

2024-03-18 Thread Tim Andersson

MP created and in review.

** Changed in: auto-package-testing
   Status: New => In Progress

** Changed in: auto-package-testing
   Importance: Undecided => High

** Changed in: auto-package-testing
 Assignee: (unassigned) => Tim Andersson (andersson123)

-- 
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to Auto Package Testing.
https://bugs.launchpad.net/bugs/2058062

Title:
  amd64 workers shouldn't abort after i386 test bed failures

Status in Auto Package Testing:
  In Progress

Bug description:
  I was looking at the results of i386 tests today and noticed a pattern
  like the following:

  Mar 15 05:43:57 juju-7f2275-prod-proposed-migration-environment-2 
/home/ubuntu/autopkgtest-cloud/worker/worker[3291087]: ERROR: Three tmpfails in 
a row, aborting worker. Log follows:
  ...
320s Creating nova instance 
adt-jammy-i386-libxml-parser-perl-20240315-051351-juju-7f2275-prod-proposed-migration-environment-2
 from image adt/ubuntu-jammy-amd64-se>
320s autopkgtest [05:43:56]: ERROR: testbed 
failure: Can't resolve build dependencies on testbed

  Not being able to resolve build dependencies for i386 is a common
  occurrence and my concern here is how much time are we losing by
  aborting the worker. Is it down for 5, 10, 15 minutes until it gets
  restarted again? Any amount of downtime for this is wasteful.

  Additionally, retrying two more times is also wasteful because they
  aren't likely to get sorted.

  Finally, the ideal solution would probably involve not running tests
  where the build-deps are gonna fail at all but that seems a lot
  harder.

  I think we should look at the FAIL_STRINGS stuff here and try to
  adjust it for i386.

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/2058062/+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 2058059] Re: Handle non-existent packages better

2024-03-18 Thread Tim Andersson

I'll look into this today

** Changed in: auto-package-testing
   Importance: Undecided => Low

** Changed in: auto-package-testing
   Status: New => In Progress

** Changed in: auto-package-testing
 Assignee: (unassigned) => Tim Andersson (andersson123)

-- 
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to Auto Package Testing.
https://bugs.launchpad.net/bugs/2058059

Title:
  Handle non-existent packages better

Status in Auto Package Testing:
  In Progress

Bug description:
  https://autopkgtest.ubuntu.com/packages/cyrus-impad

  I mistyped a package name and then saw links to Launchpad and excuses
  for a package which doesn't exist. I don't believe the service has any
  idea of what packages don't exist versus what packages don't have
  tests but I think it should especially given the external links.

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/2058059/+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] bandali joined autopkgtest-requestors

2024-03-18 Thread autopkgtest-requestors

Hello Canonical's Ubuntu QA,

Amin Bandali (bandali) has been added as a member of autopkgtest-
requestors (autopkgtest-requestors) by Tim Andersson (andersson123).
Follow the link below for more details.

https://launchpad.net/~autopkgtest-requestors/+member/bandali

-- 
You received this email because your team Canonical's Ubuntu QA is an admin of 
the autopkgtest-requestors team.


-- 
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 2058062] Re: amd64 workers shouldn't abort after i386 test bed failures

2024-03-18 Thread Tim Andersson

Decided not to fix for now. Leaving the work as is until we come back to
this.

** Changed in: auto-package-testing
Status: In Progress => Won't Fix

** Changed in: auto-package-testing
Importance: High => Undecided

--
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to Auto Package Testing.
https://bugs.launchpad.net/bugs/2058062

Title:
amd64 workers shouldn't abort after i386 test bed failures

Status in Auto Package Testing:
Won't Fix

Bug description:
I was looking at the results of i386 tests today and noticed a pattern
like the following:

Additionally, retrying two more times is also wasteful because they
aren't likely to get sorted.

Finally, the ideal solution would probably involve not running tests
where the build-deps are gonna fail at all but that seems a lot
harder.

I think we should look at the FAIL_STRINGS stuff here and try to
adjust it for i386.

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/2058062/+subscriptions

[Canonical-ubuntu-qa] [Merge] ~juliank/britney/+git/britney2-ubuntu:time-t into ~ubuntu-release/britney/+git/britney2-ubuntu:master

2024-03-18 Thread Julian Andres Klode

Julian Andres Klode has proposed merging 
~juliank/britney/+git/britney2-ubuntu:time-t into 
~ubuntu-release/britney/+git/britney2-ubuntu:master.

Requested reviews:
  Canonical's Ubuntu QA (canonical-ubuntu-qa)
  Ubuntu Release Team (ubuntu-release)

For more details, see:
https://code.launchpad.net/~juliank/britney/+git/britney2-ubuntu/+merge/462607
-- 
Your team Canonical's Ubuntu QA is requested to review the proposed merge of 
~juliank/britney/+git/britney2-ubuntu:time-t into 
~ubuntu-release/britney/+git/britney2-ubuntu:master.
diff --git a/britney2/policies/autopkgtest.py b/britney2/policies/autopkgtest.py
index c5098d6..bef4935 100644
--- a/britney2/policies/autopkgtest.py
+++ b/britney2/policies/autopkgtest.py
@@ -1131,6 +1131,9 @@ class AutopkgtestPolicy(BasePolicy):
 qname = 'debci-huge-%s-%s' % (self.options.series, arch)
 else:
 qname = 'debci-%s-%s' % (self.options.series, arch)
+# FIXME: Remove after the time_t transition
+if arch == "armhf" and self.options.series == "noble":
+params["all-proposed"] = "1"
 params['submit-time'] = datetime.strftime(datetime.utcnow(), '%Y-%m-%d %H:%M:%S%z')
 
 if self.amqp_channel:
-- 
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] ~juliank/autopkgtest-cloud:time-t into autopkgtest-cloud:master

2024-03-18 Thread Julian Andres Klode

Julian Andres Klode has proposed merging ~juliank/autopkgtest-cloud:time-t into 
autopkgtest-cloud:master.

Requested reviews:
  Canonical's Ubuntu QA (canonical-ubuntu-qa)

For more details, see:
https://code.launchpad.net/~juliank/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/462608
-- 
Your team Canonical's Ubuntu QA is requested to review the proposed merge of 
~juliank/autopkgtest-cloud:time-t 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 d2e5b0d..9ab65b3 100644
--- a/charms/focal/autopkgtest-web/webcontrol/request/submit.py
+++ b/charms/focal/autopkgtest-web/webcontrol/request/submit.py
@@ -335,6 +335,10 @@ class Submit:
 else:
 queue = "debci-%s-%s" % (release, arch)
 
+# FIXME: Remove after time_t transition is complete
+if release == "noble" and arch == "armhf":
+params["all-proposed"] = "1"
+
 params["submit-time"] = datetime.strftime(
 datetime.utcnow(), "%Y-%m-%d %H:%M:%S%z"
 )
-- 
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:time_t-armhf into autopkgtest-cloud:master

2024-03-18 Thread Tim Andersson

Tim Andersson has proposed merging ~andersson123/autopkgtest-cloud:time_t-armhf 
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/462609
-- 
Your team Canonical's Ubuntu QA is requested to review the proposed merge of 
~andersson123/autopkgtest-cloud:time_t-armhf into autopkgtest-cloud:master.
diff --git a/charms/focal/autopkgtest-web/webcontrol/request/app.py b/charms/focal/autopkgtest-web/webcontrol/request/app.py
index e751a43..bfbbfbf 100644
--- a/charms/focal/autopkgtest-web/webcontrol/request/app.py
+++ b/charms/focal/autopkgtest-web/webcontrol/request/app.py
@@ -287,6 +287,9 @@ def index_root():
 return HTML.format(
 LOGOUT + "Deleted {} requests".format(count)
 ).format(**ChainMap(session, params))
+# FIXME: remove after the time_t transition
+if params["arch"] == "armhf" and params["release"] == "noble":
+params["all-proposed"] = 1
 
 if params.get("ppas"):
 uuid = s.send_amqp_request(context="ppa", **params)
-- 
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] ~juliank/britney/+git/britney2-ubuntu:time-t into ~ubuntu-release/britney/+git/britney2-ubuntu:master

2024-03-18 Thread Julian Andres Klode

You have been requested to review the proposed merge of 
~juliank/britney/+git/britney2-ubuntu:time-t into 
~ubuntu-release/britney/+git/britney2-ubuntu:master.

For more details, see:
https://code.launchpad.net/~juliank/britney/+git/britney2-ubuntu/+merge/462607



-- 
Your team Canonical's Ubuntu QA is requested to review the proposed merge of 
~juliank/britney/+git/britney2-ubuntu:time-t into 
~ubuntu-release/britney/+git/britney2-ubuntu:master.
diff --git a/britney2/policies/autopkgtest.py b/britney2/policies/autopkgtest.py
index c5098d6..bef4935 100644
--- a/britney2/policies/autopkgtest.py
+++ b/britney2/policies/autopkgtest.py
@@ -1131,6 +1131,9 @@ class AutopkgtestPolicy(BasePolicy):
 qname = 'debci-huge-%s-%s' % (self.options.series, arch)
 else:
 qname = 'debci-%s-%s' % (self.options.series, arch)
+# FIXME: Remove after the time_t transition
+if arch == "armhf" and self.options.series == "noble":
+params["all-proposed"] = "1"
 params['submit-time'] = datetime.strftime(datetime.utcnow(), '%Y-%m-%d %H:%M:%S%z')
 
 if self.amqp_channel:
-- 
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 1983357] Re: test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on K-5.19 / J-OEM-6.1 / J-6.2 AMD64

2024-03-18 Thread Timo Aaltonen

** Changed in: linux-oem-6.1 (Ubuntu Lunar)
   Status: New => Invalid

** Changed in: linux-oem-6.1 (Ubuntu Mantic)
   Status: New => Invalid

** Changed in: linux-oem-6.1 (Ubuntu Jammy)
   Status: New => Won't Fix

-- 
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/1983357

Title:
  test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on
  K-5.19 / J-OEM-6.1 / J-6.2 AMD64

Status in QA Regression Testing:
  Invalid
Status in ubuntu-kernel-tests:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Won't Fix
Status in linux source package in Kinetic:
  Invalid
Status in linux-oem-6.1 source package in Kinetic:
  Invalid
Status in linux source package in Lunar:
  Won't Fix
Status in linux-oem-6.1 source package in Lunar:
  Invalid
Status in linux source package in Mantic:
  Fix Released
Status in linux-oem-6.1 source package in Mantic:
  Invalid
Status in linux source package in Noble:
  Fix Released
Status in linux-oem-6.1 source package in Noble:
  Invalid

Bug description:
  Issue found on 5.19.0-9.9 Kinetic AMD64 systems

  Test log:
   Running test: './test-kernel-security.py' distro: 'Ubuntu 22.10' kernel: 
'5.19.0-9.9 (Ubuntu 5.19.0-9.9-generic 5.19.0-rc5)' arch: 'amd64' uid: 0/0 
SUDO_USER: 'ubuntu')
   test_021_aslr_dapper_libs (__main__.KernelSecurityTest)
   ASLR of libs ... (default libs native) (default libs native rekey) (default 
libs COMPAT) FAIL
   
   ==
   FAIL: test_021_aslr_dapper_libs (__main__.KernelSecurityTest)
   ASLR of libs
   --
   Traceback (most recent call last):
 File "./test-kernel-security.py", line 1770, in test_021_aslr_dapper_libs
   self._test_aslr('libs', expected)
 File "./test-kernel-security.py", line 1727, in _test_aslr
   self._test_aslr_all(area, expected, "default %s" % area)
 File "./test-kernel-security.py", line 1720, in _test_aslr_all
   self._test_aslr_exec(area, expected, target, name)
 File "./test-kernel-security.py", line 1703, in _test_aslr_exec
   self.assertShellExitEquals(aslr_expected, ["./%s" % (target), area, 
"--verbose"], msg="%s:\n" % name)
 File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py",
 line 1203, in assertShellExitEquals
   self.assertEqual(expected, rc, msg + result + report)
   AssertionError: default libs COMPAT:
   Got exit code 1, expected 0
   Command: './aslr32', 'libs', '--verbose'
   Output:
   Checking ASLR of libs:
   0xf7c81790
   0xf7c81790
   0xf7c81790
   FAIL: ASLR not functional (libs always at 0xf7c81790)
   
   
   --
   Ran 1 test in 0.144s
   
   FAILED (failures=1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1983357/+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

Re: [Canonical-ubuntu-qa] [Merge] ~juliank/britney/+git/britney2-ubuntu:time-t into ~ubuntu-release/britney/+git/britney2-ubuntu:master

2024-03-18 Thread Julian Andres Klode

vs somehow doing it in autopkgtest cloud for each armhf request

Pro:

- this unblocks uploads happening now
- it actually adds all-proposed to the request so it shows up in the log and 
hence retry-autopkgtest-regressions with --all-proposed works correctly

Cons:

- doesn't handle retries without all-proposed automagically
-- 
https://code.launchpad.net/~juliank/britney/+git/britney2-ubuntu/+merge/462607
Your team Canonical's Ubuntu QA is requested to review the proposed merge of 
~juliank/britney/+git/britney2-ubuntu:time-t into 
~ubuntu-release/britney/+git/britney2-ubuntu: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 2016469] Re: test_maps in ubuntu_bpf failed on J-oem-6.1 ( run_parallel: Assertion `status == 0' failed.)

2024-03-18 Thread Timo Aaltonen

** Changed in: linux-oem-6.1 (Ubuntu Jammy)
   Status: New => Won't Fix

-- 
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/2016469

Title:
  test_maps in ubuntu_bpf failed on J-oem-6.1 ( run_parallel: Assertion
  `status == 0' failed.)

Status in ubuntu-kernel-tests:
  New
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux-oem-6.1 source package in Jammy:
  Won't Fix

Bug description:
  Issue found in J-oem-6.1.0-1009.9 after fixing the build issue in bug
  2016455.

  The test_maps in ubuntu_bpf will fail with:
    test_maps: test_maps.c:1375: __run_parallel: Assertion `status == 0' failed.

  Test log:
   Running './test_maps'
   Fork 100 tasks to 'test_update_delete'
   Fork 100 tasks to 'test_update_delete'
   Fork 100 tasks to 'test_update_delete'
   Fork 100 tasks to 'test_update_delete'
   Fork 100 tasks to 'test_update_delete'
   Fork 100 tasks to 'test_update_delete'
   Fork 100 tasks to 'test_update_delete'
   Fork 100 tasks to 'test_update_delete'
   Fork 100 tasks to 'test_update_delete'
   Fork 100 tasks to 'test_update_delete'
   Fork 100 tasks to 'test_update_delete'
   Fork 100 tasks to 'test_update_delete'
   Fork 100 tasks to 'test_hashmap_walk'
   Fork 100 tasks to 'test_hashmap'
   Fork 100 tasks to 'test_hashmap_percpu'
   Fork 100 tasks to 'test_hashmap_sizes'
   Fork 100 tasks to 'test_arraymap'
   Fork 100 tasks to 'test_arraymap_percpu'
   Fork 100 tasks to 'test_update_delete'
   Fork 100 tasks to 'test_update_delete'
   Fork 100 tasks to 'test_update_delete'
   Fork 100 tasks to 'test_update_delete'
   Fork 100 tasks to 'test_update_delete'
   Fork 100 tasks to 'test_update_delete'
   Fork 100 tasks to 'test_update_delete'
   Fork 100 tasks to 'test_update_delete'
   Fork 100 tasks to 'test_update_delete'
   Fork 100 tasks to 'test_update_delete'
   Fork 100 tasks to 'test_update_delete'
   Fork 100 tasks to 'test_update_delete'
   Fork 100 tasks to 'test_hashmap_walk'
   Fork 100 tasks to 'test_hashmap'
   Fork 100 tasks to 'test_hashmap_percpu'
   test_maps: test_maps.c:173: test_hashmap_percpu: Assertion 
`bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed.
   test_maps: test_maps.c:173: test_hashmap_percpu: Assertion 
`bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed.
   test_maps: test_maps.c:173: test_hashmap_percpu: Assertion 
`bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed.
   test_maps: test_maps.c:173: test_hashmap_percpu: Assertion 
`bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed.
   test_maps: test_maps.c:173: test_hashmap_percpu: Assertion 
`bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed.
   test_maps: test_maps.c:173: test_hashmap_percpu: Assertion 
`bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed.
   test_maps: test_maps.c:173: test_hashmap_percpu: Assertion 
`bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed.
   test_maps: test_maps.c:173: test_hashmap_percpu: Assertion 
`bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed.
   test_maps: test_maps.c:173: test_hashmap_percpu: Assertion 
`bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed.
   test_maps: test_maps.c:173: test_hashmap_percpu: Assertion 
`bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed.
   test_maps: test_maps.c:173: test_hashmap_percpu: Assertion 
`bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed.
   test_maps: test_maps.c:173: test_hashmap_percpu: Assertion 
`bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed.
   test_maps: test_maps.c:173: test_hashmap_percpu: Assertion 
`bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed.
   test_maps: test_maps.c:173: test_hashmap_percpu: Assertion 
`bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed.
   test_maps: test_maps.c:173: test_hashmap_percpu: Assertion 
`bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed.
   test_maps: test_maps.c:173: test_hashmap_percpu: Assertion 
`bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed.
   test_maps: test_maps.c:173: test_hashmap_percpu: Assertion 
`bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed.
   test_maps: test_maps.c:173: test_hashmap_percpu: Assertion 
`bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed.
   test_maps: test_maps.c:173: test_hashmap_percpu: Assertion 
`bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed.
   test_maps: test_maps.c:173: test_hashmap_percpu: Assertion 
`bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed.
   test_maps: test_maps.c:173: test_hashmap_percpu: Assertion 
`bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed.
   test_maps: test_maps.c:173: test_hashmap_percpu: Assertion 
`bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' failed.
   test_maps: test_maps.c:173: test_hashmap_percpu: Assertion 
`bpf_map_update_elem(fd, &key, value, BPF_ANY) == 0' fail

Re: [Canonical-ubuntu-qa] [Merge] ~juliank/britney/+git/britney2-ubuntu:time-t into ~ubuntu-release/britney/+git/britney2-ubuntu:master

2024-03-18 Thread Julian Andres Klode

Proposed 
https://code.launchpad.net/~juliank/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/462608
 for doing the same thing for web requests.
-- 
https://code.launchpad.net/~juliank/britney/+git/britney2-ubuntu/+merge/462607
Your team Canonical's Ubuntu QA is requested to review the proposed merge of 
~juliank/britney/+git/britney2-ubuntu:time-t into 
~ubuntu-release/britney/+git/britney2-ubuntu: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

Re: [Canonical-ubuntu-qa] [Merge] ~andersson123/autopkgtest-cloud:time_t-armhf into autopkgtest-cloud:master

2024-03-18 Thread Julian Andres Klode

Review: Approve

lgtm
-- 
https://code.launchpad.net/~andersson123/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/462609
Your team Canonical's Ubuntu QA is requested to review the proposed merge of 
~andersson123/autopkgtest-cloud:time_t-armhf 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] Invitation to canonical-desktop-team accepted by ken-vandine

2024-03-18 Thread autopkgtest-requestors

Hello Canonical's Ubuntu QA,

Ken VanDine (ken-vandine) has accepted the invitation to make Canonical
Desktop Team (canonical-desktop-team) a member of autopkgtest-requestors
(autopkgtest-requestors).


-- 
You received this email because your team Canonical's Ubuntu QA is an admin of 
the autopkgtest-requestors team.


-- 
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] ~juliank/britney/+git/britney2-ubuntu:time-t into ~ubuntu-release/britney/+git/britney2-ubuntu:master

2024-03-18 Thread Julian Andres Klode

v3: We now automatically expire on Apr 4.
-- 
https://code.launchpad.net/~juliank/britney/+git/britney2-ubuntu/+merge/462607
Your team Canonical's Ubuntu QA is requested to review the proposed merge of 
~juliank/britney/+git/britney2-ubuntu:time-t into 
~ubuntu-release/britney/+git/britney2-ubuntu: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

Re: [Canonical-ubuntu-qa] [Merge] ~juliank/britney/+git/britney2-ubuntu:time-t into ~ubuntu-release/britney/+git/britney2-ubuntu:master

2024-03-18 Thread Tim Andersson

For the record now, the autopkgtest-cloud side of things is patched as julian 
mentioned and deployed already.
-- 
https://code.launchpad.net/~juliank/britney/+git/britney2-ubuntu/+merge/462607
Your team Canonical's Ubuntu QA is requested to review the proposed merge of 
~juliank/britney/+git/britney2-ubuntu:time-t into 
~ubuntu-release/britney/+git/britney2-ubuntu: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] [Merge] ~juliank/britney/+git/britney2-ubuntu:time-t into ~ubuntu-release/britney/+git/britney2-ubuntu:master

2024-03-18 Thread mp+462607

The proposal to merge ~juliank/britney/+git/britney2-ubuntu:time-t into 
~ubuntu-release/britney/+git/britney2-ubuntu:master has been updated.

Status: Needs review => Merged

For more details, see:
https://code.launchpad.net/~juliank/britney/+git/britney2-ubuntu/+merge/462607
-- 
Your team Canonical's Ubuntu QA is requested to review the proposed merge of 
~juliank/britney/+git/britney2-ubuntu:time-t into 
~ubuntu-release/britney/+git/britney2-ubuntu: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 2058275] [NEW] queued items with obsoleted package versions shouldn't be in the queue

2024-03-18 Thread Tim Andersson

Public bug reported:

title

we keep things in the queue even when the package version has been
obsoleted

either the worker should handle this or we should have some service
removing items from the queue when the version has been obsoleted

** Affects: auto-package-testing
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to Auto Package Testing.
https://bugs.launchpad.net/bugs/2058275

Title:
  queued items with obsoleted package versions shouldn't be in the queue

Status in Auto Package Testing:
  New

Bug description:
  title

  we keep things in the queue even when the package version has been
  obsoleted

  either the worker should handle this or we should have some service
  removing items from the queue when the version has been obsoleted

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/2058275/+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 1886790] Re: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test)

2024-03-18 Thread Po-Hsu Lin

Hints removed, closing this bug.

** Changed in: ubuntu-kernel-tests
   Status: New => Fix Released

-- 
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/1886790

Title:
  lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels
  (device_add_remove_test)

Status in ubuntu-kernel-tests:
  Fix Released
Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Bionic:
  Fix Released

Bug description:
  [ Impact ]

   * The device_add_remove_test test fails on the affected series (e.g. Bionic).
   * Having the test fixed for the affected series (for example, Bionic) will 
allow us to run the LXC test suite without maintaining local changes for this 
test.

  [ Test Plan ]

   * Run the affected test on an affected series (e.g. Bionic).
   * The test should pass.

  [ Where problems could occur ]

   * The regression risk is very low, and the changes only affect the
  tests, so the regression scope is minimal.

  [ Other Info ]

  Upstream drop of network_latency: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c3082a674f46fe49383b157882c41dfabaa37113
  Related to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1848587

  Original bug report:

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/lxc/20200706_183234_ca65f@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/lxc/20200706_172136_71b68@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/l/lxc/20200706_191938_cedac@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/l/lxc/20200706_163359_98d4d@/log.gz

  The failing test seems to be:

  FAIL: lxc-tests: lxc-test-device-add-remove (0s)
  ---
  Adding /dev/network_latency to the container (device_add_remove_test) 
failed...
  ---

  This is a regression from the 4.15/5.3 to 5.4 kernels in Bionic. Note
  that this testcase is successful on Focal with the same kernel
  version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1886790/+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 2051378] Re: cpuhotplug failures on google n2d-standard-4.sev_snp VMs

[Canonical-ubuntu-qa] [Merge] ~andersson123/autopkgtest-cloud:lxd-armhf14-lxd-armhf10-replacement into autopkgtest-cloud:master

[Canonical-ubuntu-qa] [Merge] ~andersson123/autopkgtest-cloud:lxd-armhf14-lxd-armhf10-replacement into autopkgtest-cloud:master

[Canonical-ubuntu-qa] [Bug 2058074] Re: invalid PPA sucessfully queued?

[Canonical-ubuntu-qa] [Bug 2058062] Re: amd64 workers shouldn't abort after i386 test bed failures

[Canonical-ubuntu-qa] [Merge] ~andersson123/autopkgtest-cloud:i386-no-retry-on-build-dep-failure into autopkgtest-cloud:master

[Canonical-ubuntu-qa] [Bug 2058062] Re: amd64 workers shouldn't abort after i386 test bed failures

[Canonical-ubuntu-qa] [Bug 2058062] Re: amd64 workers shouldn't abort after i386 test bed failures

[Canonical-ubuntu-qa] [Bug 2058059] Re: Handle non-existent packages better

[Canonical-ubuntu-qa] bandali joined autopkgtest-requestors

[Canonical-ubuntu-qa] [Bug 2058062] Re: amd64 workers shouldn't abort after i386 test bed failures

[Canonical-ubuntu-qa] [Merge] ~juliank/britney/+git/britney2-ubuntu:time-t into ~ubuntu-release/britney/+git/britney2-ubuntu:master

[Canonical-ubuntu-qa] [Merge] ~juliank/autopkgtest-cloud:time-t into autopkgtest-cloud:master

[Canonical-ubuntu-qa] [Merge] ~andersson123/autopkgtest-cloud:time_t-armhf into autopkgtest-cloud:master

[Canonical-ubuntu-qa] [Merge] ~juliank/britney/+git/britney2-ubuntu:time-t into ~ubuntu-release/britney/+git/britney2-ubuntu:master

[Canonical-ubuntu-qa] [Bug 1983357] Re: test_021_aslr_dapper_libs from ubuntu_qrt_kernel_security failed on K-5.19 / J-OEM-6.1 / J-6.2 AMD64

Re: [Canonical-ubuntu-qa] [Merge] ~juliank/britney/+git/britney2-ubuntu:time-t into ~ubuntu-release/britney/+git/britney2-ubuntu:master

[Canonical-ubuntu-qa] [Bug 2016469] Re: test_maps in ubuntu_bpf failed on J-oem-6.1 ( run_parallel: Assertion `status == 0' failed.)

Re: [Canonical-ubuntu-qa] [Merge] ~juliank/britney/+git/britney2-ubuntu:time-t into ~ubuntu-release/britney/+git/britney2-ubuntu:master

Re: [Canonical-ubuntu-qa] [Merge] ~andersson123/autopkgtest-cloud:time_t-armhf into autopkgtest-cloud:master

[Canonical-ubuntu-qa] Invitation to canonical-desktop-team accepted by ken-vandine

Re: [Canonical-ubuntu-qa] [Merge] ~juliank/britney/+git/britney2-ubuntu:time-t into ~ubuntu-release/britney/+git/britney2-ubuntu:master

Re: [Canonical-ubuntu-qa] [Merge] ~juliank/britney/+git/britney2-ubuntu:time-t into ~ubuntu-release/britney/+git/britney2-ubuntu:master

[Canonical-ubuntu-qa] [Merge] ~juliank/britney/+git/britney2-ubuntu:time-t into ~ubuntu-release/britney/+git/britney2-ubuntu:master

[Canonical-ubuntu-qa] [Bug 2058275] [NEW] queued items with obsoleted package versions shouldn't be in the queue

[Canonical-ubuntu-qa] [Bug 1886790] Re: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test)

26 matches

Site Navigation

Mail list logo

Footer information