[test] Fix flag misconfig

--no-stress-flush-bytecode doesn't exist and should be
--no-stress-flush-code. Not supressing it means a tester could pass
--stress-flush-code and --no-flush-bytecode, which are contradictory and
will assert.

Bug: v8:12331
Cq-Include-Trybots: luci.v8.try:v8_numfuzz_dbg_ng,v8_numfuzz_ng
Change-Id: I6490271bcb11f5ea925eb8b65fbe0455c2dafeaf
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3233952Reviewed-by: Zhi An Ng <zhin@chromium.org>
Commit-Queue: Shu-yu Guo <syg@chromium.org>
Auto-Submit: Shu-yu Guo <syg@chromium.org>
Cr-Commit-Position: refs/heads/main@{#77483}

test/mjsunit/compiler/call-with-arraylike-or-spread-2.js

@@ -11,7 +11,7 @@
 
 // These tests do not work well if we flush the feedback vector, which causes
 // deoptimization.
-// Flags: --no-stress-flush-bytecode --no-flush-bytecode
+// Flags: --no-stress-flush-code --no-flush-bytecode
 
 // Tests for optimization of CallWithSpread and CallWithArrayLike.
 // This test is in a separate file because it invalidates protectors.

test/mjsunit/compiler/call-with-arraylike-or-spread-3.js

@@ -11,7 +11,7 @@
 
 // These tests do not work well if we flush the feedback vector, which causes
 // deoptimization.
-// Flags: --no-stress-flush-bytecode --no-flush-bytecode
+// Flags: --no-stress-flush-code --no-flush-bytecode
 
 // The test relies on optimizing/deoptimizing at predictable moments, so
 // it's not suitable for deoptimization fuzzing.

test/mjsunit/compiler/call-with-arraylike-or-spread-4.js

@@ -11,7 +11,7 @@
 
 // These tests do not work well if we flush the feedback vector, which causes
 // deoptimization.
-// Flags: --no-stress-flush-bytecode --no-flush-bytecode
+// Flags: --no-stress-flush-code --no-flush-bytecode
 
 // The test relies on optimizing/deoptimizing at predictable moments, so
 // this is not suitable for deoptimization fuzzing.

test/mjsunit/compiler/call-with-arraylike-or-spread-5.js

@@ -11,7 +11,7 @@
 
 // These tests do not work well if we flush the feedback vector, which causes
 // deoptimization.
-// Flags: --no-stress-flush-bytecode --no-flush-bytecode
+// Flags: --no-stress-flush-code --no-flush-bytecode
 
 // Some of the tests rely on optimizing/deoptimizing at predictable moments, so
 // this is not suitable for deoptimization fuzzing.

test/mjsunit/compiler/call-with-arraylike-or-spread-6.js

@@ -11,7 +11,7 @@
 
 // These tests do not work well if we flush the feedback vector, which causes
 // deoptimization.
-// Flags: --no-stress-flush-bytecode --no-flush-bytecode
+// Flags: --no-stress-flush-code --no-flush-bytecode
 
 // Some of the tests rely on optimizing/deoptimizing at predictable moments, so
 // this is not suitable for deoptimization fuzzing.

test/mjsunit/compiler/call-with-arraylike-or-spread-7.js

@@ -11,7 +11,7 @@
 
 // These tests do not work well if we flush the feedback vector, which causes
 // deoptimization.
-// Flags: --no-stress-flush-bytecode --no-flush-bytecode
+// Flags: --no-stress-flush-code --no-flush-bytecode
 
 // Some of the tests rely on optimizing/deoptimizing at predictable moments, so
 // this is not suitable for deoptimization fuzzing.

test/mjsunit/compiler/call-with-arraylike-or-spread.js

@@ -11,7 +11,7 @@
 
 // These tests do not work well if we flush the feedback vector, which causes
 // deoptimization.
-// Flags: --no-stress-flush-bytecode --no-flush-bytecode
+// Flags: --no-stress-flush-code --no-flush-bytecode
 
 // Some of the tests rely on optimizing/deoptimizing at predictable moments, so
 // this is not suitable for deoptimization fuzzing.