You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yun Gao (Jira)" <ji...@apache.org> on 2020/01/21 02:33:00 UTC

[jira] [Updated] (FLINK-15701) Allows transfer.sh to retry when fails to uploads logs

     [ https://issues.apache.org/jira/browse/FLINK-15701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yun Gao updated FLINK-15701:
----------------------------
    Summary: Allows transfer.sh to retry when fails to uploads logs  (was: Allows transfer.sh to retry when fails to uploads logs.)

> Allows transfer.sh to retry when fails to uploads logs
> ------------------------------------------------------
>
>                 Key: FLINK-15701
>                 URL: https://issues.apache.org/jira/browse/FLINK-15701
>             Project: Flink
>          Issue Type: Improvement
>          Components: Travis
>    Affects Versions: 1.10.0
>            Reporter: Yun Gao
>            Priority: Major
>
> Occasionally we met with the error 
> {code:java}
> COMPRESSING build artifacts.
> build_info
> container.log
> mvn-1.log
> mvn-2.log
> mvn.out
> Uploading to transfer.sh
> Could not save metadata
> {code}
> when the travis uploading logs to transfer.sh. This makes many fail tests cannot be analyzed due to lack of detail logs. To amend this situation, we should allow uploading to retry when the uploading fails. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)