** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
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/1856900
Title:
stress-ng sysinfo stressor fails on ppc64el with
So I think we're in good condition now for 5.4.0-21 on ppc64el.
--
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/1856900
Title:
stress-ng sysinfo stressor fails on ppc64el with linux
@Seth looking at the log it is run:
23:52:22 INFO | START timestamp=1585612342localtime=Mar
30 23:52:22
23:52:22 DEBUG| Persistent state client._record_indent now set to 1
23:52:22 INFO | START ubuntu_stress_smoke_test.setup
ubuntu_stress_smoke_test.setup
I don't see that the sysinfo stressor runs at all in the logs for
5.4.0-21:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-focal/focal/ppc64el/l/linux/20200331_002447_e28f4@/log.gz
--
You received this bug notification because you are a
I've manually re-run the tests on 5.4.0-18-generic on modoc several
times and can't trip this issue. Is it possible to re-run all tests
again to see if it fails when run from the test infrastructure?
--
You received this bug notification because you are a member of Kernel
Packages, which is
I believe this is because a FUSE based file system is being used in the
prior ADT testing and sysinfo is breaking on the FUSE filesystem, so it
may be a problem with with the fuse fs itself or the fuse file system
that is using the kernel fuse core.
--
You received this bug notification because
I've seen something very similar to this on this platform and I believe
it's a combination of previous regressions tests and the stress-ng
sysinfo test that triggers this. Running the stress-ng stressor after a
clean boot won't trigger this issue.
** Changed in: linux (Ubuntu)
Importance:
7 matches
Mail list logo
