You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is my first issue in the Go repo - if I miss something out please let me know and I'll add it. Furthermore, if this problem is solved then please point me in the right direction. TIA!
Problem to solve
Do some post-processing on fuzzing output as part of CI.
Current behaviour
There is a -json flag that may be passed for fuzz tests that does a fairly basic job of outputting the results of the test in a line-by-line json stream. For example
The particular field I'm interested in is Output as this contains the really important information from a testers perspective. Currently this field is just a copy of whatever line would otherwise have been printed to stdout if -json had been omitted.
Current workarounds
It's not difficult to do some regex matching on the Output field to pull out the interesting information (full stacktrace and sha of the failing input), but it feels like there could be a better way. And I don't know whether the text on stdout is considered a stable API.
Proposal
Make this Output field a structured type, or add new structured fields so that post-processing is as easy as running some jq. Something as simple as
would be ideal. Even having the FailingInput []byte in there is optional since I can pull that information out from testdata/fuzz given the sha and test name.
The text was updated successfully, but these errors were encountered:
Proposal Details
This is my first issue in the Go repo - if I miss something out please let me know and I'll add it. Furthermore, if this problem is solved then please point me in the right direction. TIA!
Problem to solve
Do some post-processing on fuzzing output as part of CI.
Current behaviour
There is a
-json
flag that may be passed for fuzz tests that does a fairly basic job of outputting the results of the test in a line-by-line json stream. For exampleThe particular field I'm interested in is
Output
as this contains the really important information from a testers perspective. Currently this field is just a copy of whatever line would otherwise have been printed to stdout if-json
had been omitted.Current workarounds
It's not difficult to do some regex matching on the
Output
field to pull out the interesting information (full stacktrace and sha of the failing input), but it feels like there could be a better way. And I don't know whether the text on stdout is considered a stable API.Proposal
Make this
Output
field a structured type, or add new structured fields so that post-processing is as easy as running somejq
. Something as simple aswould be ideal. Even having the
FailingInput []byte
in there is optional since I can pull that information out fromtestdata/fuzz
given the sha and test name.The text was updated successfully, but these errors were encountered: