gaoyunhaii opened a new pull request #10951: [FLINK-15701][Travis] Retries when 
uploading to transfer.sh fails
URL: https://github.com/apache/flink/pull/10951
 
 
   ## What is the purpose of the change
   
   When uploading the test detail outputs onto 
[transfer.sh](https://transfer.sh), occasionally we meet with the error `Could 
not save metadata`. The error makes the unstable tests might not be able to be 
located since the test logs are missing.
   
   This PR tries to enable retrying if the uploading fails. It first check that 
the uploading returns a valid URL and then it checks if the URL is accessible. 
If either is not, it will retry. The retry will stop if the maximum allowed 
times is reached.
   
   
   ## Brief change log
   
   - b60b8d03e20dc1c49acc48e69cfc73c6abba100d added retries when uploading 
fails.
   
   ## Verifying this change
   
     - Manually verified the cases when the upload is successful, the uploading 
does not return a valid URL and the returned URL is not accessible.
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): **no**
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: **no**
     - The serializers: **no**
     - The runtime per-record code paths (performance sensitive): **no**
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Yarn/Mesos, ZooKeeper: **no**
     - The S3 file system connector: **no**
   
   ## Documentation
   
     - Does this pull request introduce a new feature? **no**
     - If yes, how is the feature documented? **not applicable**

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to