--strict should be the default

Bug #277376 reported by Andrew Bennetts
4
Affects Status Importance Assigned to Milestone
Bazaar Usertest
Fix Released
Medium
Unassigned

Bug Description

--strict should be on by default. If e.g. a "bzr init-repo DIR" call fails, it could fundamentally change the test results. But without --strict if that were to fail the output would still appear normal; i.e. you'd get dodgy results but no indication that the results aren't trustworthy.

Martin Pool (mbp)
Changed in bzr-usertest:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Martin Pool (mbp) wrote :

As a workaround for this, I've changed the script that drives http://benchmark.bazaar-vcs.org/ to pass --strict.

Revision history for this message
Martin Pool (mbp) wrote :

It turns out that using --strict in fact fails at present, because the diff tests don't expect exitcode=1 when there are changes. That should be easy to fix in the test script.

Revision history for this message
Martin Pool (mbp) wrote :

This branch changes the behaviour, but has not yet updated the scripts to actually work (wbn)

Changed in bzr-usertest:
status: Confirmed → 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.