You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
mkustermann opened this issue
Jun 11, 2013
· 5 comments
Assignees
Labels
area-vmUse area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends.type-bugIncorrect behavior (everything from a crash to more subtle misbehavior)
After enabling isolate/lib/standalone/vm tests, there are more than 100 failures remaining. I'll mark all crashes/failures in the status file with this bug number.
My guess is that failures can have the following reasons:
unimplemented code in the codegenerator
code generator needs to use 'gnueabihf' calling convention
secure socket / https / extension tests: since we compile statically they can't dynamically load libraries
Please don't close this bug until either all issues have been resolved, or other (more specific) bugs have been filed.
The text was updated successfully, but these errors were encountered:
Doesn't seem to happen anymore (I've checked flaky logs). But there are still flaky markers in the status file. Please update the status files before marking this bug as fixed.
area-vmUse area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends.type-bugIncorrect behavior (everything from a crash to more subtle misbehavior)
After enabling isolate/lib/standalone/vm tests, there are more than 100 failures remaining. I'll mark all crashes/failures in the status file with this bug number.
My guess is that failures can have the following reasons:
Please don't close this bug until either all issues have been resolved, or other (more specific) bugs have been filed.
The text was updated successfully, but these errors were encountered: