bigquery.it.ITBigQueryTest: testExecuteSelectDefaultConnectionSettings failed

[flaky-bot]

This test failed!

To configure my behavior, see the Flaky Bot documentation.

If I'm commenting on this issue too often, add the flakybot: quiet label and
I will stop commenting.

---

commit: 1de3474
buildURL: Build Status, Sponge
status: failed

Test output

java.lang.NullPointerException
	at com.google.cloud.bigquery.Schema.fromPb(Schema.java:96)
	at com.google.cloud.bigquery.ConnectionImpl.getSubsequentQueryResultsWithJob(ConnectionImpl.java:685)
	at com.google.cloud.bigquery.ConnectionImpl.queryRpc(ConnectionImpl.java:327)
	at com.google.cloud.bigquery.ConnectionImpl.executeSelect(ConnectionImpl.java:195)
	at com.google.cloud.bigquery.it.ITBigQueryTest.testExecuteSelectDefaultConnectionSettings(ITBigQueryTest.java:2356)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
	at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:299)
	at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:293)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.lang.Thread.run(Thread.java:750)

[prash-mi]

PR #2106 should fix it but it is blocked due to b/235591056

[flaky-bot]

Looks like this issue is flaky. 😟

I'm going to leave this open and stop commenting.

A human should fix and close this.

---

When run at the same commit (1de3474), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge).

[prash-mi]

Update: created b/236558227 to see if it can be addressed at the backend, if so then we will not need PR#2106 which is a workaround

[prash-mi]

Fixed with #2106