tkobayas commented on issue #1444:
URL: 
https://github.com/apache/incubator-kie-issues/issues/1444#issuecomment-2337187035

   on 09-05, Jan and Rodrigo manually triggered the job.
   
   09-05 (1st): SUCCESS. No WARNING
   09-05 (2nd):  Upload was successful. No WARNING. The job failed because of 
the duplicate tag name, not related to uploading.
   
   09-08: FAILURE. The job was cancelled because of job time out (3 hours). The 
job was in the middle of 2nd attempt of uploading. 1st uploading hit 30 
WARNINGs. 
   
   ```
   [2024-09-08T03:02:07.906Z] Timeout set to expire in 3 hr 0 min
   ...
   [2024-09-08T04:37:57.001Z] [INFO] --- deploy:3.1.1:deploy (default-deploy) @ 
drools-distribution ---
   [2024-09-08T04:39:20.860Z] [WARNING] Failed to upload checksum to 
org/kie/kie-core-bom/999-20240908-SNAPSHOT/kie-core-bom-999-20240908-20240908.030343-1.pom.md5
   [2024-09-08T04:39:20.860Z] org.apache.http.client.HttpResponseException: 
status code: 408, reason phrase: Request Timeout (408)
   ...
   [2024-09-08T05:52:38.558Z] [INFO] Retrying deployment attempt 2 of 5
   ...
   [2024-09-08T06:02:07.906Z] Cancelling nested steps due to timeout
   ```
   
   With `aether.connector.basic.parallelPut=false`, usually one round of 
uploading all artifacts takes around 35 minutes (e.g. 09-01 Sunday). But on 
09-08, the 1st attempt took around 75 minutes. The network might be unusually 
unstable. 
   
   How to improve further?
   A) Increase job timeout : But note that drools weekly deployment is a 
dependency of other projects weekly deployment.
   B) Disable `deployAtEnd`
   


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