guard / guard

97%

master: 88%

LAST BUILD ON BRANCH fix-thread-status

branch: fix-thread-status

CHANGE BRANCH

x

Reset

• fix-thread-status
• master
• v2.0
• v2.0_refactorings
• v2.0-notifiers-refactoring
• turn_off_for_terminal_notifier
• bug/472/clear-terminal-title
• coolline
• v1.8
• listen2
• windows-accomodations
• v2.0.4
• multiple_tmux_color_locations
• v2.0.5
• 2.1.1
• v2.2.0
• 2.2.0
• v2.1.1
• v2.2.1
• v2.2.2
• v2.2.3
• improve-groups
• v2.2.4
• fix-531
• v2.2.5
• v2.3.0
• v2.4.0
• v2.5.0
• v2.5.1
• fix-563
• v2.6.0
• attempt_to_fix_pry_crashes
• synchronous_guard
• v2.6.1
• refactoring_attempt
• massive_cleanup
• rubocop_update
• rework_bundler_warning
• handle_relpath_failure
• reevaluator_plugin
• minor_refactoring
• rework_interactors
• fix_cli_errors
• fix_guardrc_and_namespace
• fix_deprecation_error
• fix_guard_init_templates
• v2.7.0
• fix_crashing_scopes
• api_safe_refactoring
• acceptance_tests
• refactor
• v2.7.1
• immortal_reevaluator
• fix_655_clearing_screen
• fix_guard_list
• v2.7.2
• show_deprecated
• rspec_update
• fix_659_detecting_used_guards
• v2.7.3
• v2.8.0
• screen_clear
• fix_kernel_system_debug
• v2.8.1
• refactor_notifier
• fix_664_broken_stop_hook
• v2.8.2
• fix_houndci_config
• rework_deprecations
• rework
• e2-directories_in_guardfile
• v2.9.0
• quickfix_thread
• fix_broken_notify_autodetect
• v2.9.1
• fix_hooker_error
• v2.9.2
• restore_options_accessor
• v2.10.0
• fix_ignores
• v2.10.1
• ignore_guard_compat
• v2.10.2
• fix_multi_ignore
• v2.10.3
• fix_697_broken_scope_command
• v2.10.4
• fix_705_singular_scope
• v2.10.5
• extract_sheller
• extract_notifiers
• fix_clearing_710
• minor_cleanup
• fix_missing_require
• v2.11.0
• fix_715_minitest_notify
• v2.11.1
• improve_plugin_handling
• listen

Build # 910

Build Type

push

travis-ci

Committed by cablegram

Commit Message

Accommodate differences in Thread class under MRI 1.9.3, MRI 2.0.0 and jruby.

On a killed thread, Thread#alive? behaves differently under MRI 2.0.0 than under MRI 1.9.3, and jruby and Thread#status behaves differently under jruby than under MRI 1.9.3, and MRI 2.0.0.
t=Thread.new{}.kill; puts "#{t.alive?}--#{t.status}"
  On MRI 1.9.3 => true--aborting
  On MRI 2.0.0 => true--run
  On jruby        => false--aborting

Run Details

4752 of 4895 relevant lines covered (97.08%)

69.8 hits per line