amahussein commented on pull request #2581:
URL: https://github.com/apache/hadoop/pull/2581#issuecomment-756530407
> The latest commit seemed to introduce errors.
>
> ```
> $ mvn test -Dtest='TestDS*'
> ...
> [ERROR] Errors:
> [ERROR]
TestDSTimelineV20>DistributedShellBaseTest.setup:159->DistributedShellBaseTest.setupInternal:476
» YarnRuntime
> [ERROR]
TestDSTimelineV20>DistributedShellBaseTest.setup:159->DistributedShellBaseTest.setupInternal:476
» YarnRuntime
> [ERROR]
TestDSTimelineV20>DistributedShellBaseTest.setup:159->DistributedShellBaseTest.setupInternal:476
» YarnRuntime
> [ERROR]
TestDSTimelineV20>DistributedShellBaseTest.setup:159->DistributedShellBaseTest.setupInternal:476
» YarnRuntime
> [ERROR]
TestDSTimelineV20>DistributedShellBaseTest.setup:159->DistributedShellBaseTest.setupInternal:476
» YarnRuntime
> [ERROR]
TestDSTimelineV20>DistributedShellBaseTest.setup:159->DistributedShellBaseTest.setupInternal:476
» YarnRuntime
> [INFO]
> [ERROR] Tests run: 40, Failures: 0, Errors: 6, Skipped: 0
> ```
Hey @iwasakims!
I was looking into this failure. TestDSTimelineV20 fails when it runs after
TestDSTimelineV15.
The exception is thrown as follows
```
at
org.apache.hadoop.yarn.server.timelineservice.storage.FileSystemTimelineWriterImpl.mkdirsWithRetries(FileSystemTimelineWriterImpl.java:214)
at
org.apache.hadoop.yarn.server.timelineservice.storage.FileSystemTimelineWriterImpl.serviceStart(FileSystemTimelineWriterImpl.java:188)
```
This could be something that missing in the configurations of the unitTest
or a bug in either timelineserviceV1.5 or timelineserviceV2.0
I have verified that all the configurations are maintained when the code is
split.
The reason this failure appears only now could be due to the fact that
having all the tests in one file did not let V1.5 tests run immediately before
V2.0 tests.
I haven't figured it yet, but probably this would need filing another jira.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
