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

add a style check GH workflow #2862

Merged
merged 3 commits into from
Aug 15, 2020

Conversation

neutrinoceros
Copy link
Member

@neutrinoceros neutrinoceros commented Aug 14, 2020

PR Summary

fix #2839

Here's what it look like when triggered on a PR against a master branch that already includes this file
neutrinoceros2#1

PR Checklist

  • remove Travis linting

@neutrinoceros neutrinoceros added infrastructure Related to CI, versioning, websites, organizational issues, etc code style Related to linting tools labels Aug 14, 2020
@neutrinoceros
Copy link
Member Author

neutrinoceros commented Aug 14, 2020

Welp so the checks are not triggered here, which means only the master version of workflows is used (makes a lot of sense actually).

Then did trigger on my fork though https://github.com/neutrinoceros/yt/runs/984493527?check_suite_focus=true
(and caught a flake8 error that I have no idea how we did catch earlier)

@matthewturk
Copy link
Member

Any chance you could see what the time savings is if we consolidate the steps into a single job, so we only checkout once?

@neutrinoceros
Copy link
Member Author

In fact I tried to do it as a single job originally, but it's actually longer because then it doesn't run in parallel.
Also, it's not desirable because in that config it just reports the first error and then gives up on other checkers.
What we're missing here is a "stage", not a job, but it seems to me that there's no such thing currently in GitHub workflows.

@matthewturk
Copy link
Member

matthewturk commented Aug 14, 2020 via email

@neutrinoceros neutrinoceros marked this pull request as ready for review August 14, 2020 12:54
Copy link
Member

@munkm munkm left a comment

Choose a reason for hiding this comment

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

This looks good to me!

@neutrinoceros
Copy link
Member Author

Too bad this hit the current random failure on travis... It's not affecting the codebase itself but because it does affect the conf file for Travis, maybe the run should be retriggered ? Though I'm not sure if flipping a coin is worth 2.5 h of cpu time tbh.

@munkm
Copy link
Member

munkm commented Aug 14, 2020

I'll retrigger the travis tests. I can trigger individual jobs so it's only 30 minutes for osx.

@matthewturk matthewturk merged commit af42d40 into yt-project:master Aug 15, 2020
@neutrinoceros neutrinoceros deleted the gh_linting_workflow branch August 15, 2020 14:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code style Related to linting tools infrastructure Related to CI, versioning, websites, organizational issues, etc
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Use GitHub actions for linting
3 participants