zhengruifeng commented on PR #53332: URL: https://github.com/apache/spark/pull/53332#issuecomment-3636963926
@pan3793 @sarutak compared to the PR build https://github.com/pan3793/spark/actions/runs/20052775576/job/57552885970, ``` Filesystem Size Used Avail Use% Mounted on overlay 73G 65G 8.3G 89% / tmpfs 64M 0 64M 0% /dev shm 64M 0 64M 0% /dev/shm /dev/root 73G 65G 8.3G 89% /__t tmpfs 3.2G 1.2M 3.2G 1% /run/docker.sock tmpfs 7.9G 0 7.9G 0% /proc/acpi tmpfs 7.9G 0 7.9G 0% /proc/scsi tmpfs 7.9G 0 7.9G 0% /sys/firmware ``` the daily job https://github.com/apache/spark/actions/runs/20061148640/job/57538347388 seems have more disk space ``` Filesystem Size Used Avail Use% Mounted on overlay 72G 61G 11G 85% / tmpfs 64M 0 64M 0% /dev shm 64M 0 64M 0% /dev/shm /dev/root 72G 61G 11G 85% /__t tmpfs 3.2G 1.2M 3.2G 1% /run/docker.sock tmpfs 7.9G 0 7.9G 0% /proc/acpi tmpfs 7.9G 0 7.9G 0% /proc/scsi tmpfs 7.9G 0 7.9G 0% /sys/firmware ``` Maybe the `free_disk_space_container` is not up to day in PR build? I think we can just skip this test failure for now, and monitor the daily job. -- 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]
