Updates:
Status: Invalid
Comment #2 on issue 3409 by [email protected]: r=21915 (bleeding edge)
fails with debug.check
http://code.google.com/p/v8/issues/detail?id=3409
Thanks for trying to help.
You might like to know that we have a continuous integration system at
http://build.chromium.org/p/client.v8/console that runs all tests for all
revisions, so we do have a pretty good idea about what passes and what
fails. Not every failing test run is a reason for panic, as some tests are
known to be flaky (which is unfortunate, but very hard to fix).
Also, a bleeding_edge revision that's already >150 revisions old is not
interesting any more. Unless the failures are still happening with the tip
of the bleeding_edge branch, it's not worth anyone's time to look into
them. Every so often, bleeding_edge breaks (hence the name), but offending
commits are usually fixed or reverted quickly.
--
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.
