mridulm commented on PR #2646:
URL: https://github.com/apache/celeborn/pull/2646#issuecomment-2251464677

   The test failure is unrelated to this PR:
   ```
   DeviceMonitorSuite:
   - init
   - register/unregister/notify/report
   0worker-device-checker-1
   24/07/25 20:09:13,757 ERROR [worker-disk-checker] LocalDeviceMonitor: /mnt 
high_disk_usage error, notify observers
   24/07/25 20:09:13,982 ERROR [ScalaTest-main-running-DeviceMonitorSuite] 
Utils: TimeoutException in thread ScalaTest-main-running-DeviceMonitorSuite, 
error message: none
   1worker-device-checker-3
   24/07/25 20:09:14,984 ERROR [ScalaTest-main-running-DeviceMonitorSuite] 
Utils: TimeoutException in thread ScalaTest-main-running-DeviceMonitorSuite, 
error message: none
   2worker-device-checker-4
   24/07/25 20:09:15,985 ERROR [ScalaTest-main-running-DeviceMonitorSuite] 
Utils: TimeoutException in thread ScalaTest-main-running-DeviceMonitorSuite, 
error message: none
   - tryWithTimeoutAndCallback
   - monitor non-critical error metrics *** FAILED ***
     java.lang.AssertionError: expected:<2> but was:<1>
     at org.junit.Assert.fail(Assert.java:89)
     at org.junit.Assert.failNotEquals(Assert.java:835)
     at org.junit.Assert.assertEquals(Assert.java:120)
     at org.junit.Assert.assertEquals(Assert.java:146)
     at 
org.apache.celeborn.service.deploy.worker.storage.DeviceMonitorSuite.$anonfun$new$22(DeviceMonitorSuite.scala:405)
     at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.java:23)
     at org.mockito.MockitoEnhancer.withObject(MockitoAPI.scala:632)
     at org.mockito.MockitoEnhancer.withObject$(MockitoAPI.scala:620)
     at org.mockito.MockitoSugar$.withObject(MockitoSugar.scala:8)
     at org.mockito.MockitoEnhancer.withObjectMocked(MockitoAPI.scala:607)
     ...
   ```


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to