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

Flaky test TestHadoopCommits > testConcurrentFastAppends(File) #11047

Closed
1 of 3 tasks
manuzhang opened this issue Aug 30, 2024 · 2 comments
Closed
1 of 3 tasks

Flaky test TestHadoopCommits > testConcurrentFastAppends(File) #11047

manuzhang opened this issue Aug 30, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@manuzhang
Copy link
Collaborator

Apache Iceberg version

main (development)

Query engine

None

Please describe the bug 🐞

14:26:54 TestHadoopCommits > testConcurrentFastAppends(File) FAILED
14:26:54     org.awaitility.core.ConditionTimeoutException: Condition with lambda expression in org.apache.iceberg.hadoop.TestHadoopCommits that uses java.util.concurrent.atomic.AtomicInteger, java.util.concurrent.atomic.AtomicIntegerint, intint was not fulfilled within 10 seconds.
14:26:54         at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
14:26:54         at org.awaitility.core.CallableCondition.await(CallableCondition.java:78)
14:26:54         at org.awaitility.core.CallableCondition.await(CallableCondition.java:26)
14:26:54         at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:985)
14:26:54         at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:954)
14:26:54         at org.apache.iceberg.hadoop.TestHadoopCommits.lambda$testConcurrentFastAppends$3(TestHadoopCommits.java:448)

Willingness to contribute

  • I can contribute a fix for this bug independently
  • I would be willing to contribute a fix for this bug with guidance from the Iceberg community
  • I cannot contribute a fix for this bug at this time
@manuzhang
Copy link
Collaborator Author

Fixed by #11654

@kevinjqliu
Copy link
Contributor

Seeing this issue pop up again in CI #11923 (comment)

I also had trouble with this while verifying the 1.7.2RC0 candidate

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants