gerrit master / 3.14.-rc4 build failure

[Michael Nazzareno Trimarchi]

Hi all

I don't know if my setup is wrong, but I can compile gerrit up to 3.13.5 and after that I get

se --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
[!] RollupError: bazel-out/k8-fastbuild/bin/polygerrit-ui/app/_pg_ts_out/elements/shared/gr-marked-element/gr-marked-element.js (14:17): "Renderer" is not exported by "../../../../../../../../../node_modules/marked/lib/marked.js", imported by "bazel-out/k8-fastbuild/bin/polygerrit-ui/app/_pg_ts_out/elements/shared/gr-marked-element/gr-marked-element.js".
https://rollupjs.org/troubleshooting/#error-name-is-not-exported-by-module
bazel-out/k8-fastbuild/bin/polygerrit-ui/app/_pg_ts_out/elements/shared/gr-marked-element/gr-marked-element.js (14:17)
12: import { css, html, LitElement } from 'lit';
13: import { customElement, property, queryAssignedElements, } from 'lit/decorators.js';
14: import { Marked, Renderer, Tokenizer } from 'marked';

To clarify, I want to recompile to test some Polygerrit and AI changes. I've never encountered this problem before, and I suspect that if it appears in CI, it's something you are already aware of. Any help is appreciated

Michael

[Daniele Sassoli]

Hi Michael,

What command are you running?
 

Michael

[Michael Nazzareno Trimarchi]

Hi Daniele

bazel build gerrit

Michael

 

 

Michael

--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en

---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/repo-discuss/903d0985-582f-4525-bc90-605a354b0b13n%40googlegroups.com.

--

Michael Nazzareno Trimarchi
Co-Founder & Chief Executive Officer
M. +39 347 913 2170
mic...@amarulasolutions.com
__________________________________

Amarula Solutions BV

Joop Geesinkweg 125, 1114 AB, Amsterdam, NL
T. +31 (0)85 111 9172
in...@amarulasolutions.com
www.amarulasolutions.com

[Daniele Sassoli]

On Wednesday, 22 April 2026 at 12:46:54 UTC+1 mic...@amarulasolutions.com wrote:

Hi Daniele

On Wed, Apr 22, 2026 at 1:44 PM Daniele Sassoli <daniele...@gmail.com> wrote:

Hi Michael,

On Wednesday, 22 April 2026 at 07:37:29 UTC+1 mic...@amarulasolutions.com wrote:

Hi all

I don't know if my setup is wrong, but I can compile gerrit up to 3.13.5 and after that I get

se --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
[!] RollupError: bazel-out/k8-fastbuild/bin/polygerrit-ui/app/_pg_ts_out/elements/shared/gr-marked-element/gr-marked-element.js (14:17): "Renderer" is not exported by "../../../../../../../../../node_modules/marked/lib/marked.js", imported by "bazel-out/k8-fastbuild/bin/polygerrit-ui/app/_pg_ts_out/elements/shared/gr-marked-element/gr-marked-element.js".
https://rollupjs.org/troubleshooting/#error-name-is-not-exported-by-module
bazel-out/k8-fastbuild/bin/polygerrit-ui/app/_pg_ts_out/elements/shared/gr-marked-element/gr-marked-element.js (14:17)
12: import { css, html, LitElement } from 'lit';
13: import { customElement, property, queryAssignedElements, } from 'lit/decorators.js';
14: import { Marked, Renderer, Tokenizer } from 'marked';

To clarify, I want to recompile to test some Polygerrit and AI changes. I've never encountered this problem before, and I suspect that if it appears in CI, it's something you are already aware of. Any help is appreciated

What command are you running?

bazel build gerrit

There's been a lot of changes in the build infrastructure lately.
Its probably worth you trying to use bazelisk, rather than bazel, is a safer bet. Same command, just bazelisk, not bazel.

Let me know if that helps.

[Michael Nazzareno Trimarchi]

Hi Daniele

First of all thank you. Some more information below

On Wed, Apr 22, 2026 at 1:48 PM Daniele Sassoli <daniele...@gmail.com> wrote:

On Wednesday, 22 April 2026 at 12:46:54 UTC+1 mic...@amarulasolutions.com wrote:

Hi Daniele

On Wed, Apr 22, 2026 at 1:44 PM Daniele Sassoli <daniele...@gmail.com> wrote:

Hi Michael,

On Wednesday, 22 April 2026 at 07:37:29 UTC+1 mic...@amarulasolutions.com wrote:

Hi all

I don't know if my setup is wrong, but I can compile gerrit up to 3.13.5 and after that I get

se --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging
[!] RollupError: bazel-out/k8-fastbuild/bin/polygerrit-ui/app/_pg_ts_out/elements/shared/gr-marked-element/gr-marked-element.js (14:17): "Renderer" is not exported by "../../../../../../../../../node_modules/marked/lib/marked.js", imported by "bazel-out/k8-fastbuild/bin/polygerrit-ui/app/_pg_ts_out/elements/shared/gr-marked-element/gr-marked-element.js".
https://rollupjs.org/troubleshooting/#error-name-is-not-exported-by-module
bazel-out/k8-fastbuild/bin/polygerrit-ui/app/_pg_ts_out/elements/shared/gr-marked-element/gr-marked-element.js (14:17)
12: import { css, html, LitElement } from 'lit';
13: import { customElement, property, queryAssignedElements, } from 'lit/decorators.js';
14: import { Marked, Renderer, Tokenizer } from 'marked';

To clarify, I want to recompile to test some Polygerrit and AI changes. I've never encountered this problem before, and I suspect that if it appears in CI, it's something you are already aware of. Any help is appreciated

What command are you running?

bazel build gerrit

There's been a lot of changes in the build infrastructure lately.
Its probably worth you trying to use bazelisk, rather than bazel, is a safer bet. Same command, just bazelisk, not bazel.

bazelisk --version

bazel 8.6.0

Command used to build

bazelisk build gerrit

commit 2f6e11791e9f11704009e1f387a81d9c4368676e (HEAD, tag: v3.14.0-rc4)

Just before build to ensure everything is clean and nothing is broken

git clean -ffdx

git submodule update

rm -rf ~/.gerritcodereviw

rm -rf ~/.cache/bazel*

Full log

bazelisk build gerrit
2026/04/22 14:04:12 Downloading https://releases.bazel.build/8.6.0/release/bazel-8.6.0-linux-x86_64...
2026/04/22 14:04:12 Skipping basic authentication for releases.bazel.build because no credentials found in /home/panicking/.netrc
Downloading: 61 MB out of 61 MB (100%)
Extracting Bazel installation...
Starting local Bazel server (8.6.0) and connecting to it...
INFO: Invocation ID: a7c627a3-2064-413c-bf7c-4e094cd56cf0
INFO: Options provided by the client:
  Inherited 'common' options: --isatty=1 --terminal_columns=230
INFO: Reading rc options for 'build' from /home/panicking/work/michael/gerrit/.bazelrc:
  Inherited 'common' options: --enable_workspace --enable_bzlmod --lockfile_mode=error --incompatible_enable_proto_toolchain_resolution --@protobuf//bazel/toolchains:prefer_prebuilt_protoc --@com_googlesource_gerrit_bazlets//flags:in_gerrit_tree=true --incompatible_disallow_struct_provider_syntax=false --incompatible_disallow_empty_glob=false
INFO: Reading rc options for 'build' from /home/panicking/work/michael/gerrit/.bazelrc:
  'build' options: --workspace_status_command=python3 ./tools/workspace_status.py --repository_cache=~/.gerritcodereview/bazel-cache/repository --action_env=PATH --disk_cache=~/.gerritcodereview/bazel-cache/cas --java_language_version=21 --java_runtime_version=remotejdk_21 --tool_java_language_version=21 --tool_java_runtime_version=remotejdk_21 --incompatible_strict_action_env --announce_rc
WARNING: WORKSPACE support will be removed in Bazel 9 (late 2025), please migrate to Bzlmod, see https://bazel.build/external/migration.
WARNING: Download from https://repo1.maven.org/maven2/com/googlecode/prolog-cafe/prolog-compiler/1.4.4/prolog-compiler-1.4.4-sources.jar failed: class java.io.FileNotFoundException GET returned 404 Not Found
WARNING: Download from https://repo1.maven.org/maven2/com/googlecode/prolog-cafe/prolog-runtime/1.4.4/prolog-runtime-1.4.4-sources.jar failed: class java.io.FileNotFoundException GET returned 404 Not Found
WARNING: Download from https://repo1.maven.org/maven2/com/googlecode/prolog-cafe/prolog-cafeteria/1.4.4/prolog-cafeteria-1.4.4-sources.jar failed: class java.io.FileNotFoundException GET returned 404 Not Found
WARNING: Download from https://repo1.maven.org/maven2/com/googlecode/prolog-cafe/prolog-runtime/1.4.4/prolog-runtime-1.4.4.jar failed: class java.io.FileNotFoundException GET returned 404 Not Found
WARNING: Download from https://repo1.maven.org/maven2/com/google/gitiles/blame-cache/1.6.0/blame-cache-1.6.0-sources.jar failed: class java.io.FileNotFoundException GET returned 404 Not Found
WARNING: Download from https://repo1.maven.org/maven2/com/google/gitiles/blame-cache/1.6.0/blame-cache-1.6.0.jar failed: class java.io.FileNotFoundException GET returned 404 Not Found
WARNING: Download from https://repo1.maven.org/maven2/com/googlecode/prolog-cafe/prolog-cafeteria/1.4.4/prolog-cafeteria-1.4.4.jar failed: class java.io.FileNotFoundException GET returned 404 Not Found
WARNING: Download from https://repo1.maven.org/maven2/com/googlecode/prolog-cafe/prolog-compiler/1.4.4/prolog-compiler-1.4.4.jar failed: class java.io.FileNotFoundException GET returned 404 Not Found
WARNING: Download from https://repo1.maven.org/maven2/com/googlecode/prolog-cafe/prolog-io/1.4.4/prolog-io-1.4.4.jar failed: class java.io.FileNotFoundException GET returned 404 Not Found
WARNING: Download from https://repo1.maven.org/maven2/com/googlecode/prolog-cafe/prolog-io/1.4.4/prolog-io-1.4.4-sources.jar failed: class java.io.FileNotFoundException GET returned 404 Not Found
INFO: Analyzed target //:gerrit (529 packages loaded, 25974 targets configured).
ERROR: /home/panicking/work/michael/gerrit/polygerrit-ui/app/BUILD:91:18: Bundling JavaScript polygerrit-ui/app/gr-app-bundle-js.js [rollup] failed: (Exit 1): rollup-bin.sh failed: error executing Rollup command (from target //polygerrit-ui/app:gr-app-bundle-js) bazel-out/k8-opt-exec-ST-d57f47055a04/bin/tools/node_tools/rollup-bin.sh '--bundleConfigAsCjs=true' bazel-out/k8-fastbuild/bin/polygerrit-ui/app/_pg_ts_out/elements/gr-app-entry-point.js --output.file ... (remaining 10 arguments skipped)

Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root for debugging

[!] RollupError: bazel-out/k8-fastbuild/bin/polygerrit-ui/app/_pg_ts_out/elements/shared/gr-marked-element/gr-marked-element.js (14:17): "Renderer" is not exported by "../../../../../../../../../node_modules/marked/lib/marked.js", imported by "bazel-out/k8-fastbuild/bin/polygerrit-ui/app/_pg_ts_out/elements/shared/gr-marked-element/gr-marked-element.js".
https://rollupjs.org/troubleshooting/#error-name-is-not-exported-by-module
bazel-out/k8-fastbuild/bin/polygerrit-ui/app/_pg_ts_out/elements/shared/gr-marked-element/gr-marked-element.js (14:17)
12: import { css, html, LitElement } from 'lit';
13: import { customElement, property, queryAssignedElements, } from 'lit/decorators.js';
14: import { Marked, Renderer, Tokenizer } from 'marked';

                     ^
15: import { sanitizeHtml, setElementInnerHtml, } from '../../../utils/inner-html-util';
16: /**
    at getRollupError (/home/panicking/.cache/bazel/_bazel_panicking/eccdf9677186511cfee47397edd86022/sandbox/processwrapper-sandbox/312/execroot/_main/tools/node_tools/node_modules/rollup/dist/shared/parseAst.js:285:41)
    at Object.error (/home/panicking/.cache/bazel/_bazel_panicking/eccdf9677186511cfee47397edd86022/sandbox/processwrapper-sandbox/312/execroot/_main/tools/node_tools/node_modules/rollup/dist/shared/parseAst.js:281:42)
    at Module.error (/home/panicking/.cache/bazel/_bazel_panicking/eccdf9677186511cfee47397edd86022/sandbox/processwrapper-sandbox/312/execroot/_main/tools/node_tools/node_modules/rollup/dist/shared/rollup.js:18346:28)
    at Module.traceVariable (/home/panicking/.cache/bazel/_bazel_panicking/eccdf9677186511cfee47397edd86022/sandbox/processwrapper-sandbox/312/execroot/_main/tools/node_tools/node_modules/rollup/dist/shared/rollup.js:18795:29)
    at ModuleScope.findVariable (/home/panicking/.cache/bazel/_bazel_panicking/eccdf9677186511cfee47397edd86022/sandbox/processwrapper-sandbox/312/execroot/_main/tools/node_tools/node_modules/rollup/dist/shared/rollup.js:16458:39)
    at ChildScope.findVariable (/home/panicking/.cache/bazel/_bazel_panicking/eccdf9677186511cfee47397edd86022/sandbox/processwrapper-sandbox/312/execroot/_main/tools/node_tools/node_modules/rollup/dist/shared/rollup.js:9338:38)
    at ClassBodyScope.findVariable (/home/panicking/.cache/bazel/_bazel_panicking/eccdf9677186511cfee47397edd86022/sandbox/processwrapper-sandbox/312/execroot/_main/tools/node_tools/node_modules/rollup/dist/shared/rollup.js:9338:38)
    at ChildScope.findVariable (/home/panicking/.cache/bazel/_bazel_panicking/eccdf9677186511cfee47397edd86022/sandbox/processwrapper-sandbox/312/execroot/_main/tools/node_tools/node_modules/rollup/dist/shared/rollup.js:9338:38)
    at ChildScope.findVariable (/home/panicking/.cache/bazel/_bazel_panicking/eccdf9677186511cfee47397edd86022/sandbox/processwrapper-sandbox/312/execroot/_main/tools/node_tools/node_modules/rollup/dist/shared/rollup.js:9338:38)
    at FunctionScope.findVariable (/home/panicking/.cache/bazel/_bazel_panicking/eccdf9677186511cfee47397edd86022/sandbox/processwrapper-sandbox/312/execroot/_main/tools/node_tools/node_modules/rollup/dist/shared/rollup.js:9338:38)


Target //:gerrit failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 181.591s, Critical Path: 95.26s
INFO: 500 processes: 188 internal, 285 processwrapper-sandbox, 27 worker.
ERROR: Build did NOT complete successfully

Michael

To view this discussion visit https://groups.google.com/d/msgid/repo-discuss/4b43704a-8613-4a7a-8562-93c337bf7ac1n%40googlegroups.com.

[Daniele Sassoli]

Does running "bazelisk clean --expunge" and then retrying help?

[Michael Nazzareno Trimarchi]

Hi Daniele

Nope, ok. I will check on some other setup (like not ubuntu 26.04)

Michael 

[Daniele Sassoli]

Interesting, I had an issue with the 3.14 build too, but the clean fixed it.
Let me know how you get on.

[Michael Nazzareno Trimarchi]

Hi Daniele

For now, I have solved it this way:

bazelisk build release --spawn_strategy=local
INFO: Invocation ID: 134feb4d-ebde-4395-bf5c-472e7a02924b

INFO: Options provided by the client:
  Inherited 'common' options: --isatty=1 --terminal_columns=230
INFO: Reading rc options for 'build' from /home/panicking/work/michael/gerrit/.bazelrc:
  Inherited 'common' options: --enable_workspace --enable_bzlmod --lockfile_mode=error --incompatible_enable_proto_toolchain_resolution --@protobuf//bazel/toolchains:prefer_prebuilt_protoc --@com_googlesource_gerrit_bazlets//flags:in_gerrit_tree=true --incompatible_disallow_struct_provider_syntax=false --incompatible_disallow_empty_glob=false
INFO: Reading rc options for 'build' from /home/panicking/work/michael/gerrit/.bazelrc:
  'build' options: --workspace_status_command=python3 ./tools/workspace_status.py --repository_cache=~/.gerritcodereview/bazel-cache/repository --action_env=PATH --disk_cache=~/.gerritcodereview/bazel-cache/cas --java_language_version=21 --java_runtime_version=remotejdk_21 --tool_java_language_version=21 --tool_java_runtime_version=remotejdk_21 --incompatible_strict_action_env --announce_rc

INFO: Analyzed target //:release (0 packages loaded, 0 targets configured).
INFO: Found 1 target...
Target //:release up-to-date:
  bazel-bin/release.war
  bazel-bin/release.war.jars.txt
  bazel-bin/release.war.entries.txt
INFO: Elapsed time: 18.322s, Critical Path: 18.00s
INFO: 4 processes: 26 action cache hit, 1 internal, 3 local.
INFO: Build completed successfully, 4 total actions

Change the strategy of bazel sandboxing (not optimale but working way)

Michael

[Michael Nazzareno Trimarchi]

Hi all

I found out the problem and was connected to my exported environment that mess up

the compilation environment of bazel. Some of my tools was taken from some environment installed but was there for some historical reason. I have cleanup my user

PATH and now sanboxing is working as it should be

Michael