Skip to content

Conversation

@lslezak
Copy link
Contributor

@lslezak lslezak commented May 14, 2025

Problem

  • The Coveralls reporting step in the GitHub Actions got stuck (example job)
  • And because the default timeout is 6 hours then the CI was stuck for 6 hours
  • The number of the assigned Action runners is limited so after reaching the limit new CI actions were not started and were waiting until some previous job is finished.

Debugging

Solution

  • Enable back the code coverage reporting in the web frontend
  • Configure git so a different owner is OK (this was not the root of the problem in the end but this could cause troubles elsewhere later so I'm keeping this change anyway.)
  • Run the coverage actions outside container, run them in the Ubuntu host directly
    (That's a bit tricky, if a job runs in a container then all steps run in the container, you cannot run a command outside the container. The workaround is to define a dependent job which runs outside the container and pass the coverage data as an artifact which is uploaded/downloaded.)
  • Decrease the timeout, explicitly set 1 hour for CI and 20 minutes for Coveralls to not block for too long if the job gets stuck for whatever reason.
  • Limit the permissions as suggested by the GitHub scanner to only read the repository content.

Testing

  • Works fine, see the green marks for this pull request, the Coveralls reports were correctly sent.

Copy link
Contributor

@joseivanlopez joseivanlopez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@lslezak lslezak merged commit 2e436fc into master May 14, 2025
15 checks passed
@lslezak lslezak deleted the coveralls_config branch May 14, 2025 16:04
@imobachgs imobachgs mentioned this pull request May 26, 2025
imobachgs added a commit that referenced this pull request May 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants