-
Notifications
You must be signed in to change notification settings - Fork 29
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] Fix flaky espionage dispatch mission test #401
Comments
This issue can be reproduced locally (not tested in Docker), by running the fleet dispatch espionage tests in loop:
There is also another flaky case with the same testDispatchFleetDebrisEspionageReport that pops up when running only that test in the loop:
|
Hi @rautamik, Thank you for testing this and for sharing the command to reproduce the error at will, that is very helpful! 👍 |
Re-opening this issue: the flaky tests still occur in new PR's. I'm working on refactoring how the tests interact with time as certain tests are setting time to static values (2024-01-01) and other tests do not and therefore use the current time which causes conflicts. If all tests use the same starting point this problem should go away once and for all. |
Fixed by #433 |
Describe the bug
This test sometimes fails when running jobs:
For example, see this GitHub Action run:
https://github.com/lanedirt/OGameX/actions/runs/11373489520/job/31640153417
To Reproduce
Steps to reproduce the behavior:
php artisan test
in theogame-app
docker container.Expected behavior
Test to always succeed, especially if nothing regarding espionage missions has been changed. The problem in this case can be caused by underlying game logic that is actually faulty, or it can be caused by something else that makes it flaky (i.e. fail sometimes while it shouldn't).
The text was updated successfully, but these errors were encountered: