Bug #3541

Ruby 1.9: broken unittest, unexpected invocation: Process.waitall()

Added by Jos Backus about 2 years ago. Updated about 2 years ago.

Status:Closed Start date:04/13/2010
Priority:Normal Due date:
Assignee:- % Done:

0%
Category:testing
Target version:1.5.8
Keywords: Affected Facter version:
Branch:
Votes: 0

Description

When running the Facter unit tests, the following failure is seen:

Facter::Util::Resolution when returning the value and the code is a block
-- should waitall to avoid zombies if the timeout is exceeded (FAILED - 1)
1)
Mocha::ExpectationError in 'Facter::Util::Resolution when returning the value and the code is a block should waitall to avoid zombies if the timeout is exceeded'
unexpected invocation: Process.waitall()
satisfied expectations:
- allowed any number of times, already invoked once: #<Facter::Util::Resolution:0x98cb5b8>.warn(any_parameters)
- expected exactly once, already invoked once: Thread.new(any_parameters)
- expected exactly once, already invoked once: Process.waitall(any_parameters)

bug-3541.diff - Patch to fix(?) the issue (350 Bytes) Jos Backus, 04/13/2010 12:42 am

History

#1
Updated by Jos Backus about 2 years ago

#2
Updated by Jos Backus about 2 years ago

  • Target version set to 1.5.8

Note that I’m stumped as to why the suggested patch fixes the issue.

#3
Updated by James Turnbull about 2 years ago

  • Category changed from library to testing
  • Status changed from Unreviewed to In Topic Branch Pending Review

#4
Updated by James Turnbull about 2 years ago

  • Status changed from In Topic Branch Pending Review to Closed

Pushed in commit:2f016f387367d6e52504194098333d1692e33c67 in branch master.

Also available in: Atom PDF