This repository was archived by the owner on Sep 25, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Sep 25, 2026. It is now read-only.
com.example.storage.ITBucketSnippets: testConfigureBucketCors failed #1301
Description
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: 48b99be
buildURL: Build Status, Sponge
status: failed
Test output
java.lang.NullPointerException at com.example.storage.bucket.ConfigureBucketCors.configureBucketCors(ConfigureBucketCors.java:67) at com.example.storage.ITBucketSnippets.testConfigureBucketCors(ITBucketSnippets.java:499) 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.RunAfters.evaluate(RunAfters.java:27) 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)
Metadata
Metadata
Assignees
Labels
Issues related to the googleapis/java-storage API.Tells the Flaky Bot not to close or comment on this issue.An issue filed by the Flaky Bot. Should not be added manually.Moderately-important priority. Fix may not be included in next release.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Activity
fix(java): run Maven in plain console-friendly mode (googleapis#1301) (…
flaky-bot commentedon Mar 18, 2022
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 (48b99be), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge).