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
// We do want to keep at least one call, otherwise tools/syz-execprog
// will immediately exit.
returnfalse
}
In any case, we now already have such crashes in our database. We either delete them and patch the code never to report them or we get rid of the reproducer consistency check completely.
We're seeing
job: reproducer consistency is invalid
errors once in a while.syzkaller/syz-ci/jobs.go
Lines 416 to 417 in ff949d2
Last time it happened on this bug: https://syzkaller.appspot.com/bug?extid=27209997e4015fb4702e
There are indeed a number of crash reports with C reports, but empty
syz
reports. I don't immediately understand how it could have happened.The text was updated successfully, but these errors were encountered: