Tests run for too long leading to timeouts #563
Assignees
Labels
Milestone
Comments
7 tasks
7 tasks
Carsopre
added a commit
that referenced
this issue
Aug 30, 2024
## Issue addressed Solves #563 ## Code of conduct - [x] I HAVE NOT added sensitive or compromised (test) data to the repository. - [x] I HAVE NOT added vulnerabilities to the repository. - [x] I HAVE discussed my solution with (other) members of the RA2CE team. ## What has been done? - Moved logic in protocol as static method in the `Segmentation` class. Not ideal, but better than before. - Modified test `network.ini` files so that their segmentation length property is `100` (meters) rather than `0.0001` which makes it way longer to compute. ### Checklist - [x] Code is formatted using our custom `black` and `isort` definitions. - [x] Tests are either added or updated. - [x] Branch is up to date with `master`. - [x] Updated documentation if needed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Ra2ce version checks
masterhere.Reproducible example
https://dpcbuild.deltares.nl/buildConfiguration/Ra2ce_Ra2ceContinuousDelivery_RunAllTests/4423291?hideTestsFromDependencies=false&hideProblemsFromDependencies=false&expandBuildDeploymentsSection=false&expandBuildChangesSection=true&expandBuildProblemsSection=true
https://dpcbuild.deltares.nl/buildConfiguration/Ra2ce_Ra2ceContinuousIntegrationBuild_RunSlowAndExternalTestsPytestXdist/4417918?hideTestsFromDependencies=false&hideProblemsFromDependencies=false&expandBuildDeploymentsSection=false&expandBuildChangesSection=true&expandBuildProblemsSection=true
Current behaviour
Since recent versions the code hangs on where it use to run relatively fast(er).
Desired behaviour
Tests do not timeout.
Additional context
No response
The text was updated successfully, but these errors were encountered: