You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think for PRs we spin up a new VM and for master builds we may have a permanent VM running. I vaguely recall @dave-tucker mentioned something about a pretty beefy instance running...
Rolf is correct.
We have a fixed machine with 16 vCPUs, 104 GB RAM for PRs which could be a tad excessive IMHO. I think we should probably create machines on demand for master too and ideally with the same config used for PRs (albeit with secrets).
The process for updating the VM images used isn't documented but @talex5 has done this in the past.
I'm working on using LinuxKit for this but I'm waiting on my mount PR's to merge before I continue.
expect (not inspect, but that seems to be what it wants from the error) is already installed on all build VMs. Perhaps it is trying to execute it on the CI host? In that case, it needs adding to the LinuxKit CI Dockerfile: https://github.com/linuxkit/linuxkit-ci/blob/master/Dockerfile
Activity
justincormack commentedon Jul 15, 2017
cc @talex5 @dave-tucker
justincormack commentedon Jul 15, 2017
Weirdly it passes on PRs and fails on master merges. Why?
rn commentedon Jul 15, 2017
I think for PRs we spin up a new VM and for master builds we may have a permanent VM running. I vaguely recall @dave-tucker mentioned something about a pretty beefy instance running...
dave-tucker commentedon Jul 17, 2017
Rolf is correct.
We have a fixed machine with
16 vCPUs, 104 GB RAMfor PRs which could be a tad excessive IMHO. I think we should probably create machines on demand formastertoo and ideally with the same config used for PRs (albeit with secrets).The process for updating the VM images used isn't documented but @talex5 has done this in the past.
I'm working on using LinuxKit for this but I'm waiting on my
mountPR's to merge before I continue.talex5 commentedon Jul 17, 2017
expect(notinspect, but that seems to be what it wants from the error) is already installed on all build VMs. Perhaps it is trying to execute it on the CI host? In that case, it needs adding to the LinuxKit CIDockerfile: https://github.com/linuxkit/linuxkit-ci/blob/master/Dockerfiledave-tucker commentedon Aug 8, 2017
Closed via a042a1c