Public bug reported:
Issue found on node "kili"
rlimit STARTING
rlimit RETURNED 2
rlimit FAILED
stress-ng: debug: [1496254] 56 processors online, 56 processors configured
stress-ng: info: [1496254] dispatching hogs: 4 rlimit
stress-ng: debug: [1496254] cache allocate: default cache size: 35840K
stress-ng: debug: [1496254] starting stressors
stress-ng: debug: [1496255] stress-ng-rlimit: started [1496255] (instance 0)
stress-ng: debug: [1496256] stress-ng-rlimit: started [1496256] (instance 1)
stress-ng: debug: [1496254] 4 stressors spawned
stress-ng: debug: [1496257] stress-ng-rlimit: started [1496257] (instance 2)
stress-ng: debug: [1496258] stress-ng-rlimit: started [1496258] (instance 3)
stress-ng: debug: [1496258] stress-ng-rlimit: child died: signal 9 'SIGKILL'
(instance 3)
stress-ng: debug: [1496256] stress-ng-rlimit: child died: signal 9 'SIGKILL'
(instance 1)
stress-ng: debug: [1496255] stress-ng-rlimit: child died: signal 9 'SIGKILL'
(instance 0)
stress-ng: debug: [1496258] stress-ng-rlimit: assuming killed by OOM killer,
bailing out (instance 3)
stress-ng: debug: [1496256] stress-ng-rlimit: assuming killed by OOM killer,
bailing out (instance 1)
stress-ng: debug: [1496255] stress-ng-rlimit: assuming killed by OOM killer,
bailing out (instance 0)
stress-ng: debug: [1496257] stress-ng-rlimit: child died: signal 9 'SIGKILL'
(instance 2)
stress-ng: debug: [1496257] stress-ng-rlimit: assuming killed by OOM killer,
bailing out (instance 2)
stress-ng: debug: [1496254] process [1496255] terminated
stress-ng: debug: [1496254] process [1496256] terminated
stress-ng: debug: [1496254] process [1496257] terminated
stress-ng: debug: [1496254] process [1496258] terminated
stress-ng: info: [1496254] successful run completed in 1.25s
stress-ng: fail: [1496254] rlimit instance 0 unexpected null checksum data
stress-ng: fail: [1496254] rlimit instance 1 unexpected null checksum data
stress-ng: fail: [1496254] rlimit instance 2 unexpected null checksum data
stress-ng: fail: [1496254] rlimit instance 3 unexpected null checksum data
stress-ng: fail: [1496254] metrics check: stressor metrics corrupted, data is
compromised
info: 5 failures reached, aborting stress process
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.6.0-1010-oem 5.6.0-1010.10
ProcVersionSignature: User Name 5.6.0-1010.10-oem 5.6.8
Uname: Linux 5.6.0-1010-oem x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue May 19 07:14:25 2020
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: linux-signed-oem-5.6
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: stress-ng
Importance: Undecided
Status: New
** Affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
** Affects: linux-signed-oem-5.6 (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal package-from-proposed sru-20200427
ubuntu-stress-smoke-test uec-images
** Also affects: stress-ng
Importance: Undecided
Status: New
** Summary changed:
- rlimit from ubuntu_stress_smoke_test failed on F-OEM-5.6 Edit
+ rlimit from ubuntu_stress_smoke_test failed on F-OEM-5.6
** Also affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
** Tags added: sru-20200427 ubuntu-stress-smoke-test
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879448
Title:
rlimit from ubuntu_stress_smoke_test failed on F-OEM-5.6
To manage notifications about this bug go to:
https://bugs.launchpad.net/stress-ng/+bug/1879448/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
