Paul Dreik
|
29e78413fe
|
output failed fuzz cases (#409)
this is to get more debug output from cases like this:
c9cd8e6211/checks ?check_suite_id=351526761
https://pipelines.actions.githubusercontent.com/gFSIASDqcDhMdHkcuMJEdsUcdOsOrVBr8d56BjAkszcoMkibGp/_apis/pipelines/1/runs/274/signedlogcontent/3?urlExpires=2019-12-21T18%3A50%3A08.3387613Z&urlSigningMethod=HMACV1&urlSignature=DVF3u4jEs81xJP6Hmi8LLQlLOztJke8MsP62J0MXruQ%3D
which ends with:
2019-12-20T23:08:42.6830393Z ../src/generic/numberparsing.h:243:31: runtime error: 1e+311 is outside the range of representable values of type 'double'
2019-12-20T23:08:42.6836790Z SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior ../src/generic/numberparsing.h:243:31 in
2019-12-20T23:08:42.6837715Z MS: 2 InsertRepeatedBytes-CrossOver-; base unit: 47cf79b80bc84f2ec8b39c1c73daa6c1222ef624
2019-12-20T23:08:42.6866416Z artifact_prefix='./'; Test unit written to ./crash-3fa2f47d980d4bf5812af18fb0d0a0ce9b5cc65a
2019-12-20T23:08:42.6999448Z ##[error]Process completed with exit code 1.
2019-12-20T23:08:42.7030863Z Cleaning up orphan processes
The problem is that github actions does not store artifacts on failure.
|
2019-12-21 20:32:32 +01:00 |
Paul Dreik
|
8192e63a4b
|
update apt repos before installing (#408)
This should hopefully resolve the recent errors in the github action
for running the fuzzers.
|
2019-12-21 19:23:51 +01:00 |
Paul Dreik
|
c5504ef50b
|
run the oss fuzz initial seed corpus in CI (#378)
This makes sure the seed corpus keeps being healthy.
|
2019-11-23 22:49:41 +01:00 |
Paul Dreik
|
3fd1c3b64a
|
run short fuzzing and valgrind in github action
|
2019-11-11 22:17:32 +01:00 |