Strange warning about being unable to open a log file with non-ASCII characters in path #24444

clin1234 · 2024-11-21T19:48:23Z

clin1234
Nov 21, 2024

C:\Users\שזדס>bazelisk.exe info
WARNING: Invoking Bazel in batch mode since it is not invoked from within a workspace (below a directory having a WORKSPACE file).
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
java.util.logging.ErrorManager: 4: Failed to open log file
java.io.FileNotFoundException: c:\users\×©×××¡\_bazel_×©×××¡\u5mzpase\java.log.laptop-12hpo6t3.שזדס.log.java.20241121-144712.10532 (The system cannot find the path specified)
        at java.base/java.io.FileOutputStream.open0(Native Method)
        at java.base/java.io.FileOutputStream.open(Unknown Source)
        at java.base/java.io.FileOutputStream.<init>(Unknown Source)
        at com.google.devtools.build.lib.util.SimpleLogHandler$Output.open(SimpleLogHandler.java:741)
        at com.google.devtools.build.lib.util.SimpleLogHandler.openOutputIfNeeded(SimpleLogHandler.java:828)
        at com.google.devtools.build.lib.util.SimpleLogHandler.publish(SimpleLogHandler.java:433)
        at java.logging/java.util.logging.Logger.log(Unknown Source)
        at com.google.common.flogger.backend.system.AbstractBackend.log(AbstractBackend.java:76)
        at com.google.common.flogger.backend.system.SimpleLoggerBackend.log(SimpleLoggerBackend.java:31)
        at com.google.common.flogger.AbstractLogger.write(AbstractLogger.java:137)
        at com.google.common.flogger.LogContext.logImpl(LogContext.java:566)
        at com.google.common.flogger.LogContext.log(LogContext.java:686)
        at com.google.devtools.build.lib.analysis.BlazeVersionInfo.logVersionInfo(BlazeVersionInfo.java:65)
        at com.google.devtools.build.lib.analysis.BlazeVersionInfo.setBuildInfo(BlazeVersionInfo.java:80)
        at com.google.devtools.build.lib.bazel.Bazel.main(Bazel.java:95)

fmeum · 2024-11-21T22:46:03Z

fmeum
Nov 21, 2024
Collaborator

Could you set USE_BAZEL_VERSION to last_green and try again? A bunch of Unicode have been fixed in the last couple of days.

1 reply

clin1234 Nov 22, 2024
Author

To clarify, it's a warning, not an error

$ USE_BAZEL_VERSION=last_green bazelisk version
Bazelisk version: development
WARNING: Invoking Bazel in batch mode since it is not invoked from within a workspace (below a directory having a MODULE.bazel file).
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
java.util.logging.ErrorManager: 4: Failed to open log file
java.io.FileNotFoundException: c:\users\×©×××¡\_bazel_×©×××¡\u5mzpase\java.log.laptop-12hpo6t3.שזדס.log.java.20241121-210145.5760 (The system cannot find the path specified)
        at java.base/java.io.FileOutputStream.open0(Native Method)
        at java.base/java.io.FileOutputStream.open(Unknown Source)
        at java.base/java.io.FileOutputStream.<init>(Unknown Source)
        at com.google.devtools.build.lib.util.SimpleLogHandler$Output.open(SimpleLogHandler.java:741)
        at com.google.devtools.build.lib.util.SimpleLogHandler.openOutputIfNeeded(SimpleLogHandler.java:828)
        at com.google.devtools.build.lib.util.SimpleLogHandler.publish(SimpleLogHandler.java:433)
        at java.logging/java.util.logging.Logger.log(Unknown Source)
        at com.google.common.flogger.backend.system.AbstractBackend.log(AbstractBackend.java:76)
        at com.google.common.flogger.backend.system.SimpleLoggerBackend.log(SimpleLoggerBackend.java:31)
        at com.google.common.flogger.AbstractLogger.write(AbstractLogger.java:137)
        at com.google.common.flogger.LogContext.logImpl(LogContext.java:566)
        at com.google.common.flogger.LogContext.log(LogContext.java:686)
        at com.google.devtools.build.lib.analysis.BlazeVersionInfo.logVersionInfo(BlazeVersionInfo.java:65)
        at com.google.devtools.build.lib.analysis.BlazeVersionInfo.setBuildInfo(BlazeVersionInfo.java:80)
        at com.google.devtools.build.lib.bazel.Bazel.main(Bazel.java:103)
ERROR: While parsing option --client_env==C:=C:\Users\×©×××¡: Variable definitions must be in the form of a 'name=value' assignment

clin1234 · 2024-11-22T02:03:24Z

clin1234
Nov 22, 2024
Author

Also, every subcommand with last_green errors with ERROR: While parsing option --client_env==C:=C:\Users\×©×××¡: Variable definitions must be in the form of a 'name=value' assignment

1 reply

fmeum Nov 22, 2024
Collaborator

This has been fixed at HEAD: #24448

fmeum · 2024-11-22T12:51:11Z

fmeum
Nov 22, 2024
Collaborator

I'm working on getting this warning resolved.

0 replies

clin1234 · 2024-11-22T14:48:29Z

clin1234
Nov 22, 2024
Author

The second error is gone, but are last_green builds lacking version info on purpose?

$ USE_BAZEL_VERSION=last_green bazelisk version
2024/11/22 09:46:24 Using unreleased version at commit 26386ef113690815c7505252b861a89710852ac5
2024/11/22 09:46:24 Downloading https://storage.googleapis.com/bazel-builds/artifacts/windows/26386ef113690815c7505252b861a89710852ac5/bazel...
Downloading: 54 MB out of 54 MB (100%)
Bazelisk version: development
WARNING: Invoking Bazel in batch mode since it is not invoked from within a workspace (below a directory having a MODULE.bazel file).
Extracting Bazel installation...
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
java.util.logging.ErrorManager: 4: Failed to open log file
java.io.FileNotFoundException: c:\users\×©×××¡\_bazel_×©×××¡\u5mzpase\java.log.laptop-12hpo6t3.שזדס.log.java.20241122-094655.20976 (The system cannot find the path specified)
        at java.base/java.io.FileOutputStream.open0(Native Method)
        at java.base/java.io.FileOutputStream.open(Unknown Source)
        at java.base/java.io.FileOutputStream.<init>(Unknown Source)
        at com.google.devtools.build.lib.util.SimpleLogHandler$Output.open(SimpleLogHandler.java:741)
        at com.google.devtools.build.lib.util.SimpleLogHandler.openOutputIfNeeded(SimpleLogHandler.java:828)
        at com.google.devtools.build.lib.util.SimpleLogHandler.publish(SimpleLogHandler.java:433)
        at java.logging/java.util.logging.Logger.log(Unknown Source)
        at com.google.common.flogger.backend.system.AbstractBackend.log(AbstractBackend.java:76)
        at com.google.common.flogger.backend.system.SimpleLoggerBackend.log(SimpleLoggerBackend.java:31)
        at com.google.common.flogger.AbstractLogger.write(AbstractLogger.java:137)
        at com.google.common.flogger.LogContext.logImpl(LogContext.java:566)
        at com.google.common.flogger.LogContext.log(LogContext.java:686)
        at com.google.devtools.build.lib.analysis.BlazeVersionInfo.logVersionInfo(BlazeVersionInfo.java:65)
        at com.google.devtools.build.lib.analysis.BlazeVersionInfo.setBuildInfo(BlazeVersionInfo.java:80)
        at com.google.devtools.build.lib.bazel.Bazel.main(Bazel.java:103)
Build target: @@//src/main/java/com/google/devtools/build/lib/bazel:BazelServer
Build time: Thu Jan 01 00:00:00 1970 (0)
Build timestamp: Thu Jan 01 00:00:00 1970 (0)
Build timestamp as int: 0

2 replies

fmeum Nov 22, 2024
Collaborator

Yes, they are.

Wyverald Nov 22, 2024
Maintainer

I suppose they've always been this way (unstamped), but maybe we can stamp them with the commit hash at least? @meteorcloudy

clin1234 · 2024-12-23T17:12:42Z

clin1234
Dec 23, 2024
Author

Warning is still here:

$ USE_BAZEL_VERSION=last_green bazelisk version
2024/12/23 12:11:58 Using unreleased version at commit cf94101ebead07aea121d4e688f511b3f41997cb
2024/12/23 12:11:58 Downloading https://storage.googleapis.com/bazel-builds/artifacts/windows/cf94101ebead07aea121d4e688f511b3f41997cb/bazel...
Downloading: 54 MB out of 54 MB (100%)
Bazelisk version: development
WARNING: Invoking Bazel in batch mode since it is not invoked from within a workspace (below a directory having a MODULE.bazel file).
Extracting Bazel installation...
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
java.util.logging.ErrorManager: 4: Failed to open log file
java.io.FileNotFoundException: c:\users\×©×××¡\_bazel_×©×××¡\u5mzpase\java.log.laptop-12hpo6t3.שזדס.log.java.20241223-121209.11580 (The system cannot find the path specified)
        at java.base/java.io.FileOutputStream.open0(Native Method)
        at java.base/java.io.FileOutputStream.open(Unknown Source)
        at java.base/java.io.FileOutputStream.<init>(Unknown Source)
        at com.google.devtools.build.lib.util.SimpleLogHandler$Output.open(SimpleLogHandler.java:741)
        at com.google.devtools.build.lib.util.SimpleLogHandler.openOutputIfNeeded(SimpleLogHandler.java:828)
        at com.google.devtools.build.lib.util.SimpleLogHandler.publish(SimpleLogHandler.java:433)
        at java.logging/java.util.logging.Logger.log(Unknown Source)
        at com.google.common.flogger.backend.system.AbstractBackend.log(AbstractBackend.java:76)
        at com.google.common.flogger.backend.system.SimpleLoggerBackend.log(SimpleLoggerBackend.java:31)
        at com.google.common.flogger.AbstractLogger.write(AbstractLogger.java:137)
        at com.google.common.flogger.LogContext.logImpl(LogContext.java:566)
        at com.google.common.flogger.LogContext.log(LogContext.java:686)
        at com.google.devtools.build.lib.analysis.BlazeVersionInfo.logVersionInfo(BlazeVersionInfo.java:70)
        at com.google.devtools.build.lib.analysis.BlazeVersionInfo.setBuildInfo(BlazeVersionInfo.java:85)
        at com.google.devtools.build.lib.bazel.Bazel.main(Bazel.java:103)
Build target: @@//src/main/java/com/google/devtools/build/lib/bazel:BazelServer
Build time: Thu Jan 01 00:00:00 1970 (0)
Build timestamp: Thu Jan 01 00:00:00 1970 (0)
Build timestamp as int: 0

1 reply

fmeum Dec 23, 2024
Collaborator

This needs #24457, which is still in review and blocked on a rules_java update.

Milkow34 · 2025-01-09T20:54:03Z

Milkow34
Jan 9, 2025

The error indicates a path encoding issue due to non-ASCII characters in your Windows username (שזדס). Bazel fails to handle these characters properly, resulting in a FileNotFoundException for log files.

Solutions:

Change the Temp Directory Path:
- Set the TMP and TEMP environment variables to a path without non-ASCII characters (e.g., C:\Temp).
- Restart your terminal after changing the variables.
Run Bazel from a Different User Account:
- Create a new user with only ASCII characters in the username and run Bazel from that account.
Relocate the Bazel Output Base:
- Use the --output_user_root flag to specify a directory with an ASCII-only path:
```
bazelisk.exe --output_user_root=C:\bazel_output info
```

These steps should resolve the issue. Let me know if further assistance is needed!

0 replies

clin1234 · 2025-01-09T22:08:10Z

clin1234
Jan 9, 2025
Author


שזדס@LAPTOP-12HPO6T3 MINGW64 ~
$ USE_BAZEL_VERSION=rolling bazelisk version
2025/01/09 17:05:07 Downloading https://releases.bazel.build/9.0.0/rolling/9.0.0-pre.20241208.2/bazel-9.0.0-pre.20241208.2-windows-x86_64.exe...
Downloading: 54 MB out of 54 MB (100%)
Bazelisk version: development
WARNING: Invoking Bazel in batch mode since it is not invoked from within a workspace (below a directory having a MODULE.bazel file).
Extracting Bazel installation...
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
java.util.logging.ErrorManager: 4: Failed to open log file
java.io.FileNotFoundException: c:\users\×©×××¡\_bazel_×©×××¡\u5mzpase\java.log.laptop-12hpo6t3.שזדס.log.java.20250109-170515.23164 (The system cannot find the path specified)
        at java.base/java.io.FileOutputStream.open0(Native Method)
        at java.base/java.io.FileOutputStream.open(Unknown Source)
        at java.base/java.io.FileOutputStream.<init>(Unknown Source)
        at com.google.devtools.build.lib.util.SimpleLogHandler$Output.open(SimpleLogHandler.java:741)
        at com.google.devtools.build.lib.util.SimpleLogHandler.openOutputIfNeeded(SimpleLogHandler.java:828)
        at com.google.devtools.build.lib.util.SimpleLogHandler.publish(SimpleLogHandler.java:433)
        at java.logging/java.util.logging.Logger.log(Unknown Source)
        at com.google.common.flogger.backend.system.AbstractBackend.log(AbstractBackend.java:76)
        at com.google.common.flogger.backend.system.SimpleLoggerBackend.log(SimpleLoggerBackend.java:31)
        at com.google.common.flogger.AbstractLogger.write(AbstractLogger.java:137)
        at com.google.common.flogger.LogContext.logImpl(LogContext.java:566)
        at com.google.common.flogger.LogContext.log(LogContext.java:686)
        at com.google.devtools.build.lib.analysis.BlazeVersionInfo.logVersionInfo(BlazeVersionInfo.java:65)
        at com.google.devtools.build.lib.analysis.BlazeVersionInfo.setBuildInfo(BlazeVersionInfo.java:80)
        at com.google.devtools.build.lib.bazel.Bazel.main(Bazel.java:103)
Build label: 9.0.0-pre.20241208.2
Build target: @@//src/main/java/com/google/devtools/build/lib/bazel:BazelServer
Build time: Wed Dec 18 18:56:45 2024 (1734548205)
Build timestamp: 1734548205
Build timestamp as int: 1734548205

שזדס@LAPTOP-12HPO6T3 MINGW64 ~
$ USE_BAZEL_VERSION=stable bazelisk version
2025/01/09 17:05:26 could not download Bazel: could not resolve the version 'stable' to an actual version number: invalid version 'stable'

שזדס@LAPTOP-12HPO6T3 MINGW64 ~
$ USE_BAZEL_VERSION=latest bazelisk version
Bazelisk version: development
WARNING: Invoking Bazel in batch mode since it is not invoked from within a workspace (below a directory having a MODULE.bazel file).
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
java.util.logging.ErrorManager: 4: Failed to open log file
java.io.FileNotFoundException: c:\users\×©×××¡\_bazel_×©×××¡\u5mzpase\java.log.laptop-12hpo6t3.שזדס.log.java.20250109-170538.14412 (The system cannot find the path specified)
        at java.base/java.io.FileOutputStream.open0(Native Method)
        at java.base/java.io.FileOutputStream.open(Unknown Source)
        at java.base/java.io.FileOutputStream.<init>(Unknown Source)
        at com.google.devtools.build.lib.util.SimpleLogHandler$Output.open(SimpleLogHandler.java:741)
        at com.google.devtools.build.lib.util.SimpleLogHandler.openOutputIfNeeded(SimpleLogHandler.java:828)
        at com.google.devtools.build.lib.util.SimpleLogHandler.publish(SimpleLogHandler.java:433)
        at java.logging/java.util.logging.Logger.log(Unknown Source)
        at com.google.common.flogger.backend.system.AbstractBackend.log(AbstractBackend.java:76)
        at com.google.common.flogger.backend.system.SimpleLoggerBackend.log(SimpleLoggerBackend.java:31)
        at com.google.common.flogger.AbstractLogger.write(AbstractLogger.java:137)
        at com.google.common.flogger.LogContext.logImpl(LogContext.java:566)
        at com.google.common.flogger.LogContext.log(LogContext.java:686)
        at com.google.devtools.build.lib.analysis.BlazeVersionInfo.logVersionInfo(BlazeVersionInfo.java:65)
        at com.google.devtools.build.lib.analysis.BlazeVersionInfo.setBuildInfo(BlazeVersionInfo.java:80)
        at com.google.devtools.build.lib.bazel.Bazel.main(Bazel.java:103)
Build label: 8.0.0
Build target: @@//src/main/java/com/google/devtools/build/lib/bazel:BazelServer
Build time: Mon Dec 09 18:03:10 2024 (1733767390)
Build timestamp: 1733767390
Build timestamp as int: 1733767390

שזדס@LAPTOP-12HPO6T3 MINGW64 ~
$ USE_BAZEL_VERSION=last_green bazelisk version
Bazelisk version: development
WARNING: Invoking Bazel in batch mode since it is not invoked from within a workspace (below a directory having a MODULE.bazel file).
OpenJDK 64-Bit Server VM warning: Options -Xverify:none and -noverify were deprecated in JDK 13 and will likely be removed in a future release.
java.util.logging.ErrorManager: 4: Failed to open log file
java.io.FileNotFoundException: c:\users\×©×××¡\_bazel_×©×××¡\u5mzpase\java.log.laptop-12hpo6t3.שזדס.log.java.20250109-170643.23592 (The system cannot find the path specified)
        at java.base/java.io.FileOutputStream.open0(Native Method)
        at java.base/java.io.FileOutputStream.open(Unknown Source)
        at java.base/java.io.FileOutputStream.<init>(Unknown Source)
        at com.google.devtools.build.lib.util.SimpleLogHandler$Output.open(SimpleLogHandler.java:741)
        at com.google.devtools.build.lib.util.SimpleLogHandler.openOutputIfNeeded(SimpleLogHandler.java:828)
        at com.google.devtools.build.lib.util.SimpleLogHandler.publish(SimpleLogHandler.java:433)
        at java.logging/java.util.logging.Logger.log(Unknown Source)
        at com.google.common.flogger.backend.system.AbstractBackend.log(AbstractBackend.java:76)
        at com.google.common.flogger.backend.system.SimpleLoggerBackend.log(SimpleLoggerBackend.java:31)
        at com.google.common.flogger.AbstractLogger.write(AbstractLogger.java:137)
        at com.google.common.flogger.LogContext.logImpl(LogContext.java:566)
        at com.google.common.flogger.LogContext.log(LogContext.java:686)
        at com.google.devtools.build.lib.analysis.BlazeVersionInfo.logVersionInfo(BlazeVersionInfo.java:70)
        at com.google.devtools.build.lib.analysis.BlazeVersionInfo.setBuildInfo(BlazeVersionInfo.java:85)
        at com.google.devtools.build.lib.bazel.Bazel.main(Bazel.java:103)
Build target: @@//src/main/java/com/google/devtools/build/lib/bazel:BazelServer
Build time: Thu Jan 01 00:00:00 1970 (0)
Build timestamp: Thu Jan 01 00:00:00 1970 (0)
Build timestamp as int: 0

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Strange warning about being unable to open a log file with non-ASCII characters in path #24444

{{title}}

Replies: 7 comments 5 replies

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Strange warning about being unable to open a log file with non-ASCII characters in path #24444

clin1234 Nov 21, 2024

Replies: 7 comments · 5 replies

fmeum Nov 21, 2024 Collaborator

clin1234 Nov 22, 2024 Author

clin1234 Nov 22, 2024 Author

fmeum Nov 22, 2024 Collaborator

fmeum Nov 22, 2024 Collaborator

clin1234 Nov 22, 2024 Author

fmeum Nov 22, 2024 Collaborator

Wyverald Nov 22, 2024 Maintainer

clin1234 Dec 23, 2024 Author

fmeum Dec 23, 2024 Collaborator

Milkow34 Jan 9, 2025

Solutions:

clin1234 Jan 9, 2025 Author

clin1234
Nov 21, 2024

Replies: 7 comments 5 replies

fmeum
Nov 21, 2024
Collaborator

clin1234 Nov 22, 2024
Author

clin1234
Nov 22, 2024
Author

fmeum Nov 22, 2024
Collaborator

fmeum
Nov 22, 2024
Collaborator

clin1234
Nov 22, 2024
Author

fmeum Nov 22, 2024
Collaborator

Wyverald Nov 22, 2024
Maintainer

clin1234
Dec 23, 2024
Author

fmeum Dec 23, 2024
Collaborator

Milkow34
Jan 9, 2025

clin1234
Jan 9, 2025
Author