Unable to release new emsdk due to closure-compiler Java errors on mac-arm64 builder

[sbc100]

Trying to release 6.0.0 in #1717 , we are seeing this error from the mac-arm64 builder:

shared:INFO: (Emscripten: Running sanity checks)
Error: LinkageError occurred while loading main class com.google.javascript.jscomp.CommandLineRunner
        java.lang.UnsupportedClassVersionError: com/google/javascript/jscomp/CommandLineRunner has been compiled by a more recent version of the Java Runtime (class file version 65.0), this version of the Java Runtime only recognizes class file versions up to 61.0
Error: LinkageError occurred while loading main class com.google.javascript.jscomp.CommandLineRunner
        java.lang.UnsupportedClassVersionError: com/google/javascript/jscomp/CommandLineRunner has been compiled by a more recent version of the Java Runtime (class file version 65.0), this version of the Java Runtime only recognizes class file versions up to 61.0
Command '['/Users/distiller/project/node/22.16.0_64bit/bin/node', '--max_old_space_size=8192', '/Users/distiller/project/upstream/emscripten/node_modules/.bin/google-closure-compiler', '--platform=java', '--version']' returned non-zero exit status 1.
emcc: error: closure compiler (/Users/distiller/project/node/22.16.0_64bit/bin/node --max_old_space_size=8192 /Users/distiller/project/upstream/emscripten/node_modules/.bin/google-closure-compiler --platform=java --version) did not execute properly!

[sbc100]

This error message is confusing to me because my understanding is that the closure compiler update should not include a native binary for macos-arm64, whereas the older version has an x86_64 binary.

My only guess is that the previously we using Rosetta to run the x86_64 binary? And now we have an arm64 that is somehow not running correctly?

[dschuff]

Yeah, I believe we were previously using Rosetta to run the x86_64 binary (because we didn't have Java installed). But now we should be running the native arm64 binary (and of course Java should work too, that's a separate issue).

[dschuff]

Could it have something to do with node? Are we sure that the node that's running here is ARM64 and not x86-64? (I notice it has "64bit" in the name and I would expect it to mention arm explicitly if it was that). I could imagine that since closure is installed via npm that an intel version of node could force it down the Java path rather than the arm64 path.

[sbc100]

I think I figured it out: https://chromium-review.git.corp.google.com/c/emscripten-releases/+/7896915