| 2009-11-17 03:59:17 |
Dragomir Minkovski |
description |
Hello.
I grab this branch: https://code.launchpad.net/~mysql/mysql-server/mysql-6.0-codebase-bugfixing
and I do
cd mysql-6.0-codebase-bugfixing
bzr branch -r tag:mysql-6.0.10 . ../a
bzr branch -r tag:mysql-6.0.9 . ../b
cd a
bzr --no-aliases --no-plugins missing --include-merges ../b
and it shows 2491 revisions, quite a possible result. Then I do
bzr --no-aliases --no-plugins log -n0 -r tag:mysql-6.0.9..-1
and it shows 8 revisions. That 8 is weird to me; I expected the log command to print "all revisions on the path from 6.0.9 to -1 (including merged ones, due to -n0)", and thus I expected to see the same as what's missing between b and a; I expected 2491. Those 8 revisions don't reflect at all the difference between 6.0.9 and -1 (in terms of code changes).
Is this normal?
What is the definition of "bzr log -rX..Y" ("bzr help log" says "-rX..Y display from X to Y inclusive") ?
This is a problem because it confuses an automated regression searching tool that we use (the tool takes a start and an end revision, and does bisection to find where a bug was introduced; it uses "bzr log" to find the path to bisect; and here those few 8 revisions are not the proper path).
Using bzr.dev:
Bazaar (bzr) 2.1.0dev3
from bzr checkout /home/mysql_src/logiciels/bzr_versions/bzr.dev
revision: 4782
revid: pqm@pqm.ubuntu.com-20091103035826-tr4qa6fznzmirgiq
branch nick: bzr.dev |
This is a Sun/MySQL - Canonical escalation imported into Launchpad by the Canonical Support Team (internal case 6612 )
Original escalation: 2009-11-16 10:12 UTC
Hello.
I grab this branch: https://code.launchpad.net/~mysql/mysql-server/mysql-6.0-codebase-bugfixing
and I do
cd mysql-6.0-codebase-bugfixing
bzr branch -r tag:mysql-6.0.10 . ../a
bzr branch -r tag:mysql-6.0.9 . ../b
cd a
bzr --no-aliases --no-plugins missing --include-merges ../b
and it shows 2491 revisions, quite a possible result. Then I do
bzr --no-aliases --no-plugins log -n0 -r tag:mysql-6.0.9..-1
and it shows 8 revisions. That 8 is weird to me; I expected the log command to print "all revisions on the path from 6.0.9 to -1 (including merged ones, due to -n0)", and thus I expected to see the same as what's missing between b and a; I expected 2491. Those 8 revisions don't reflect at all the difference between 6.0.9 and -1 (in terms of code changes).
Is this normal?
What is the definition of "bzr log -rX..Y" ("bzr help log" says "-rX..Y display from X to Y inclusive") ?
This is a problem because it confuses an automated regression searching tool that we use (the tool takes a start and an end revision, and does bisection to find where a bug was introduced; it uses "bzr log" to find the path to bisect; and here those few 8 revisions are not the proper path).
Using bzr.dev:
Bazaar (bzr) 2.1.0dev3
from bzr checkout /home/mysql_src/logiciels/bzr_versions/bzr.dev
revision: 4782
revid: pqm@pqm.ubuntu.com-20091103035826-tr4qa6fznzmirgiq
branch nick: bzr.dev
|
|
