Skip to content

Broken Release Action? #1479

@hoeck

Description

@hoeck

After merging a PR I noticed that the release action fails when trying to commit the benchmark results (after having succeeded in committing the results of another node version of the matrix build).
So the results for a new or updated library are only shown for those node versions where the commit was successful. At least for a few hours until renovate-bot triggers a new release.

Running the benchmarks locally, everything runs fine. A single JSON file is written and it should not cause problems when committing that.

Then I noticed that other runs of the release action also (randomly?) failed.

Without digging deeper into the reason I'd suggest replacing the aged https://github.com/github-actions-x commit action with something that looks a bit more maintained, e.g. https://github.com/EndBug/add-and-commit

To me this error smells like some race condition that maybe happens when there are too many commits going on in parallel?

Any ideas, suggestions or objections?

If not I would like to try changing the release workflow to use said commit action and see if it helps.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions