It looks like this failed the regression tests in the recent runs:
1. http://build.prakashsurya.com:8080/job/openzfs-regression-tests/138/
2. http://build.prakashsurya.com:8080/job/openzfs-regression-tests/140/
To help with debugging these failures, I've tar-ed up the workspace of the
ztest failures, configured anonymous FTP, and put the tarballs up for download.
Assuming I configured things correctly, one should be able to use any FTP
client to download the files, e.g. I can point my chrome browser at
`ftp://build.prakashsurya.com`. There's two files:
1. ftp://build.prakashsurya.com/openzfs-run-ztest-138.tar.gz - This contains
the ztest results for the first run, openzfs-regression-tests 138
2. ftp://build.prakashsurya.com/openzfs-run-ztest-138.tar.gz - This contains
the ztest results for the second run, openzfs-regression-tests 140
There's a core file in the second run from the failed ztest, but the first run
didn't tigger crash ztest so there's no core file. An illumos system might be
necessary (i.e. `mdb`) to properly analyze the core file, but my guess is any
implementation of `zdb` (e.g. illumos, linux, mac, freebsd, w/e) should be able
to be used to inspect the ztest vdev files contained in the tarballs.
---
Reply to this email directly or view it on GitHub:
https://github.com/openzfs/openzfs/pull/51#issuecomment-170971178
_______________________________________________
developer mailing list
developer@open-zfs.org
http://lists.open-zfs.org/mailman/listinfo/developer
