Closed
Bug 854209
Opened 12 years ago
Closed 12 years ago
add asm.js mochitests
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla23
People
(Reporter: luke, Assigned: luke)
References
Details
Attachments
(1 file)
12.32 KB,
patch
|
sstangl
:
review+
|
Details | Diff | Splinter Review |
OdinMonkey has a bunch of unit tests in js/src/jit-tests/tests/asm.js, but we need some browser tests as well:
- crashing with asm.js (testing breakpad)
- out-of-bounds and slow-script exceptions handled by Odin
- asm.js code running in a web worker
- something non-trivial like zlib
Comment 1•12 years ago
|
||
A web worker test is in 854197, hope it's helpful.
Comment 2•12 years ago
|
||
Bug 854197, I meant.
Assignee | ||
Comment 3•12 years ago
|
||
Ted: I'd like to write a mochitest that runs asm.js, triggers some faults that the asm.js signal handler handles, then triggers a real crash that breakpad handles. Is there any way to do this from a mochitest, or does it require xpcshell (which requires 842728 to be fixed)?
Comment 4•12 years ago
|
||
You can't crash a Mochitest and handle it. You can crash a plugin or a content process, but I'm not sure if either of those would test what you want. We may need to fix the xpcshell thing to test this properly.
Assignee | ||
Comment 5•12 years ago
|
||
(In reply to Ted Mielczarek [:ted.mielczarek] from comment #4)
Ah, ok. Any plans to do that in the near term? It'd be great to get in an automated test to catch signal handler regressions wrt breakpad.
Assignee | ||
Comment 6•12 years ago
|
||
Here's a first round that verifies asm.js optimizations, hits asm.js-handled faults, and runs asm.js code in a worker.
The only thing pending is adding an xpconnect test that the crash handler works when asm.js handlers have been installed (which has been hand-verified, of course). But that will have to block on bug 842728.
Updated•12 years ago
|
Attachment #743821 -
Flags: review?(sstangl) → review+
Assignee | ||
Comment 7•12 years ago
|
||
Comment 8•12 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla23
You need to log in
before you can comment on or make changes to this bug.
Description
•