andygrove commented on PR #6061:
URL: 
https://github.com/apache/datafusion-comet/pull/6061#issuecomment-6116491970

   Thanks @ErikBPF, the reproducer helped. Since the PR was already open I 
pushed the workflow change myself in 49ff6ce03b, so no need for a follow-up 
patch. It writes the log to a `mktemp` file, retries only when Maven's error 
names a download, and runs under `shell: bash`. You were right about the shell. 
The step ran under `sh -e {0}`, so `$RANDOM` was empty and the jitter was 
always zero.
   
   I kept the short `scalafix:` goal and match `No plugin found for prefix` 
directly. The root POM declares the plugin, so in this job that error only 
means the descriptor did not download, and Maven still logs the HTTP cause in 
the `Failed to retrieve plugin descriptor` warning just above it. A qualified 
goal would need the Scala suffix for each matrix row, and it would still miss a 
404, which Maven reports as `Could not find artifact` rather than `Could not 
transfer artifact`.
   
   The 404 case turned out to matter. Since this PR was opened the lint has 
failed this way five more times: 403s on the merge-queue runs for #6065 and 
#6541, a 429 on the merge-queue run for #6647 after the resolver's own six 
retries, and 404s on two PR runs. Maven caches a 404 in the local repository, 
so the original loop would have failed all four attempts on those. I confirmed 
that with Maven 3.9.6 against a `file://` mirror: a plain rerun fails with "was 
cached in the local repository" and a rerun with `-U` succeeds, so the retries 
now pass `-U`.
   
   @kazuyukitanimura yes, still active. Those three merge-queue evictions are 
why.
   


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