Skip to content
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

[mono] Move mono.mscordbi subset off the offical build #81917

Merged
merged 1 commit into from
Feb 10, 2023

Conversation

steveisok
Copy link
Member

@steveisok steveisok commented Feb 9, 2023

This isn't in use, so there's no need to build and ship it. Instead, this is being moved to the mono windows x64 public leg.

This isn't in use, so there's no need to build and ship it. Instead, this is being moved
to the mono windows x64 leg.
@ghost
Copy link

ghost commented Feb 9, 2023

Tagging subscribers to this area: @directhex
See info in area-owners.md if you want to be subscribed.

Issue Details

This isn't in use, so there's no need to build and ship it. Instead, this is being moved to the mono windows x64 leg.

Author: steveisok
Assignees: steveisok
Labels:

area-Infrastructure-mono

Milestone: -

@thaystg
Copy link
Member

thaystg commented Feb 9, 2023

@steveisok
Copy link
Member Author

Should we also remove from: https://github.com/dotnet/runtime/blob/main/eng/pipelines/runtime-codeql.yml ?

No, I think that can stay.

@marek-safar marek-safar merged commit 84c2ff1 into dotnet:main Feb 10, 2023
@ghost ghost locked as resolved and limited conversation to collaborators Mar 12, 2023
@carlossanlop
Copy link
Member

/backport to release/6.0

@github-actions github-actions bot unlocked this conversation Apr 17, 2023
@github-actions
Copy link
Contributor

Started backporting to release/6.0: https://github.com/dotnet/runtime/actions/runs/4724948321

@carlossanlop
Copy link
Member

/backport to release/7.0

@github-actions
Copy link
Contributor

Started backporting to release/7.0: https://github.com/dotnet/runtime/actions/runs/4724957322

@github-actions
Copy link
Contributor

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

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

Applying: [mono] Move mono.mscordbi subset off the offical build
Using index info to reconstruct a base tree...
A	eng/pipelines/extra-platforms/runtime-extra-platforms-other.yml
M	eng/pipelines/runtime-official.yml
Falling back to patching base and 3-way merge...
Auto-merging eng/pipelines/runtime-official.yml
CONFLICT (content): Merge conflict in eng/pipelines/runtime-official.yml
CONFLICT (modify/delete): eng/pipelines/extra-platforms/runtime-extra-platforms-other.yml deleted in HEAD and modified in [mono] Move mono.mscordbi subset off the offical build. Version [mono] Move mono.mscordbi subset off the offical build of eng/pipelines/extra-platforms/runtime-extra-platforms-other.yml left in tree.
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 [mono] Move mono.mscordbi subset off the offical build
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
Error: The process '/usr/bin/git' failed with exit code 128

Please backport manually!

@github-actions
Copy link
Contributor

@carlossanlop 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 github-actions bot locked as resolved and limited conversation to collaborators Apr 17, 2023
@carlossanlop
Copy link
Member

Sigh... I'll reopen the closed PRs and manually remove the unwanted commits added after retargeting to the base branches.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants