tree 748076851c56c37e8b8c1d949351d0d6c79d798a
parent 7a023f6acf8029e1ebe27d6d74ae3d447a78749b
author Googler <tedx@google.com> 1753411111 -0700
committer carmenchui@google.com <carmenchui@google.com> 1753984296 +0000
gpgsig -----BEGIN SSH SIGNATURE-----
 U1NIU0lHAAAAAQAAADMAAAALc3NoLWVkMjU1MTkAAAAgKGv7sLM+pEIDOAfTydgJW53atR
 dADtO6XLKIRKDwcvIAAAADZ2l0AAAAAAAAAAZzaGE1MTIAAABTAAAAC3NzaC1lZDI1NTE5
 AAAAQGBvr7fGBU43xz6E6w5jIY/0xcodSCbGxAWFpKKLnr/Hh3neC+C9RuxSnhsIEaTVla
 eHlJUPUFRsBor3uidmQQ0=
 -----END SSH SIGNATURE-----

Deflake jvm_flags_escaping_test

This CL changes the test behavior to grep the log for "unexpected EOF [...]".
The affected test sends a malformed JVM option with an unterminated quote pair to the java_binary wrapper, and then attempts to execute it.
It seems that somehow, bash's "syntax error" error message doesn't always get propagated all the way to the log. This seems like recent behavior and its root cause is currently unknown.

Luckily, the actual more important error message ("unexpected EOF") still appears earlier in the log, and we'll grep for that in addition.

New error message:
```
bazel-bin/test_untokenizable_jvm_flag_when_escaping_is_enabled/cannot_tokenize: line 231: unexpected EOF while looking for matching `''
```

Old error message:
```
bazel-bin/test_untokenizable_jvm_flag_when_escaping_is_enabled/cannot_tokenize: line 231: unexpected EOF while looking for matching `''
bazel-bin/test_untokenizable_jvm_flag_when_escaping_is_enabled/cannot_tokenize: line 250: syntax error: unexpected end of file
```

PiperOrigin-RevId: 786926665
Change-Id: I0c554693a096d336694e157f507eb331582baba6