Repository navigation
superpmi-replay pipeline fails when re-run in CI due to the log artifact already existing #77295
Description
I've re-run the superpmi leg in my PR today and it has failed in the "Publish SuperPMI logs" and "Publish SuperPMI build logs" with errors:
##[error]Artifact SuperPMI_Logs_x64_checked already exists for build 58267.
and
##[error]Artifact SuperPMI_BuildLogs_x64_checked already exists for build 58267.
It sounds like a bug.
Activity
janvorli commentedon Oct 20, 2022
Here is a reference to the log:
https://dev.azure.com/dnceng-public/public/_build/results?buildId=58267&view=logs&j=406f67d9-8952-5074-7a53-dcb346cb6a5f&t=feeda9ba-a6cf-55e3-b217-8f390a72d061
janvorli commentedon Oct 20, 2022
The PR was #77268
mangod9 commentedon Oct 20, 2022
@BruceForstall to route appropriately? Also looks like there are some intermittent failures in the jobs recently?
BruceForstall commentedon Oct 20, 2022
This happens when the job is re-run in AzDO. We use the
PublishPipelineArtifact@1task which fails when trying to overwrite the same log file name. I don't think it supports a "force" mode. All other users seem to usecontinueOnError: trueso maybe we need to do that as well to avoid this. Of course, that means we still won't upload the second or subsequent log files, but we won't complain about it, either.mangod9 commentedon Oct 21, 2022
correct, other legs show that as a warning but the leg itself completes as green if tests are passing on rerun
BruceForstall commentedon Nov 4, 2022
This was fixed with #77685