Closed daviddias closed 5 years ago
Note: part of this was caused by go-ipfs not cleaning up after itself: https://github.com/ipfs/testing/issues/118, https://github.com/ipfs/testing/issues/70. We've improved the situation but I'm not sure if it's fixed.
Duplicate of https://github.com/ipfs/testing/issues/118, closing
Coincidentally I was just separately saying to @VictorBjelkholm that any reason that CI fails because of something other than the tests failing is really bad. It’s super frustrating and time consuming for the developer and wastes resources.
Off the top of my head the big issues are:
It also really sucks when this happens for contributors as they can’t just restart a build. The fact that this effects the community as well as PL is really bad.
These are the current open issues for addressing these problems:
What is the time sink?
Jenkins keeps running out of Space
How do you think it can be solved?
Get bigger machine or develop a post CI task that cleans after
How many hours per week do you waste thanks to this time sink?
Sum of hours per multiple contributor, easily 40 or more.
How important do you think this is to fix?
It is a big PITA