I haven't seen failures in tests in a while, only thing I've noticed is GitHub actions just stalling with no output.
In the linked PR, I see the error: [error] Test org.apache.daffodil.example.TestScalaAPI.testScalaAPI2 failed: expected:<0> but was:<1>, took 0.307 sec I wonder if these isAtEnd changes have introduced a race condition, or made an existing race condition more likely to get hit? On 4/27/21 2:13 PM, Beckerle, Mike wrote: > My PR keeps failing to build on Windows e.g., > This failed the windows java8 build: > https://github.com/mbeckerle/daffodil/actions/runs/789865909 > <https://github.com/mbeckerle/daffodil/actions/runs/789865909> > > Previously today it failed the windows java 11 build. > > The errors were different. Earlier today it was in daffodil-io, the linked > checks above it's in daffodil-sapi. > > In neither case is there an [error] identifying the specific test failing. > Only > a summary at the end indicating there were failures in that module. > > Is any of this expected behavior? I've seen mostly all 6 standard CI checks > working of late on others' PRs. > > > Mike Beckerle | Principal Engineer > > [email protected] <mailto:[email protected]> > > P +1-781-330-0412 >
