[wasm] Add guard regions to end of WebAssembly.Memory buffers

test/mjsunit/mjsunit.status

Index: test/mjsunit/mjsunit.status
diff --git a/test/mjsunit/mjsunit.status b/test/mjsunit/mjsunit.status
index 0b395513ab226cffe241a56bf83603304535f66f..64b4b3030d60b466dd7a43ef41d04f29ee565ee6 100644
--- a/test/mjsunit/mjsunit.status
+++ b/test/mjsunit/mjsunit.status
@@ -702,4 +702,22 @@
   'whitespaces': [SKIP],
 }],  # variant == asm_wasm
 
+['variant == wasm_traps', {
+  # Skip stuff uninteresting for wasm traps
+  'bugs/*': [SKIP],
+  'compiler/*': [SKIP],
+  'es6/*': [SKIP],
+  'es7/*': [SKIP],
+  'es8/*': [SKIP],
+  'harmony/*': [SKIP],
+  'ignition/*': [SKIP],
+  'lithium/*': [SKIP],
+  'third_party/*': [SKIP],
+  'tools/*': [SKIP],
+  'apply': [SKIP],
+  'math-*': [SKIP],
+  'unicode-test': [SKIP],
+  'whitespaces': [SKIP],
+}],  # variant == wasm_traps
+

[Michael Achenbach, 2016/11/04 17:52:54]

What about cctest?
https://cs.chromium.org/chromium/src/v8/test/cctest/cctest.status?q=test/ccte...

Please also check the newer suites for debugger and inspector. They might miss
the skips for asm_wasm as well.

[Michael Achenbach, 2016/11/08 07:51:08]

Please also take a look at cctest as mentioned above.

[Eric Holk, 2016/11/08 23:58:15]

I originally had blocked cctests too, but I decided to enable them because they
exercise some Wasm paths that the JS tests don't and that were affected by this
change. Enabling the cctests revealed a few bugs in this change.

I added skips for inspect and debugger though.

[Eric Holk, 2016/11/08 23:58:15]

Is there a way to invert one of the skip patterns? It'd be nice to be able to
say something like "skip all the cctests that do not has wasm in their name."

[Michael Achenbach, 2016/11/09 08:05:32]

No, this feature doesn't exist. We're misusing the status files since a while
now for all kinds of things. The original intent was to temporarily silence a
small number of bugs.

I'm afraid that all cctests with the new variant will add significant runtime
and we'll run into timeouts on the bots. Why is the other wasm variant not using
cctest? If you keep it activated, could you please once run test just cctest
with linux debug and wasm_traps only and measure the time of the slowest tests,
e.g. tools/run-tests.py --variant=wasm_traps cctest --time

Then please skip the slowest tests if there are significant slow ones.

 ]