DAFFODIL-1908 tracks this issue. It isn't specific to TravisCI, but certain environments seem to make it easier to trigger. I haven't seen it in a while on my system. Best guess is some kind of non-thread-safe code when compiling schemas, but I don't think any one has been able to track it down so far.
TravisCI lets you retrigger a build--I usually do that when I see random failures just to make sure all the tests pass. I've recently seen what appear to be network issues and dependencies fail to download. - Steve On 08/15/2018 01:06 PM, Mike Beckerle wrote: > So the travis CI build failed for a recent PR of mine. > > > It's complaining about file > daffodil-test/src/test/resources/org/apache/daffodil/section07/namespaces/multi_base_09.dfdl.xsd > > > I haven't touched this file. It has not been modified in a long time I > believe. > > > Perhaps unique in our system, this file is UTF-16BE character set encoding. > > > Other travis CI builds aren't tripping over this; but mine is getting: > > Schema Definition Error: No XML Node could be loaded from > URISchemaSource(file:/home/travis/build/apache/incubator-daffodil/daffodil-test/target/scala-2.12/test-classes/org/apache/daffodil/section06/namespaces/multi_base_09.dfdl.xsd) > > Any ideas what is going on? This seems to be inconsistently occurring, as not > every travisCI test fails. Just some of them. > > > >
