** Changed in: ubuntu-kernel-tests
Status: Confirmed => In Progress
** Changed in: ubuntu-kernel-tests
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Focal)
Status:
Note that with LTP test suite update this test is not causing failure to
cgroup_fj_* anymore.
Now it's only failing on GCP g1-small instance. This test will take over
an hour (1h2m) which is slightly above our current threshold (120x,
actual timeout is 60m).
I think we can bump it to 150x (75m).
** Tags removed: ubuntu-ltp
** Tags added: ubuntu-ltp-controllers
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1836694
Title:
memcg_test_3 from controllers in LTP timeout with
** Merge proposal unlinked:
https://code.launchpad.net/~canonical-kernel-team/+git/rt-hints/+merge/444376
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1836694
Title:
memcg_test_3
** Merge proposal linked:
https://code.launchpad.net/~canonical-kernel-team/+git/rt-hints/+merge/444376
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1836694
Title:
memcg_test_3
So this timeout is reproduced only on ARM64? And only when its run
cgroup -> memcg test order? Ill also look into this issue
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1836694
Title:
One interesting finding on ARM64 node appleton-kernel with Jammy
5.15.0-46-generic
If you run the memcg_test_3 directly, it's fairly quick to finish:
However, if you run the cgroup test first (as the order in controller
suite), it will timeout even with 2hr threshold.
controllers suite test
Set timeout multiplier unconditionally [1] can solve this issue on AWS
instances, but test shows ARM64 bare metal node appleton-kernel will
still get this timeout error with jammy lowlatency kernel. Even with 1
hr timeout.
We will need some manual test result on this node before adjusting this.
Test on B-aws arm64 instance a1.medium shows it will take about 500
seconds to finish (~8 minutes), which is higher than our current 5
minutes threshold.
As a1.medium is not a VM, it won't benefit from the LTP_TIMEOUT_MUL setting we
have.
I will modify this part to see how it goes.
--
You
This memcg_test_3 failure on ARM64 instances is no longer causing
cgroup_fj_* test to fail, it just timeout with 30 seconds threshold.
Will need to test it again manually.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Ubuntu 21.10 (Impish Indri) has reached end of life, so this bug will
not be fixed for that specific release.
** Changed in: linux (Ubuntu Impish)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
The Hirsute Hippo has reached End of Life, so this bug will not be fixed
for that release.
** Changed in: linux (Ubuntu Hirsute)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Spotted on 5.4.0-1061.64~18.04.1
** Summary changed:
- memcg_test_3 from controllers in LTP timeout with Bionic/Focal/Hirsute
+ memcg_test_3 from controllers in LTP timeout with Bionic/Focal/Hirsute (arm64)
** Tags added: sru-20211129
--
You received this bug notification because you are a
13 matches
Mail list logo
