Closed kloczek closed 1 year ago
What environment is this running on? I just cloned it and ran make -O -j48 V=1 VERBOSE=1 test -j1 without any problems.
What happens if you try a single test (sudo ./high_cpu.sh)?
Hey @kloczek - just checking in to see if you have any updates on this?
here it is ..
[tkloczko@devel-g2v scenarios]$ ./high_cpu.sh
PID: 4064649
ChildrenPID: 4064651
ChildPID: 4064651
/home/tkloczko/rpmbuild/BUILD/ProcDump-for-Linux-1.2/bin/procdump -C 80 -p 4064651
ProcDump v1.2 - Sysinternals process dump utility
Copyright (C) 2020 Microsoft Corporation. All rights reserved. Licensed under the MIT license.
Mark Russinovich, Mario Hewardt, John Salem, Javid Habibi
Monitors a process and writes a dump file when the process meets the
specified criteria.
Process: stress-ng (4064651)
CPU Threshold: >=80
Commit Threshold: n/a
Thread Threshold: n/a
File descriptor Threshold: n/a
Signal: n/a
Polling interval (ms): 1000
Threshold (s): 10
Number of Dumps: 1
Output directory for core dumps: .
Press Ctrl-C to end monitoring without terminating the process.
[03:43:00 - WARN]: Procdump not running with elevated credentials. If your uid does not match the uid of the target process procdump will not be able to capture memory dumps
[03:43:08 - INFO]: CPU: 80%
[03:43:09 - INFO]: Core dump 0 generated: ./stress_ng_cpu_2022-05-26_03:43:08.4064651
I just retested my whole package and as long as test suite is executed with -j1
everything looks like it is OK.
With parallelisation it fails.
I see. Yes, when running the tests via make (specifying the -jX flag where X > 1) the tests might not work. That is by design as some of the tests rely on procdump monitoring by process name. If you run them in parallel you might end up with multiple processes with the same name at the same time. We can add a check in the Makefile that makes sure -j1 has been set and error otherwise.
I'm closing this issue. If there are any concerns, please re-open.
Looks like test suite is failing