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.

Sign up for GitHub

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

Jump to bottom

spanner.it.slow.ITBackupTest: test01_Backups failed #2720

Open
flaky-bot bot opened this issue Nov 1, 2023 · 20 comments
Open

spanner.it.slow.ITBackupTest: test01_Backups failed #2720

flaky-bot bot opened this issue Nov 1, 2023 · 20 comments
Assignees
@rahul2393
Labels
api: spanner Issues related to the googleapis/java-spanner API. flakybot: flaky Tells the Flaky Bot not to close or comment on this issue. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@flaky-bot
Copy link

flaky-bot bot commented Nov 1, 2023

Note: #2410 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.

commit: e320753
buildURL: Build Status, Sponge
status: failed

Test output
java.lang.AssertionError
	at org.junit.Assert.fail(Assert.java:87)
	at org.junit.Assert.assertTrue(Assert.java:42)
	at org.junit.Assert.assertTrue(Assert.java:53)
	at com.google.cloud.spanner.it.slow.ITBackupTest.testPagination(ITBackupTest.java:720)
	at com.google.cloud.spanner.it.slow.ITBackupTest.test01_Backups(ITBackupTest.java:358)
	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.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
	at org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
	at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
	at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
	at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
	at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
	at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
	at org.junit.rules.RunRules.evaluate(RunRules.java:20)
	at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
	at org.junit.runners.Suite.runChild(Suite.java:128)
	at org.junit.runners.Suite.runChild(Suite.java:27)
	at org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
	at org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
	at org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:413)
	at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:49)
	at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:120)
	at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:95)
	at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
	at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:69)
	at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:146)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:385)
	at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:162)
	at org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:507)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:495)
@flaky-bot flaky-bot bot added flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Nov 1, 2023
@product-auto-label product-auto-label bot added the api: spanner Issues related to the googleapis/java-spanner API. label Nov 1, 2023
@flaky-bot Flaky Bot
Copy link
Author

flaky-bot bot commented Nov 10, 2023

commit: 7e142ff
buildURL: Build Status, Sponge
status: failed

@flaky-bot Flaky Bot
Copy link
Author

flaky-bot bot commented Nov 11, 2023

commit: 8618042
buildURL: Build Status, Sponge
status: failed

@flaky-bot Flaky Bot
Copy link
Author

flaky-bot bot commented Nov 15, 2023

commit: 7820be8
buildURL: Build Status, Sponge
status: failed

@flaky-bot Flaky Bot
Copy link
Author

flaky-bot bot commented Nov 16, 2023

commit: bf06ef1
buildURL: Build Status, Sponge
status: failed

@flaky-bot Flaky Bot
Copy link
Author

flaky-bot bot commented Nov 24, 2023

commit: 3cba4c6
buildURL: Build Status, Sponge
status: failed

@flaky-bot Flaky Bot
Copy link
Author

flaky-bot bot commented Nov 27, 2023

commit: 4b17331
buildURL: Build Status, Sponge
status: failed

@flaky-bot Flaky Bot
Copy link
Author

flaky-bot bot commented Nov 30, 2023

commit: 9ea4f4f
buildURL: Build Status, Sponge
status: failed

@flaky-bot Flaky Bot
Copy link
Author

flaky-bot bot commented Dec 2, 2023

commit: c895c92
buildURL: Build Status, Sponge
status: failed

@flaky-bot Flaky Bot
Copy link
Author

flaky-bot bot commented Dec 9, 2023

commit: 20562d4
buildURL: Build Status, Sponge
status: failed

@flaky-bot Flaky Bot
Copy link
Author

flaky-bot bot commented Dec 13, 2023

commit: e62b4fe
buildURL: Build Status, Sponge
status: failed

@flaky-bot Flaky Bot
Copy link
Author

flaky-bot bot commented Dec 15, 2023

commit: 99ae565
buildURL: Build Status, Sponge
status: failed

@flaky-bot Flaky Bot
Copy link
Author

flaky-bot bot commented Dec 16, 2023

commit: c56c569
buildURL: Build Status, Sponge
status: failed

@flaky-bot Flaky Bot
Copy link
Author

flaky-bot bot commented Dec 21, 2023

commit: 247946e
buildURL: Build Status, Sponge
status: failed

@flaky-bot Flaky Bot
Copy link
Author

flaky-bot bot commented Dec 27, 2023

commit: 21f5eba
buildURL: Build Status, Sponge
status: failed

@flaky-bot Flaky Bot
Copy link
Author

flaky-bot bot commented Jan 4, 2024

commit: 4a13583
buildURL: Build Status, Sponge
status: failed

@flaky-bot Flaky Bot
Copy link
Author

flaky-bot bot commented Jan 6, 2024

commit: 58f94b2
buildURL: Build Status, Sponge
status: failed

@flaky-bot Flaky Bot
Copy link
Author

flaky-bot bot commented Jan 13, 2024

commit: 19f75d8
buildURL: Build Status, Sponge
status: failed

@flaky-bot flaky-bot bot added the flakybot: flaky Tells the Flaky Bot not to close or comment on this issue. label Jan 18, 2024
@flaky-bot Flaky Bot
Copy link
Author

flaky-bot bot commented Jan 18, 2024

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 (19f75d8), this test passed in one build (Build Status, Sponge) and failed in another build (Build Status, Sponge).

@arpan14 arpan14 assigned rahul2393 and unassigned arpan14 Apr 15, 2024
@rahul2393
Copy link
Contributor

Closing since issue is not happening for long time.

@flaky-bot flaky-bot bot reopened this May 6, 2024
@flaky-bot Flaky Bot
Copy link
Author

flaky-bot bot commented May 6, 2024

Oops! Looks like this issue is still flaky. It failed again. 😬

I reopened the issue, but a human will need to close it again.

commit: 5394139
buildURL: Build Status, Sponge
status: failed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rahul2393 rahul2393

Labels
api: spanner Issues related to the googleapis/java-spanner API. flakybot: flaky Tells the Flaky Bot not to close or comment on this issue. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@arpan14 @rahul2393