Skip to content

Actions: jdmanring/linux_hammer2

Actions

CI

Actions

Loading...
Loading

Show workflow options

Create status badge

Loading
ci.yml
331 workflow runs
331 workflow runs

Filter by Event

⌥ + click/return to exclude

Filter by Status

⌥ + click/return to exclude

Filter by Branch

⌥ + click/return to exclude

Filter by Actor

⌥ + click/return to exclude
Every kernel-facing test declares its reference control CI #331: Commit 593775f pushed by jdmanring
2m 28s main
main
2m 28s
The other two uses of offset_in_folio are correct, and it was checked CI #330: Commit c21ba4d pushed by jdmanring
2m 37s main
main
2m 37s
Record 0.9.36, the fallocate punch that skipped its own zeroing CI #329: Commit 0697254 pushed by jdmanring
2m 29s main
main
2m 29s
The ioctl surface against upstream's is written down CI #328: Commit 153df93 pushed by jdmanring
2m 24s main
main
2m 24s
The keep-size difference between the two modes is not a difference CI #327: Commit e41be94 pushed by jdmanring
2m 29s main
main
2m 29s
The fallocate zeroing works and the folio it zeroes is not the one read CI #326: Commit 831c529 pushed by jdmanring
2m 28s main
main
2m 28s
The folio_zero_segment candidate is eliminated by reading the kernel CI #325: Commit d9fd428 pushed by jdmanring
2m 35s main
main
2m 35s
The fallocate punch changes nothing, reproduced three ways CI #324: Commit 3b2f041 pushed by jdmanring
1m 33s main
main
1m 33s
The fallocate readings do not reproduce and the entry says so CI #323: Commit b485cdc pushed by jdmanring
2m 45s main
main
2m 45s
The staged fallocate works and the exerciser is what failed it CI #322: Commit 7d5a709 pushed by jdmanring
2m 31s main
main
2m 31s
The fallocate punch zeroes pages that are not the bytes it reads back CI #321: Commit 270601d pushed by jdmanring
2m 23s main
main
2m 23s
The fallocate punch writes non-zero blocks, from counters not reading CI #320: Commit 7258034 pushed by jdmanring
2m 27s main
main
2m 27s
The bulkfree accounting that made a punch look expensive is confirmed CI #319: Commit ea7cedf pushed by jdmanring
2m 31s main
main
2m 31s
A fallocate punch never reaches the media, and the cause was wrong CI #318: Commit b23ab4e pushed by jdmanring
2m 2s main
main
2m 2s
The staged fallocate punch frees no block and costs one instead CI #317: Commit 579a632 pushed by jdmanring
2m 33s main
main
2m 33s
Lifting the readings into a governed doc was measured and is unnecessary CI #316: Commit 3751e34 pushed by jdmanring
2m 31s main
main
2m 31s
The rule for a dated document's claim about this tree is written down CI #315: Commit c61dcef pushed by jdmanring
2m 25s main
main
2m 25s
A filing draft said the port still runs XOPs synchronously CI #314: Commit f669805 pushed by jdmanring
2m 31s main
main
2m 31s
Five tool paths in the research corpus did not resolve CI #313: Commit ae3bb20 pushed by jdmanring
2m 27s main
main
2m 27s
The spin reading cited a commit this tree does not have CI #312: Commit 8fe0155 pushed by jdmanring
2m 4s main
main
2m 4s
Record the sweep over the staged patches and what it read CI #311: Commit 3251d73 pushed by jdmanring
2m 25s main
main
2m 25s
Record 0.9.35, the reptrack spin released before the drop CI #310: Commit 8b4408d pushed by jdmanring
1m 45s main
main
1m 45s
Record the fleet reading on the freemap recovery fix CI #309: Commit 48f1fda pushed by jdmanring
1m 30s main
main
1m 30s
Record 0.9.34, the freemap recovery's null chain fixed here CI #308: Commit 67b56de pushed by jdmanring
2m 1s main
main
2m 1s
Record 0.9.33, the staged-file check reading its stated population CI #307: Commit 0d7d238 pushed by jdmanring
2m 14s main
main
2m 14s