mirror of
https://git.FreeBSD.org/src.git
synced 2024-12-02 08:42:48 +00:00
stress2: Update the exclude list
This commit is contained in:
parent
7b6fe2428a
commit
af67f36a92
@ -30,8 +30,6 @@ gnop8.sh Waiting for patch commit 20201214
|
|||||||
gnop9.sh Waiting for patch commit 20201214
|
gnop9.sh Waiting for patch commit 20201214
|
||||||
graid1_8.sh Known issue 20170909
|
graid1_8.sh Known issue 20170909
|
||||||
graid1_9.sh panic: Bad effnlink 20180212
|
graid1_9.sh panic: Bad effnlink 20180212
|
||||||
ifconfig.sh Bug 253824 20210322
|
|
||||||
ifconfig2.sh https://people.freebsd.org/~pho/stress/log/log0051.txt 20210210
|
|
||||||
lockf5.sh Spinning threads seen 20160718
|
lockf5.sh Spinning threads seen 20160718
|
||||||
maxvnodes2.sh https://people.freebsd.org/~pho/stress/log/log0083.txt 20210329
|
maxvnodes2.sh https://people.freebsd.org/~pho/stress/log/log0083.txt 20210329
|
||||||
memguard.sh https://people.freebsd.org/~pho/stress/log/log0088.txt 20210402
|
memguard.sh https://people.freebsd.org/~pho/stress/log/log0088.txt 20210402
|
||||||
@ -51,6 +49,7 @@ oom2.sh Hang in pfault 20180324
|
|||||||
overcommit2.sh CAM stuck in vmwait seen 20200112
|
overcommit2.sh CAM stuck in vmwait seen 20200112
|
||||||
pageout.sh panic: handle_written_filepage: not started 20190218
|
pageout.sh panic: handle_written_filepage: not started 20190218
|
||||||
pmc8.sh panic: [pmc,2749] (ri21, rc1) waiting too long for pmc to ... 20210621
|
pmc8.sh panic: [pmc,2749] (ri21, rc1) waiting too long for pmc to ... 20210621
|
||||||
|
rename14.sh https://people.freebsd.org/~pho/stress/log/log0433.txt 20230409
|
||||||
sctp2.sh panic: Queues are not empty when handling SHUTDOWN-COMPLETE 20210211
|
sctp2.sh panic: Queues are not empty when handling SHUTDOWN-COMPLETE 20210211
|
||||||
sctp3.sh panic: Queues are not empty when handling SHUTDOWN-COMPLETE 20210211
|
sctp3.sh panic: Queues are not empty when handling SHUTDOWN-COMPLETE 20210211
|
||||||
sendfile25.sh WiP 20200611
|
sendfile25.sh WiP 20200611
|
||||||
|
Loading…
Reference in New Issue
Block a user