| Summary: | Timeout reported as "ERROR: Exit status is 9" which is not very helpful | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] Ptest-runner | Reporter: | Tim Orling <tim.orling> |
| Component: | ptest-runner | Assignee: | Aníbal Limón <anibal> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Medium+ | CC: | alex.kanavin, anibal, randy.macleod, richard.purdie, tvgamblin |
| Version: | unspecified | ||
| Target Milestone: | 4.0 M2 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Tim Orling
2021-09-16 15:16:29 UTC
Might be related: https://lists.yoctoproject.org/g/yocto/message/54739 https://lists.yoctoproject.org/g/yocto/message/54740 I think so. Can you try the patches locally? Anibal, If you can do this great, if not, ping me and I'll take a look. I was tempted to use this library: http://libexplain.sourceforge.net/ https://linux.die.net/man/3/explain_waitpid but we probably shouldn't add complexity to ptest-runner. What do you think Anibal? The library isn't going to help much. We know that error 9 is killing ptest on timeout, what we need is as much information as possible about why ptest got stuck. (In reply to comment #5) > The library isn't going to help much. We know that error 9 is killing ptest > on timeout, what we need is as much information as possible about why ptest > got stuck. Yes I think the unique way is to see the logs and figure out why got stuck or reproduce the issue locally. I think this has already been fixed? https://git.yoctoproject.org/ptest-runner2/log/ Fixed as described above. |