Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: add a total timeout of 30 minutes #1178

Merged
merged 1 commit into from
Dec 1, 2023

Conversation

JKRhb
Copy link
Member

@JKRhb JKRhb commented Nov 30, 2023

In the context of #1175, I noticed that the codecov step was somehow hanging for over 2 hours without causing the CI to fail. To address the issue, this PR proposes to add an additional "total" timeout value of 30 minutes for the whole job which should be enough to cover all runs that work as intended.

Copy link

codecov bot commented Nov 30, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (6c88392) 76.33% compared to head (6c13206) 76.33%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1178   +/-   ##
=======================================
  Coverage   76.33%   76.33%           
=======================================
  Files          80       80           
  Lines       16829    16829           
  Branches     1615     1615           
=======================================
  Hits        12847    12847           
  Misses       3952     3952           
  Partials       30       30           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Member

@danielpeintner danielpeintner left a comment

Choose a reason for hiding this comment

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

LGTM.

Do we still need

- name: Test with coverage report
run: npm run coverage:only
timeout-minutes: 10

Maybe yes to be able to detect problems earlier, right

@JKRhb
Copy link
Member Author

JKRhb commented Nov 30, 2023

LGTM.

Do we still need

- name: Test with coverage report
run: npm run coverage:only
timeout-minutes: 10

Maybe yes to be able to detect problems earlier, right

Yeah, exactly, would probably still be useful to have that time-limit as well :)

Copy link
Member

@relu91 relu91 left a comment

Choose a reason for hiding this comment

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

ok 👍

@relu91 relu91 merged commit 5c06db1 into eclipse-thingweb:master Dec 1, 2023
12 checks passed
@JKRhb JKRhb deleted the total-timeout branch December 1, 2023 16:36
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.

None yet

3 participants