Github user spodkowinski commented on the issue:
https://github.com/apache/cassandra-dtest/pull/13
The main motivation here was to be able to fix dtests just by merging a PR
on the ccm test-branch. Currently what needs to be done for ccm fixes to become
effective, is to cut a ccm release and afterwards upgrade the version the
dtest's `requirements.txt`. That's not very efficient if you just want to fix a
single dtest.
In this case, it would be better to un-couple dtests from regular ccm
releases, both to get dtests results green again more quickly and not having to
publish ccm releases that are addressing issues not relevant outside the
context of dtests (e.g.
https://github.com/pcmanus/ccm/commit/ff47a9f4339da2dacea16713bb2360b1b04b70c2).
As for bisecting, we could also use a git commit instead of a branch in
`requirements.txt` Or use both, regular releases that are known to be working
and individual commits for bug fixes in between.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
