Skip to content

fix: increase report timeout to 3 minutes #135

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

Merged
merged 1 commit into from
Feb 11, 2020

Conversation

bahmutov
Copy link
Contributor

@bahmutov bahmutov requested a review from flotwig February 11, 2020 15:30
Copy link

@flotwig flotwig left a comment

Choose a reason for hiding this comment

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

still sad that this is necessary, time to fix the socket slowness at it's source ⚔️

@bahmutov
Copy link
Contributor Author

bahmutov commented Feb 11, 2020 via email

@bahmutov bahmutov merged commit f3f8de9 into master Feb 11, 2020
@bahmutov
Copy link
Contributor Author

🎉 This PR is included in version 1.12.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

rndmerle pushed a commit to rndmerle/code-coverage that referenced this pull request Apr 25, 2020
@emilyrohrbough emilyrohrbough deleted the longer-report-timeout-134 branch March 22, 2023 17:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Report timing out despite having __coverage__
2 participants