-
Notifications
You must be signed in to change notification settings - Fork 36
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
Remove manylinux container from CI #670
Conversation
- name: Run TFLite Ops and Core CC Unit Tests | ||
run: ./bazelisk test larq_compute_engine/tests:cc_tests --copt=-O2 --distinct_host_configuration=false --test_output=all | ||
- name: Install pip dependencies | ||
run: pip install numpy --no-cache-dir |
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.
I think we also used to also need six
for TF to build properly. Not sure if this is still the case.
run: pip install numpy --no-cache-dir | |
run: pip install numpy six --no-cache-dir |
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.
Thanks for the tip, lets see what CI does.
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.
This also decreased the build time from ~18min to around ~13min 🚀
What do these changes do?
In our private fork we had problems where the manylinux container is too outdated for our unittests. Combined with the fact that it doesn't actually test anything (the tested code does not really overlap with the converter, which is the only thing that we use the manylinux container for), it makes more sense to remove the container from CI.
How Has This Been Tested?
CI