Updates:
Status: Accepted
Owner: [email protected]
Comment #2 on issue 1075 by [email protected]: ARM: Some deserialization
tests fails
http://code.google.com/p/v8/issues/detail?id=1075
This is actually not fixed, the tests are disabled in the cctest.status
file.
The reason why these are failing is that the tools/test.py script does not
take dependent tests into account when starting threads. The runner simply
starts tests in the right order, i.e., a dependent test is started after
the test it is dependent on is started, but it can be started before the
first tests finishes.
The reason we are failing this on arm is that the test runner is using -j8
(which is a lot for a 2 cpu machine), and depending on the cpu scheduler we
might try to read the serialized file before it has been completely written.
This can easily be reproduced locally (non arm) by running:
tools/test.py -j40 cctest/test-se*
(crashes on almost all runs but are dependent on cpu scheduling)
I am stealing this
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
