Forums : Technical Issue Help

Hi,

I see the last update taken from impresscms dates from 2 months ago. there have been commits since that.

Could you take a look please?

Thanks!

David Janssens almost 15 years ago

David,

The failed job was one which was first started when we finalized the change to the way source code line counts were done to eliminate the negative line counts for some projects. It appears to have failed partway through. I have rescheduled that job and will monitor it until it is finished. Once that is done, normal updates should begin immediately. Will report back here with any progress.

Thanks!

ssnow-blackduck almost 15 years ago

I just checked tonight - it has failed on counting lines (step 3). Would you have another look?

Thanks!

Steve Kenow almost 15 years ago

Steve,

Thanks for the heads-up. I've restarted the job and will monitor it.

Thanks!

ssnow-blackduck almost 15 years ago

Hi!

I suspect it may be failing because of the sheer magnitude of the job. Please see:
https://www.ohloh.net/p/impresscms/analyses/latest
https://www.ohloh.net/p/impresscms/estimated_cost

70 000+ files!
23 million LoC

The current enlistment is:
https://impresscms.svn.sourceforge.net/svnroot/impresscms
Which includes all branches and releases...

Related: https://www.ohloh.net/forums/3491/topics/6043

Best regards,

M ;-)

Marc Laporte almost 15 years ago

Marc,

Thanks for the clarification! And I was wondering why it was taking forever to run ohcount... Sometimes you just can't see the forest for the trees!

ssnow-blackduck almost 15 years ago

We can certainly exclude certain parts of our repository. The core/branches and the core/tasks folders have no real use for ohloh, as they contain static snapshots of releases and a sandbox for experimenting.

That would cut the size of the repository considerably.

Is there a way to exclude certain paths?

David Janssens almost 15 years ago

David,

Yes you can exclude those directories if you like by clicking the Choose files to ignore link on the enlistments page. Problem is that it will not take effect until we finish one update.

See: https://www.ohloh.net/blog/LatestUpdatesToIgnoringFilesandDirectories
for assistance with the syntax for this.

P.S. If you don't need core/branches, core/releases and core/tasks, perhaps we would be better off with two enlistments:

https://impresscms.svn.sourceforge.net/svnroot/impresscms/core/trunk/

• and - https://impresscms.svn.sourceforge.net/svnroot/impresscms/addons/

Then we don't have any Choose files to ignore issues...

Thanks!

ssnow-blackduck almost 15 years ago

Hi blackduck,
addons contains quite a bit of our development activity, so you understand I'm reluctant to let it go.

If I add the listing for https://impresscms.svn.sourceforge.net/svnroot/impresscms/core/trunk/ first to get through the update a first time, would it be possible that I then change the repository back to https://impresscms.svn.sourceforge.net/svnroot/impresscms/, while excluding the tasks, releases and branches for the next update?

Thanks!

David Janssens almost 15 years ago

For now, I've removed the old enlistment and added https://impresscms.svn.sourceforge.net/svnroot/impresscms/core/trunk as a new enlistment.

David - we can work out how to incorporate addons back in

Most likely, we'll also want core/tasks as an enlistment because a lot of work may be done there as part of development, It is a temporary workspace, but the commits are significant there.

Steve Kenow almost 15 years ago

Steve and David,

I believe you will be able to bring addons in as a separate enlistment. It shouldn't matter that it is in the same repository. It all gets processed as a whole when it comes to the statistics and commits. As far as the ignores issue, I'm not sure but I'd bet that if the enlistment changes significantly, you'll need to re-install the ignores and wait for a full update before they can take effect. It's a frustration, I know but the only way we'll find out is to try it.

We could also try to add core/tasks as a third enlistment. If it is not overwhelmingly large, it should be no issue. The problems occur when projects add excessive numbers of enlistments which each carry some random chance of problems. The chance of failures from internet-related and repository-related failures don't go up linearly with numbers, they are more like exponential in nature. But three enlistments is quite manageable.

Thanks!

ssnow-blackduck almost 15 years ago

Steve and David,

All jobs for the two new enlistments finished OK. A new update started overnight. That also finished OK.

Analyze page is at Jun 10 2011 and last commit is at 2011-06-10.

Now it would be time to add addons, if desired.

Please let me know here if there are any further problems.

Thanks!

ssnow-blackduck almost 15 years ago