hiero-ledger / hiero-ledger/hiero-consensus-node

ci(bug): Fix workflow race condition

Open
#23,680 0 comments 0 reactions 1 assignee Claimed by @PavelSBorisov View on GitHub
Bug github_actions
Dominant language
Java
Stars
406
Forks
226
Avg merge
3d 4h
Merged PRs (30d)
210

Description

The error [here](https://github.com/hiero-ledger/hiero-consensus-node/actions/runs/22153755634/job/64052025875) is that the workflow deleted the xts-candidate tag, prepping to tag, around the same time [another instance](https://github.com/hiero-ledger/hiero-consensus-node/actions/runs/22153723324) of it tagged xts-candidate and pushed. When this workflow went to tag the commit as xts-candidate the tag existed again, causing a failure.

Re-running the job worked as a quick-bandage.

We need to investigate the race condition here and see if we can get around it.

Suggestion: Use github actions concurrency groups [[1]](https://docs.github.com/en/actions/how-tos/write-workflows/choose-when-workflows-run/control-workflow-concurrency) [[2]](https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax#concurrency)

---

In parallel (not related) add the workflow link to the slack report.

---

Definition of Done:
- [ ] Concurrency groups enabled (do not cancel in progress)
- [ ] Workflow link included in slack error report

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.