> On Dec 18, 2019, at 1:57 PM, Steve Lawrence <slawre...@apache.org> wrote:
>
> Unfortunately, this error happens from time to time, and we haven't been
> able to track it down. Primarily because I don't think anyone has been
> able to reliably reproduce it. I know I've never actually seen it
> outside of the CI.
>
> The bug for this is https://issues.apache.org/jira/browse/DAFFODIL-1908
>
> I think the assumption is there is some kindof non-thread-safe code in
> Xerces (or something that parses the XML) and it hits som race condition
> that prevents it from detecting that the file is UTF-16, and so can't
> parse the file correctly.
If you think that this a Xerces issue then I’d ask on the Xerces dev list.
Regards,
Dave
>
> When I see this, I usually just trigger a new build and it goes away so
> we at least can confirm that the new commit didn't cause any new problems.
>
>
> On 12/18/19 4:16 PM, Sloane, Brandon wrote:
>> After merging in my DataValue PR, I noticed some inconsitent results in our
>> automated testing.
>>
>> Prior to merging, all tests passed.
>>
>> After merging, there was an error in 2 of the configurations:
>>
>>
>> * Java 11, Scala 2.11, Windows-latest
>> https://github.com/apache/incubator-daffodil/runs/355023220
>>
>> * Java 11, Scala 2.12, Windows-latest
>> https://github.com/apache/incubator-daffodil/runs/355023183
>>
>>
>> After re-running the checks, the above 2 configurations passed, but there
>> was an error on a third configuration:
>>
>> * Java 9, scala 2.11, Ubuntu-latest
>> https://github.com/apache/incubator-daffodil/runs/355200232
>>
>> The 2.11 Windows failure was a timeout fetching an external resource; which
>> is a reasonable cause of a transient failure.
>>
>> The 2 remaining failures were both a failure to read the
>> file:/D:/a/incubator-daffodil/incubator-daffodil/daffodil-test/target/scala-2.11/test-classes/org/apache/daffodil/section06/namespaces/multi_base_09.dfdl.xsd
>> file. This file claims to use the UTF-16BE encoding (eyeballing it as a hex
>> file; this appears to be accurate. If this were a determinstic failure, I
>> would blame encoding issues, but I am not sure what to make about the
>> non-deterministic aspect.
>>
>> Thoughts?
>>
>>
>> Brandon T. Sloane
>>
>> Associate, Services
>>
>> bslo...@tresys.com | tresys.com
>>
>
