Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@adamgfraser
Copy link
Contributor

We are seeing some builds fail on CI with a message that no output has been received for 10 minutes. This indicates that something is going wrong but it is not simply a test timing out since that should be caught by the test framework and reported as a test failure. Initial work to identify the underlying cause.

@fsvehla
Copy link
Contributor

fsvehla commented Sep 27, 2020

Might be worth trying to double the Runtime’s executor size and see if it makes a difference - maybe it’s getting starved?

@adamgfraser
Copy link
Contributor Author

@fsvehla Good idea! I will try that after this run. 🙏

@adamgfraser
Copy link
Contributor Author

It looks like the CI failures we are seeing are being driven by an issue in ZIO.foreachParN where it can leak fibers. ZIO.foreachParN is called in the implementation of releaseAll in ZManaged and tests in ZIO Test are represented as managed effects. So some of the time when a test suite has terminated the test suite will try to clean everything up but will suspend indefinitely waiting for one of these fibers forked in an uninterruptible region to terminate. You can see the same thing in the preserves ordering of nested finalizers test for ZManaged#foreachParN, which will sometimes fail to terminate.

@adamgfraser
Copy link
Contributor Author

Superseded by #4253.

@adamgfraser adamgfraser deleted the ci branch September 28, 2020 02:08
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.

2 participants