[ https://issues.apache.org/jira/browse/HDFS-16625?focusedWorklogId=781000&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-781000 ]
ASF GitHub Bot logged work on HDFS-16625: ----------------------------------------- Author: ASF GitHub Bot Created on: 14/Jun/22 06:40 Start Date: 14/Jun/22 06:40 Worklog Time Spent: 10m Work Description: saintstack commented on PR #4414: URL: https://github.com/apache/hadoop/pull/4414#issuecomment-1154777686 Javadoc build fails are unrelated to this PR's add of a check to two unit tests. The TestRollingUpgrade failure we've flagged already as pre-existing condition and the TestClientProtocolForPipelineRecovery failure is not a test changed here. Let me merge. Issue Time Tracking ------------------- Worklog Id: (was: 781000) Time Spent: 1h (was: 50m) > Unit tests aren't checking for PMDK availability > ------------------------------------------------ > > Key: HDFS-16625 > URL: https://issues.apache.org/jira/browse/HDFS-16625 > Project: Hadoop HDFS > Issue Type: Test > Components: test > Affects Versions: 3.4.0, 3.3.4 > Reporter: Steve Vaughan > Priority: Blocker > Labels: pull-request-available > Time Spent: 1h > Remaining Estimate: 0h > > There are unit tests that require native PMDK libraries which aren't checking > if the library is available, resulting in unsuccessful test. Adding the > following in the test setup addresses the problem. > {code:java} > assumeTrue ("Requires PMDK", NativeIO.POSIX.isPmdkAvailable()); {code} -- This message was sent by Atlassian Jira (v8.20.7#820007) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org