-
Notifications
You must be signed in to change notification settings - Fork 83
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
Fix vdrproxy CI job intermittent failures #994
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looking at the logs from the failed container
Listening on http://0.0.0.0:3030 ...
Error initializing pool: Pool timeout: Request was interrupted
it seems that the issue is that there's needs to be bit of timeout between the steps of starting indy pool and starting vdrproxy.
Hmmm... Okay, so it's not the proxy itself. Where did you get the container logs, though? As in, were they already present somewhere or did you do a custom run with something like |
… throughout the workflow Signed-off-by: Bogdan Mircea <[email protected]>
Signed-off-by: Bogdan Mircea <[email protected]>
Signed-off-by: Bogdan Mircea <[email protected]>
Signed-off-by: Bogdan Mircea <[email protected]>
Signed-off-by: Bogdan Mircea <[email protected]>
d1d2ad8
to
4861572
Compare
Signed-off-by: Bogdan Mircea <[email protected]>
Signed-off-by: Bogdan Mircea <[email protected]>
Codecov Report
@@ Coverage Diff @@
## main #994 +/- ##
=======================================
Coverage 30.02% 30.02%
=======================================
Files 415 415
Lines 26916 26916
Branches 5243 5243
=======================================
+ Hits 8081 8082 +1
Misses 16639 16639
+ Partials 2196 2195 -1
Flags with carried forward coverage won't be shown. Click here to find out more. |
Signed-off-by: Bogdan Mircea <[email protected]>
Signed-off-by: Bogdan Mircea <[email protected]>
Attempts to fix the vdrproxy CI job by adding a health check action for the services ports.
Additionally, within the same action and some other, the Rust toolchain version was hardcoded, therefore tweaked the inputs to accept the version for consistency reasons.