andrew
1673e1c0dd
Enforce 100% line coverage again. Closes #30
2024-08-01 16:03:17 -07:00
andrew
561ed45e3e
Show missing coverage lines in console output
2024-08-01 15:43:09 -07:00
andrew
bfd02503e7
Remove duplicate clang compiler warning action
2024-07-12 13:44:51 -07:00
andrew
d0bd293f8d
Try to fix Jenkins
2024-07-12 13:38:11 -07:00
andrew
3288c583e4
Make metrics thread-safe
...
Even concurrently with calling non-const methods on the associated
ConflictSet
2024-07-12 13:22:02 -07:00
andrew
8ba9b04d8c
Remove "32-bit versions" jenkins stage
...
This is the default now
2024-07-08 15:45:10 -07:00
andrew
1f421e95ff
Resuppress coverage
2024-06-30 21:48:43 -07:00
andrew
2646d5eaf1
Get back to 100% coverage
...
Closes #30
This is achieved by running libfuzzer with USE_32_BIT_VERSIONS={OFF,ON},
and then combining the corpora. I suspect that the problem earlier was
that we only had the 32 bit corpus but were measuring coverage for 64
bit in jenkins.
2024-06-30 21:15:42 -07:00
andrew
9dec45317e
Try to fix code coverage in Jenkins
2024-06-30 15:38:06 -07:00
andrew
d3f4afa167
More SIMD for scanning Node256 with 32-bit versions
2024-06-28 19:48:06 -07:00
andrew
08ed17f47b
Fail jenkins build if not 100% line coverage
2024-04-18 12:43:48 -07:00
andrew
7af961f141
Fix jenkins build
2024-03-28 11:44:01 -07:00
andrew
a91df62608
Add USE_SIMD_FALLBACK build in jenkins
2024-03-28 11:33:53 -07:00
andrew
5b0c3c2428
Exclude more from coverage
...
Only count ConflictSet.cpp in jenkins now, and also add some more
excludes for unreachable lines
2024-03-18 12:05:52 -07:00
andrew
671da5d096
Collect gcc warnings again in Jenkins
2024-03-15 19:00:01 -07:00
andrew
0f795cf163
Set -DNVALGRIND for release artifacts
2024-03-13 20:45:59 -07:00
andrew
c2606cd26a
Add clang build in jenkins and record issues for clang
...
I can't seem to get gcc to do what I want for this control flow warning
thingy
2024-03-13 13:39:39 -07:00
andrew
30abf7833d
Use gcc for coverage build
2024-03-05 12:41:19 -08:00
andrew
d9c0d24e58
Don't run benchmarks in jenkins
...
It's probably too noisy and I don't even look anyway
2024-03-05 12:34:35 -08:00
andrew
16aa52c071
Try cross-compiling to arm in jenkins
2024-03-04 22:58:04 -08:00
andrew
b68e04ba80
Fix file pattern
2024-03-04 20:09:38 -08:00
andrew
45e8d68234
Try building an RPM in jenkins
2024-03-04 19:55:45 -08:00
andrew
68bd39e130
Put skip list in its own shared lib
...
Now we can right benchmarks against one api, and just change the library
path
2024-02-27 12:02:01 -08:00
andrew
d43a8a5907
Run benchmark in jenkins
2024-02-23 16:17:28 -08:00
andrew
4b7d6d6cfb
Try building paper in jenkins
2024-02-05 12:29:53 -08:00
andrew
c4c86a69c6
Jenkins fix attempts
2024-02-04 18:08:58 -08:00
andrew
345af773fb
Try building in jenkins
2024-02-04 17:56:16 -08:00
andrew