alamb opened a new issue, #21938:
URL: https://github.com/apache/datafusion/issues/21938

   ### Describe the bug
   
   I have noticed recently that often CI checks fail on main (not PRs). For 
example, looking at: https://github.com/apache/datafusion/commits/main/
   
   <img width="1461" height="827" alt="Image" 
src="https://github.com/user-attachments/assets/f7a7bf11-224b-44e2-94d1-e6661facfbe6";
 />
   
   If you look at what is failing it is that these jobs are "cancelled"
   
   <img width="1456" height="847" alt="Image" 
src="https://github.com/user-attachments/assets/b8a67d82-dc95-45ca-90bd-5ba09b809c58";
 />
   
   
   ### To Reproduce
   
   I am not sure why they don't pass or fail all the time. Maybe it is related 
to if we have merged another PR within a short time?
   
   Here is an example failure:
   https://github.com/apache/datafusion/actions/runs/25127768271/job/73645414258
   ```
   Disk space before cleanup:
   Filesystem      Size  Used Avail Use% Mounted on
   overlay         145G   59G   86G  41% /
   tmpfs            64M     0   64M   0% /dev
   shm              64M     0   64M   0% /dev/shm
   /dev/root       145G   59G   86G  41% /__t
   tmpfs           3.2G  1.1M  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
   context canceled
   Error: The operation was canceled.
   
   ```
   
   It seems to only affect "Dependencies" jobs
   
   ### Expected behavior
   
   
   
   
   ### Additional context
   
   _No response_


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

Reply via email to