From: SourceForge.net <no...@so...> - 2012-07-19 16:03:26
|
Bugs item #3544685, was opened at 2012-07-16 10:50 Message generated for change (Comment added) made by stwo You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=3544685&group_id=10894 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: 49. Threading Group: development: 8.5.12 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Stuart Cassoff (stwo) Assigned to: Joe Mistachkin (mistachkin) Summary: Threaded build failures on OpenBSD-current Initial Comment: Trunk and 8.5.12rc0. async-4.3 fails on i386 and amd64 (sporadic) "Test file error: child killed: SIGABRT" interp-36.7 fails on i386 and amd64 event-14.1 fails on i386 (sporadic), difficult to reproduce, try repeatedly running the event tests with minimal delay between runs. I am currently able to reproduce this one with trunk but not 8.5.12rc0. ---------------------------------------------------------------------- >Comment By: Stuart Cassoff (stwo) Date: 2012-07-19 09:03 Message: Re async-4.3: There may be a specific problem with async-4.3 but for now the SIGABRT comes from other code in async.test which can be boiled down to: $ make runtest % testasync delete [testasync create q] Abort trap (core dumped) ---------------------------------------------------------------------- Comment By: Stuart Cassoff (stwo) Date: 2012-07-19 08:00 Message: interp-36.7 passes if "after 10 ..." is changed to "after 200 ..." ---------------------------------------------------------------------- Comment By: Don Porter (dgp) Date: 2012-07-19 06:57 Message: so, timing sensitivty could be an issue. Does it help to change the "after 10 ..." to "after 200 ..." ? ---------------------------------------------------------------------- Comment By: Stuart Cassoff (stwo) Date: 2012-07-18 21:20 Message: This is with 8.5.12rc1. I can't get info for async-4.3 anymore since it just SIGABRTs, I guess, but iirc the reason for failure was similar. ==== interp-36.7 SlaveBgerror sets error handler of slave [1999035] FAILED ==== Contents of test case: slave eval { variable done {} after 0 error foo after 10 [list ::set [namespace which -variable done] {}] vwait [namespace which -variable done] } set result ---- Result was: untouched ---- Result should have been (exact matching): foo ==== interp-36.7 FAILED ---------------------------------------------------------------------- Comment By: Don Porter (dgp) Date: 2012-07-17 10:20 Message: What does the interp-36.7 failure look like? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=110894&aid=3544685&group_id=10894 |