weaselab/conflict-set
2
0
Fork 0
Code Issues 4 Packages Releases 13 Activity

Add more to corpus (from fuzzing on osx)
Some checks reported errors
Tests / Clang total: 1784, passed: 1784
Details
Clang |Total|New|Outstanding|Fixed|Trend |:-:|:-:|:-:|:-:|:-: |0|0|0|0|:clap:
Details
Tests / Debug total: 1782, passed: 1782
Details
Tests / SIMD fallback total: 1784, passed: 1784
Details
Tests / Release [gcc] total: 1784, passed: 1784
Details
GNU C Compiler (gcc) |Total|New|Outstanding|Fixed|Trend |:-:|:-:|:-:|:-:|:-: |0|0|0|0|:clap:
Details
Tests / Release [gcc,aarch64] total: 1330, passed: 1330
Details
Tests / Coverage total: 1340, passed: 1340
Details
Code Coverage #### Project Overview No changes detected, that affect the code coverage. * Line Coverage: 99.12% (1799/1815) * Branch Coverage: 67.50% (1485/2200) * Complexity Density: 0.00 * Lines of Code: 1815 #### Quality Gates Summary Output truncated.
Details
weaselab/conflict-set/pipeline/head Something is wrong with the build of this commit
Details

Browse Source 
Maybe we should just accumulate the corpus instead of replacing it? That
should be easier on git right?
This commit is contained in:
Andrew Noyes
2024-08-09 18:06:54 -07:00
parent 182c065c8e
commit 9f8800af16
91 changed files with 1 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

BIN
corpus/4f6f6c3d09001ba95b1f1d2e2c66715441247e5b Normal file
View File

Binary file not shown.