Skip to content

Conversation

@mmitche
Copy link
Member

@mmitche mmitche commented Aug 30, 2024

Works around #9670. An updated redist came in from a recent update. The old redist has been uploaded to netcorenativeassets, and we use that rather than the Windows SDK path to resolve the file paths.

Microsoft Reviewers: Open in CodeFlow

Works around dotnet#9670. An updated redist came in from a recent update. The old redist has been uploaded to netcorenativeassets, and we use that rather than the Windows SDK path to resolve the file paths.
@mmitche mmitche requested review from a team as code owners August 30, 2024 18:08
@dotnet-policy-service dotnet-policy-service bot added the PR metadata: Label to tag PRs, to facilitate with triage label Aug 30, 2024
@mmitche
Copy link
Member Author

mmitche commented Aug 30, 2024

@mmitche mmitche merged commit 212b7c1 into dotnet:release/9.0-rc1 Aug 30, 2024
Kuldeep-MS pushed a commit to Kuldeep-MS/wpf that referenced this pull request Sep 3, 2024
Works around dotnet#9670. An updated redist came in from a recent update. The old redist has been uploaded to netcorenativeassets, and we use that rather than the Windows SDK path to resolve the file paths.
@Kuldeep-MS
Copy link
Contributor

/backport to release/9.0

@github-actions
Copy link

github-actions bot commented Sep 5, 2024

Started backporting to release/9.0: https://github.com/dotnet/wpf/actions/runs/10714354131

@github-actions
Copy link

github-actions bot commented Sep 5, 2024

@Kuldeep-MS an error occurred while backporting to release/9.0, please check the run log for details!

Error: @Kuldeep-MS is not a repo collaborator, backporting is not allowed. If you're a collaborator please make sure your dotnet team membership visibility is set to Public on https://github.com/orgs/dotnet/people?query=Kuldeep-MS

@Kuldeep-MS
Copy link
Contributor

/backport to release/9.0

@github-actions
Copy link

github-actions bot commented Sep 5, 2024

Started backporting to release/9.0: https://github.com/dotnet/wpf/actions/runs/10714368827

@Kuldeep-MS
Copy link
Contributor

/backport to release/6.0

@github-actions
Copy link

Started backporting to release/6.0: https://github.com/dotnet/wpf/actions/runs/10820168379

@Kuldeep-MS
Copy link
Contributor

/backport to release/8.0

@github-actions
Copy link

@Kuldeep-MS backporting to release/6.0 failed, the patch most likely resulted in conflicts:

$ git am --3way --empty=keep --ignore-whitespace --keep-non-patch changes.patch

Applying: Work around d3d redist incompat. Works around https://github.com/dotnet/wpf/issues/9670. An updated redist came in from a recent update. The old redist has been uploaded to netcorenativeassets, and we use that rather than the Windows SDK path to resolve the file paths.
Using index info to reconstruct a base tree...
M	global.json
Falling back to patching base and 3-way merge...
Auto-merging global.json
CONFLICT (content): Merge conflict in global.json
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 Work around d3d redist incompat. Works around https://github.com/dotnet/wpf/issues/9670. An updated redist came in from a recent update. The old redist has been uploaded to netcorenativeassets, and we use that rather than the Windows SDK path to resolve the file paths.
Error: The process '/usr/bin/git' failed with exit code 128

Please backport manually!

@github-actions
Copy link

@Kuldeep-MS an error occurred while backporting to release/6.0, please check the run log for details!

Error: git am failed, most likely due to a merge conflict.

@github-actions
Copy link

Started backporting to release/8.0: https://github.com/dotnet/wpf/actions/runs/10820172202

@github-actions
Copy link

@Kuldeep-MS backporting to release/8.0 failed, the patch most likely resulted in conflicts:

$ git am --3way --empty=keep --ignore-whitespace --keep-non-patch changes.patch

Applying: Work around d3d redist incompat. Works around https://github.com/dotnet/wpf/issues/9670. An updated redist came in from a recent update. The old redist has been uploaded to netcorenativeassets, and we use that rather than the Windows SDK path to resolve the file paths.
Using index info to reconstruct a base tree...
M	global.json
Falling back to patching base and 3-way merge...
Auto-merging global.json
CONFLICT (content): Merge conflict in global.json
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 Work around d3d redist incompat. Works around https://github.com/dotnet/wpf/issues/9670. An updated redist came in from a recent update. The old redist has been uploaded to netcorenativeassets, and we use that rather than the Windows SDK path to resolve the file paths.
Error: The process '/usr/bin/git' failed with exit code 128

Please backport manually!

@github-actions
Copy link

@Kuldeep-MS an error occurred while backporting to release/8.0, please check the run log for details!

Error: git am failed, most likely due to a merge conflict.

@mmitche
Copy link
Member Author

mmitche commented Oct 8, 2024

When the d3d fix is available and rolled out in the windows SDK (on 1ES hosted pool machines), this fix should be reverted.

@github-actions github-actions bot locked and limited conversation to collaborators Nov 8, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

PR metadata: Label to tag PRs, to facilitate with triage

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants