-
Notifications
You must be signed in to change notification settings - Fork 320
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Attachments with path too long lead to missing results in trx #2085
Labels
Comments
Adding sprint because it looks like low hanging fruit for some future sprint. |
Not clear to me how the linked issue is connected to long paths, if you are still around @kaadhina and you remember what was going on, can you tell me? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If there are test cases with attachments with path too long, it can lead to missing results. in trx report. We may skip the attachment but this should ideally not lead to missing test results in the trx
This has more detailed info and logs:
https://developercommunity.visualstudio.com/content/problem/612228/azure-devops-unit-test-result-not-being-published.html
AB#1865106
The text was updated successfully, but these errors were encountered: