Bazel builds stuck on v0.7.7

[rejuvenile]

v0.7.7, my Bazel builds are suddently stuck; the logs show:

Nov 20 13:42:07 docker[455230]:   2025-11-20T21:42:07.727082Z  INFO nativelink_scheduler::simple_scheduler: Oldest actions in state, items: ["stage=Queued last_transition=13h 41m 45s 228ms 419us 759ns client_operation_id=15d20408-0d1f-4321-a080-408d00583646 action_digest=0d248614e87fc86dfd0ed275f73b84ddfba39b31707e92f4566c898a2a1b7313-167", "stage=Queued last_transition=13h 41m 45s 228ms 361us 277n>
Nov 20 13:42:07 [455230]:     at nativelink-scheduler/src/simple_scheduler.rs:519
Nov 20 13:42:07 [455230]:     in nativelink_scheduler::simple_scheduler::simple_scheduler_task_worker_matching

[rejuvenile]

I restarted the scheduler, with seemingly no effect, but after restarting the workers as well, remote builds resumed.

[MarcusSorealheis]

Interesting. Thank you reporting. Are you able to delineate the order of operations holistically so we can look to reproduce and fix it?

[MarcusSorealheis]

I restarted the scheduler, with seemingly no effect, but after restarting the workers as well, remote builds resumed.

In this case, did you upgrade only one component of your nativelink deployment to 0.7.7?

[rejuvenile]

I restarted the scheduler, with seemingly no effect, but after restarting the workers as well, remote builds resumed.

In this case, did you upgrade only one component of your nativelink deployment to 0.7.7?

No, they were both running 0.7.7 from the start, and running days without issue beforehand. I’m not sure what it takes to repro. this but I’ll keep my eye out.

[MarcusSorealheis]

@rejuvenile I'm not sure if this issue has persisted since the restart. I expect the issue goes away in 0.7.8, which we released last week. Please keeps us posted and thank you again for the reporting and consistency.