Comment #5 on issue 3706 by [email protected]: Android test failures
https://code.google.com/p/v8/issues/detail?id=3706
unittests/ThreadLocalStorageTest.DoTest and
cctest/test-mark-compact/RegressJoinThreadsOnIsolateDeinit are fixed by #2
and #3.
mjsunit/asm/uint32div is no longer failing, but was not addressed by #2 or
#3 so must have been fixed by another commit.
intl/break-iterator/zh-break is still failing, and
test/mjsunit/es6/math-log2-log10 has now started failing. I don't
understand these failures well enough to be able to fix them or feel
comfortable suppressing them.
Would a bot running tests on Android be a good idea to catch this sort of
failure automatically?
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
