Closed
Bug 1442786
Opened 6 years ago
Closed 6 years ago
Failed spidermonkey jobs do not upload binaries
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla60
Tracking | Status | |
---|---|---|
firefox60 | --- | fixed |
People
(Reporter: sfink, Assigned: sfink)
Details
Attachments
(1 file)
2.09 KB,
patch
|
nbp
:
review+
|
Details | Diff | Splinter Review |
I was looking through some ancient patches, and found this one that I thought I had already landed. nbp ran into this some time ago, where he was trying to reproduce a try failure but it unhelpfully would not give him the binary that it was using to fail the test. (If I remember correctly, the issue ended up being that try turns off ASLR?)
Assignee | ||
Comment 1•6 years ago
|
||
Attachment #8955686 -
Flags: review?(nicolas.b.pierron)
Assignee | ||
Comment 2•6 years ago
|
||
Argh. Lost my attachment comment. The problem is that a calling script without set -e was sourcing a script with set -e in it, thus inheriting set -e, and then when tests failed, it bailed out immediately instead of continuing as was intended.
Comment 3•6 years ago
|
||
Comment on attachment 8955686 [details] [diff] [review] Prevent set -e from leaking into calling scripts Review of attachment 8955686 [details] [diff] [review]: ----------------------------------------------------------------- Thanks for catching this issue :) I learning some Shell scripting too, I did not knew that set could be scoped that way. > If I remember correctly, the issue ended up being that try turns off ASLR? Correct.
Attachment #8955686 -
Flags: review?(nicolas.b.pierron) → review+
Pushed by sfink@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/8799608e5f0b Prevent set -e from leaking into calling scripts, r=nbp
Comment 5•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/8799608e5f0b
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
status-firefox60:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla60
You need to log in
before you can comment on or make changes to this bug.
Description
•