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: run whole testsuite in containers #179

Merged
merged 1 commit into from
Jul 5, 2016

Conversation

lucab
Copy link
Contributor

@lucab lucab commented Jun 20, 2016

Rework configuration to run testsuite into containerized
environments. This allows to run all tests on travis.

Rework configuration to run testsuite into containerized
environments. This allows to run all tests on travis.
@lucab
Copy link
Contributor Author

lucab commented Jun 22, 2016

Regarding the "creative" part of this PR, I think I'm quite bending travis here by ditching all of its language framework and going for vanilla containers here. For reviewers, some points to consider:

Cons:

  • testing multiple go-versions will be harder (sticking to packaged golang for simplicity now)
  • increased testing-time/complexity (due to having to setup a full container, run systemd on init and then attach to run the tests)

Pros:

  • allow full testing of all packages (before we were missing those depending on system session/bus)
  • allow testing multiple release / systemd packages (debian testing and latest ubuntu LTS for the moment, but more are easily added)

IMHO pros outweights cons, even if I would consider this kind of setup unconventional (ie. may break if travis decides to ditch it).

@jonboulle
Copy link
Contributor

I agree that pros > cons for now and would also consider this something of
an interim solution (it's definitely a step forward from the current lack
of test coverage, which is becoming more critical as we leverage go-systemd
more extensively).

On 22 June 2016 at 17:27, Luca Bruno notifications@github.com wrote:

Regarding the "creative" part of this PR, I think I'm quite bending travis
here by ditching all of its language framework and going for vanilla
containers here. For reviewers, some points to consider:

Cons:

  • testing multiple go-versions will be harder (sticking to packaged
    golang for simplicity now)
  • increased testing-time/complexity (due to having to setup a full
    container, run systemd on init and then attach to run the tests)

Pros:

  • allow full testing of all packages (before we were missing those
    depending on system session/bus)
  • allow testing multiple release / systemd packages (debian testing
    and latest ubuntu LTS for the moment, but more are easily added)

IMHO pros outweights cons, even if I would consider this kind of setup
unconventional (ie. may break if travis decides to ditch it).


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#179 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/ACewNxOL7dvLWfRR8mFTr9OxxUrPR9nwks5qOVRqgaJpZM4I5cGi
.

@s-urbaniak
Copy link

agreed with what has been said above, lgtm

@lucab lucab merged commit 4fdcc47 into coreos:master Jul 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants