-
-
Notifications
You must be signed in to change notification settings - Fork 81
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
Migrate to GitHub Actions from CircleCI #398
Conversation
abf745d
to
9a1296e
Compare
This PR will centralize CI to GitHub Actions as introduced in rubocop#388.
9a1296e
to
eef0431
Compare
Hey @koic, locally I'm getting the failures you excluded for JRuby with CRuby, but only when running the full spec suite with I wonder if this is something I should be looking into, but if its only me I wouldn't bother. I regenerated my lockfile but I can't say if that is related to that. |
Hm, I couldn't reproduce it on my local environment. It also passes when using the seed. |
I think I figured it out. Not sure why it's not failing for you though. Will open a PR. |
Well, not really. I bisected it down to the following order rubocop-performance/spec/rubocop/cli/autocorrect_spec.rb Lines 11 to 13 in 47c0de5
rspec --bisect , TIL)
Solution seemed simple enough by changing it into this: around do |ex|
previous_config = RuboCop::ConfigLoader.default_configuration
RuboCop::ConfigLoader.default_configuration = nil
RuboCop::ConfigLoader.default_configuration.for_all_cops['SuggestExtensions'] = false
RuboCop::ConfigLoader.default_configuration.for_all_cops['NewCops'] = 'disable'
ex.call
ensure
RuboCop::ConfigLoader.default_configuration = previous_config
end which did remove the failures. But now I'm not getting failures anymore at all even with the command that previously reliably produced them without changes to the code, and other specs in rubocop also do the same pattern without problems. So I'm a bit stumped again 🤷 |
This PR will centralize CI to GitHub Actions as introduced in #388.
Before submitting the PR make sure the following are checked:
[Fix #issue-number]
(if the related issue exists).master
(if not - rebase it).bundle exec rake default
. It executes all tests and runs RuboCop on its own code.{change_type}_{change_description}.md
if the new code introduces user-observable changes. See changelog entry format for details.