On Wed, Feb 08, 2006 at 07:08:35AM -0700, Ralph H. Castain wrote:
> Hi Gleb
>
> I just checked out another copy of the trunk and cannot replicate
> this problem. Could you take out a fresh trunk and see if it works
> for you? Could be something just got out of sync on your current
> checkout (s
On Feb 8, 2006, at 12:46 PM, Ralph H. Castain wrote:
In addition, I took advantage of the change to fix something Brian
had flagged in the orte/mca/rmgr/urm/rmgr_urm.c file where he noted
that the wireup of stdin for io forwarding should occur at the LAUNCH
stage (as opposed to the STG1 stage ga
Hey all -
A question for the group... I'm working on the build system changes
needed for the project split. I'm currently running into a bug in
Automake 1.9.5 and older that is causing me to have to do some fairly
nasty workarounds. The bug was fixed in AM 1.9.6, which has been out
for
Hmmmyuck! I'll take a look - will set it back to what it was
before in the interim.
Thanks
Ralph
At 07:05 AM 2/9/2006, you wrote:
On Feb 8, 2006, at 12:46 PM, Ralph H. Castain wrote:
> In addition, I took advantage of the change to fix something Brian
> had flagged in the orte/mca/rmgr/ur
Sounds fine with me - whatever makes the job easier for you.
Ralph
At 07:16 AM 2/9/2006, you wrote:
Hey all -
A question for the group... I'm working on the build system changes
needed for the project split. I'm currently running into a bug in
Automake 1.9.5 and older that is causing me to h
Okay, it turned out that the counters were not being adjusted as
processes hit the INIT and LAUNCHED stages - just a case where that
hadn't been implemented yet. I've fixed that now (it was easier to
fix than go back) and the wireup_stdin function is now being called.
Brian: can you verify tha
On Feb 9, 2006, at 9:56 AM, Ralph H. Castain wrote:
Sounds fine with me - whatever makes the job easier for you.
Ditto. I think the system is complex enough that adding workarounds
for known bugs in AM (especially ones that have been fixed and are
available to us) is not worthwhile.
--
That did the trick for me. Thanks!
Brian
On Feb 9, 2006, at 10:40 AM, Ralph H. Castain wrote:
Okay, it turned out that the counters were not being adjusted as
processes hit the INIT and LAUNCHED stages - just a case where that
hadn't been implemented yet. I've fixed that now (it was easier to
Nathan --
Ralph and I talked about this and decided not to bring it over to the
1.0 branch -- the fix uses new functionality that exists on the trunk
and not in the 1.0 branch. The fix could be re-crafted to use
existing functionality on the 1.0 branch (we're really trying to only
put bu
I've coded a hacky workaround in our code to get past this. Basically,
I capture all of the state transitions and the first one fired for a job
I fire the 'init' state internally in our tool. Generally this occurs
for one of the gate transitions, G1 or something. It'll work this way.
Furthe
10 matches
Mail list logo
