-
Notifications
You must be signed in to change notification settings - Fork 17
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
Switch to Github Action docker-based CI #48
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
charleskawczynski
force-pushed
the
GithubAction/Docker
branch
from
April 1, 2020 22:44
2e787a4
to
9a23863
Compare
Codecov Report
@@ Coverage Diff @@
## master #48 +/- ##
==========================================
- Coverage 58.64% 3.96% -54.68%
==========================================
Files 12 12
Lines 486 504 +18
==========================================
- Hits 285 20 -265
- Misses 201 484 +283
Continue to review full report at Codecov.
|
charleskawczynski
force-pushed
the
GithubAction/Docker
branch
18 times, most recently
from
April 3, 2020 23:47
c19fc94
to
8761144
Compare
charleskawczynski
changed the title
Create dockerimage.yml
Switch to Github Action docker-based CI
Apr 3, 2020
bors r+ |
bors bot
added a commit
that referenced
this pull request
Apr 3, 2020
48: Switch to Github Action docker-based CI r=charleskawczynski a=charleskawczynski Co-authored-by: Charles Kawczynski <[email protected]>
charleskawczynski
force-pushed
the
GithubAction/Docker
branch
from
April 4, 2020 00:21
8761144
to
45409a3
Compare
Canceled |
bors r+ |
bors bot
added a commit
that referenced
this pull request
Apr 4, 2020
48: Switch to Github Action docker-based CI r=charleskawczynski a=charleskawczynski Since we've been having build/environment issues, I thought it might be worth giving a docker-based CI a try. The way this works is: - CI is now controlled by a Github Action - The GHA checks out the PR/master and builds a docker image on top of the Julia docker image - The docker image is then used to run the tests The hope is that this will stabilize the build environment since everything is built from docker, which should be a clean slate each build, rather than runners whose environments potentially change (which was the case for the last failure on Travis). This also removes a handful of deps and source code, but we'll add these back in incrementally. Co-authored-by: Charles Kawczynski <[email protected]>
charleskawczynski
force-pushed
the
GithubAction/Docker
branch
from
April 4, 2020 00:27
45409a3
to
4e070c3
Compare
Canceled |
bors r+ |
bors r+ |
bors bot
added a commit
that referenced
this pull request
Apr 5, 2020
48: Switch to Github Action docker-based CI r=charleskawczynski a=charleskawczynski Since we've been having build/environment issues, I thought it might be worth giving a docker-based CI a try. The way this works is: - CI is now controlled by a Github Action - The GHA checks out the PR/master and builds a docker image on top of the Julia docker image - The docker image is then used to run the tests The hope is that this will stabilize the build environment since everything is built from docker, which should be a clean slate each build, rather than runners whose environments potentially change (which was the case for the last failure on Travis). This also removes a handful of deps and source code, but we'll add these back in incrementally. Co-authored-by: Charles Kawczynski <[email protected]>
charleskawczynski
force-pushed
the
GithubAction/Docker
branch
from
April 5, 2020 16:52
3f39fc3
to
6677d11
Compare
Canceled |
bors r+ |
bors bot
added a commit
that referenced
this pull request
Apr 5, 2020
48: Switch to Github Action docker-based CI r=charleskawczynski a=charleskawczynski Since we've been having build/environment issues, I thought it might be worth giving a docker-based CI a try. The way this works is: - CI is now controlled by a Github Action - The GHA checks out the PR/master and builds a docker image on top of the Julia docker image - The docker image is then used to run the tests The hope is that this will stabilize the build environment since everything is built from docker, which should be a clean slate each build, rather than runners whose environments potentially change (which was the case for the last failure on Travis). This also removes a handful of deps and source code, but we'll add these back in incrementally. Co-authored-by: Charles Kawczynski <[email protected]>
charleskawczynski
force-pushed
the
GithubAction/Docker
branch
from
April 5, 2020 16:59
6677d11
to
eac3eec
Compare
Canceled |
bors r+ |
bors bot
added a commit
that referenced
this pull request
Apr 5, 2020
48: Switch to Github Action docker-based CI r=charleskawczynski a=charleskawczynski Since we've been having build/environment issues, I thought it might be worth giving a docker-based CI a try. The way this works is: - CI is now controlled by a Github Action - The GHA checks out the PR/master and builds a docker image on top of the Julia docker image - The docker image is then used to run the tests The hope is that this will stabilize the build environment since everything is built from docker, which should be a clean slate each build, rather than runners whose environments potentially change (which was the case for the last failure on Travis). This also removes a handful of deps and source code, but we'll add these back in incrementally. Co-authored-by: Charles Kawczynski <[email protected]>
Canceled |
charleskawczynski
force-pushed
the
GithubAction/Docker
branch
from
April 5, 2020 17:05
eac3eec
to
4937de5
Compare
bors r+ |
bors bot
added a commit
that referenced
this pull request
Apr 5, 2020
48: Switch to Github Action docker-based CI r=charleskawczynski a=charleskawczynski Since we've been having build/environment issues, I thought it might be worth giving a docker-based CI a try. The way this works is: - CI is now controlled by a Github Action - The GHA checks out the PR/master and builds a docker image on top of the Julia docker image - The docker image is then used to run the tests The hope is that this will stabilize the build environment since everything is built from docker, which should be a clean slate each build, rather than runners whose environments potentially change (which was the case for the last failure on Travis). This also removes a handful of deps and source code, but we'll add these back in incrementally. Co-authored-by: Charles Kawczynski <[email protected]>
charleskawczynski
force-pushed
the
GithubAction/Docker
branch
from
April 5, 2020 17:15
4937de5
to
e89812a
Compare
Canceled |
bors r+ |
bors bot
added a commit
that referenced
this pull request
Apr 5, 2020
48: Switch to Github Action docker-based CI r=charleskawczynski a=charleskawczynski Since we've been having build/environment issues, I thought it might be worth giving a docker-based CI a try. The way this works is: - CI is now controlled by a Github Action - The GHA checks out the PR/master and builds a docker image on top of the Julia docker image - The docker image is then used to run the tests The hope is that this will stabilize the build environment since everything is built from docker, which should be a clean slate each build, rather than runners whose environments potentially change (which was the case for the last failure on Travis). This also removes a handful of deps and source code, but we'll add these back in incrementally. Co-authored-by: Charles Kawczynski <[email protected]>
Timed out |
charleskawczynski
force-pushed
the
GithubAction/Docker
branch
from
April 9, 2020 15:45
e89812a
to
ac4baa0
Compare
bors try |
tryBuild succeeded |
bors r+ |
Build succeeded: |
Closed
7 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since we've been having build/environment issues, I thought it might be worth giving a docker-based CI a try. The way this works is:
The hope is that this will stabilize the build environment since everything is built from docker, which should be a clean slate each build, rather than runners whose environments potentially change (which was the case for the last failure on Travis).
This also removes a handful of deps and source code, but we'll add these back in incrementally.