Found on Groovy/linux 5.8.0-31.33
** Tags added: 5.8 groovy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1783881
Title:
ltp-syscalls: msgstress03 / msgstress04 fails
** Tags added: focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1783881
Title:
ltp-syscalls: msgstress03 / msgstress04 fails because systemd limits
number of
** Tags added: 4.15 bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1783881
Title:
ltp-syscalls: msgstress03 / msgstress04 fails because systemd limits
number of
Updating bug to include msgstress04 failure.
msgstress04 - part of log from F aws : 5.4.0-1026.26 : amd64
12969. 09/23 17:30:15 DEBUG| utils:0153| [stdout] startup='Wed Sep 23 17:11:41
2020'
12970. 09/23 17:30:15 DEBUG| utils:0153| [stdout] msgstress04 0 TINFO : Found
32000 available message
msgstress03 and msgstress04 is failing with similar behavior on Focal
aws : 5.4.0-1026.26 : amd64
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1783881
Title:
** Tags added: sru-20200921
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1783881
Title:
ltp-syscalls: msgstress03 fails because systemd limits number of
processes
Thank you @christian. I marked the Xenial test cases under this same
bug, though can open a new bug and update the hint bug references if
needed. I'll check back to see when/if ddstreet/rbalint have a chance to
review.
For the test results you're posting, I was wondering where you're
getting
Seeing similar problems on Xenial and I suspect it's similar to the
problems occurring with Bionic and Focal:
http://autopkgtest.ubuntu.com/packages/s/systemd/xenial/amd64
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
Public bug reported:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20200817_235646_79e19@/log.gz
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
**
Public bug reported:
Testing failed on:
amd64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/lxc/20200617_163718_07690@/log.gz
arm64:
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kmod in Ubuntu.
https://bugs.launchpad.net/bugs/1872863
Title:
QEMU/KVM display is garbled
12 matches
Mail list logo