-
Notifications
You must be signed in to change notification settings - Fork 88
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
Failing Kubernetes Tests in the CI #412
Comments
To debug something failing more freely, if it is failing as part of a PR where no sensitive secrets can be exposed, I suggest using this github action to expose a SSH session so one can debug it live: https://github.com/yuvipanda/jupyterhub-ssh/blob/a61098162014f5a8c8ad3759273345838873619c/.github/workflows/test-chart.yaml#L154-L160 # WARNING: Only allow this for pull_request runs that doesn't contain
# sensitive information.
#
# action reference: https://github.com/mxschmitt/action-tmate@v3
- name: To enter a SSH debugging session, read these logs
if: failure() && github.event_name == 'pull_request' && matrix.debuggable == 'debuggable'
uses: mxschmitt/action-tmate@v3 I see that the current workflow isn't triggering during pull_requests though, but that can be enabled. This is how i trigger tests related to another helm chart: https://github.com/yuvipanda/jupyterhub-ssh/blob/a61098162014f5a8c8ad3759273345838873619c/.github/workflows/test-chart.yaml#L6-L24 |
Thanks @consideRatio Just debugged this, the issue is with docker image, its pulling an image that doesn't exists in k3d (maybe not imported properly):
|
I think I understand the problem now, I shall create a PR soon. |
What happened:
The Kubernetes tests are failing in the CI (GitHub Actions)
https://github.com/dask/dask-gateway/runs/3161766008
What you expected to happen:
The Kubernetes tests passing.
I think the first step is to have more logging on why it is failing. Some of this GitHub Actions recipes suggested by @consideRatio might be useful: #408 (comment)
Current logs (from the CI):
The text was updated successfully, but these errors were encountered: