Clear xgboost arch migrators status again #9
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The macOS ARM migrator is already applied. However the bot shows an error. We tried to clear this before, but the bot still ran into issues with the recipe format. Have made a formatting change, which may help (however was unable to reproduce the bot issue so couldn't test). Clearing the status here to try again and see if it is fixed.
|
Thanks Matt! 🙏 Let's see how this goes 🍀 |
|
Looks like the migrator bot is still unhappy Not really sure why. Raising an issue: regro/cf-scripts#1890 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The macOS ARM migrator is already applied. However the bot shows an error. We tried to clear this before, but the bot still ran into issues with the recipe format. Have made a formatting change, which may help (however was unable to reproduce the bot issue so couldn't test). Clearing the status here to try again and see if it is fixed.
xref: #8 (where this was originally tried)