Data already exists failure
See original GitHub issueBuild
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
https://github.com/dotnet/runtime/pull/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:
- Add the label “Known Build Error”
- 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 |
Issue Analytics
- State:
- Created a year ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
HTTP response code for POST when resource already exists
It depends if you consider the existence of the object an error or not. If you process the append, 200 or 204 are...
Read more >Resolving "database already exists" error during SQL ...
Use SQL Server Management Studio to detach or rename the conflicting local database. This will ensure that the existing database files are not ......
Read more >Solving the 'Already Exists' Error in Spark DataFrames
One common issue that many data scientists encounter is the 'already exists' error when using the dataframe.write.option('mode','overwrite') ...
Read more >"The data you have entered already exists" when trying to ...
I am trying to add recruiting@innovexsolutions.co.ke as a shared inbox but I get the error: The data you have entered already exists. @Deeraj...
Read more >Resolving Already Exists error when re-deploying CDK code.
To resolve this error, complete the following actions depending on your use case: For unintentionally retained resources, manually delete the resources.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
For Ricardo’s first suggestion,
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
).@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: