We have a strange situation on a 1.6.3 svn repo. I'm stopping short of
calling it a bug right now, but I suspect it is.
I have a handful of revisions (all from the same user and roughly the
same time) containing no changed paths, no changed props, etc.
Meaning: when I svnadmin dump those revisions, they have a log message,
author, etc, but no paths or props. (This is not the case of doing an
svn log from the "wrong" part of the tree and finding nothing. There is
nothing to be found.)
a. Any explanation for how that can happen?
b. worth filing a bug over?
In 191K revisions, we've never seen this before. We have an automated
process that pulls commit data into a SQL database that we use to
drive parts of our automated release process, so we have built monitors
to detect any "missing" revisions to prompt us to re-run the post-commit
hook to populate this data. Because these contain no paths, the post-
commit hook doesn't put enough data into the SQL DB to satisfy the
monitor that the revision was recorded and so it started squawking.
It doesn't appear to otherwise be hurting us, and I can easily "fix"
the monitor by putting a piece of electrical tape over this particular
warning, but I'd prefer to understand what happened, and if a bug,
Here's a sample dump entry for one of the "bad" revisions:
Electronic Expansion UpdateCRS09_3083CRS09_3083
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-09-28 23:40:42 CEST