27/04/2020 14:58, Aaron Conole: > Ferruh Yigit <ferruh.yi...@intel.com> writes: > > [1] Two issues reported > > a) ninja: build stopped: Error writing to build log: Disk quota > > exceeded. > > This occurs on some of the ARM64 builds. Travis is aware of the issue, > but don't seem urgently fixing it. :-/ I think we have a series > outstanding that should be applied to drop those builds for now.
I saw some "Disk quota exceeded" on x86 static builds. So I changed my mind, I am not sure dropping only Arm from Travis is a solution, even temporary. > > b) No output has been received in the last 10m0s, this potentially > > indicates a > > stalled build or something wrong with the build itself. > > This is a future enhancement I need to work on. When a build has jobs > that are stalled / errored, we need to restart them (at least once). Or > otherwise flag it. It especially happens when internal travis > infrastructure fails. Yes Travis infrastructure fails. Always. Travis is free, but it is not a reason to provide a randomly failing tool. I suggest switching to other platforms like OBS or our community lab, preferring the most reliable one.
