Skip to content

Conversation

@deivid-rodriguez
Copy link
Contributor

Description:

This is a temporary workaround for #3451.

It seems most likely a problem in either jruby or webrick, so until fixed upstream let's skip it so that it doesn't get in the middle.

Related upstream tickets:

ruby/webrick#40
jruby/jruby#6171

Tasks:

  • Describe the problem / feature
  • Write tests
  • Write code to solve the problem
  • Get code review from coworkers / friends

I will abide by the code of conduct.

@olleolleolle
Copy link
Contributor

olleolleolle commented Apr 10, 2020

It seems like JRuby (jruby-9.2.11.0) offers resistance to this:

TestGemRemoteFetcher#test_ssl_client_cert_auth_connection:
NoMethodError: undefined method `skip' for TestGemRemoteFetcher:Class

https://github.com/rubygems/rubygems/pull/3507/checks?check_run_id=577724865#step:4:73

@deivid-rodriguez
Copy link
Contributor Author

Oh, yeah, it should be fixed by #3508, since the skip will start running in the right context.

@deivid-rodriguez
Copy link
Contributor Author

Since #3508 might've fixed something (I'm not confident at all but who knows), I'll leave this PR opened until the flaky happens one more time, and then merge it. If on the contrary it doesn't happen again, I'll close this after a while.

I believe these are most certainly due to a problem outside of rubygems.
I'm skipping these at least until webrick officially supports jruby
(defining "officially" as "webrick's CI passes on jruby").
@deivid-rodriguez deivid-rodriguez force-pushed the skip_tests_using_webrick_on_jruby branch from b408c81 to 4fca025 Compare April 24, 2020 11:48
@deivid-rodriguez
Copy link
Contributor Author

@deivid-rodriguez deivid-rodriguez merged commit 12e6d4b into master Apr 24, 2020
@deivid-rodriguez deivid-rodriguez deleted the skip_tests_using_webrick_on_jruby branch April 24, 2020 12:46
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.

4 participants