Skip to content

Conversation

@jonathanmetzman
Copy link
Collaborator

Dont use old testing version

Dont use old testing version
@jonathanmetzman
Copy link
Collaborator Author

/gcbrun

@decoNR
Copy link
Collaborator

decoNR commented Dec 18, 2025

There is a CI error on All-Tests (clusterfuzz-testing-public), which appears to be related to the Datastore emulator's Java dependency.

Copy link
Contributor

@javanlacerda javanlacerda left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we use the latest? I think pinning a version is a safer approach.

@jonathanmetzman
Copy link
Collaborator Author

There is a CI error on All-Tests (clusterfuzz-testing-public), which appears to be related to the Datastore emulator's Java dependency.

I think it's a race condition unrelated to this PR.

@jonathanmetzman
Copy link
Collaborator Author

Should we use the latest? I think pinning a version is a safer approach.

If we're pinning I guess there's not harm in using Vitor's old image (I guess until it goes out of date). Do you think I should just abandon this PR or better to update to the most recent image?

Use the specific tag 000dc1f-202511191429 for the CI image in all steps.
Copy link
Contributor

@javanlacerda javanlacerda left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. We should just check the JAVA version that is failing.

@jonathanmetzman
Copy link
Collaborator Author

There is a CI error on All-Tests (clusterfuzz-testing-public), which appears to be related to the Datastore emulator's Java dependency.

I think it's a race condition unrelated to this PR.

I'm totally wrong, it is a java failure you were right

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.

3 participants