[Pvfs2-developers] failed assert in id_gen_safe_register()
Scott Atchley
atchley at myri.com
Mon Sep 10 09:34:54 EDT 2007
On Sep 10, 2007, at 9:27 AM, Sam Lang wrote:
>> What is the best way to catch changes like this so I can keep
>> bmi_mx up to date with CVS?
>
> Honestly I thought I had changed the id_gen_safe calls in bmi_mx to
> id_gen_fast calls, so that's my bad. To catch things like this, we
> should add nightly tests with the mx method enabled. We've got
> some nodes here with mx, but we don't always have access to them.
> If you've got a few nodes for testing, we can help you setup the
> tests and notification stuff to report to our tinderbox. In an
> ideal world, we would have regular performance tests of PVFS and
> the mx code running as well, but I suppose that's a pipe dream.
>
> -sam
You did change it but I did not catch it. I did a fresh checkout from
PVFS CVS and then replaced bmi_mx with my latest SVN checkout so that
I can make changes to support Open-MX.
I diff'd the files but I did not catch the change from *_safe_* to
*_fast_*. Would it be possible to send me patches when you make
changes so that our SVN stays in synch with your CVS?
Thanks,
Scott
More information about the Pvfs2-developers
mailing list