syzbot


gvisor test error: lost connection to test machine (9)

Status: auto-obsoleted due to no activity on 2024/10/07 08:04
Reported-by: syzbot+0facc7d94c8a1abc35b2@syzkaller.appspotmail.com
First crash: 417d, last: 417d
Similar bugs (7)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
gvisor gvisor test error: lost connection to test machine (4) -1 1 1883d 1876d 0/26 closed as invalid on 2020/09/13 08:17
gvisor gvisor test error: lost connection to test machine (5) -1 1350 1569d 1771d 0/26 auto-closed as invalid on 2021/07/13 14:39
gvisor gvisor test error: lost connection to test machine (3) -1 187 1972d 1977d 0/26 closed as invalid on 2020/04/08 10:30
gvisor gvisor test error: lost connection to test machine (2) -1 225 2086d 2360d 0/26 auto-closed as invalid on 2020/03/13 01:01
gvisor gvisor test error: lost connection to test machine (6) -1 1 1332d 1332d 0/26 closed as invalid on 2022/01/07 14:19
gvisor gvisor test error: lost connection to test machine -1 160 2609d 2623d 0/26 closed as invalid on 2018/12/12 10:27
gvisor gvisor test error: lost connection to test machine (7) -1 12 1275d 1287d 0/26 auto-closed as invalid on 2022/06/01 21:37
Crashes (1):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/07/09 08:03 gvisor fa204cf4cc60 39158d80 console log ci-gvisor-arm64-systrap-1 gvisor test error: lost connection to test machine
* Struck through repros no longer work on HEAD.