Use fsck to detect corrupt file systems in reproducers #14555
Triggered via pull request
November 28, 2024 18:23
FlorentRevest
Status
Failure
Total duration
12m 53s
Artifacts
–
This run and associated checks have been archived and are scheduled for deletion.
Learn more about checks retention
ci.yml
on: pull_request
aux
4m 49s
build
12m 22s
dashboard
5m 19s
race
10m 45s
race_dashboard
7m 18s
old
6m 34s
gvisor
4m 5s
Matrix: arch
Annotations
20 errors
|
race:
fsck_test.go#L70
btrfsck --readonly should exit 0 on a clean file system
|
|
race:
fsck_test.go#L70
fsck.cramfs should exit 0 on a clean file system
|
|
race:
fsck_test.go#L70
fsck.erofs should exit 0 on a clean file system
|
|
race:
fsck_test.go#L70
fsck.exfat -n should exit 0 on a clean file system
|
|
race:
fsck_test.go#L70
fsck.ext4 -n should exit 0 on a clean file system
|
|
race:
fsck_test.go#L70
fsck.f2fs should exit 0 on a clean file system
|
|
race:
fsck_test.go#L70
fsck.gfs2 -n should exit 0 on a clean file system
|
|
race:
fsck_test.go#L70
fsck.jfs -n should exit 0 on a clean file system
|
|
race:
fsck_test.go#L70
fsck.minix should exit 0 on a clean file system
|
|
race:
fsck_test.go#L70
fsck.msdos -n should exit 0 on a clean file system
|
|
build:
fsck_test.go#L70
btrfsck --readonly should exit 0 on a clean file system
|
|
build:
fsck_test.go#L70
fsck.cramfs should exit 0 on a clean file system
|
|
build:
fsck_test.go#L70
fsck.erofs should exit 0 on a clean file system
|
|
build:
fsck_test.go#L70
fsck.exfat -n should exit 0 on a clean file system
|
|
build:
fsck_test.go#L70
fsck.ext4 -n should exit 0 on a clean file system
|
|
build:
fsck_test.go#L70
fsck.f2fs should exit 0 on a clean file system
|
|
build:
fsck_test.go#L70
fsck.gfs2 -n should exit 0 on a clean file system
|
|
build:
fsck_test.go#L70
fsck.jfs -n should exit 0 on a clean file system
|
|
build:
fsck_test.go#L70
fsck.minix should exit 0 on a clean file system
|
|
build:
fsck_test.go#L70
fsck.msdos -n should exit 0 on a clean file system
|