Comment #3 on issue 2848 by [email protected]: cctest:
TestJSONStringifyAccessCheck() fails with empty handle in r16208
http://code.google.com/p/v8/issues/detail?id=2848
Yes, it is a known problem that running a set of tests directly through
the "cctest" binary in one process breaks a lot of tests. We only run tests
through the test harness, which spawns a new process for each single test
(modulo threaded tests). To be specific, the following incarnation works
and gives you the same coverage:
./tools/run-tests.py --arch=x64 --mode=debug --no-presubmit cctest/test-api
That being said, I agree that it is _very_ confusing that the "cctest"
binary has the ability to run multiple tests in one process, even though
the tests are written in a way that doesn't support that. But I don't think
we will benefit from fixing all the tests in that regard, it will not give
us additional coverage.
My proposal would be to either remove the ability to run multiple tests in
one process from "cctest", or at least print a big fat warning if it does.
People have been bitten by this several times already.
--
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/groups/opt_out.
