On Thu, 31 Aug 2023 08:40:58 GMT, Aleksey Shipilev wrote:
> Current vmTestbase/nsk/monitoring/stress/thread tests contains 21 tests, each
> running exclusively. This drags the tier4 test times up. There seem to be no
> reason to run these tests exclusively, though: they complete in reasonable
On Thu, 31 Aug 2023 08:40:58 GMT, Aleksey Shipilev wrote:
> Current vmTestbase/nsk/monitoring/stress/thread tests contains 21 tests, each
> running exclusively. This drags the tier4 test times up. There seem to be no
> reason to run these tests exclusively, though: they complete in reasonable
On Thu, 31 Aug 2023 14:03:15 GMT, Thomas Stuefe wrote:
> I think this is fine, but it may inconvenience some test maintainers since we
> may now run against /proc/sys/kernel/threads-max or whatever other limits
> there are. Or do we do worse things already in other tests?
Yeah, I think we do w
On Thu, 31 Aug 2023 15:21:52 GMT, Leonid Mesnik wrote:
>> Current vmTestbase/nsk/monitoring/stress/thread tests contains 21 tests,
>> each running exclusively. This drags the tier4 test times up. There seem to
>> be no reason to run these tests exclusively, though: they complete in
>> reasonab
On Thu, 31 Aug 2023 08:40:58 GMT, Aleksey Shipilev wrote:
> Current vmTestbase/nsk/monitoring/stress/thread tests contains 21 tests, each
> running exclusively. This drags the tier4 test times up. There seem to be no
> reason to run these tests exclusively, though: they complete in reasonable
On Thu, 31 Aug 2023 08:40:58 GMT, Aleksey Shipilev wrote:
> Current vmTestbase/nsk/monitoring/stress/thread tests contains 21 tests, each
> running exclusively. This drags the tier4 test times up. There seem to be no
> reason to run these tests exclusively, though: they complete in reasonable
On Thu, 31 Aug 2023 08:40:58 GMT, Aleksey Shipilev wrote:
> Current vmTestbase/nsk/monitoring/stress/thread tests contains 21 tests, each
> running exclusively. This drags the tier4 test times up. There seem to be no
> reason to run these tests exclusively, though: they complete in reasonable
Current vmTestbase/nsk/monitoring/stress/thread tests contains 21 tests, each
running exclusively. This drags the tier4 test times up. There seem to be no
reason to run these tests exclusively, though: they complete in reasonable
time, are lightly-threaded, and consume the usual amount of memory
