Data already exists failure

[AaronRobinsonMSFT]

Build

https://dev.azure.com/dnceng-public/cbb18261-c48f-4abb-8651-8cdcb5474649/_build/results?buildId=65930

The data already exists, but there was a failure. I believe the tests have all passed but the infrastructure has failed for some readon.

Build leg reported

Build / SuperPMI replay windows x64 checked / Publish SuperPMI logs

Pull Request

dotnet/runtime#77556

Action required for the engineering services team

To triage this issue (First Responder / @dotnet/dnceng):

• Open the failing build above and investigate
• Add a comment explaining your findings

If this is an issue that is causing build breaks across multiple builds and would get benefit from being listed on the build analysis check, follow the next steps:

1. Add the label "Known Build Error"
2. Edit this issue and add an error string in the Json below that can help us match this issue with future build breaks. You should use the known issues documentation

{
   "ErrorMessage" : "Artifact SuperPMI_Logs_x64_checked already exists for build",
   "BuildRetry": false
}

Additional information about the issue reported

No response

Report

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
0	0	0

[oleksandr-didyk]

Taking a look at the issue, will update once I have any new info

[oleksandr-didyk]

From what I can tell you have re-ran the build due to failure to send the work item to Helix, which might have caused the duplicate log artifact error.

I triggered the affected pipeline again, hopefully it will fix the issue

[oleksandr-didyk]

After the pipeline was triggered again, it finished with no issues.

Please feel free to re-open the issue if you run into something similar or need further help

[riarenas]

@AaronRobinsonMSFT Given how this is a side effect of rerunning failed jobs in the pipeline, you could consider changing the log upload step to either:

1. Not cause the build to fail if the step fails
2. Append the attempt number to the log artifact name you are attempting to upload.

[michellemcdaniel]

For Ricardo's first suggestion,

continueOnError: true

should be added to the Publish Artifacts tasks here.

For the second, the artifactName in those two steps is what would need the attempt number (which is System.JobAttempt).