Skip to content
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

CI build/push failures on tfserving-proxy image are not included in exit values #2477

Closed
RafalSkolasinski opened this issue Sep 23, 2020 · 1 comment
Labels
bug triage Needs to be triaged and prioritised accordingly

Comments

@RafalSkolasinski
Copy link
Contributor

User reported that seldonio/tfserving-proxy_rest:1.2.3 is not present on the Docker Hub.
The post 1.2.3 nightly and dev builds are present.

It looks like there was an issue in the CI build. It failed on building the related GRPC image

ERROR: An error occurred: context deadline exceeded

but this was not caught by the exit values so went unnoticed
Python exit value: 0
Operator exit value: 0
Engine exit value: 0
Executor exit value: 0
Mock model exit value: 0
Alibi Detect exit value: 0
Request Logger exit value: 0

Extra context:

@RafalSkolasinski RafalSkolasinski added bug triage Needs to be triaged and prioritised accordingly labels Sep 23, 2020
@RafalSkolasinski
Copy link
Contributor Author

Actually, I was initially wrong. The pipeline failed

Pipeline failed on stage 'build-and-push' : container 'step-build-and-push-images'. The execution of the pipeline has stopped.�[0m

because the related exit value is included, it just not get printed in logs
+ ${TFPROXY_EXIT_VALUE} \

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug triage Needs to be triaged and prioritised accordingly
Projects
None yet
Development

No branches or pull requests

2 participants