You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An issue to track the current bug we are seeing on the Github runner with ZFS where during the stress test we get the following error:
+ opam exec -- dune exec -- ./stress/stress.exe zfs:zfs
cannot promote 'zfs/cache-tmp/0-c-c1': not a cloned filesystem
stress: internal error, uncaught exception:
(Failure
"\"sudo\" \"zfs\" \"promote\" \"zfs/cache-tmp/0-c-c1\" failed with exit status 1")
Note, previously on Travis builds this was working (with the same version of ZFS): https://travis-ci.org/github/ocurrent/obuilder/builds/768095520 and the stress test works with an older version of ZFS I've tried locally. Setting the stress test to output debug logs also suggests all of the zfs commands leading up to this call to promote are identical so I'm wondering if there is some weird github runner issue happening here. I'll see if I can update to the right version locally to see if that shows the bug.
The text was updated successfully, but these errors were encountered:
An issue to track the current bug we are seeing on the Github runner with ZFS where during the stress test we get the following error:
Note, previously on Travis builds this was working (with the same version of ZFS): https://travis-ci.org/github/ocurrent/obuilder/builds/768095520 and the stress test works with an older version of ZFS I've tried locally. Setting the stress test to output debug logs also suggests all of the
zfs
commands leading up to this call topromote
are identical so I'm wondering if there is some weird github runner issue happening here. I'll see if I can update to the right version locally to see if that shows the bug.The text was updated successfully, but these errors were encountered: