Kyle Kingsbury

Ah! Like, imagine a user runs a test like `{:ssh {:username nil}}`, or maybe called a jepsen.control function without an SSH session bound--those could also cause NPEs. If this is...

Yes, because I know that one's a transient error. NullPointerException, though, could mean *lots* of things... in this case, it looks like a transient problem, but in other cases, it...

Yeah, there's absolutely nothing stopping you from catching this in your DB setup/teardown too--I do this pretty frequently.

The instructions are for Debian Jessie; Stretch just came out and I haven't started the upgrade process yet. You're welcome to start moving things forward to Stretch if you like.

What does "a long time" mean here? Longer than the time limit you set for the test?

Huh. That shouldn't happen! It looks like Jepsen's in the middle of making some requests to the Postgres node, and presumably it's not answering. There *should* be timeouts here, but...

Oh! Yeah, that could be a thing. I haven't actually finished the Stolon test--I found bugs in single-node Postgres deployments and worked on those instead, so this test is very...

I think this is because you're running buster, and jepsen.os.debian is written for stretch, which is the most recent LTS version. Buster may have changed some package names. You're welcome...

On 6/15/20 10:17 AM, Zhang Jian wrote: > I tried Jepsen on Ubuntu 18.04, Debian 10.x and Debian 9.12.0. They all have the > same problem. I don't know how...

Cool! That looks like a bug in clj-ssh--might be worth reporting it there?