Skip to content

New crash @ HEAD #27471

@keith

Description

@keith

Description of the bug:

INFO: Caught InterruptedException from ExecutionException for remote branch of external/rules_pycross++lock_file+modular_pip_lock_file_repo/deps/[email protected], which may cause a crash.
INFO: Caught InterruptedException from ExecutionException for remote branch of external/rules_pycross++lock_file+modular_pip_lock_file_repo/deps/[email protected], which may cause a crash.
INFO: Caught InterruptedException from ExecutionException for remote branch of external/rules_pycross++lock_file+modular_pip_lock_file_repo/deps/[email protected], which may cause a crash.
INFO: Caught InterruptedException from ExecutionException for remote branch of external/rules_pycross++lock_file+modular_pip_lock_file_repo/deps/[email protected], which may cause a crash.
Analyzing: 7000 targets (3605 packages loaded, 186060 targets and 4943 aspects configured)
[4,068 / 5,899] 2 / 332 tests; checking cached actions; last test: //bazel/pip/requirements:update_requirements_0_test


[4,068 / 5,899] 2 / 332 tests; checking cached actions; last test: //bazel/pip/requirements:update_requirements_0_test
FATAL: bazel crashed due to an internal error. Printing stack trace:
java.lang.AssertionError: Neither branch of utils/benchmarking/mammoth/cluster-configurations/built-overlays.tar completed. Local was cancelled and done and remote was not cancelled and done.
        at com.google.devtools.build.lib.dynamic.DynamicSpawnStrategy.waitBranches(DynamicSpawnStrategy.java:555)
        at com.google.devtools.build.lib.dynamic.DynamicSpawnStrategy.exec(DynamicSpawnStrategy.java:244)
        at com.google.devtools.build.lib.exec.SpawnStrategyResolver.exec(SpawnStrategyResolver.java:46)
        at com.google.devtools.build.lib.analysis.actions.SpawnAction.execute(SpawnAction.java:282)
        at com.google.devtools.build.lib.skyframe.SkyframeActionExecutor$ActionRunner.executeAction(SkyframeActionExecutor.java:1236)
        at com.google.devtools.build.lib.skyframe.SkyframeActionExecutor$ActionRunner.run(SkyframeActionExecutor.java:1141)
        at com.google.devtools.build.lib.skyframe.ActionExecutionState.runStateMachine(ActionExecutionState.java:166)
        at com.google.devtools.build.lib.skyframe.ActionExecutionState.getResultOrDependOnFuture(ActionExecutionState.java:95)
        at com.google.devtools.build.lib.skyframe.SkyframeActionExecutor.executeAction(SkyframeActionExecutor.java:652)
        at com.google.devtools.build.lib.skyframe.ActionExecutionFunction.checkCacheAndExecuteIfNeeded(ActionExecutionFunction.java:780)
        at com.google.devtools.build.lib.skyframe.ActionExecutionFunction.computeInternal(ActionExecutionFunction.java:345)
        at com.google.devtools.build.lib.skyframe.ActionExecutionFunction.compute(ActionExecutionFunction.java:202)
        at com.google.devtools.build.skyframe.AbstractParallelEvaluator$Evaluate.run(AbstractParallelEvaluator.java:471)
        at com.google.devtools.build.lib.concurrent.AbstractQueueVisitor$WrappedRunnable.run(AbstractQueueVisitor.java:435)
        at java.base/java.util.concurrent.ForkJoinTask$RunnableExecuteAction.compute(Unknown Source)
        at java.base/java.util.concurrent.ForkJoinTask$RunnableExecuteAction.compute(Unknown Source)
        at java.base/java.util.concurrent.ForkJoinTask$InterruptibleTask.exec(Unknown Source)
        at java.base/java.util.concurrent.ForkJoinTask.doExec(Unknown Source)
        at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(Unknown Source)
        at java.base/java.util.concurrent.ForkJoinPool.runWorker(Unknown Source)
        at java.base/java.util.concurrent.ForkJoinWorkerThread.run(Unknown Source)

Not sure if the exceptions above are related to the final trace, but I believe this is the first time I've seen this

Which category does this issue belong to?

No response

What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

No response

Which operating system are you running Bazel on?

No response

What is the output of bazel info release?

9df37fd

If bazel info release returns development version or (@non-git), tell us how you built Bazel.

No response

What's the output of git remote get-url origin; git rev-parse HEAD ?


If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.

No response

Have you found anything relevant by searching the web?

No response

Any other information, logs, or outputs that you want to share?

No response

Metadata

Metadata

Assignees

Labels

P1I'll work on this now. (Assignee required)type: bug

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions