[ 
https://issues.apache.org/jira/browse/NIFI-12768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joe Witt reopened NIFI-12768:
-----------------------------

> Intermittent Failures in TestListFile.testFilterAge
> ---------------------------------------------------
>
>                 Key: NIFI-12768
>                 URL: https://issues.apache.org/jira/browse/NIFI-12768
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 2.0.0-M2
>            Reporter: David Handermann
>            Assignee: David Handermann
>            Priority: Major
>             Fix For: 2.0.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The TestListFIle class has not changed substantively in quite some time, but 
> it has begun to fail more recently across multiple platforms on GitHub Action 
> runners.
> The {{testFilterAge}} method often fails with the same stack trace:
> {noformat}
> Error:  org.apache.nifi.processors.standard.TestListFile.testFilterAge -- 
> Time elapsed: 6.436 s <<< FAILURE!
> org.opentest4j.AssertionFailedError: expected: <age2.txt> but was: <age1.txt>
>       at 
> org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
>       at 
> org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
>       at 
> org.junit.jupiter.api.AssertEquals.failNotEqual(AssertEquals.java:197)
>       at 
> org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:182)
>       at 
> org.junit.jupiter.api.AssertEquals.assertEquals(AssertEquals.java:177)
>       at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:1141)
>       at 
> org.apache.nifi.processors.standard.TestListFile.testFilterAge(TestListFile.java:331)
>       at java.base/java.lang.reflect.Method.invoke(Method.java:580)
>       at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
>       at java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
> {noformat}
> The test method use recalculated timestamps to set file modification time, so 
> the problem appears to be related to these timing calculations.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to