CI Failures

[DavidTruby]

The CI obviously isn't working as planned so I suggest we disable it for now. I'm not certain but it looks like we're hitting a per-process memory limit on the docker containers and the OOM killer is killing the compiler process. Apologies for this not working correctly, I didn't see this behavior on my own branch but I suspect that is just due to the smaller sample size.

[sscalpone]

@DavidTruby Are we able to purchase service with more available resources?

[RichBarton-Arm]

@sscalpone my understanding is that this is a limit on the docker container rather than the available resources on the machine. The machine has 128Gb of RAM, which should be plenty even for F18. @DavidTruby - any luck with getting drone.ci to change this limit or make it possible for users to change it?

[DavidTruby]

Unfortunately I tried to reach out on their discourse (which seems to be the place to go for support) and didn't receive a reply, you can see my issue here:
https://discourse.drone.io/t/random-failures-time-outs-on-drone-cloud/6294

[DavidTruby]

With regards to purchasing, github's built in CI (launched two weeks ago) allows "bring your own machine" configurations where you can provide your own machines to run the CI on. This could possibly be an option if we are willing to pay e.g. for cloud servers and hook them up with this.

[isuruf]

Azure pipelines (they share the same infrastructure with Github CI as both are owned by Microsoft) work for x86_64. See https://dev.azure.com/isuruf/repos/_build/results?buildId=18

[sscalpone]

@DavidTruby Is this issue better titled "Enable CI"?