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

[CI] Remove lint step from unity/pr-head step #17155

Merged
merged 2 commits into from
Jul 16, 2024

Conversation

Lunderberg
Copy link
Contributor

This step should only be performed as part of the lint/pr-head CI step. It was included as part of the unity-specific CI steps prior to merging of unity into main. It is no longer necessary as part of unity/pr-head.

This step should only be performed as part of the `lint/pr-head` CI
step.  It was included as part of the unity-specific CI steps prior to
merging of unity into main.  It is no longer necessary as part of
`unity/pr-head`.
@Lunderberg Lunderberg force-pushed the ci_remove_lint_step_from_unity branch from fd582ee to 374ad4e Compare July 12, 2024 18:57
@Lunderberg
Copy link
Contributor Author

@tvm-bot rerun

Copy link
Contributor

@quic-sanirudh quic-sanirudh left a comment

Choose a reason for hiding this comment

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

This will definitely help, thanks.

Not strictly related to this PR, but as a general question, do we need to keep the unity/pr-head separate anymore? I see that it builds and runs some cpu and gpu tests, couldn't we just move them to the cpu and gpu heads and just remove this. It might help avoid building for cpu and gpu in 2 separate builds, and avoid running some of these tests multiple times?

@vinx13 vinx13 merged commit 73078f1 into apache:main Jul 16, 2024
19 checks passed
@Lunderberg Lunderberg deleted the ci_remove_lint_step_from_unity branch July 16, 2024 23:44
@Lunderberg
Copy link
Contributor Author

do we need to keep the unity/pr-head separate anymore?

I don’t know of any reason why they’d need to remain separate, and that would definitely help make the test summaries more readable.

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

Successfully merging this pull request may close these issues.

3 participants