Felipe Contreras <felipe.contreras@xxxxxxxxx> writes: > I'm rerolling this series with the changes fron Junio, plus a bit more cleanups. > > I dropped the last patch, because I found an issue and a separate patch series > would take care of that. Other than that the main changes remain the same. > > The old remote-testgit is now remote-testpy (as it's testing the python > framework, not really remote helpers). The tests are simplified, and exercise > more features of transport-helper, and unsuprisingly, find more bugs. Thanks. I've queued [v6 p1.1] but not later parts (yet). The result merged to 'pu' however seems to break t5800. It could be a stupid and trivial merge error or something, but I didn't look into the details. Could interested parties take a look? $ cd t && sh ./t5800-remote-testpy.sh ok 1 - setup repository ok 2 - cloning from local repo ok 3 - cloning from remote repo ok 4 - create new commit on remote ok 5 - pulling from local repo ok 6 - pulling from remote remote ok 7 - pushing to local repo not ok 8 - synch with changes from localclone # # (cd clone && # git pull) # not ok 9 - pushing remote local repo # # (cd clone && # echo content >>file && # git commit -a -m four && # git push) && # compare_refs clone HEAD server HEAD # ok 10 - fetch new branch not ok 11 - fetch multiple branches # # (cd localclone && # git fetch # ) && # compare_refs server master localclone refs/remotes/origin/master && # compare_refs server new localclone refs/remotes/origin/new # not ok 12 - push when remote has extra refs # # (cd clone && # echo content >>file && # git commit -a -m six && # git push # ) && # compare_refs clone master server master # ok 13 - push new branch by name not ok 14 - push new branch with old:new refspec # TODO known breakage ok 15 - proper failure checks for fetching not ok 16 - proper failure checks for pushing # TODO known breakage # still have 2 known breakage(s) # failed 4 among remaining 14 test(s) 1..16 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html