memory-hotplug test from ubuntu_kernel_selftests timeout on some instance of B-gcp-5.3 / B-oracle-5.4
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-kernel-tests |
Triaged
|
Undecided
|
Unassigned |
Bug Description
Kernel: 5.3.0-1014.
This test has passed on some instances:
* f1-micro
* g1-small
* n1-highcpu-32
* n1-highmem-16
* n1std2
* n1std64
Failed (timeout) on:
* n1-highcpu-16
* n1-highmem-8
* n1std8
# selftests: memory-hotplug: mem-on-off-test.sh
# Test scope: 2% hotplug memory
# online all hot-pluggable memory in offline state:
# SKIPPED - no hot-pluggable memory in offline state
# offline 2% hot-pluggable memory in online state
# trying to offline 1 out of 3 memory block(s):
# online->offline memory32
#
not ok 1 selftests: memory-hotplug: mem-on-off-test.sh # TIMEOUT
This will need manual verification against these instances to see if this has something to do with the new timeout feature in kselftest framework.
tags: | added: 5.3 amd64 bionic gcp sru-20200217 ubuntu-kernel-selftests |
tags: | added: kqa-blocker |
description: | updated |
Changed in ubuntu-kernel-tests: | |
status: | New → Triaged |
tags: | added: sru-20200406 |
tags: | added: sru-20210719 |
tags: | added: sru-20230417 |
Giving that this is a simple test timeout and not a critical failure, i'm removing the kqa-blocker tag. Please reference bug 1864626, this may be similar giving that there was a patch submitted to ubuntu- kernel- selftests that allows the user to define timeouts via settings file
https://<email address hidden>/