Closed yuyichao closed 7 years ago
can we make this run not on the ubuntu slave? there are too many nightly jobs on that builder and it gets backed up
I've just been copying the previous config file I touched, where should I run this then?
centos 7 maybe? that only has the one job right now
Sure, is this the right way to do it?
I just realized that doing this will not run the tests with inliing off.
@tkelman @staticfloat do we actually still want to have a buildbot running noinline tests? I think it won't really be testing sth that we want to keep working (now that we don't need inlining off for coverage). I might be useful as a Fuzz test but probably not more than that.
If we still want to have no-inline tests, https://github.com/JuliaLang/julia/pull/18680 should provide an much easier way.
I think it's worth identifying and tracking fragile tests, yes
In that case https://github.com/JuliaLang/julia/pull/18681....
It's trivial to add a second Ubuntu buildbot if that's what we need. Then tasks assigned to an Ubuntu builder will be load-balanced accordingly.
we may want to do that anyway, but we have the centos worker and it's a bit underutilized
Rebased and updated the script to use the env added in https://github.com/JuliaLang/julia/pull/18680. This still launches the test process manually so that the compile test on master process also has inlining off.
@staticfloat
Use a separate buildbot for noinline tests
Fix #55 I realized that the test list is from
CoverageBase.jl
so this requires https://github.com/JuliaCI/CoverageBase.jl/pull/19 @staticfloat