`[stream] xclaim and xpending, all options` test seems to be flaky about redis HOT 7 CLOSED

Yeah, I appreciate that Microsoft has given us such a nice tool in Github Actions, but their compute power is limited! I proposed a fix in #165, which apparently passes on the first try here in Githubland. Let me know what you think.

from redis.

...and even before that. And some other tests are passing in between the failures. So, yes, it's definitely not predictable enough. I'll work on reproducing this locally

from redis.

Not surprisingly, this works locally on an aging MacBook Pro. I would guess that my local environment has a bit more power than the Github Actions environment. My next step would be to look at the timing expectations around the Github Actions test runs... It's been a little while since I've been in this code base, but this seems like a classic integration testing situation 😁 🤓 ⌚

from redis.

This worked well on my local machine! (Ubuntu 20.04) I'll look into it too 😉

from redis.

Oo, interesting, did this test behavior change recently? Or has it been misbehaving for a while now?

from redis.

I see this going back to https://github.com/denodrivers/redis/runs/1523779037?check_suite_focus=true (20 days ago), at least

from redis.

We already have delay statements in the run. I would like to push a change set which increases these values and then see how it performs under github actions

await delay(5);

from redis.