[
https://issues.apache.org/jira/browse/YARN-11926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18058554#comment-18058554
]
Chris Nauroth commented on YARN-11926:
--------------------------------------
[~qwerty2.0] , thank you for reporting this. Are you interested in sending a
pull request? I think it would be fine to push out the timestamps 5 years to
unblock current test runs quickly. Alternatively, if you felt like changing the
test code so that it could do "now + 5 years" dynamically, that would be good
too.
If you're not interested in sending a pull request, that's totally understood,
and then I'll probably update the hard-coded timestamps myself.
> hadoop-yarn-server-resourcemanager: TestRMWebServicesReservation fails due to
> outdated timestamps
> -------------------------------------------------------------------------------------------------
>
> Key: YARN-11926
> URL: https://issues.apache.org/jira/browse/YARN-11926
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 3.4.1
> Reporter: Ronald Macmaster
> Priority: Minor
>
> We've noticed consistent build failures for this test class on the hadoop 3.4
> branch.
> It looks like timestamps that were chosen 10 years into the future around
> 2015 have now expired as of late 2025.
> Tweaking these timestamps in update-reservation.json to a much later date
> seems to fix the test class run locally, but it doesn't seem like the most
> future-proof solution. Nonetheless, it would be a palatable and trivial fix.
> A better way to solve this might also be to use offsets from the current
> system time in the test class.
> [outdated
> timestamps|https://github.com/apache/hadoop/blob/8222ac0f546911b387b6a141e06dd8bf5306d565/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/resources/update-reservation.json#L6-L7]
> that fail TestRMWebServicesReservation.java
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
