LuciferYang commented on PR #51982: URL: https://github.com/apache/spark/pull/51982#issuecomment-3180123263
Actually, at first I also thought it was a test timeout, but after further investigation, I found that wasn't the case. From the link you provided, we can click the `view raw log` button to jump to the raw log, where we can see the following log entries: - https://github.com/bothra90/spark/actions/runs/16890007851/job/47847187857 - https://productionresultssa17.blob.core.windows.net/actions-results/503f3eff-310b-4318-baf1-05bb09b4c767/workflow-job-run-cd4a0ec5-046b-5e46-bf3d-5275fd324cde/logs/job/job-logs.txt?rsct=text%2Fplain&se=2025-08-12T16%3A23%3A55Z&sig=ZeCDltw1656cFR0hprOSzNtfxPUsYaRZNisojapREO0%3D&ske=2025-08-13T02%3A05%3A47Z&skoid=ca7593d4-ee42-46cd-af88-8b886a2f84eb&sks=b&skt=2025-08-12T14%3A05%3A47Z&sktid=398a6654-997b-47e9-b12b-9515b896b4de&skv=2025-05-05&sp=r&spr=https&sr=b&st=2025-08-12T16%3A13%3A50Z&sv=2025-05-05 ``` 2025-08-11T20:35:52.1545306Z # If you would like to submit a bug report, please visit: 2025-08-11T20:35:52.1546207Z # http://www.azul.com/support/ 2025-08-11T20:35:52.1546675Z # The crash happened outside the Java Virtual Machine in native code. 2025-08-11T20:35:52.1547085Z # See problematic frame for where to report the bug. 2025-08-11T20:35:52.1547369Z # 2025-08-11T20:36:50.1651953Z Warning: Unable to read from client, please check on client for further details of the problem. 2025-08-11T21:26:57.0049131Z 2025-08-11T21:26:59.0048819Z Session terminated, killing shell... ...killed. 2025-08-11T21:26:59.0566823Z ##[error]The operation was canceled. 2025-08-11T21:26:59.0899479Z ##[group]Run actions/upload-artifact@v4 ``` From the logs, we can observe the following: 1. At 2025-08-11T20:35:52, RocksDB crashed. 2. At 2025-08-11T21:26:59, the current GitHub Action Task for the test was terminated. Between 2025-08-11T20:35:52 and 2025-08-11T21:26:59, only one log entry was printed: `Warning: Unable to read from client, please check on client for further details of the problem.` No other test cases were executed during this period. Therefore, I believe that after the RocksDB crash, the entire testing process became stuck until the test task timed out, and this timeout was triggered by the RocksDB crash. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
