The push to this branch on my fork usually causes our workflows that test
it on all those configurations, to run.
Nothing running though. It says no workflows.
Anybody have a clue why?
On Sun, Mar 24, 2024 at 12:24 AM Mike Beckerle
wrote:
> *@mbeckerle* commented on this pull request.
>
>
I have some new fuzz testing stuff.
It depends on TestUtils which is in daffodil-core, but lives in the
src/test, so isn't in the packaged daffodil jars.
I want to use this stuff to test separate DFDL schemas. Those depend on the
packaged daffodil jars.
TestUtils is effectively an application
Just reporting back, FYI, on this issue.
I am now experiencing these hangs on a native bare-metal Ubuntu install on
a separate computer. So it has nothing to do with virtual machines.
At one point when it hung I was clicking around and saw this dialog to show
on a side monitor:
[image:
So Owl has a ZipLayer - for messages that contain the bytes of a zip file.
As part of exercising these new Daffodil Layer APIs, I have rewritten this
Zip Layer.
I have written a fuzz tester, the objective being to try to crash the
layers so they throw bad exceptions like NPE or other ill-behaved
