I'll investigate the logs and report my findings...
[mailto:] On Behalf Of Robert
Sent: Tuesday, February 01, 2011 1:59 AM
Subject: Re: [vpb] vpbmaster build question...
It sounds like VPB is black listing cores due to errors on the tasks
that ran on these cores, so it's limiting the build to just the ones
that are working. VPB does this to handle outages on a network build
where problems on a single machine don't bring the whole build to a
If it is black listing that is limiting the cores that are available
then you'll need to look at the logs to see if there have been any
failures and any reports of blacklisting. You will find a logs
directory in the directory that you ran the build from and within this
there will be lots of separate .log files that will provide the output
from each osgdem run, one per task.
If it isn't black listing then you'll need to try running vpbmaster in
a debugger and see what is going w.r.t threading.
On Mon, Jan 31, 2011 at 11:43 PM, Shayne Tueller
Linux Fedora core 13. The number of tasks generated was 5314 for this build.
I fired off a VPB build using vpbmaster on a 16 processor machine running
As predicted, vpbmaster fired off 16 osgdem threads to work on the build.
running had slowly decreased until that now there are only 0 to 2 threads
As the build went along I noticed that the number of osgdem threads
running with about 2500 tasks remaining. I never see any more osgdem threads
than 2 being generated to work on the build. This seems a bit strange.
have been working as the build process went along to completion. There is no
Is this correct behavior? I would have thought that up to 16 threads would
indication of any errors in the output so far.
Has anyone else seen this or know what might be going on?
Read this topic online here:
Post generated by Mail2Forum