shuppy
Replied in [this comment](https://github.com/servo/servo/issues/33486#issuecomment-2359851826), but not longer pursuing this right now.
> I think this can be done as a step that obtains that using REST and then sets steps output to response. Then, next step can use this output in...
> Also do note that there are [workflow call nesting limits](https://docs.github.com/en/actions/sharing-automations/reusing-workflows#nesting-reusable-workflows). Yeah, we touch the limit in this patch with `try` and `try-label` → `dispatch-workflow` → `windows-auto` → `windows`, but...
> Can't we use [job concurrency](https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/control-the-concurrency-of-workflows-and-jobs) for this? That’s what we do in this patch :)
Also to fix after the weekend, the `build-result` job [fails](https://github.com/delan/servo/actions/runs/10417638807/job/28854756911) when the `self-hosted` job is cancelled: ```yaml - name: Success if: ${{ !contains(needs.*.result, 'failure') && !contains(needs.*.result, 'cancelled') }} run: exit...
It looks like a “cancelled” result in the `self-hosted` job [infects the whole workflow run](https://github.com/delan/servo/actions/runs/10446746640), even if we [fix the check](https://github.com/delan/servo/commit/8c054cac3ddfa22f04a5d1e77dc057c4140f375b#diff-7829468e86c1cc5d5133195b5cb48e1ff6c75e3e9203777f6b2e379d9e4882b3R55) in the `main` workflow and set the job to...
> So I think `contains(needs.*.result, 'failure') || cancelled()` should be enough. Great, [that works too](https://github.com/delan/servo/commit/949758b69b5dc7caa5c9224f9575b5fa5555aec7)! But the `self-hosted` job being cancelled [still makes the whole workflow cancelled](https://github.com/delan/servo/actions/runs/10450947049/job/28936341577), and I can’t...
> (Although there is still some small race, but I do not think it would be problematic in practice) I’m not so sure. The consequence of a race is that...
> maybe adding result job to windows-auto (that will handle cancellation of self-hostet runner correctly) will cause for main to only pick up result of result job in windows-auto? Already...
> Maybe we can assign labels to unlabeled runners (this would be uniq_id) in decision task (using job concurrency to only have one job doing labeling at time), and then...