| Summary: | ERROR: Execution of event handler 'errorreport_handler' failed | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Yocto Project Subprojects] Error Reporting tool | Reporter: | Michael Wood <michael.g.wood> | ||||||||
| Component: | Error Reporting Tool | Assignee: | Mariano Lopez <mariano.lopez> | ||||||||
| Status: | VERIFIED FIXED | QA Contact: | Cristina Agurida <cristina-danielax.agurida> | ||||||||
| Severity: | normal | ||||||||||
| Priority: | Medium+ | CC: | alexandru.c.georgescu, ross.burton | ||||||||
| Version: | unspecified | ||||||||||
| Target Milestone: | 1.9 M3 | ||||||||||
| Hardware: | x86 | ||||||||||
| OS: | Multiple | ||||||||||
| Whiteboard: | |||||||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||||||
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |||||||||
| Attachments: |
|
||||||||||
Created attachment 2553 [details]
exception log
Hi Michael, I need the steps to reproduce the issue. Can you share this? Thanks I was just forwarding this on as a report from Ross (cc'd) maybe he can give more info. The reproducer steps were "build something". My guess was something in the output was not being sufficiently escaped. Created attachment 2562 [details]
part of the parsed output
It looks like the problem is with the synchronization writing into "error-report.txt". If you check the attachment with the last part of the parsed output of the exception log, you can see two task that failed wrote into that file.
Aha. So, each failure needs to go to a random filename in case there are parallel errors being reported? Sent patch to review This bug has been solved with commit: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=master-next&id=cd379328b9ee211d87d65490af6d6f79b77ed80a Verified on master: 0f8d89ce66cfffccc9911d6c61470a585173b79d |
Created attachment 2552 [details] full-error-log ERROR: Execution of event handler 'errorreport_handler' failed Traceback (most recent call last): File "errorreport_handler(e)", line 38, in errorreport_handler(e=<bb.event.BuildCompleted object at 0x32a2690>)