-
Notifications
You must be signed in to change notification settings - Fork 41
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
Fix tests and cache containers for CI #160
Conversation
Co-authored-by: Sebastian Castro <4603398+sea-bass@users.noreply.github.com>
a854b31
to
c283a86
Compare
Well, this saved a good chunk of time for the ROS tests! There's probably a way to also make a Docker image for the ROS-free version so that the PDDLStream building is similarly cached... but definitely not necessary. I'm good to approve this whenever you tell me it's ready, @eholum ! |
Woohoo!
I started down this road by adding a new non-ros target to the dockerfile but probably don't have the strength of will to tackle that as part of this PR.
Right now this is going to cache and push everything to a single "main" image. Probably not a huge deal until someone starts pulling and using images instead of building locally, but as long as your compose file doesn't reference what you're using in CI it won't matter for users. For CI, having multiple PRs open at once and you'll start stepping on each other's toes. We could tag with branch names at the cost of having to occasionally clear out the registry. Do you have a preference? |
I don't think this repo is active enough / the dependencies will change frequently enough to do per branch caching at this moment. So I'm OK keeping it as is for now. |
Replacing: #159, since I have absolute power now.
Resolves: #85
This PR:
run_tests.sh
script returns an accurate failure code if tests fail