Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CI: Remove Shippable & move AArch64 package generation to Travis #3733

Merged
merged 12 commits into from
Aug 13, 2021

Conversation

kinke
Copy link
Member

@kinke kinke commented May 20, 2021

As the service is sadly no more.

README.md Outdated
[5]: https://app.shippable.com/github/ldc-developers/ldc/runs?branchName=master
[6]: https://travis-ci.org/ldc-developers/ldc/branches
[7]: https://www.bountysource.com/teams/ldc-developers/issues
[5]: https://travis-ci.org/ldc-developers/ldc/branches
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You probably want to migrate to .com in the next 10 days, too: https://blog.travis-ci.com/2021-05-07-orgshutdown
But then you'll be hit with the rate limiting which made so many people drop Travis.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Argh, thx for the heads-up. The announcement that they'd drop .org in the upcoming weeks has been there for months, so I started not believing it. ;) - Too bad, I was positively surprised about the recent performance gains (AArch64 job done in ~23 mins) and thought it would allow for a smooth Shippable replacement, incl. AArch64 Linux package generation. IIRC, I don't have sufficient rights to migrate our existing account (been playing with .com a while back with a personal account, to play with their AArch64 Graviton CPU).

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, according to https://docs.travis-ci.com/user/billing-overview/#partner-queue-solution, Travis' AArch64 offering is sponsored by ARM and won't cost any credits.

@kinke kinke changed the title CI: Remove Shippable CI: Remove Shippable & move AArch64 package generation to Travis May 22, 2021
@kinke
Copy link
Member Author

kinke commented May 28, 2021

@dnadlinger @redstar: I cannot migrate the Travis ldc repo to .com, one of you guys will have to do it: https://travis-ci.com/organizations/ldc-developers/migrate. Edit: Oh and please migrate llvm-project too, I hope it's fast enough for prebuilding LLVM too.

@kinke
Copy link
Member Author

kinke commented Jun 5, 2021

TODO: add reggae as well, edit: and mimalloc

As the service is sadly no more.
@kinke kinke force-pushed the shippable branch 3 times, most recently from c978794 to 7dcaaaf Compare August 12, 2021 19:29
@kinke
Copy link
Member Author

kinke commented Aug 13, 2021

Alright, Travis and thus native AArch64 CI on Linux is back in business, and in better shape than ever, probably due to a combination of LLVM 12 and a more recent base image:

  • lit-tests results aren't ignored any longer, just 2 tests had to be disabled (facilitated by dynamic-compile not working with LLVM 12).
  • All gdb tests (except for one lit-test) now work and have been enabled.
  • LTO integration tests re-enabled as well.
  • Using default ld.gold for CI now, no more countless linker warnings requiring ld.bfd.
  • Prebuilt package uses mimalloc and bundles reggae.
  • CI performance has been really great so far (~25 mins), incl. single-core performance (multiple times higher than Shippable's). Overall, about twice as fast for the full LDC job here compared to Shippable; bottleneck being once more available RAM, not number of CPU cores (the lit-tests complete in ~10 seconds with 80 threads...).

@kinke kinke merged commit b21370e into ldc-developers:master Aug 13, 2021
@kinke kinke deleted the shippable branch August 13, 2021 02:43
@JohanEngelen
Copy link
Member

This is great news, nice work!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants