Closed Bug 1374203 Opened 4 years ago Closed 4 years ago
Permafailing CCov jit failure in relazify
.js | eval With Cache Code .js:2:3 Error: Assertion failed: got false, expected true (code 3, args "") after eval With Cache Code .js:2:3 Error: Assertion failed: got false, expected true
Started on this merge to m-c from inbound: https://treeherder.mozilla.org/#/jobs?repo=mozilla-central&revision=bb8eab3c3ac4147848c4c85d628ba72029978665&filter-searchStr=8367c40940bf0c0370b0a065e9ed99010c3d3d80
This is a test case that I added recently, I will investigate later today. The test case was added in Bug 1330373. What should I do to reproduce a CCov build locally?
This test case got added in Bug 1330373 and check if decoded function can successfully be relazified. Which goes against the code coverage approach of preventing the relazification in order to keep the counters alive.
Attachment #8879232 - Flags: review?(gmierz2)
Comment on attachment 8879232 [details] [diff] [review] Skip xdr/relazify.js test case. Review of attachment 8879232 [details] [diff] [review]: ----------------------------------------------------------------- Thanks for disabling it for us.
Attachment #8879232 - Flags: review+
Attachment #8879232 - Flags: review?(gmierz2) → review+
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/mozilla-inbound/rev/44031d370133 Code Coverage builds: Skip xdr/relazify.js test case. r=gmierz
(In reply to OrangeFactor Robot from comment #7) > 7 failures […] in the last 7 days. I do not see how these could happen now that the test case is in the filtered list.
Flags: needinfo?(nicolas.b.pierron) → needinfo?(gmierz2)
Based on the orangefactor graph, it stopped on the 20th of June and nothing else has happened since then. It looks lile it is disabled now though. So, we have nothing to worry about here (unless we get a failure within the next week). :)
You need to log in before you can comment on or make changes to this bug.