| commit | eff04427e1bccd43baefede3a2d188d873461c9f | [log] [tgz] |
|---|---|---|
| author | Googler <tedx@google.com> | Thu Jul 24 19:38:31 2025 -0700 |
| committer | carmenchui@google.com <carmenchui@google.com> | Thu Jul 31 17:51:36 2025 +0000 |
| tree | 748076851c56c37e8b8c1d949351d0d6c79d798a | |
| parent | 7a023f6acf8029e1ebe27d6d74ae3d447a78749b [diff] |
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
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
