Add CI testing against dev branches of deepcell-toolbox and deepcell-tracking #636
Conversation
There was a problem hiding this comment.
Just wanted to confirm that this will test against latest commit to master (e.g. not other branches that might still be wip) for each each of the deepcell-* repos?
I like this pattern and we should consider adding the same enhancement to the deepcell-tracking since it is dependent on deepcell-toolbox.
Correct - this sets up tests against
Agreed! |
Test against the development branches of the deepcell- dependencies: deepcell-toolbox and deepcell-tracking. This should help catch incompatibilities between unreleased versions of libraries in the deepcell ecosystem.
rossbar
force-pushed
the
ci/test-against-deepcell-dev
branch
from
17767d5
to
ed19648
Compare
|
Sorry for the swirling - I wasn't convinced this was installing the dev branches correctly. Merging now! |
This should help catch incompatibilities between unreleased versions of libraries in the deepcell ecosystem.
What
Why
deepcell-tfdepends ondeepcell-trackinganddeepcell-toolbox. If there is a change in one of these dependencies, there is no way to tell in the automated test running whether this will break something indeepcell-tfuntil the underlying libraries are released. Testing against the dev branches will catch potential issues sooner, at the expense of being noisier and reducing test specificity (failures can originate from either deepcell-tf or the dependencies). Overall however I think this should improve the ability to things consistent across libraries.