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: Move emscripten to ubuntu docker builds #105

Closed
wants to merge 2 commits into from

Conversation

Squareys
Copy link
Contributor

Hi @mosra !

This is an initial test to switch to the emscripten docker image with ubuntu base image.

Best,
Jonathan

@codecov
Copy link

codecov bot commented Nov 18, 2020

Codecov Report

Merging #105 (9654456) into master (92daf1a) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #105   +/-   ##
=======================================
  Coverage   97.56%   97.56%           
=======================================
  Files          98       98           
  Lines        7193     7193           
=======================================
  Hits         7018     7018           
  Misses        175      175           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 92daf1a...9654456. Read the comment docs.

@Squareys Squareys force-pushed the switch-emsc-ci branch 6 times, most recently from 18be680 to 7e53641 Compare November 18, 2020 09:47
@Squareys Squareys changed the title ci: WIP move to emscripten docker builds (ubuntu based) ci: Move emscripten to ubuntu docker builds Nov 18, 2020
@Squareys
Copy link
Contributor Author

@mosra Ready for review/merge! :)

Copy link
Owner

@mosra mosra left a comment

Choose a reason for hiding this comment

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

I don't want spend time switching as I have other things to do right now, but when the time comes, it'll definitely be handy. Thank you! 👍

wget https://github.com/ninja-build/ninja/releases/download/v1.8.2/ninja-linux.zip
unzip ninja-linux.zip
mv ninja /usr/local/bin/
ninja --version
Copy link
Owner

Choose a reason for hiding this comment

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

Heh. I suppose apt install ninja just doesn't work on docker, right?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Oh, actually sure, that would work, if there's a package (I assume it's called ninja-build, though?)

Copy link
Owner

Choose a reason for hiding this comment

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

In the yml it's listed among the packages, but I think it's ninja-build, yes.

# Using whatever is the default, since that could be hopefully most
# up-to-date
env:
- JOBID=emscripten
- TARGET=emscripten
- EMSCRIPTEN_VERSION=2.0.7
Copy link
Owner

Choose a reason for hiding this comment

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

I want to test on the oldest version available, ideally exactly what was there on Mac (1.38.42)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The docker image supports everything above 1.39.0, 1.38.42 is pretty ancient

Copy link
Owner

Choose a reason for hiding this comment

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

ok then 1.39.0 :)

-DCMAKE_BUILD_TYPE=Release \
-DCMAKE_CXX_FLAGS_RELEASE="-DNDEBUG -O1" \
-DCMAKE_INSTALL_PREFIX=$HOME/deps \
-DCMAKE_EXE_LINKER_FLAGS_RELEASE="-O1" \
-DBUILD_TESTS=ON \
-G Ninja
ninja -j4
ninja -j2
Copy link
Owner

Choose a reason for hiding this comment

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

Just ninja, it should figure out the cores on its own.

I faintly remember I had to do this because otherwise at some point it was running 8 jobs at once, running out of memory. Probably not an issue nowadays anymore.

@mosra mosra added this to the 2020.0b milestone Nov 21, 2020
@mosra
Copy link
Owner

mosra commented Nov 21, 2020

Travis forced me to a extremely limited trial plan way sooner than I expected, so this is critically important now. Merged as 824a74c, this one build cost me 1120 credits out of the 10k, the build on master will be another 1120 and then I have maybe one Magnum build left and there we are.

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

Successfully merging this pull request may close these issues.

2 participants