-
Notifications
You must be signed in to change notification settings - Fork 738
Updated make file for docker building to perform extra sanity tests #533
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
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm % testing in CI without a CIRCLE_TAG
.circleci/config.yml
Outdated
command: make -C ./docker version=${CIRCLE_TAG} build | ||
- run: | ||
name: test | ||
command: make -C ./docker version=${CIRCLE_TAG} test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is no CIRCLE_TAG set when for build-docker-image I think. Its designed to run on all commits just not just releases.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed just found that on the portal, added some fix for that in following commit.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like it works just fine. So basically now it will always build against the latest tagged version.
20a604f
to
d144cc8
Compare
@sbc100 after some fighting with CircleCi I was able to reproduce an original reason why I've added entrypoint:
This is result of non-standard user used in Circle Ci (that is not 1000:1000). Should I revert entrypoint and add support for that? |
I think the fix is that the emscripten root needs to be writable due to the code in emscripten that checks if the emscripten root is writable. I think adding this line should fix it:
We should probably update the emscripten code so that only the cache directory (and not the containing directory need to be writable). |
d144cc8
to
4774741
Compare
# compilation as non-root | ||
docker run --rm -u `id -u`:`id -g` -e HOME=/tmp -v `pwd`:/src -w /src emscripten/emsdk:${version} \ | ||
bash -c "\ | ||
mkdir -p .test \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why the .
prefix here? Why not just test?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not a particular reason, just convention - I can change that.
docker run --rm -u `id -u`:`id -g` -e HOME=/tmp --net=host emscripten/emsdk:${version} embuilder build zlib | ||
|
||
# compilation without entrypoint | ||
docker run --rm -e /bin/bash -v `pwd`:/src -w /src emscripten/emsdk:${version} \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you mean to not include -u
here?
Reapply #526
This change:
make
commands for CircleCI, and addstest
stepTo be merged after: #530