windows/aarch64 - REFTEST TEST-UNEXPECTED-FAIL | build/tests/jsreftest/tests/shell.js:127: TypeError: Assertion failed: got "0", expected "5e-324" item 1
Categories
(Core :: JavaScript Engine, defect, P5)
Tracking
()
People
(Reporter: intermittent-bug-filer, Unassigned)
References
(Blocks 2 open bugs)
Details
#[markdown(off)]
Filed by: egao [at] mozilla.com
https://treeherder.mozilla.org/logviewer.html#?job_id=226690338&repo=try
Issue observed on win10/aarch64 test run.
09:01:26 INFO - TEST-INFO | FAILED! TypeError: Assertion failed: got "0", expected "5e-324"
09:01:26 INFO - JavaScript error: file:///C:/tasks/task_1549529362/build/tests/jsreftest/tests/shell.js, line 127: TypeError: Assertion failed: got "0", expected "5e-324"
09:01:26 INFO - REFTEST TEST-UNEXPECTED-FAIL | file:///C:/tasks/task_1549529362/build/tests/jsreftest/tests/jsreftest.html?test=non262/Math/fround.js | Unknown file:///C:/tasks/task_1549529362/build/tests/jsreftest/tests/shell.js:127: TypeError: Assertion failed: got "0", expected "5e-324" item 1
Comment 1•6 years ago
|
||
:sdetar, not sure if this is in your area or not, I suspect arm64 acts differently and amd64 or i386 for large numbers and floating points. If this isn't your area I can look further. My goal is to associate these test failures with tracking bugs, so if there is work in progress lets make this blocking that.
Updated•6 years ago
|
Comment hidden (Intermittent Failures Robot) |
Comment 3•6 years ago
|
||
:jmaher, added to Meta bug 1526995 which I am using to track these bugs related to the JS engine. Once we have ARM64 Ion support completed, we can re-validate if these test still fail and need to be fixed.
Comment hidden (Intermittent Failures Robot) |
Updated•6 years ago
|
Comment hidden (Intermittent Failures Robot) |
Comment 6•6 years ago
|
||
This test was disabled/skipped for windows10-aarch64 in https://phabricator.services.mozilla.com/D24741.
Updated•6 years ago
|
Updated•3 years ago
|
Updated•1 year ago
|
Description
•