Remove Travis testing

[wilzbach]

• Travis got super slow and unreliable over the last weeks
• Even reduced to only one OSX job it still takes hours for a PR to build
• We often run into failures as the job reaches the maximal 50 minutes build limit
• Travis was only intended to test bootstrapping with the latest DMD + GDC + LDC (SemaphoreCI does this now pretty reliable.
• If auto-merge should obey combined CI status dlang-bot#69 gets merged, we would need to wait for hours or even days until a PR gets merged (even if all other CI pass)

Or in Martin's word:

What's the worth of a CI that doesn't report back in 1 day.

See also:

• auto-merge should obey combined CI status dlang-bot#69 (comment)
• Move tests from Travis to SemaphoreCI #7617 (comment)
• https://travis-ci.org/dlang/dmd/builds
• http://forum.dlang.org/post/ronypzvsafxpqlpnxlsf@forum.dlang.org (Heads-up for pending auto-merge change)
• http://forum.dlang.org/post/zbxaviowooiaenaawmgs@forum.dlang.org (Re: Bump the minimal version required to compile DMD to 2.076.1)

CC @MartinNowak

[dlang-bot]

Thanks for your pull request, @wilzbach!

Bugzilla references

Your PR doesn't reference any Bugzilla issue.

If your PR contains non-trivial changes, please reference a Bugzilla issue or create a manual changelog.

[JinShil]

So does this mean we have to forego the OSX tests?

[wilzbach]

So does this mean we have to forego the OSX tests?

To be clear: OSX is still fully tested for 64_32 and 64_64 on auto-tester.
Travis/Semaphore only tests bootstrapping with the latest release - in Martin's words:

so let me repeat what was decided when we made the frontend switch from C++ to D.

• Other platforms are bootstrapped by cross-compilation.
• DMD must be compilable with the latest stable/major release of dmd, ldc, and gdc.
  To enforce this policy the Travis-CI test was set up.

http://forum.dlang.org/post/zbxaviowooiaenaawmgs@forum.dlang.org

[JinShil]

Travis/Semaphore only tests bootstrapping with the latest release

Ok, so we are giving up the OSX bootstrap tests, right?

[wilzbach]

Ok, so we are giving up the OSX bootstrap tests, right?

Yep.

[jacob-carlborg]

What about macOS on CircleCI?

[wilzbach]

What about macOS on CircleCI?

We only get 500 minutes for free / month:

What if I am building open-source?
We also offer the Seed plan for macOS open-source projects:

2x macOS concurrency
Recommended for teams building 1-5 builds/day
500 max minutes/month*
...
Overages are as follows:
Seed & Startup: .08/minute

[jacob-carlborg]

We only get 500 minutes for free / month:

Right, forgot that part.

[MartinNowak]

There was an outage of OSX on Travis-Ci hence their huge backlog.
https://www.traviscistatus.com/incidents/6xb4kjczh4k6
Looks like they've upped their capacity just today.

As we were just digging into the purpose of that OSX test, we figured it became obsolete now that glibc/gcc is no longer used on OSX.
dlang/dlang-bot#69 (comment)
Here was the original cause that lead to the addition of the clang based OSX tester.
dlang/druntime#1542

So does this mean we have to forego the OSX tests?

Not at all, the auto-tester was and will remain our central CI infrastructure. Other things were only added to supplement it, or temporarily to bridge missing parts.