[Swift-devel] new commits

Sarah Kenny skenny at uchicago.edu
Tue Oct 5 18:11:17 CDT 2010


On Tue, Oct 5, 2010 at 4:13 PM, Mihael Hategan <hategan at mcs.anl.gov> wrote:

> On Tue, 2010-10-05 at 14:31 -0500, Sarah Kenny wrote:
> > On Tue, Oct 5, 2010 at 12:58 PM, Mihael Hategan <hategan at mcs.anl.gov>
> > wrote:
> >         I think I committed some changes based on your patch. One
> >         problem was
> >         that gram2 doesn't seem to support a job name. Did you find a
> >         way around
> >         that?
> >
> > hmm, it is working on abe (gram2) and queenbee (gram5)...were you
> > getting an error running it elsewhere or did it just not pick up the
> > name? i'm thinking if it works for some gram versions and not others
> > it might be ok to commit unless it actually causes an error in
> > versions where the name is not passed (?)
>
> That was the problem. It caused an error.
>

ok...do you know where you ran it that you were able to produce the error?



> >
> > i thought you had committed (or were going to commit) the change as
> > well, but i'm not seeing it here:
> >
> >
> http://cogkit.svn.sourceforge.net/viewvc/cogkit/branches/4.1.7/src/cog/modules/provider-coaster/src/org/globus/cog/abstraction/coaster/service/job/manager/Settings.java?revision=2623&view=markup&pathrev=2623
>
> It's in trunk.
>
> But:
>
> http://cogkit.svn.sourceforge.net/viewvc/cogkit/trunk/current/src/cog/modules/provider-gt2/src/org/globus/cog/abstraction/impl/execution/gt2/JobSubmissionTaskHandler.java?r1=2815&r2=2867
>
> >
> > is there somewhere else i should be looking?
> >
> >
> >
> >
> >         On Tue, 2010-10-05 at 12:26 -0500, Sarah Kenny wrote:
> >         > hi all, i have a fix to swift that allows the jobName
> >         parameter to be
> >         > passed to GRAM (so the job name actually shows up in the
> >         queue). this
> >         > will be my first commit to the cog/swift source so i want to
> >         know
> >         > where the best place is to do this? i'd like it to be in the
> >         stable
> >         > release so that it's there when we update. my user group
> >         (HNL) has
> >         > been using the stable branch with this fix added for several
> >         months so
> >         > it's pretty well-tested.
> >         >
> >         > i guess the question is would it be best to commit this to
> >         the
> >         > development code (which as i understand is
> >         cogkit/trunk/current) to be
> >         > migrated to the stable code (cogkit/branches/4.1.7) in the
> >         near future
> >         > when we decide to update the stable branch?
> >         >
> >         > also, i'm guessing i'll need to get access (from mihael or
> >         mike
> >         > wilde?) to the cog source...
> >
> >
> >         I can do that. Do you have a sourceforge account?
> >
> >
> >
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/swift-devel/attachments/20101005/2db249f4/attachment.html>


More information about the Swift-devel mailing list