KiCad / kicad-mac-builder

The macOS V5+ KiCad builder and packager [moved to https://gitlab.com/kicad]
13 stars 6 forks source link

kicad-mac-builder-10.12-master-upload #10 failed #248

Closed wayneandlayneci closed 5 years ago

wayneandlayneci commented 5 years ago

Build 'kicad-mac-builder-10.12-master-upload' is failing!

Last 50 lines of build output:

[...truncated 1.12 KB...]
 > git checkout -f 5ac92991b1b5c58f9cf3523363269a64c93cb5ed
Commit message: "Merge pull request #244 from KiCad/libngspice"
 > git rev-list --no-walk 94fce796d178b24c848617ceedbc70b496189ec9 # timeout=10
[kicad-mac-builder-10.12-master-upload] $ /bin/sh -xe /var/folders/67/nvcz1w6j6gbcfkxv0pkxj25h0000gq/T/jenkins4068508397142237979.sh
+ vagrant plugin install vagrant-scp
Installing the 'vagrant-scp' plugin. This can take a few minutes...
Installed the plugin 'vagrant-scp (0.5.7)'!
+ cd ci/10.12
+ PATH=/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin
+ vagrant halt
+ PATH=/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin
+ vagrant destroy -f
==> default: Destroying VM and associated drives...
+ rm -rf .vagrant
+ PATH=/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin
+ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'macos_10.12'...
Progress: 10%Progress: 20%Progress: 30%Progress: 90%==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: 1012_default_1543990399182_12739
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.
Build step 'Execute shell' marked build as failure
Archiving artifacts

Changes since last successful build: No changes

View full output