apache / apache/hudi

Fix Flaky test TestInputFormat. testReadIncrementally

Open
#16,116 0 comments 0 reactions 0 assignees View on GitHub
area:tests from-jira priority:high
Dominant language
Java
Stars
6.2k
Forks
2.5k
Avg merge
2d 8h
Merged PRs (30d)
111

Description

TestInputFormat. testReadIncrementally

 

Ref logs:

[https://dev.azure.com/apache-hudi-ci-org/785b6ef4-2f42-4a89-8f0e-5f0d7039a0cc/_apis/build/builds/18675/logs/30]

 
{code:java}
2023-07-19T04:05:05.6883452Z [ERROR] Tests run: 35, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 69.184 s <<< FAILURE! - in org.apache.hudi.table.format.TestInputFormat
2023-07-19T04:05:05.6884096Z [ERROR] testReadIncrementally{HoodieTableType}[2] Time elapsed: 2.27 s <<< FAILURE!
2023-07-19T04:05:05.6884816Z java.lang.AssertionError:
2023-07-19T04:05:05.6884917Z
2023-07-19T04:05:05.6885695Z Expected: is "[+I[id3, Danny, 23, 1970-01-01T00:00:00.003, par1], +I[id4, Danny, 23, 1970-01-01T00:00:00.004, par1], +I[id5, Danny, 23, 1970-01-01T00:00:00.005, par1], +I[id6, Danny, 23, 1970-01-01T00:00:00.006, par1]]"
2023-07-19T04:05:05.6886368Z but: was "[+I[id5, Danny, 23, 1970-01-01T00:00:00.005, par1], +I[id6, Danny, 23, 1970-01-01T00:00:00.006, par1]]"
2023-07-19T04:05:05.6886671Z at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:20)
2023-07-19T04:05:05.6886946Z at org.hamcrest.MatcherAssert.assertThat(MatcherAssert.java:8)
2023-07-19T04:05:05.6887218Z at org.apache.hudi.utils.TestData.assertRowDataEquals(TestData.java:641)
2023-07-19T04:05:05.6887525Z at org.apache.hudi.table.format.TestInputFormat.testReadIncrementally(TestInputFormat.java:793)
2023-07-19T04:05:05.6887803Z at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
2023-07-19T04:05:05.6888065Z at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
2023-07-19T04:05:05.6888363Z at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
2023-07-19T04:05:05.6888638Z at java.lang.reflect.Method.invoke(Method.java:498)
2023-07-19T04:05:05.6888910Z at org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:688)
2023-07-19T04:05:05.6889210Z at org.junit.jupiter.engine.execution.MethodInvocation.proceed(MethodInvocation.java:60)
2023-07-19T04:05:05.6889575Z at org.junit.jupiter.engine.execution.InvocationInterceptorChain$ValidatingInvocation.proceed(InvocationInterceptorChain.java:131)
2023-07-19T04:05:05.6889936Z at org.junit.jupiter.engine.extension.TimeoutExtension.intercept(TimeoutExtension.java:149)
2023-07-19T04:05:05.6890523Z at org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestableMethod(TimeoutExtension.java:140)
2023-07-19T04:05:05.6890875Z at org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestTemplateMethod(TimeoutExtension.java:92)
2023-07-19T04:05:05.6891262Z at org.junit.jupiter.engine.execution.ExecutableInvoker$ReflectiveInterceptorCall.lambda$ofVoidMethod$0(ExecutableInvoker.java:115)
2023-07-19T04:05:05.6891623Z at org.junit.jupiter.engine.execution.ExecutableInvoker.lambda$invoke$0(ExecutableInvoker.java:105)
2023-07-19T04:05:05.6891996Z at org.junit.jupiter.engine.execution.InvocationInterceptorChain$InterceptedInvocation.proceed(InvocationInterceptorChain.java:106)
2023-07-19T04:05:05.6892429Z at org.junit.jupiter.engine.execution.InvocationInterceptorChain.proceed(InvocationInterceptorChain.java:64)
2023-07-19T04:05:05.6892794Z at org.junit.jupiter.engine.execution.InvocationInterceptorChain.chainAndInvoke(InvocationInterceptorChain.java:45)
2023-07-19T04:05:05.6893144Z at org.junit.jupiter.engine.execution.InvocationInterceptorChain.invoke(InvocationInterceptorChain.java:37) {code}

## JIRA info

- Link: https://issues.apache.org/jira/browse/HUDI-6577
- Type: Test

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with org.apache.hudi.table.format.TestInputFormat.testReadIncrementally at line 793 and inspect the failure from the referenced CI log. Run this test repeatedly to identify why id3 and id4 are sometimes omitted; done means the test reliably produces the expected four records for both table types.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
stream-processing, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.