Test262 update 2015-06-11 (Take 3)

Test262 update 2015-06-11 (Take 3)

This reverts commit 72bb369d08e8d141f77c0c05f95cf8ed7ac5a9ec.

Always skip slow tests.

Also, some eval tests are failing in strict mode with nosnap

BUG=N
LOG=N
R=adamk@chromium.org, littledan@chromium.org, machenbach@chromium.org

Committed: https://crrev.com/0f502f679e339f90bd7e560ffff40c06e471eb40
Cr-Commit-Position: refs/heads/master@{#29164}

[arv (Not doing code reviews), 2015-06-18 05:01:00]

PTAL

Patchset 1 is the revert.

Patchset 2 contains the skips of the tests that timed out on debug and nosnap.

[Michael Achenbach, 2015-06-18 08:18:22]

LGTM ~ comment. Just realized that our tryserver nosnap trybot doesn't run
test262-es6. So ignore my try attempt.

https://codereview.chromium.org/1190063002/diff/20001/test/test262-es6/test26...
File test/test262-es6/test262-es6.status (right):

https://codereview.chromium.org/1190063002/diff/20001/test/test262-es6/test26...
test/test262-es6/test262-es6.status:600: 
Are you sure these are all? Note, that the buildbot gui has a small bug/feature
and only shows max 10 failures due to scalability problems. Or are the 54
failures in the stdio just an expansion of the many different variants? See:
http://build.chromium.org/p/client.v8/builders/V8%20Linux%20-%20nosnap/builds...

E.g.:
=== test262-es6/language/statements/variable/12.2.1-9-s ===
--- stdout ---
native v8natives.js:0: SyntaxError: Unexpected eval or arguments in strict mode

I don't see this test skipped yet.

[arv (Not doing code reviews), 2015-06-18 14:24:35]

On 2015/06/18 08:18:22, Michael Achenbach wrote:
> LGTM ~ comment. Just realized that our tryserver nosnap trybot doesn't run
> test262-es6. So ignore my try attempt.

Maybe I can add a nosnap bot to the CL description?

>
https://codereview.chromium.org/1190063002/diff/20001/test/test262-es6/test26...
> File test/test262-es6/test262-es6.status (right):
> 
>
https://codereview.chromium.org/1190063002/diff/20001/test/test262-es6/test26...
> test/test262-es6/test262-es6.status:600: 
> Are you sure these are all? Note, that the buildbot gui has a small
bug/feature
> and only shows max 10 failures due to scalability problems. Or are the 54
> failures in the stdio just an expansion of the many different variants? See:
>
http://build.chromium.org/p/client.v8/builders/V8%20Linux%20-%20nosnap/builds...
> 
> E.g.:
> === test262-es6/language/statements/variable/12.2.1-9-s ===
> --- stdout ---
> native v8natives.js:0: SyntaxError: Unexpected eval or arguments in strict
mode
> 
> I don't see this test skipped yet.

[arv (Not doing code reviews), 2015-06-18 14:24:49]

https://codereview.chromium.org/1190063002/diff/20001/test/test262-es6/test26...
File test/test262-es6/test262-es6.status (right):

https://codereview.chromium.org/1190063002/diff/20001/test/test262-es6/test26...
test/test262-es6/test262-es6.status:600: 
On 2015/06/18 08:18:22, Michael Achenbach wrote:
> Are you sure these are all? Note, that the buildbot gui has a small
bug/feature
> and only shows max 10 failures due to scalability problems. Or are the 54
> failures in the stdio just an expansion of the many different variants? See:
>
http://build.chromium.org/p/client.v8/builders/V8%20Linux%20-%20nosnap/builds...
> 
> E.g.:
> === test262-es6/language/statements/variable/12.2.1-9-s ===
> --- stdout ---
> native v8natives.js:0: SyntaxError: Unexpected eval or arguments in strict
mode
> 
> I don't see this test skipped yet.

I did look at the actual log. The waterfall does not even show the full path.

Also remember that we are running each entry 8 times.

I will however check the list in the log again.

[Michael Achenbach, 2015-06-18 16:34:40]

> Maybe I can add a nosnap bot to the CL description?

You can. But it won't help as there is no nosnap bot that runs test262-es6, I'd
need to add such a bot first...

[adamk, 2015-06-18 17:08:14]

lgtm

[arv (Not doing code reviews), 2015-06-19 18:10:01]

The CQ bit was checked by arv@chromium.org

[arv (Not doing code reviews), 2015-06-19 18:10:02]

The patchset sent to the CQ was uploaded after l-g-t-m from adamk@chromium.org,
machenbach@chromium.org
Link to the patchset: https://codereview.chromium.org/1190063002/#ps40001
(title: "Some eval tests are failing with nosnap")

[commit-bot: I haz the power, 2015-06-19 18:10:27]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1190063002/40001

[commit-bot: I haz the power, 2015-06-19 18:58:09]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2015-06-19 18:58:26]

Patchset 3 (id:??) landed as
https://crrev.com/0f502f679e339f90bd7e560ffff40c06e471eb40
Cr-Commit-Position: refs/heads/master@{#29164}