Facter (2.x) Stage 1, step 1: Windows Specs - Build # 150 - Failure!

[c...@puppetlabs.com]

See https://jenkins.puppetlabs.com/job/Facter-Specs-Windows-2.x/150/

============================
CHANGES (All changes since first failure)
============================
Changes for Build #150



============================
TESTS
============================
There are total tests of which test(s) failed.
No tests ran.

============================
BUILD LOG (last 100 lines)
============================
Started by upstream project "Facter-Pipeline-Kickoff-2.x" build number 149
originally caused by:
Started by timer
Building remotely on panama.delivery.puppetlabs.net (unit swarm) in workspace /var/lib/jenkins/workspace/Facter-Specs-Windows-2.x
Wiping out workspace first.
Cloning the remote Git repository
Cloning repository git://github.delivery.puppetlabs.net/puppetlabs-facter.git
> git init /var/lib/jenkins/workspace/Facter-Specs-Windows-2.x # timeout=10
Fetching upstream changes from git://github.delivery.puppetlabs.net/puppetlabs-facter.git
> git --version # timeout=10
> git fetch --tags --progress git://github.delivery.puppetlabs.net/puppetlabs-facter.git +refs/heads/*:refs/remotes/origin/*
> git config remote.origin.url git://github.delivery.puppetlabs.net/puppetlabs-facter.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-facter.git # timeout=10
Fetching upstream changes from git://github.delivery.puppetlabs.net/puppetlabs-facter.git
> git fetch --tags --progress git://github.delivery.puppetlabs.net/puppetlabs-facter.git +refs/heads/*:refs/remotes/origin/*
Checking out Revision 3f6775ca05580c9949d1afe1afe6754eb7bc3214 (refs/remotes/origin/2.x)
> git config core.sparsecheckout # timeout=10
> git checkout -f 3f6775ca05580c9949d1afe1afe6754eb7bc3214
> git rev-list 3f6775ca05580c9949d1afe1afe6754eb7bc3214 # 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 Facter (2.x) Stage 1, step 1: Windows Specs » unit-win2012,ruby-1.9.3-p551.1
Triggering Facter (2.x) Stage 1, step 1: Windows Specs » unit-win2012,ruby-2.1.5.2-x86
Triggering Facter (2.x) Stage 1, step 1: Windows Specs » unit-win2012,ruby-2.0.0.4-x64
Triggering Facter (2.x) Stage 1, step 1: Windows Specs » unit-win2008,ruby-2.1.5.2-x64
Triggering Facter (2.x) Stage 1, step 1: Windows Specs » unit-win2008,ruby-2.0.0.4-x64
Triggering Facter (2.x) Stage 1, step 1: Windows Specs » unit-win2003,ruby-1.9.3-p551.1
Triggering Facter (2.x) Stage 1, step 1: Windows Specs » unit-win2008,ruby-2.1.5.2-x86
Triggering Facter (2.x) Stage 1, step 1: Windows Specs » unit-win2012,ruby-2.1.5.2-x64
Triggering Facter (2.x) Stage 1, step 1: Windows Specs » unit-win2008,ruby-1.9.3-p551.1
Triggering Facter (2.x) Stage 1, step 1: Windows Specs » unit-win2003,ruby-2.1.5.2-x86
Facter (2.x) Stage 1, step 1: Windows Specs » unit-win2012,ruby-1.9.3-p551.1 completed with result FAILURE
Facter (2.x) Stage 1, step 1: Windows Specs » unit-win2012,ruby-2.1.5.2-x86 completed with result FAILURE
Facter (2.x) Stage 1, step 1: Windows Specs » unit-win2012,ruby-2.0.0.4-x64 completed with result FAILURE
Facter (2.x) Stage 1, step 1: Windows Specs » unit-win2008,ruby-2.1.5.2-x64 completed with result FAILURE
Facter (2.x) Stage 1, step 1: Windows Specs » unit-win2008,ruby-2.0.0.4-x64 completed with result FAILURE
Facter (2.x) Stage 1, step 1: Windows Specs » unit-win2003,ruby-1.9.3-p551.1 completed with result FAILURE
Facter (2.x) Stage 1, step 1: Windows Specs » unit-win2008,ruby-2.1.5.2-x86 completed with result FAILURE
Facter (2.x) Stage 1, step 1: Windows Specs » unit-win2012,ruby-2.1.5.2-x64 completed with result FAILURE
Facter (2.x) Stage 1, step 1: Windows Specs » unit-win2008,ruby-1.9.3-p551.1 completed with result FAILURE
Facter (2.x) Stage 1, step 1: Windows Specs » unit-win2003,ruby-2.1.5.2-x86 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/Facter-Specs-Windows-2.x/151/

============================
CHANGES (Changes that may have contributed to fixing the build)
============================
Changes for Build #151

Changes for Build #150