Change Details

As per parent task, it's possible that the origin computation urls was mixed up. Resulting in the same origin for different dumps. This needs to be investigated and fixed if it's actually true (at least one occurrence is referenced in the parent). This would also explain an error i saw about so far unexplained 'No revision found' on the latest svn loader dump scheduling.

As per parent task, it's possible that the origin computation urls was mixed up. Resulting in the same origin for different dumps. This needs to be investigated and fixed if it's actually true (at least one occurrence is referenced in the parent). Note: This would also explain an error so far unexplained 'No revision found' on the latest svn loader rescheduling.

As per parent task, it's possible that the origin computation urls was mixed up. Resulting in the same origin for different dumps. This needs to be investigated and fixed if it's actually true (at least one occurrence is referenced in the parent). Note: This would also explain an error i saw about so far unexplained 'No revision found' on the latest svn loader dump rescheduling.