Checker's false-invalid as it may raise an exception: multiset.core.MultiSet cannot be cast to clojure.lang.IObj about jepsen

[bogdando]

@aphyr please take a look

[bogdando]

The patch #105 fixes the issue magically, now I can see the real failure reason in the analysis:

{:queue {:valid? false, :error "can't dequeue 137"},
:total-queue
{:valid? true,
:lost #{},
:recovered #{144 143 146 142 145},
:recovered-frac 5/147,
:unexpected-frac 0,
:unexpected nil,
:lost-frac 0,
:duplicated-frac 1/147,
:ok-frac 1,
:duplicated #{137}},
:valid? false}

[bogdando]

Well, the ":unexpected nil," looks a bit ugly, but at least other useful data presents with the patch...

[aphyr]

multiset.core.MultiSet cannot be cast to clojure.lang.IObj
 at clojure.core/with_meta (core.clj:217)  
    clojure.core$set.invoke (core.clj:3957)
    jepsen.checker$reify__6627.check (checker.clj:172)

You have a multiset, and the checker calls set on it. Multisets don't have a set representation, which is probably why this failed. Might be a checker bug around unexpected, but I recall the rabbit test running fine last I hacked on it. No guarantees, of course. ;-) Might also be a mismatch between the history values and the checker.

[bogdando]

As far as I've just reused the code from the master branch as is, the bug seems vaild.

[bogdando]

I have no idea then how to fix this. The checker just doesn't work with those cast errors

[bogdando]

Should be fixed by ed17b08