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

travis: introduce multi-arch configuration #231

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

mrc0mmand
Copy link
Member

@mrc0mmand mrc0mmand commented Jan 23, 2020

This PR supersedes #230 by moving testing into Travis CI, so we can test casync on multiple architectures. Currently it runs on:

  • x86_64
  • x86
  • s390x
  • ppc64le
  • aarch64

It also uses Ubuntu Bionic instead of Xenial, so no more python 3.6 issues. After merging, the Semaphore CI for this repo can be turned off, but I'll pursue the migration to Semaphore v2 in other repos (mkosi & systemd).

/cc @evverx, @keszybz, @poettering

@mrc0mmand mrc0mmand force-pushed the setup-travis branch 10 times, most recently from 3fd423b to 7088cad Compare January 23, 2020 09:58
@mrc0mmand mrc0mmand changed the title [WIP] travis: introduce multi-arch configuration travis: introduce multi-arch configuration Jan 23, 2020
@mrc0mmand mrc0mmand mentioned this pull request Jan 23, 2020
@evverx
Copy link
Member

evverx commented Jan 24, 2020

@mrc0mmand thank you!

As far as I know, travis_terminate should be called somewhere to prevent Travis from freezing when jobs fail (on arm at least). Could you try building casync with UBSan (so that the tests would fail) to figure out whether travis_terminate still should be used instead of exit?

@evverx
Copy link
Member

evverx commented Jan 24, 2020

Judging by https://travis-ci.org/systemd/systemd/jobs/639931506 (where it took Travis 10 minutes to terminate the job after it failed) it seems travis_terminate is still necessary.

@evverx
Copy link
Member

evverx commented Jan 24, 2020

One last thing. By the looks of it, the project isn't actively maintained so I'm not sure whether it makes sense to try to keep testing it (or try to additionally bring ASan+UBsan, Coverity and so on). I'd put the PR on hold and wait for @poettering to chime in.

@keszybz
Copy link
Member

keszybz commented Aug 20, 2022

Damn. Travis is gone now too.

@keszybz
Copy link
Member

keszybz commented Aug 20, 2022

Hmm, I think we want to keep this alive. @mrc0mmand do you think you could add the magic to switch to github actions?

@keszybz
Copy link
Member

keszybz commented Aug 20, 2022

Scratch that. I'll talk with @poettering if we want to keep this project alive.

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

Successfully merging this pull request may close these issues.

None yet

3 participants