-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] sof-logger resisted pkill -INT, using -KILL #385
Comments
Quick workaround submitted at #381 |
Commit 61271a3 ("logger: stop discarding all error messages and fix the cleanup code") made two mistakes: 1. It used the -INT signal which doesn't always work. This broke most tests. 2. It then misused exit_failure=2 where 2 means Not Applicable. This turned most broken tests to green. Rushed commit a2669ff ("hijack.sh: don't fail yet when sof-logger resists kill -INT") then downgraded all this to warning to get the tests passing again. However it didn't deal with the real issue: stopping the logger on the first try. Switching to TERM does it and will hopefully close https://github.com/thesofproject/sof/issues/3433 Signed-off-by: Marc Herbert <marc.herbert@intel.com>
I cannot reproduce locally but I got an idea:
I don't do anything From https://pubs.opengroup.org/onlinepubs/7908799/xsh/signal.h.html
I've never done the REMOTE_ thing, no idea how to do it. @xiulipan or @aiChaoSONG could you compare REMOTE_ vs local for me? |
I switched from -INT to -TERM and it works, please review: #382 I filed this in sof because I was afraid it was an issue with the logger but now I think it's just an sof-test issue. |
Keep this issue open before we root cause if this is a bug of sof-logger or test case.
|
I believe this has been fixed by #382 |
#373 was merged because https://sof-ci.01.org/softestpr/PR373/build182/devicetest was all green. However almost all tests were failing because the sof-logger resisted kill -INT. To make it worse I misused
exit_status=2
which has the special meaning Not Applicable which means no error and everything is green.The text was updated successfully, but these errors were encountered: