[Draft] Fix hard link creation in tar tests in Android, iOS, tvOS#69416
[Draft] Fix hard link creation in tar tests in Android, iOS, tvOS#69416carlossanlop wants to merge 3 commits into
Conversation
|
Tagging subscribers to this area: @dotnet/area-system-io Issue DetailsFixes #68360 My suspicion is that in Android, iOS and tvOS (the only Unix platforms where this test failed) need to be elevated so the hardlink can be created. Draft since I need to test this hypothesis in the CI first.
|
|
/azp run runtime-extra-platforms |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run runtime-extra-platforms |
|
Azure Pipelines successfully started running 1 pipeline(s). |
…zation, mavoid locaal method to improve stacktrace.
…to potential long paths when extracting to temp dir.
|
/azp run runtime-extra-platforms |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
The test was recently disabled in LinuxBionic. I need to see the CI results to determine what to do there. |
|
/azp run runtime-extra-platforms |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
The |
|
/azp run runtime-extra-platforms |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
This PR will end up fixing two bugs. Will resubmit soon. |
Fixes #68360
My suspicion is that in Android, iOS and tvOS (the only Unix platforms where this test failed) need to be elevated so the hardlink can be created.My suspicion was wrong. We cannot elevate in those platforms.
In Android, it's not possible to create hard links so we should skip in that platform.
In iOS/tvOS we should be able to, but the logic that generated the "sanitized" path was not generating it correctly.