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

ITBiqueryTest.testConnectionCancel failing with AssertionError on Kokoro GraalVM job #1916

Closed
mpeddada1 opened this issue Mar 10, 2022 · 6 comments
Assignees
Labels
api: bigquery Issues related to the googleapis/java-bigquery API. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. 🚨 This issue needs some love. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@mpeddada1
Copy link
Contributor

The ITBigqueryTest.testConnectionCancel is failing with the following error for the Native Image testing Kokoro job. This failure was first discovered in #1374.

[ERROR] testConnectionCancel  Time elapsed: 5.127 s  <<< FAILURE!
java.lang.AssertionError
	at com.google.cloud.bigquery.it.ITBigQueryTest.testConnectionCancel(ITBigQueryTest.java:2610)

Note that the failure occurs before the Native Image build step.

However, running this test locally with mvn test -Pnative results in a successful build.

Screen Shot 2022-03-10 at 12 16 21 PM

Creating this issue to keep track of similar errors in the future.

cc @stephaniewang526

@product-auto-label product-auto-label bot added the api: bigquery Issues related to the googleapis/java-bigquery API. label Mar 10, 2022
@stephaniewang526 stephaniewang526 added the type: process A process-related concern. May include testing, release, or the like. label Mar 10, 2022
@stephaniewang526
Copy link
Contributor

stephaniewang526 commented Apr 13, 2022

Hi @mpeddada1, any update on this?

@stephaniewang526 stephaniewang526 added type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. and removed type: process A process-related concern. May include testing, release, or the like. labels Apr 16, 2022
@yoshi-automation yoshi-automation added the 🚨 This issue needs some love. label Apr 16, 2022
@mpeddada1
Copy link
Contributor Author

Hi @stephaniewang526, I've just double checked that this passes locally. We used to run into this error in #1374 before we even got to the Native Image build stage. The good news is that, with the latest run of the Kokoro Native Image presubmit, the test in question passed (which makes me think that the AssertionError was transient). However, it currently fails at the native image build stage with:

Error: Substition: com.google.api.client.googleapis.services.AbstractGoogleClientRequest$ApiClientVersion.toString() conflicts with previously registered: com.google.api.client.googleapis.services.AbstractGoogleClientRequest$ApiClientVersion.toString()

The solution for this will be to upgrade java-shared-config with a newer version of native-image-support-java googleapis/java-shared-config#465

@stephaniewang526
Copy link
Contributor

Thank you @mpeddada1 for the thorough investigation! Any idea on the ETA of the newer version of java-shared-config and what version we should watch out for?

@mpeddada1
Copy link
Contributor Author

Thanks @stephaniewang526! Looks like you've already merged the version upgrade PR in: #2000. We can try rebasing the PR now.

@suztomo
Copy link
Member

suztomo commented Apr 20, 2022

Memo

Screen Shot 2022-04-20 at 5 08 18 PM

@stephaniewang526
Copy link
Contributor

Yes, thank you! Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: bigquery Issues related to the googleapis/java-bigquery API. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. 🚨 This issue needs some love. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

No branches or pull requests

4 participants