Hello,
git bisect is very usefull to find which commit in a given branch
break some tests.
It is a usefull automated debug tool.
Here's a first version of git bisect howto with Qserv :
1. Install Qserv following the last version of README file : https://dev.lsstcorp.org/cgit/LSST/DMS/qserv.git/tree/README.txt?h=u/fjammes/DM-699
2. clone Qserv :
cd ~/src
git clone [log in to unmask]:LSST/DMS/qserv
3. If you want to find which commit broke the master branch, after
commit ded65eff5b98b793604a35d081276748f2eff188, you can run :
git bisect start HEAD
ded65eff5b98b793604a35d081276748f2eff188 --
git bisect run tests/tools/run-tests.sh
run-tests.sh, which configure Qserv and launch integration tests,
will be launched for each commits between
ded65eff5b98b793604a35d081276748f2eff188 and HEAD, in master branch,
and git bisect will tell you which commit broke the tests in master
branch, assuming tests were runned successfully in
ded65eff5b98b793604a35d081276748f2eff188.
You can use this procedure in any branch which have at least one
commit which support integration tests execution.
This procedure is still in beta version, and your help would be
appreciated in order to improve it.
WARN : Before using this procedure please wait for
u/fjammes/DM-699 to be merged. Indeed, last Qserv versions
depends on qservdata and qservdata has been removed from distserver.
That's why it is difficult to have a commit of Qserv in master
branch which supports the integration tests, excepts if you install
test datasets by hand. Having such a commit is a pre-requisite for
git bisect to work.
Cheers,
Fabrice
Use REPLY-ALL to reply to list
To unsubscribe from the QSERV-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1
