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

specs randomly dump undefined method `thread_safety' for #<Class...> #77

Closed
Fryguy opened this issue Jan 31, 2020 · 4 comments · Fixed by #116
Closed

specs randomly dump undefined method `thread_safety' for #<Class...> #77

Fryguy opened this issue Jan 31, 2020 · 4 comments · Fixed by #116

Comments

@Fryguy
Copy link
Member

Fryguy commented Jan 31, 2020

If you run the tests with bundle exec rspec --order random you will occasionally get the following error in the output (but the tests don't actually fail):

#<Thread:0x00007fecd012e048@/Users/jfrey/dev/more_core_extensions/spec/core_ext/module/cache_with_timeout_spec.rb:166 run> terminated with exception (report_on_exception is true):
Traceback (most recent call last):
	2: from /Users/jfrey/dev/more_core_extensions/spec/core_ext/module/cache_with_timeout_spec.rb:167:in `block (4 levels) in <top (required)>'
	1: from /Users/jfrey/dev/more_core_extensions/spec/core_ext/module/cache_with_timeout_spec.rb:167:in `times'
/Users/jfrey/dev/more_core_extensions/spec/core_ext/module/cache_with_timeout_spec.rb:168:in `block (5 levels) in <top (required)>': undefined method `thread_safety' for #<Class:0x00007fecd3284890> (NoMethodError)

@jrafanie

@jrafanie
Copy link
Member

fun!

@Fryguy
Copy link
Member Author

Fryguy commented Jan 31, 2020

correction...the specs don't fail though...

@Fryguy Fryguy changed the title specs fail randomly with undefined method `thread_safety' for #<Class...> specs randomly dump undefined method `thread_safety' for #<Class...> Jan 31, 2020
@djberg96
Copy link
Contributor

Yep, I see the same thing locally.

Ruby 2.6.5 on Catalina, btw.

@miq-bot
Copy link
Member

miq-bot commented Mar 6, 2023

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation.

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

Successfully merging a pull request may close this issue.

4 participants