[jira] [Commented] (FLINK-34449) Flink build took too long

2024-02-28 Thread Matthias Pohl (Jira) 


[ 
https://issues.apache.org/jira/browse/FLINK-34449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17821967#comment-17821967
 ] 

Matthias Pohl commented on FLINK-34449:
---

This time, it happened in the caching step:
https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=57957=logs=87489130-75dc-54e4-1f45-80c30aa367a3=5f5e3bcf-c82b-57ca-7f80-f293d0ad4448=1

> Flink build took too long
> -
>
> Key: FLINK-34449
> URL: https://issues.apache.org/jira/browse/FLINK-34449
> Project: Flink
>  Issue Type: Bug
>  Components: Build System / CI, Test Infrastructure
>Affects Versions: 1.17.2
>Reporter: Matthias Pohl
>Priority: Major
>  Labels: test-stability
>
> We saw a timeout when building Flink in e2e1 stage. No logs are available to 
> investigate the issue:
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=57551=logs=bbb1e2a2-a43c-55c8-fb48-5cfe7a8a0ca6
> {code}
> Nothing to show. Final logs are missing. This can happen when the job is 
> cancelled or times out.
> {code}
> I'd consider this an infrastructure issue but created the Jira issue for 
> documentation purposes. Let's see whether that pops up again.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (FLINK-34449) Flink build took too long

2024-02-23 Thread Matthias Pohl (Jira) 


[ 
https://issues.apache.org/jira/browse/FLINK-34449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17820023#comment-17820023
 ] 

Matthias Pohl commented on FLINK-34449:
---

https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=57807=logs=87489130-75dc-54e4-1f45-80c30aa367a3=73da6d75-f30d-5d5a-acbe-487a9dcff678

> Flink build took too long
> -
>
> Key: FLINK-34449
> URL: https://issues.apache.org/jira/browse/FLINK-34449
> Project: Flink
>  Issue Type: Bug
>  Components: Build System / CI, Test Infrastructure
>Affects Versions: 1.17.2
>Reporter: Matthias Pohl
>Priority: Major
>  Labels: test-stability
>
> We saw a timeout when building Flink in e2e1 stage. No logs are available to 
> investigate the issue:
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=57551=logs=bbb1e2a2-a43c-55c8-fb48-5cfe7a8a0ca6
> {code}
> Nothing to show. Final logs are missing. This can happen when the job is 
> cancelled or times out.
> {code}
> I'd consider this an infrastructure issue but created the Jira issue for 
> documentation purposes. Let's see whether that pops up again.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Commented] (FLINK-34449) Flink build took too long

2024-02-22 Thread Matthias Pohl (Jira) 


[ 
https://issues.apache.org/jira/browse/FLINK-34449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17819649#comment-17819649
 ] 

Matthias Pohl commented on FLINK-34449:
---

https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=57761=logs=87489130-75dc-54e4-1f45-80c30aa367a3=73da6d75-f30d-5d5a-acbe-487a9dcff678

> Flink build took too long
> -
>
> Key: FLINK-34449
> URL: https://issues.apache.org/jira/browse/FLINK-34449
> Project: Flink
>  Issue Type: Bug
>  Components: Build System / CI, Test Infrastructure
>Reporter: Matthias Pohl
>Priority: Major
>  Labels: test-stability
>
> We saw a timeout when building Flink in e2e1 stage. No logs are available to 
> investigate the issue:
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=57551=logs=bbb1e2a2-a43c-55c8-fb48-5cfe7a8a0ca6
> {code}
> Nothing to show. Final logs are missing. This can happen when the job is 
> cancelled or times out.
> {code}
> I'd consider this an infrastructure issue but created the Jira issue for 
> documentation purposes. Let's see whether that pops up again.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)