Jenkins Failure [#581] - Puppet (3.x) Stage 1, step 1: Linux Specs

[c...@puppetlabs.com]

See https://jenkins.puppetlabs.com/job/Puppet-Specs-3x/581/

============================
CHANGES (All changes since first failure)
============================
Changes for Build #581
[source] (PUP-3045) Send a TERM when Exec processes timeout




============================
TESTS
============================
There are 85050 total tests of which 2 test(s) failed.
2 tests failed.
FAILED: Puppet::Type::Exec.Puppet::Type::Exec for simple parameters when setting timeout when timeout is exceeded on POSIX sends a SIGTERM and raises a Puppet::Error

Error Message:
failed Puppet::Type::Exec for simple parameters when setting timeout when timeout is exceeded on POSIX sends a SIGTERM and raises a Puppet::Error

Stack Trace:

not all expectations were satisfied
unsatisfied expectations:
- expected at least once, not yet invoked: Process.kill(any_parameters)
satisfied expectations:
- allowed any number of times, not yet invoked: Signal.trap(any_parameters)
- allowed any number of times, invoked once: #<Puppet::Util::Feature:0x2912650>.posix?(any_parameters)
- allowed any number of times, invoked twice: #<Puppet::Util::Feature:0x2912650>.microsoft_windows?(any_parameters)

./spec/unit/type/exec_spec.rb:409:in `block (5 levels) in <top (required)>'
./spec/shared_contexts/platform.rb:46:in `block (2 levels) in <top (required)>'


FAILED: Puppet::Type::Exec.Puppet::Type::Exec for simple parameters when setting timeout when timeout is exceeded on POSIX sends a SIGTERM and raises a Puppet::Error

Error Message:
failed Puppet::Type::Exec for simple parameters when setting timeout when timeout is exceeded on POSIX sends a SIGTERM and raises a Puppet::Error

Stack Trace:

not all expectations were satisfied
unsatisfied expectations:
- expected at least once, not yet invoked: Process.kill(any_parameters)
satisfied expectations:
- allowed any number of times, not yet invoked: Signal.trap(any_parameters)
- allowed any number of times, invoked once: #<Puppet::Util::Feature:0x1265358>.posix?(any_parameters)
- allowed any number of times, invoked twice: #<Puppet::Util::Feature:0x1265358>.microsoft_windows?(any_parameters)

./spec/unit/type/exec_spec.rb:409:in `block (5 levels) in <top (required)>'
./spec/shared_contexts/platform.rb:46:in `block (2 levels) in <top (required)>'




============================
BUILD LOG (last 100 lines)
============================
Started by upstream project "Puppet-Pipeline-Kickoff-3x" build number 566
originally caused by:
Started by an SCM change
Building remotely on eternal.delivery.puppetlabs.net (unit swarm) in workspace /var/lib/jenkins/workspace/Puppet-Specs-3x
Wiping out workspace first.
Cloning the remote Git repository
Using shallow clone
Cloning repository git://github.delivery.puppetlabs.net/puppetlabs-puppet.git
> git init /var/lib/jenkins/workspace/Puppet-Specs-3x # timeout=10
Fetching upstream changes from git://github.delivery.puppetlabs.net/puppetlabs-puppet.git
> git --version # timeout=10
> git fetch --tags --progress git://github.delivery.puppetlabs.net/puppetlabs-puppet.git +refs/heads/*:refs/remotes/origin/* --depth=1
> git config remote.origin.url git://github.delivery.puppetlabs.net/puppetlabs-puppet.git # timeout=10
> git config remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
> git config remote.origin.url git://github.delivery.puppetlabs.net/puppetlabs-puppet.git # timeout=10
Pruning obsolete local branches
Fetching upstream changes from git://github.delivery.puppetlabs.net/puppetlabs-puppet.git
> git fetch --tags --progress git://github.delivery.puppetlabs.net/puppetlabs-puppet.git +refs/heads/*:refs/remotes/origin/* --prune
Checking out Revision 08a07da09e71bb25b408c7126a23644d9f94b22d (refs/remotes/origin/3.x)
> git config core.sparsecheckout # timeout=10
> git checkout -f 08a07da09e71bb25b408c7126a23644d9f94b22d
> git rev-list 2667053d0438d650c909158c79ce85cfaee8019a # timeout=10
> git tag -a -f -m Jenkins Build #581 jenkins-Puppet-Specs-3x-581 # timeout=10
Cleaning workspace
> git rev-parse --verify HEAD # timeout=10
Resetting working tree
> git reset --hard # timeout=10
> git clean -fdx # timeout=10
No emails were triggered.
Triggering Puppet (3.x) Stage 1, step 1: Linux Specs » 2.x,2.0.1,extra,unit,ruby-1.9.3-p484
Triggering Puppet (3.x) Stage 1, step 1: Linux Specs » 2.x,2.0.1,base,unit,ruby-1.9.3-p484
Triggering Puppet (3.x) Stage 1, step 1: Linux Specs » 2.x,2.0.1,base,unit,ruby-2.1.1
Triggering Puppet (3.x) Stage 1, step 1: Linux Specs » 2.x,2.0.1,extra,unit,ruby-2.1.1
Puppet (3.x) Stage 1, step 1: Linux Specs » 2.x,2.0.1,extra,unit,ruby-1.9.3-p484 completed with result SUCCESS
Puppet (3.x) Stage 1, step 1: Linux Specs » 2.x,2.0.1,base,unit,ruby-1.9.3-p484 completed with result SUCCESS
Puppet (3.x) Stage 1, step 1: Linux Specs » 2.x,2.0.1,base,unit,ruby-2.1.1 completed with result FAILURE
Puppet (3.x) Stage 1, step 1: Linux Specs » 2.x,2.0.1,extra,unit,ruby-2.1.1 completed with result FAILURE
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any

[c...@puppetlabs.com]

See https://jenkins.puppetlabs.com/job/Puppet-Specs-3x/582/

============================
CHANGES (Changes that may have contributed to fixing the build)
============================
Changes for Build #582
[source] (PUP-3045) Re-factor timeout spec test for windows