The documentation does not describe what output a script should give when used with bzr bisect run

Bug #538025 reported by SirVer
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar Bisect Plugin
Fix Released
Undecided
Gustaf Thorslund

Bug Description

Should this be return values or output on stdio. Should this be "yes", "no", 0, 1 ? It would be nice to add this to the documentation.

Related branches

Revision history for this message
Václav Šmilauer (eudoxos) wrote :

Confirming, just bumped into that one. I had to read source to find out this:

                if retcode == 0:
                    done = self._set_state(None, 'yes')
                elif retcode == 125:
                    break
                else:
                    done = self._set_state(None, 'no')

So it should return 0 for yes, 125 for error (WTF??!), anything else for no.

Changed in bzr-bisect:
status: New → Confirmed
Revision history for this message
SirVer (sirver) wrote :

thanks vaclav. After realizing that bisect does not bisect into merge commits, i abandoned it again though. As it stands now it is quite useless for real distributed development.

Changed in bzr-bisect:
assignee: nobody → Gustaf Thorslund (gthorslund)
Changed in bzr-bisect:
status: Confirmed → In Progress
Changed in bzr-bisect:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.