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

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: 4 comments 4 replies

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{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: 4 comments · 4 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
Nov 21, 2024

Replies: 4 comments 4 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