Bug 7899 - ERROR: Execution of event handler 'errorreport_handler' failed
Summary: ERROR: Execution of event handler 'errorreport_handler' failed
Status: VERIFIED FIXED
Alias: None
Product: Error Reporting tool
Classification: Yocto Project Subprojects
Component: Error Reporting Tool (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 1.9 M3
Assignee: Mariano Lopez
QA Contact: Cristina Agurida
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2015-06-17 10:56 UTC by Michael Wood
Modified: 2015-07-22 14:02 UTC (History)
2 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments
full-error-log (1.10 MB, application/x-tar)
2015-06-17 10:56 UTC, Michael Wood
no flags Details
exception log (108.83 KB, application/x-tar)
2015-06-17 11:22 UTC, Michael Wood
no flags Details
part of the parsed output (2.87 KB, text/x-log)
2015-06-25 14:49 UTC, Mariano Lopez
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Wood 2015-06-17 10:56:44 UTC
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>)
Comment 1 Michael Wood 2015-06-17 11:22:58 UTC
Created attachment 2553 [details]
exception log
Comment 2 Mariano Lopez 2015-06-18 15:25:24 UTC
Hi Michael,

I need the steps to reproduce the issue. Can you share this?

Thanks
Comment 3 Michael Wood 2015-06-22 10:10:44 UTC
I was just forwarding this on as a report from Ross (cc'd) maybe he can give more info.
Comment 4 Ross Burton 2015-06-22 10:47:30 UTC
The reproducer steps were "build something".  My guess was something in the output was not being sufficiently escaped.
Comment 5 Mariano Lopez 2015-06-25 14:49:24 UTC
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.
Comment 6 Ross Burton 2015-06-25 15:03:03 UTC
Aha.  So, each failure needs to go to a random filename in case there are parallel errors being reported?
Comment 7 Mariano Lopez 2015-06-26 14:05:17 UTC
Sent patch to review
Comment 9 Cristina Agurida 2015-07-22 14:02:07 UTC
Verified on master: 0f8d89ce66cfffccc9911d6c61470a585173b79d