-
-
Notifications
You must be signed in to change notification settings - Fork 222
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BUG: Async behat tests no longer work #4612
Comments
We should probably enable a daily run of e2e tests in async mode so that we catch regressions faster. Or run them in parallel for every pr? #4110 (comment) |
We could just run them on merge to But we first have to fix this -_- |
Currently we run tests only in sync mode `CATCHUPTRIGGER_ENABLE_SYNCHRONOUS_OPTION=1` as the async mode is broken: neos#4612 I presume the `sleep(2)` is an artefact for the async tests to work at some earlier point.
Currently we run tests only in sync mode `CATCHUPTRIGGER_ENABLE_SYNCHRONOUS_OPTION=1` as the async mode is broken: neos#4612 I presume the `sleep(2)` is an artefact for the async tests to work at some earlier point.
Currently we run tests only in sync mode `CATCHUPTRIGGER_ENABLE_SYNCHRONOUS_OPTION=1` as the async mode is broken: neos/neos-development-collection#4612 I presume the `sleep(2)` is an artefact for the async tests to work at some earlier point.
I tested your branch and after a few adjustments the change worked quite well, at least there were only 15 async failure before bernhards workspace pr. (The failures where still flacky but just a few) Details
After the workspace pr the test rate decreased and 90 fail: Details
|
😵💫 |
Also the |
Obsolete with #4746 |
Probably as a regression of #4455 Behat tests fail when executed in default (asynchronous) mode, i.e. without
CATCHUPTRIGGER_ENABLE_SYNCHRONOUS_OPTION=1
.NOTE: Although we want to improve catch up and blocking process, we decided to "embrace eventual consistency" in general, i.e. never rely on projections to be updated in the same process because this will lead to a more stable and scalable/maintainable architecture
Related: #4423
The text was updated successfully, but these errors were encountered: