canonical-ubuntu-qa team mailing list archive

[Po-Hsu Lin <2029373@xxxxxxxxxxxxxxxxxx>]

Test results on different releases in cycle 2024.08.05 on node ivysaur:
 * Noble
  - apache: 12m26s
  - crafty: 10m08s
 * Jammy
  - apache: 12m37s
  - crafty: 10m09s
 * Focal
  - apache: 12m31s
  - crafty: 10m13s

Test results on different releases in cycle 2024.07.08 on node ivysaur:
 * Noble
  - apache: 12m36s
  - crafty: 10m08s
 * Jammy
  - apache: 11m15s
  - crafty: 09m09s
 * Focal
  - apache: 11m29s
  - crafty: 10m09s

Note that these tests are marked as "NOTRUN: test not run, no data" in
the end of the test. So adjusting the timeout threshold should be OK, as
it's just allow it to finish properly instead of relaxing the
performance threshold.

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

Title:
  ubuntu_performance_pts_apache fails on focal 5.4.0-156.173

Status in ubuntu-kernel-tests:
  In Progress

Bug description:
  ubuntu_performance_pts_apache and ubuntu_performance_pts_crafty fail
  with Timer expired (600 sec.), nuking pid 20401

  First time seen on ivysaur instance for both generic and lowlatency
  image.

  This is the first we test these in a while, previous releases failed
  with boot failure, therefore this is not considered a new regression.

  Link: http://10.246.75.167/2023.07.10/focal/linux/5.4.0-156.173/sru-
  lowlatency-metal-ivysaur.amd64-ubuntu_performance_pts-log.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2029373/+subscriptions