Skip to content

Linux kernel block layer testing framework

active 2025-05-272026-08-24 (UTC)

Complete coverage26,552 / 26,552 hourly files (100%) · 2 absent upstream2023-08-152026-08-25 (UTC)
Events
310
Pushes
45
Pull requests
26
Issues
23
Stars
5
Forks
2

Activity over time

Daily event counts in the loaded window

Line chart, 455 days from 2025-05-27 to 2026-08-24. Pushes: 45 total, peak 2 in a day. Pull requests: 26 total, peak 2 in a day. Issues: 23 total, peak 2 in a day. Comments: 173 total, peak 6 in a day. Stars: 5 total, peak 1 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
kawasaki12945862
yizhanglinux8101148
igaw500136
bvanassche200212
disgoel5004
gitPo1son4012
vigneshraman2002
schlad1001
mtkaczyk1001
shroffni1001
hreinecke1010
gjoyce-ibm1001
liangxiao11010

Recent activity

Latest issues, pull requests and releases

  • Issue comment#240kawasaki2026-04-20 00:47
    loop: add regression test for partscan double-scan race
  • Issue comment#241yizhanglinux2026-04-08 02:13
    [not run] test loaded scsi-debug which impact the following test which need scsi-debug
  • Issue comment#241kawasaki2026-04-08 01:06
    [not run] test loaded scsi-debug which impact the following test which need scsi-debug
  • Issue#233kawasaki2026-04-07 00:38
    Compile warning found in blktests on ppc64le
  • Issue comment#234yizhanglinux2026-03-30 00:26
    blktests scsi/011 zbd/010 failed on ppc64le
  • Issue comment#233kawasaki2026-03-29 11:06
    Compile warning found in blktests on ppc64le
  • Issue comment#236kawasaki2026-03-29 07:09
    src/Makefile: nvme-passthru-admin-uring not built when linux/ublk_cmd.h is absent
  • Issue comment#178kawasaki2026-03-24 04:17
    nvme: Add test for sending admin commands over disabled paths
  • Issue#233yizhanglinux2026-03-21 14:27
    Compile warning found in blktests on ppc64le
  • Issue comment#178kawasaki2026-03-20 05:55
    nvme: Add test for sending admin commands over disabled paths
  • Issue comment#218kawasaki2026-03-20 01:49
    Skip tests if scsi_debug module is already loaded and in use
  • Issue comment#218disgoel2026-03-16 10:25
    Skip tests if scsi_debug module is already loaded and in use
  • Issue comment#218kawasaki2026-03-01 09:00
    Skip tests if scsi_debug module is already loaded and in use
  • Pull request#223yizhanglinux2026-02-01 04:32
  • Issue comment#224kawasaki2026-01-26 12:03
    `nvme/039` assumes too much
  • Issue comment#217kawasaki2026-01-26 02:50
    blktests does not update `nvme_adrfam` when using NVMET_TRTYPES
  • Issue comment#223yizhanglinux2026-01-23 15:14
    check: fix kmemleak scan when DEBUG_KMEMLEAK_DEFAULT_OFF enabled
  • Issue#224igaw2026-01-23 09:33
    `nvme/039` assumes too much
  • Pull request#223yizhanglinux2026-01-23 05:22
  • Issue comment#217kawasaki2026-01-17 05:25
    blktests does not update `nvme_adrfam` when using NVMET_TRTYPES
  • Issue comment#207kawasaki2026-01-17 05:22
    blktests nvmet configfs not clean up after blktests nvme/063 failed
  • Issue#185kawasaki2026-01-17 05:18
    Test srp/002 hangs
  • Issue comment#214igaw2026-01-16 17:37
    nvme/050: add support for NVMe multipath devices
  • Issue comment#214yizhanglinux2026-01-12 14:04
    nvme/050: skip test with NVMe multipath device
  • Issue comment#219kawasaki2026-01-11 11:01
    blktests throtl/001 failure due to `scsi_debug` delay=1 by default

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 5 stars here means stars gained during the window, not the repo's star count.