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:
ltp-syscall
** 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
Sta
** Tags added: sru-20200629
--
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
Sta
** Tags added: 5.0
--
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
Status in ub
** Tags added: sru-20200217
** Tags added: gcp
--
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
** Tags added: gke
--
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
Status in ub
** Tags added: sru-20200127
--
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
Sta
** Tags added: 5.3
--
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
Status in ub
** Tags added: sru-20200106
--
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
Sta
** Tags added: azure
** Also affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu Cosmic)
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
This failure occurs in the cloud, on amazon aws, it can be reproduced on
c4/c5.large abd c5.metal
where it passes on c5n.xlarge / i3.metal m3.large m4.large.
I will try the suggested steps above on one of the affected flavor types
and see if we can get to the bottom of this.
** Changed in: ubunt
** Tags added: sru-20191202
** Tags added: s390x
--
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 numb
** Changed in: ubuntu-kernel-tests
Status: New => Triaged
--
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 syst
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd i
** Tags added: amd64 linux-kvm sru-20190603 ubuntu-ltp-syscalls
--
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 syste
Hi,
I recommend you to change your test system.
For example, you can modify /etc/systemd/system.conf and change DefaultTasksMax
there. But that is for the systemd started units...
Note that TasksMax these days can accept % values of kernel configured max
tasks too, meaning i.e. one can set it t
The number of processes (in systemd, tasks).
The command below works for me.
Now, should we change the default on our test systems? Running under
systemd-run does not look like a good option.
# systemd-run -p TasksMax=100 ./testcases/bin/msgstress03
--
You received this bug notification be
What about calling it like this:
$ sudo systemd-run ./testcases/bin/msgstress03
Does that make it pass correctly?
Which resource in particular is exhausted? and can it be toggled somehow
using any of
https://www.freedesktop.org/software/systemd/man/systemd.directives.html
?
** Changed in: syste
** Also affects: ubuntu-kernel-tests
Importance: Undecided
Status: New
--
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 fa
20 matches
Mail list logo