What’s going on with CI now? I’m not impressed by a random Windows failure 
breaking the entire build, especially one that’s apparently been failing for a 
while apparently. Dependabot??
—
Matt Sicker

> Begin forwarded message:
> 
> From: Matt Sicker <notificati...@github.com>
> Subject: [apache/logging-log4j2] Run failed: build - master (1be6c1e)
> Date: May 13, 2022 at 15:51:50 CDT
> To: apache/logging-log4j2 <logging-log...@noreply.github.com>
> Cc: Ci activity <ci_activ...@noreply.github.com>
> Reply-To: apache/logging-log4j2 <nore...@github.com>
> 
>  
> 
> [apache/logging-log4j2] build workflow run
>  
> 
>  
> build: Some jobs were not successful
>  
> View workflow run 
> <https://github.com/apache/logging-log4j2/actions/runs/2321667155>
>  
>       
> build / build (ubuntu-latest) 
> Cancelled
>   2 <https://github.com/apache/logging-log4j2/actions/runs/2321667155>
>       
> build / build (windows-latest) 
> Failed in 23 minutes and 29 seconds
>   1 <https://github.com/apache/logging-log4j2/actions/runs/2321667155>
>       
> build / build (macos-latest) 
> Cancelled
>   2 <https://github.com/apache/logging-log4j2/actions/runs/2321667155>
>       
> build / deploy 
> Skipped
>  
>  
> 
> —
> You are receiving this because this workflow ran on your branch.
> Manage your GitHub Actions notifications 
> <https://github.com/settings/notifications>
>  
> GitHub, Inc. ・88 Colin P Kelly Jr Street ・San Francisco, CA 94107
> 

Reply via email to