Closed manast closed 2 weeks ago
@manast thanks for notifying us. Can you please remind me how to run the test suite?
nm, figured this out from your actions:
yarn install --frozen-lockfile --non-interactive
yarn build
BULLMQ_TEST_PREFIX={b} yarn test
with local dragonfly: ./dragonfly --dbfilename= --noversion_check --maxmemory=8G --cluster_mode=emulated --lock_on_hashtags --logtostderr
Hi there. This same issue broke our production :D Waiting for a fix. Reverting to ghcr.io/dragonflydb/dragonfly:v1.24.0
works. Would probably be good to push a revert to 1.25.1 to fix deployments fetching the latest version.
Good idea, I pushed the latest tag to point to v1.24.0 for now.
Describe the bug Since v1.25.0 released today, BullMQ's test suite produces a hard crash in dragonfly's server.
To Reproduce
Steps to reproduce the behavior: Just run the test suite but one of the tests that reproduces the issue is the first test in test_concurrency.ts: https://github.com/taskforcesh/bullmq/blob/master/tests/test_concurrency.ts#L33
Expected behavior Should not crash and test should pass
Screenshots
Environment (please complete the following information):
uname -a
Reproducible Code Snippet
Additional context This is the output of the server when it crashes:
This is the last command sent to Dragonfly and that triggers the crash:
Let me know if you need more info.