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

Update xla_docker_build.tf #6488

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from
Draft

Update xla_docker_build.tf #6488

wants to merge 1 commit into from

Conversation

ManfeiBai
Copy link
Collaborator

@ManfeiBai ManfeiBai commented Feb 7, 2024

possible fix for this issue:

(Reading database ... 106380 files and directories currently installed.)
Step #4 - "run_e2e_tests": Removing google-cloud-cli-gke-gcloud-auth-plugin (463.0.0-0) ...
Step #4 - "run_e2e_tests": + apt-get -y install google-cloud-sdk-gke-gcloud-auth-plugin -o DPkg::options::=--force-overwrite
Step #4 - "run_e2e_tests": Reading package lists...
Step #4 - "run_e2e_tests": Building dependency tree...
Step #4 - "run_e2e_tests": Reading state information...
Step #4 - "run_e2e_tests": Some packages could not be installed. This may mean that you have
Step #4 - "run_e2e_tests": requested an impossible situation or if you are using the unstable
Step #4 - "run_e2e_tests": distribution that some required packages have not yet been created
Step #4 - "run_e2e_tests": or been moved out of Incoming.
Step #4 - "run_e2e_tests": The following information may help to resolve the situation:
Step #4 - "run_e2e_tests": 
Step #4 - "run_e2e_tests": The following packages have unmet dependencies:
Step #4 - "run_e2e_tests":  google-cloud-cli-gke-gcloud-auth-plugin : Breaks: google-cloud-sdk-gke-gcloud-auth-plugin but 463.0.0-0 is to be installed
Step #4 - "run_e2e_tests": E: Unable to correct problems, you have held broken packages.
Finished Step #4 - "run_e2e_tests"
ERROR
ERROR: build step 4 "google/cloud-sdk" failed: step exited with non-zero status: 100

error log

error disappear after #6485, maybe env changed?

@ManfeiBai
Copy link
Collaborator Author

wait for TPUCI result, although this change will only affect after merged;

this PR will be closed after gain the result, because this error disappear in the current TPUCI now, maybe the testing env has changed very quickly?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant