| Summary: | broken repository data (SVN) for Object Teams | ||
|---|---|---|---|
| Product: | Community | Reporter: | Stephan Herrmann <stephan.herrmann> |
| Component: | Dashboard | Assignee: | Portal Bugzilla Dummy Inbox <portal-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | douglas.clarke |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Stephan Herrmann
There is some inconsistency wrt to how the top-level project is represented in the SVN repositories. I've added some special-case handling code to work around it and it seems to be doing the job. Did you change the repository information in the project metadata last weekend? tools.objectteams isn't represented in the dash database, but the chart information (which is generated from the database and cached) is there. Very bizarre. I am investigating. (In reply to comment #1) > There is some inconsistency wrt to how the top-level project is represented in > the SVN repositories. I've added some special-case handling code to work around > it and it seems to be doing the job. Thanks, commit data on the old project summary are back. But no change on the new page. Is that what you're seeing, too? > Did you change the repository information in the project metadata last weekend? No change. Has always been /tools/org.eclipse.objectteams (where is the cvs/svn bit stored?) > tools.objectteams isn't represented in the dash database, but the chart > information (which is generated from the database and cached) is there. Very > bizarre. I am investigating. And still: the new page gives, e.g., May 2011: 183. The old pages says 05/11: 1206. This doesn't look like the same database :-/ *** Bug 352353 has been marked as a duplicate of this bug. *** The problem manifested again over the weekend. I am in the process of filling in the missing data. It seems that the source of the problem is a change made in one of the files that processes SVN data (svn-parse.pl to be specific). The file itself works fine, but when the automated process extracts the file out of CVS, it didn't set the execute property. This resulted in a permission error that prevented all SVN repositories from being processed. We have added a line to our script that should ensure that the execute bit is properly set. I am marking this as fixed. |