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.

Sign up for GitHub

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

Jump to bottom

Fix syntax error in YAML file of rapids CI #286

Merged
merged 1 commit into from
Oct 17, 2024
Merged

Fix syntax error in YAML file of rapids CI #286

merged 1 commit into from
Oct 17, 2024

Conversation

toshihikoyanase
Copy link
Member

Motivation

This PR will resolve the syntax error in rapids.yaml.
As we can see the following CI result, the Run examples block is not correctly indented:

GitHub Actions .github/workflows/rapids.yml
Invalid workflow file
You have an error in your yaml syntax on line 12

Description of the changes

  • Fix the indent of the lines in rapids.yaml

@toshihikoyanase
Copy link
Member Author

I don't think the workflow name in rapids.yaml should be base. Can I rename it to rapids in this PR?

y0z
y0z approved these changes Oct 17, 2024
View reviewed changes
Copy link
Member

@y0z y0z left a comment •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. To fix CI at first, I merged this PR and will make another PR to rename this.

@y0z y0z added the CI Continuous integration. label Oct 17, 2024
@y0z y0z added this to the v4.1.0 milestone Oct 17, 2024
@y0z y0z merged commit 81328c2 into optuna:main Oct 17, 2024
7 checks passed
@y0z y0z mentioned this pull request Oct 17, 2024
Merged
@toshihikoyanase toshihikoyanase deleted the fix-syntac-error-of-rapids-ci-yaml branch October 17, 2024 12:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@y0z y0z y0z approved these changes

Assignees
No one assigned
Labels
CI Continuous integration.
Projects
None yet
Milestone
v4.1.0
Development

Successfully merging this pull request may close these issues.
2 participants
@toshihikoyanase @y0z