-
Notifications
You must be signed in to change notification settings - Fork 61
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
Flaky postgresql test #1027
Comments
This issue is stale because it has been open for 4 weeks with no activity. |
After the refactor, the parallelization of tests done here |
Seems that it's still valid, reopening for investigation https://github.com/eclipse-tractusx/tractusx-edc/actions/runs/9268208526 |
looks like a new runtime with jetty is started when another one is still running, and the ports are defined statically so they are the same for every runtime (also for different tests). |
Seems strange that a runtime is started when another one still running, we don't run them in parallel afaik |
This issue is stale because it has been open for 2 weeks with no activity. |
This issue was closed because it has been inactive for 7 days since being marked as stale. |
1 similar comment
This issue was closed because it has been inactive for 7 days since being marked as stale. |
Looks like the last time they broke on |
It could be, but i think I saw some failure on dependabot PRs, i would leave this open for now, probably it might need further investigation |
Seems that similar failure happens also in upstream, less frequent though https://github.com/eclipse-edc/Connector/actions/runs/9743379424/job/26886697525?pr=4312 |
This issue is stale because it has been open for 2 weeks with no activity. |
A possibility could be that the |
Ok, I think that also my last theory was wrong... -_- |
This issue is stale because it has been open for 4 weeks with no activity. |
This issue is stale because it has been open for 4 weeks with no activity. |
This issue is stale because it has been open for 4 weeks with no activity. |
Ok, I've got another theory:
the port that it uses is generated randomly after the
At this point I'd see two solutions:
|
@ndr-brt Looked around and didn't see any way to force a custom port in the ryuk container... It's weird to me how frequent the port clashes are, given the large range of ports the getFreePort has... One idea to debug this would be to print the port that clashes, and also get a log of all binded ports in the host. Maybe we could get the exact culprit then? |
@rafaelmag110 a first fix has been proposed here: eclipse-edc/Connector#4712 |
This issue is stale because it has been open for 4 weeks with no activity. |
waiting for the update to the next EDC snapshot to apply the new test strategy |
This issue is stale because it has been open for 4 weeks with no activity. |
WHAT
There's a flaky test in the "postgresql" test cluster, it fails from time to time, e.g.:
https://github.com/eclipse-tractusx/tractusx-edc/actions/runs/7785340855/job/21227835752
FURTHER NOTES
// anything else you want to outline
Please be sure to take a look at
our contribution guidelines and
our PR etiquette.
The text was updated successfully, but these errors were encountered: