conflict-set

Author	SHA1	Message	Date
Andrew Noyes	14515e186a	Update readme benchmarks again All checks were successful Tests / Clang total: 1096, passed: 1096 Details Clang \|Total\|New\|Outstanding\|Fixed\|Trend \|:-:\|:-:\|:-:\|:-:\|:-: \|0\|0\|0\|0\|:clap: Details Tests / Release [gcc] total: 1096, passed: 1096 Details GNU C Compiler (gcc) \|Total\|New\|Outstanding\|Fixed\|Trend \|:-:\|:-:\|:-:\|:-:\|:-: \|0\|0\|0\|0\|:clap: Details Tests / Release [gcc,aarch64] total: 824, passed: 824 Details Tests / Coverage total: 823, passed: 823 Details weaselab/conflict-set/pipeline/head This commit looks good Details I think the last skiplisttest benchmark looked bad because I had vscode + firefox + ?? open	2024-03-27 16:47:36 -07:00
Andrew Noyes	76a7e17b29	Update readme benchmarks Some checks failed Tests / Clang total: 1096, failed: 2, passed: 1094 Details Tests / Release [gcc] total: 1096, failed: 2, passed: 1094 Details Tests / Release [gcc,aarch64] total: 824, failed: 2, passed: 822 Details Tests / Coverage total: 823, passed: 823 Details weaselab/conflict-set/pipeline/head There was a failure building this commit Details I was incorrectly linking to an old build of conflict set, before the conflict-set name change. I don't know what the regression is from, but update the README for transparency now.	2024-03-27 16:12:45 -07:00
Andrew Noyes	a4d1f91670	Update README benchmark after adding getBytes All checks were successful Tests / Clang total: 1096, passed: 1096 Details Clang \|Total\|New\|Outstanding\|Fixed\|Trend \|:-:\|:-:\|:-:\|:-:\|:-: \|0\|0\|0\|0\|:clap: Details Tests / Release [gcc] total: 1096, passed: 1096 Details GNU C Compiler (gcc) \|Total\|New\|Outstanding\|Fixed\|Trend \|:-:\|:-:\|:-:\|:-:\|:-: \|0\|0\|0\|0\|:clap: Details Tests / Release [gcc,aarch64] total: 824, passed: 824 Details Tests / Coverage total: 823, passed: 823 Details weaselab/conflict-set/pipeline/head This commit looks good Details	2024-03-20 16:26:05 -07:00
Andrew Noyes	2e08b54785	Update README.md with 1.0 benchmarks Some checks reported errors weaselab/conflict-set/pipeline/head Something is wrong with the build of this commit Details Closes #7	2024-03-19 16:41:59 -07:00
Andrew Noyes	be8ac879c5	Update README benchmarks All checks were successful Tests / Clang total: 825, passed: 825 Details Clang \|Total\|New\|Outstanding\|Fixed\|Trend \|:-:\|:-:\|:-:\|:-:\|:-: \|0\|0\|0\|0\|:clap: Details Tests / Release [gcc] total: 825, passed: 825 Details GNU C Compiler (gcc) \|Total\|New\|Outstanding\|Fixed\|Trend \|:-:\|:-:\|:-:\|:-:\|:-: \|0\|0\|0\|0\|:clap: Details Tests / Release [gcc,aarch64] total: 824, passed: 824 Details Tests / Coverage total: 823, passed: 823 Details weaselab/conflict-set/pipeline/head This commit looks good Details	2024-03-18 17:24:26 -07:00
Andrew Noyes	9cafef8bbb	Update benchmarks after fixing skip list bug in `a9b3d3d` Some checks failed Tests / Clang total: 932, passed: 932 Details Clang \|Total\|New\|Outstanding\|Fixed\|Trend \|:-:\|:-:\|:-:\|:-:\|:-: \|0\|0\|0\|0\|:clap: Details Tests / Release [gcc] total: 932, passed: 932 Details Tests / Release [gcc,aarch64] total: 931, failed: 309, passed: 622 Details Tests / Coverage total: 930, passed: 930 Details weaselab/conflict-set/pipeline/head There was a failure building this commit Details	2024-03-14 15:50:55 -07:00
Andrew Noyes	8a36e72640	Update readme benchmarks	2024-03-07 15:55:31 -08:00
Andrew Noyes	70e3377eac	Update benchmark in README.md All checks were successful Tests / Release [gcc] total: 471, passed: 471 Details GNU C Compiler (gcc) \|Total\|New\|Outstanding\|Fixed\|Trend \|:-:\|:-:\|:-:\|:-:\|:-: \|0\|0\|0\|0\|:clap: Reference build: <a href="https://jenkins.weaselab.dev/job/weaselab/job/conflict-set/job/main/37//gcc">weaselab » conflict-set » main #37</a> Details Tests / Coverage total: 469, passed: 469 Details weaselab/conflict-set/pipeline/head This commit looks good Details Don't try to make sense of the diff - the benchmark itself changed too	2024-02-23 17:31:48 -08:00
Andrew Noyes	1efc787805	Add README.md	2024-02-20 13:13:48 -08:00

9 Commits