From aespinosa at cs.uchicago.edu Fri Apr 1 05:35:00 2011
From: aespinosa at cs.uchicago.edu (Allan Espinosa)
Date: Fri, 1 Apr 2011 05:35:00 -0500
Subject: [Swift-devel] [Bug 291] New: Add a exists() function to test for
file existence
In-Reply-To:
References:
Message-ID:
Would it be better to handle it as an exception?
type file;
app foo (file x) {
foo x;
}
app (file x) produce_a () {
}
file a <"dne">;
try{
foo (a);
}
catch (dne) {
a = produce_a();
foo(a);
}
2011/3/31 :
> https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=291
>
> ? ? ? ? ? Summary: Add a exists() function to test for file existence
> ? ? ? ? ? Product: Swift
> ? ? ? ? ? Version: 0.93
> ? ? ? ? ?Platform: PC
> ? ? ? ?OS/Version: Mac OS
> ? ? ? ? ? ?Status: NEW
> ? ? ? ? ?Severity: enhancement
> ? ? ? ? ?Priority: P1
> ? ? ? ? Component: SwiftScript language
> ? ? ? ?AssignedTo: wozniak at mcs.anl.gov
> ? ? ? ?ReportedBy: wilde at mcs.anl.gov
>
>
> Requested by John Dennis / NCAR.
>
> --
> Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are watching the reporter.
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>
>
--
Allan M. Espinosa
PhD student, Computer Science
University of Chicago
From bugzilla-daemon at mcs.anl.gov Fri Apr 1 05:49:34 2011
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Fri, 1 Apr 2011 05:49:34 -0500 (CDT)
Subject: [Swift-devel] [Bug 299] New: deadlock on workflow
Message-ID:
https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=299
Summary: deadlock on workflow
Product: Swift
Version: 0.92
Platform: PC
OS/Version: Linux
Status: ASSIGNED
Severity: major
Priority: P2
Component: SwiftScript language
AssignedTo: hategan at mcs.anl.gov
ReportedBy: aespinosa at cs.uchicago.edu
Related thread:
http://mail.ci.uchicago.edu/pipermail/swift-devel/2011-February/007476.html
--
Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
From bugzilla-daemon at mcs.anl.gov Fri Apr 1 05:53:26 2011
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Fri, 1 Apr 2011 05:53:26 -0500 (CDT)
Subject: [Swift-devel] [Bug 301] New: hang checker waiting on a partially
executed job
Message-ID:
https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=301
Summary: hang checker waiting on a partially executed job
Product: Swift
Version: trunk
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: SwiftScript language
AssignedTo: hategan at mcs.anl.gov
ReportedBy: aespinosa at cs.uchicago.edu
Swift's listening for a job that's at least in 'Initializing shared directory
state'. The job does not progress after that.
Related thread:
http://mail.ci.uchicago.edu/pipermail/swift-devel/2011-March/007662.html
The problem of the hanging job maybe related to Bug 299
(https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=299)
--
Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
From bugzilla-daemon at mcs.anl.gov Fri Apr 1 06:14:59 2011
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Fri, 1 Apr 2011 06:14:59 -0500 (CDT)
Subject: [Swift-devel] [Bug 273] resume is currently broken
In-Reply-To:
References:
Message-ID: <20110401111459.389801C072@wind.mcs.anl.gov>
https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=273
Allan Espinosa changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|resume is currently broken |resume is currently broken
|(trunk) |
--
Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
From bugzilla-daemon at mcs.anl.gov Fri Apr 1 06:38:27 2011
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Fri, 1 Apr 2011 06:38:27 -0500 (CDT)
Subject: [Swift-devel] [Bug 307] New: array slicing
Message-ID:
https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=307
Summary: array slicing
Product: Swift
Version: trunk
Platform: PC
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P2
Component: SwiftScript language
AssignedTo: hategan at mcs.anl.gov
ReportedBy: aespinosa at cs.uchicago.edu
Feature request:
http://mail.ci.uchicago.edu/pipermail/swift-user/2011-March/001881.html
--
Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
From tim.g.armstrong at gmail.com Fri Apr 1 10:22:55 2011
From: tim.g.armstrong at gmail.com (Tim Armstrong)
Date: Fri, 1 Apr 2011 10:22:55 -0500
Subject: [Swift-devel] [Bug 291] New: Add a exists() function to test for
file existence
In-Reply-To:
References:
Message-ID:
Try/catch statements don't have a clean intepretation if you're trying to
follow the flow of data through the program.
On Fri, Apr 1, 2011 at 5:35 AM, Allan Espinosa wrote:
> Would it be better to handle it as an exception?
>
> type file;
>
> app foo (file x) {
> foo x;
> }
>
> app (file x) produce_a () {
> }
>
> file a <"dne">;
>
> try{
> foo (a);
> }
> catch (dne) {
> a = produce_a();
> foo(a);
> }
>
> 2011/3/31 :
> > https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=291
> >
> > Summary: Add a exists() function to test for file existence
> > Product: Swift
> > Version: 0.93
> > Platform: PC
> > OS/Version: Mac OS
> > Status: NEW
> > Severity: enhancement
> > Priority: P1
> > Component: SwiftScript language
> > AssignedTo: wozniak at mcs.anl.gov
> > ReportedBy: wilde at mcs.anl.gov
> >
> >
> > Requested by John Dennis / NCAR.
> >
> > --
> > Configure bugmail:
> https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
> > ------- You are receiving this mail because: -------
> > You are watching the reporter.
> > _______________________________________________
> > Swift-devel mailing list
> > Swift-devel at ci.uchicago.edu
> > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> >
> >
>
>
>
> --
> Allan M. Espinosa
> PhD student, Computer Science
> University of Chicago
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From tim.g.armstrong at gmail.com Fri Apr 1 10:23:25 2011
From: tim.g.armstrong at gmail.com (Tim Armstrong)
Date: Fri, 1 Apr 2011 10:23:25 -0500
Subject: [Swift-devel] Re: Your message to Swift-commit awaits moderator
approval
In-Reply-To: <1615879940.53640.1301628454283.JavaMail.root@zimbra.anl.gov>
References:
<1615879940.53640.1301628454283.JavaMail.root@zimbra.anl.gov>
Message-ID:
I've also been having the same problem.
On Thu, Mar 31, 2011 at 10:27 PM, Michael Wilde wrote:
> Jon, Im not sure whats happening with these commit notifications.
> you should subscribe to the list, but I marked you as "accept" on this list
> for now.
>
> I cleaned out all the other pending notifications.
>
> We should add instructions for new developers/committers to subscribe to
> this list (in a general info page for new developers)
>
> Whats confusing me here is that I also got a "awaits moderator approval"
> even though Im on the list.
>
> - Mike
>
>
> ----- Original Message -----
> > Just bringing this to your attention.
> >
> >
> > ---------- Forwarded message ----------
> > From: < swift-commit-bounces at ci.uchicago.edu >
> > Date: Thu, Mar 31, 2011 at 10:12 PM
> > Subject: Your message to Swift-commit awaits moderator approval
> > To: jonmon at ci.uchicago.edu
> >
> >
> > Your mail to 'Swift-commit' with the subject
> >
> > r4236 - trunk/bin
> >
> > Is being held until the list moderator can review it for approval.
> >
> > The reason it is being held:
> >
> > Post by non-member to a members-only list
> >
> > Either the message will get posted to the list, or you will receive
> > notification of the moderator's decision. If you would like to cancel
> > this posting, please visit the following URL:
> >
> >
> http://mail.ci.uchicago.edu/mailman/confirm/swift-commit/82735f2236917ed3bfa130c8b93c84dc223123df
> >
> >
> >
> >
> > --
> > Any intelligent fool can make things bigger and more complex... It
> > takes a touch of genius - and a lot of courage to move in the opposite
> > direction.
> > - Albert Einstein
>
> --
> Michael Wilde
> Computation Institute, University of Chicago
> Mathematics and Computer Science Division
> Argonne National Laboratory
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From aespinosa at cs.uchicago.edu Fri Apr 1 10:32:18 2011
From: aespinosa at cs.uchicago.edu (Allan Espinosa)
Date: Fri, 1 Apr 2011 10:32:18 -0500
Subject: [Swift-devel] Request: replies to bugzilla reports on the list
should reflect on the bug page as well
Message-ID:
I don't know how to to this in bugzilla. But in the OSG GOC bug
tracker, my over-email replies to the bug gets reflected on the
ticket page.
-Allan
From wilde at mcs.anl.gov Fri Apr 1 10:51:03 2011
From: wilde at mcs.anl.gov (Michael Wilde)
Date: Fri, 1 Apr 2011 10:51:03 -0500 (CDT)
Subject: [Swift-devel] [Bug 291] New: Add a exists() function to test
for file existence
In-Reply-To:
Message-ID: <1299017498.54908.1301673063970.JavaMail.root@zimbra.anl.gov>
----- Original Message -----
> Try/catch statements don't have a clean intepretation if you're trying
> to follow the flow of data through the program.
I cant comment on this, as its likely a point of programming style that could involve much debate.
On the issue of an exists() function, I feel:
- we should first verify that exists() will solve the NCAR need in a sufficiently clean way
- if so, implement it, because its easy to do
- I do favor an exception handling model in the language, but feel that this is a much more complex PL and systems research project - far more complex just to design not to mention implement than the exists() function.
So even if we would conclude that exceptions and try/catch would be cleaner, we dont have the resources or the driving requirement to do that in any near time frame.
I think it would be a year-long MS-scale project.
- Mike
>
>
> On Fri, Apr 1, 2011 at 5:35 AM, Allan Espinosa <
> aespinosa at cs.uchicago.edu > wrote:
>
>
> Would it be better to handle it as an exception?
>
> type file;
>
> app foo (file x) {
> foo x;
> }
>
> app (file x) produce_a () {
> }
>
> file a <"dne">;
>
> try{
> foo (a);
> }
> catch (dne) {
> a = produce_a();
> foo(a);
> }
>
> 2011/3/31 < bugzilla-daemon at mcs.anl.gov >:
>
>
>
> > https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=291
> >
> > Summary: Add a exists() function to test for file existence
> > Product: Swift
> > Version: 0.93
> > Platform: PC
> > OS/Version: Mac OS
> > Status: NEW
> > Severity: enhancement
> > Priority: P1
> > Component: SwiftScript language
> > AssignedTo: wozniak at mcs.anl.gov
> > ReportedBy: wilde at mcs.anl.gov
> >
> >
> > Requested by John Dennis / NCAR.
> >
> > --
> > Configure bugmail:
> > https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
> > ------- You are receiving this mail because: -------
> > You are watching the reporter.
> > _______________________________________________
> > Swift-devel mailing list
> > Swift-devel at ci.uchicago.edu
> > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> >
> >
>
>
>
> --
> Allan M. Espinosa < http://amespinosa.wordpress.com >
> PhD student, Computer Science
> University of Chicago < http://people.cs.uchicago.edu/~aespinosa >
>
>
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
From hategan at mcs.anl.gov Fri Apr 1 12:32:57 2011
From: hategan at mcs.anl.gov (Mihael Hategan)
Date: Fri, 01 Apr 2011 10:32:57 -0700
Subject: [Swift-devel] [Bug 291] New: Add a exists() function to test
for file existence
In-Reply-To: <1299017498.54908.1301673063970.JavaMail.root@zimbra.anl.gov>
References: <1299017498.54908.1301673063970.JavaMail.root@zimbra.anl.gov>
Message-ID: <1301679177.25559.0.camel@blabla2.none>
On Fri, 2011-04-01 at 10:51 -0500, Michael Wilde wrote:
> - we should first verify that exists() will solve the NCAR need in a sufficiently clean way
I think this is important. Can we get a description of the problem
instead of a (otherwise) random proposal for a solution?
From wilde at mcs.anl.gov Fri Apr 1 12:51:29 2011
From: wilde at mcs.anl.gov (Michael Wilde)
Date: Fri, 1 Apr 2011 12:51:29 -0500 (CDT)
Subject: [Swift-devel] [Bug 291] New: Add a exists() function to test
for file existence
In-Reply-To: <1301679177.25559.0.camel@blabla2.none>
Message-ID: <729744535.55640.1301680289613.JavaMail.root@zimbra.anl.gov>
Basically as far as I understand: the presence or absence of a particular data file within the inout dataset is to be used to determine whether the code to process that dataset subsection gets invoked or not:
if (exists("extra.data")) {
DataFile extraInput<"extra.data">;
extraResult = analyze(extraInput);
}
The above is my assumption based on a phone call. We can and should verify the assumption with a simple example.
I also thought we can try this today by seeing if extraInput can be an array, mapped to zero items if nothing to do and 1 item if something to do. That would at least let us test the use case.
John, can you verify if the example Swift lines above are what you are looking for here?
- Mike
----- Original Message -----
> On Fri, 2011-04-01 at 10:51 -0500, Michael Wilde wrote:
>
> > - we should first verify that exists() will solve the NCAR need in a
> > sufficiently clean way
>
> I think this is important. Can we get a description of the problem
> instead of a (otherwise) random proposal for a solution?
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
From wilde at mcs.anl.gov Fri Apr 1 13:25:02 2011
From: wilde at mcs.anl.gov (Michael Wilde)
Date: Fri, 1 Apr 2011 13:25:02 -0500 (CDT)
Subject: [Swift-devel] [Bug 291] New: Add a exists() function to test
for file existence
In-Reply-To: <2A5A416A-CAB6-4D82-B55F-0CFBC8F3B770@ucar.edu>
Message-ID: <114092944.55753.1301682302213.JavaMail.root@zimbra.anl.gov>
John, I cc'ed you to confirm that the function is exactly what you were looking for, and that the simple code below matches exactly the requirement thats driving this feature request.
Can you confirm that both of these are true?
We just want to make sure that we understand the need and determine if the proposed exists() function is the best way to address it. From your comment below, I was not quite sure if exists() is exactly the right approach here.
Thanks,
Mike
----- Original Message -----
> Michael,
>
> This type of function would be great to have.
>
> John
> On Apr 1, 2011, at 11:51 AM, Michael Wilde wrote:
>
> > Basically as far as I understand: the presence or absence of a
> > particular data file within the inout dataset is to be used to
> > determine whether the code to process that dataset subsection gets
> > invoked or not:
> >
> > if (exists("extra.data")) {
> > DataFile extraInput<"extra.data">;
> > extraResult = analyze(extraInput);
> > }
> >
> > The above is my assumption based on a phone call. We can and should
> > verify the assumption with a simple example.
> >
> > I also thought we can try this today by seeing if extraInput can be
> > an array, mapped to zero items if nothing to do and 1 item if
> > something to do. That would at least let us test the use case.
> >
> > John, can you verify if the example Swift lines above are what you
> > are looking for here?
> >
> > - Mike
> >
> > ----- Original Message -----
> >> On Fri, 2011-04-01 at 10:51 -0500, Michael Wilde wrote:
> >>
> >>> - we should first verify that exists() will solve the NCAR need in
> >>> a
> >>> sufficiently clean way
> >>
> >> I think this is important. Can we get a description of the problem
> >> instead of a (otherwise) random proposal for a solution?
> >
> > --
> > Michael Wilde
> > Computation Institute, University of Chicago
> > Mathematics and Computer Science Division
> > Argonne National Laboratory
> >
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
From bugzilla-daemon at mcs.anl.gov Fri Apr 1 13:25:38 2011
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Fri, 1 Apr 2011 13:25:38 -0500 (CDT)
Subject: [Swift-devel] [Bug 303] fixed_array_mapper versus array_mapper on
output
In-Reply-To:
References:
Message-ID: <20110401182538.E0DED1C072@wind.mcs.anl.gov>
https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=303
Allan Espinosa changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|aespinosa at cs.uchicago.edu |hategan at mcs.anl.gov
--- Comment #2 from Allan Espinosa 2011-04-01 13:25:38 ---
Update on the latest trunk: Swift svn swift-r4208 cog-r3073 (which include's
Mihael's patch to trunk r4089 :
http://mail.ci.uchicago.edu/pipermail/swift-devel/2011-February/007466.html)
fixed_array_mapper version:
type file;
app(file o[])
split(file i){
split "-l" 1 @filename(i) "seqout.";
}
file out[] ;
file input <"seq.in">;
out = split(input);
$swift split.swift
Swift svn swift-r4208 cog-r3073
RunID: 20110401-1319-tsq0pb48
Progress: time:0
No events in 10s.
Registered futures:
----
Waiting threads:
----
No events in 10s.
Registered futures:
----
Waiting threads:
----
Progress: time:30007 Initializing site shared directory:1
No events in 10s.
Registered futures:
----
Waiting threads:
----
...
...
...
looks like fixed_array_mapper doesn't work anymore. out[] should be waiting on
four futures correct?
--
Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
From bugzilla-daemon at mcs.anl.gov Fri Apr 1 13:31:30 2011
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Fri, 1 Apr 2011 13:31:30 -0500 (CDT)
Subject: [Swift-devel] [Bug 303] fixed_array_mapper versus array_mapper on
output
In-Reply-To:
References:
Message-ID: <20110401183130.C60021C072@wind.mcs.anl.gov>
https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=303
Allan Espinosa changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |swift-devel at ci.uchicago.edu
--- Comment #3 from Allan Espinosa 2011-04-01 13:31:30 ---
Latest trunk on array_mapper version:
type file;
app(file o[])
split(file i){
split "-l" 1 @filename(i) "seqout.";
}
string s[] = ["seqout.aa", "seqout.ab", "seqout.ac","seqout.ad"];
file out[] ;
file input <"seq.in">;
out = split(input);
Swift svn swift-r4208 cog-r3073
RunID: 20110401-1328-p44eon1h
Progress: time:1
No events in 10s.
Registered futures:
file[] out Closed, no listeners
----
Waiting threads:
----
No events in 10s.
Registered futures:
file[] out Closed, no listeners
----
Waiting threads:
----
Progress: time:30008 Initializing site shared directory:1
No events in 10s.
Registered futures:
file[] out Closed, no listeners
----
Waiting threads:
I'm not sure now if r4089 fixed the problem or not since later commits like the
merge from the fast branch could have broken things. Also, the app() split()
function should be included in the list of waiting thread when it got the state
of 'initializing shared directory' right?
--
Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are watching the assignee of the bug.
From ketancmaheshwari at gmail.com Fri Apr 1 13:46:03 2011
From: ketancmaheshwari at gmail.com (Ketan Maheshwari)
Date: Fri, 1 Apr 2011 13:46:03 -0500
Subject: [Swift-devel] Swift Documentation Platform
Message-ID: <7CB7BF6B-7DE4-4E93-AF3D-176164F5A65C@gmail.com>
Hi,
While we close in on a decision, I am writing this as an observation to the ongoing discussion about Swift Documentation Platform. And some thoughts in the end.
As of now we have a Main, existing Swift Documentation page:
[1] http://www.ci.uchicago.edu/swift/docs/index.php
In addition, we have pages on CI wiki related to Swift documentations:
[2] http://www.ci.uchicago.edu/wiki/bin/view/SWFT/WebHome
The above link contains many useful but semi-complete/unrounded pages on cookbooks, tutorials and may technical notes.
We have a page on cog wiki dedicated to Coasters:
[3] http://wiki.cogkit.org/wiki/Coasters
The pictures are very neat but slightly outdated and needs update. More pictures would also be required in my opinion to explain several of the relatively new coasters concepts.
We have google sites whose contents overlap with [1] , likely that it is completely redundant to [1]
[4] https://sites.google.com/site/swiftguide/home
A wealth of information about Swift techniques, examples, issues, notes and ideas are living on the following:
[5] https://bugzilla.mcs.anl.gov/swift/
[6] mail.ci.uchicago.edu/pipermail/swift-user
[7] http://mail.ci.uchicago.edu/pipermail/swift-devel/
[8] Mike's Swift Notes (As an attached doc)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Notes.SwiftUsage.doc
Type: application/msword
Size: 212480 bytes
Desc: not available
URL:
-------------- next part --------------
[9] \O/ <--- Mihael's head .............................................. (kidding Mihael)
This really calls for some kind of massive distillation and unification effort. Ideally we want *only* one place where all the information resides that a user wants to know.
Things could be hyperlinked to some extent but it has its own harms. A simple, serial, low-branched documentation would be ideal in my opinion.
I am, at the moment putting some energy into the above and trying to think on structuring my efforts which I am finding a bit overwhelming.
May I have your valuable suggestions on what would be a super master stroke strategy that could gather all these scattered gems into one nice place.
Thanks for reading this long and a bit rantish mail and putting on your ideas.
Cheers,
Ketan
From wozniak at mcs.anl.gov Fri Apr 1 14:06:30 2011
From: wozniak at mcs.anl.gov (Justin M Wozniak)
Date: Fri, 1 Apr 2011 14:06:30 -0500 (CDT)
Subject: [Swift-devel] Swift Documentation Platform
In-Reply-To: <7CB7BF6B-7DE4-4E93-AF3D-176164F5A65C@gmail.com>
References: <7CB7BF6B-7DE4-4E93-AF3D-176164F5A65C@gmail.com>
Message-ID:
Building this list is a good start. Where should we store it?
You could also add the other CoG and Karajan docs.
As of Wednesday we decided we are giving up on Google Sites for user
documentation, but we are going to continue with the swift-devel site for
internal (but publically-readable) notes.
We're thinking of putting at least a month into asciidoc. Once we have
that in place, we should be able to easily paste things into there from
any source.
Justin
On Fri, 1 Apr 2011, Ketan Maheshwari wrote:
> Hi,
>
> While we close in on a decision, I am writing this as an observation to
> the ongoing discussion about Swift Documentation Platform. And some
> thoughts in the end.
>
> As of now we have a Main, existing Swift Documentation page:
>
> [1] http://www.ci.uchicago.edu/swift/docs/index.php
>
> In addition, we have pages on CI wiki related to Swift documentations:
>
>
> [2] http://www.ci.uchicago.edu/wiki/bin/view/SWFT/WebHome
>
> The above link contains many useful but semi-complete/unrounded pages on
> cookbooks, tutorials and may technical notes.
>
>
> We have a page on cog wiki dedicated to Coasters:
>
> [3] http://wiki.cogkit.org/wiki/Coasters
>
> The pictures are very neat but slightly outdated and needs update. More
> pictures would also be required in my opinion to explain several of the
> relatively new coasters concepts.
>
>
> We have google sites whose contents overlap with [1] , likely that it is
> completely redundant to [1]
>
> [4] https://sites.google.com/site/swiftguide/home
>
>
> A wealth of information about Swift techniques, examples, issues, notes
> and ideas are living on the following: [5]
> https://bugzilla.mcs.anl.gov/swift/
>
> [6] mail.ci.uchicago.edu/pipermail/swift-user
>
> [7] http://mail.ci.uchicago.edu/pipermail/swift-devel/
>
> [8] Mike's Swift Notes (As an attached doc)
--
Justin M Wozniak
From bugzilla-daemon at mcs.anl.gov Fri Apr 1 14:13:18 2011
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Fri, 1 Apr 2011 14:13:18 -0500 (CDT)
Subject: [Swift-devel] [Bug 303] fixed_array_mapper versus array_mapper on
output
In-Reply-To:
References:
Message-ID: <20110401191318.DBFD51C072@wind.mcs.anl.gov>
https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=303
Allan Espinosa changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WORKSFORME
--- Comment #4 from Allan Espinosa 2011-04-01 14:13:18 ---
Proposed workaround: ad-hoc join to convert an array of strings to a space
separated string:
$ cat join.swift
type file;
app(file o[])
split(file i){
split "-l" 1 @filename(i) "seqout.";
}
string s[] = ["seqout.aa", "seqout.ab", "seqout.ac","seqout.ad"];
string tomap[];
tomap[-1] = "";
/* ad-hoc join */
foreach si, i in s {
tomap[i] = @strcat(tomap[i-1], si, " ");
}
file out[] ;
file input <"seq.in">;
out = split(input);
swift-r3835 cog-r2988
RunID: 20110401-1411-a88h1ak5
Progress:
Final status: Finished successfully:1
--
Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are watching the assignee of the bug.
From bugzilla-daemon at mcs.anl.gov Fri Apr 1 16:23:44 2011
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Fri, 1 Apr 2011 16:23:44 -0500 (CDT)
Subject: [Swift-devel] [Bug 303] fixed_array_mapper versus array_mapper on
output
In-Reply-To:
References:
Message-ID: <20110401212344.942531C073@wind.mcs.anl.gov>
https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=303
Michael Wilde changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
CC| |wilde at mcs.anl.gov
Resolution|WORKSFORME |
--
Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.
From bugzilla-daemon at mcs.anl.gov Fri Apr 1 16:25:41 2011
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Fri, 1 Apr 2011 16:25:41 -0500 (CDT)
Subject: [Swift-devel] [Bug 303] fixed_array_mapper versus array_mapper on
output
In-Reply-To:
References:
Message-ID: <20110401212541.E3D151C073@wind.mcs.anl.gov>
https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=303
Michael Wilde changed:
What |Removed |Added
----------------------------------------------------------------------------
Platform|PC |All
Version|trunk |0.92
--- Comment #5 from Michael Wilde 2011-04-01 16:25:41 ---
We need to turn each of these examples of array mapping into a test case and
ensure that it works on both trunk and 0.92.
Some of these examples should be added to the user guide.
--
Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.
From wilde at mcs.anl.gov Fri Apr 1 16:49:58 2011
From: wilde at mcs.anl.gov (Michael Wilde)
Date: Fri, 1 Apr 2011 16:49:58 -0500 (CDT)
Subject: [Swift-devel] duplicated job submission in swift-0.92?
In-Reply-To: <1301623475.12764.3.camel@blabla2.none>
Message-ID: <201785481.56903.1301694598367.JavaMail.root@zimbra.anl.gov>
I think we mist-spoke: The posted release 0.92 also exhibits the twice-each bug as far as I acn tell.
Mihael, Justin: can you test asap to confirm or refute that observation?
Thanks,
- Mike
which swift: ~/swift/rev/swift-0.92/bin/swift
com$ swift -version
Swift svn swift-r4157 cog-r3056
com$ cd ~/swift/lab
com$ cat zz3.swift
int arr[];
arr[0]=1;
arr[1]=2;
foreach a in arr {
trace("for", a);
}
com$ swift zz3.swift
Swift svn swift-r4157 cog-r3056
RunID: 20110401-1645-yyy87p39
Progress:
SwiftScript trace: for, 2
SwiftScript trace: for, 1
SwiftScript trace: for, 1
SwiftScript trace: for, 2
Final status:
com$
----- Original Message -----
> I think both are good as they are.
>
> Would you like me to send it?
>
> Mihael
>
> On Thu, 2011-03-31 at 20:57 -0500, Michael Wilde wrote:
> > And I will send this to swift-user:
> >
> > "Dear Swift Users,
> >
> > On March 29 we discovered that the Release 0.92 branches of the
> > Swift and CoG trees were changed after the release and a concurrency
> > bug was introduced. If you are running Swift from this *source code*
> > base, please revert back to a known-working release such as the 0.92
> > binary release if at all possible.
> >
> > We're working on restoring the 0.92 SVN branch to the correct state
> > and will report back to this email list when that is done."
> >
> > Anything else to say? Feel free to send this out, adjusted as
> > needed, or just tell me what to change and I will.
> >
> > - Mike
> >
> >
> > ----- Original Message -----
> > > Please check this proposed warning on the Downloads page and let
> > > me
> > > know if its what we need there:
> > >
> > > http://www.ci.uchicago.edu/~wilde/swift/downloads/index.php
> > >
> > > I also fixed the 0.91 typo (but the downloads dont actually work
> > > from
> > > this test web. I think they will once this is committed and pushed
> > > live).
> > >
> > > - Mike
> > >
> > >
> > > ----- Original Message -----
> > > > ----- Original Message -----
> > > > > On Thu, 2011-03-31 at 20:14 -0500, Michael Wilde wrote:
> > > > > > ----- Original Message -----
> > > > > > > We decided the following:
> > > > > > > - I will revert the changes in the 0.92 branch
> > > > > > > - re-commit bug fixes that were committed after the merge
> > > > > > > - merge the 0.92 branch to trunk
> > > > > > > - fix the problems in trunk
> > > > > >
> > > > > > Sounds good. But when and how does the fix get to users?
> > > > >
> > > > > The package(s) are fine. Though we should probably also have a
> > > > > source
> > > > > package. The merge was done after the package(s) were uploaded
> > > > > to
> > > > > the
> > > > > swift site.
> > > >
> > > > Ah, great!
> > > >
> > > > > This only affects folks who have checked out from SVN the 0.92
> > > > > branch
> > > > > after the merge 9 days (or so) ago.
> > > >
> > > > Hmm - I question that. The release we use, based on 0.92 on
> > > > Beagle,
> > > > shows the twice-each error, and it was made on Feb 25, about 35
> > > > days
> > > > ago. Does this merit clarification?
> > > >
> > > > > We should send an email to the user list once this is fixed.
> > > > > We
> > > > > may
> > > > > also
> > > > > want to send an email warning them not to check out from SVN
> > > > > but
> > > > > download the precompiled package instead.
> > > >
> > > > OK. I cant say that this will reach everyone. Perhaps some
> > > > status
> > > > notes on the Download page are in order. The 0.91 link there is
> > > > wrong,
> > > > so we need to fix that page anyways.
> > > >
> > > > > I am a bit confused though. I would have expected the release
> > > > > to
> > > > > come
> > > > > with some announcement of some form.
> > > >
> > > > Agreed. We kept this low profile because we were trying to
> > > > coordinate
> > > > it with a Web change that we never accomplished. And we've lost
> > > > the
> > > > habit of swift-user announcements but got to get back to doing
> > > > that.
> > > > So, yes.
> > > > >
> > > > > >
> > > > > > Either create a 0.92.1 release (sounds hard based on above)
> > > > > > or create a 0.93 release (in which case should we create the
> > > > > > 0.93
> > > > > > branch from trunk as soon as this is fixed?)
> > > > > >
> > > > > > How long to re-test? (Thats a question for Sarah, Justin,
> > > > > > and
> > > > > > Ketan)
> > > > > > Could this include the Cray support mods?
> > > > >
> > > > > No! Fixing a problem is not a venue for introducing untested
> > > > > things
> > > > > into
> > > > > a release.
> > > >
> > > > I meant the Cray feature for 0.93 not 0.92.1
> > > > Yes, that should be tested.
> > > > But its being used pretty heavily.
> > > >
> > > > - Mike
> > > >
> > > > > But it could be discussed separately :)
> > > > >
> > > > > Mihael
> > > >
> > > > --
> > > > Michael Wilde
> > > > Computation Institute, University of Chicago
> > > > Mathematics and Computer Science Division
> > > > Argonne National Laboratory
> > > >
> > > > _______________________________________________
> > > > Swift-devel mailing list
> > > > Swift-devel at ci.uchicago.edu
> > > > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> > >
> > > --
> > > Michael Wilde
> > > Computation Institute, University of Chicago
> > > Mathematics and Computer Science Division
> > > Argonne National Laboratory
> > >
> > > _______________________________________________
> > > Swift-devel mailing list
> > > Swift-devel at ci.uchicago.edu
> > > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> >
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
From wilde at mcs.anl.gov Fri Apr 1 17:19:17 2011
From: wilde at mcs.anl.gov (Michael Wilde)
Date: Fri, 1 Apr 2011 17:19:17 -0500 (CDT)
Subject: [Swift-devel] duplicated job submission in swift-0.92?
In-Reply-To: <201785481.56903.1301694598367.JavaMail.root@zimbra.anl.gov>
Message-ID: <599442617.57099.1301696357109.JavaMail.root@zimbra.anl.gov>
And Swift 0.91 works OK - it does *not* exhibit the twice-each bug.
Justin: when you went backwards down the Swift 0.92 branch on Thursday morning, what did you find in terms of where it appeared the bug was introduced?
- Mike
----- Original Message -----
> I think we mist-spoke: The posted release 0.92 also exhibits the
> twice-each bug as far as I acn tell.
>
> Mihael, Justin: can you test asap to confirm or refute that
> observation?
>
> Thanks,
>
> - Mike
>
> which swift: ~/swift/rev/swift-0.92/bin/swift
>
> com$ swift -version
> Swift svn swift-r4157 cog-r3056
>
> com$ cd ~/swift/lab
> com$ cat zz3.swift
> int arr[];
>
> arr[0]=1;
> arr[1]=2;
>
> foreach a in arr {
> trace("for", a);
> }
>
> com$ swift zz3.swift
> Swift svn swift-r4157 cog-r3056
>
> RunID: 20110401-1645-yyy87p39
> Progress:
> SwiftScript trace: for, 2
> SwiftScript trace: for, 1
> SwiftScript trace: for, 1
> SwiftScript trace: for, 2
> Final status:
> com$
>
>
> ----- Original Message -----
> > I think both are good as they are.
> >
> > Would you like me to send it?
> >
> > Mihael
> >
> > On Thu, 2011-03-31 at 20:57 -0500, Michael Wilde wrote:
> > > And I will send this to swift-user:
> > >
> > > "Dear Swift Users,
> > >
> > > On March 29 we discovered that the Release 0.92 branches of the
> > > Swift and CoG trees were changed after the release and a
> > > concurrency
> > > bug was introduced. If you are running Swift from this *source
> > > code*
> > > base, please revert back to a known-working release such as the
> > > 0.92
> > > binary release if at all possible.
> > >
> > > We're working on restoring the 0.92 SVN branch to the correct
> > > state
> > > and will report back to this email list when that is done."
> > >
> > > Anything else to say? Feel free to send this out, adjusted as
> > > needed, or just tell me what to change and I will.
> > >
> > > - Mike
> > >
> > >
> > > ----- Original Message -----
> > > > Please check this proposed warning on the Downloads page and let
> > > > me
> > > > know if its what we need there:
> > > >
> > > > http://www.ci.uchicago.edu/~wilde/swift/downloads/index.php
> > > >
> > > > I also fixed the 0.91 typo (but the downloads dont actually work
> > > > from
> > > > this test web. I think they will once this is committed and
> > > > pushed
> > > > live).
> > > >
> > > > - Mike
> > > >
> > > >
> > > > ----- Original Message -----
> > > > > ----- Original Message -----
> > > > > > On Thu, 2011-03-31 at 20:14 -0500, Michael Wilde wrote:
> > > > > > > ----- Original Message -----
> > > > > > > > We decided the following:
> > > > > > > > - I will revert the changes in the 0.92 branch
> > > > > > > > - re-commit bug fixes that were committed after the
> > > > > > > > merge
> > > > > > > > - merge the 0.92 branch to trunk
> > > > > > > > - fix the problems in trunk
> > > > > > >
> > > > > > > Sounds good. But when and how does the fix get to users?
> > > > > >
> > > > > > The package(s) are fine. Though we should probably also have
> > > > > > a
> > > > > > source
> > > > > > package. The merge was done after the package(s) were
> > > > > > uploaded
> > > > > > to
> > > > > > the
> > > > > > swift site.
> > > > >
> > > > > Ah, great!
> > > > >
> > > > > > This only affects folks who have checked out from SVN the
> > > > > > 0.92
> > > > > > branch
> > > > > > after the merge 9 days (or so) ago.
> > > > >
> > > > > Hmm - I question that. The release we use, based on 0.92 on
> > > > > Beagle,
> > > > > shows the twice-each error, and it was made on Feb 25, about
> > > > > 35
> > > > > days
> > > > > ago. Does this merit clarification?
> > > > >
> > > > > > We should send an email to the user list once this is fixed.
> > > > > > We
> > > > > > may
> > > > > > also
> > > > > > want to send an email warning them not to check out from SVN
> > > > > > but
> > > > > > download the precompiled package instead.
> > > > >
> > > > > OK. I cant say that this will reach everyone. Perhaps some
> > > > > status
> > > > > notes on the Download page are in order. The 0.91 link there
> > > > > is
> > > > > wrong,
> > > > > so we need to fix that page anyways.
> > > > >
> > > > > > I am a bit confused though. I would have expected the
> > > > > > release
> > > > > > to
> > > > > > come
> > > > > > with some announcement of some form.
> > > > >
> > > > > Agreed. We kept this low profile because we were trying to
> > > > > coordinate
> > > > > it with a Web change that we never accomplished. And we've
> > > > > lost
> > > > > the
> > > > > habit of swift-user announcements but got to get back to doing
> > > > > that.
> > > > > So, yes.
> > > > > >
> > > > > > >
> > > > > > > Either create a 0.92.1 release (sounds hard based on
> > > > > > > above)
> > > > > > > or create a 0.93 release (in which case should we create
> > > > > > > the
> > > > > > > 0.93
> > > > > > > branch from trunk as soon as this is fixed?)
> > > > > > >
> > > > > > > How long to re-test? (Thats a question for Sarah, Justin,
> > > > > > > and
> > > > > > > Ketan)
> > > > > > > Could this include the Cray support mods?
> > > > > >
> > > > > > No! Fixing a problem is not a venue for introducing untested
> > > > > > things
> > > > > > into
> > > > > > a release.
> > > > >
> > > > > I meant the Cray feature for 0.93 not 0.92.1
> > > > > Yes, that should be tested.
> > > > > But its being used pretty heavily.
> > > > >
> > > > > - Mike
> > > > >
> > > > > > But it could be discussed separately :)
> > > > > >
> > > > > > Mihael
> > > > >
> > > > > --
> > > > > Michael Wilde
> > > > > Computation Institute, University of Chicago
> > > > > Mathematics and Computer Science Division
> > > > > Argonne National Laboratory
> > > > >
> > > > > _______________________________________________
> > > > > Swift-devel mailing list
> > > > > Swift-devel at ci.uchicago.edu
> > > > > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> > > >
> > > > --
> > > > Michael Wilde
> > > > Computation Institute, University of Chicago
> > > > Mathematics and Computer Science Division
> > > > Argonne National Laboratory
> > > >
> > > > _______________________________________________
> > > > Swift-devel mailing list
> > > > Swift-devel at ci.uchicago.edu
> > > > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> > >
>
> --
> Michael Wilde
> Computation Institute, University of Chicago
> Mathematics and Computer Science Division
> Argonne National Laboratory
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
From wozniak at mcs.anl.gov Fri Apr 1 17:33:04 2011
From: wozniak at mcs.anl.gov (Justin M Wozniak)
Date: Fri, 1 Apr 2011 17:33:04 -0500 (Central Daylight Time)
Subject: [Swift-devel] duplicated job submission in swift-0.92?
In-Reply-To: <599442617.57099.1301696357109.JavaMail.root@zimbra.anl.gov>
References: <599442617.57099.1301696357109.JavaMail.root@zimbra.anl.gov>
Message-ID:
I found that it appeared between Swift r3835 and r3837.
On Fri, 1 Apr 2011, Michael Wilde wrote:
> And Swift 0.91 works OK - it does *not* exhibit the twice-each bug.
>
> Justin: when you went backwards down the Swift 0.92 branch on Thursday
> morning, what did you find in terms of where it appeared the bug was
> introduced?
>
> - Mike
>
>
> ----- Original Message -----
>> I think we mist-spoke: The posted release 0.92 also exhibits the
>> twice-each bug as far as I acn tell.
>>
>> Mihael, Justin: can you test asap to confirm or refute that
>> observation?
>>
>> Thanks,
>>
>> - Mike
>>
>> which swift: ~/swift/rev/swift-0.92/bin/swift
>>
>> com$ swift -version
>> Swift svn swift-r4157 cog-r3056
>>
>> com$ cd ~/swift/lab
>> com$ cat zz3.swift
>> int arr[];
>>
>> arr[0]=1;
>> arr[1]=2;
>>
>> foreach a in arr {
>> trace("for", a);
>> }
>>
>> com$ swift zz3.swift
>> Swift svn swift-r4157 cog-r3056
>>
>> RunID: 20110401-1645-yyy87p39
>> Progress:
>> SwiftScript trace: for, 2
>> SwiftScript trace: for, 1
>> SwiftScript trace: for, 1
>> SwiftScript trace: for, 2
>> Final status:
>> com$
>>
>>
>> ----- Original Message -----
>>> I think both are good as they are.
>>>
>>> Would you like me to send it?
>>>
>>> Mihael
>>>
>>> On Thu, 2011-03-31 at 20:57 -0500, Michael Wilde wrote:
>>>> And I will send this to swift-user:
>>>>
>>>> "Dear Swift Users,
>>>>
>>>> On March 29 we discovered that the Release 0.92 branches of the
>>>> Swift and CoG trees were changed after the release and a
>>>> concurrency
>>>> bug was introduced. If you are running Swift from this *source
>>>> code*
>>>> base, please revert back to a known-working release such as the
>>>> 0.92
>>>> binary release if at all possible.
>>>>
>>>> We're working on restoring the 0.92 SVN branch to the correct
>>>> state
>>>> and will report back to this email list when that is done."
>>>>
>>>> Anything else to say? Feel free to send this out, adjusted as
>>>> needed, or just tell me what to change and I will.
>>>>
>>>> - Mike
>>>>
>>>>
>>>> ----- Original Message -----
>>>>> Please check this proposed warning on the Downloads page and let
>>>>> me
>>>>> know if its what we need there:
>>>>>
>>>>> http://www.ci.uchicago.edu/~wilde/swift/downloads/index.php
>>>>>
>>>>> I also fixed the 0.91 typo (but the downloads dont actually work
>>>>> from
>>>>> this test web. I think they will once this is committed and
>>>>> pushed
>>>>> live).
>>>>>
>>>>> - Mike
>>>>>
>>>>>
>>>>> ----- Original Message -----
>>>>>> ----- Original Message -----
>>>>>>> On Thu, 2011-03-31 at 20:14 -0500, Michael Wilde wrote:
>>>>>>>> ----- Original Message -----
>>>>>>>>> We decided the following:
>>>>>>>>> - I will revert the changes in the 0.92 branch
>>>>>>>>> - re-commit bug fixes that were committed after the
>>>>>>>>> merge
>>>>>>>>> - merge the 0.92 branch to trunk
>>>>>>>>> - fix the problems in trunk
>>>>>>>>
>>>>>>>> Sounds good. But when and how does the fix get to users?
>>>>>>>
>>>>>>> The package(s) are fine. Though we should probably also have
>>>>>>> a
>>>>>>> source
>>>>>>> package. The merge was done after the package(s) were
>>>>>>> uploaded
>>>>>>> to
>>>>>>> the
>>>>>>> swift site.
>>>>>>
>>>>>> Ah, great!
>>>>>>
>>>>>>> This only affects folks who have checked out from SVN the
>>>>>>> 0.92
>>>>>>> branch
>>>>>>> after the merge 9 days (or so) ago.
>>>>>>
>>>>>> Hmm - I question that. The release we use, based on 0.92 on
>>>>>> Beagle,
>>>>>> shows the twice-each error, and it was made on Feb 25, about
>>>>>> 35
>>>>>> days
>>>>>> ago. Does this merit clarification?
>>>>>>
>>>>>>> We should send an email to the user list once this is fixed.
>>>>>>> We
>>>>>>> may
>>>>>>> also
>>>>>>> want to send an email warning them not to check out from SVN
>>>>>>> but
>>>>>>> download the precompiled package instead.
>>>>>>
>>>>>> OK. I cant say that this will reach everyone. Perhaps some
>>>>>> status
>>>>>> notes on the Download page are in order. The 0.91 link there
>>>>>> is
>>>>>> wrong,
>>>>>> so we need to fix that page anyways.
>>>>>>
>>>>>>> I am a bit confused though. I would have expected the
>>>>>>> release
>>>>>>> to
>>>>>>> come
>>>>>>> with some announcement of some form.
>>>>>>
>>>>>> Agreed. We kept this low profile because we were trying to
>>>>>> coordinate
>>>>>> it with a Web change that we never accomplished. And we've
>>>>>> lost
>>>>>> the
>>>>>> habit of swift-user announcements but got to get back to doing
>>>>>> that.
>>>>>> So, yes.
>>>>>>>
>>>>>>>>
>>>>>>>> Either create a 0.92.1 release (sounds hard based on
>>>>>>>> above)
>>>>>>>> or create a 0.93 release (in which case should we create
>>>>>>>> the
>>>>>>>> 0.93
>>>>>>>> branch from trunk as soon as this is fixed?)
>>>>>>>>
>>>>>>>> How long to re-test? (Thats a question for Sarah, Justin,
>>>>>>>> and
>>>>>>>> Ketan)
>>>>>>>> Could this include the Cray support mods?
>>>>>>>
>>>>>>> No! Fixing a problem is not a venue for introducing untested
>>>>>>> things
>>>>>>> into
>>>>>>> a release.
>>>>>>
>>>>>> I meant the Cray feature for 0.93 not 0.92.1
>>>>>> Yes, that should be tested.
>>>>>> But its being used pretty heavily.
>>>>>>
>>>>>> - Mike
>>>>>>
>>>>>>> But it could be discussed separately :)
>>>>>>>
>>>>>>> Mihael
>>>>>>
>>>>>> --
>>>>>> Michael Wilde
>>>>>> Computation Institute, University of Chicago
>>>>>> Mathematics and Computer Science Division
>>>>>> Argonne National Laboratory
>>>>>>
>>>>>> _______________________________________________
>>>>>> Swift-devel mailing list
>>>>>> Swift-devel at ci.uchicago.edu
>>>>>> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>>>>>
>>>>> --
>>>>> Michael Wilde
>>>>> Computation Institute, University of Chicago
>>>>> Mathematics and Computer Science Division
>>>>> Argonne National Laboratory
>>>>>
>>>>> _______________________________________________
>>>>> Swift-devel mailing list
>>>>> Swift-devel at ci.uchicago.edu
>>>>> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>>>>
>>
>> --
>> Michael Wilde
>> Computation Institute, University of Chicago
>> Mathematics and Computer Science Division
>> Argonne National Laboratory
>>
>> _______________________________________________
>> Swift-devel mailing list
>> Swift-devel at ci.uchicago.edu
>> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>
>
--
Justin M Wozniak
From wilde at mcs.anl.gov Fri Apr 1 17:50:58 2011
From: wilde at mcs.anl.gov (Michael Wilde)
Date: Fri, 1 Apr 2011 17:50:58 -0500 (CDT)
Subject: [Swift-devel] duplicated job submission in swift-0.92?
In-Reply-To:
Message-ID: <1780706965.57162.1301698258805.JavaMail.root@zimbra.anl.gov>
So I think somehow in your discussions with Mihael yesterday this either got missed or mis-interpreted. These revs were revs *on the way* to 0.92, and were *not* a part of your integration of trunk into the 0.92 branch after the 0.92 release.
I just called Mihael, and he will look at these later this weekend.
- Mike
----- Original Message -----
> I found that it appeared between Swift r3835 and r3837.
>
> On Fri, 1 Apr 2011, Michael Wilde wrote:
>
> > And Swift 0.91 works OK - it does *not* exhibit the twice-each bug.
> >
> > Justin: when you went backwards down the Swift 0.92 branch on
> > Thursday
> > morning, what did you find in terms of where it appeared the bug was
> > introduced?
> >
> > - Mike
> >
> >
> > ----- Original Message -----
> >> I think we mist-spoke: The posted release 0.92 also exhibits the
> >> twice-each bug as far as I acn tell.
> >>
> >> Mihael, Justin: can you test asap to confirm or refute that
> >> observation?
> >>
> >> Thanks,
> >>
> >> - Mike
> >>
> >> which swift: ~/swift/rev/swift-0.92/bin/swift
> >>
> >> com$ swift -version
> >> Swift svn swift-r4157 cog-r3056
> >>
> >> com$ cd ~/swift/lab
> >> com$ cat zz3.swift
> >> int arr[];
> >>
> >> arr[0]=1;
> >> arr[1]=2;
> >>
> >> foreach a in arr {
> >> trace("for", a);
> >> }
> >>
> >> com$ swift zz3.swift
> >> Swift svn swift-r4157 cog-r3056
> >>
> >> RunID: 20110401-1645-yyy87p39
> >> Progress:
> >> SwiftScript trace: for, 2
> >> SwiftScript trace: for, 1
> >> SwiftScript trace: for, 1
> >> SwiftScript trace: for, 2
> >> Final status:
> >> com$
> >>
> >>
> >> ----- Original Message -----
> >>> I think both are good as they are.
> >>>
> >>> Would you like me to send it?
> >>>
> >>> Mihael
> >>>
> >>> On Thu, 2011-03-31 at 20:57 -0500, Michael Wilde wrote:
> >>>> And I will send this to swift-user:
> >>>>
> >>>> "Dear Swift Users,
> >>>>
> >>>> On March 29 we discovered that the Release 0.92 branches of the
> >>>> Swift and CoG trees were changed after the release and a
> >>>> concurrency
> >>>> bug was introduced. If you are running Swift from this *source
> >>>> code*
> >>>> base, please revert back to a known-working release such as the
> >>>> 0.92
> >>>> binary release if at all possible.
> >>>>
> >>>> We're working on restoring the 0.92 SVN branch to the correct
> >>>> state
> >>>> and will report back to this email list when that is done."
> >>>>
> >>>> Anything else to say? Feel free to send this out, adjusted as
> >>>> needed, or just tell me what to change and I will.
> >>>>
> >>>> - Mike
> >>>>
> >>>>
> >>>> ----- Original Message -----
> >>>>> Please check this proposed warning on the Downloads page and let
> >>>>> me
> >>>>> know if its what we need there:
> >>>>>
> >>>>> http://www.ci.uchicago.edu/~wilde/swift/downloads/index.php
> >>>>>
> >>>>> I also fixed the 0.91 typo (but the downloads dont actually work
> >>>>> from
> >>>>> this test web. I think they will once this is committed and
> >>>>> pushed
> >>>>> live).
> >>>>>
> >>>>> - Mike
> >>>>>
> >>>>>
> >>>>> ----- Original Message -----
> >>>>>> ----- Original Message -----
> >>>>>>> On Thu, 2011-03-31 at 20:14 -0500, Michael Wilde wrote:
> >>>>>>>> ----- Original Message -----
> >>>>>>>>> We decided the following:
> >>>>>>>>> - I will revert the changes in the 0.92 branch
> >>>>>>>>> - re-commit bug fixes that were committed after the
> >>>>>>>>> merge
> >>>>>>>>> - merge the 0.92 branch to trunk
> >>>>>>>>> - fix the problems in trunk
> >>>>>>>>
> >>>>>>>> Sounds good. But when and how does the fix get to users?
> >>>>>>>
> >>>>>>> The package(s) are fine. Though we should probably also have
> >>>>>>> a
> >>>>>>> source
> >>>>>>> package. The merge was done after the package(s) were
> >>>>>>> uploaded
> >>>>>>> to
> >>>>>>> the
> >>>>>>> swift site.
> >>>>>>
> >>>>>> Ah, great!
> >>>>>>
> >>>>>>> This only affects folks who have checked out from SVN the
> >>>>>>> 0.92
> >>>>>>> branch
> >>>>>>> after the merge 9 days (or so) ago.
> >>>>>>
> >>>>>> Hmm - I question that. The release we use, based on 0.92 on
> >>>>>> Beagle,
> >>>>>> shows the twice-each error, and it was made on Feb 25, about
> >>>>>> 35
> >>>>>> days
> >>>>>> ago. Does this merit clarification?
> >>>>>>
> >>>>>>> We should send an email to the user list once this is fixed.
> >>>>>>> We
> >>>>>>> may
> >>>>>>> also
> >>>>>>> want to send an email warning them not to check out from SVN
> >>>>>>> but
> >>>>>>> download the precompiled package instead.
> >>>>>>
> >>>>>> OK. I cant say that this will reach everyone. Perhaps some
> >>>>>> status
> >>>>>> notes on the Download page are in order. The 0.91 link there
> >>>>>> is
> >>>>>> wrong,
> >>>>>> so we need to fix that page anyways.
> >>>>>>
> >>>>>>> I am a bit confused though. I would have expected the
> >>>>>>> release
> >>>>>>> to
> >>>>>>> come
> >>>>>>> with some announcement of some form.
> >>>>>>
> >>>>>> Agreed. We kept this low profile because we were trying to
> >>>>>> coordinate
> >>>>>> it with a Web change that we never accomplished. And we've
> >>>>>> lost
> >>>>>> the
> >>>>>> habit of swift-user announcements but got to get back to doing
> >>>>>> that.
> >>>>>> So, yes.
> >>>>>>>
> >>>>>>>>
> >>>>>>>> Either create a 0.92.1 release (sounds hard based on
> >>>>>>>> above)
> >>>>>>>> or create a 0.93 release (in which case should we create
> >>>>>>>> the
> >>>>>>>> 0.93
> >>>>>>>> branch from trunk as soon as this is fixed?)
> >>>>>>>>
> >>>>>>>> How long to re-test? (Thats a question for Sarah, Justin,
> >>>>>>>> and
> >>>>>>>> Ketan)
> >>>>>>>> Could this include the Cray support mods?
> >>>>>>>
> >>>>>>> No! Fixing a problem is not a venue for introducing untested
> >>>>>>> things
> >>>>>>> into
> >>>>>>> a release.
> >>>>>>
> >>>>>> I meant the Cray feature for 0.93 not 0.92.1
> >>>>>> Yes, that should be tested.
> >>>>>> But its being used pretty heavily.
> >>>>>>
> >>>>>> - Mike
> >>>>>>
> >>>>>>> But it could be discussed separately :)
> >>>>>>>
> >>>>>>> Mihael
> >>>>>>
> >>>>>> --
> >>>>>> Michael Wilde
> >>>>>> Computation Institute, University of Chicago
> >>>>>> Mathematics and Computer Science Division
> >>>>>> Argonne National Laboratory
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> Swift-devel mailing list
> >>>>>> Swift-devel at ci.uchicago.edu
> >>>>>> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> >>>>>
> >>>>> --
> >>>>> Michael Wilde
> >>>>> Computation Institute, University of Chicago
> >>>>> Mathematics and Computer Science Division
> >>>>> Argonne National Laboratory
> >>>>>
> >>>>> _______________________________________________
> >>>>> Swift-devel mailing list
> >>>>> Swift-devel at ci.uchicago.edu
> >>>>> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> >>>>
> >>
> >> --
> >> Michael Wilde
> >> Computation Institute, University of Chicago
> >> Mathematics and Computer Science Division
> >> Argonne National Laboratory
> >>
> >> _______________________________________________
> >> Swift-devel mailing list
> >> Swift-devel at ci.uchicago.edu
> >> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> >
> >
>
> --
> Justin M Wozniak
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
From hategan at mcs.anl.gov Fri Apr 1 21:37:15 2011
From: hategan at mcs.anl.gov (Mihael Hategan)
Date: Fri, 01 Apr 2011 19:37:15 -0700
Subject: [Swift-devel] duplicated job submission in swift-0.92?
In-Reply-To:
References: <599442617.57099.1301696357109.JavaMail.root@zimbra.anl.gov>
Message-ID: <1301711835.7410.1.camel@blabla2.none>
That's possible, looking at the code.
Though what makes you think it's that?
Mihael
On Fri, 2011-04-01 at 17:33 -0500, Justin M Wozniak wrote:
> I found that it appeared between Swift r3835 and r3837.
>
> On Fri, 1 Apr 2011, Michael Wilde wrote:
>
> > And Swift 0.91 works OK - it does *not* exhibit the twice-each bug.
> >
> > Justin: when you went backwards down the Swift 0.92 branch on Thursday
> > morning, what did you find in terms of where it appeared the bug was
> > introduced?
> >
> > - Mike
> >
> >
> > ----- Original Message -----
> >> I think we mist-spoke: The posted release 0.92 also exhibits the
> >> twice-each bug as far as I acn tell.
> >>
> >> Mihael, Justin: can you test asap to confirm or refute that
> >> observation?
> >>
> >> Thanks,
> >>
> >> - Mike
> >>
> >> which swift: ~/swift/rev/swift-0.92/bin/swift
> >>
> >> com$ swift -version
> >> Swift svn swift-r4157 cog-r3056
> >>
> >> com$ cd ~/swift/lab
> >> com$ cat zz3.swift
> >> int arr[];
> >>
> >> arr[0]=1;
> >> arr[1]=2;
> >>
> >> foreach a in arr {
> >> trace("for", a);
> >> }
> >>
> >> com$ swift zz3.swift
> >> Swift svn swift-r4157 cog-r3056
> >>
> >> RunID: 20110401-1645-yyy87p39
> >> Progress:
> >> SwiftScript trace: for, 2
> >> SwiftScript trace: for, 1
> >> SwiftScript trace: for, 1
> >> SwiftScript trace: for, 2
> >> Final status:
> >> com$
> >>
> >>
> >> ----- Original Message -----
> >>> I think both are good as they are.
> >>>
> >>> Would you like me to send it?
> >>>
> >>> Mihael
> >>>
> >>> On Thu, 2011-03-31 at 20:57 -0500, Michael Wilde wrote:
> >>>> And I will send this to swift-user:
> >>>>
> >>>> "Dear Swift Users,
> >>>>
> >>>> On March 29 we discovered that the Release 0.92 branches of the
> >>>> Swift and CoG trees were changed after the release and a
> >>>> concurrency
> >>>> bug was introduced. If you are running Swift from this *source
> >>>> code*
> >>>> base, please revert back to a known-working release such as the
> >>>> 0.92
> >>>> binary release if at all possible.
> >>>>
> >>>> We're working on restoring the 0.92 SVN branch to the correct
> >>>> state
> >>>> and will report back to this email list when that is done."
> >>>>
> >>>> Anything else to say? Feel free to send this out, adjusted as
> >>>> needed, or just tell me what to change and I will.
> >>>>
> >>>> - Mike
> >>>>
> >>>>
> >>>> ----- Original Message -----
> >>>>> Please check this proposed warning on the Downloads page and let
> >>>>> me
> >>>>> know if its what we need there:
> >>>>>
> >>>>> http://www.ci.uchicago.edu/~wilde/swift/downloads/index.php
> >>>>>
> >>>>> I also fixed the 0.91 typo (but the downloads dont actually work
> >>>>> from
> >>>>> this test web. I think they will once this is committed and
> >>>>> pushed
> >>>>> live).
> >>>>>
> >>>>> - Mike
> >>>>>
> >>>>>
> >>>>> ----- Original Message -----
> >>>>>> ----- Original Message -----
> >>>>>>> On Thu, 2011-03-31 at 20:14 -0500, Michael Wilde wrote:
> >>>>>>>> ----- Original Message -----
> >>>>>>>>> We decided the following:
> >>>>>>>>> - I will revert the changes in the 0.92 branch
> >>>>>>>>> - re-commit bug fixes that were committed after the
> >>>>>>>>> merge
> >>>>>>>>> - merge the 0.92 branch to trunk
> >>>>>>>>> - fix the problems in trunk
> >>>>>>>>
> >>>>>>>> Sounds good. But when and how does the fix get to users?
> >>>>>>>
> >>>>>>> The package(s) are fine. Though we should probably also have
> >>>>>>> a
> >>>>>>> source
> >>>>>>> package. The merge was done after the package(s) were
> >>>>>>> uploaded
> >>>>>>> to
> >>>>>>> the
> >>>>>>> swift site.
> >>>>>>
> >>>>>> Ah, great!
> >>>>>>
> >>>>>>> This only affects folks who have checked out from SVN the
> >>>>>>> 0.92
> >>>>>>> branch
> >>>>>>> after the merge 9 days (or so) ago.
> >>>>>>
> >>>>>> Hmm - I question that. The release we use, based on 0.92 on
> >>>>>> Beagle,
> >>>>>> shows the twice-each error, and it was made on Feb 25, about
> >>>>>> 35
> >>>>>> days
> >>>>>> ago. Does this merit clarification?
> >>>>>>
> >>>>>>> We should send an email to the user list once this is fixed.
> >>>>>>> We
> >>>>>>> may
> >>>>>>> also
> >>>>>>> want to send an email warning them not to check out from SVN
> >>>>>>> but
> >>>>>>> download the precompiled package instead.
> >>>>>>
> >>>>>> OK. I cant say that this will reach everyone. Perhaps some
> >>>>>> status
> >>>>>> notes on the Download page are in order. The 0.91 link there
> >>>>>> is
> >>>>>> wrong,
> >>>>>> so we need to fix that page anyways.
> >>>>>>
> >>>>>>> I am a bit confused though. I would have expected the
> >>>>>>> release
> >>>>>>> to
> >>>>>>> come
> >>>>>>> with some announcement of some form.
> >>>>>>
> >>>>>> Agreed. We kept this low profile because we were trying to
> >>>>>> coordinate
> >>>>>> it with a Web change that we never accomplished. And we've
> >>>>>> lost
> >>>>>> the
> >>>>>> habit of swift-user announcements but got to get back to doing
> >>>>>> that.
> >>>>>> So, yes.
> >>>>>>>
> >>>>>>>>
> >>>>>>>> Either create a 0.92.1 release (sounds hard based on
> >>>>>>>> above)
> >>>>>>>> or create a 0.93 release (in which case should we create
> >>>>>>>> the
> >>>>>>>> 0.93
> >>>>>>>> branch from trunk as soon as this is fixed?)
> >>>>>>>>
> >>>>>>>> How long to re-test? (Thats a question for Sarah, Justin,
> >>>>>>>> and
> >>>>>>>> Ketan)
> >>>>>>>> Could this include the Cray support mods?
> >>>>>>>
> >>>>>>> No! Fixing a problem is not a venue for introducing untested
> >>>>>>> things
> >>>>>>> into
> >>>>>>> a release.
> >>>>>>
> >>>>>> I meant the Cray feature for 0.93 not 0.92.1
> >>>>>> Yes, that should be tested.
> >>>>>> But its being used pretty heavily.
> >>>>>>
> >>>>>> - Mike
> >>>>>>
> >>>>>>> But it could be discussed separately :)
> >>>>>>>
> >>>>>>> Mihael
> >>>>>>
> >>>>>> --
> >>>>>> Michael Wilde
> >>>>>> Computation Institute, University of Chicago
> >>>>>> Mathematics and Computer Science Division
> >>>>>> Argonne National Laboratory
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> Swift-devel mailing list
> >>>>>> Swift-devel at ci.uchicago.edu
> >>>>>> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> >>>>>
> >>>>> --
> >>>>> Michael Wilde
> >>>>> Computation Institute, University of Chicago
> >>>>> Mathematics and Computer Science Division
> >>>>> Argonne National Laboratory
> >>>>>
> >>>>> _______________________________________________
> >>>>> Swift-devel mailing list
> >>>>> Swift-devel at ci.uchicago.edu
> >>>>> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> >>>>
> >>
> >> --
> >> Michael Wilde
> >> Computation Institute, University of Chicago
> >> Mathematics and Computer Science Division
> >> Argonne National Laboratory
> >>
> >> _______________________________________________
> >> Swift-devel mailing list
> >> Swift-devel at ci.uchicago.edu
> >> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> >
> >
>
From benc at hawaga.org.uk Fri Apr 1 23:34:02 2011
From: benc at hawaga.org.uk (Ben Clifford)
Date: Sat, 2 Apr 2011 04:34:02 +0000 (GMT)
Subject: [Swift-devel] saturday morning rambling about exceptions
In-Reply-To:
References:
Message-ID:
> Try/catch statements don't have a clean intepretation if you're trying to
> follow the flow of data through the program.
Right.
I thought about this a bit before but it started getting all haskelly and
something i didn't want to approach - as mike says its much more
researchy.
The main idea which I found most comfortable was Haskell's Either type.
That can model something like exceptions but is more amenable to a
dataflow style of programming.
(although C implements something very restricted similar in the form of
pointers which can be NULL, or when returning a return code that is in
some range of values for an error and some other range of values for
success)
The way the haskell Either type works is that something which might "throw
an exception" returns a value that is either an error object or a correct
value object.
So then you use an if or a case or anything else that can change behaviour
based on data to change your flow.
Imagine in C:
p = malloc(5);
if(p == NULL) {
/* catch-exception, but dataflow style - we don't have to look at p
right after the malloc. We can store it into a structure and
come back to it later to check.
unfortuantely, there is not enough space in p to represent
any richer kind of exception information other than "FAIL" */
} else {
{
/* no exception, and we have the correct value in p */
}
In haskell, that looks like:
p = somefunc
case p of
Right d -> doSomethingWith d -- somefunc succeeded and returned
-- us value d
Left ex -> handleError ex -- somefunc failed and returned
-- value ex as the equivalnet of a
-- Java Exception object.
Now it gets a bit awkward having to unwrap "Right d" after every such
function call, and in that respect I think a syntax that looks more like
try-catch is much easier to program with. However I think the right way to
go is to define its semantics in terms of "dataflow" style exceptions
above rather than control-flow.
I think that's possible and would result in something that satisfies both
the dataflow-purist camp and the "I like exception syntax" camp (both
camps of which I'm in ;)
--
From benc at hawaga.org.uk Fri Apr 1 23:36:32 2011
From: benc at hawaga.org.uk (Ben Clifford)
Date: Sat, 2 Apr 2011 04:36:32 +0000 (GMT)
Subject: [Swift-devel] [Bug 291] New: Add a exists() function to test
for file existence
In-Reply-To: <729744535.55640.1301680289613.JavaMail.root@zimbra.anl.gov>
References: <729744535.55640.1301680289613.JavaMail.root@zimbra.anl.gov>
Message-ID:
> Basically as far as I understand: the presence or absence of a
> particular data file within the inout dataset is to be used to determine
> whether the code to process that dataset subsection gets invoked or not:
>
> if (exists("extra.data")) {
> DataFile extraInput<"extra.data">;
> extraResult = analyze(extraInput);
> }
Somehow this feels to me like you should be able to say something liek:
DataFile extraInput<"extra.data">;
extraResult =? analyze(extraInput);
and have extra.data either kept from before or repopulated.
Or even have the swift runtime see that extraInput exists already and
always skip the statement to create it, without anything else expressed in
the code.
--
From hategan at mcs.anl.gov Sat Apr 2 03:33:52 2011
From: hategan at mcs.anl.gov (Mihael Hategan)
Date: Sat, 02 Apr 2011 01:33:52 -0700
Subject: [Swift-devel] [Bug 291] New: Add a exists() function to test
for file existence
In-Reply-To:
References: <729744535.55640.1301680289613.JavaMail.root@zimbra.anl.gov>
Message-ID: <1301733232.18577.3.camel@blabla2.none>
On Sat, 2011-04-02 at 04:36 +0000, Ben Clifford wrote:
> > Basically as far as I understand: the presence or absence of a
> > particular data file within the inout dataset is to be used to determine
> > whether the code to process that dataset subsection gets invoked or not:
>
> >
> > if (exists("extra.data")) {
> > DataFile extraInput<"extra.data">;
> > extraResult = analyze(extraInput);
> > }
>
> Somehow this feels to me like you should be able to say something liek:
>
> DataFile extraInput<"extra.data">;
> extraResult =? analyze(extraInput);
Right. Or if you didn't want to be cryptic:
DataFile optional extraInput<"extra.data">;
...
And I am emphasizing here that the optional attribute should belong to
the data. You probably don't want to have it optional with one
invocation and non optional with another. Given that the successful
completion of a run requires that all invocations complete successfully,
anything else would be silly.
From benc at hawaga.org.uk Sat Apr 2 04:00:16 2011
From: benc at hawaga.org.uk (Ben Clifford)
Date: Sat, 2 Apr 2011 09:00:16 +0000 (GMT)
Subject: [Swift-devel] [Bug 291] New: Add a exists() function to test
for file existence
In-Reply-To: <1301733232.18577.3.camel@blabla2.none>
References: <729744535.55640.1301680289613.JavaMail.root@zimbra.anl.gov>
<1301733232.18577.3.camel@blabla2.none>
Message-ID:
> And I am emphasizing here that the optional attribute should belong to
> the data. You probably don't want to have it optional with one
> invocation and non optional with another. Given that the successful
> completion of a run requires that all invocations complete successfully,
> anything else would be silly.
maybe "optional" is not the right word. its data that needs to exist. but
you are specifying two ways for it to exist in the scope of the current
run: either you find it on a filesystem, or you run some program that
outputs it. but I agree that whatever it is called, its attached to the
data not to an invocation. it sounds a lot like the virtual data idea.
--
From dennis at ucar.edu Fri Apr 1 13:30:38 2011
From: dennis at ucar.edu (John Dennis)
Date: Fri, 1 Apr 2011 12:30:38 -0600
Subject: [Swift-devel] [Bug 291] New: Add a exists() function to test
for file existence
In-Reply-To: <114092944.55753.1301682302213.JavaMail.root@zimbra.anl.gov>
References: <114092944.55753.1301682302213.JavaMail.root@zimbra.anl.gov>
Message-ID:
On Apr 1, 2011, at 12:25 PM, Michael Wilde wrote:
> John, I cc'ed you to confirm that the function is exactly what you
> were looking for, and that the simple code below matches exactly the
> requirement thats driving this feature request.
>
> Can you confirm that both of these are true?
Michael,
So assuming that there is a logical negation operator in Swift the
function you describe matches my requirements.
Thanks,
John
> We just want to make sure that we understand the need and determine
> if the proposed exists() function is the best way to address it.
> From your comment below, I was not quite sure if exists() is exactly
> the right approach here.
>
> Thanks,
>
> Mike
>
>
> ----- Original Message -----
>> Michael,
>>
>> This type of function would be great to have.
>>
>> John
>> On Apr 1, 2011, at 11:51 AM, Michael Wilde wrote:
>>
>>> Basically as far as I understand: the presence or absence of a
>>> particular data file within the inout dataset is to be used to
>>> determine whether the code to process that dataset subsection gets
>>> invoked or not:
>>>
>>> if (exists("extra.data")) {
>>> DataFile extraInput<"extra.data">;
>>> extraResult = analyze(extraInput);
>>> }
>>>
>>> The above is my assumption based on a phone call. We can and should
>>> verify the assumption with a simple example.
>>>
>>> I also thought we can try this today by seeing if extraInput can be
>>> an array, mapped to zero items if nothing to do and 1 item if
>>> something to do. That would at least let us test the use case.
>>>
>>> John, can you verify if the example Swift lines above are what you
>>> are looking for here?
>>>
>>> - Mike
>>>
>>> ----- Original Message -----
>>>> On Fri, 2011-04-01 at 10:51 -0500, Michael Wilde wrote:
>>>>
>>>>> - we should first verify that exists() will solve the NCAR need in
>>>>> a
>>>>> sufficiently clean way
>>>>
>>>> I think this is important. Can we get a description of the problem
>>>> instead of a (otherwise) random proposal for a solution?
>>>
>>> --
>>> Michael Wilde
>>> Computation Institute, University of Chicago
>>> Mathematics and Computer Science Division
>>> Argonne National Laboratory
>>>
>
> --
> Michael Wilde
> Computation Institute, University of Chicago
> Mathematics and Computer Science Division
> Argonne National Laboratory
>
From dennis at ucar.edu Fri Apr 1 13:04:07 2011
From: dennis at ucar.edu (John Dennis)
Date: Fri, 1 Apr 2011 12:04:07 -0600
Subject: [Swift-devel] [Bug 291] New: Add a exists() function to test
for file existence
In-Reply-To: <729744535.55640.1301680289613.JavaMail.root@zimbra.anl.gov>
References: <729744535.55640.1301680289613.JavaMail.root@zimbra.anl.gov>
Message-ID: <2A5A416A-CAB6-4D82-B55F-0CFBC8F3B770@ucar.edu>
Michael,
This type of function would be great to have.
John
On Apr 1, 2011, at 11:51 AM, Michael Wilde wrote:
> Basically as far as I understand: the presence or absence of a
> particular data file within the inout dataset is to be used to
> determine whether the code to process that dataset subsection gets
> invoked or not:
>
> if (exists("extra.data")) {
> DataFile extraInput<"extra.data">;
> extraResult = analyze(extraInput);
> }
>
> The above is my assumption based on a phone call. We can and should
> verify the assumption with a simple example.
>
> I also thought we can try this today by seeing if extraInput can be
> an array, mapped to zero items if nothing to do and 1 item if
> something to do. That would at least let us test the use case.
>
> John, can you verify if the example Swift lines above are what you
> are looking for here?
>
> - Mike
>
> ----- Original Message -----
>> On Fri, 2011-04-01 at 10:51 -0500, Michael Wilde wrote:
>>
>>> - we should first verify that exists() will solve the NCAR need in a
>>> sufficiently clean way
>>
>> I think this is important. Can we get a description of the problem
>> instead of a (otherwise) random proposal for a solution?
>
> --
> Michael Wilde
> Computation Institute, University of Chicago
> Mathematics and Computer Science Division
> Argonne National Laboratory
>
From ketan at mcs.anl.gov Fri Apr 1 17:03:42 2011
From: ketan at mcs.anl.gov (Ketan Maheshwari)
Date: Fri, 1 Apr 2011 17:03:42 -0500
Subject: [Swift-devel] Coasters Configuration Optimizations
Message-ID: <05C21979-33F0-4DCD-A99B-DCE5771FE26C@mcs.anl.gov>
Hello,
Today, I successfully ran an experiment with 5000 tasks on beagle with Coasters. These modFTdock tasks correspond to the production grade modFTdock parameters and each task takes around 20 minutes to complete.
After some discussions with Mike, I configured my sites.xml file to obtain necessary resources on beagle.
However, it seems that I did not configure my sites.xml optimally as the resources requested exceeded my requirements.
In summary 13 blocks for 24 hours and 4 blocks for 22 hours (120 nodes) were requested while the needed were at most 4 hours on each block or more on less number of blocks.
Attached are the following:
sites.xml
tc.data
A qstat snapshot at the completion of the experiment.
Suggestions and insights on how to optimize the configuration are welcome.
Regards,
Ketan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sites.xml
Type: application/xml
Size: 1653 bytes
Desc: not available
URL:
-------------- next part --------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tc.data
Type: application/octet-stream
Size: 239 bytes
Desc: not available
URL:
-------------- next part --------------
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: qstat.snapshotatjob4955.txt
URL:
-------------- next part --------------
From wilde at mcs.anl.gov Sat Apr 2 08:16:43 2011
From: wilde at mcs.anl.gov (Michael Wilde)
Date: Sat, 2 Apr 2011 08:16:43 -0500 (CDT)
Subject: [Swift-devel] duplicated job submission in swift-0.92?
In-Reply-To: <1301711835.7410.1.camel@blabla2.none>
Message-ID: <162077988.57719.1301750203568.JavaMail.root@zimbra.anl.gov>
Mihael,
My understanding is that Justin used a binary search approach: he kept extracting a point-in-time snapshot from SVN, and built and tested it, selecting dates in binary-search mode until he narrowed down the revision range that caused the failure to between r3835 and r3837.
Justin can confirm this when he sees this message, but don't count on confirmation very soon this weekend. Best to do you own tests to verify (or I can if that would help).
- Mike
----- Original Message -----
> That's possible, looking at the code.
>
> Though what makes you think it's that?
>
> Mihael
>
> On Fri, 2011-04-01 at 17:33 -0500, Justin M Wozniak wrote:
> > I found that it appeared between Swift r3835 and r3837.
> >
> > On Fri, 1 Apr 2011, Michael Wilde wrote:
> >
> > > And Swift 0.91 works OK - it does *not* exhibit the twice-each
> > > bug.
> > >
> > > Justin: when you went backwards down the Swift 0.92 branch on
> > > Thursday
> > > morning, what did you find in terms of where it appeared the bug
> > > was
> > > introduced?
> > >
> > > - Mike
> > >
> > >
> > > ----- Original Message -----
> > >> I think we mist-spoke: The posted release 0.92 also exhibits the
> > >> twice-each bug as far as I acn tell.
> > >>
> > >> Mihael, Justin: can you test asap to confirm or refute that
> > >> observation?
> > >>
> > >> Thanks,
> > >>
> > >> - Mike
> > >>
> > >> which swift: ~/swift/rev/swift-0.92/bin/swift
> > >>
> > >> com$ swift -version
> > >> Swift svn swift-r4157 cog-r3056
> > >>
> > >> com$ cd ~/swift/lab
> > >> com$ cat zz3.swift
> > >> int arr[];
> > >>
> > >> arr[0]=1;
> > >> arr[1]=2;
> > >>
> > >> foreach a in arr {
> > >> trace("for", a);
> > >> }
> > >>
> > >> com$ swift zz3.swift
> > >> Swift svn swift-r4157 cog-r3056
> > >>
> > >> RunID: 20110401-1645-yyy87p39
> > >> Progress:
> > >> SwiftScript trace: for, 2
> > >> SwiftScript trace: for, 1
> > >> SwiftScript trace: for, 1
> > >> SwiftScript trace: for, 2
> > >> Final status:
> > >> com$
> > >>
> > >>
> > >> ----- Original Message -----
> > >>> I think both are good as they are.
> > >>>
> > >>> Would you like me to send it?
> > >>>
> > >>> Mihael
> > >>>
> > >>> On Thu, 2011-03-31 at 20:57 -0500, Michael Wilde wrote:
> > >>>> And I will send this to swift-user:
> > >>>>
> > >>>> "Dear Swift Users,
> > >>>>
> > >>>> On March 29 we discovered that the Release 0.92 branches of the
> > >>>> Swift and CoG trees were changed after the release and a
> > >>>> concurrency
> > >>>> bug was introduced. If you are running Swift from this *source
> > >>>> code*
> > >>>> base, please revert back to a known-working release such as the
> > >>>> 0.92
> > >>>> binary release if at all possible.
> > >>>>
> > >>>> We're working on restoring the 0.92 SVN branch to the correct
> > >>>> state
> > >>>> and will report back to this email list when that is done."
> > >>>>
> > >>>> Anything else to say? Feel free to send this out, adjusted as
> > >>>> needed, or just tell me what to change and I will.
> > >>>>
> > >>>> - Mike
> > >>>>
> > >>>>
> > >>>> ----- Original Message -----
> > >>>>> Please check this proposed warning on the Downloads page and
> > >>>>> let
> > >>>>> me
> > >>>>> know if its what we need there:
> > >>>>>
> > >>>>> http://www.ci.uchicago.edu/~wilde/swift/downloads/index.php
> > >>>>>
> > >>>>> I also fixed the 0.91 typo (but the downloads dont actually
> > >>>>> work
> > >>>>> from
> > >>>>> this test web. I think they will once this is committed and
> > >>>>> pushed
> > >>>>> live).
> > >>>>>
> > >>>>> - Mike
> > >>>>>
> > >>>>>
> > >>>>> ----- Original Message -----
> > >>>>>> ----- Original Message -----
> > >>>>>>> On Thu, 2011-03-31 at 20:14 -0500, Michael Wilde wrote:
> > >>>>>>>> ----- Original Message -----
> > >>>>>>>>> We decided the following:
> > >>>>>>>>> - I will revert the changes in the 0.92 branch
> > >>>>>>>>> - re-commit bug fixes that were committed after the
> > >>>>>>>>> merge
> > >>>>>>>>> - merge the 0.92 branch to trunk
> > >>>>>>>>> - fix the problems in trunk
> > >>>>>>>>
> > >>>>>>>> Sounds good. But when and how does the fix get to users?
> > >>>>>>>
> > >>>>>>> The package(s) are fine. Though we should probably also have
> > >>>>>>> a
> > >>>>>>> source
> > >>>>>>> package. The merge was done after the package(s) were
> > >>>>>>> uploaded
> > >>>>>>> to
> > >>>>>>> the
> > >>>>>>> swift site.
> > >>>>>>
> > >>>>>> Ah, great!
> > >>>>>>
> > >>>>>>> This only affects folks who have checked out from SVN the
> > >>>>>>> 0.92
> > >>>>>>> branch
> > >>>>>>> after the merge 9 days (or so) ago.
> > >>>>>>
> > >>>>>> Hmm - I question that. The release we use, based on 0.92 on
> > >>>>>> Beagle,
> > >>>>>> shows the twice-each error, and it was made on Feb 25, about
> > >>>>>> 35
> > >>>>>> days
> > >>>>>> ago. Does this merit clarification?
> > >>>>>>
> > >>>>>>> We should send an email to the user list once this is fixed.
> > >>>>>>> We
> > >>>>>>> may
> > >>>>>>> also
> > >>>>>>> want to send an email warning them not to check out from SVN
> > >>>>>>> but
> > >>>>>>> download the precompiled package instead.
> > >>>>>>
> > >>>>>> OK. I cant say that this will reach everyone. Perhaps some
> > >>>>>> status
> > >>>>>> notes on the Download page are in order. The 0.91 link there
> > >>>>>> is
> > >>>>>> wrong,
> > >>>>>> so we need to fix that page anyways.
> > >>>>>>
> > >>>>>>> I am a bit confused though. I would have expected the
> > >>>>>>> release
> > >>>>>>> to
> > >>>>>>> come
> > >>>>>>> with some announcement of some form.
> > >>>>>>
> > >>>>>> Agreed. We kept this low profile because we were trying to
> > >>>>>> coordinate
> > >>>>>> it with a Web change that we never accomplished. And we've
> > >>>>>> lost
> > >>>>>> the
> > >>>>>> habit of swift-user announcements but got to get back to
> > >>>>>> doing
> > >>>>>> that.
> > >>>>>> So, yes.
> > >>>>>>>
> > >>>>>>>>
> > >>>>>>>> Either create a 0.92.1 release (sounds hard based on
> > >>>>>>>> above)
> > >>>>>>>> or create a 0.93 release (in which case should we create
> > >>>>>>>> the
> > >>>>>>>> 0.93
> > >>>>>>>> branch from trunk as soon as this is fixed?)
> > >>>>>>>>
> > >>>>>>>> How long to re-test? (Thats a question for Sarah, Justin,
> > >>>>>>>> and
> > >>>>>>>> Ketan)
> > >>>>>>>> Could this include the Cray support mods?
> > >>>>>>>
> > >>>>>>> No! Fixing a problem is not a venue for introducing untested
> > >>>>>>> things
> > >>>>>>> into
> > >>>>>>> a release.
> > >>>>>>
> > >>>>>> I meant the Cray feature for 0.93 not 0.92.1
> > >>>>>> Yes, that should be tested.
> > >>>>>> But its being used pretty heavily.
> > >>>>>>
> > >>>>>> - Mike
> > >>>>>>
> > >>>>>>> But it could be discussed separately :)
> > >>>>>>>
> > >>>>>>> Mihael
> > >>>>>>
> > >>>>>> --
> > >>>>>> Michael Wilde
> > >>>>>> Computation Institute, University of Chicago
> > >>>>>> Mathematics and Computer Science Division
> > >>>>>> Argonne National Laboratory
> > >>>>>>
> > >>>>>> _______________________________________________
> > >>>>>> Swift-devel mailing list
> > >>>>>> Swift-devel at ci.uchicago.edu
> > >>>>>> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> > >>>>>
> > >>>>> --
> > >>>>> Michael Wilde
> > >>>>> Computation Institute, University of Chicago
> > >>>>> Mathematics and Computer Science Division
> > >>>>> Argonne National Laboratory
> > >>>>>
> > >>>>> _______________________________________________
> > >>>>> Swift-devel mailing list
> > >>>>> Swift-devel at ci.uchicago.edu
> > >>>>> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> > >>>>
> > >>
> > >> --
> > >> Michael Wilde
> > >> Computation Institute, University of Chicago
> > >> Mathematics and Computer Science Division
> > >> Argonne National Laboratory
> > >>
> > >> _______________________________________________
> > >> Swift-devel mailing list
> > >> Swift-devel at ci.uchicago.edu
> > >> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> > >
> > >
> >
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
From bugzilla-daemon at mcs.anl.gov Sat Apr 2 08:36:12 2011
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Sat, 2 Apr 2011 08:36:12 -0500 (CDT)
Subject: [Swift-devel] [Bug 313] New: update.sh script to push Swift web
contents to live site gives lengthy errors
Message-ID:
https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=313
Summary: update.sh script to push Swift web contents to live
site gives lengthy errors
Product: Swift
Version: 0.93
Platform: PC
OS/Version: Mac OS
Status: NEW
Severity: normal
Priority: P2
Component: Documentation
AssignedTo: wozniak at mcs.anl.gov
ReportedBy: wilde at mcs.anl.gov
I have been seeing the permission errors below from this script for a while
now.
Justin, I think you mentioned that you know what causes them so Im assigning
this to you.
Errors are:
com$ cd /ci/www/projects/swift
com$ ./update.sh
chmod: changing permissions of `./update.sh': Operation not permitted
chmod: changing permissions of `updatenodocs.sh': Operation not permitted
--------- Updating www... ----------
U downloads/index.php
Updated to revision 4241.
find: ./guides/trunk/historical: Permission denied
find: ./guides/trunk/formatting: Permission denied
find: ./guides/trunk/plot-tour: Permission denied
find: ./guides/release-0.91/historical: Permission denied
find: ./guides/release-0.91/formatting: Permission denied
find: ./guides/release-0.91/plot-tour: Permission denied
--------- Updating docs... ----------
--------- Updating guide: guides/trunk ----------
/ci/www/projects/swift/guides/trunk /ci/www/projects/swift
ln: accessing `formatting/docbook': Permission denied
ln: accessing `formatting/fop': Permission denied
Skipped '.'
./update.sh: line 23: ./buildguides.sh: Permission denied
/ci/www/projects/swift/guides/trunk/userguide
/ci/www/projects/swift/guides/trunk /ci/www/projects/swift
chmod: changing permissions of `appmodel.php': Operation not permitted
chmod: changing permissions of `buildoptions.php': Operation not permitted
chmod: changing permissions of `cdm.php': Operation not permitted
chmod: changing permissions of `clustering.php': Operation not permitted
chmod: changing permissions of `coasters.php': Operation not permitted
chmod: changing permissions of `commands.php': Operation not permitted
chmod: changing permissions of `engineconfiguration.php': Operation not
permitted
chmod: changing permissions of `extending.php': Operation not permitted
chmod: changing permissions of `functions.php': Operation not permitted
chmod: changing permissions of `index.php': Operation not permitted
chmod: changing permissions of `kickstart.php': Operation not permitted
chmod: changing permissions of `language.php': Operation not permitted
chmod: changing permissions of `localhowtos.php': Operation not permitted
chmod: changing permissions of `mappers.php': Operation not permitted
chmod: changing permissions of `overview.php': Operation not permitted
chmod: changing permissions of `procedures.php': Operation not permitted
chmod: changing permissions of `profiles.php': Operation not permitted
chmod: changing permissions of `reliability.php': Operation not permitted
chmod: changing permissions of `sitecatalog.php': Operation not permitted
chmod: changing permissions of `techoverview.php': Operation not permitted
chmod: changing permissions of `transformationcatalog.php': Operation not
permitted
chmod: changing permissions of `userguide-rotated.jpeg': Operation not
permitted
chmod: changing permissions of `userguide-shane.jpeg': Operation not permitted
chmod: changing permissions of `swift-site-model.png': Operation not permitted
chmod: changing permissions of `type-hierarchy.png': Operation not permitted
chmod: changing permissions of `appmodel.php': Operation not permitted
chmod: changing permissions of `buildoptions.php': Operation not permitted
chmod: changing permissions of `cdm.php': Operation not permitted
chmod: changing permissions of `clustering.php': Operation not permitted
chmod: changing permissions of `coasters.php': Operation not permitted
chmod: changing permissions of `commands.php': Operation not permitted
chmod: changing permissions of `engineconfiguration.php': Operation not
permitted
chmod: changing permissions of `extending.php': Operation not permitted
chmod: changing permissions of `functions.php': Operation not permitted
chmod: changing permissions of `index.php': Operation not permitted
chmod: changing permissions of `kickstart.php': Operation not permitted
chmod: changing permissions of `language.php': Operation not permitted
chmod: changing permissions of `localhowtos.php': Operation not permitted
chmod: changing permissions of `mappers.php': Operation not permitted
chmod: changing permissions of `overview.php': Operation not permitted
chmod: changing permissions of `procedures.php': Operation not permitted
chmod: changing permissions of `profiles.php': Operation not permitted
chmod: changing permissions of `reliability.php': Operation not permitted
chmod: changing permissions of `sitecatalog.php': Operation not permitted
chmod: changing permissions of `techoverview.php': Operation not permitted
chmod: changing permissions of `transformationcatalog.php': Operation not
permitted
chmod: cannot access `*.pdf': No such file or directory
/ci/www/projects/swift/guides/trunk /ci/www/projects/swift
chmod: changing permissions of `userguide': Operation not permitted
chmod: changing permissions of `userguide/procedures.php': Operation not
permitted
chmod: changing permissions of `userguide/commands.php': Operation not
permitted
chmod: changing permissions of `userguide/localhowtos.php': Operation not
permitted
chmod: changing permissions of `userguide/profiles.php': Operation not
permitted
chmod: changing permissions of `userguide/appmodel.php': Operation not
permitted
chmod: changing permissions of `userguide/coasters.php': Operation not
permitted
chmod: changing permissions of `userguide/swift-site-model.png': Operation not
permitted
chmod: changing permissions of `userguide/mappers.php': Operation not permitted
chmod: changing permissions of `userguide/overview.php': Operation not
permitted
chmod: changing permissions of `userguide/kickstart.php': Operation not
permitted
chmod: changing permissions of `userguide/sitecatalog.php': Operation not
permitted
chmod: changing permissions of `userguide/functions.php': Operation not
permitted
chmod: changing permissions of `userguide/cdm.php': Operation not permitted
chmod: changing permissions of `userguide/extending.php': Operation not
permitted
chmod: changing permissions of `userguide/language.php': Operation not
permitted
chmod: changing permissions of `userguide/buildoptions.php': Operation not
permitted
chmod: changing permissions of `userguide/index.php': Operation not permitted
chmod: changing permissions of `userguide/reliability.php': Operation not
permitted
chmod: changing permissions of `userguide/techoverview.php': Operation not
permitted
chmod: changing permissions of `userguide/type-hierarchy.png': Operation not
permitted
chmod: changing permissions of `userguide/engineconfiguration.php': Operation
not permitted
chmod: changing permissions of `userguide/clustering.php': Operation not
permitted
chmod: changing permissions of `userguide/userguide-shane.jpeg': Operation not
permitted
chmod: changing permissions of `userguide/userguide-rotated.jpeg': Operation
not permitted
chmod: changing permissions of `userguide/transformationcatalog.php': Operation
not permitted
chmod: changing permissions of `userguide': Operation not permitted
/ci/www/projects/swift
--------- Updating guide: guides/release-0.91 ----------
/ci/www/projects/swift/guides/release-0.91 /ci/www/projects/swift
ln: accessing `formatting/docbook': Permission denied
ln: accessing `formatting/fop': Permission denied
Skipped '.'
./update.sh: line 23: ./buildguides.sh: Permission denied
/ci/www/projects/swift/guides/release-0.91/userguide
/ci/www/projects/swift/guides/release-0.91 /ci/www/projects/swift
chmod: changing permissions of `appmodel.php': Operation not permitted
chmod: changing permissions of `buildoptions.php': Operation not permitted
chmod: changing permissions of `clustering.php': Operation not permitted
chmod: changing permissions of `coasters.php': Operation not permitted
chmod: changing permissions of `commands.php': Operation not permitted
chmod: changing permissions of `engineconfiguration.php': Operation not
permitted
chmod: changing permissions of `extending.php': Operation not permitted
chmod: changing permissions of `functions.php': Operation not permitted
chmod: changing permissions of `index.php': Operation not permitted
chmod: changing permissions of `kickstart.php': Operation not permitted
chmod: changing permissions of `language.php': Operation not permitted
chmod: changing permissions of `localhowtos.php': Operation not permitted
chmod: changing permissions of `mappers.php': Operation not permitted
chmod: changing permissions of `overview.php': Operation not permitted
chmod: changing permissions of `procedures.php': Operation not permitted
chmod: changing permissions of `profiles.php': Operation not permitted
chmod: changing permissions of `reliability.php': Operation not permitted
chmod: changing permissions of `sitecatalog.php': Operation not permitted
chmod: changing permissions of `techoverview.php': Operation not permitted
chmod: changing permissions of `transformationcatalog.php': Operation not
permitted
chmod: changing permissions of `userguide-rotated.jpeg': Operation not
permitted
chmod: changing permissions of `userguide-shane.jpeg': Operation not permitted
chmod: changing permissions of `swift-site-model.png': Operation not permitted
chmod: changing permissions of `type-hierarchy.png': Operation not permitted
chmod: changing permissions of `appmodel.php': Operation not permitted
chmod: changing permissions of `buildoptions.php': Operation not permitted
chmod: changing permissions of `clustering.php': Operation not permitted
chmod: changing permissions of `coasters.php': Operation not permitted
chmod: changing permissions of `commands.php': Operation not permitted
chmod: changing permissions of `engineconfiguration.php': Operation not
permitted
chmod: changing permissions of `extending.php': Operation not permitted
chmod: changing permissions of `functions.php': Operation not permitted
chmod: changing permissions of `index.php': Operation not permitted
chmod: changing permissions of `kickstart.php': Operation not permitted
chmod: changing permissions of `language.php': Operation not permitted
chmod: changing permissions of `localhowtos.php': Operation not permitted
chmod: changing permissions of `mappers.php': Operation not permitted
chmod: changing permissions of `overview.php': Operation not permitted
chmod: changing permissions of `procedures.php': Operation not permitted
chmod: changing permissions of `profiles.php': Operation not permitted
chmod: changing permissions of `reliability.php': Operation not permitted
chmod: changing permissions of `sitecatalog.php': Operation not permitted
chmod: changing permissions of `techoverview.php': Operation not permitted
chmod: changing permissions of `transformationcatalog.php': Operation not
permitted
chmod: cannot access `*.pdf': No such file or directory
/ci/www/projects/swift/guides/release-0.91 /ci/www/projects/swift
chmod: changing permissions of `userguide': Operation not permitted
chmod: changing permissions of `userguide/procedures.php': Operation not
permitted
chmod: changing permissions of `userguide/commands.php': Operation not
permitted
chmod: changing permissions of `userguide/localhowtos.php': Operation not
permitted
chmod: changing permissions of `userguide/profiles.php': Operation not
permitted
chmod: changing permissions of `userguide/appmodel.php': Operation not
permitted
chmod: changing permissions of `userguide/coasters.php': Operation not
permitted
chmod: changing permissions of `userguide/swift-site-model.png': Operation not
permitted
chmod: changing permissions of `userguide/mappers.php': Operation not permitted
chmod: changing permissions of `userguide/overview.php': Operation not
permitted
chmod: changing permissions of `userguide/kickstart.php': Operation not
permitted
chmod: changing permissions of `userguide/sitecatalog.php': Operation not
permitted
chmod: changing permissions of `userguide/functions.php': Operation not
permitted
chmod: changing permissions of `userguide/extending.php': Operation not
permitted
chmod: changing permissions of `userguide/language.php': Operation not
permitted
chmod: changing permissions of `userguide/buildoptions.php': Operation not
permitted
chmod: changing permissions of `userguide/index.php': Operation not permitted
chmod: changing permissions of `userguide/reliability.php': Operation not
permitted
chmod: changing permissions of `userguide/techoverview.php': Operation not
permitted
chmod: changing permissions of `userguide/type-hierarchy.png': Operation not
permitted
chmod: changing permissions of `userguide/engineconfiguration.php': Operation
not permitted
chmod: changing permissions of `userguide/clustering.php': Operation not
permitted
chmod: changing permissions of `userguide/userguide-shane.jpeg': Operation not
permitted
chmod: changing permissions of `userguide/userguide-rotated.jpeg': Operation
not permitted
chmod: changing permissions of `userguide/transformationcatalog.php': Operation
not permitted
chmod: changing permissions of `userguide': Operation not permitted
/ci/www/projects/swift
--------- All done ----------
com
--
Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the reporter.
From wilde at mcs.anl.gov Sat Apr 2 08:54:54 2011
From: wilde at mcs.anl.gov (Michael Wilde)
Date: Sat, 2 Apr 2011 08:54:54 -0500 (CDT)
Subject: [Swift-devel] [Bug 291] New: Add a exists() function to test
for file existence
In-Reply-To:
Message-ID: <1089753936.57755.1301752494884.JavaMail.root@zimbra.anl.gov>
Sounds good, John. Yes, there is a logical negation operator, "!":
com$ cat bool.swift
boolean b = true;
if(!b) {
trace("its true");
} else {
trace("its false");
}
com$ swift bool.swift
Swift svn swift-r3826 cog-r2988
RunID: 20110402-0854-r3p5rrqa
Progress:
SwiftScript trace: its false
Final status:
com$
- Mike
----- Original Message -----
> On Apr 1, 2011, at 12:25 PM, Michael Wilde wrote:
>
> > John, I cc'ed you to confirm that the function is exactly what you
> > were looking for, and that the simple code below matches exactly the
> > requirement thats driving this feature request.
> >
> > Can you confirm that both of these are true?
>
> Michael,
>
> So assuming that there is a logical negation operator in Swift the
> function you describe matches my requirements.
>
> Thanks,
> John
>
>
> > We just want to make sure that we understand the need and determine
> > if the proposed exists() function is the best way to address it.
> > From your comment below, I was not quite sure if exists() is exactly
> > the right approach here.
> >
> > Thanks,
> >
> > Mike
> >
> >
> > ----- Original Message -----
> >> Michael,
> >>
> >> This type of function would be great to have.
> >>
> >> John
> >> On Apr 1, 2011, at 11:51 AM, Michael Wilde wrote:
> >>
> >>> Basically as far as I understand: the presence or absence of a
> >>> particular data file within the inout dataset is to be used to
> >>> determine whether the code to process that dataset subsection gets
> >>> invoked or not:
> >>>
> >>> if (exists("extra.data")) {
> >>> DataFile extraInput<"extra.data">;
> >>> extraResult = analyze(extraInput);
> >>> }
> >>>
> >>> The above is my assumption based on a phone call. We can and
> >>> should
> >>> verify the assumption with a simple example.
> >>>
> >>> I also thought we can try this today by seeing if extraInput can
> >>> be
> >>> an array, mapped to zero items if nothing to do and 1 item if
> >>> something to do. That would at least let us test the use case.
> >>>
> >>> John, can you verify if the example Swift lines above are what you
> >>> are looking for here?
> >>>
> >>> - Mike
> >>>
> >>> ----- Original Message -----
> >>>> On Fri, 2011-04-01 at 10:51 -0500, Michael Wilde wrote:
> >>>>
> >>>>> - we should first verify that exists() will solve the NCAR need
> >>>>> in
> >>>>> a
> >>>>> sufficiently clean way
> >>>>
> >>>> I think this is important. Can we get a description of the
> >>>> problem
> >>>> instead of a (otherwise) random proposal for a solution?
> >>>
> >>> --
> >>> Michael Wilde
> >>> Computation Institute, University of Chicago
> >>> Mathematics and Computer Science Division
> >>> Argonne National Laboratory
> >>>
> >
> > --
> > Michael Wilde
> > Computation Institute, University of Chicago
> > Mathematics and Computer Science Division
> > Argonne National Laboratory
> >
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
From tim.g.armstrong at gmail.com Sat Apr 2 09:38:50 2011
From: tim.g.armstrong at gmail.com (Tim Armstrong)
Date: Sat, 2 Apr 2011 09:38:50 -0500
Subject: [Swift-devel] Re: saturday morning rambling about exceptions
In-Reply-To:
References:
Message-ID:
Yeah, I like the simplicity of if(!exists(...)).
With try/catch I just think it would be difficult for the user to reason
about what state things are in when an exception occurs and we end up in the
catch block - it seems very nondeterministic which threads will be running
and how much progress they will have made
- tim
On Fri, Apr 1, 2011 at 11:34 PM, Ben Clifford wrote:
>
> > Try/catch statements don't have a clean intepretation if you're trying to
> > follow the flow of data through the program.
>
> Right.
>
> I thought about this a bit before but it started getting all haskelly and
> something i didn't want to approach - as mike says its much more
> researchy.
>
> The main idea which I found most comfortable was Haskell's Either type.
> That can model something like exceptions but is more amenable to a
> dataflow style of programming.
>
> (although C implements something very restricted similar in the form of
> pointers which can be NULL, or when returning a return code that is in
> some range of values for an error and some other range of values for
> success)
>
> The way the haskell Either type works is that something which might "throw
> an exception" returns a value that is either an error object or a correct
> value object.
>
> So then you use an if or a case or anything else that can change behaviour
> based on data to change your flow.
>
> Imagine in C:
>
> p = malloc(5);
> if(p == NULL) {
> /* catch-exception, but dataflow style - we don't have to look at p
> right after the malloc. We can store it into a structure and
> come back to it later to check.
> unfortuantely, there is not enough space in p to represent
> any richer kind of exception information other than "FAIL" */
> } else {
> {
> /* no exception, and we have the correct value in p */
> }
>
> In haskell, that looks like:
> p = somefunc
> case p of
> Right d -> doSomethingWith d -- somefunc succeeded and returned
> -- us value d
> Left ex -> handleError ex -- somefunc failed and returned
> -- value ex as the equivalnet of a
> -- Java Exception object.
>
> Now it gets a bit awkward having to unwrap "Right d" after every such
> function call, and in that respect I think a syntax that looks more like
> try-catch is much easier to program with. However I think the right way to
> go is to define its semantics in terms of "dataflow" style exceptions
> above rather than control-flow.
>
> I think that's possible and would result in something that satisfies both
> the dataflow-purist camp and the "I like exception syntax" camp (both
> camps of which I'm in ;)
>
> --
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From wilde at mcs.anl.gov Sat Apr 2 10:36:04 2011
From: wilde at mcs.anl.gov (Michael Wilde)
Date: Sat, 2 Apr 2011 10:36:04 -0500 (CDT)
Subject: [Swift-devel] Re: saturday morning rambling about exceptions
In-Reply-To:
Message-ID: <810281195.57855.1301758564983.JavaMail.root@zimbra.anl.gov>
----- Original Message -----
> Yeah, I like the simplicity of if(!exists(...)).
I do too, but Ben, I like the ideas you suggest of dataflow-based exception handling and think we should continue the discussion.
I think that the exists() use case is not one for exception handling. Rather, it raises other programming model issues related to both mapping and to the original make-like "virtual data" semantics of VDL: if a file doesnt exist you execute the function to create it. Maybe we can cleanly integrate this back into Swift in an optional manner (ie, it only happens when explicitly requested). On the other hand, maybe thats exactly what exists() will give us? Dont know yet.
I think the exception handling mechanism is very useful to pursue for true exception conditions. And there to, we have the issue of when should exceptions get handled transparently by the runtime system and when should the script be able to see them? Maybe, there, too, exception handling happens transparent unless the user sets explicit exception handling. We'd need to consider if this changes with a dataflow-based approach.
- Mike
> With try/catch I just think it would be difficult for the user to
> reason about what state things are in when an exception occurs and we
> end up in the catch block - it seems very nondeterministic which
> threads will be running and how much progress they will have made
>
> - tim
>
>
>
>
> On Fri, Apr 1, 2011 at 11:34 PM, Ben Clifford < benc at hawaga.org.uk >
> wrote:
>
>
>
> > Try/catch statements don't have a clean intepretation if you're
> > trying to
> > follow the flow of data through the program.
>
> Right.
>
> I thought about this a bit before but it started getting all haskelly
> and
> something i didn't want to approach - as mike says its much more
> researchy.
>
> The main idea which I found most comfortable was Haskell's Either
> type.
> That can model something like exceptions but is more amenable to a
> dataflow style of programming.
>
> (although C implements something very restricted similar in the form
> of
> pointers which can be NULL, or when returning a return code that is in
> some range of values for an error and some other range of values for
> success)
>
> The way the haskell Either type works is that something which might
> "throw
> an exception" returns a value that is either an error object or a
> correct
> value object.
>
> So then you use an if or a case or anything else that can change
> behaviour
> based on data to change your flow.
>
> Imagine in C:
>
> p = malloc(5);
> if(p == NULL) {
> /* catch-exception, but dataflow style - we don't have to look at p
> right after the malloc. We can store it into a structure and
> come back to it later to check.
> unfortuantely, there is not enough space in p to represent
> any richer kind of exception information other than "FAIL" */
> } else {
> {
> /* no exception, and we have the correct value in p */
> }
>
> In haskell, that looks like:
> p = somefunc
> case p of
> Right d -> doSomethingWith d -- somefunc succeeded and returned
> -- us value d
> Left ex -> handleError ex -- somefunc failed and returned
> -- value ex as the equivalnet of a
> -- Java Exception object.
>
> Now it gets a bit awkward having to unwrap "Right d" after every such
> function call, and in that respect I think a syntax that looks more
> like
> try-catch is much easier to program with. However I think the right
> way to
> go is to define its semantics in terms of "dataflow" style exceptions
> above rather than control-flow.
>
> I think that's possible and would result in something that satisfies
> both
> the dataflow-purist camp and the "I like exception syntax" camp (both
> camps of which I'm in ;)
>
> --
>
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
From wozniak at mcs.anl.gov Sat Apr 2 12:26:34 2011
From: wozniak at mcs.anl.gov (Justin M Wozniak)
Date: Sat, 2 Apr 2011 12:26:34 -0500 (Central Daylight Time)
Subject: [Swift-devel] [Bug 291] New: Add a exists() function to test
for file existence
In-Reply-To: <2A5A416A-CAB6-4D82-B55F-0CFBC8F3B770@ucar.edu>
References: <729744535.55640.1301680289613.JavaMail.root@zimbra.anl.gov>
<2A5A416A-CAB6-4D82-B55F-0CFBC8F3B770@ucar.edu>
Message-ID:
I have a prototype of this, I'll get it checked in later today.
Justin
On Fri, 1 Apr 2011, John Dennis wrote:
> Michael,
>
> This type of function would be great to have.
>
> John
> On Apr 1, 2011, at 11:51 AM, Michael Wilde wrote:
>
>> Basically as far as I understand: the presence or absence of a particular
>> data file within the inout dataset is to be used to determine whether the
>> code to process that dataset subsection gets invoked or not:
>>
>> if (exists("extra.data")) {
>> DataFile extraInput<"extra.data">;
>> extraResult = analyze(extraInput);
>> }
>>
>> The above is my assumption based on a phone call. We can and should verify
>> the assumption with a simple example.
>>
>> I also thought we can try this today by seeing if extraInput can be an
>> array, mapped to zero items if nothing to do and 1 item if something to do.
>> That would at least let us test the use case.
>>
>> John, can you verify if the example Swift lines above are what you are
>> looking for here?
>>
>> - Mike
>>
>> ----- Original Message -----
>>> On Fri, 2011-04-01 at 10:51 -0500, Michael Wilde wrote:
>>>
>>>> - we should first verify that exists() will solve the NCAR need in a
>>>> sufficiently clean way
>>>
>>> I think this is important. Can we get a description of the problem
>>> instead of a (otherwise) random proposal for a solution?
>>
>> --
>> Michael Wilde
>> Computation Institute, University of Chicago
>> Mathematics and Computer Science Division
>> Argonne National Laboratory
>>
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
--
Justin M Wozniak
From wozniak at mcs.anl.gov Sat Apr 2 12:45:49 2011
From: wozniak at mcs.anl.gov (Justin M Wozniak)
Date: Sat, 2 Apr 2011 12:45:49 -0500 (Central Daylight Time)
Subject: [Swift-devel] duplicated job submission in swift-0.92?
In-Reply-To: <162077988.57719.1301750203568.JavaMail.root@zimbra.anl.gov>
References: <162077988.57719.1301750203568.JavaMail.root@zimbra.anl.gov>
Message-ID:
That's right- I will run it again today to confirm.
On Sat, 2 Apr 2011, Michael Wilde wrote:
> Mihael,
>
> My understanding is that Justin used a binary search approach: he kept
> extracting a point-in-time snapshot from SVN, and built and tested it,
> selecting dates in binary-search mode until he narrowed down the
> revision range that caused the failure to between r3835 and r3837.
>
> Justin can confirm this when he sees this message, but don't count on
> confirmation very soon this weekend. Best to do you own tests to verify
> (or I can if that would help).
>
> - Mike
>
> ----- Original Message -----
>> That's possible, looking at the code.
>>
>> Though what makes you think it's that?
>>
>> Mihael
>>
>> On Fri, 2011-04-01 at 17:33 -0500, Justin M Wozniak wrote:
>>> I found that it appeared between Swift r3835 and r3837.
>>>
>>> On Fri, 1 Apr 2011, Michael Wilde wrote:
>>>
>>>> And Swift 0.91 works OK - it does *not* exhibit the twice-each
>>>> bug.
>>>>
>>>> Justin: when you went backwards down the Swift 0.92 branch on
>>>> Thursday
>>>> morning, what did you find in terms of where it appeared the bug
>>>> was
>>>> introduced?
>>>>
>>>> - Mike
>>>>
>>>>
>>>> ----- Original Message -----
>>>>> I think we mist-spoke: The posted release 0.92 also exhibits the
>>>>> twice-each bug as far as I acn tell.
>>>>>
>>>>> Mihael, Justin: can you test asap to confirm or refute that
>>>>> observation?
>>>>>
>>>>> Thanks,
>>>>>
>>>>> - Mike
>>>>>
>>>>> which swift: ~/swift/rev/swift-0.92/bin/swift
>>>>>
>>>>> com$ swift -version
>>>>> Swift svn swift-r4157 cog-r3056
>>>>>
>>>>> com$ cd ~/swift/lab
>>>>> com$ cat zz3.swift
>>>>> int arr[];
>>>>>
>>>>> arr[0]=1;
>>>>> arr[1]=2;
>>>>>
>>>>> foreach a in arr {
>>>>> trace("for", a);
>>>>> }
>>>>>
>>>>> com$ swift zz3.swift
>>>>> Swift svn swift-r4157 cog-r3056
>>>>>
>>>>> RunID: 20110401-1645-yyy87p39
>>>>> Progress:
>>>>> SwiftScript trace: for, 2
>>>>> SwiftScript trace: for, 1
>>>>> SwiftScript trace: for, 1
>>>>> SwiftScript trace: for, 2
>>>>> Final status:
>>>>> com$
>>>>>
>>>>>
>>>>> ----- Original Message -----
>>>>>> I think both are good as they are.
>>>>>>
>>>>>> Would you like me to send it?
>>>>>>
>>>>>> Mihael
>>>>>>
>>>>>> On Thu, 2011-03-31 at 20:57 -0500, Michael Wilde wrote:
>>>>>>> And I will send this to swift-user:
>>>>>>>
>>>>>>> "Dear Swift Users,
>>>>>>>
>>>>>>> On March 29 we discovered that the Release 0.92 branches of the
>>>>>>> Swift and CoG trees were changed after the release and a
>>>>>>> concurrency
>>>>>>> bug was introduced. If you are running Swift from this *source
>>>>>>> code*
>>>>>>> base, please revert back to a known-working release such as the
>>>>>>> 0.92
>>>>>>> binary release if at all possible.
>>>>>>>
>>>>>>> We're working on restoring the 0.92 SVN branch to the correct
>>>>>>> state
>>>>>>> and will report back to this email list when that is done."
>>>>>>>
>>>>>>> Anything else to say? Feel free to send this out, adjusted as
>>>>>>> needed, or just tell me what to change and I will.
>>>>>>>
>>>>>>> - Mike
>>>>>>>
>>>>>>>
>>>>>>> ----- Original Message -----
>>>>>>>> Please check this proposed warning on the Downloads page and
>>>>>>>> let
>>>>>>>> me
>>>>>>>> know if its what we need there:
>>>>>>>>
>>>>>>>> http://www.ci.uchicago.edu/~wilde/swift/downloads/index.php
>>>>>>>>
>>>>>>>> I also fixed the 0.91 typo (but the downloads dont actually
>>>>>>>> work
>>>>>>>> from
>>>>>>>> this test web. I think they will once this is committed and
>>>>>>>> pushed
>>>>>>>> live).
>>>>>>>>
>>>>>>>> - Mike
>>>>>>>>
>>>>>>>>
>>>>>>>> ----- Original Message -----
>>>>>>>>> ----- Original Message -----
>>>>>>>>>> On Thu, 2011-03-31 at 20:14 -0500, Michael Wilde wrote:
>>>>>>>>>>> ----- Original Message -----
>>>>>>>>>>>> We decided the following:
>>>>>>>>>>>> - I will revert the changes in the 0.92 branch
>>>>>>>>>>>> - re-commit bug fixes that were committed after the
>>>>>>>>>>>> merge
>>>>>>>>>>>> - merge the 0.92 branch to trunk
>>>>>>>>>>>> - fix the problems in trunk
>>>>>>>>>>>
>>>>>>>>>>> Sounds good. But when and how does the fix get to users?
>>>>>>>>>>
>>>>>>>>>> The package(s) are fine. Though we should probably also have
>>>>>>>>>> a
>>>>>>>>>> source
>>>>>>>>>> package. The merge was done after the package(s) were
>>>>>>>>>> uploaded
>>>>>>>>>> to
>>>>>>>>>> the
>>>>>>>>>> swift site.
>>>>>>>>>
>>>>>>>>> Ah, great!
>>>>>>>>>
>>>>>>>>>> This only affects folks who have checked out from SVN the
>>>>>>>>>> 0.92
>>>>>>>>>> branch
>>>>>>>>>> after the merge 9 days (or so) ago.
>>>>>>>>>
>>>>>>>>> Hmm - I question that. The release we use, based on 0.92 on
>>>>>>>>> Beagle,
>>>>>>>>> shows the twice-each error, and it was made on Feb 25, about
>>>>>>>>> 35
>>>>>>>>> days
>>>>>>>>> ago. Does this merit clarification?
>>>>>>>>>
>>>>>>>>>> We should send an email to the user list once this is fixed.
>>>>>>>>>> We
>>>>>>>>>> may
>>>>>>>>>> also
>>>>>>>>>> want to send an email warning them not to check out from SVN
>>>>>>>>>> but
>>>>>>>>>> download the precompiled package instead.
>>>>>>>>>
>>>>>>>>> OK. I cant say that this will reach everyone. Perhaps some
>>>>>>>>> status
>>>>>>>>> notes on the Download page are in order. The 0.91 link there
>>>>>>>>> is
>>>>>>>>> wrong,
>>>>>>>>> so we need to fix that page anyways.
>>>>>>>>>
>>>>>>>>>> I am a bit confused though. I would have expected the
>>>>>>>>>> release
>>>>>>>>>> to
>>>>>>>>>> come
>>>>>>>>>> with some announcement of some form.
>>>>>>>>>
>>>>>>>>> Agreed. We kept this low profile because we were trying to
>>>>>>>>> coordinate
>>>>>>>>> it with a Web change that we never accomplished. And we've
>>>>>>>>> lost
>>>>>>>>> the
>>>>>>>>> habit of swift-user announcements but got to get back to
>>>>>>>>> doing
>>>>>>>>> that.
>>>>>>>>> So, yes.
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Either create a 0.92.1 release (sounds hard based on
>>>>>>>>>>> above)
>>>>>>>>>>> or create a 0.93 release (in which case should we create
>>>>>>>>>>> the
>>>>>>>>>>> 0.93
>>>>>>>>>>> branch from trunk as soon as this is fixed?)
>>>>>>>>>>>
>>>>>>>>>>> How long to re-test? (Thats a question for Sarah, Justin,
>>>>>>>>>>> and
>>>>>>>>>>> Ketan)
>>>>>>>>>>> Could this include the Cray support mods?
>>>>>>>>>>
>>>>>>>>>> No! Fixing a problem is not a venue for introducing untested
>>>>>>>>>> things
>>>>>>>>>> into
>>>>>>>>>> a release.
>>>>>>>>>
>>>>>>>>> I meant the Cray feature for 0.93 not 0.92.1
>>>>>>>>> Yes, that should be tested.
>>>>>>>>> But its being used pretty heavily.
>>>>>>>>>
>>>>>>>>> - Mike
>>>>>>>>>
>>>>>>>>>> But it could be discussed separately :)
>>>>>>>>>>
>>>>>>>>>> Mihael
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Michael Wilde
>>>>>>>>> Computation Institute, University of Chicago
>>>>>>>>> Mathematics and Computer Science Division
>>>>>>>>> Argonne National Laboratory
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> Swift-devel mailing list
>>>>>>>>> Swift-devel at ci.uchicago.edu
>>>>>>>>> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>>>>>>>>
>>>>>>>> --
>>>>>>>> Michael Wilde
>>>>>>>> Computation Institute, University of Chicago
>>>>>>>> Mathematics and Computer Science Division
>>>>>>>> Argonne National Laboratory
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Swift-devel mailing list
>>>>>>>> Swift-devel at ci.uchicago.edu
>>>>>>>> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>>>>>>>
>>>>>
>>>>> --
>>>>> Michael Wilde
>>>>> Computation Institute, University of Chicago
>>>>> Mathematics and Computer Science Division
>>>>> Argonne National Laboratory
>>>>>
>>>>> _______________________________________________
>>>>> Swift-devel mailing list
>>>>> Swift-devel at ci.uchicago.edu
>>>>> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>>>>
>>>>
>>>
>
>
--
Justin M Wozniak
From hategan at mcs.anl.gov Sat Apr 2 13:18:30 2011
From: hategan at mcs.anl.gov (Mihael Hategan)
Date: Sat, 02 Apr 2011 11:18:30 -0700
Subject: [Swift-devel] [Bug 291] New: Add a exists() function to test
for file existence
In-Reply-To:
References: <729744535.55640.1301680289613.JavaMail.root@zimbra.anl.gov>
<1301733232.18577.3.camel@blabla2.none>
Message-ID: <1301768310.19940.5.camel@blabla2.none>
On Sat, 2011-04-02 at 09:00 +0000, Ben Clifford wrote:
> > And I am emphasizing here that the optional attribute should belong to
> > the data. You probably don't want to have it optional with one
> > invocation and non optional with another. Given that the successful
> > completion of a run requires that all invocations complete successfully,
> > anything else would be silly.
>
> maybe "optional" is not the right word. its data that needs to exist. but
> you are specifying two ways for it to exist in the scope of the current
> run: either you find it on a filesystem, or you run some program that
> outputs it. but I agree that whatever it is called, its attached to the
> data not to an invocation. it sounds a lot like the virtual data idea.
>
"maybe"? but that sounds imperative rather than declarative.
From hategan at mcs.anl.gov Sat Apr 2 13:20:04 2011
From: hategan at mcs.anl.gov (Mihael Hategan)
Date: Sat, 02 Apr 2011 11:20:04 -0700
Subject: [Swift-devel] duplicated job submission in swift-0.92?
In-Reply-To:
References: <162077988.57719.1301750203568.JavaMail.root@zimbra.anl.gov>
Message-ID: <1301768404.19940.6.camel@blabla2.none>
On Sat, 2011-04-02 at 12:45 -0500, Justin M Wozniak wrote:
> That's right- I will run it again today to confirm.
>
> On Sat, 2 Apr 2011, Michael Wilde wrote:
>
> > Mihael,
> >
> > My understanding is that Justin used a binary search approach:
Nicely done.
> he kept
> > extracting a point-in-time snapshot from SVN, and built and tested it,
> > selecting dates in binary-search mode until he narrowed down the
> > revision range that caused the failure to between r3835 and r3837.
> >
> > Justin can confirm this when he sees this message, but don't count on
> > confirmation very soon this weekend. Best to do you own tests to verify
> > (or I can if that would help).
> >
> > - Mike
> >
> > ----- Original Message -----
> >> That's possible, looking at the code.
> >>
> >> Though what makes you think it's that?
> >>
> >> Mihael
> >>
> >> On Fri, 2011-04-01 at 17:33 -0500, Justin M Wozniak wrote:
> >>> I found that it appeared between Swift r3835 and r3837.
> >>>
> >>> On Fri, 1 Apr 2011, Michael Wilde wrote:
> >>>
> >>>> And Swift 0.91 works OK - it does *not* exhibit the twice-each
> >>>> bug.
> >>>>
> >>>> Justin: when you went backwards down the Swift 0.92 branch on
> >>>> Thursday
> >>>> morning, what did you find in terms of where it appeared the bug
> >>>> was
> >>>> introduced?
> >>>>
> >>>> - Mike
> >>>>
> >>>>
> >>>> ----- Original Message -----
> >>>>> I think we mist-spoke: The posted release 0.92 also exhibits the
> >>>>> twice-each bug as far as I acn tell.
> >>>>>
> >>>>> Mihael, Justin: can you test asap to confirm or refute that
> >>>>> observation?
> >>>>>
> >>>>> Thanks,
> >>>>>
> >>>>> - Mike
> >>>>>
> >>>>> which swift: ~/swift/rev/swift-0.92/bin/swift
> >>>>>
> >>>>> com$ swift -version
> >>>>> Swift svn swift-r4157 cog-r3056
> >>>>>
> >>>>> com$ cd ~/swift/lab
> >>>>> com$ cat zz3.swift
> >>>>> int arr[];
> >>>>>
> >>>>> arr[0]=1;
> >>>>> arr[1]=2;
> >>>>>
> >>>>> foreach a in arr {
> >>>>> trace("for", a);
> >>>>> }
> >>>>>
> >>>>> com$ swift zz3.swift
> >>>>> Swift svn swift-r4157 cog-r3056
> >>>>>
> >>>>> RunID: 20110401-1645-yyy87p39
> >>>>> Progress:
> >>>>> SwiftScript trace: for, 2
> >>>>> SwiftScript trace: for, 1
> >>>>> SwiftScript trace: for, 1
> >>>>> SwiftScript trace: for, 2
> >>>>> Final status:
> >>>>> com$
> >>>>>
> >>>>>
> >>>>> ----- Original Message -----
> >>>>>> I think both are good as they are.
> >>>>>>
> >>>>>> Would you like me to send it?
> >>>>>>
> >>>>>> Mihael
> >>>>>>
> >>>>>> On Thu, 2011-03-31 at 20:57 -0500, Michael Wilde wrote:
> >>>>>>> And I will send this to swift-user:
> >>>>>>>
> >>>>>>> "Dear Swift Users,
> >>>>>>>
> >>>>>>> On March 29 we discovered that the Release 0.92 branches of the
> >>>>>>> Swift and CoG trees were changed after the release and a
> >>>>>>> concurrency
> >>>>>>> bug was introduced. If you are running Swift from this *source
> >>>>>>> code*
> >>>>>>> base, please revert back to a known-working release such as the
> >>>>>>> 0.92
> >>>>>>> binary release if at all possible.
> >>>>>>>
> >>>>>>> We're working on restoring the 0.92 SVN branch to the correct
> >>>>>>> state
> >>>>>>> and will report back to this email list when that is done."
> >>>>>>>
> >>>>>>> Anything else to say? Feel free to send this out, adjusted as
> >>>>>>> needed, or just tell me what to change and I will.
> >>>>>>>
> >>>>>>> - Mike
> >>>>>>>
> >>>>>>>
> >>>>>>> ----- Original Message -----
> >>>>>>>> Please check this proposed warning on the Downloads page and
> >>>>>>>> let
> >>>>>>>> me
> >>>>>>>> know if its what we need there:
> >>>>>>>>
> >>>>>>>> http://www.ci.uchicago.edu/~wilde/swift/downloads/index.php
> >>>>>>>>
> >>>>>>>> I also fixed the 0.91 typo (but the downloads dont actually
> >>>>>>>> work
> >>>>>>>> from
> >>>>>>>> this test web. I think they will once this is committed and
> >>>>>>>> pushed
> >>>>>>>> live).
> >>>>>>>>
> >>>>>>>> - Mike
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> ----- Original Message -----
> >>>>>>>>> ----- Original Message -----
> >>>>>>>>>> On Thu, 2011-03-31 at 20:14 -0500, Michael Wilde wrote:
> >>>>>>>>>>> ----- Original Message -----
> >>>>>>>>>>>> We decided the following:
> >>>>>>>>>>>> - I will revert the changes in the 0.92 branch
> >>>>>>>>>>>> - re-commit bug fixes that were committed after the
> >>>>>>>>>>>> merge
> >>>>>>>>>>>> - merge the 0.92 branch to trunk
> >>>>>>>>>>>> - fix the problems in trunk
> >>>>>>>>>>>
> >>>>>>>>>>> Sounds good. But when and how does the fix get to users?
> >>>>>>>>>>
> >>>>>>>>>> The package(s) are fine. Though we should probably also have
> >>>>>>>>>> a
> >>>>>>>>>> source
> >>>>>>>>>> package. The merge was done after the package(s) were
> >>>>>>>>>> uploaded
> >>>>>>>>>> to
> >>>>>>>>>> the
> >>>>>>>>>> swift site.
> >>>>>>>>>
> >>>>>>>>> Ah, great!
> >>>>>>>>>
> >>>>>>>>>> This only affects folks who have checked out from SVN the
> >>>>>>>>>> 0.92
> >>>>>>>>>> branch
> >>>>>>>>>> after the merge 9 days (or so) ago.
> >>>>>>>>>
> >>>>>>>>> Hmm - I question that. The release we use, based on 0.92 on
> >>>>>>>>> Beagle,
> >>>>>>>>> shows the twice-each error, and it was made on Feb 25, about
> >>>>>>>>> 35
> >>>>>>>>> days
> >>>>>>>>> ago. Does this merit clarification?
> >>>>>>>>>
> >>>>>>>>>> We should send an email to the user list once this is fixed.
> >>>>>>>>>> We
> >>>>>>>>>> may
> >>>>>>>>>> also
> >>>>>>>>>> want to send an email warning them not to check out from SVN
> >>>>>>>>>> but
> >>>>>>>>>> download the precompiled package instead.
> >>>>>>>>>
> >>>>>>>>> OK. I cant say that this will reach everyone. Perhaps some
> >>>>>>>>> status
> >>>>>>>>> notes on the Download page are in order. The 0.91 link there
> >>>>>>>>> is
> >>>>>>>>> wrong,
> >>>>>>>>> so we need to fix that page anyways.
> >>>>>>>>>
> >>>>>>>>>> I am a bit confused though. I would have expected the
> >>>>>>>>>> release
> >>>>>>>>>> to
> >>>>>>>>>> come
> >>>>>>>>>> with some announcement of some form.
> >>>>>>>>>
> >>>>>>>>> Agreed. We kept this low profile because we were trying to
> >>>>>>>>> coordinate
> >>>>>>>>> it with a Web change that we never accomplished. And we've
> >>>>>>>>> lost
> >>>>>>>>> the
> >>>>>>>>> habit of swift-user announcements but got to get back to
> >>>>>>>>> doing
> >>>>>>>>> that.
> >>>>>>>>> So, yes.
> >>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>> Either create a 0.92.1 release (sounds hard based on
> >>>>>>>>>>> above)
> >>>>>>>>>>> or create a 0.93 release (in which case should we create
> >>>>>>>>>>> the
> >>>>>>>>>>> 0.93
> >>>>>>>>>>> branch from trunk as soon as this is fixed?)
> >>>>>>>>>>>
> >>>>>>>>>>> How long to re-test? (Thats a question for Sarah, Justin,
> >>>>>>>>>>> and
> >>>>>>>>>>> Ketan)
> >>>>>>>>>>> Could this include the Cray support mods?
> >>>>>>>>>>
> >>>>>>>>>> No! Fixing a problem is not a venue for introducing untested
> >>>>>>>>>> things
> >>>>>>>>>> into
> >>>>>>>>>> a release.
> >>>>>>>>>
> >>>>>>>>> I meant the Cray feature for 0.93 not 0.92.1
> >>>>>>>>> Yes, that should be tested.
> >>>>>>>>> But its being used pretty heavily.
> >>>>>>>>>
> >>>>>>>>> - Mike
> >>>>>>>>>
> >>>>>>>>>> But it could be discussed separately :)
> >>>>>>>>>>
> >>>>>>>>>> Mihael
> >>>>>>>>>
> >>>>>>>>> --
> >>>>>>>>> Michael Wilde
> >>>>>>>>> Computation Institute, University of Chicago
> >>>>>>>>> Mathematics and Computer Science Division
> >>>>>>>>> Argonne National Laboratory
> >>>>>>>>>
> >>>>>>>>> _______________________________________________
> >>>>>>>>> Swift-devel mailing list
> >>>>>>>>> Swift-devel at ci.uchicago.edu
> >>>>>>>>> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> >>>>>>>>
> >>>>>>>> --
> >>>>>>>> Michael Wilde
> >>>>>>>> Computation Institute, University of Chicago
> >>>>>>>> Mathematics and Computer Science Division
> >>>>>>>> Argonne National Laboratory
> >>>>>>>>
> >>>>>>>> _______________________________________________
> >>>>>>>> Swift-devel mailing list
> >>>>>>>> Swift-devel at ci.uchicago.edu
> >>>>>>>> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> >>>>>>>
> >>>>>
> >>>>> --
> >>>>> Michael Wilde
> >>>>> Computation Institute, University of Chicago
> >>>>> Mathematics and Computer Science Division
> >>>>> Argonne National Laboratory
> >>>>>
> >>>>> _______________________________________________
> >>>>> Swift-devel mailing list
> >>>>> Swift-devel at ci.uchicago.edu
> >>>>> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> >>>>
> >>>>
> >>>
> >
> >
>
From wilde at mcs.anl.gov Sat Apr 2 14:07:04 2011
From: wilde at mcs.anl.gov (Michael Wilde)
Date: Sat, 2 Apr 2011 14:07:04 -0500 (CDT)
Subject: [Swift-devel] Re: Important: Please confirm evidence on twiceEach()
bug
In-Reply-To: <1301768243.19940.4.camel@blabla2.none>
Message-ID: <908171605.57992.1301771224770.JavaMail.root@zimbra.anl.gov>
Moving an off-list thread to the list:
A few comments below just to make sure we're all in sync...
> I was just trying to figure out what the problem was and whether the
> binary packages were affected.
My tests show that the bug occurs in the 0.92 binary and *not* in the 0.91 binary.
Please replicate these tests yourself to verify. My test was:
com$ cat zz3.swift
int arr[];
arr[0]=1;
arr[1]=2;
foreach a in arr {
trace("for", a);
}
com$ PATH=~/swift/rev/swift-0.91/bin:$PATH
com$ which swift
~/swift/rev/swift-0.91/bin/swift
com$ swift zz3.swift
Swift svn swift-r3826 cog-r2988
RunID: 20110402-1401-68rni1b1
Progress:
SwiftScript trace: for, 1
SwiftScript trace: for, 2
Final status:
com$ PATH=~/swift/rev/swift-0.92/bin:$PATH
com$ which swift
~/swift/rev/swift-0.92/bin/swift
com$ swift zz3.swift
Swift svn swift-r4157 cog-r3056
RunID: 20110402-1402-zqhod0ha
Progress:
SwiftScript trace: for, 2
SwiftScript trace: for, 1
SwiftScript trace: for, 1
SwiftScript trace: for, 2
Final status:
com$
> In that process, I had a suspicion that it was the merge because I
> thought 0.92 was tested before the release and the bug should have
> shown
> up.
The bug has *some* subtlety in that I did massive runs for modftdock on 0.92 and they never encountered this bug.
But I verified that in at least two cases the bug does *not* occur:
foreach a,i in [0:9]
vec=readData(); foreach a,i in vec
I had two nested loops: the outer was driven by a readData array; the inner by a constant array.
I think its either the case that we have no test case for this problem, or that some tests are silently failing in our testing.
> It seemed reasonable to suspect that the merge introduced it, but
> I
> didn't test that to confirm it. I will now.
This is what I am questioning: it seems clear that this but *could not possibly* have come form Justin's recent (wrong-direction) merge in prep for 0.93.
> However, I do think the merge was done the other way around, and I
> revert it to keep in line with what we agreed was the "proper" way of
> handling releases.
Yes, I agree totally here: Justin's merge was done in the wrong direction - a well-intentioned mis-interpretetion of the Subversion book Merge chapter. I knew that Justin was going to do this, but I was not astute enough in merge and release methodology to have caught the problem. My fault as much as Justin's. But its clear to me that:
- the twiceEach bug was introduced long before this merge
- its good that we have the 0.92 branch now restored to its proper state
- we should do something like an 0.91.2 (or .1) release containing the twiceEach fix
- we should document our release methods and start (resume?) using tags as well
- we need to add a test case to the test suite for this bug, and keep growing the test suite with both functional and regression tests.
> Apart from that I will figure out what exactly the bug was due to and
> try to fix it.
Great - thanks!
- Mike
From hategan at mcs.anl.gov Sat Apr 2 14:14:13 2011
From: hategan at mcs.anl.gov (Mihael Hategan)
Date: Sat, 02 Apr 2011 12:14:13 -0700
Subject: [Swift-devel] Re: Important: Please confirm evidence on twiceEach()
bug
In-Reply-To: <908171605.57992.1301771224770.JavaMail.root@zimbra.anl.gov>
References: <908171605.57992.1301771224770.JavaMail.root@zimbra.anl.gov>
Message-ID: <1301771653.21635.1.camel@blabla2.none>
On Sat, 2011-04-02 at 14:07 -0500, Michael Wilde wrote:
> > It seemed reasonable to suspect that the merge introduced it, but
> > I
> > didn't test that to confirm it. I will now.
>
> This is what I am questioning: it seems clear that this but *could not
> possibly* have come form Justin's recent (wrong-direction) merge in
> prep for 0.93.
Oh, it became clear in the mean time that it is not true. But at the
time, it seemed likely.
From wilde at mcs.anl.gov Sat Apr 2 15:34:55 2011
From: wilde at mcs.anl.gov (Michael Wilde)
Date: Sat, 2 Apr 2011 15:34:55 -0500 (CDT)
Subject: [Swift-devel] Swift Documentation Platform
In-Reply-To:
Message-ID: <955316759.58065.1301776495245.JavaMail.root@zimbra.anl.gov>
----- Original Message -----
> Building this list is a good start. Where should we store it?
Same web as the ReleasePlan:
https://sites.google.com/site/swiftdevel/release-plans
which is where we should move:
https://sites.google.com/site/swiftparallelscripting/swift-docs-todos
>
> You could also add the other CoG and Karajan docs.
>
> As of Wednesday we decided we are giving up on Google Sites for user
> documentation, but we are going to continue with the swift-devel site
> for
> internal (but publically-readable) notes.
This sounds good. If any pages there need to be private to the group, they can.
Maybe one more sites/ web: swftgroup for internal group matters unrelated to swift.
> We're thinking of putting at least a month into asciidoc. Once we have
> that in place, we should be able to easily paste things into there
> from
> any source.
With a few guidelines, we can try editing a few of the doc items in transit from the cookbook into asciidoc. We dont need the whole doc toolchain working: just enough to generate eg an html page or pdf.
Is that something we can do soon? We'd need to start and maintain a content writing guide and some references to asciidoc.
Then we need a way to separate the "core web" from "per release" documents.
- Mike
- Mike
>
> Justin
>
> On Fri, 1 Apr 2011, Ketan Maheshwari wrote:
>
> > Hi,
> >
> > While we close in on a decision, I am writing this as an observation
> > to
> > the ongoing discussion about Swift Documentation Platform. And some
> > thoughts in the end.
> >
> > As of now we have a Main, existing Swift Documentation page:
> >
> > [1] http://www.ci.uchicago.edu/swift/docs/index.php
> >
> > In addition, we have pages on CI wiki related to Swift
> > documentations:
> >
> >
> > [2] http://www.ci.uchicago.edu/wiki/bin/view/SWFT/WebHome
> >
> > The above link contains many useful but semi-complete/unrounded
> > pages on
> > cookbooks, tutorials and may technical notes.
> >
> >
> > We have a page on cog wiki dedicated to Coasters:
> >
> > [3] http://wiki.cogkit.org/wiki/Coasters
> >
> > The pictures are very neat but slightly outdated and needs update.
> > More
> > pictures would also be required in my opinion to explain several of
> > the
> > relatively new coasters concepts.
> >
> >
> > We have google sites whose contents overlap with [1] , likely that
> > it is
> > completely redundant to [1]
> >
> > [4] https://sites.google.com/site/swiftguide/home
> >
> >
> > A wealth of information about Swift techniques, examples, issues,
> > notes
> > and ideas are living on the following: [5]
> > https://bugzilla.mcs.anl.gov/swift/
> >
> > [6] mail.ci.uchicago.edu/pipermail/swift-user
> >
> > [7] http://mail.ci.uchicago.edu/pipermail/swift-devel/
> >
> > [8] Mike's Swift Notes (As an attached doc)
>
> --
> Justin M Wozniak
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
From bugzilla-daemon at mcs.anl.gov Sat Apr 2 16:38:39 2011
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Sat, 2 Apr 2011 16:38:39 -0500 (CDT)
Subject: [Swift-devel] [Bug 315] New: better diagnostics to identify
unmapped paths
Message-ID:
https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=315
Summary: better diagnostics to identify unmapped paths
Product: Swift
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: SwiftScript language
AssignedTo: hategan at mcs.anl.gov
ReportedBy: aespinosa at cs.uchicago.edu
This works
$ cat seq.in
1
2
3
4
$ cat array_incomplete.swift
type file;
app(file o[])
split(file i, int j){
split "-l" 1 @filename(i) @strcat(j, "seqout.");
}
file input <"seq.in">;
foreach j in [0:1] {
string foo;
if (j == 0) {
foo = "0seqout.aa, 0seqout.ab, 0seqout.ac, 0seqout.ad";
}
if (j == 1) {
foo = "1seqout.aa, 1seqout.ab, 1seqout.ac, 1seqout.ad";
}
file out[] ;
if (j < 1) {
out = split(input, j); // line 21
}
else {
out = split(input, j); // line 23
}
}
$$ ~/swift/swift-0.92/bin/swift -tc.file tc.data array_incomplete.swift
Swift svn swift-r4157 cog-r3056
RunID: 20110402-1619-dn042ure
Progress:
Progress: Stage in:1 Finished successfully:1
Final status: Finished successfully:2
But if I comment out line 21, we get this error message:
~/swift/swift-0.92/bin/swift -tc.file tc.data array_incomplete.swift
Swift svn swift-r4157 cog-r3056
RunID: 20110402-1621-k63e22s2
Progress:
Execution failed:
mapper.existing() returned a path [0] that it cannot subsequently map
The swift log file contains this corresponding entry:
011-04-02 16:21:13,887-0500 DEBUG VDL2ExecutionContext vdl:setfieldvalue @
array_incomplete.kml, line: 155: java.lang.IllegalStateException:
mapper.existing() returned a path [0] that it cannot subsequently map
Checking the kml file we have this call to setFieldValue():
array_incomplete.kml:155
foo
swift#string#17003
Mike and I concluded that the reason for the error was that out[] is already
recognized as an output dataset in line 23. But for j=0, out[] as an output
file was not produced and will result in unmapped paths.
Is there a better way to diagnose this problem off the bat? Or is this the
expected behavior? Can out[] be an input file (non-intermediate) for j=0 and
output file for j=1?
--
Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
From aespinosa at cs.uchicago.edu Sat Apr 2 16:41:15 2011
From: aespinosa at cs.uchicago.edu (Allan Espinosa)
Date: Sat, 2 Apr 2011 16:41:15 -0500
Subject: [Swift-devel] Fwd: [Swift-user] determining unmapped paths
In-Reply-To: <655120943.25600.1301012918101.JavaMail.root@zimbra.anl.gov>
References:
<655120943.25600.1301012918101.JavaMail.root@zimbra.anl.gov>
Message-ID:
Filed as bug 315: https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=315
2011/3/24 Michael Wilde :
> Sarah, this is a perfect example of a messaging deficiency to fix. Can you add to bugzilla?
>
> Thanks,
>
> Mike
>
>
> ----- Forwarded Message -----
> From: "Allan Espinosa"
> To: "Swift-User"
> Sent: Thursday, March 24, 2011 4:28:51 PM
> Subject: [Swift-user] determining unmapped paths
>
> I'm trying figure out where in my workflow is causing this problem:
>
> 2011-03-24 16:23:50,485-0500 WARN ?FlowNode Ex098
> java.lang.IllegalStateException: mapper.existing() returned a path [3]
> that it cannot subsequently map
> ? ? ? ?at org.griphyn.vdl.mapping.RootDataNode.checkInputs(RootDataNode.java:129)
> ? ? ? ?at org.griphyn.vdl.mapping.RootArrayDataNode.checkInputs(RootArrayDataNode.java:67)
> ? ? ? ?at org.griphyn.vdl.mapping.RootArrayDataNode.innerInit(RootArrayDataNode.java:53)
> ? ? ? ?at org.griphyn.vdl.mapping.RootArrayDataNode.handleClosed(RootArrayDataNode.java:80)
> ? ? ? ?at org.griphyn.vdl.mapping.AbstractDataNode.notifyListeners(AbstractDataNode.java:583)
> ? ? ? ?at org.griphyn.vdl.mapping.AbstractDataNode.closeShallow(AbstractDataNode.java:396)
> ? ? ? ?at org.griphyn.vdl.mapping.ArrayDataNode.closeDeep(ArrayDataNode.java:51)
> ? ? ? ?at org.griphyn.vdl.karajan.lib.PartialCloseDataset.function(PartialCloseDataset.java:79)
> ? ? ? ?at org.griphyn.vdl.karajan.lib.VDLFunction.post(VDLFunction.java:68)
> ? ? ? ?at org.globus.cog.karajan.workflow.nodes.Sequential.startNext(Sequential.java:29)
> ? ? ? ?at org.globus.cog.karajan.workflow.nodes.Sequential.executeChildren(Sequential.java:20)
> ? ? ? ?at org.globus.cog.karajan.workflow.nodes.FlowContainer.execute(FlowContainer.java:63)
> ? ? ? ?at org.globus.cog.karajan.workflow.nodes.FlowNode.restart(FlowNode.java:139)
> ? ? ? ?at org.globus.cog.karajan.workflow.nodes.FlowNode.start(FlowNode.java:197)
> ? ? ? ?at org.globus.cog.karajan.workflow.events.EventBus.start(EventBus.java:104)
> ? ? ? ?at org.globus.cog.karajan.workflow.events.EventTargetPair.run(EventTargetPair.java:40)
> ? ? ? ?at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> ? ? ? ?at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> ? ? ? ?at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> ? ? ? ?at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> ? ? ? ?at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> ? ? ? ?at java.lang.Thread.run(Thread.java:619)
>
> It doesn't specify which data object it crashes on so i'm quite
> clueless at this point.
>
> I'm using the latest trunk
>
> any particular log4j class i should be enabling to debug?
>
>
> Thanks,
> -Allan
>
> --
--
Allan M. Espinosa
PhD student, Computer Science
University of Chicago
From bugzilla-daemon at mcs.anl.gov Sat Apr 2 17:15:33 2011
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Sat, 2 Apr 2011 17:15:33 -0500 (CDT)
Subject: [Swift-devel] [Bug 307] array slicing
In-Reply-To:
References:
Message-ID: <20110402221533.A80AC1C072@wind.mcs.anl.gov>
https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=307
Allan Espinosa changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |swift-devel at ci.uchicago.edu
Resolution| |WORKSFORME
--- Comment #1 from Allan Espinosa 2011-04-02 17:15:33 ---
Proposed workaround: Use sparse arrays:
Example usecase: we want to send 2 elements to each agg_job();
type file;
app agg_job(file in[]) {
echo @filenames(in);
}
file foo[] ;
file sub1[] ; // elements [0:1]
file sub2[] ; // elements [2:3]
foreach i in [0:1]{
sub1[i] = foo[i];
}
foreach i in [2:3]{
sub2[i] = foo[i];
}
agg_job(sub1);
agg_job(sub2)
--
Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are watching the assignee of the bug.
From bugzilla-daemon at mcs.anl.gov Sat Apr 2 18:18:25 2011
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Sat, 2 Apr 2011 18:18:25 -0500 (CDT)
Subject: [Swift-devel] [Bug 315] better diagnostics to identify unmapped
paths
In-Reply-To:
References:
Message-ID: <20110402231825.BAB9D2BFB3@wind.mcs.anl.gov>
https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=315
Michael Wilde changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |wilde at mcs.anl.gov
--- Comment #1 from Michael Wilde 2011-04-02 18:18:25 ---
First, to note: this test fails in 0.92 and works in 0.91. Even stranger, in
0.92 the test *succeeds* in about 1 out of 20 tries, which suggests there is
some kind of race condition here.
I think we can also simplify the test case further, and retry. Doing that now.
...
Further experimentation suggests this has something to do with the way
conditionals and local array variables nested inside a foreach loop are
handled. Depending on how much of the statements inside the loop are commented
out, the code either works or fails in 0.92.
So we should wait until we have a 0.92 point release with twiceEach fixed, and
then re-test.
If it still fails, I (or Allan or Mihael) should try a few variations and make
sure all logically correct ones work, and that incorrect ones get reasonable
error messages.
Lastly, the original intent for this bug was to also generate a better error
message stating which object Swift is having trouble mapping.
Also note: you need the following tc entry in addition to Allan's test script
below:
localhost split /usr/bin/split INSTALLED
INTEL32::LINUX null
---
>From a larger perspective:
This bug and the test cases for it raise a very confusing aspect of Swift
semantics: how mapping of output arrays affects Swift's notion of the array
size. We need to document the rules that govern Swift's behavior in these
cases and cleanly define how this relates to both size and array closing.
We need to decide if Swift *should* be giving a runtime error in the case Allan
shows, and what that error should be.
My understanding of this example is the following:
- we have an output array of files out[]
- we map that array to N file names
- we call a function f() to create the array
- the app function uses filenames(out) to place the filenames on the command
line
Now, when will @filenames() be runnable? (wrt futures and array closing)?
Can this array grow later?
Does the app() need to create all filenames mapped in the out() array?
These seem to be subtle issues that need to be documented, with clarifying,
runnable test examples.
We can split this doc test out to a separate enh bg after the primary problem
is fixed. I realized when trying to simplify the test case that the
documentation points above are not so closely related to the actual problem
here as I initially thought.
--
Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
From hategan at mcs.anl.gov Sat Apr 2 20:37:04 2011
From: hategan at mcs.anl.gov (Mihael Hategan)
Date: Sat, 02 Apr 2011 18:37:04 -0700
Subject: [Swift-devel] duplicated job submission in swift-0.92?
In-Reply-To: <1301597554.1319.5.camel@blabla2.none>
References: <357669173.48524.1301541122267.JavaMail.root@zimbra.anl.gov>
<1301541697.23803.9.camel@blabla2.none>
<1301596477.1319.0.camel@blabla2.none>
<1301597554.1319.5.camel@blabla2.none>
Message-ID: <1301794624.12893.1.camel@blabla2.none>
On Thu, 2011-03-31 at 11:52 -0700, Mihael Hategan wrote:
> We decided the following:
> - I will revert the changes in the 0.92 branch
done
> - re-commit bug fixes that were committed after the merge
done
> - merge the 0.92 branch to trunk
done
> - fix the problems in trunk
and done except the problem was in the branch. I think it was a manual
merge of mine gone wrong. Trunk should be clean.
We should make a patch release.
Mihael
From wilde at mcs.anl.gov Sun Apr 3 13:16:11 2011
From: wilde at mcs.anl.gov (Michael Wilde)
Date: Sun, 3 Apr 2011 13:16:11 -0500 (CDT)
Subject: [Swift-devel] duplicated job submission in swift-0.92?
In-Reply-To: <1301794624.12893.1.camel@blabla2.none>
Message-ID: <938578309.58852.1301854571833.JavaMail.root@zimbra.anl.gov>
Nice - thank you, Mihael! Can you make the branch next? Call it 0.92.1 or .2, whatever you think is best practice (I favor 0.92.1 but have no strong feeling).
- Mike
----- Original Message -----
> On Thu, 2011-03-31 at 11:52 -0700, Mihael Hategan wrote:
> > We decided the following:
> > - I will revert the changes in the 0.92 branch
>
> done
>
> > - re-commit bug fixes that were committed after the merge
>
> done
>
> > - merge the 0.92 branch to trunk
>
> done
>
> > - fix the problems in trunk
>
> and done except the problem was in the branch. I think it was a manual
> merge of mine gone wrong. Trunk should be clean.
>
> We should make a patch release.
>
> Mihael
>
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
From hategan at mcs.anl.gov Sun Apr 3 13:19:47 2011
From: hategan at mcs.anl.gov (Mihael Hategan)
Date: Sun, 03 Apr 2011 11:19:47 -0700
Subject: [Swift-devel] duplicated job submission in swift-0.92?
In-Reply-To: <938578309.58852.1301854571833.JavaMail.root@zimbra.anl.gov>
References: <938578309.58852.1301854571833.JavaMail.root@zimbra.anl.gov>
Message-ID: <1301854787.25788.0.camel@blabla2.none>
That would be a tag and we'd do it after we test the current code in the
branch a bit.
On Sun, 2011-04-03 at 13:16 -0500, Michael Wilde wrote:
> Nice - thank you, Mihael! Can you make the branch next? Call it 0.92.1 or .2, whatever you think is best practice (I favor 0.92.1 but have no strong feeling).
>
> - Mike
>
> ----- Original Message -----
> > On Thu, 2011-03-31 at 11:52 -0700, Mihael Hategan wrote:
> > > We decided the following:
> > > - I will revert the changes in the 0.92 branch
> >
> > done
> >
> > > - re-commit bug fixes that were committed after the merge
> >
> > done
> >
> > > - merge the 0.92 branch to trunk
> >
> > done
> >
> > > - fix the problems in trunk
> >
> > and done except the problem was in the branch. I think it was a manual
> > merge of mine gone wrong. Trunk should be clean.
> >
> > We should make a patch release.
> >
> > Mihael
> >
> >
> > _______________________________________________
> > Swift-devel mailing list
> > Swift-devel at ci.uchicago.edu
> > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>
From bugzilla-daemon at mcs.anl.gov Sun Apr 3 16:23:47 2011
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Sun, 3 Apr 2011 16:23:47 -0500 (CDT)
Subject: [Swift-devel] [Bug 291] Add a exists() function to test for file
existence
In-Reply-To:
References:
Message-ID: <20110403212347.3F19A2DE32@wind.mcs.anl.gov>
https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=291
Justin Wozniak changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
--- Comment #1 from Justin Wozniak 2011-04-03 16:23:46 ---
Implemented.
--
Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the reporter.
From bugzilla-daemon at mcs.anl.gov Sun Apr 3 16:48:14 2011
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Sun, 3 Apr 2011 16:48:14 -0500 (CDT)
Subject: [Swift-devel] [Bug 261] update.sh script (for pushing web content
live) gives errors
In-Reply-To:
References:
Message-ID: <20110403214814.1FF4A2DF27@wind.mcs.anl.gov>
https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=261
Justin Wozniak changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |benc at hawaga.org.uk,
| |wilde at mcs.anl.gov
--- Comment #2 from Justin Wozniak 2011-04-03 16:48:13 ---
Working on this now. I will fix the group perms that I can. Seems that some
files in here are owned by benc.
--
Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
You are watching the reporter.
From bugzilla-daemon at mcs.anl.gov Sun Apr 3 16:50:17 2011
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Sun, 3 Apr 2011 16:50:17 -0500 (CDT)
Subject: [Swift-devel] [Bug 313] update.sh script to push Swift web contents
to live site gives lengthy errors
In-Reply-To:
References:
Message-ID: <20110403215017.921822DF3C@wind.mcs.anl.gov>
https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=313
Justin Wozniak changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
--- Comment #1 from Justin Wozniak 2011-04-03 16:50:17 ---
Ok, Mike, try again. I think in the future I will have to set my umask to a
more permissive setting when working here.
--
Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the reporter.
From wozniak at mcs.anl.gov Sun Apr 3 16:56:54 2011
From: wozniak at mcs.anl.gov (Justin M Wozniak)
Date: Sun, 3 Apr 2011 16:56:54 -0500 (Central Daylight Time)
Subject: [Swift-devel] [Bug 291] New: Add a exists() function to test
for file existence
In-Reply-To:
References: <729744535.55640.1301680289613.JavaMail.root@zimbra.anl.gov>
<2A5A416A-CAB6-4D82-B55F-0CFBC8F3B770@ucar.edu>
Message-ID:
Ok, John, you can give this a try in trunk if you like. The syntax for
the built-in is @exists, it takes a string and returns a boolean.
Justin
On Sat, 2 Apr 2011, Justin M Wozniak wrote:
>
> I have a prototype of this, I'll get it checked in later today.
> Justin
>
> On Fri, 1 Apr 2011, John Dennis wrote:
>
>> Michael,
>>
>> This type of function would be great to have.
>>
>> John
>> On Apr 1, 2011, at 11:51 AM, Michael Wilde wrote:
>>
>>> Basically as far as I understand: the presence or absence of a particular
>>> data file within the inout dataset is to be used to determine whether the
>>> code to process that dataset subsection gets invoked or not:
>>>
>>> if (exists("extra.data")) {
>>> DataFile extraInput<"extra.data">;
>>> extraResult = analyze(extraInput);
>>> }
>>>
>>> The above is my assumption based on a phone call. We can and should
>>> verify the assumption with a simple example.
>>>
>>> I also thought we can try this today by seeing if extraInput can be an
>>> array, mapped to zero items if nothing to do and 1 item if something to
>>> do. That would at least let us test the use case.
>>>
>>> John, can you verify if the example Swift lines above are what you are
>>> looking for here?
>>>
>>> - Mike
>>>
>>> ----- Original Message -----
>>>> On Fri, 2011-04-01 at 10:51 -0500, Michael Wilde wrote:
>>>>
>>>>> - we should first verify that exists() will solve the NCAR need in a
>>>>> sufficiently clean way
>>>>
>>>> I think this is important. Can we get a description of the problem
>>>> instead of a (otherwise) random proposal for a solution?
>>>
>>> --
>>> Michael Wilde
>>> Computation Institute, University of Chicago
>>> Mathematics and Computer Science Division
>>> Argonne National Laboratory
>>>
>>
>> _______________________________________________
>> Swift-devel mailing list
>> Swift-devel at ci.uchicago.edu
>> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>
>
--
Justin M Wozniak
From jon.monette at gmail.com Sun Apr 3 19:14:32 2011
From: jon.monette at gmail.com (Jonathan Monette)
Date: Sun, 3 Apr 2011 19:14:32 -0500
Subject: [Swift-devel] compile error
Message-ID:
I just tried compiling swift-r4251 and got the following compile errror:
compile:
[echo] [swift]: COMPILE
[mkdir] Created dir:
/autonfs/home/jonmon/Library/Swift/trunk/cog/modules/swift/build
[javac] Compiling 377 source files to
/autonfs/home/jonmon/Library/Swift/trunk/cog/modules/swift/build
[javac]
/autonfs/home/jonmon/Library/Swift/trunk/cog/modules/swift/src/org/griphyn/vdl/engine/Karajan.java:578:
cannot find symbol
[javac] symbol : method getAnyNumOdInputArgs()
[javac] location: class org.griphyn.vdl.engine.ProcedureSignature
[javac] if (!proc.getAnyNumOdInputArgs() && (call.sizeOfInputArray() <
proc.sizeOfInputArray() - noOfOptInArgs ||
[javac] ^
[javac]
/autonfs/home/jonmon/Library/Swift/trunk/cog/modules/swift/src/org/griphyn/vdl/engine/Karajan.java:587:
cannot find symbol
[javac] symbol : method getAnyNumOdOutputArgs()
[javac] location: class org.griphyn.vdl.engine.ProcedureSignature
[javac] if (!proc.getAnyNumOdOutputArgs() && (call.sizeOfOutputArray()
!= proc.sizeOfOutputArray()))
[javac] ^
[javac]
/autonfs/home/jonmon/Library/Swift/trunk/cog/modules/swift/src/org/griphyn/vdl/engine/Karajan.java:599:
cannot find symbol
[javac] symbol : method getAnyNumOdInputArgs()
[javac] location: class org.griphyn.vdl.engine.ProcedureSignature
[javac] if (proc.getAnyNumOdInputArgs()) {
[javac] ^
[javac]
/autonfs/home/jonmon/Library/Swift/trunk/cog/modules/swift/src/org/griphyn/vdl/engine/Karajan.java:626:
cannot find symbol
[javac] symbol : method getAnyNumOdInputArgs()
[javac] location: class org.griphyn.vdl.engine.ProcedureSignature
[javac] if (!proc.getAnyNumOdInputArgs() && noOfMandArgs <
proc.sizeOfInputArray() - noOfOptInArgs)
[javac] ^
[javac]
/autonfs/home/jonmon/Library/Swift/trunk/cog/modules/swift/src/org/griphyn/vdl/engine/Karajan.java:667:
cannot find symbol
[javac] symbol : method getAnyNumOdOutputArgs()
[javac] location: class org.griphyn.vdl.engine.ProcedureSignature
[javac] if (proc.getAnyNumOdOutputArgs()) {
[javac] ^
[javac]
/autonfs/home/jonmon/Library/Swift/trunk/cog/modules/swift/src/org/griphyn/vdl/engine/Karajan.java:955:
cannot find symbol
[javac] symbol : method getAnyNumOdInputArgs()
[javac] location: class org.griphyn.vdl.engine.ProcedureSignature
[javac] if (!funcSignature.getAnyNumOdInputArgs() &&
[javac] ^
[javac]
/autonfs/home/jonmon/Library/Swift/trunk/cog/modules/swift/src/org/griphyn/vdl/engine/Karajan.java:966:
cannot find symbol
[javac] symbol : method getAnyNumOdInputArgs()
[javac] location: class org.griphyn.vdl.engine.ProcedureSignature
[javac] if (!funcSignature.getAnyNumOdInputArgs()) {
[javac] ^
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 7 errors
BUILD FAILED
/autonfs/home/jonmon/Library/Swift/trunk/cog/modules/swift/build.xml:73: The
following error occurred while executing this line:
/autonfs/home/jonmon/Library/Swift/trunk/cog/mbuild.xml:465: The following
error occurred while executing this line:
/autonfs/home/jonmon/Library/Swift/trunk/cog/mbuild.xml:228: Compile failed;
see the compiler error output for details.
I am using javac version 1.6.0_22
--
Any intelligent fool can make things bigger and more complex... It takes a
touch of genius - and a lot of courage to move in the opposite direction.
- Albert Einstein
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From wozniak at mcs.anl.gov Sun Apr 3 21:54:36 2011
From: wozniak at mcs.anl.gov (Justin M Wozniak)
Date: Sun, 3 Apr 2011 21:54:36 -0500 (Central Daylight Time)
Subject: [Swift-devel] compile error
In-Reply-To:
References:
Message-ID:
Oops, please try again at r4251.
On Sun, 3 Apr 2011, Jonathan Monette wrote:
> I just tried compiling swift-r4251 and got the following compile errror:
> compile:
> [echo] [swift]: COMPILE
> [mkdir] Created dir:
> /autonfs/home/jonmon/Library/Swift/trunk/cog/modules/swift/build
> [javac] Compiling 377 source files to
> /autonfs/home/jonmon/Library/Swift/trunk/cog/modules/swift/build
> [javac]
> /autonfs/home/jonmon/Library/Swift/trunk/cog/modules/swift/src/org/griphyn/vdl/engine/Karajan.java:578:
> cannot find symbol
> [javac] symbol : method getAnyNumOdInputArgs()
> [javac] location: class org.griphyn.vdl.engine.ProcedureSignature
> [javac] if (!proc.getAnyNumOdInputArgs() && (call.sizeOfInputArray() <
> proc.sizeOfInputArray() - noOfOptInArgs ||
> [javac] ^
> [javac]
> /autonfs/home/jonmon/Library/Swift/trunk/cog/modules/swift/src/org/griphyn/vdl/engine/Karajan.java:587:
> cannot find symbol
> [javac] symbol : method getAnyNumOdOutputArgs()
> [javac] location: class org.griphyn.vdl.engine.ProcedureSignature
> [javac] if (!proc.getAnyNumOdOutputArgs() && (call.sizeOfOutputArray()
> != proc.sizeOfOutputArray()))
> [javac] ^
> [javac]
> /autonfs/home/jonmon/Library/Swift/trunk/cog/modules/swift/src/org/griphyn/vdl/engine/Karajan.java:599:
> cannot find symbol
> [javac] symbol : method getAnyNumOdInputArgs()
> [javac] location: class org.griphyn.vdl.engine.ProcedureSignature
> [javac] if (proc.getAnyNumOdInputArgs()) {
> [javac] ^
> [javac]
> /autonfs/home/jonmon/Library/Swift/trunk/cog/modules/swift/src/org/griphyn/vdl/engine/Karajan.java:626:
> cannot find symbol
> [javac] symbol : method getAnyNumOdInputArgs()
> [javac] location: class org.griphyn.vdl.engine.ProcedureSignature
> [javac] if (!proc.getAnyNumOdInputArgs() && noOfMandArgs <
> proc.sizeOfInputArray() - noOfOptInArgs)
> [javac] ^
> [javac]
> /autonfs/home/jonmon/Library/Swift/trunk/cog/modules/swift/src/org/griphyn/vdl/engine/Karajan.java:667:
> cannot find symbol
> [javac] symbol : method getAnyNumOdOutputArgs()
> [javac] location: class org.griphyn.vdl.engine.ProcedureSignature
> [javac] if (proc.getAnyNumOdOutputArgs()) {
> [javac] ^
> [javac]
> /autonfs/home/jonmon/Library/Swift/trunk/cog/modules/swift/src/org/griphyn/vdl/engine/Karajan.java:955:
> cannot find symbol
> [javac] symbol : method getAnyNumOdInputArgs()
> [javac] location: class org.griphyn.vdl.engine.ProcedureSignature
> [javac] if (!funcSignature.getAnyNumOdInputArgs() &&
> [javac] ^
> [javac]
> /autonfs/home/jonmon/Library/Swift/trunk/cog/modules/swift/src/org/griphyn/vdl/engine/Karajan.java:966:
> cannot find symbol
> [javac] symbol : method getAnyNumOdInputArgs()
> [javac] location: class org.griphyn.vdl.engine.ProcedureSignature
> [javac] if (!funcSignature.getAnyNumOdInputArgs()) {
> [javac] ^
> [javac] Note: Some input files use unchecked or unsafe operations.
> [javac] Note: Recompile with -Xlint:unchecked for details.
> [javac] 7 errors
>
> BUILD FAILED
> /autonfs/home/jonmon/Library/Swift/trunk/cog/modules/swift/build.xml:73: The
> following error occurred while executing this line:
> /autonfs/home/jonmon/Library/Swift/trunk/cog/mbuild.xml:465: The following
> error occurred while executing this line:
> /autonfs/home/jonmon/Library/Swift/trunk/cog/mbuild.xml:228: Compile failed;
> see the compiler error output for details.
>
> I am using javac version 1.6.0_22
>
>
--
Justin M Wozniak
From jon.monette at gmail.com Sun Apr 3 22:02:02 2011
From: jon.monette at gmail.com (Jonathan Monette)
Date: Sun, 3 Apr 2011 22:02:02 -0500
Subject: [Swift-devel] compile error
In-Reply-To:
References:
Message-ID:
That fixed the compile error.
On Sun, Apr 3, 2011 at 9:54 PM, Justin M Wozniak wrote:
>
> Oops, please try again at r4251.
>
>
> On Sun, 3 Apr 2011, Jonathan Monette wrote:
>
> I just tried compiling swift-r4251 and got the following compile errror:
>> compile:
>> [echo] [swift]: COMPILE
>> [mkdir] Created dir:
>> /autonfs/home/jonmon/Library/Swift/trunk/cog/modules/swift/build
>> [javac] Compiling 377 source files to
>> /autonfs/home/jonmon/Library/Swift/trunk/cog/modules/swift/build
>> [javac]
>>
>> /autonfs/home/jonmon/Library/Swift/trunk/cog/modules/swift/src/org/griphyn/vdl/engine/Karajan.java:578:
>> cannot find symbol
>> [javac] symbol : method getAnyNumOdInputArgs()
>> [javac] location: class org.griphyn.vdl.engine.ProcedureSignature
>> [javac] if (!proc.getAnyNumOdInputArgs() && (call.sizeOfInputArray() <
>> proc.sizeOfInputArray() - noOfOptInArgs ||
>> [javac] ^
>> [javac]
>>
>> /autonfs/home/jonmon/Library/Swift/trunk/cog/modules/swift/src/org/griphyn/vdl/engine/Karajan.java:587:
>> cannot find symbol
>> [javac] symbol : method getAnyNumOdOutputArgs()
>> [javac] location: class org.griphyn.vdl.engine.ProcedureSignature
>> [javac] if (!proc.getAnyNumOdOutputArgs() && (call.sizeOfOutputArray()
>> != proc.sizeOfOutputArray()))
>> [javac] ^
>> [javac]
>>
>> /autonfs/home/jonmon/Library/Swift/trunk/cog/modules/swift/src/org/griphyn/vdl/engine/Karajan.java:599:
>> cannot find symbol
>> [javac] symbol : method getAnyNumOdInputArgs()
>> [javac] location: class org.griphyn.vdl.engine.ProcedureSignature
>> [javac] if (proc.getAnyNumOdInputArgs()) {
>> [javac] ^
>> [javac]
>>
>> /autonfs/home/jonmon/Library/Swift/trunk/cog/modules/swift/src/org/griphyn/vdl/engine/Karajan.java:626:
>> cannot find symbol
>> [javac] symbol : method getAnyNumOdInputArgs()
>> [javac] location: class org.griphyn.vdl.engine.ProcedureSignature
>> [javac] if (!proc.getAnyNumOdInputArgs() && noOfMandArgs <
>> proc.sizeOfInputArray() - noOfOptInArgs)
>> [javac] ^
>> [javac]
>>
>> /autonfs/home/jonmon/Library/Swift/trunk/cog/modules/swift/src/org/griphyn/vdl/engine/Karajan.java:667:
>> cannot find symbol
>> [javac] symbol : method getAnyNumOdOutputArgs()
>> [javac] location: class org.griphyn.vdl.engine.ProcedureSignature
>> [javac] if (proc.getAnyNumOdOutputArgs()) {
>> [javac] ^
>> [javac]
>>
>> /autonfs/home/jonmon/Library/Swift/trunk/cog/modules/swift/src/org/griphyn/vdl/engine/Karajan.java:955:
>> cannot find symbol
>> [javac] symbol : method getAnyNumOdInputArgs()
>> [javac] location: class org.griphyn.vdl.engine.ProcedureSignature
>> [javac] if (!funcSignature.getAnyNumOdInputArgs() &&
>> [javac] ^
>> [javac]
>>
>> /autonfs/home/jonmon/Library/Swift/trunk/cog/modules/swift/src/org/griphyn/vdl/engine/Karajan.java:966:
>> cannot find symbol
>> [javac] symbol : method getAnyNumOdInputArgs()
>> [javac] location: class org.griphyn.vdl.engine.ProcedureSignature
>> [javac] if (!funcSignature.getAnyNumOdInputArgs()) {
>> [javac] ^
>> [javac] Note: Some input files use unchecked or unsafe operations.
>> [javac] Note: Recompile with -Xlint:unchecked for details.
>> [javac] 7 errors
>>
>> BUILD FAILED
>> /autonfs/home/jonmon/Library/Swift/trunk/cog/modules/swift/build.xml:73:
>> The
>> following error occurred while executing this line:
>> /autonfs/home/jonmon/Library/Swift/trunk/cog/mbuild.xml:465: The following
>> error occurred while executing this line:
>> /autonfs/home/jonmon/Library/Swift/trunk/cog/mbuild.xml:228: Compile
>> failed;
>> see the compiler error output for details.
>>
>> I am using javac version 1.6.0_22
>>
>>
>>
> --
> Justin M Wozniak
>
--
Any intelligent fool can make things bigger and more complex... It takes a
touch of genius - and a lot of courage to move in the opposite direction.
- Albert Einstein
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From wilde at mcs.anl.gov Sun Apr 3 23:21:38 2011
From: wilde at mcs.anl.gov (Michael Wilde)
Date: Sun, 3 Apr 2011 23:21:38 -0500 (CDT)
Subject: [Swift-devel] duplicated job submission in swift-0.92?
In-Reply-To: <1301854787.25788.0.camel@blabla2.none>
Message-ID: <1959342990.59362.1301890898256.JavaMail.root@zimbra.anl.gov>
Ive tried the failing examples on a fresh checkout of the 0.92 branch, and that works now - excellent.
Allan and Jon, can you try your scripts on this latest 0.92 from svn?
Ive also re-built the 0.92 version with Cray support. That seems to work as well.
When I updated my 0.92 branch I jumped to: swift-r4252, cog-r3088, which I assume is largely from un-doing the inadvertent post-0.92 merge from trunk?
- Mike
----- Original Message -----
> That would be a tag and we'd do it after we test the current code in
> the
> branch a bit.
>
> On Sun, 2011-04-03 at 13:16 -0500, Michael Wilde wrote:
> > Nice - thank you, Mihael! Can you make the branch next? Call it
> > 0.92.1 or .2, whatever you think is best practice (I favor 0.92.1
> > but have no strong feeling).
> >
> > - Mike
> >
> > ----- Original Message -----
> > > On Thu, 2011-03-31 at 11:52 -0700, Mihael Hategan wrote:
> > > > We decided the following:
> > > > - I will revert the changes in the 0.92 branch
> > >
> > > done
> > >
> > > > - re-commit bug fixes that were committed after the merge
> > >
> > > done
> > >
> > > > - merge the 0.92 branch to trunk
> > >
> > > done
> > >
> > > > - fix the problems in trunk
> > >
> > > and done except the problem was in the branch. I think it was a
> > > manual
> > > merge of mine gone wrong. Trunk should be clean.
> > >
> > > We should make a patch release.
> > >
> > > Mihael
> > >
> > >
> > > _______________________________________________
> > > Swift-devel mailing list
> > > Swift-devel at ci.uchicago.edu
> > > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> >
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
From jon.monette at gmail.com Sun Apr 3 23:25:15 2011
From: jon.monette at gmail.com (Jonathan Monette)
Date: Sun, 3 Apr 2011 23:25:15 -0500
Subject: [Swift-devel] duplicated job submission in swift-0.92?
In-Reply-To: <1959342990.59362.1301890898256.JavaMail.root@zimbra.anl.gov>
References: <1301854787.25788.0.camel@blabla2.none>
<1959342990.59362.1301890898256.JavaMail.root@zimbra.anl.gov>
Message-ID:
Sure. Is it all in 0.92 or is it some branch like 0.92.1?
On Sun, Apr 3, 2011 at 11:21 PM, Michael Wilde wrote:
> Ive tried the failing examples on a fresh checkout of the 0.92 branch, and
> that works now - excellent.
>
> Allan and Jon, can you try your scripts on this latest 0.92 from svn?
>
> Ive also re-built the 0.92 version with Cray support. That seems to work as
> well.
>
> When I updated my 0.92 branch I jumped to: swift-r4252, cog-r3088, which I
> assume is largely from un-doing the inadvertent post-0.92 merge from trunk?
>
> - Mike
>
> ----- Original Message -----
> > That would be a tag and we'd do it after we test the current code in
> > the
> > branch a bit.
> >
> > On Sun, 2011-04-03 at 13:16 -0500, Michael Wilde wrote:
> > > Nice - thank you, Mihael! Can you make the branch next? Call it
> > > 0.92.1 or .2, whatever you think is best practice (I favor 0.92.1
> > > but have no strong feeling).
> > >
> > > - Mike
> > >
> > > ----- Original Message -----
> > > > On Thu, 2011-03-31 at 11:52 -0700, Mihael Hategan wrote:
> > > > > We decided the following:
> > > > > - I will revert the changes in the 0.92 branch
> > > >
> > > > done
> > > >
> > > > > - re-commit bug fixes that were committed after the merge
> > > >
> > > > done
> > > >
> > > > > - merge the 0.92 branch to trunk
> > > >
> > > > done
> > > >
> > > > > - fix the problems in trunk
> > > >
> > > > and done except the problem was in the branch. I think it was a
> > > > manual
> > > > merge of mine gone wrong. Trunk should be clean.
> > > >
> > > > We should make a patch release.
> > > >
> > > > Mihael
> > > >
> > > >
> > > > _______________________________________________
> > > > Swift-devel mailing list
> > > > Swift-devel at ci.uchicago.edu
> > > > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> > >
>
> --
> Michael Wilde
> Computation Institute, University of Chicago
> Mathematics and Computer Science Division
> Argonne National Laboratory
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>
--
Any intelligent fool can make things bigger and more complex... It takes a
touch of genius - and a lot of courage to move in the opposite direction.
- Albert Einstein
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From wilde at mcs.anl.gov Sun Apr 3 23:28:46 2011
From: wilde at mcs.anl.gov (Michael Wilde)
Date: Sun, 3 Apr 2011 23:28:46 -0500 (CDT)
Subject: [Swift-devel] duplicated job submission in swift-0.92?
In-Reply-To:
Message-ID: <38660267.59366.1301891326199.JavaMail.root@zimbra.anl.gov>
Its in the 0.92 SVN source branches (of both CoG and Swift). Once we test and tag it, it will get released as 0.92.1
- Mike
----- Original Message -----
> Sure. Is it all in 0.92 or is it some branch like 0.92.1?
>
>
> On Sun, Apr 3, 2011 at 11:21 PM, Michael Wilde < wilde at mcs.anl.gov >
> wrote:
>
>
> Ive tried the failing examples on a fresh checkout of the 0.92 branch,
> and that works now - excellent.
>
> Allan and Jon, can you try your scripts on this latest 0.92 from svn?
>
> Ive also re-built the 0.92 version with Cray support. That seems to
> work as well.
>
> When I updated my 0.92 branch I jumped to: swift-r4252, cog-r3088,
> which I assume is largely from un-doing the inadvertent post-0.92
> merge from trunk?
>
> - Mike
>
>
>
>
> ----- Original Message -----
> > That would be a tag and we'd do it after we test the current code in
> > the
> > branch a bit.
> >
> > On Sun, 2011-04-03 at 13:16 -0500, Michael Wilde wrote:
> > > Nice - thank you, Mihael! Can you make the branch next? Call it
> > > 0.92.1 or .2, whatever you think is best practice (I favor 0.92.1
> > > but have no strong feeling).
> > >
> > > - Mike
> > >
> > > ----- Original Message -----
> > > > On Thu, 2011-03-31 at 11:52 -0700, Mihael Hategan wrote:
> > > > > We decided the following:
> > > > > - I will revert the changes in the 0.92 branch
> > > >
> > > > done
> > > >
> > > > > - re-commit bug fixes that were committed after the merge
> > > >
> > > > done
> > > >
> > > > > - merge the 0.92 branch to trunk
> > > >
> > > > done
> > > >
> > > > > - fix the problems in trunk
> > > >
> > > > and done except the problem was in the branch. I think it was a
> > > > manual
> > > > merge of mine gone wrong. Trunk should be clean.
> > > >
> > > > We should make a patch release.
> > > >
> > > > Mihael
> > > >
> > > >
> > > > _______________________________________________
> > > > Swift-devel mailing list
> > > > Swift-devel at ci.uchicago.edu
> > > > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> > >
>
>
> --
> Michael Wilde
> Computation Institute, University of Chicago
> Mathematics and Computer Science Division
> Argonne National Laboratory
>
> _______________________________________________
>
>
>
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>
>
>
> --
> Any intelligent fool can make things bigger and more complex... It
> takes a touch of genius - and a lot of courage to move in the opposite
> direction.
> - Albert Einstein
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
From jon.monette at gmail.com Sun Apr 3 23:29:21 2011
From: jon.monette at gmail.com (Jonathan Monette)
Date: Sun, 3 Apr 2011 23:29:21 -0500
Subject: [Swift-devel] duplicated job submission in swift-0.92?
In-Reply-To: <38660267.59366.1301891326199.JavaMail.root@zimbra.anl.gov>
References:
<38660267.59366.1301891326199.JavaMail.root@zimbra.anl.gov>
Message-ID:
Ok. I will give it a try
On Sun, Apr 3, 2011 at 11:28 PM, Michael Wilde wrote:
> Its in the 0.92 SVN source branches (of both CoG and Swift). Once we test
> and tag it, it will get released as 0.92.1
>
> - Mike
>
> ----- Original Message -----
> > Sure. Is it all in 0.92 or is it some branch like 0.92.1?
> >
> >
> > On Sun, Apr 3, 2011 at 11:21 PM, Michael Wilde < wilde at mcs.anl.gov >
> > wrote:
> >
> >
> > Ive tried the failing examples on a fresh checkout of the 0.92 branch,
> > and that works now - excellent.
> >
> > Allan and Jon, can you try your scripts on this latest 0.92 from svn?
> >
> > Ive also re-built the 0.92 version with Cray support. That seems to
> > work as well.
> >
> > When I updated my 0.92 branch I jumped to: swift-r4252, cog-r3088,
> > which I assume is largely from un-doing the inadvertent post-0.92
> > merge from trunk?
> >
> > - Mike
> >
> >
> >
> >
> > ----- Original Message -----
> > > That would be a tag and we'd do it after we test the current code in
> > > the
> > > branch a bit.
> > >
> > > On Sun, 2011-04-03 at 13:16 -0500, Michael Wilde wrote:
> > > > Nice - thank you, Mihael! Can you make the branch next? Call it
> > > > 0.92.1 or .2, whatever you think is best practice (I favor 0.92.1
> > > > but have no strong feeling).
> > > >
> > > > - Mike
> > > >
> > > > ----- Original Message -----
> > > > > On Thu, 2011-03-31 at 11:52 -0700, Mihael Hategan wrote:
> > > > > > We decided the following:
> > > > > > - I will revert the changes in the 0.92 branch
> > > > >
> > > > > done
> > > > >
> > > > > > - re-commit bug fixes that were committed after the merge
> > > > >
> > > > > done
> > > > >
> > > > > > - merge the 0.92 branch to trunk
> > > > >
> > > > > done
> > > > >
> > > > > > - fix the problems in trunk
> > > > >
> > > > > and done except the problem was in the branch. I think it was a
> > > > > manual
> > > > > merge of mine gone wrong. Trunk should be clean.
> > > > >
> > > > > We should make a patch release.
> > > > >
> > > > > Mihael
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Swift-devel mailing list
> > > > > Swift-devel at ci.uchicago.edu
> > > > > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> > > >
> >
> >
> > --
> > Michael Wilde
> > Computation Institute, University of Chicago
> > Mathematics and Computer Science Division
> > Argonne National Laboratory
> >
> > _______________________________________________
> >
> >
> >
> > Swift-devel mailing list
> > Swift-devel at ci.uchicago.edu
> > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> >
> >
> >
> > --
> > Any intelligent fool can make things bigger and more complex... It
> > takes a touch of genius - and a lot of courage to move in the opposite
> > direction.
> > - Albert Einstein
>
> --
> Michael Wilde
> Computation Institute, University of Chicago
> Mathematics and Computer Science Division
> Argonne National Laboratory
>
>
--
Any intelligent fool can make things bigger and more complex... It takes a
touch of genius - and a lot of courage to move in the opposite direction.
- Albert Einstein
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From hategan at mcs.anl.gov Sun Apr 3 23:53:57 2011
From: hategan at mcs.anl.gov (Mihael Hategan)
Date: Sun, 03 Apr 2011 21:53:57 -0700
Subject: [Swift-devel] duplicated job submission in swift-0.92?
In-Reply-To: <1959342990.59362.1301890898256.JavaMail.root@zimbra.anl.gov>
References: <1959342990.59362.1301890898256.JavaMail.root@zimbra.anl.gov>
Message-ID: <1301892837.19399.0.camel@blabla2.none>
On Sun, 2011-04-03 at 23:21 -0500, Michael Wilde wrote:
> Ive tried the failing examples on a fresh checkout of the 0.92 branch, and that works now - excellent.
>
> Allan and Jon, can you try your scripts on this latest 0.92 from svn?
>
> Ive also re-built the 0.92 version with Cray support. That seems to work as well.
>
> When I updated my 0.92 branch I jumped to: swift-r4252, cog-r3088,
> which I assume is largely from un-doing the inadvertent post-0.92
> merge from trunk?
Yes. Svn revisions are monotonic in time.
>
> - Mike
>
> ----- Original Message -----
> > That would be a tag and we'd do it after we test the current code in
> > the
> > branch a bit.
> >
> > On Sun, 2011-04-03 at 13:16 -0500, Michael Wilde wrote:
> > > Nice - thank you, Mihael! Can you make the branch next? Call it
> > > 0.92.1 or .2, whatever you think is best practice (I favor 0.92.1
> > > but have no strong feeling).
> > >
> > > - Mike
> > >
> > > ----- Original Message -----
> > > > On Thu, 2011-03-31 at 11:52 -0700, Mihael Hategan wrote:
> > > > > We decided the following:
> > > > > - I will revert the changes in the 0.92 branch
> > > >
> > > > done
> > > >
> > > > > - re-commit bug fixes that were committed after the merge
> > > >
> > > > done
> > > >
> > > > > - merge the 0.92 branch to trunk
> > > >
> > > > done
> > > >
> > > > > - fix the problems in trunk
> > > >
> > > > and done except the problem was in the branch. I think it was a
> > > > manual
> > > > merge of mine gone wrong. Trunk should be clean.
> > > >
> > > > We should make a patch release.
> > > >
> > > > Mihael
> > > >
> > > >
> > > > _______________________________________________
> > > > Swift-devel mailing list
> > > > Swift-devel at ci.uchicago.edu
> > > > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> > >
>
From jon.monette at gmail.com Mon Apr 4 00:04:39 2011
From: jon.monette at gmail.com (Jonathan Monette)
Date: Mon, 4 Apr 2011 00:04:39 -0500
Subject: [Swift-devel] duplicated job submission in swift-0.92?
In-Reply-To: <1301892837.19399.0.camel@blabla2.none>
References: <1959342990.59362.1301890898256.JavaMail.root@zimbra.anl.gov>
<1301892837.19399.0.camel@blabla2.none>
Message-ID:
My small workflow finished without error and was faster than what trunk was
doing(maybe had something to do with the twice foreach loop). Running my
largest workflow to see what happens. But seems to be working fine.
On Sun, Apr 3, 2011 at 11:53 PM, Mihael Hategan wrote:
> On Sun, 2011-04-03 at 23:21 -0500, Michael Wilde wrote:
> > Ive tried the failing examples on a fresh checkout of the 0.92 branch,
> and that works now - excellent.
> >
> > Allan and Jon, can you try your scripts on this latest 0.92 from svn?
> >
> > Ive also re-built the 0.92 version with Cray support. That seems to work
> as well.
> >
> > When I updated my 0.92 branch I jumped to: swift-r4252, cog-r3088,
> > which I assume is largely from un-doing the inadvertent post-0.92
> > merge from trunk?
>
> Yes. Svn revisions are monotonic in time.
>
> >
> > - Mike
> >
> > ----- Original Message -----
> > > That would be a tag and we'd do it after we test the current code in
> > > the
> > > branch a bit.
> > >
> > > On Sun, 2011-04-03 at 13:16 -0500, Michael Wilde wrote:
> > > > Nice - thank you, Mihael! Can you make the branch next? Call it
> > > > 0.92.1 or .2, whatever you think is best practice (I favor 0.92.1
> > > > but have no strong feeling).
> > > >
> > > > - Mike
> > > >
> > > > ----- Original Message -----
> > > > > On Thu, 2011-03-31 at 11:52 -0700, Mihael Hategan wrote:
> > > > > > We decided the following:
> > > > > > - I will revert the changes in the 0.92 branch
> > > > >
> > > > > done
> > > > >
> > > > > > - re-commit bug fixes that were committed after the merge
> > > > >
> > > > > done
> > > > >
> > > > > > - merge the 0.92 branch to trunk
> > > > >
> > > > > done
> > > > >
> > > > > > - fix the problems in trunk
> > > > >
> > > > > and done except the problem was in the branch. I think it was a
> > > > > manual
> > > > > merge of mine gone wrong. Trunk should be clean.
> > > > >
> > > > > We should make a patch release.
> > > > >
> > > > > Mihael
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Swift-devel mailing list
> > > > > Swift-devel at ci.uchicago.edu
> > > > > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> > > >
> >
>
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>
--
Any intelligent fool can make things bigger and more complex... It takes a
touch of genius - and a lot of courage to move in the opposite direction.
- Albert Einstein
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From wilde at mcs.anl.gov Mon Apr 4 13:51:37 2011
From: wilde at mcs.anl.gov (Michael Wilde)
Date: Mon, 4 Apr 2011 13:51:37 -0500 (CDT)
Subject: [Swift-devel] prelim instructions for asciidoc?
Message-ID: <1519782816.62044.1301943097680.JavaMail.root@zimbra.anl.gov>
Justin, do you have any preliminary instructions for running asciidoc in some simple standalone fashion so people can start to try it?
Not a priority, but if you have prelim tools set up or even identified, we can get a jump start on writing, conversion and gathering of material.
Im thinking that a first step can be grabbing cookbook items or email fragments and getting their text into SVN into a doc/inprogress dir while we coerce each small section into asciidoc.
- Mike
From wozniak at mcs.anl.gov Mon Apr 4 14:19:23 2011
From: wozniak at mcs.anl.gov (Justin M Wozniak)
Date: Mon, 4 Apr 2011 14:19:23 -0500 (CDT)
Subject: [Swift-devel] Re: prelim instructions for asciidoc?
In-Reply-To: <1519782816.62044.1301943097680.JavaMail.root@zimbra.anl.gov>
References: <1519782816.62044.1301943097680.JavaMail.root@zimbra.anl.gov>
Message-ID:
My initial asciidoc notes are in:
https://svn.ci.uchicago.edu/svn/vdl2/test/asciidoc-manual
The output is up at:
http://www.mcs.anl.gov/~wozniak/manual.html
Justin
On Mon, 4 Apr 2011, Michael Wilde wrote:
> Justin, do you have any preliminary instructions for running asciidoc in
> some simple standalone fashion so people can start to try it?
>
> Not a priority, but if you have prelim tools set up or even identified,
> we can get a jump start on writing, conversion and gathering of
> material.
>
> Im thinking that a first step can be grabbing cookbook items or email
> fragments and getting their text into SVN into a doc/inprogress dir
> while we coerce each small section into asciidoc.
>
> - Mike
--
Justin M Wozniak
From wilde at mcs.anl.gov Mon Apr 4 15:06:46 2011
From: wilde at mcs.anl.gov (Michael Wilde)
Date: Mon, 4 Apr 2011 15:06:46 -0500 (CDT)
Subject: [Swift-devel] Re: Can you test 0.92 branch for 0.92.1 release?
In-Reply-To:
Message-ID: <1249515087.62581.1301947606402.JavaMail.root@zimbra.anl.gov>
Sounds good David. Ketan agreed he would test on Beagle.
Thanks,
Mike
----- Original Message -----
> No problem, I should have some time later tonight to re-run the
> provider tests on the CI/Argonne machines.
>
>
> David
>
>
> On Mon, Apr 4, 2011 at 2:52 PM, Sarah Kenny < skenny at uchicago.edu >
> wrote:
>
>
> today is pretty booked with uci stuff but i can give this my full
> attention tomorrow if that will work. i can take abe, ranger and also
> test on local workstations if you want to take ci/argonne machines
> david (?) or suggest something else if you like.
>
>
>
> On Mon, Apr 4, 2011 at 11:42 AM, Michael Wilde < wilde at mcs.anl.gov >
> wrote:
>
>
> David, Sarah,
>
> How quickly could you re-divide the Swift site test plan between you
> and confirm back to swift-devel that we are ready to tag and release
> the branch as 0.92.1?
>
> Before we do that, you need to add a test to the test suite that can
> replicate the twice-each bug and verify that its detected in 0.92 and
> corrected in 0.92.1
>
> Can you possibly do this by noon tomorrow?
>
> Can you post a checklist of tests with names of who's going to run
> them?
>
>
> given that this is floating around now in 2 different forms, can we
> agree on a single location? (for sanity's sake :P)
>
> https://sites.google.com/site/swiftdevel/site-specific-testing
>
> http://www.ci.uchicago.edu/wiki/bin/view/SWFT/ReleasePlans#developer_notes
>
>
>
>
>
>
> Depending on what you can commit to, I will see if I, Ketan, and/or
> Justin can help take various sites as well. I feel we really need to
> do this quickly so we have a stable trusted release out there.
>
>
>
> Thanks,
>
> Mike
>
> --
> Michael Wilde
> Computation Institute, University of Chicago
> Mathematics and Computer Science Division
> Argonne National Laboratory
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
From ketan at mcs.anl.gov Mon Apr 4 15:40:57 2011
From: ketan at mcs.anl.gov (Ketan Maheshwari)
Date: Mon, 4 Apr 2011 15:40:57 -0500
Subject: [Swift-devel] Re: prelim instructions for asciidoc?
In-Reply-To:
References: <1519782816.62044.1301943097680.JavaMail.root@zimbra.anl.gov>
Message-ID: <873283AE-B549-43C0-963A-154291A47E2F@mcs.anl.gov>
Justin,
Is asciidoc pre-installed somewhere or it needs to be installed?
Ketan
On Apr 4, 2011, at 2:19 PM, Justin M Wozniak wrote:
>
> My initial asciidoc notes are in:
>
> https://svn.ci.uchicago.edu/svn/vdl2/test/asciidoc-manual
>
> The output is up at:
>
> http://www.mcs.anl.gov/~wozniak/manual.html
>
> Justin
>
> On Mon, 4 Apr 2011, Michael Wilde wrote:
>
>> Justin, do you have any preliminary instructions for running asciidoc in some simple standalone fashion so people can start to try it?
>>
>> Not a priority, but if you have prelim tools set up or even identified, we can get a jump start on writing, conversion and gathering of material.
>>
>> Im thinking that a first step can be grabbing cookbook items or email fragments and getting their text into SVN into a doc/inprogress dir while we coerce each small section into asciidoc.
>>
>> - Mike
>
> --
> Justin M Wozniak
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
From wozniak at mcs.anl.gov Mon Apr 4 15:53:23 2011
From: wozniak at mcs.anl.gov (Justin M Wozniak)
Date: Mon, 4 Apr 2011 15:53:23 -0500 (CDT)
Subject: [Swift-devel] Re: prelim instructions for asciidoc?
In-Reply-To: <873283AE-B549-43C0-963A-154291A47E2F@mcs.anl.gov>
References: <1519782816.62044.1301943097680.JavaMail.root@zimbra.anl.gov>
<873283AE-B549-43C0-963A-154291A47E2F@mcs.anl.gov>
Message-ID:
It needs to be installed.
Justin
On Mon, 4 Apr 2011, Ketan Maheshwari wrote:
> Justin,
>
> Is asciidoc pre-installed somewhere or it needs to be installed?
>
> Ketan
>
> On Apr 4, 2011, at 2:19 PM, Justin M Wozniak wrote:
>
>>
>> My initial asciidoc notes are in:
>>
>> https://svn.ci.uchicago.edu/svn/vdl2/test/asciidoc-manual
>>
>> The output is up at:
>>
>> http://www.mcs.anl.gov/~wozniak/manual.html
>>
>> Justin
>>
>> On Mon, 4 Apr 2011, Michael Wilde wrote:
>>
>>> Justin, do you have any preliminary instructions for running asciidoc
>>> in some simple standalone fashion so people can start to try it?
>>>
>>> Not a priority, but if you have prelim tools set up or even
>>> identified, we can get a jump start on writing, conversion and
>>> gathering of material.
>>>
>>> Im thinking that a first step can be grabbing cookbook items or email
>>> fragments and getting their text into SVN into a doc/inprogress dir
>>> while we coerce each small section into asciidoc.
>>>
>>> - Mike
>>
>> --
>> Justin M Wozniak
>> _______________________________________________
>> Swift-devel mailing list
>> Swift-devel at ci.uchicago.edu
>> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>
>
--
Justin M Wozniak
From wilde at mcs.anl.gov Mon Apr 4 15:58:02 2011
From: wilde at mcs.anl.gov (Michael Wilde)
Date: Mon, 4 Apr 2011 15:58:02 -0500 (CDT)
Subject: [Swift-devel] Re: prelim instructions for asciidoc?
In-Reply-To:
Message-ID: <1452296610.62943.1301950682895.JavaMail.root@zimbra.anl.gov>
This looks like a good example of a technical site built almost entirely with asciidoc:
http://www.networkupstools.org/index.html
- Mike
----- Original Message -----
> It needs to be installed.
> Justin
>
> On Mon, 4 Apr 2011, Ketan Maheshwari wrote:
>
> > Justin,
> >
> > Is asciidoc pre-installed somewhere or it needs to be installed?
> >
> > Ketan
> >
> > On Apr 4, 2011, at 2:19 PM, Justin M Wozniak wrote:
> >
> >>
> >> My initial asciidoc notes are in:
> >>
> >> https://svn.ci.uchicago.edu/svn/vdl2/test/asciidoc-manual
> >>
> >> The output is up at:
> >>
> >> http://www.mcs.anl.gov/~wozniak/manual.html
> >>
> >> Justin
> >>
> >> On Mon, 4 Apr 2011, Michael Wilde wrote:
> >>
> >>> Justin, do you have any preliminary instructions for running
> >>> asciidoc
> >>> in some simple standalone fashion so people can start to try it?
> >>>
> >>> Not a priority, but if you have prelim tools set up or even
> >>> identified, we can get a jump start on writing, conversion and
> >>> gathering of material.
> >>>
> >>> Im thinking that a first step can be grabbing cookbook items or
> >>> email
> >>> fragments and getting their text into SVN into a doc/inprogress
> >>> dir
> >>> while we coerce each small section into asciidoc.
> >>>
> >>> - Mike
> >>
> >> --
> >> Justin M Wozniak
> >> _______________________________________________
> >> Swift-devel mailing list
> >> Swift-devel at ci.uchicago.edu
> >> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> >
> >
>
> --
> Justin M Wozniak
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
From wilde at mcs.anl.gov Mon Apr 4 16:12:13 2011
From: wilde at mcs.anl.gov (Michael Wilde)
Date: Mon, 4 Apr 2011 16:12:13 -0500 (CDT)
Subject: [Swift-devel] Re: prelim instructions for asciidoc?
In-Reply-To:
Message-ID: <310355473.63032.1301951533351.JavaMail.root@zimbra.anl.gov>
wow, that was easy!
$ wget http://sourceforge.net/projects/asciidoc/files/asciidoc/8.6.4/asciidoc-8.6.4.tar.gz/download
$ tar -xzf asciidoc-8.6.4.tar.gz
$ cd asciidoc-8.6.4
$ ./configure --prefix $HOME/asciidoc
$ make install
$ PATH=$PATH:$HOME/asciidoc/bin
$ asciidoc manual.txt # creates manual.html
- Mike
----- Original Message -----
> It needs to be installed.
> Justin
>
> On Mon, 4 Apr 2011, Ketan Maheshwari wrote:
>
> > Justin,
> >
> > Is asciidoc pre-installed somewhere or it needs to be installed?
> >
> > Ketan
> >
> > On Apr 4, 2011, at 2:19 PM, Justin M Wozniak wrote:
> >
> >>
> >> My initial asciidoc notes are in:
> >>
> >> https://svn.ci.uchicago.edu/svn/vdl2/test/asciidoc-manual
> >>
> >> The output is up at:
> >>
> >> http://www.mcs.anl.gov/~wozniak/manual.html
> >>
> >> Justin
> >>
> >> On Mon, 4 Apr 2011, Michael Wilde wrote:
> >>
> >>> Justin, do you have any preliminary instructions for running
> >>> asciidoc
> >>> in some simple standalone fashion so people can start to try it?
> >>>
> >>> Not a priority, but if you have prelim tools set up or even
> >>> identified, we can get a jump start on writing, conversion and
> >>> gathering of material.
> >>>
> >>> Im thinking that a first step can be grabbing cookbook items or
> >>> email
> >>> fragments and getting their text into SVN into a doc/inprogress
> >>> dir
> >>> while we coerce each small section into asciidoc.
> >>>
> >>> - Mike
> >>
> >> --
> >> Justin M Wozniak
> >> _______________________________________________
> >> Swift-devel mailing list
> >> Swift-devel at ci.uchicago.edu
> >> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> >
> >
>
> --
> Justin M Wozniak
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
From ketan at mcs.anl.gov Mon Apr 4 16:19:57 2011
From: ketan at mcs.anl.gov (Ketan Maheshwari)
Date: Mon, 4 Apr 2011 16:19:57 -0500
Subject: [Swift-devel] Re: prelim instructions for asciidoc?
In-Reply-To: <310355473.63032.1301951533351.JavaMail.root@zimbra.anl.gov>
References: <310355473.63032.1301951533351.JavaMail.root@zimbra.anl.gov>
Message-ID: <28F22E08-2153-4211-A413-5EA97117543F@mcs.anl.gov>
And,
asciidoc -n manual.txt #creates manual.html with section numbers :-)
Ketan
On Apr 4, 2011, at 4:12 PM, Michael Wilde wrote:
> wow, that was easy!
>
> $ wget http://sourceforge.net/projects/asciidoc/files/asciidoc/8.6.4/asciidoc-8.6.4.tar.gz/download
> $ tar -xzf asciidoc-8.6.4.tar.gz
> $ cd asciidoc-8.6.4
> $ ./configure --prefix $HOME/asciidoc
> $ make install
> $ PATH=$PATH:$HOME/asciidoc/bin
> $ asciidoc manual.txt # creates manual.html
>
> - Mike
>
> ----- Original Message -----
>> It needs to be installed.
>> Justin
>>
>> On Mon, 4 Apr 2011, Ketan Maheshwari wrote:
>>
>>> Justin,
>>>
>>> Is asciidoc pre-installed somewhere or it needs to be installed?
>>>
>>> Ketan
>>>
>>> On Apr 4, 2011, at 2:19 PM, Justin M Wozniak wrote:
>>>
>>>>
>>>> My initial asciidoc notes are in:
>>>>
>>>> https://svn.ci.uchicago.edu/svn/vdl2/test/asciidoc-manual
>>>>
>>>> The output is up at:
>>>>
>>>> http://www.mcs.anl.gov/~wozniak/manual.html
>>>>
>>>> Justin
>>>>
>>>> On Mon, 4 Apr 2011, Michael Wilde wrote:
>>>>
>>>>> Justin, do you have any preliminary instructions for running
>>>>> asciidoc
>>>>> in some simple standalone fashion so people can start to try it?
>>>>>
>>>>> Not a priority, but if you have prelim tools set up or even
>>>>> identified, we can get a jump start on writing, conversion and
>>>>> gathering of material.
>>>>>
>>>>> Im thinking that a first step can be grabbing cookbook items or
>>>>> email
>>>>> fragments and getting their text into SVN into a doc/inprogress
>>>>> dir
>>>>> while we coerce each small section into asciidoc.
>>>>>
>>>>> - Mike
>>>>
>>>> --
>>>> Justin M Wozniak
>>>> _______________________________________________
>>>> Swift-devel mailing list
>>>> Swift-devel at ci.uchicago.edu
>>>> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>>>
>>>
>>
>> --
>> Justin M Wozniak
>
> --
> Michael Wilde
> Computation Institute, University of Chicago
> Mathematics and Computer Science Division
> Argonne National Laboratory
>
From ketancmaheshwari at gmail.com Mon Apr 4 16:36:10 2011
From: ketancmaheshwari at gmail.com (Ketan Maheshwari)
Date: Mon, 4 Apr 2011 16:36:10 -0500
Subject: [Swift-devel] Re: prelim instructions for asciidoc?
In-Reply-To: <28F22E08-2153-4211-A413-5EA97117543F@mcs.anl.gov>
References: <310355473.63032.1301951533351.JavaMail.root@zimbra.anl.gov>
<28F22E08-2153-4211-A413-5EA97117543F@mcs.anl.gov>
Message-ID: <913F7D8C-3B8A-43A0-A028-4540E477409A@gmail.com>
Hi,
asciidoc -a toc -n manual.txt # toc + numbered sections
Ketan
On Apr 4, 2011, at 4:19 PM, Ketan Maheshwari wrote:
> And,
>
> asciidoc -n manual.txt #creates manual.html with section numbers :-)
>
> Ketan
>
> On Apr 4, 2011, at 4:12 PM, Michael Wilde wrote:
>
>> wow, that was easy!
>>
>> $ wget http://sourceforge.net/projects/asciidoc/files/asciidoc/8.6.4/asciidoc-8.6.4.tar.gz/download
>> $ tar -xzf asciidoc-8.6.4.tar.gz
>> $ cd asciidoc-8.6.4
>> $ ./configure --prefix $HOME/asciidoc
>> $ make install
>> $ PATH=$PATH:$HOME/asciidoc/bin
>> $ asciidoc manual.txt # creates manual.html
>>
>> - Mike
>>
>> ----- Original Message -----
>>> It needs to be installed.
>>> Justin
>>>
>>> On Mon, 4 Apr 2011, Ketan Maheshwari wrote:
>>>
>>>> Justin,
>>>>
>>>> Is asciidoc pre-installed somewhere or it needs to be installed?
>>>>
>>>> Ketan
>>>>
>>>> On Apr 4, 2011, at 2:19 PM, Justin M Wozniak wrote:
>>>>
>>>>>
>>>>> My initial asciidoc notes are in:
>>>>>
>>>>> https://svn.ci.uchicago.edu/svn/vdl2/test/asciidoc-manual
>>>>>
>>>>> The output is up at:
>>>>>
>>>>> http://www.mcs.anl.gov/~wozniak/manual.html
>>>>>
>>>>> Justin
>>>>>
>>>>> On Mon, 4 Apr 2011, Michael Wilde wrote:
>>>>>
>>>>>> Justin, do you have any preliminary instructions for running
>>>>>> asciidoc
>>>>>> in some simple standalone fashion so people can start to try it?
>>>>>>
>>>>>> Not a priority, but if you have prelim tools set up or even
>>>>>> identified, we can get a jump start on writing, conversion and
>>>>>> gathering of material.
>>>>>>
>>>>>> Im thinking that a first step can be grabbing cookbook items or
>>>>>> email
>>>>>> fragments and getting their text into SVN into a doc/inprogress
>>>>>> dir
>>>>>> while we coerce each small section into asciidoc.
>>>>>>
>>>>>> - Mike
>>>>>
>>>>> --
>>>>> Justin M Wozniak
>>>>> _______________________________________________
>>>>> Swift-devel mailing list
>>>>> Swift-devel at ci.uchicago.edu
>>>>> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>>>>
>>>>
>>>
>>> --
>>> Justin M Wozniak
>>
>> --
>> Michael Wilde
>> Computation Institute, University of Chicago
>> Mathematics and Computer Science Division
>> Argonne National Laboratory
>>
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
From bugzilla-daemon at mcs.anl.gov Mon Apr 4 22:21:12 2011
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Mon, 4 Apr 2011 22:21:12 -0500 (CDT)
Subject: [Swift-devel] [Bug 319] New: Set logging level via swift.properties
to a few pre-defined levels
Message-ID:
https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=319
Summary: Set logging level via swift.properties to a few
pre-defined levels
Product: Swift
Version: 0.93
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: Log processing and plotting
AssignedTo: wozniak at mcs.anl.gov
ReportedBy: wilde at mcs.anl.gov
Implement log properties of fast, info, normal, debug, trace (or similar, much
like coaster worker.pl)
fast - very light logging, for performance research
info - lighter than normal logging
normal - a log level that doesnt degrade performance much, tells the user
everything they need, and is sufficient to drive all features including
provenance, Text User Interface (-tui option) and performance plotting
- debug - supports most debugging needed
- trace - for only the most detailed level of debugging
The current log4j control mechanism should be used only for fine grained
developer control.
--
Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the reporter.
From wilde at mcs.anl.gov Mon Apr 4 22:23:34 2011
From: wilde at mcs.anl.gov (Michael Wilde)
Date: Mon, 4 Apr 2011 22:23:34 -0500 (CDT)
Subject: [Swift-devel] Re: Google Summer of Code Application
In-Reply-To:
Message-ID: <135804436.64241.1301973814929.JavaMail.root@zimbra.anl.gov>
Dear Ashish,
I suggest project #1 below, the integration of Swift into Globus Online.
Swift Bugzilla is located at https://bugzilla.mcs.anl.gov/swift/
I'll try to locate a bug to work on. Are you familiar with log4j? We need to encode useful sets of log4j processing options as a set of simple log levels settable as a swift property.
Ive just filed this as:
Bug 319 - Set logging level via swift.properties to a few pre-defined levels
Justin or Mihael may want to comment on this.
But feel free to peruse bugzilla for something else suitable to tackle.
- Mike
----- Original Message -----
> Respected Sir,
>
> I know that i am extremely late in starting this conversation, but i
> have just got free from my exams and other commitments
> I am a 4 th year undergraduate student of the computer science
> department from Indian Institute of Technology,Delhi.
>
> I am interested in the following two projects from your project ideas.
>
> 1. Integrate swift with Globus Online to provide an application
> execution and scripting interface.
> 2. Implementing efficient map-reduce models using swift parallel
> programming.
>
> A small description of my skills relevant to the two projects are
> - Experience of Bash Scripting and python scripting.I have extensively
> used bash scripting.
> - Basic understanding of REST. During an intern at Netapp, Bangalore,
> I was required to use SOAP for my work.
> - Experience of working with map reduce and running hadoop
> programs(You can have a look at one of the assignments that i did in
> my course on cloud computing and virtualziation
> http://www.cse.iitd.ernet.in/~sbansal/csl862/pa3/ ).
> - Experience of writing programs in java.I have for my courses
> extensively used java.
>
>
> I will like you to kindly tell me, which of these two projects would
> you like me to focus on, for my gsoc application.Also the gsoc
> application template mentions that we should try and fix bugs or
> provide some feedback on how a bug should be fixed. Could you tell me
> about any specific bug that I should focus on, in order to demonstrate
> my coding competence?
>
> Regards
> Ashish
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
From bugzilla-daemon at mcs.anl.gov Mon Apr 4 22:26:34 2011
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Mon, 4 Apr 2011 22:26:34 -0500 (CDT)
Subject: [Swift-devel] [Bug 319] Set logging level via swift.properties to a
few pre-defined levels
In-Reply-To:
References:
Message-ID: <20110405032634.0D3E21C073@wind.mcs.anl.gov>
https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=319
--- Comment #1 from Michael Wilde 2011-04-04 22:26:33 ---
add nice timestamps to stdout log - hh:mm:ss (currently is a simple integer per
a recent fix by Mihael)
same log record as is sent to stdout should occur in detailed log for
corss-referencing
--
Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the reporter.
From bugzilla-daemon at mcs.anl.gov Tue Apr 5 10:25:02 2011
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Tue, 5 Apr 2011 10:25:02 -0500 (CDT)
Subject: [Swift-devel] [Bug 321] New: Improve "cant find wrapper log" error
message and document in new Debugging chapter
Message-ID:
https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=321
Summary: Improve "cant find wrapper log" error message and
document in new Debugging chapter
Product: Swift
Version: 0.93
Platform: All
OS/Version: All
Status: ASSIGNED
Severity: major
Priority: P1
Component: error messages
AssignedTo: skenny at uchicago.edu
ReportedBy: wilde at mcs.anl.gov
This bug is filed to deal specifically with the very frequent error message
that is perplexing a new Swift user in the message I cc below. I think we
should do several specific things in response. I mark this high prio because
erros very similar to this one are probably the highest cause of Swift
problems, confusion, and frustration for new users.
1. Reword the message "failed to transfer wrapper log" to say what it means
2. Document the process of where to look for issues causing this.
3. More clearly document the tag, how and when to use it, and how it
affects debugging. Stress that its a performance enhancement that inhibits
debugging and should not be used until a workflow is stable. (Note that in
this case the user put scratch on the home filesystem which defeats the
purpose. Im not sure f this caused a failure; I think not, but would be good to
verify. This should not be in our basic templates, although this user didnt
use gensites.
4. Work through the common cases of app-not-found, app-not-executable,
app-encoutered-an-error (signal or non-zero exit) and app-didnt-return-expected
files. Maybe I missed a few cases, but these are the main ones. Each one
should be *instantly* recognizable, and ideally we should report all these in
plain clear English that enables the user to fix them instantly.
5. Review this email thread for anything I missed in either debugging or
documentation.
The results of fixing this bug should be:
- better error messages for the above cases
- the start of a user guide section on Debugging (use asciidoc; a new
standalobg doc that becomes a user guide chapter is fine for now).
- Mike
Hi Weiyang,
I'm cc'ing this to swift-user, where you should send all questions, so that
other Swift developers and users can offer help as well, and all users can
learn from the answers.
Its hard for me to debug this without seeing your .swift script and your log
file.
The error message means: Swift tried to run a batch job to execute an app()
call, and the attempt did not even return the per-job log file (the "wrapper
log") from the execution site (ie what you defined in your pool entry).
First, please comment out the tag. Thats an optimization and may be
confusing things (or may even be cause of the error, but that is less likely).
The most likely cause of the problem here is that your application "touch" is
listed in your tc under the wrong pathname: touch is /bin/touch, not /usr/bin.
The best way to get a sense of how far your script progressed is to do a full
"find" under your swiftwork directory from the directory for the failing run id
(test-20110405-0940-rqa4nyka), and see what is there.
The shared/ directory should contain whatever input files were processed. If
you did not use the tag, then there should also be a "job directory"
for each app swift tried to run. This is described in the user guide.
Since these were not present, I concluded that Swift could not execute your
application.
The Swift team is working to improve both these messages and the documentation
for debugging such situations to make this much easier to spot.
Also, I dont know how far your workflow ran the previous time, but thus looks
like a large run. You should test new workflows (or even any changes you make)
on very small runs first, so that there are fewer files and parallel jobs to
sort through when debugging new scripts.
- Mike
----- Original Message -----
> Hello,
>
>
> My swift codes just encountered new problems: After submitted jobs
> using foreach it's saying
>
>
> Failed to transfer wrapper log from test-20110405-0940-rqa4nyka/info/u
> on pbs
>
>
> My guess is there're sth wrong with pbs (the execution provider)
>
>
> My sites.xml and tc.data is exactly kept the same since last time you
> advised
>
>
> sites.xml:
>
>
>
>
>
>
> 1:00:00
> 8
> 8
>
> 1
> 1
> 1.99
> 10000
> CI-SES000031
>
>
> /home/frankwang/tmp
> /home/frankwang/swiftwork
>
>
>
>
>
> pbs echo /bin/echo INSTALLED INTEL32::LINUX null
> pbs sh /bin/bash INSTALLED INTEL32::LINUX null
> pbs touch /usr/bin/touch INSTALLED INTEL32::LINUX
> GLOBUS::maxwalltime="0:1"
>
>
> The same problem occured when I was using various version of swift.
>
>
> Can you take a time to figure it out?
>
>
> Weiyang
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
--
Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the reporter.
From bugzilla-daemon at mcs.anl.gov Tue Apr 5 10:27:25 2011
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Tue, 5 Apr 2011 10:27:25 -0500 (CDT)
Subject: [Swift-devel] [Bug 321] Improve "cant find wrapper log" error
message and document in new Debugging chapter
In-Reply-To:
References:
Message-ID: <20110405152725.266B21C073@wind.mcs.anl.gov>
https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=321
--- Comment #1 from Michael Wilde 2011-04-05 10:27:24 ---
Please follow this email thread through to resolution for any other message and
documentation needed:
http://mail.ci.uchicago.edu/pipermail/swift-user/2011-April/001909.html
Both the problem and the expertise level of this user are "just right" to
better understand what most users with only moderate computing skills need in
order to succeed with Swift.
--
Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the reporter.
From wilde at mcs.anl.gov Tue Apr 5 10:45:23 2011
From: wilde at mcs.anl.gov (Michael Wilde)
Date: Tue, 5 Apr 2011 10:45:23 -0500 (CDT)
Subject: [Swift-devel] Fwd: [Bug 321] Improve "cant find wrapper log" error
message and document in new Debugging chapter
In-Reply-To: <20110405152725.2D9751C074@wind.mcs.anl.gov>
Message-ID: <1105880808.65692.1302018323354.JavaMail.root@zimbra.anl.gov>
Sarah, I assigned you this bug because I think its an ideal place to get started on the error message and debugability-improvement project.
So after you complete the testing for 0.92.1, can you shift your focus to this? You will need to discuss on the list how to break the work down into smaller pieces and likely discuss the questions that come up.
I think you should immediately on starting create a new debugging.txt asciidoc User Guide section, which you can develop standalone until the asciidoc effort is far enough along to manage chapters as separate files.
If there's anything else on your to-do list for 0.93, we can discuss in tomorrows developer phone call how to prioritize the work.
Does this sound like a good way to dive into the message-improvement project?
- Mike
----- Forwarded Message -----
From: bugzilla-daemon at mcs.anl.gov
To: wilde at mcs.anl.gov
Sent: Tuesday, April 5, 2011 10:27:25 AM
Subject: [Bug 321] Improve "cant find wrapper log" error message and document in new Debugging chapter
https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=321
--- Comment #1 from Michael Wilde 2011-04-05 10:27:24 ---
Please follow this email thread through to resolution for any other message and
documentation needed:
http://mail.ci.uchicago.edu/pipermail/swift-user/2011-April/001909.html
Both the problem and the expertise level of this user are "just right" to
better understand what most users with only moderate computing skills need in
order to succeed with Swift.
--
Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You reported the bug.
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
From bugzilla-daemon at mcs.anl.gov Tue Apr 5 10:51:48 2011
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Tue, 5 Apr 2011 10:51:48 -0500 (CDT)
Subject: [Swift-devel] [Bug 289] Add mechanism to delete temporary files no
longer in scope
In-Reply-To:
References:
Message-ID: <20110405155148.9B9F61C073@wind.mcs.anl.gov>
https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=289
Michael Wilde changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
AssignedTo|hategan at mcs.anl.gov |wozniak at mcs.anl.gov
Target Milestone|--- |v0.93
--- Comment #1 from Michael Wilde 2011-04-05 10:51:48 ---
Justin, please add your proposal for this feature here.
Mihael, please review and comment, and advise Justin on code paths as needed.
--
Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching the reporter.
From dennis at ucar.edu Tue Apr 5 10:59:23 2011
From: dennis at ucar.edu (John Dennis)
Date: Tue, 5 Apr 2011 09:59:23 -0600
Subject: [Swift-devel] [Bug 291] New: Add a exists() function to test
for file existence
In-Reply-To:
References: <729744535.55640.1301680289613.JavaMail.root@zimbra.anl.gov>
<2A5A416A-CAB6-4D82-B55F-0CFBC8F3B770@ucar.edu>
Message-ID:
Justin,
Thanks for adding this feature. I not currently setup on a system
with the swift trunk. I suspect Sheri is currently work
with the trunk. Sheri, could you take a look at this feature during
your work with swift?
Thanks,
John
On Apr 3, 2011, at 3:56 PM, Justin M Wozniak wrote:
>
> Ok, John, you can give this a try in trunk if you like. The syntax
> for the built-in is @exists, it takes a string and returns a boolean.
> Justin
>
> On Sat, 2 Apr 2011, Justin M Wozniak wrote:
>
>>
>> I have a prototype of this, I'll get it checked in later today.
>> Justin
>>
>> On Fri, 1 Apr 2011, John Dennis wrote:
>>
>>> Michael,
>>>
>>> This type of function would be great to have.
>>> John
>>> On Apr 1, 2011, at 11:51 AM, Michael Wilde wrote:
>>>> Basically as far as I understand: the presence or absence of a
>>>> particular data file within the inout dataset is to be used to
>>>> determine whether the code to process that dataset subsection
>>>> gets invoked or not:
>>>> if (exists("extra.data")) {
>>>> DataFile extraInput<"extra.data">;
>>>> extraResult = analyze(extraInput);
>>>> }
>>>> The above is my assumption based on a phone call. We can and
>>>> should verify the assumption with a simple example.
>>>> I also thought we can try this today by seeing if extraInput can
>>>> be an array, mapped to zero items if nothing to do and 1 item if
>>>> something to do. That would at least let us test the use case.
>>>> John, can you verify if the example Swift lines above are what
>>>> you are looking for here?
>>>> - Mike
>>>> ----- Original Message -----
>>>>> On Fri, 2011-04-01 at 10:51 -0500, Michael Wilde wrote:
>>>>>> - we should first verify that exists() will solve the NCAR need
>>>>>> in a
>>>>>> sufficiently clean way
>>>>> I think this is important. Can we get a description of the problem
>>>>> instead of a (otherwise) random proposal for a solution?
>>>> --
>>>> Michael Wilde
>>>> Computation Institute, University of Chicago
>>>> Mathematics and Computer Science Division
>>>> Argonne National Laboratory
>>> _______________________________________________
>>> Swift-devel mailing list
>>> Swift-devel at ci.uchicago.edu
>>> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>>
>>
>
> --
> Justin M Wozniak
From wilde at mcs.anl.gov Tue Apr 5 11:42:50 2011
From: wilde at mcs.anl.gov (Michael Wilde)
Date: Tue, 5 Apr 2011 11:42:50 -0500 (CDT)
Subject: [Swift-devel] Re: R library(ncdf) [PADS Support #12231]
In-Reply-To: <8AF6D68D-2A89-4EDC-878B-9BAB4C63E655@ci.uchicago.edu>
Message-ID: <370016820.65991.1302021770552.JavaMail.root@zimbra.anl.gov>
Hi Neil,
Thanks for the heads-up. No, I have never tried building R with ncdf.
The next 4 weeks are very busy for me as well with travel, workshops and proposals.
I'm sending to swift-devel as well as Rob and Sheri of the MCS Climate group to see if they have any info on building the netCDF package for R.
Regards,
Mike
----- Original Message -----
> Hi, Mike. Have you ever tried to install the ncdf package for R? I
> have a ticket open with Ti, but he seems to be having trouble with it.
> He thought he had it at one point (see below) but there was a problem
> -- I think he used the OS version of R. I'll send you my reply from
> when I tried to use what he had built. If you have any spare cycles
> for this in the interest of moving my SwiftR project forward over the
> next 2-3 weeks that would be great. I'll let you know if I hear
> anything from Ti. I'm not bugging him about it this week because I
> have my hands full and I think he's helping get ready for the Globus
> meeting, but I'm just trying to keep the issue alive. Thanks, Mike.
>
>
> Neil
>
>
> Begin forwarded message:
>
> > From: "Ti Leggett"
> > Date: March 28, 2011 12:42:58 PM CDT
> > To: nbest at ci.uchicago.edu
> > Subject: R library(ncdf) [PADS Support #12231]
> > Reply-To: pads-support at ci.uchicago.edu
> >
> > Bleh, accidentally hit comment instead of reply:
> >
> >
> > The magic command was this:
> > R CMD INSTALL -l /soft/R-ncdf-1.8-gcc4.1-r1/lib/R2.12/site-library
> > /software/common/src/ncdf_1.8.1.tar.gz
> > --configure-args="LDFLAGS='-L/soft/hdf5-1.8.2-gcc4.1-r1/lib -lhdf5
> > -lhdf5_hl' --with-netcdf_incdir=/soft/netcdf-4.0-gcc4.1-r1/include
> > --with-netcdf_libdir=/soft/netcdf-4.0-gcc4.1-r1/lib"
> >
> > Add the following to your .soft to use it:
> >
> > +netcdf-4.0-gcc4.1-r1
> > +szip-2.1-gcc4.1-r1
> > +hdf5-1.8.2-gcc4.1-r1
> > +R-ncdf-gcc-R2.12
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
From bugzilla-daemon at mcs.anl.gov Tue Apr 5 11:51:16 2011
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Tue, 5 Apr 2011 11:51:16 -0500 (CDT)
Subject: [Swift-devel] [Bug 323] New: Report status for, and document,
how to get Swift to
submit jobs meeting a site's scheduler constraints
Message-ID:
https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=323
Summary: Report status for, and document, how to get Swift to
submit jobs meeting a site's scheduler constraints
Product: Swift
Version: 1.0
Platform: All
OS/Version: All
Status: ASSIGNED
Severity: normal
Priority: P3
Component: Documentation
AssignedTo: ketan at mcs.anl.gov
ReportedBy: wilde at mcs.anl.gov
A user guide section on "How do I get Swift to submit jobs into a specific
queue, reservation, etc" would be useful.
This is the main reason that people initially deviate from coaster defaults
into more complex pool entries: to force jobs to fit into some site-imposed
constraint.
Ketan's experience reflected in the thread below, of not knowing why his job
didnt run, illustrates the need for both enhanced reporting and status from
Swift as well as documentation.
----- Original Message -----
> Ketan,
>
> No, your job 64063 is not eligible to run in the development
> reservation. You requested 5 nodes (mppwidth = 120), and the
> development reservation is limited to 3.
>
> If your job is less than 1 hour, and also less than 3 nodes (72 cores)
> than your job will run in this reservation.
>
> Jason Hedden
>
> On Apr 5, 2011, at 10:54 AM, Ketan Maheshwari wrote:
>
> > Jason,
> >
> > Is it possible to verify if my request (walltime is 49 minutes) went
> > to this "Development Reservation" queue.
> >
> > Ketan
> >
> > On Mar 23, 2011, at 10:26 AM, Jason Hedden wrote:
> >
> >> I've enabled the development reservation on Beagle. Monday through
> >> Friday between 8:00AM and 5:00PM 3 nodes are reserved for jobs that
> >> request less than 1 hour walltime. Similarly to PADS, no additional
> >> job parameters are required, any job that fits these requirements
> >> will run in the reservation.
> >>
> >> Jason Hedden
> >>
> >> On Mar 22, 2011, at 4:26 PM, Daniel S. Katz wrote:
> >>
> >>> I agree, we definitely want at least some small jobs to be able to
> >>> run quickly most of the time, at least during business hours on
> >>> weekdays.
> >>>
> >>> On Mar 23, 2011, at 2:29 AM, Lorenzo Pesce wrote:
> >>>
> >>>> Seems reasonable and useful to me.
> >>>>
> >>>> On Mar 22, 2011, at 1:12 PM, Ti Leggett wrote:
> >>>>
> >>>>> -----BEGIN PGP SIGNED MESSAGE-----
> >>>>> Hash: SHA1
> >>>>>
> >>>>> I think that decision will be based on what kinds of jobs we
> >>>>> want to favor, so I imagine in a few months when we convene to
> >>>>> make the policy decision.
> >>>>>
> >>>>> On Mar 22, 2011, at 1:11 PM, Michael Wilde wrote:
> >>>>>
> >>>>>> No objection: it sounds like a good idea.
> >>>>>>
> >>>>>> I can't recall, but are we also going to have a development or
> >>>>>> fast queue, or is the scheduler just going to treat requests as
> >>>>>> if smaller requests get higher priority?
> >>>>>>
> >>>>>> - Mike
> >>>>>>
> >>>>>> ----- Original Message -----
> >>>>>>> -----BEGIN PGP SIGNED MESSAGE-----
> >>>>>>> Hash: SHA1
> >>>>>>>
> >>>>>>> This was just brought up by a user. There's currently no easy
> >>>>>>> way for
> >>>>>>> a user to test out their code, especially an MPI code other
> >>>>>>> than to
> >>>>>>> submit an interactive job and wait for it to finally run. What
> >>>>>>> we do
> >>>>>>> on other clusters is have a development reservation during
> >>>>>>> "business"
> >>>>>>> hours, say 8:00am to 5:00pm for jobs an hour or less. Anyone
> >>>>>>> object to
> >>>>>>> putting aside 3 nodes for these types of jobs for people to be
> >>>>>>> able to
> >>>>>>> test code quickly?
> >>>>>>> -----BEGIN PGP SIGNATURE-----
> >>>>>>> Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
> >>>>>>>
> >>>>>>> iEYEARECAAYFAk2I5W0ACgkQ4RgdOxQVi0DkHQCfSCyc/hpAJ7prmphcK64EsrC9
> >>>>>>> 5y8AoJs1EsE5nSRHt22p9bkDlHalZsvL
> >>>>>>> =7e74
> >>>>>>> -----END PGP SIGNATURE-----
> >>>>>>> _______________________________________________
> >>>>>>> beagle-planning mailing list
> >>>>>>> beagle-planning at ci.uchicago.edu
> >>>>>>> http://mail.ci.uchicago.edu/mailman/listinfo/beagle-planning
> >>>>>>
> >>>>>> --
> >>>>>> Michael Wilde
> >>>>>> Computation Institute, University of Chicago
> >>>>>> Mathematics and Computer Science Division
> >>>>>> Argonne National Laboratory
> >>>>>>
> >>>>>
> >>>>> -----BEGIN PGP SIGNATURE-----
> >>>>> Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
> >>>>>
> >>>>> iEYEARECAAYFAk2I5poACgkQ4RgdOxQVi0BsswCggHcK5CgdUjazD0eoBaWE7nAY
> >>>>> 6R8An1Wcz9e+C8pA5w9wpyJdaJ3hGg79
> >>>>> =YP0B
> >>>>> -----END PGP SIGNATURE-----
> >>>>> _______________________________________________
> >>>>> beagle-planning mailing list
> >>>>> beagle-planning at ci.uchicago.edu
> >>>>> http://mail.ci.uchicago.edu/mailman/listinfo/beagle-planning
> >>>>
> >>>> _______________________________________________
> >>>> beagle-planning mailing list
> >>>> beagle-planning at ci.uchicago.edu
> >>>> http://mail.ci.uchicago.edu/mailman/listinfo/beagle-planning
> >>>
> >>> --
> >>> Daniel S. Katz
> >>> University of Chicago
> >>> (773) 834-7186 (voice)
> >>> (773) 834-3700 (fax)
> >>> d.katz at ieee.org or dsk at ci.uchicago.edu
> >>> http://www.ci.uchicago.edu/~dsk/
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> beagle-planning mailing list
> >>> beagle-planning at ci.uchicago.edu
> >>> http://mail.ci.uchicago.edu/mailman/listinfo/beagle-planning
> >>
> >> _______________________________________________
> >> beagle-planning mailing list
> >> beagle-planning at ci.uchicago.edu
> >> http://mail.ci.uchicago.edu/mailman/listinfo/beagle-planning
> >
>
> _______________________________________________
> beagle-planning mailing list
> beagle-planning at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/beagle-planning
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
--
Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the reporter.
From wilde at mcs.anl.gov Tue Apr 5 11:52:48 2011
From: wilde at mcs.anl.gov (Michael Wilde)
Date: Tue, 5 Apr 2011 11:52:48 -0500 (CDT)
Subject: [Swift-devel] Re: R library(ncdf) [PADS Support #12231]
In-Reply-To: <370016820.65991.1302021770552.JavaMail.root@zimbra.anl.gov>
Message-ID: <916965871.66061.1302022368502.JavaMail.root@zimbra.anl.gov>
----- Forwarded Message -----
From: "Michael Wilde"
To: "Neil Best"
Cc: "joshua elliott" , "PADS Support"
Sent: Tuesday, April 5, 2011 11:47:04 AM
Subject: Re: R library(ncdf) [PADS Support #12231]
According to this thread I found on google, the R install may be looking for HDF5 libs to load netCDF:
http://www.unidata.ucar.edu/support/help/MailArchives/netcdf-perl/msg00374.html
Does the R package doc say anything about how to ensure that the HDF5 libs are in your LD_LIBRARY_PATH?
- MIke
----- Original Message -----
> Begin forwarded message:
>
> > From: Neil Best
> > Date: March 28, 2011 3:04:17 PM CDT
> > To: pads-support at ci.uchicago.edu
> > Subject: Re: R library(ncdf) [PADS Support #12231]
> >
> > In a fresh login shell starting a fresh R session after changing my
> > .soft I get this:
> >
> >> sessionInfo()
> > R version 2.12.0 (2010-10-15)
> > Platform: x86_64-unknown-linux-gnu (64-bit)
> >
> > locale:
> > [1] LC_CTYPE=en_US.UTF-8 LC_NUMERIC=C
> > [3] LC_TIME=en_US.UTF-8 LC_COLLATE=en_US.UTF-8
> > [5] LC_MONETARY=C LC_MESSAGES=en_US.UTF-8
> > [7] LC_PAPER=en_US.UTF-8 LC_NAME=C
> > [9] LC_ADDRESS=C LC_TELEPHONE=C
> > [11] LC_MEASUREMENT=en_US.UTF-8 LC_IDENTIFICATION=C
> >
> > attached base packages:
> > [1] stats graphics grDevices utils datasets methods base
> >> .libPaths()
> > [1] "/home/nbest/R/x86_64-unknown-linux-gnu-library/2.12/"
> > [2] "/soft/R-DBI-0.2-5-gcc4.1-r1/lib/R2.12/site-library"
> > [3] "/soft/R-RPostgreSQL-0.1-7-gcc4.1-r1/lib/R2.12/site-library"
> > [4] "/soft/R-sp-0.9-72-gcc4.1-r1/lib/R2.12/site-library"
> > [5] "/soft/R-rgdal-0.6-30-gcc4.1-r1/lib/R2.12/site-library"
> > [6] "/soft/R-RColorBrewer-1.0.2-gcc4.1-r1/lib/R2.12/site-library"
> > [7] "/soft/R-ncdf-1.8-gcc4.1-r1/lib/R2.12/site-library"
> > [8] "/soft/R-2.12.0-gcc4.1-r1/lib64/R/library"
> >> library(ncdf)
> > Error: package 'ncdf' was built before R 2.10.0: please re-install
> > it
> >
> >
> > You were able to load it? What would be different between our
> > sessions? It's not in my home library, so I reasonably sure that
> > it's trying to load your build.
> >
> > [nbest at login2 R]$ find ~nbest/R -type d -name ncdf
> > [nbest at login2 R]$ find /soft/R-ncdf-1.8-gcc4.1-r1/ -type d -name
> > ncdf
> > /soft/R-ncdf-1.8-gcc4.1-r1/lib/R2.12/site-library/ncdf
> >
> > I tried installing it to ~nbest/R using the args you gave me, but it
> > still fails:
> >
> > [nbest at login2 src]$ R CMD INSTALL -l ~/R
> > /software/common/src/ncdf_1.8.1.tar.gz
> > --configure-args="LDFLAGS='-L/soft/hdf5-1.8.2-gcc4.1-r1/lib -lhdf5
> > -lhdf5_hl' --with-netcdf_incdir=/soft/netcdf-4.0-gcc4.1-r1/include
> > --with-netcdf_libdir=/soft/netcdf-4.0-gcc4.1-r1/lib"
> > . . .
> > unable to load shared object
> > '/autonfs/home/nbest/R/ncdf/libs/ncdf.so':
> > /soft/netcdf-4.0-gcc4.1-r1/lib/libnetcdf.so.5: undefined symbol:
> > H5P_CLS_FILE_CREATE_g
> >
> > I think that's the same error as before. I still can't imagine
> > what's different about our environments. Can you?
> >
> >
> >
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
----- Original Message -----
> Hi Neil,
>
> Thanks for the heads-up. No, I have never tried building R with ncdf.
>
> The next 4 weeks are very busy for me as well with travel, workshops
> and proposals.
>
> I'm sending to swift-devel as well as Rob and Sheri of the MCS Climate
> group to see if they have any info on building the netCDF package for
> R.
>
> Regards,
>
> Mike
>
> ----- Original Message -----
> > Hi, Mike. Have you ever tried to install the ncdf package for R? I
> > have a ticket open with Ti, but he seems to be having trouble with
> > it.
> > He thought he had it at one point (see below) but there was a
> > problem
> > -- I think he used the OS version of R. I'll send you my reply from
> > when I tried to use what he had built. If you have any spare cycles
> > for this in the interest of moving my SwiftR project forward over
> > the
> > next 2-3 weeks that would be great. I'll let you know if I hear
> > anything from Ti. I'm not bugging him about it this week because I
> > have my hands full and I think he's helping get ready for the Globus
> > meeting, but I'm just trying to keep the issue alive. Thanks, Mike.
> >
> >
> > Neil
> >
> >
> > Begin forwarded message:
> >
> > > From: "Ti Leggett"
> > > Date: March 28, 2011 12:42:58 PM CDT
> > > To: nbest at ci.uchicago.edu
> > > Subject: R library(ncdf) [PADS Support #12231]
> > > Reply-To: pads-support at ci.uchicago.edu
> > >
> > > Bleh, accidentally hit comment instead of reply:
> > >
> > >
> > > The magic command was this:
> > > R CMD INSTALL -l /soft/R-ncdf-1.8-gcc4.1-r1/lib/R2.12/site-library
> > > /software/common/src/ncdf_1.8.1.tar.gz
> > > --configure-args="LDFLAGS='-L/soft/hdf5-1.8.2-gcc4.1-r1/lib -lhdf5
> > > -lhdf5_hl' --with-netcdf_incdir=/soft/netcdf-4.0-gcc4.1-r1/include
> > > --with-netcdf_libdir=/soft/netcdf-4.0-gcc4.1-r1/lib"
> > >
> > > Add the following to your .soft to use it:
> > >
> > > +netcdf-4.0-gcc4.1-r1
> > > +szip-2.1-gcc4.1-r1
> > > +hdf5-1.8.2-gcc4.1-r1
> > > +R-ncdf-gcc-R2.12
>
> --
> Michael Wilde
> Computation Institute, University of Chicago
> Mathematics and Computer Science Division
> Argonne National Laboratory
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
From bugzilla-daemon at mcs.anl.gov Tue Apr 5 13:21:39 2011
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Tue, 5 Apr 2011 13:21:39 -0500 (CDT)
Subject: [Swift-devel] [Bug 321] Improve "cant find wrapper log" error
message and document in new Debugging chapter
In-Reply-To:
References:
Message-ID: <20110405182139.E994B1C073@wind.mcs.anl.gov>
https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=321
ketan changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ketan at mcs.anl.gov
--- Comment #2 from ketan 2011-04-05 13:21:39 ---
Might be good to put a diagnostic remark on the lines of "The filesystem you
are using might not be writable by provider" as this is often the case on
"failed to transfer ..." errors.
--
Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the reporter.
From wilde at mcs.anl.gov Tue Apr 5 13:36:42 2011
From: wilde at mcs.anl.gov (Michael Wilde)
Date: Tue, 5 Apr 2011 13:36:42 -0500 (CDT)
Subject: [Swift-devel] Re: Can you test 0.92 branch for 0.92.1 release?
In-Reply-To:
Message-ID: <1738774714.66684.1302028602212.JavaMail.root@zimbra.anl.gov>
Thanks, David. Please cc all discussion of this sort to swift-devel.
I assume SVN is working for you now? (It was working for me, from communicadao, around 9AM this morning).
- Mike
----- Original Message -----
> It appears that there may be a problem with svn.ci.uchicago.edu . I am
> unable to connect from an SVN client or through the web interface -
> both attempts just hang indefinitely. I have sent an email to support
> (ticket 12539), but just wanted to give you guys a heads up that there
> may be an issue there. I will try to run the tests again in the
> morning.
>
> David
>
>
> On Mon, Apr 4, 2011 at 2:42 PM, Michael Wilde < wilde at mcs.anl.gov >
> wrote:
>
>
> David, Sarah,
>
> How quickly could you re-divide the Swift site test plan between you
> and confirm back to swift-devel that we are ready to tag and release
> the branch as 0.92.1?
>
> Before we do that, you need to add a test to the test suite that can
> replicate the twice-each bug and verify that its detected in 0.92 and
> corrected in 0.92.1
>
> Can you possibly do this by noon tomorrow?
>
> Can you post a checklist of tests with names of who's going to run
> them?
>
> Depending on what you can commit to, I will see if I, Ketan, and/or
> Justin can help take various sites as well. I feel we really need to
> do this quickly so we have a stable trusted release out there.
>
>
>
> Thanks,
>
> Mike
>
> --
> Michael Wilde
> Computation Institute, University of Chicago
> Mathematics and Computer Science Division
> Argonne National Laboratory
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
From bugzilla-daemon at mcs.anl.gov Tue Apr 5 13:52:38 2011
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Tue, 5 Apr 2011 13:52:38 -0500 (CDT)
Subject: [Swift-devel] [Bug 325] New: indicate host gridftp server that
caused the error:
Message-ID:
https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=325
Summary: indicate host gridftp server that caused the error:
Product: Swift
Version: trunk
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: error messages
AssignedTo: skenny at uchicago.edu
ReportedBy: aespinosa at cs.uchicago.edu
CC: swift-devel at ci.uchicago.edu
type file;
app (file o) cat(file i) {
cat i @stdout=o;
}
file y<"gsiftp://somehost//filename3">;
file x <"gsiftp://somehost//filename";
x=cat(y);
sites.xml
...
...
/someworkdir
When something goes wrong with either hosts 'somehost' and 'another' host, logs
and error messages only report this:
...
Caused by: org.globus.cog.abstraction.impl.file.IrrecoverableResourceException:
Error communicating with the GridFTP server
Caused by: org.globus.cog.abstraction.impl.common.task.TaskSubmissionException:
org.globus.cog.abstraction.impl.file.IrrecoverableResourceException: Error
communicating with the GridFTP server
Caused by: org.globus.cog.abstraction.impl.file.IrrecoverableResourceException:
Error communicating with the GridFTP server
Caused by: java.net.ConnectException: Connection refused
Final status: Failed:4 Finished in previous run:11
This is manageable for single remote resources. but with more pools (hence
gridftp endpoints), this is getting harder to debug
--
Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
From wilde at mcs.anl.gov Tue Apr 5 14:10:09 2011
From: wilde at mcs.anl.gov (Michael Wilde)
Date: Tue, 5 Apr 2011 14:10:09 -0500 (CDT)
Subject: [Swift-devel] Re: Can you test 0.92 branch for 0.92.1 release?
In-Reply-To: <1738774714.66684.1302028602212.JavaMail.root@zimbra.anl.gov>
Message-ID: <721045497.66956.1302030609111.JavaMail.root@zimbra.anl.gov>
David, Sarah, Ketan,
Can you all report back to the devel list on your progress on testing the release? Ie, what systems are you testing, and which of those tests are complete? When will the rest be done, and hence when are we ready to tag and release the fix?
I asked who will create the test to confirm that the twice-each bug is fixed, but no one responded. Which of the three of you feel you know how to do this? Is this being tested in your new tests?
Ketan tells me that in the 0.92+ interim release I made for Beagle it looks like the resume feature is not working. I was aware that such a bug was reported in trunk, but in the original 0.92 Cray version (under /home/wilde/swift/rev) resume *was* working. Does the test suite test the resume feature at the moment?
Lastly, who will tag and upload the new release, remove or change the red warning in the download page, and announce 0.92.1 on swift-user?
- Mike
----- Original Message -----
> Thanks, David. Please cc all discussion of this sort to swift-devel.
>
> I assume SVN is working for you now? (It was working for me, from
> communicadao, around 9AM this morning).
>
> - Mike
>
>
> ----- Original Message -----
> > It appears that there may be a problem with svn.ci.uchicago.edu . I
> > am
> > unable to connect from an SVN client or through the web interface -
> > both attempts just hang indefinitely. I have sent an email to
> > support
> > (ticket 12539), but just wanted to give you guys a heads up that
> > there
> > may be an issue there. I will try to run the tests again in the
> > morning.
> >
> > David
> >
> >
> > On Mon, Apr 4, 2011 at 2:42 PM, Michael Wilde < wilde at mcs.anl.gov >
> > wrote:
> >
> >
> > David, Sarah,
> >
> > How quickly could you re-divide the Swift site test plan between you
> > and confirm back to swift-devel that we are ready to tag and release
> > the branch as 0.92.1?
> >
> > Before we do that, you need to add a test to the test suite that can
> > replicate the twice-each bug and verify that its detected in 0.92
> > and
> > corrected in 0.92.1
> >
> > Can you possibly do this by noon tomorrow?
> >
> > Can you post a checklist of tests with names of who's going to run
> > them?
> >
> > Depending on what you can commit to, I will see if I, Ketan, and/or
> > Justin can help take various sites as well. I feel we really need to
> > do this quickly so we have a stable trusted release out there.
> >
> >
> >
> > Thanks,
> >
> > Mike
> >
> > --
> > Michael Wilde
> > Computation Institute, University of Chicago
> > Mathematics and Computer Science Division
> > Argonne National Laboratory
>
> --
> Michael Wilde
> Computation Institute, University of Chicago
> Mathematics and Computer Science Division
> Argonne National Laboratory
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
From skenny at uchicago.edu Tue Apr 5 14:13:37 2011
From: skenny at uchicago.edu (Sarah Kenny)
Date: Tue, 5 Apr 2011 12:13:37 -0700
Subject: [Swift-devel] Re: Can you test 0.92 branch for 0.92.1 release?
In-Reply-To: <721045497.66956.1302030609111.JavaMail.root@zimbra.anl.gov>
References: <1738774714.66684.1302028602212.JavaMail.root@zimbra.anl.gov>
<721045497.66956.1302030609111.JavaMail.root@zimbra.anl.gov>
Message-ID:
i'm currently working on a swift script to replicate the bug for .92 which i
will then commit to svn in the test suite. if you mike, or ketan already
have this let me know (i'm trying to hack the script jon posted to the list)
and i'll use yours...david said he doesn't have one.
as i said, my plan was to test on ranger, abe and a couple of (uci) local
workstations.
~sk
On Tue, Apr 5, 2011 at 12:10 PM, Michael Wilde wrote:
> David, Sarah, Ketan,
>
> Can you all report back to the devel list on your progress on testing the
> release? Ie, what systems are you testing, and which of those tests are
> complete? When will the rest be done, and hence when are we ready to tag
> and release the fix?
>
> I asked who will create the test to confirm that the twice-each bug is
> fixed, but no one responded. Which of the three of you feel you know how to
> do this? Is this being tested in your new tests?
>
> Ketan tells me that in the 0.92+ interim release I made for Beagle it looks
> like the resume feature is not working. I was aware that such a bug was
> reported in trunk, but in the original 0.92 Cray version (under
> /home/wilde/swift/rev) resume *was* working. Does the test suite test the
> resume feature at the moment?
>
> Lastly, who will tag and upload the new release, remove or change the red
> warning in the download page, and announce 0.92.1 on swift-user?
>
> - Mike
>
>
> ----- Original Message -----
> > Thanks, David. Please cc all discussion of this sort to swift-devel.
> >
> > I assume SVN is working for you now? (It was working for me, from
> > communicadao, around 9AM this morning).
> >
> > - Mike
> >
> >
> > ----- Original Message -----
> > > It appears that there may be a problem with svn.ci.uchicago.edu . I
> > > am
> > > unable to connect from an SVN client or through the web interface -
> > > both attempts just hang indefinitely. I have sent an email to
> > > support
> > > (ticket 12539), but just wanted to give you guys a heads up that
> > > there
> > > may be an issue there. I will try to run the tests again in the
> > > morning.
> > >
> > > David
> > >
> > >
> > > On Mon, Apr 4, 2011 at 2:42 PM, Michael Wilde < wilde at mcs.anl.gov >
> > > wrote:
> > >
> > >
> > > David, Sarah,
> > >
> > > How quickly could you re-divide the Swift site test plan between you
> > > and confirm back to swift-devel that we are ready to tag and release
> > > the branch as 0.92.1?
> > >
> > > Before we do that, you need to add a test to the test suite that can
> > > replicate the twice-each bug and verify that its detected in 0.92
> > > and
> > > corrected in 0.92.1
> > >
> > > Can you possibly do this by noon tomorrow?
> > >
> > > Can you post a checklist of tests with names of who's going to run
> > > them?
> > >
> > > Depending on what you can commit to, I will see if I, Ketan, and/or
> > > Justin can help take various sites as well. I feel we really need to
> > > do this quickly so we have a stable trusted release out there.
> > >
> > >
> > >
> > > Thanks,
> > >
> > > Mike
> > >
> > > --
> > > Michael Wilde
> > > Computation Institute, University of Chicago
> > > Mathematics and Computer Science Division
> > > Argonne National Laboratory
> >
> > --
> > Michael Wilde
> > Computation Institute, University of Chicago
> > Mathematics and Computer Science Division
> > Argonne National Laboratory
> >
> > _______________________________________________
> > Swift-devel mailing list
> > Swift-devel at ci.uchicago.edu
> > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>
> --
> Michael Wilde
> Computation Institute, University of Chicago
> Mathematics and Computer Science Division
> Argonne National Laboratory
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From ketancmaheshwari at gmail.com Tue Apr 5 14:17:52 2011
From: ketancmaheshwari at gmail.com (Ketan Maheshwari)
Date: Tue, 5 Apr 2011 14:17:52 -0500
Subject: [Swift-devel] Re: Can you test 0.92 branch for 0.92.1 release?
In-Reply-To:
References: <1738774714.66684.1302028602212.JavaMail.root@zimbra.anl.gov>
<721045497.66956.1302030609111.JavaMail.root@zimbra.anl.gov>
Message-ID:
Sarah,
I do not have the test you are asking for yet. I am looking at the test suite and will start on Beagle soon.
Ketan
On Apr 5, 2011, at 2:13 PM, Sarah Kenny wrote:
> i'm currently working on a swift script to replicate the bug for .92 which i will then commit to svn in the test suite. if you mike, or ketan already have this let me know (i'm trying to hack the script jon posted to the list) and i'll use yours...david said he doesn't have one.
>
> as i said, my plan was to test on ranger, abe and a couple of (uci) local workstations.
>
> ~sk
>
> On Tue, Apr 5, 2011 at 12:10 PM, Michael Wilde wrote:
> David, Sarah, Ketan,
>
> Can you all report back to the devel list on your progress on testing the release? Ie, what systems are you testing, and which of those tests are complete? When will the rest be done, and hence when are we ready to tag and release the fix?
>
> I asked who will create the test to confirm that the twice-each bug is fixed, but no one responded. Which of the three of you feel you know how to do this? Is this being tested in your new tests?
>
> Ketan tells me that in the 0.92+ interim release I made for Beagle it looks like the resume feature is not working. I was aware that such a bug was reported in trunk, but in the original 0.92 Cray version (under /home/wilde/swift/rev) resume *was* working. Does the test suite test the resume feature at the moment?
>
> Lastly, who will tag and upload the new release, remove or change the red warning in the download page, and announce 0.92.1 on swift-user?
>
> - Mike
>
>
> ----- Original Message -----
> > Thanks, David. Please cc all discussion of this sort to swift-devel.
> >
> > I assume SVN is working for you now? (It was working for me, from
> > communicadao, around 9AM this morning).
> >
> > - Mike
> >
> >
> > ----- Original Message -----
> > > It appears that there may be a problem with svn.ci.uchicago.edu . I
> > > am
> > > unable to connect from an SVN client or through the web interface -
> > > both attempts just hang indefinitely. I have sent an email to
> > > support
> > > (ticket 12539), but just wanted to give you guys a heads up that
> > > there
> > > may be an issue there. I will try to run the tests again in the
> > > morning.
> > >
> > > David
> > >
> > >
> > > On Mon, Apr 4, 2011 at 2:42 PM, Michael Wilde < wilde at mcs.anl.gov >
> > > wrote:
> > >
> > >
> > > David, Sarah,
> > >
> > > How quickly could you re-divide the Swift site test plan between you
> > > and confirm back to swift-devel that we are ready to tag and release
> > > the branch as 0.92.1?
> > >
> > > Before we do that, you need to add a test to the test suite that can
> > > replicate the twice-each bug and verify that its detected in 0.92
> > > and
> > > corrected in 0.92.1
> > >
> > > Can you possibly do this by noon tomorrow?
> > >
> > > Can you post a checklist of tests with names of who's going to run
> > > them?
> > >
> > > Depending on what you can commit to, I will see if I, Ketan, and/or
> > > Justin can help take various sites as well. I feel we really need to
> > > do this quickly so we have a stable trusted release out there.
> > >
> > >
> > >
> > > Thanks,
> > >
> > > Mike
> > >
> > > --
> > > Michael Wilde
> > > Computation Institute, University of Chicago
> > > Mathematics and Computer Science Division
> > > Argonne National Laboratory
> >
> > --
> > Michael Wilde
> > Computation Institute, University of Chicago
> > Mathematics and Computer Science Division
> > Argonne National Laboratory
> >
> > _______________________________________________
> > Swift-devel mailing list
> > Swift-devel at ci.uchicago.edu
> > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>
> --
> Michael Wilde
> Computation Institute, University of Chicago
> Mathematics and Computer Science Division
> Argonne National Laboratory
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From jon.monette at gmail.com Tue Apr 5 14:26:48 2011
From: jon.monette at gmail.com (Jonathan Monette)
Date: Tue, 5 Apr 2011 14:26:48 -0500
Subject: [Swift-devel] Re: Can you test 0.92 branch for 0.92.1 release?
In-Reply-To:
References: <1738774714.66684.1302028602212.JavaMail.root@zimbra.anl.gov>
<721045497.66956.1302030609111.JavaMail.root@zimbra.anl.gov>
Message-ID:
The script I posted might be too complex to use to replicate the twice each
bug. However, didn't Mike post a simple loop script that was looping twice
when the bug was initially found?
On Tue, Apr 5, 2011 at 2:17 PM, Ketan Maheshwari wrote:
> Sarah,
>
> I do not have the test you are asking for yet. I am looking at the test
> suite and will start on Beagle soon.
>
> Ketan
>
> On Apr 5, 2011, at 2:13 PM, Sarah Kenny wrote:
>
> i'm currently working on a swift script to replicate the bug for .92 which
> i will then commit to svn in the test suite. if you mike, or ketan already
> have this let me know (i'm trying to hack the script jon posted to the list)
> and i'll use yours...david said he doesn't have one.
>
> as i said, my plan was to test on ranger, abe and a couple of (uci) local
> workstations.
>
> ~sk
>
> On Tue, Apr 5, 2011 at 12:10 PM, Michael Wilde wrote:
>
>> David, Sarah, Ketan,
>>
>> Can you all report back to the devel list on your progress on testing the
>> release? Ie, what systems are you testing, and which of those tests are
>> complete? When will the rest be done, and hence when are we ready to tag
>> and release the fix?
>>
>> I asked who will create the test to confirm that the twice-each bug is
>> fixed, but no one responded. Which of the three of you feel you know how to
>> do this? Is this being tested in your new tests?
>>
>> Ketan tells me that in the 0.92+ interim release I made for Beagle it
>> looks like the resume feature is not working. I was aware that such a bug
>> was reported in trunk, but in the original 0.92 Cray version (under
>> /home/wilde/swift/rev) resume *was* working. Does the test suite test the
>> resume feature at the moment?
>>
>> Lastly, who will tag and upload the new release, remove or change the red
>> warning in the download page, and announce 0.92.1 on swift-user?
>>
>> - Mike
>>
>>
>> ----- Original Message -----
>> > Thanks, David. Please cc all discussion of this sort to swift-devel.
>> >
>> > I assume SVN is working for you now? (It was working for me, from
>> > communicadao, around 9AM this morning).
>> >
>> > - Mike
>> >
>> >
>> > ----- Original Message -----
>> > > It appears that there may be a problem with svn.ci.uchicago.edu . I
>> > > am
>> > > unable to connect from an SVN client or through the web interface -
>> > > both attempts just hang indefinitely. I have sent an email to
>> > > support
>> > > (ticket 12539), but just wanted to give you guys a heads up that
>> > > there
>> > > may be an issue there. I will try to run the tests again in the
>> > > morning.
>> > >
>> > > David
>> > >
>> > >
>> > > On Mon, Apr 4, 2011 at 2:42 PM, Michael Wilde < wilde at mcs.anl.gov >
>> > > wrote:
>> > >
>> > >
>> > > David, Sarah,
>> > >
>> > > How quickly could you re-divide the Swift site test plan between you
>> > > and confirm back to swift-devel that we are ready to tag and release
>> > > the branch as 0.92.1?
>> > >
>> > > Before we do that, you need to add a test to the test suite that can
>> > > replicate the twice-each bug and verify that its detected in 0.92
>> > > and
>> > > corrected in 0.92.1
>> > >
>> > > Can you possibly do this by noon tomorrow?
>> > >
>> > > Can you post a checklist of tests with names of who's going to run
>> > > them?
>> > >
>> > > Depending on what you can commit to, I will see if I, Ketan, and/or
>> > > Justin can help take various sites as well. I feel we really need to
>> > > do this quickly so we have a stable trusted release out there.
>> > >
>> > >
>> > >
>> > > Thanks,
>> > >
>> > > Mike
>> > >
>> > > --
>> > > Michael Wilde
>> > > Computation Institute, University of Chicago
>> > > Mathematics and Computer Science Division
>> > > Argonne National Laboratory
>> >
>> > --
>> > Michael Wilde
>> > Computation Institute, University of Chicago
>> > Mathematics and Computer Science Division
>> > Argonne National Laboratory
>> >
>> > _______________________________________________
>> > Swift-devel mailing list
>> > Swift-devel at ci.uchicago.edu
>> > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>>
>> --
>> Michael Wilde
>> Computation Institute, University of Chicago
>> Mathematics and Computer Science Division
>> Argonne National Laboratory
>>
>>
>
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>
>
--
Any intelligent fool can make things bigger and more complex... It takes a
touch of genius - and a lot of courage to move in the opposite direction.
- Albert Einstein
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From wilde at mcs.anl.gov Tue Apr 5 14:33:42 2011
From: wilde at mcs.anl.gov (Michael Wilde)
Date: Tue, 5 Apr 2011 14:33:42 -0500 (CDT)
Subject: [Swift-devel] Re: Can you test 0.92 branch for 0.92.1 release?
In-Reply-To:
Message-ID: <1046706498.67103.1302032022991.JavaMail.root@zimbra.anl.gov>
Yes, I had posted variations of the following to the list:
zz3.swift:
int arr[];
arr[0]=1;
arr[1]=2;
foreach a in arr {
trace("for", a);
}
zz6.swift:
int arr[];
foreach a,i in [0:9] {
arr[i] = i;
}
trace("arr",arr);
foreach a,i in arr {
trace("for", a,i);
}
com$ PATH=/home/wilde/swift/src/0.92/cog/modules/swift/dist/swift-svn/bin/:$PATH
com$ which swift
~/swift/src/0.92/cog/modules/swift/dist/swift-svn/bin/swift
com$ cd swift/lab
com$ swift zz3.swift
Swift svn swift-r4252 (swift modified locally) cog-r3088 (cog modified locally)
RunID: 20110404-1344-j98f22id
Progress:
SwiftScript trace: for, 2
SwiftScript trace: for, 1
Final status:
com$ PATH=~/swift/rev/swift-0.92/bin:$PATH
com$ swift zz3.swift
Swift svn swift-r4157 cog-r3056
RunID: 20110404-1344-ensm4te8
Progress:
SwiftScript trace: for, 1
SwiftScript trace: for, 2
SwiftScript trace: for, 2
SwiftScript trace: for, 1
Final status:
com$ swift zz6.swift
Swift svn swift-r4157 cog-r3056
RunID: 20110404-1344-i7y6q1i1
Progress:
SwiftScript trace: arr, arr.$[]/10
SwiftScript trace: for, 3, 3
SwiftScript trace: for, 2, 2
SwiftScript trace: for, 4, 4
SwiftScript trace: for, 5, 5
SwiftScript trace: for, 3, 3
SwiftScript trace: for, 5, 5
SwiftScript trace: for, 9, 9
SwiftScript trace: for, 4, 4
SwiftScript trace: for, 1, 1
SwiftScript trace: for, 7, 7
SwiftScript trace: for, 7, 7
SwiftScript trace: for, 6, 6
SwiftScript trace: for, 9, 9
SwiftScript trace: for, 6, 6
SwiftScript trace: for, 1, 1
SwiftScript trace: for, 2, 2
SwiftScript trace: for, 0, 0
SwiftScript trace: for, 8, 8
SwiftScript trace: for, 0, 0
SwiftScript trace: for, 8, 8
Final status:
com$
----- Original Message -----
> The script I posted might be too complex to use to replicate the twice
> each bug. However, didn't Mike post a simple loop script that was
> looping twice when the bug was initially found?
>
>
> On Tue, Apr 5, 2011 at 2:17 PM, Ketan Maheshwari <
> ketancmaheshwari at gmail.com > wrote:
>
>
>
> Sarah,
>
>
> I do not have the test you are asking for yet. I am looking at the
> test suite and will start on Beagle soon.
>
>
> Ketan
>
>
>
>
>
>
>
> On Apr 5, 2011, at 2:13 PM, Sarah Kenny wrote:
>
>
> i'm currently working on a swift script to replicate the bug for .92
> which i will then commit to svn in the test suite. if you mike, or
> ketan already have this let me know (i'm trying to hack the script jon
> posted to the list) and i'll use yours...david said he doesn't have
> one.
>
> as i said, my plan was to test on ranger, abe and a couple of (uci)
> local workstations.
>
> ~sk
>
>
> On Tue, Apr 5, 2011 at 12:10 PM, Michael Wilde < wilde at mcs.anl.gov >
> wrote:
>
>
> David, Sarah, Ketan,
>
> Can you all report back to the devel list on your progress on testing
> the release? Ie, what systems are you testing, and which of those
> tests are complete? When will the rest be done, and hence when are we
> ready to tag and release the fix?
>
> I asked who will create the test to confirm that the twice-each bug is
> fixed, but no one responded. Which of the three of you feel you know
> how to do this? Is this being tested in your new tests?
>
> Ketan tells me that in the 0.92+ interim release I made for Beagle it
> looks like the resume feature is not working. I was aware that such a
> bug was reported in trunk, but in the original 0.92 Cray version
> (under /home/wilde/swift/rev) resume *was* working. Does the test
> suite test the resume feature at the moment?
>
> Lastly, who will tag and upload the new release, remove or change the
> red warning in the download page, and announce 0.92.1 on swift-user?
>
> - Mike
>
>
>
>
>
> ----- Original Message -----
> > Thanks, David. Please cc all discussion of this sort to swift-devel.
> >
> > I assume SVN is working for you now? (It was working for me, from
> > communicadao, around 9AM this morning).
> >
> > - Mike
> >
> >
> > ----- Original Message -----
> > > It appears that there may be a problem with svn.ci.uchicago.edu .
> > > I
> > > am
> > > unable to connect from an SVN client or through the web interface
> > > -
> > > both attempts just hang indefinitely. I have sent an email to
> > > support
> > > (ticket 12539), but just wanted to give you guys a heads up that
> > > there
> > > may be an issue there. I will try to run the tests again in the
> > > morning.
> > >
> > > David
> > >
> > >
> > > On Mon, Apr 4, 2011 at 2:42 PM, Michael Wilde < wilde at mcs.anl.gov
> > > >
> > > wrote:
> > >
> > >
> > > David, Sarah,
> > >
> > > How quickly could you re-divide the Swift site test plan between
> > > you
> > > and confirm back to swift-devel that we are ready to tag and
> > > release
> > > the branch as 0.92.1?
> > >
> > > Before we do that, you need to add a test to the test suite that
> > > can
> > > replicate the twice-each bug and verify that its detected in 0.92
> > > and
> > > corrected in 0.92.1
> > >
> > > Can you possibly do this by noon tomorrow?
> > >
> > > Can you post a checklist of tests with names of who's going to run
> > > them?
> > >
> > > Depending on what you can commit to, I will see if I, Ketan,
> > > and/or
> > > Justin can help take various sites as well. I feel we really need
> > > to
> > > do this quickly so we have a stable trusted release out there.
> > >
> > >
> > >
> > > Thanks,
> > >
> > > Mike
> > >
> > > --
> > > Michael Wilde
> > > Computation Institute, University of Chicago
> > > Mathematics and Computer Science Division
> > > Argonne National Laboratory
> >
> > --
> > Michael Wilde
> > Computation Institute, University of Chicago
> > Mathematics and Computer Science Division
> > Argonne National Laboratory
> >
> > _______________________________________________
> > Swift-devel mailing list
> > Swift-devel at ci.uchicago.edu
> > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>
> --
>
>
>
> Michael Wilde
> Computation Institute, University of Chicago
> Mathematics and Computer Science Division
> Argonne National Laboratory
>
>
>
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>
>
>
>
> --
> Any intelligent fool can make things bigger and more complex... It
> takes a touch of genius - and a lot of courage to move in the opposite
> direction.
> - Albert Einstein
>
>
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
From jon.monette at gmail.com Tue Apr 5 14:37:09 2011
From: jon.monette at gmail.com (Jonathan Monette)
Date: Tue, 5 Apr 2011 14:37:09 -0500
Subject: [Swift-devel] Re: Can you test 0.92 branch for 0.92.1 release?
In-Reply-To: <1046706498.67103.1302032022991.JavaMail.root@zimbra.anl.gov>
References:
<1046706498.67103.1302032022991.JavaMail.root@zimbra.anl.gov>
Message-ID:
Yes. That is the one I remember seeing. That is much easier than what my
Montage scripts are doing.
On Tue, Apr 5, 2011 at 2:33 PM, Michael Wilde wrote:
> Yes, I had posted variations of the following to the list:
>
> zz3.swift:
>
> int arr[];
>
> arr[0]=1;
> arr[1]=2;
>
> foreach a in arr {
> trace("for", a);
> }
>
> zz6.swift:
>
>
> int arr[];
>
> foreach a,i in [0:9] {
> arr[i] = i;
> }
>
> trace("arr",arr);
>
> foreach a,i in arr {
> trace("for", a,i);
> }
>
>
> com$
> PATH=/home/wilde/swift/src/0.92/cog/modules/swift/dist/swift-svn/bin/:$PATH
> com$ which swift
> ~/swift/src/0.92/cog/modules/swift/dist/swift-svn/bin/swift
> com$ cd swift/lab
> com$ swift zz3.swift
> Swift svn swift-r4252 (swift modified locally) cog-r3088 (cog modified
> locally)
>
> RunID: 20110404-1344-j98f22id
> Progress:
> SwiftScript trace: for, 2
> SwiftScript trace: for, 1
> Final status:
> com$ PATH=~/swift/rev/swift-0.92/bin:$PATH
> com$ swift zz3.swift
> Swift svn swift-r4157 cog-r3056
>
> RunID: 20110404-1344-ensm4te8
> Progress:
> SwiftScript trace: for, 1
> SwiftScript trace: for, 2
> SwiftScript trace: for, 2
> SwiftScript trace: for, 1
> Final status:
> com$ swift zz6.swift
> Swift svn swift-r4157 cog-r3056
>
> RunID: 20110404-1344-i7y6q1i1
> Progress:
> SwiftScript trace: arr, arr.$[]/10
> SwiftScript trace: for, 3, 3
> SwiftScript trace: for, 2, 2
> SwiftScript trace: for, 4, 4
> SwiftScript trace: for, 5, 5
> SwiftScript trace: for, 3, 3
> SwiftScript trace: for, 5, 5
> SwiftScript trace: for, 9, 9
> SwiftScript trace: for, 4, 4
> SwiftScript trace: for, 1, 1
> SwiftScript trace: for, 7, 7
> SwiftScript trace: for, 7, 7
> SwiftScript trace: for, 6, 6
> SwiftScript trace: for, 9, 9
> SwiftScript trace: for, 6, 6
> SwiftScript trace: for, 1, 1
> SwiftScript trace: for, 2, 2
> SwiftScript trace: for, 0, 0
> SwiftScript trace: for, 8, 8
> SwiftScript trace: for, 0, 0
> SwiftScript trace: for, 8, 8
> Final status:
> com$
>
>
>
>
>
>
> ----- Original Message -----
> > The script I posted might be too complex to use to replicate the twice
> > each bug. However, didn't Mike post a simple loop script that was
> > looping twice when the bug was initially found?
> >
> >
> > On Tue, Apr 5, 2011 at 2:17 PM, Ketan Maheshwari <
> > ketancmaheshwari at gmail.com > wrote:
> >
> >
> >
> > Sarah,
> >
> >
> > I do not have the test you are asking for yet. I am looking at the
> > test suite and will start on Beagle soon.
> >
> >
> > Ketan
> >
> >
> >
> >
> >
> >
> >
> > On Apr 5, 2011, at 2:13 PM, Sarah Kenny wrote:
> >
> >
> > i'm currently working on a swift script to replicate the bug for .92
> > which i will then commit to svn in the test suite. if you mike, or
> > ketan already have this let me know (i'm trying to hack the script jon
> > posted to the list) and i'll use yours...david said he doesn't have
> > one.
> >
> > as i said, my plan was to test on ranger, abe and a couple of (uci)
> > local workstations.
> >
> > ~sk
> >
> >
> > On Tue, Apr 5, 2011 at 12:10 PM, Michael Wilde < wilde at mcs.anl.gov >
> > wrote:
> >
> >
> > David, Sarah, Ketan,
> >
> > Can you all report back to the devel list on your progress on testing
> > the release? Ie, what systems are you testing, and which of those
> > tests are complete? When will the rest be done, and hence when are we
> > ready to tag and release the fix?
> >
> > I asked who will create the test to confirm that the twice-each bug is
> > fixed, but no one responded. Which of the three of you feel you know
> > how to do this? Is this being tested in your new tests?
> >
> > Ketan tells me that in the 0.92+ interim release I made for Beagle it
> > looks like the resume feature is not working. I was aware that such a
> > bug was reported in trunk, but in the original 0.92 Cray version
> > (under /home/wilde/swift/rev) resume *was* working. Does the test
> > suite test the resume feature at the moment?
> >
> > Lastly, who will tag and upload the new release, remove or change the
> > red warning in the download page, and announce 0.92.1 on swift-user?
> >
> > - Mike
> >
> >
> >
> >
> >
> > ----- Original Message -----
> > > Thanks, David. Please cc all discussion of this sort to swift-devel.
> > >
> > > I assume SVN is working for you now? (It was working for me, from
> > > communicadao, around 9AM this morning).
> > >
> > > - Mike
> > >
> > >
> > > ----- Original Message -----
> > > > It appears that there may be a problem with svn.ci.uchicago.edu .
> > > > I
> > > > am
> > > > unable to connect from an SVN client or through the web interface
> > > > -
> > > > both attempts just hang indefinitely. I have sent an email to
> > > > support
> > > > (ticket 12539), but just wanted to give you guys a heads up that
> > > > there
> > > > may be an issue there. I will try to run the tests again in the
> > > > morning.
> > > >
> > > > David
> > > >
> > > >
> > > > On Mon, Apr 4, 2011 at 2:42 PM, Michael Wilde < wilde at mcs.anl.gov
> > > > >
> > > > wrote:
> > > >
> > > >
> > > > David, Sarah,
> > > >
> > > > How quickly could you re-divide the Swift site test plan between
> > > > you
> > > > and confirm back to swift-devel that we are ready to tag and
> > > > release
> > > > the branch as 0.92.1?
> > > >
> > > > Before we do that, you need to add a test to the test suite that
> > > > can
> > > > replicate the twice-each bug and verify that its detected in 0.92
> > > > and
> > > > corrected in 0.92.1
> > > >
> > > > Can you possibly do this by noon tomorrow?
> > > >
> > > > Can you post a checklist of tests with names of who's going to run
> > > > them?
> > > >
> > > > Depending on what you can commit to, I will see if I, Ketan,
> > > > and/or
> > > > Justin can help take various sites as well. I feel we really need
> > > > to
> > > > do this quickly so we have a stable trusted release out there.
> > > >
> > > >
> > > >
> > > > Thanks,
> > > >
> > > > Mike
> > > >
> > > > --
> > > > Michael Wilde
> > > > Computation Institute, University of Chicago
> > > > Mathematics and Computer Science Division
> > > > Argonne National Laboratory
> > >
> > > --
> > > Michael Wilde
> > > Computation Institute, University of Chicago
> > > Mathematics and Computer Science Division
> > > Argonne National Laboratory
> > >
> > > _______________________________________________
> > > Swift-devel mailing list
> > > Swift-devel at ci.uchicago.edu
> > > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> >
> > --
> >
> >
> >
> > Michael Wilde
> > Computation Institute, University of Chicago
> > Mathematics and Computer Science Division
> > Argonne National Laboratory
> >
> >
> >
> >
> > _______________________________________________
> > Swift-devel mailing list
> > Swift-devel at ci.uchicago.edu
> > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> >
> >
> >
> >
> > --
> > Any intelligent fool can make things bigger and more complex... It
> > takes a touch of genius - and a lot of courage to move in the opposite
> > direction.
> > - Albert Einstein
> >
> >
> >
> > _______________________________________________
> > Swift-devel mailing list
> > Swift-devel at ci.uchicago.edu
> > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>
> --
> Michael Wilde
> Computation Institute, University of Chicago
> Mathematics and Computer Science Division
> Argonne National Laboratory
>
>
--
Any intelligent fool can make things bigger and more complex... It takes a
touch of genius - and a lot of courage to move in the opposite direction.
- Albert Einstein
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From skenny at uchicago.edu Tue Apr 5 14:38:50 2011
From: skenny at uchicago.edu (Sarah Kenny)
Date: Tue, 5 Apr 2011 12:38:50 -0700
Subject: [Swift-devel] Re: Can you test 0.92 branch for 0.92.1 release?
In-Reply-To:
References:
<1046706498.67103.1302032022991.JavaMail.root@zimbra.anl.gov>
Message-ID:
got it thanks...to be clear i wasn't going to try to run the whole montage
scripit :P but this is easier than extracting the faulty loop :)
On Tue, Apr 5, 2011 at 12:37 PM, Jonathan Monette wrote:
> Yes. That is the one I remember seeing. That is much easier than what my
> Montage scripts are doing.
>
>
> On Tue, Apr 5, 2011 at 2:33 PM, Michael Wilde wrote:
>
>> Yes, I had posted variations of the following to the list:
>>
>> zz3.swift:
>>
>> int arr[];
>>
>> arr[0]=1;
>> arr[1]=2;
>>
>> foreach a in arr {
>> trace("for", a);
>> }
>>
>> zz6.swift:
>>
>>
>> int arr[];
>>
>> foreach a,i in [0:9] {
>> arr[i] = i;
>> }
>>
>> trace("arr",arr);
>>
>> foreach a,i in arr {
>> trace("for", a,i);
>> }
>>
>>
>> com$
>> PATH=/home/wilde/swift/src/0.92/cog/modules/swift/dist/swift-svn/bin/:$PATH
>> com$ which swift
>> ~/swift/src/0.92/cog/modules/swift/dist/swift-svn/bin/swift
>> com$ cd swift/lab
>> com$ swift zz3.swift
>> Swift svn swift-r4252 (swift modified locally) cog-r3088 (cog modified
>> locally)
>>
>> RunID: 20110404-1344-j98f22id
>> Progress:
>> SwiftScript trace: for, 2
>> SwiftScript trace: for, 1
>> Final status:
>> com$ PATH=~/swift/rev/swift-0.92/bin:$PATH
>> com$ swift zz3.swift
>> Swift svn swift-r4157 cog-r3056
>>
>> RunID: 20110404-1344-ensm4te8
>> Progress:
>> SwiftScript trace: for, 1
>> SwiftScript trace: for, 2
>> SwiftScript trace: for, 2
>> SwiftScript trace: for, 1
>> Final status:
>> com$ swift zz6.swift
>> Swift svn swift-r4157 cog-r3056
>>
>> RunID: 20110404-1344-i7y6q1i1
>> Progress:
>> SwiftScript trace: arr, arr.$[]/10
>> SwiftScript trace: for, 3, 3
>> SwiftScript trace: for, 2, 2
>> SwiftScript trace: for, 4, 4
>> SwiftScript trace: for, 5, 5
>> SwiftScript trace: for, 3, 3
>> SwiftScript trace: for, 5, 5
>> SwiftScript trace: for, 9, 9
>> SwiftScript trace: for, 4, 4
>> SwiftScript trace: for, 1, 1
>> SwiftScript trace: for, 7, 7
>> SwiftScript trace: for, 7, 7
>> SwiftScript trace: for, 6, 6
>> SwiftScript trace: for, 9, 9
>> SwiftScript trace: for, 6, 6
>> SwiftScript trace: for, 1, 1
>> SwiftScript trace: for, 2, 2
>> SwiftScript trace: for, 0, 0
>> SwiftScript trace: for, 8, 8
>> SwiftScript trace: for, 0, 0
>> SwiftScript trace: for, 8, 8
>> Final status:
>> com$
>>
>>
>>
>>
>>
>>
>> ----- Original Message -----
>> > The script I posted might be too complex to use to replicate the twice
>> > each bug. However, didn't Mike post a simple loop script that was
>> > looping twice when the bug was initially found?
>> >
>> >
>> > On Tue, Apr 5, 2011 at 2:17 PM, Ketan Maheshwari <
>> > ketancmaheshwari at gmail.com > wrote:
>> >
>> >
>> >
>> > Sarah,
>> >
>> >
>> > I do not have the test you are asking for yet. I am looking at the
>> > test suite and will start on Beagle soon.
>> >
>> >
>> > Ketan
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > On Apr 5, 2011, at 2:13 PM, Sarah Kenny wrote:
>> >
>> >
>> > i'm currently working on a swift script to replicate the bug for .92
>> > which i will then commit to svn in the test suite. if you mike, or
>> > ketan already have this let me know (i'm trying to hack the script jon
>> > posted to the list) and i'll use yours...david said he doesn't have
>> > one.
>> >
>> > as i said, my plan was to test on ranger, abe and a couple of (uci)
>> > local workstations.
>> >
>> > ~sk
>> >
>> >
>> > On Tue, Apr 5, 2011 at 12:10 PM, Michael Wilde < wilde at mcs.anl.gov >
>> > wrote:
>> >
>> >
>> > David, Sarah, Ketan,
>> >
>> > Can you all report back to the devel list on your progress on testing
>> > the release? Ie, what systems are you testing, and which of those
>> > tests are complete? When will the rest be done, and hence when are we
>> > ready to tag and release the fix?
>> >
>> > I asked who will create the test to confirm that the twice-each bug is
>> > fixed, but no one responded. Which of the three of you feel you know
>> > how to do this? Is this being tested in your new tests?
>> >
>> > Ketan tells me that in the 0.92+ interim release I made for Beagle it
>> > looks like the resume feature is not working. I was aware that such a
>> > bug was reported in trunk, but in the original 0.92 Cray version
>> > (under /home/wilde/swift/rev) resume *was* working. Does the test
>> > suite test the resume feature at the moment?
>> >
>> > Lastly, who will tag and upload the new release, remove or change the
>> > red warning in the download page, and announce 0.92.1 on swift-user?
>> >
>> > - Mike
>> >
>> >
>> >
>> >
>> >
>> > ----- Original Message -----
>> > > Thanks, David. Please cc all discussion of this sort to swift-devel.
>> > >
>> > > I assume SVN is working for you now? (It was working for me, from
>> > > communicadao, around 9AM this morning).
>> > >
>> > > - Mike
>> > >
>> > >
>> > > ----- Original Message -----
>> > > > It appears that there may be a problem with svn.ci.uchicago.edu .
>> > > > I
>> > > > am
>> > > > unable to connect from an SVN client or through the web interface
>> > > > -
>> > > > both attempts just hang indefinitely. I have sent an email to
>> > > > support
>> > > > (ticket 12539), but just wanted to give you guys a heads up that
>> > > > there
>> > > > may be an issue there. I will try to run the tests again in the
>> > > > morning.
>> > > >
>> > > > David
>> > > >
>> > > >
>> > > > On Mon, Apr 4, 2011 at 2:42 PM, Michael Wilde < wilde at mcs.anl.gov
>> > > > >
>> > > > wrote:
>> > > >
>> > > >
>> > > > David, Sarah,
>> > > >
>> > > > How quickly could you re-divide the Swift site test plan between
>> > > > you
>> > > > and confirm back to swift-devel that we are ready to tag and
>> > > > release
>> > > > the branch as 0.92.1?
>> > > >
>> > > > Before we do that, you need to add a test to the test suite that
>> > > > can
>> > > > replicate the twice-each bug and verify that its detected in 0.92
>> > > > and
>> > > > corrected in 0.92.1
>> > > >
>> > > > Can you possibly do this by noon tomorrow?
>> > > >
>> > > > Can you post a checklist of tests with names of who's going to run
>> > > > them?
>> > > >
>> > > > Depending on what you can commit to, I will see if I, Ketan,
>> > > > and/or
>> > > > Justin can help take various sites as well. I feel we really need
>> > > > to
>> > > > do this quickly so we have a stable trusted release out there.
>> > > >
>> > > >
>> > > >
>> > > > Thanks,
>> > > >
>> > > > Mike
>> > > >
>> > > > --
>> > > > Michael Wilde
>> > > > Computation Institute, University of Chicago
>> > > > Mathematics and Computer Science Division
>> > > > Argonne National Laboratory
>> > >
>> > > --
>> > > Michael Wilde
>> > > Computation Institute, University of Chicago
>> > > Mathematics and Computer Science Division
>> > > Argonne National Laboratory
>> > >
>> > > _______________________________________________
>> > > Swift-devel mailing list
>> > > Swift-devel at ci.uchicago.edu
>> > > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>> >
>> > --
>> >
>> >
>> >
>> > Michael Wilde
>> > Computation Institute, University of Chicago
>> > Mathematics and Computer Science Division
>> > Argonne National Laboratory
>> >
>> >
>> >
>> >
>> > _______________________________________________
>> > Swift-devel mailing list
>> > Swift-devel at ci.uchicago.edu
>> > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>> >
>> >
>> >
>> >
>> > --
>> > Any intelligent fool can make things bigger and more complex... It
>> > takes a touch of genius - and a lot of courage to move in the opposite
>> > direction.
>> > - Albert Einstein
>> >
>> >
>> >
>> > _______________________________________________
>> > Swift-devel mailing list
>> > Swift-devel at ci.uchicago.edu
>> > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>>
>> --
>> Michael Wilde
>> Computation Institute, University of Chicago
>> Mathematics and Computer Science Division
>> Argonne National Laboratory
>>
>>
>
>
> --
> Any intelligent fool can make things bigger and more complex... It takes a
> touch of genius - and a lot of courage to move in the opposite direction.
> - Albert Einstein
>
>
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From wilde at mcs.anl.gov Tue Apr 5 14:50:08 2011
From: wilde at mcs.anl.gov (Michael Wilde)
Date: Tue, 5 Apr 2011 14:50:08 -0500 (CDT)
Subject: [Swift-devel] Re: Can you test 0.92 branch for 0.92.1 release?
In-Reply-To:
Message-ID: <1305237903.67225.1302033008679.JavaMail.root@zimbra.anl.gov>
Just to clarify: we detected this bug by diagnosing the error that Allan was getting in his SCEC workflow, trying to add a file to a local cache that was already there.
I never verified if the same bug was causing failures in Montage, but Jon reported Apr 4 12:04 AM that the small Montage was working under the fixed 0.92 branch and that the large Montage run was still to be tested.
- Mike
----- Original Message -----
> got it thanks...to be clear i wasn't going to try to run the whole
> montage scripit :P but this is easier than extracting the faulty loop
> :)
>
>
> On Tue, Apr 5, 2011 at 12:37 PM, Jonathan Monette <
> jon.monette at gmail.com > wrote:
>
>
> Yes. That is the one I remember seeing. That is much easier than what
> my Montage scripts are doing.
>
>
>
>
>
> On Tue, Apr 5, 2011 at 2:33 PM, Michael Wilde < wilde at mcs.anl.gov >
> wrote:
>
>
> Yes, I had posted variations of the following to the list:
>
> zz3.swift:
>
> int arr[];
>
> arr[0]=1;
> arr[1]=2;
>
> foreach a in arr {
> trace("for", a);
> }
>
> zz6.swift:
>
>
> int arr[];
>
> foreach a,i in [0:9] {
> arr[i] = i;
> }
>
> trace("arr",arr);
>
> foreach a,i in arr {
> trace("for", a,i);
> }
>
>
> com$
> PATH=/home/wilde/swift/src/0.92/cog/modules/swift/dist/swift-svn/bin/:$PATH
> com$ which swift
> ~/swift/src/0.92/cog/modules/swift/dist/swift-svn/bin/swift
> com$ cd swift/lab
> com$ swift zz3.swift
> Swift svn swift-r4252 (swift modified locally) cog-r3088 (cog modified
> locally)
>
> RunID: 20110404-1344-j98f22id
> Progress:
> SwiftScript trace: for, 2
> SwiftScript trace: for, 1
> Final status:
> com$ PATH=~/swift/rev/swift-0.92/bin:$PATH
> com$ swift zz3.swift
> Swift svn swift-r4157 cog-r3056
>
> RunID: 20110404-1344-ensm4te8
> Progress:
> SwiftScript trace: for, 1
> SwiftScript trace: for, 2
> SwiftScript trace: for, 2
> SwiftScript trace: for, 1
> Final status:
> com$ swift zz6.swift
> Swift svn swift-r4157 cog-r3056
>
> RunID: 20110404-1344-i7y6q1i1
> Progress:
> SwiftScript trace: arr, arr.$[]/10
> SwiftScript trace: for, 3, 3
> SwiftScript trace: for, 2, 2
> SwiftScript trace: for, 4, 4
> SwiftScript trace: for, 5, 5
> SwiftScript trace: for, 3, 3
> SwiftScript trace: for, 5, 5
> SwiftScript trace: for, 9, 9
> SwiftScript trace: for, 4, 4
> SwiftScript trace: for, 1, 1
> SwiftScript trace: for, 7, 7
> SwiftScript trace: for, 7, 7
> SwiftScript trace: for, 6, 6
> SwiftScript trace: for, 9, 9
> SwiftScript trace: for, 6, 6
> SwiftScript trace: for, 1, 1
> SwiftScript trace: for, 2, 2
> SwiftScript trace: for, 0, 0
> SwiftScript trace: for, 8, 8
> SwiftScript trace: for, 0, 0
> SwiftScript trace: for, 8, 8
> Final status:
> com$
>
>
>
>
>
>
>
>
>
> ----- Original Message -----
> > The script I posted might be too complex to use to replicate the
> > twice
> > each bug. However, didn't Mike post a simple loop script that was
> > looping twice when the bug was initially found?
> >
> >
> > On Tue, Apr 5, 2011 at 2:17 PM, Ketan Maheshwari <
> > ketancmaheshwari at gmail.com > wrote:
> >
> >
> >
> > Sarah,
> >
> >
> > I do not have the test you are asking for yet. I am looking at the
> > test suite and will start on Beagle soon.
> >
> >
> > Ketan
> >
> >
> >
> >
> >
> >
> >
> > On Apr 5, 2011, at 2:13 PM, Sarah Kenny wrote:
> >
> >
> > i'm currently working on a swift script to replicate the bug for .92
> > which i will then commit to svn in the test suite. if you mike, or
> > ketan already have this let me know (i'm trying to hack the script
> > jon
> > posted to the list) and i'll use yours...david said he doesn't have
> > one.
> >
> > as i said, my plan was to test on ranger, abe and a couple of (uci)
> > local workstations.
> >
> > ~sk
> >
> >
> > On Tue, Apr 5, 2011 at 12:10 PM, Michael Wilde < wilde at mcs.anl.gov >
> > wrote:
> >
> >
> > David, Sarah, Ketan,
> >
> > Can you all report back to the devel list on your progress on
> > testing
> > the release? Ie, what systems are you testing, and which of those
> > tests are complete? When will the rest be done, and hence when are
> > we
> > ready to tag and release the fix?
> >
> > I asked who will create the test to confirm that the twice-each bug
> > is
> > fixed, but no one responded. Which of the three of you feel you know
> > how to do this? Is this being tested in your new tests?
> >
> > Ketan tells me that in the 0.92+ interim release I made for Beagle
> > it
> > looks like the resume feature is not working. I was aware that such
> > a
> > bug was reported in trunk, but in the original 0.92 Cray version
> > (under /home/wilde/swift/rev) resume *was* working. Does the test
> > suite test the resume feature at the moment?
> >
> > Lastly, who will tag and upload the new release, remove or change
> > the
> > red warning in the download page, and announce 0.92.1 on swift-user?
> >
> > - Mike
> >
> >
> >
> >
> >
> > ----- Original Message -----
> > > Thanks, David. Please cc all discussion of this sort to
> > > swift-devel.
> > >
> > > I assume SVN is working for you now? (It was working for me, from
> > > communicadao, around 9AM this morning).
> > >
> > > - Mike
> > >
> > >
> > > ----- Original Message -----
> > > > It appears that there may be a problem with svn.ci.uchicago.edu
> > > > .
> > > > I
> > > > am
> > > > unable to connect from an SVN client or through the web
> > > > interface
> > > > -
> > > > both attempts just hang indefinitely. I have sent an email to
> > > > support
> > > > (ticket 12539), but just wanted to give you guys a heads up that
> > > > there
> > > > may be an issue there. I will try to run the tests again in the
> > > > morning.
> > > >
> > > > David
> > > >
> > > >
> > > > On Mon, Apr 4, 2011 at 2:42 PM, Michael Wilde <
> > > > wilde at mcs.anl.gov
> > > > >
> > > > wrote:
> > > >
> > > >
> > > > David, Sarah,
> > > >
> > > > How quickly could you re-divide the Swift site test plan between
> > > > you
> > > > and confirm back to swift-devel that we are ready to tag and
> > > > release
> > > > the branch as 0.92.1?
> > > >
> > > > Before we do that, you need to add a test to the test suite that
> > > > can
> > > > replicate the twice-each bug and verify that its detected in
> > > > 0.92
> > > > and
> > > > corrected in 0.92.1
> > > >
> > > > Can you possibly do this by noon tomorrow?
> > > >
> > > > Can you post a checklist of tests with names of who's going to
> > > > run
> > > > them?
> > > >
> > > > Depending on what you can commit to, I will see if I, Ketan,
> > > > and/or
> > > > Justin can help take various sites as well. I feel we really
> > > > need
> > > > to
> > > > do this quickly so we have a stable trusted release out there.
> > > >
> > > >
> > > >
> > > > Thanks,
> > > >
> > > > Mike
> > > >
> > > > --
> > > > Michael Wilde
> > > > Computation Institute, University of Chicago
> > > > Mathematics and Computer Science Division
> > > > Argonne National Laboratory
> > >
> > > --
> > > Michael Wilde
> > > Computation Institute, University of Chicago
> > > Mathematics and Computer Science Division
> > > Argonne National Laboratory
> > >
> > > _______________________________________________
> > > Swift-devel mailing list
> > > Swift-devel at ci.uchicago.edu
> > > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> >
> > --
> >
> >
> >
> > Michael Wilde
> > Computation Institute, University of Chicago
> > Mathematics and Computer Science Division
> > Argonne National Laboratory
> >
> >
> >
> >
> > _______________________________________________
> > Swift-devel mailing list
> > Swift-devel at ci.uchicago.edu
> > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> >
> >
> >
> >
> > --
> > Any intelligent fool can make things bigger and more complex... It
> > takes a touch of genius - and a lot of courage to move in the
> > opposite
> > direction.
> > - Albert Einstein
> >
> >
> >
> > _______________________________________________
> > Swift-devel mailing list
> > Swift-devel at ci.uchicago.edu
> > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>
> --
> Michael Wilde
> Computation Institute, University of Chicago
> Mathematics and Computer Science Division
> Argonne National Laboratory
>
>
>
>
> --
>
>
>
> Any intelligent fool can make things bigger and more complex... It
> takes a touch of genius - and a lot of courage to move in the opposite
> direction.
> - Albert Einstein
>
>
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
From jon.monette at gmail.com Tue Apr 5 14:57:39 2011
From: jon.monette at gmail.com (Jonathan Monette)
Date: Tue, 5 Apr 2011 14:57:39 -0500
Subject: [Swift-devel] Re: Can you test 0.92 branch for 0.92.1 release?
In-Reply-To: <1305237903.67225.1302033008679.JavaMail.root@zimbra.anl.gov>
References:
<1305237903.67225.1302033008679.JavaMail.root@zimbra.anl.gov>
Message-ID:
Correct. Based off how I was looping I was receiving the same cache error
that Allan was receiving. Also, I never though of this but my Montage
scripts were running very slowly in the trunk at some point(I am assuming
this was the point that the twice each bug was introduced and everything was
being done twice). Under the 0.92 branch by small workflows complete. My
large workflows error out with PBS error 254 I believe. Cannot remember the
error code but believe it was this one. But this is not due to the twice
each bug.
On Tue, Apr 5, 2011 at 2:50 PM, Michael Wilde wrote:
> Just to clarify: we detected this bug by diagnosing the error that Allan
> was getting in his SCEC workflow, trying to add a file to a local cache that
> was already there.
>
> I never verified if the same bug was causing failures in Montage, but Jon
> reported Apr 4 12:04 AM that the small Montage was working under the fixed
> 0.92 branch and that the large Montage run was still to be tested.
>
> - Mike
>
> ----- Original Message -----
> > got it thanks...to be clear i wasn't going to try to run the whole
> > montage scripit :P but this is easier than extracting the faulty loop
> > :)
> >
> >
> > On Tue, Apr 5, 2011 at 12:37 PM, Jonathan Monette <
> > jon.monette at gmail.com > wrote:
> >
> >
> > Yes. That is the one I remember seeing. That is much easier than what
> > my Montage scripts are doing.
> >
> >
> >
> >
> >
> > On Tue, Apr 5, 2011 at 2:33 PM, Michael Wilde < wilde at mcs.anl.gov >
> > wrote:
> >
> >
> > Yes, I had posted variations of the following to the list:
> >
> > zz3.swift:
> >
> > int arr[];
> >
> > arr[0]=1;
> > arr[1]=2;
> >
> > foreach a in arr {
> > trace("for", a);
> > }
> >
> > zz6.swift:
> >
> >
> > int arr[];
> >
> > foreach a,i in [0:9] {
> > arr[i] = i;
> > }
> >
> > trace("arr",arr);
> >
> > foreach a,i in arr {
> > trace("for", a,i);
> > }
> >
> >
> > com$
> >
> PATH=/home/wilde/swift/src/0.92/cog/modules/swift/dist/swift-svn/bin/:$PATH
> > com$ which swift
> > ~/swift/src/0.92/cog/modules/swift/dist/swift-svn/bin/swift
> > com$ cd swift/lab
> > com$ swift zz3.swift
> > Swift svn swift-r4252 (swift modified locally) cog-r3088 (cog modified
> > locally)
> >
> > RunID: 20110404-1344-j98f22id
> > Progress:
> > SwiftScript trace: for, 2
> > SwiftScript trace: for, 1
> > Final status:
> > com$ PATH=~/swift/rev/swift-0.92/bin:$PATH
> > com$ swift zz3.swift
> > Swift svn swift-r4157 cog-r3056
> >
> > RunID: 20110404-1344-ensm4te8
> > Progress:
> > SwiftScript trace: for, 1
> > SwiftScript trace: for, 2
> > SwiftScript trace: for, 2
> > SwiftScript trace: for, 1
> > Final status:
> > com$ swift zz6.swift
> > Swift svn swift-r4157 cog-r3056
> >
> > RunID: 20110404-1344-i7y6q1i1
> > Progress:
> > SwiftScript trace: arr, arr.$[]/10
> > SwiftScript trace: for, 3, 3
> > SwiftScript trace: for, 2, 2
> > SwiftScript trace: for, 4, 4
> > SwiftScript trace: for, 5, 5
> > SwiftScript trace: for, 3, 3
> > SwiftScript trace: for, 5, 5
> > SwiftScript trace: for, 9, 9
> > SwiftScript trace: for, 4, 4
> > SwiftScript trace: for, 1, 1
> > SwiftScript trace: for, 7, 7
> > SwiftScript trace: for, 7, 7
> > SwiftScript trace: for, 6, 6
> > SwiftScript trace: for, 9, 9
> > SwiftScript trace: for, 6, 6
> > SwiftScript trace: for, 1, 1
> > SwiftScript trace: for, 2, 2
> > SwiftScript trace: for, 0, 0
> > SwiftScript trace: for, 8, 8
> > SwiftScript trace: for, 0, 0
> > SwiftScript trace: for, 8, 8
> > Final status:
> > com$
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > ----- Original Message -----
> > > The script I posted might be too complex to use to replicate the
> > > twice
> > > each bug. However, didn't Mike post a simple loop script that was
> > > looping twice when the bug was initially found?
> > >
> > >
> > > On Tue, Apr 5, 2011 at 2:17 PM, Ketan Maheshwari <
> > > ketancmaheshwari at gmail.com > wrote:
> > >
> > >
> > >
> > > Sarah,
> > >
> > >
> > > I do not have the test you are asking for yet. I am looking at the
> > > test suite and will start on Beagle soon.
> > >
> > >
> > > Ketan
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > On Apr 5, 2011, at 2:13 PM, Sarah Kenny wrote:
> > >
> > >
> > > i'm currently working on a swift script to replicate the bug for .92
> > > which i will then commit to svn in the test suite. if you mike, or
> > > ketan already have this let me know (i'm trying to hack the script
> > > jon
> > > posted to the list) and i'll use yours...david said he doesn't have
> > > one.
> > >
> > > as i said, my plan was to test on ranger, abe and a couple of (uci)
> > > local workstations.
> > >
> > > ~sk
> > >
> > >
> > > On Tue, Apr 5, 2011 at 12:10 PM, Michael Wilde < wilde at mcs.anl.gov >
> > > wrote:
> > >
> > >
> > > David, Sarah, Ketan,
> > >
> > > Can you all report back to the devel list on your progress on
> > > testing
> > > the release? Ie, what systems are you testing, and which of those
> > > tests are complete? When will the rest be done, and hence when are
> > > we
> > > ready to tag and release the fix?
> > >
> > > I asked who will create the test to confirm that the twice-each bug
> > > is
> > > fixed, but no one responded. Which of the three of you feel you know
> > > how to do this? Is this being tested in your new tests?
> > >
> > > Ketan tells me that in the 0.92+ interim release I made for Beagle
> > > it
> > > looks like the resume feature is not working. I was aware that such
> > > a
> > > bug was reported in trunk, but in the original 0.92 Cray version
> > > (under /home/wilde/swift/rev) resume *was* working. Does the test
> > > suite test the resume feature at the moment?
> > >
> > > Lastly, who will tag and upload the new release, remove or change
> > > the
> > > red warning in the download page, and announce 0.92.1 on swift-user?
> > >
> > > - Mike
> > >
> > >
> > >
> > >
> > >
> > > ----- Original Message -----
> > > > Thanks, David. Please cc all discussion of this sort to
> > > > swift-devel.
> > > >
> > > > I assume SVN is working for you now? (It was working for me, from
> > > > communicadao, around 9AM this morning).
> > > >
> > > > - Mike
> > > >
> > > >
> > > > ----- Original Message -----
> > > > > It appears that there may be a problem with svn.ci.uchicago.edu
> > > > > .
> > > > > I
> > > > > am
> > > > > unable to connect from an SVN client or through the web
> > > > > interface
> > > > > -
> > > > > both attempts just hang indefinitely. I have sent an email to
> > > > > support
> > > > > (ticket 12539), but just wanted to give you guys a heads up that
> > > > > there
> > > > > may be an issue there. I will try to run the tests again in the
> > > > > morning.
> > > > >
> > > > > David
> > > > >
> > > > >
> > > > > On Mon, Apr 4, 2011 at 2:42 PM, Michael Wilde <
> > > > > wilde at mcs.anl.gov
> > > > > >
> > > > > wrote:
> > > > >
> > > > >
> > > > > David, Sarah,
> > > > >
> > > > > How quickly could you re-divide the Swift site test plan between
> > > > > you
> > > > > and confirm back to swift-devel that we are ready to tag and
> > > > > release
> > > > > the branch as 0.92.1?
> > > > >
> > > > > Before we do that, you need to add a test to the test suite that
> > > > > can
> > > > > replicate the twice-each bug and verify that its detected in
> > > > > 0.92
> > > > > and
> > > > > corrected in 0.92.1
> > > > >
> > > > > Can you possibly do this by noon tomorrow?
> > > > >
> > > > > Can you post a checklist of tests with names of who's going to
> > > > > run
> > > > > them?
> > > > >
> > > > > Depending on what you can commit to, I will see if I, Ketan,
> > > > > and/or
> > > > > Justin can help take various sites as well. I feel we really
> > > > > need
> > > > > to
> > > > > do this quickly so we have a stable trusted release out there.
> > > > >
> > > > >
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Mike
> > > > >
> > > > > --
> > > > > Michael Wilde
> > > > > Computation Institute, University of Chicago
> > > > > Mathematics and Computer Science Division
> > > > > Argonne National Laboratory
> > > >
> > > > --
> > > > Michael Wilde
> > > > Computation Institute, University of Chicago
> > > > Mathematics and Computer Science Division
> > > > Argonne National Laboratory
> > > >
> > > > _______________________________________________
> > > > Swift-devel mailing list
> > > > Swift-devel at ci.uchicago.edu
> > > > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> > >
> > > --
> > >
> > >
> > >
> > > Michael Wilde
> > > Computation Institute, University of Chicago
> > > Mathematics and Computer Science Division
> > > Argonne National Laboratory
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > Swift-devel mailing list
> > > Swift-devel at ci.uchicago.edu
> > > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> > >
> > >
> > >
> > >
> > > --
> > > Any intelligent fool can make things bigger and more complex... It
> > > takes a touch of genius - and a lot of courage to move in the
> > > opposite
> > > direction.
> > > - Albert Einstein
> > >
> > >
> > >
> > > _______________________________________________
> > > Swift-devel mailing list
> > > Swift-devel at ci.uchicago.edu
> > > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> >
> > --
> > Michael Wilde
> > Computation Institute, University of Chicago
> > Mathematics and Computer Science Division
> > Argonne National Laboratory
> >
> >
> >
> >
> > --
> >
> >
> >
> > Any intelligent fool can make things bigger and more complex... It
> > takes a touch of genius - and a lot of courage to move in the opposite
> > direction.
> > - Albert Einstein
> >
> >
> >
> > _______________________________________________
> > Swift-devel mailing list
> > Swift-devel at ci.uchicago.edu
> > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>
> --
> Michael Wilde
> Computation Institute, University of Chicago
> Mathematics and Computer Science Division
> Argonne National Laboratory
>
>
--
Any intelligent fool can make things bigger and more complex... It takes a
touch of genius - and a lot of courage to move in the opposite direction.
- Albert Einstein
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From wilde at mcs.anl.gov Tue Apr 5 15:01:19 2011
From: wilde at mcs.anl.gov (Michael Wilde)
Date: Tue, 5 Apr 2011 15:01:19 -0500 (CDT)
Subject: [Swift-devel] Resume not working in 0.92? Please test.
Message-ID: <599769624.67355.1302033679071.JavaMail.root@zimbra.anl.gov>
Ketan, to follow up on your mention to me that resume is not working on the latest 0.92 on Beagle, can you do the following:
Try a simple foreach script (like /home/wilde/swift/lab/catsnsleep) under the old 0.92 Cray version. Say 10 sleeps throttles 1 at a time on localhost.
Hit ^c, then try resume. This *should* work.
Then try same in the fixed 0.92 branch to see if possibly resume is broken there (as it was reported to be in trunk:
https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=273
Then try trunk as well.
Can you check to see if the current test suite has a resume test? If so, please try that as well (or instead of the above). If not, can you add it, and report back to swift-devel what you find on the state of resume?
- Mike
From wilde at mcs.anl.gov Tue Apr 5 15:06:42 2011
From: wilde at mcs.anl.gov (Michael Wilde)
Date: Tue, 5 Apr 2011 15:06:42 -0500 (CDT)
Subject: [Swift-devel] Re: Can you test 0.92 branch for 0.92.1 release?
In-Reply-To:
Message-ID: <417068539.67412.1302034002663.JavaMail.root@zimbra.anl.gov>
Jon,
PBS Error 254 may be something like app in tc.data is not executable, or app script calls something not found or not executable, or that makes it return non-zero. It falls in that class of error that I just railed about in Bug 321: https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=321
Its not clear to me that the same root problem manifests in exactly the same error codes and messages under varioud providers and configurations, which is another problem that the fix(es) to Big 321 should deal with.
When you fix your 254, could you report back to swift-devel what it was, and either file as a new bug or update Bug 321?
- Mike
----- Original Message -----
> Correct. Based off how I was looping I was receiving the same cache
> error that Allan was receiving. Also, I never though of this but my
> Montage scripts were running very slowly in the trunk at some point(I
> am assuming this was the point that the twice each bug was introduced
> and everything was being done twice). Under the 0.92 branch by small
> workflows complete. My large workflows error out with PBS error 254 I
> believe. Cannot remember the error code but believe it was this one.
> But this is not due to the twice each bug.
>
>
> On Tue, Apr 5, 2011 at 2:50 PM, Michael Wilde < wilde at mcs.anl.gov >
> wrote:
>
>
> Just to clarify: we detected this bug by diagnosing the error that
> Allan was getting in his SCEC workflow, trying to add a file to a
> local cache that was already there.
>
> I never verified if the same bug was causing failures in Montage, but
> Jon reported Apr 4 12:04 AM that the small Montage was working under
> the fixed 0.92 branch and that the large Montage run was still to be
> tested.
>
> - Mike
>
>
>
>
> ----- Original Message -----
> > got it thanks...to be clear i wasn't going to try to run the whole
> > montage scripit :P but this is easier than extracting the faulty
> > loop
> > :)
> >
> >
> > On Tue, Apr 5, 2011 at 12:37 PM, Jonathan Monette <
> > jon.monette at gmail.com > wrote:
> >
> >
> > Yes. That is the one I remember seeing. That is much easier than
> > what
> > my Montage scripts are doing.
> >
> >
> >
> >
> >
> > On Tue, Apr 5, 2011 at 2:33 PM, Michael Wilde < wilde at mcs.anl.gov >
> > wrote:
> >
> >
> > Yes, I had posted variations of the following to the list:
> >
> > zz3.swift:
> >
> > int arr[];
> >
> > arr[0]=1;
> > arr[1]=2;
> >
> > foreach a in arr {
> > trace("for", a);
> > }
> >
> > zz6.swift:
> >
> >
> > int arr[];
> >
> > foreach a,i in [0:9] {
> > arr[i] = i;
> > }
> >
> > trace("arr",arr);
> >
> > foreach a,i in arr {
> > trace("for", a,i);
> > }
> >
> >
> > com$
> > PATH=/home/wilde/swift/src/0.92/cog/modules/swift/dist/swift-svn/bin/:$PATH
> > com$ which swift
> > ~/swift/src/0.92/cog/modules/swift/dist/swift-svn/bin/swift
> > com$ cd swift/lab
> > com$ swift zz3.swift
> > Swift svn swift-r4252 (swift modified locally) cog-r3088 (cog
> > modified
> > locally)
> >
> > RunID: 20110404-1344-j98f22id
> > Progress:
> > SwiftScript trace: for, 2
> > SwiftScript trace: for, 1
> > Final status:
> > com$ PATH=~/swift/rev/swift-0.92/bin:$PATH
> > com$ swift zz3.swift
> > Swift svn swift-r4157 cog-r3056
> >
> > RunID: 20110404-1344-ensm4te8
> > Progress:
> > SwiftScript trace: for, 1
> > SwiftScript trace: for, 2
> > SwiftScript trace: for, 2
> > SwiftScript trace: for, 1
> > Final status:
> > com$ swift zz6.swift
> > Swift svn swift-r4157 cog-r3056
> >
> > RunID: 20110404-1344-i7y6q1i1
> > Progress:
> > SwiftScript trace: arr, arr.$[]/10
> > SwiftScript trace: for, 3, 3
> > SwiftScript trace: for, 2, 2
> > SwiftScript trace: for, 4, 4
> > SwiftScript trace: for, 5, 5
> > SwiftScript trace: for, 3, 3
> > SwiftScript trace: for, 5, 5
> > SwiftScript trace: for, 9, 9
> > SwiftScript trace: for, 4, 4
> > SwiftScript trace: for, 1, 1
> > SwiftScript trace: for, 7, 7
> > SwiftScript trace: for, 7, 7
> > SwiftScript trace: for, 6, 6
> > SwiftScript trace: for, 9, 9
> > SwiftScript trace: for, 6, 6
> > SwiftScript trace: for, 1, 1
> > SwiftScript trace: for, 2, 2
> > SwiftScript trace: for, 0, 0
> > SwiftScript trace: for, 8, 8
> > SwiftScript trace: for, 0, 0
> > SwiftScript trace: for, 8, 8
> > Final status:
> > com$
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > ----- Original Message -----
> > > The script I posted might be too complex to use to replicate the
> > > twice
> > > each bug. However, didn't Mike post a simple loop script that was
> > > looping twice when the bug was initially found?
> > >
> > >
> > > On Tue, Apr 5, 2011 at 2:17 PM, Ketan Maheshwari <
> > > ketancmaheshwari at gmail.com > wrote:
> > >
> > >
> > >
> > > Sarah,
> > >
> > >
> > > I do not have the test you are asking for yet. I am looking at the
> > > test suite and will start on Beagle soon.
> > >
> > >
> > > Ketan
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > On Apr 5, 2011, at 2:13 PM, Sarah Kenny wrote:
> > >
> > >
> > > i'm currently working on a swift script to replicate the bug for
> > > .92
> > > which i will then commit to svn in the test suite. if you mike, or
> > > ketan already have this let me know (i'm trying to hack the script
> > > jon
> > > posted to the list) and i'll use yours...david said he doesn't
> > > have
> > > one.
> > >
> > > as i said, my plan was to test on ranger, abe and a couple of
> > > (uci)
> > > local workstations.
> > >
> > > ~sk
> > >
> > >
> > > On Tue, Apr 5, 2011 at 12:10 PM, Michael Wilde < wilde at mcs.anl.gov
> > > >
> > > wrote:
> > >
> > >
> > > David, Sarah, Ketan,
> > >
> > > Can you all report back to the devel list on your progress on
> > > testing
> > > the release? Ie, what systems are you testing, and which of those
> > > tests are complete? When will the rest be done, and hence when are
> > > we
> > > ready to tag and release the fix?
> > >
> > > I asked who will create the test to confirm that the twice-each
> > > bug
> > > is
> > > fixed, but no one responded. Which of the three of you feel you
> > > know
> > > how to do this? Is this being tested in your new tests?
> > >
> > > Ketan tells me that in the 0.92+ interim release I made for Beagle
> > > it
> > > looks like the resume feature is not working. I was aware that
> > > such
> > > a
> > > bug was reported in trunk, but in the original 0.92 Cray version
> > > (under /home/wilde/swift/rev) resume *was* working. Does the test
> > > suite test the resume feature at the moment?
> > >
> > > Lastly, who will tag and upload the new release, remove or change
> > > the
> > > red warning in the download page, and announce 0.92.1 on
> > > swift-user?
> > >
> > > - Mike
> > >
> > >
> > >
> > >
> > >
> > > ----- Original Message -----
> > > > Thanks, David. Please cc all discussion of this sort to
> > > > swift-devel.
> > > >
> > > > I assume SVN is working for you now? (It was working for me,
> > > > from
> > > > communicadao, around 9AM this morning).
> > > >
> > > > - Mike
> > > >
> > > >
> > > > ----- Original Message -----
> > > > > It appears that there may be a problem with
> > > > > svn.ci.uchicago.edu
> > > > > .
> > > > > I
> > > > > am
> > > > > unable to connect from an SVN client or through the web
> > > > > interface
> > > > > -
> > > > > both attempts just hang indefinitely. I have sent an email to
> > > > > support
> > > > > (ticket 12539), but just wanted to give you guys a heads up
> > > > > that
> > > > > there
> > > > > may be an issue there. I will try to run the tests again in
> > > > > the
> > > > > morning.
> > > > >
> > > > > David
> > > > >
> > > > >
> > > > > On Mon, Apr 4, 2011 at 2:42 PM, Michael Wilde <
> > > > > wilde at mcs.anl.gov
> > > > > >
> > > > > wrote:
> > > > >
> > > > >
> > > > > David, Sarah,
> > > > >
> > > > > How quickly could you re-divide the Swift site test plan
> > > > > between
> > > > > you
> > > > > and confirm back to swift-devel that we are ready to tag and
> > > > > release
> > > > > the branch as 0.92.1?
> > > > >
> > > > > Before we do that, you need to add a test to the test suite
> > > > > that
> > > > > can
> > > > > replicate the twice-each bug and verify that its detected in
> > > > > 0.92
> > > > > and
> > > > > corrected in 0.92.1
> > > > >
> > > > > Can you possibly do this by noon tomorrow?
> > > > >
> > > > > Can you post a checklist of tests with names of who's going to
> > > > > run
> > > > > them?
> > > > >
> > > > > Depending on what you can commit to, I will see if I, Ketan,
> > > > > and/or
> > > > > Justin can help take various sites as well. I feel we really
> > > > > need
> > > > > to
> > > > > do this quickly so we have a stable trusted release out there.
> > > > >
> > > > >
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Mike
> > > > >
> > > > > --
> > > > > Michael Wilde
> > > > > Computation Institute, University of Chicago
> > > > > Mathematics and Computer Science Division
> > > > > Argonne National Laboratory
> > > >
> > > > --
> > > > Michael Wilde
> > > > Computation Institute, University of Chicago
> > > > Mathematics and Computer Science Division
> > > > Argonne National Laboratory
> > > >
> > > > _______________________________________________
> > > > Swift-devel mailing list
> > > > Swift-devel at ci.uchicago.edu
> > > > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> > >
> > > --
> > >
> > >
> > >
> > > Michael Wilde
> > > Computation Institute, University of Chicago
> > > Mathematics and Computer Science Division
> > > Argonne National Laboratory
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > Swift-devel mailing list
> > > Swift-devel at ci.uchicago.edu
> > > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> > >
> > >
> > >
> > >
> > > --
> > > Any intelligent fool can make things bigger and more complex... It
> > > takes a touch of genius - and a lot of courage to move in the
> > > opposite
> > > direction.
> > > - Albert Einstein
> > >
> > >
> > >
> > > _______________________________________________
> > > Swift-devel mailing list
> > > Swift-devel at ci.uchicago.edu
> > > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> >
> > --
> > Michael Wilde
> > Computation Institute, University of Chicago
> > Mathematics and Computer Science Division
> > Argonne National Laboratory
> >
> >
> >
> >
> > --
> >
> >
> >
> > Any intelligent fool can make things bigger and more complex... It
> > takes a touch of genius - and a lot of courage to move in the
> > opposite
> > direction.
> > - Albert Einstein
> >
> >
> >
> > _______________________________________________
> > Swift-devel mailing list
> > Swift-devel at ci.uchicago.edu
> > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>
> --
>
>
>
> Michael Wilde
> Computation Institute, University of Chicago
> Mathematics and Computer Science Division
> Argonne National Laboratory
>
>
>
>
> --
> Any intelligent fool can make things bigger and more complex... It
> takes a touch of genius - and a lot of courage to move in the opposite
> direction.
> - Albert Einstein
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
From jon.monette at gmail.com Tue Apr 5 15:14:22 2011
From: jon.monette at gmail.com (Jonathan Monette)
Date: Tue, 5 Apr 2011 15:14:22 -0500
Subject: [Swift-devel] Re: Can you test 0.92 branch for 0.92.1 release?
In-Reply-To: <417068539.67412.1302034002663.JavaMail.root@zimbra.anl.gov>
References:
<417068539.67412.1302034002663.JavaMail.root@zimbra.anl.gov>
Message-ID:
Yes. I will certainly do that. And those are the usual suspects that I
have seen for error 254, but the app I believe is failing do not have any of
those properties. I am re-running the script hoping with some changes that
will hopefully shed more on where it fails. PADS is in maintenance mode.
There are several jobs in the queue and looks like none are even running.
On Tue, Apr 5, 2011 at 3:06 PM, Michael Wilde wrote:
> Jon,
>
> PBS Error 254 may be something like app in tc.data is not executable, or
> app script calls something not found or not executable, or that makes it
> return non-zero. It falls in that class of error that I just railed about in
> Bug 321: https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=321
>
> Its not clear to me that the same root problem manifests in exactly the
> same error codes and messages under varioud providers and configurations,
> which is another problem that the fix(es) to Big 321 should deal with.
>
> When you fix your 254, could you report back to swift-devel what it was,
> and either file as a new bug or update Bug 321?
>
> - Mike
>
>
> ----- Original Message -----
> > Correct. Based off how I was looping I was receiving the same cache
> > error that Allan was receiving. Also, I never though of this but my
> > Montage scripts were running very slowly in the trunk at some point(I
> > am assuming this was the point that the twice each bug was introduced
> > and everything was being done twice). Under the 0.92 branch by small
> > workflows complete. My large workflows error out with PBS error 254 I
> > believe. Cannot remember the error code but believe it was this one.
> > But this is not due to the twice each bug.
> >
> >
> > On Tue, Apr 5, 2011 at 2:50 PM, Michael Wilde < wilde at mcs.anl.gov >
> > wrote:
> >
> >
> > Just to clarify: we detected this bug by diagnosing the error that
> > Allan was getting in his SCEC workflow, trying to add a file to a
> > local cache that was already there.
> >
> > I never verified if the same bug was causing failures in Montage, but
> > Jon reported Apr 4 12:04 AM that the small Montage was working under
> > the fixed 0.92 branch and that the large Montage run was still to be
> > tested.
> >
> > - Mike
> >
> >
> >
> >
> > ----- Original Message -----
> > > got it thanks...to be clear i wasn't going to try to run the whole
> > > montage scripit :P but this is easier than extracting the faulty
> > > loop
> > > :)
> > >
> > >
> > > On Tue, Apr 5, 2011 at 12:37 PM, Jonathan Monette <
> > > jon.monette at gmail.com > wrote:
> > >
> > >
> > > Yes. That is the one I remember seeing. That is much easier than
> > > what
> > > my Montage scripts are doing.
> > >
> > >
> > >
> > >
> > >
> > > On Tue, Apr 5, 2011 at 2:33 PM, Michael Wilde < wilde at mcs.anl.gov >
> > > wrote:
> > >
> > >
> > > Yes, I had posted variations of the following to the list:
> > >
> > > zz3.swift:
> > >
> > > int arr[];
> > >
> > > arr[0]=1;
> > > arr[1]=2;
> > >
> > > foreach a in arr {
> > > trace("for", a);
> > > }
> > >
> > > zz6.swift:
> > >
> > >
> > > int arr[];
> > >
> > > foreach a,i in [0:9] {
> > > arr[i] = i;
> > > }
> > >
> > > trace("arr",arr);
> > >
> > > foreach a,i in arr {
> > > trace("for", a,i);
> > > }
> > >
> > >
> > > com$
> > >
> PATH=/home/wilde/swift/src/0.92/cog/modules/swift/dist/swift-svn/bin/:$PATH
> > > com$ which swift
> > > ~/swift/src/0.92/cog/modules/swift/dist/swift-svn/bin/swift
> > > com$ cd swift/lab
> > > com$ swift zz3.swift
> > > Swift svn swift-r4252 (swift modified locally) cog-r3088 (cog
> > > modified
> > > locally)
> > >
> > > RunID: 20110404-1344-j98f22id
> > > Progress:
> > > SwiftScript trace: for, 2
> > > SwiftScript trace: for, 1
> > > Final status:
> > > com$ PATH=~/swift/rev/swift-0.92/bin:$PATH
> > > com$ swift zz3.swift
> > > Swift svn swift-r4157 cog-r3056
> > >
> > > RunID: 20110404-1344-ensm4te8
> > > Progress:
> > > SwiftScript trace: for, 1
> > > SwiftScript trace: for, 2
> > > SwiftScript trace: for, 2
> > > SwiftScript trace: for, 1
> > > Final status:
> > > com$ swift zz6.swift
> > > Swift svn swift-r4157 cog-r3056
> > >
> > > RunID: 20110404-1344-i7y6q1i1
> > > Progress:
> > > SwiftScript trace: arr, arr.$[]/10
> > > SwiftScript trace: for, 3, 3
> > > SwiftScript trace: for, 2, 2
> > > SwiftScript trace: for, 4, 4
> > > SwiftScript trace: for, 5, 5
> > > SwiftScript trace: for, 3, 3
> > > SwiftScript trace: for, 5, 5
> > > SwiftScript trace: for, 9, 9
> > > SwiftScript trace: for, 4, 4
> > > SwiftScript trace: for, 1, 1
> > > SwiftScript trace: for, 7, 7
> > > SwiftScript trace: for, 7, 7
> > > SwiftScript trace: for, 6, 6
> > > SwiftScript trace: for, 9, 9
> > > SwiftScript trace: for, 6, 6
> > > SwiftScript trace: for, 1, 1
> > > SwiftScript trace: for, 2, 2
> > > SwiftScript trace: for, 0, 0
> > > SwiftScript trace: for, 8, 8
> > > SwiftScript trace: for, 0, 0
> > > SwiftScript trace: for, 8, 8
> > > Final status:
> > > com$
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > ----- Original Message -----
> > > > The script I posted might be too complex to use to replicate the
> > > > twice
> > > > each bug. However, didn't Mike post a simple loop script that was
> > > > looping twice when the bug was initially found?
> > > >
> > > >
> > > > On Tue, Apr 5, 2011 at 2:17 PM, Ketan Maheshwari <
> > > > ketancmaheshwari at gmail.com > wrote:
> > > >
> > > >
> > > >
> > > > Sarah,
> > > >
> > > >
> > > > I do not have the test you are asking for yet. I am looking at the
> > > > test suite and will start on Beagle soon.
> > > >
> > > >
> > > > Ketan
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > On Apr 5, 2011, at 2:13 PM, Sarah Kenny wrote:
> > > >
> > > >
> > > > i'm currently working on a swift script to replicate the bug for
> > > > .92
> > > > which i will then commit to svn in the test suite. if you mike, or
> > > > ketan already have this let me know (i'm trying to hack the script
> > > > jon
> > > > posted to the list) and i'll use yours...david said he doesn't
> > > > have
> > > > one.
> > > >
> > > > as i said, my plan was to test on ranger, abe and a couple of
> > > > (uci)
> > > > local workstations.
> > > >
> > > > ~sk
> > > >
> > > >
> > > > On Tue, Apr 5, 2011 at 12:10 PM, Michael Wilde < wilde at mcs.anl.gov
> > > > >
> > > > wrote:
> > > >
> > > >
> > > > David, Sarah, Ketan,
> > > >
> > > > Can you all report back to the devel list on your progress on
> > > > testing
> > > > the release? Ie, what systems are you testing, and which of those
> > > > tests are complete? When will the rest be done, and hence when are
> > > > we
> > > > ready to tag and release the fix?
> > > >
> > > > I asked who will create the test to confirm that the twice-each
> > > > bug
> > > > is
> > > > fixed, but no one responded. Which of the three of you feel you
> > > > know
> > > > how to do this? Is this being tested in your new tests?
> > > >
> > > > Ketan tells me that in the 0.92+ interim release I made for Beagle
> > > > it
> > > > looks like the resume feature is not working. I was aware that
> > > > such
> > > > a
> > > > bug was reported in trunk, but in the original 0.92 Cray version
> > > > (under /home/wilde/swift/rev) resume *was* working. Does the test
> > > > suite test the resume feature at the moment?
> > > >
> > > > Lastly, who will tag and upload the new release, remove or change
> > > > the
> > > > red warning in the download page, and announce 0.92.1 on
> > > > swift-user?
> > > >
> > > > - Mike
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > ----- Original Message -----
> > > > > Thanks, David. Please cc all discussion of this sort to
> > > > > swift-devel.
> > > > >
> > > > > I assume SVN is working for you now? (It was working for me,
> > > > > from
> > > > > communicadao, around 9AM this morning).
> > > > >
> > > > > - Mike
> > > > >
> > > > >
> > > > > ----- Original Message -----
> > > > > > It appears that there may be a problem with
> > > > > > svn.ci.uchicago.edu
> > > > > > .
> > > > > > I
> > > > > > am
> > > > > > unable to connect from an SVN client or through the web
> > > > > > interface
> > > > > > -
> > > > > > both attempts just hang indefinitely. I have sent an email to
> > > > > > support
> > > > > > (ticket 12539), but just wanted to give you guys a heads up
> > > > > > that
> > > > > > there
> > > > > > may be an issue there. I will try to run the tests again in
> > > > > > the
> > > > > > morning.
> > > > > >
> > > > > > David
> > > > > >
> > > > > >
> > > > > > On Mon, Apr 4, 2011 at 2:42 PM, Michael Wilde <
> > > > > > wilde at mcs.anl.gov
> > > > > > >
> > > > > > wrote:
> > > > > >
> > > > > >
> > > > > > David, Sarah,
> > > > > >
> > > > > > How quickly could you re-divide the Swift site test plan
> > > > > > between
> > > > > > you
> > > > > > and confirm back to swift-devel that we are ready to tag and
> > > > > > release
> > > > > > the branch as 0.92.1?
> > > > > >
> > > > > > Before we do that, you need to add a test to the test suite
> > > > > > that
> > > > > > can
> > > > > > replicate the twice-each bug and verify that its detected in
> > > > > > 0.92
> > > > > > and
> > > > > > corrected in 0.92.1
> > > > > >
> > > > > > Can you possibly do this by noon tomorrow?
> > > > > >
> > > > > > Can you post a checklist of tests with names of who's going to
> > > > > > run
> > > > > > them?
> > > > > >
> > > > > > Depending on what you can commit to, I will see if I, Ketan,
> > > > > > and/or
> > > > > > Justin can help take various sites as well. I feel we really
> > > > > > need
> > > > > > to
> > > > > > do this quickly so we have a stable trusted release out there.
> > > > > >
> > > > > >
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > > Mike
> > > > > >
> > > > > > --
> > > > > > Michael Wilde
> > > > > > Computation Institute, University of Chicago
> > > > > > Mathematics and Computer Science Division
> > > > > > Argonne National Laboratory
> > > > >
> > > > > --
> > > > > Michael Wilde
> > > > > Computation Institute, University of Chicago
> > > > > Mathematics and Computer Science Division
> > > > > Argonne National Laboratory
> > > > >
> > > > > _______________________________________________
> > > > > Swift-devel mailing list
> > > > > Swift-devel at ci.uchicago.edu
> > > > > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> > > >
> > > > --
> > > >
> > > >
> > > >
> > > > Michael Wilde
> > > > Computation Institute, University of Chicago
> > > > Mathematics and Computer Science Division
> > > > Argonne National Laboratory
> > > >
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > Swift-devel mailing list
> > > > Swift-devel at ci.uchicago.edu
> > > > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Any intelligent fool can make things bigger and more complex... It
> > > > takes a touch of genius - and a lot of courage to move in the
> > > > opposite
> > > > direction.
> > > > - Albert Einstein
> > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > Swift-devel mailing list
> > > > Swift-devel at ci.uchicago.edu
> > > > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> > >
> > > --
> > > Michael Wilde
> > > Computation Institute, University of Chicago
> > > Mathematics and Computer Science Division
> > > Argonne National Laboratory
> > >
> > >
> > >
> > >
> > > --
> > >
> > >
> > >
> > > Any intelligent fool can make things bigger and more complex... It
> > > takes a touch of genius - and a lot of courage to move in the
> > > opposite
> > > direction.
> > > - Albert Einstein
> > >
> > >
> > >
> > > _______________________________________________
> > > Swift-devel mailing list
> > > Swift-devel at ci.uchicago.edu
> > > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> >
> > --
> >
> >
> >
> > Michael Wilde
> > Computation Institute, University of Chicago
> > Mathematics and Computer Science Division
> > Argonne National Laboratory
> >
> >
> >
> >
> > --
> > Any intelligent fool can make things bigger and more complex... It
> > takes a touch of genius - and a lot of courage to move in the opposite
> > direction.
> > - Albert Einstein
>
> --
> Michael Wilde
> Computation Institute, University of Chicago
> Mathematics and Computer Science Division
> Argonne National Laboratory
>
>
--
Any intelligent fool can make things bigger and more complex... It takes a
touch of genius - and a lot of courage to move in the opposite direction.
- Albert Einstein
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From ketancmaheshwari at gmail.com Tue Apr 5 16:47:22 2011
From: ketancmaheshwari at gmail.com (Ketan Maheshwari)
Date: Tue, 5 Apr 2011 16:47:22 -0500
Subject: [Swift-devel] Re: Resume not working in 0.92? Please test.
In-Reply-To: <599769624.67355.1302033679071.JavaMail.root@zimbra.anl.gov>
References: <599769624.67355.1302033679071.JavaMail.root@zimbra.anl.gov>
Message-ID: <500F071C-66B5-404E-8DBE-CC284B360861@gmail.com>
Mike,
I tested resume and it is working indeed:
I tested it on local as well as Beagle and it is working well for the latest 0.92 Cray version.
Unfortunately, I did not preserve the old 0.92 branch on Beagle. If you see resume is worth testing for that branch, I will check it out that too.
The resume test does not exist on current test suite. I will add a test and let you know how it goes.
Ketan
On Apr 5, 2011, at 3:01 PM, Michael Wilde wrote:
> Ketan, to follow up on your mention to me that resume is not working on the latest 0.92 on Beagle, can you do the following:
>
> Try a simple foreach script (like /home/wilde/swift/lab/catsnsleep) under the old 0.92 Cray version. Say 10 sleeps throttles 1 at a time on localhost.
>
> Hit ^c, then try resume. This *should* work.
>
> Then try same in the fixed 0.92 branch to see if possibly resume is broken there (as it was reported to be in trunk:
> https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=273
>
> Then try trunk as well.
>
> Can you check to see if the current test suite has a resume test? If so, please try that as well (or instead of the above). If not, can you add it, and report back to swift-devel what you find on the state of resume?
>
> - Mike
>
From wilde at mcs.anl.gov Tue Apr 5 17:16:25 2011
From: wilde at mcs.anl.gov (Michael Wilde)
Date: Tue, 5 Apr 2011 17:16:25 -0500 (CDT)
Subject: [Swift-devel] Re: Resume not working in 0.92? Please test.
In-Reply-To: <500F071C-66B5-404E-8DBE-CC284B360861@gmail.com>
Message-ID: <1278351924.68275.1302041785570.JavaMail.root@zimbra.anl.gov>
OK, very good, Ketan. Resume worked for me in the old Cray 0.92 version, so if it works in the current one, then that is great.
So I'm assuming that your original suspicion that resume does not work in the latest 0.92+ branch was erroneous.
Please test trunk as well, which is the code version that Allan filed bug 273 against.
I see in your modftdock writeup that when you document resume you did not give the same arguments to swift as in the initial invocation. Those are needed for correct resume behavior. The resume feature assumes that the resumed run is running in the exact same environment as the run represented in the rlog.
If you need it for reference, the original Cray 0.92 version is in /home/wilde/swift/rev/swift-r4143+cog-r3056+pbscoast
(but I see little need to test that rev other than to verify that it exhibits the twice-each bug).
- Mike
----- Original Message -----
> Mike,
>
> I tested resume and it is working indeed:
>
> I tested it on local as well as Beagle and it is working well for the
> latest 0.92 Cray version.
>
> Unfortunately, I did not preserve the old 0.92 branch on Beagle. If
> you see resume is worth testing for that branch, I will check it out
> that too.
>
> The resume test does not exist on current test suite. I will add a
> test and let you know how it goes.
>
>
> Ketan
>
> On Apr 5, 2011, at 3:01 PM, Michael Wilde wrote:
>
> > Ketan, to follow up on your mention to me that resume is not working
> > on the latest 0.92 on Beagle, can you do the following:
> >
> > Try a simple foreach script (like /home/wilde/swift/lab/catsnsleep)
> > under the old 0.92 Cray version. Say 10 sleeps throttles 1 at a time
> > on localhost.
> >
> > Hit ^c, then try resume. This *should* work.
> >
> > Then try same in the fixed 0.92 branch to see if possibly resume is
> > broken there (as it was reported to be in trunk:
> > https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=273
> >
> > Then try trunk as well.
> >
> > Can you check to see if the current test suite has a resume test? If
> > so, please try that as well (or instead of the above). If not, can
> > you add it, and report back to swift-devel what you find on the
> > state of resume?
> >
> > - Mike
> >
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
From ketancmaheshwari at gmail.com Tue Apr 5 18:17:57 2011
From: ketancmaheshwari at gmail.com (Ketan Maheshwari)
Date: Tue, 5 Apr 2011 18:17:57 -0500
Subject: [Swift-devel] Re: Resume not working in 0.92? Please test.
In-Reply-To: <599769624.67355.1302033679071.JavaMail.root@zimbra.anl.gov>
References: <599769624.67355.1302033679071.JavaMail.root@zimbra.anl.gov>
Message-ID:
Mike,
I tested and it seems, resume is broken in the trunk. I will go ahead and put a note on Allan's bug report.
Ketan
On Apr 5, 2011, at 3:01 PM, Michael Wilde wrote:
> Ketan, to follow up on your mention to me that resume is not working on the latest 0.92 on Beagle, can you do the following:
>
> Try a simple foreach script (like /home/wilde/swift/lab/catsnsleep) under the old 0.92 Cray version. Say 10 sleeps throttles 1 at a time on localhost.
>
> Hit ^c, then try resume. This *should* work.
>
> Then try same in the fixed 0.92 branch to see if possibly resume is broken there (as it was reported to be in trunk:
> https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=273
>
> Then try trunk as well.
>
> Can you check to see if the current test suite has a resume test? If so, please try that as well (or instead of the above). If not, can you add it, and report back to swift-devel what you find on the state of resume?
>
> - Mike
>
From bugzilla-daemon at mcs.anl.gov Tue Apr 5 18:21:01 2011
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Tue, 5 Apr 2011 18:21:01 -0500 (CDT)
Subject: [Swift-devel] [Bug 273] resume is currently broken
In-Reply-To:
References:
Message-ID: <20110405232101.7FFED2B91A@wind.mcs.anl.gov>
https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=273
ketan changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ketan at mcs.anl.gov
--- Comment #2 from ketan 2011-04-05 18:21:01 ---
I tested for this bug again today (2011-04-05) and it is still broken.
--
Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
From hategan at mcs.anl.gov Tue Apr 5 18:24:16 2011
From: hategan at mcs.anl.gov (Mihael Hategan)
Date: Tue, 05 Apr 2011 16:24:16 -0700
Subject: [Swift-devel] Re: Resume not working in 0.92? Please test.
In-Reply-To:
References: <599769624.67355.1302033679071.JavaMail.root@zimbra.anl.gov>
Message-ID: <1302045856.29787.0.camel@blabla2.none>
On Tue, 2011-04-05 at 18:17 -0500, Ketan Maheshwari wrote:
> Mike,
>
> I tested and it seems, resume is broken in the trunk.
Can't say I'm surprised there. I'll take a look.
From mickelso at mcs.anl.gov Wed Apr 6 09:24:22 2011
From: mickelso at mcs.anl.gov (Sheri Mickelson)
Date: Wed, 06 Apr 2011 09:24:22 -0500
Subject: [Swift-devel] [Bug 291] New: Add a exists() function to test
for file existence
In-Reply-To:
References: <729744535.55640.1301680289613.JavaMail.root@zimbra.anl.gov>
<2A5A416A-CAB6-4D82-B55F-0CFBC8F3B770@ucar.edu>
Message-ID: <4D9C7796.6000608@mcs.anl.gov>
Hi John,
I'm currently working with an older version of swift, not with the trunk.
But I should be able to try it out in a week or so when I start adding ncl to the swift script.
-Sheri
John Dennis wrote:
> Justin,
>
> Thanks for adding this feature. I not currently setup on a system
> with the swift trunk. I suspect Sheri is currently work
> with the trunk. Sheri, could you take a look at this feature during
> your work with swift?
>
> Thanks,
> John
>
> On Apr 3, 2011, at 3:56 PM, Justin M Wozniak wrote:
>
>>
>> Ok, John, you can give this a try in trunk if you like. The syntax
>> for the built-in is @exists, it takes a string and returns a boolean.
>> Justin
>>
>> On Sat, 2 Apr 2011, Justin M Wozniak wrote:
>>
>>>
>>> I have a prototype of this, I'll get it checked in later today.
>>> Justin
>>>
>>> On Fri, 1 Apr 2011, John Dennis wrote:
>>>
>>>> Michael,
>>>>
>>>> This type of function would be great to have.
>>>> John
>>>> On Apr 1, 2011, at 11:51 AM, Michael Wilde wrote:
>>>>> Basically as far as I understand: the presence or absence of a
>>>>> particular data file within the inout dataset is to be used to
>>>>> determine whether the code to process that dataset subsection gets
>>>>> invoked or not:
>>>>> if (exists("extra.data")) {
>>>>> DataFile extraInput<"extra.data">;
>>>>> extraResult = analyze(extraInput);
>>>>> }
>>>>> The above is my assumption based on a phone call. We can and
>>>>> should verify the assumption with a simple example.
>>>>> I also thought we can try this today by seeing if extraInput can be
>>>>> an array, mapped to zero items if nothing to do and 1 item if
>>>>> something to do. That would at least let us test the use case.
>>>>> John, can you verify if the example Swift lines above are what you
>>>>> are looking for here?
>>>>> - Mike
>>>>> ----- Original Message -----
>>>>>> On Fri, 2011-04-01 at 10:51 -0500, Michael Wilde wrote:
>>>>>>> - we should first verify that exists() will solve the NCAR need in a
>>>>>>> sufficiently clean way
>>>>>> I think this is important. Can we get a description of the problem
>>>>>> instead of a (otherwise) random proposal for a solution?
>>>>> --
>>>>> Michael Wilde
>>>>> Computation Institute, University of Chicago
>>>>> Mathematics and Computer Science Division
>>>>> Argonne National Laboratory
>>>> _______________________________________________
>>>> Swift-devel mailing list
>>>> Swift-devel at ci.uchicago.edu
>>>> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>>>
>>>
>>
>> --
>> Justin M Wozniak
>
From bugzilla-daemon at mcs.anl.gov Wed Apr 6 11:52:37 2011
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Wed, 6 Apr 2011 11:52:37 -0500 (CDT)
Subject: [Swift-devel] [Bug 329] New: Improve tutorial content and user flow
for accessing remote sites.
Message-ID:
https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=329
Summary: Improve tutorial content and user flow for accessing
remote sites.
Product: Swift
Version: 0.93
Platform: PC
OS/Version: Mac OS
Status: ASSIGNED
Severity: normal
Priority: P1
Component: Documentation
AssignedTo: dk0966 at cs.ship.edu
ReportedBy: wilde at mcs.anl.gov
By "user flow" I mean how we connect the user from "I want to do X" to the
tutorial material that shows the user how to do it.
This is from an OSG Fermilab user:
On Mon, Feb 28, 2011 at 11:30:57AM -0600, Dave Dykstra wrote:
> Here's another status report on this. I was only able to get a bit
> further on the tutorial, and since then all my ExTENCI time has been
> redirected to the Wide Area Lustre subproject. I need to give a talk
> on that next week at the OSG All Hands Meeting. The week after that
> I should be able to get back to swift.
Mike,
I was still tied up with Lustre until this week. I am continuing on the
swift tutorial this week and got past the bugs in it and got through
section 4.2, "Running on a remote site". That section is so vague as to
be barely of much use, but I did manage to get swift to run a job on an
OSG site (fnal) and just succeeded also on a Teragrid site (queenbee).
I was able to do that with my DOE certificate after finding these helpful
web pages
https://www.teragrid.org/web/user-support/sso_nontgca
http://info.teragrid.org/restdemo/html/tg/services/gram5
I didn't even realize before that Teragrid sites support basically the
same globus interface as OSG sites. That shows how little I knew about
Teragrid.
So I'm not very far from the end of the tutorial now.
- Dave
--
Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the reporter.
From skenny at uchicago.edu Wed Apr 6 12:12:54 2011
From: skenny at uchicago.edu (Sarah Kenny)
Date: Wed, 6 Apr 2011 10:12:54 -0700
Subject: [Swift-devel] svn commit email
Message-ID:
hey all, my svn commits at the moment are generating an email saying my
message (which should just be a post-commit email) is awaiting moderator
approval...anyone else getting this?
~sk
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From jon.monette at gmail.com Wed Apr 6 12:15:45 2011
From: jon.monette at gmail.com (Jonathan Monette)
Date: Wed, 6 Apr 2011 12:15:45 -0500
Subject: [Swift-devel] svn commit email
In-Reply-To:
References:
Message-ID:
Yea. I have gotten them. But it seems for me only if I try to commit to
trunk. I can commit to SwiftApps with out email.
On Apr 6, 2011 12:13 PM, "Sarah Kenny" wrote:
> hey all, my svn commits at the moment are generating an email saying my
> message (which should just be a post-commit email) is awaiting moderator
> approval...anyone else getting this?
>
> ~sk
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From jon.monette at gmail.com Wed Apr 6 12:31:31 2011
From: jon.monette at gmail.com (Jonathan Monette)
Date: Wed, 6 Apr 2011 12:31:31 -0500
Subject: [Swift-devel] Re: Can you test 0.92 branch for 0.92.1 release?
In-Reply-To:
References:
<417068539.67412.1302034002663.JavaMail.root@zimbra.anl.gov>
Message-ID:
Ok. I found the app. It is a wrapper script I have that just makes sure
the the app I call returns exit code 0 and not some other exit code. Some
of the apps run and complete but not all of them. I can only assume it is
still returning an error code so I have to track this down. One thing that
should be changed is when the error 254 occurs that it specifies the name of
the app that failed(or job or something). This will at least help track
down why and where.
On Tue, Apr 5, 2011 at 3:14 PM, Jonathan Monette wrote:
> Yes. I will certainly do that. And those are the usual suspects that I
> have seen for error 254, but the app I believe is failing do not have any of
> those properties. I am re-running the script hoping with some changes that
> will hopefully shed more on where it fails. PADS is in maintenance mode.
> There are several jobs in the queue and looks like none are even running.
>
>
> On Tue, Apr 5, 2011 at 3:06 PM, Michael Wilde wrote:
>
>> Jon,
>>
>> PBS Error 254 may be something like app in tc.data is not executable, or
>> app script calls something not found or not executable, or that makes it
>> return non-zero. It falls in that class of error that I just railed about in
>> Bug 321: https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=321
>>
>> Its not clear to me that the same root problem manifests in exactly the
>> same error codes and messages under varioud providers and configurations,
>> which is another problem that the fix(es) to Big 321 should deal with.
>>
>> When you fix your 254, could you report back to swift-devel what it was,
>> and either file as a new bug or update Bug 321?
>>
>> - Mike
>>
>>
>> ----- Original Message -----
>> > Correct. Based off how I was looping I was receiving the same cache
>> > error that Allan was receiving. Also, I never though of this but my
>> > Montage scripts were running very slowly in the trunk at some point(I
>> > am assuming this was the point that the twice each bug was introduced
>> > and everything was being done twice). Under the 0.92 branch by small
>> > workflows complete. My large workflows error out with PBS error 254 I
>> > believe. Cannot remember the error code but believe it was this one.
>> > But this is not due to the twice each bug.
>> >
>> >
>> > On Tue, Apr 5, 2011 at 2:50 PM, Michael Wilde < wilde at mcs.anl.gov >
>> > wrote:
>> >
>> >
>> > Just to clarify: we detected this bug by diagnosing the error that
>> > Allan was getting in his SCEC workflow, trying to add a file to a
>> > local cache that was already there.
>> >
>> > I never verified if the same bug was causing failures in Montage, but
>> > Jon reported Apr 4 12:04 AM that the small Montage was working under
>> > the fixed 0.92 branch and that the large Montage run was still to be
>> > tested.
>> >
>> > - Mike
>> >
>> >
>> >
>> >
>> > ----- Original Message -----
>> > > got it thanks...to be clear i wasn't going to try to run the whole
>> > > montage scripit :P but this is easier than extracting the faulty
>> > > loop
>> > > :)
>> > >
>> > >
>> > > On Tue, Apr 5, 2011 at 12:37 PM, Jonathan Monette <
>> > > jon.monette at gmail.com > wrote:
>> > >
>> > >
>> > > Yes. That is the one I remember seeing. That is much easier than
>> > > what
>> > > my Montage scripts are doing.
>> > >
>> > >
>> > >
>> > >
>> > >
>> > > On Tue, Apr 5, 2011 at 2:33 PM, Michael Wilde < wilde at mcs.anl.gov >
>> > > wrote:
>> > >
>> > >
>> > > Yes, I had posted variations of the following to the list:
>> > >
>> > > zz3.swift:
>> > >
>> > > int arr[];
>> > >
>> > > arr[0]=1;
>> > > arr[1]=2;
>> > >
>> > > foreach a in arr {
>> > > trace("for", a);
>> > > }
>> > >
>> > > zz6.swift:
>> > >
>> > >
>> > > int arr[];
>> > >
>> > > foreach a,i in [0:9] {
>> > > arr[i] = i;
>> > > }
>> > >
>> > > trace("arr",arr);
>> > >
>> > > foreach a,i in arr {
>> > > trace("for", a,i);
>> > > }
>> > >
>> > >
>> > > com$
>> > >
>> PATH=/home/wilde/swift/src/0.92/cog/modules/swift/dist/swift-svn/bin/:$PATH
>> > > com$ which swift
>> > > ~/swift/src/0.92/cog/modules/swift/dist/swift-svn/bin/swift
>> > > com$ cd swift/lab
>> > > com$ swift zz3.swift
>> > > Swift svn swift-r4252 (swift modified locally) cog-r3088 (cog
>> > > modified
>> > > locally)
>> > >
>> > > RunID: 20110404-1344-j98f22id
>> > > Progress:
>> > > SwiftScript trace: for, 2
>> > > SwiftScript trace: for, 1
>> > > Final status:
>> > > com$ PATH=~/swift/rev/swift-0.92/bin:$PATH
>> > > com$ swift zz3.swift
>> > > Swift svn swift-r4157 cog-r3056
>> > >
>> > > RunID: 20110404-1344-ensm4te8
>> > > Progress:
>> > > SwiftScript trace: for, 1
>> > > SwiftScript trace: for, 2
>> > > SwiftScript trace: for, 2
>> > > SwiftScript trace: for, 1
>> > > Final status:
>> > > com$ swift zz6.swift
>> > > Swift svn swift-r4157 cog-r3056
>> > >
>> > > RunID: 20110404-1344-i7y6q1i1
>> > > Progress:
>> > > SwiftScript trace: arr, arr.$[]/10
>> > > SwiftScript trace: for, 3, 3
>> > > SwiftScript trace: for, 2, 2
>> > > SwiftScript trace: for, 4, 4
>> > > SwiftScript trace: for, 5, 5
>> > > SwiftScript trace: for, 3, 3
>> > > SwiftScript trace: for, 5, 5
>> > > SwiftScript trace: for, 9, 9
>> > > SwiftScript trace: for, 4, 4
>> > > SwiftScript trace: for, 1, 1
>> > > SwiftScript trace: for, 7, 7
>> > > SwiftScript trace: for, 7, 7
>> > > SwiftScript trace: for, 6, 6
>> > > SwiftScript trace: for, 9, 9
>> > > SwiftScript trace: for, 6, 6
>> > > SwiftScript trace: for, 1, 1
>> > > SwiftScript trace: for, 2, 2
>> > > SwiftScript trace: for, 0, 0
>> > > SwiftScript trace: for, 8, 8
>> > > SwiftScript trace: for, 0, 0
>> > > SwiftScript trace: for, 8, 8
>> > > Final status:
>> > > com$
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> > > ----- Original Message -----
>> > > > The script I posted might be too complex to use to replicate the
>> > > > twice
>> > > > each bug. However, didn't Mike post a simple loop script that was
>> > > > looping twice when the bug was initially found?
>> > > >
>> > > >
>> > > > On Tue, Apr 5, 2011 at 2:17 PM, Ketan Maheshwari <
>> > > > ketancmaheshwari at gmail.com > wrote:
>> > > >
>> > > >
>> > > >
>> > > > Sarah,
>> > > >
>> > > >
>> > > > I do not have the test you are asking for yet. I am looking at the
>> > > > test suite and will start on Beagle soon.
>> > > >
>> > > >
>> > > > Ketan
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > > On Apr 5, 2011, at 2:13 PM, Sarah Kenny wrote:
>> > > >
>> > > >
>> > > > i'm currently working on a swift script to replicate the bug for
>> > > > .92
>> > > > which i will then commit to svn in the test suite. if you mike, or
>> > > > ketan already have this let me know (i'm trying to hack the script
>> > > > jon
>> > > > posted to the list) and i'll use yours...david said he doesn't
>> > > > have
>> > > > one.
>> > > >
>> > > > as i said, my plan was to test on ranger, abe and a couple of
>> > > > (uci)
>> > > > local workstations.
>> > > >
>> > > > ~sk
>> > > >
>> > > >
>> > > > On Tue, Apr 5, 2011 at 12:10 PM, Michael Wilde < wilde at mcs.anl.gov
>> > > > >
>> > > > wrote:
>> > > >
>> > > >
>> > > > David, Sarah, Ketan,
>> > > >
>> > > > Can you all report back to the devel list on your progress on
>> > > > testing
>> > > > the release? Ie, what systems are you testing, and which of those
>> > > > tests are complete? When will the rest be done, and hence when are
>> > > > we
>> > > > ready to tag and release the fix?
>> > > >
>> > > > I asked who will create the test to confirm that the twice-each
>> > > > bug
>> > > > is
>> > > > fixed, but no one responded. Which of the three of you feel you
>> > > > know
>> > > > how to do this? Is this being tested in your new tests?
>> > > >
>> > > > Ketan tells me that in the 0.92+ interim release I made for Beagle
>> > > > it
>> > > > looks like the resume feature is not working. I was aware that
>> > > > such
>> > > > a
>> > > > bug was reported in trunk, but in the original 0.92 Cray version
>> > > > (under /home/wilde/swift/rev) resume *was* working. Does the test
>> > > > suite test the resume feature at the moment?
>> > > >
>> > > > Lastly, who will tag and upload the new release, remove or change
>> > > > the
>> > > > red warning in the download page, and announce 0.92.1 on
>> > > > swift-user?
>> > > >
>> > > > - Mike
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > > ----- Original Message -----
>> > > > > Thanks, David. Please cc all discussion of this sort to
>> > > > > swift-devel.
>> > > > >
>> > > > > I assume SVN is working for you now? (It was working for me,
>> > > > > from
>> > > > > communicadao, around 9AM this morning).
>> > > > >
>> > > > > - Mike
>> > > > >
>> > > > >
>> > > > > ----- Original Message -----
>> > > > > > It appears that there may be a problem with
>> > > > > > svn.ci.uchicago.edu
>> > > > > > .
>> > > > > > I
>> > > > > > am
>> > > > > > unable to connect from an SVN client or through the web
>> > > > > > interface
>> > > > > > -
>> > > > > > both attempts just hang indefinitely. I have sent an email to
>> > > > > > support
>> > > > > > (ticket 12539), but just wanted to give you guys a heads up
>> > > > > > that
>> > > > > > there
>> > > > > > may be an issue there. I will try to run the tests again in
>> > > > > > the
>> > > > > > morning.
>> > > > > >
>> > > > > > David
>> > > > > >
>> > > > > >
>> > > > > > On Mon, Apr 4, 2011 at 2:42 PM, Michael Wilde <
>> > > > > > wilde at mcs.anl.gov
>> > > > > > >
>> > > > > > wrote:
>> > > > > >
>> > > > > >
>> > > > > > David, Sarah,
>> > > > > >
>> > > > > > How quickly could you re-divide the Swift site test plan
>> > > > > > between
>> > > > > > you
>> > > > > > and confirm back to swift-devel that we are ready to tag and
>> > > > > > release
>> > > > > > the branch as 0.92.1?
>> > > > > >
>> > > > > > Before we do that, you need to add a test to the test suite
>> > > > > > that
>> > > > > > can
>> > > > > > replicate the twice-each bug and verify that its detected in
>> > > > > > 0.92
>> > > > > > and
>> > > > > > corrected in 0.92.1
>> > > > > >
>> > > > > > Can you possibly do this by noon tomorrow?
>> > > > > >
>> > > > > > Can you post a checklist of tests with names of who's going to
>> > > > > > run
>> > > > > > them?
>> > > > > >
>> > > > > > Depending on what you can commit to, I will see if I, Ketan,
>> > > > > > and/or
>> > > > > > Justin can help take various sites as well. I feel we really
>> > > > > > need
>> > > > > > to
>> > > > > > do this quickly so we have a stable trusted release out there.
>> > > > > >
>> > > > > >
>> > > > > >
>> > > > > > Thanks,
>> > > > > >
>> > > > > > Mike
>> > > > > >
>> > > > > > --
>> > > > > > Michael Wilde
>> > > > > > Computation Institute, University of Chicago
>> > > > > > Mathematics and Computer Science Division
>> > > > > > Argonne National Laboratory
>> > > > >
>> > > > > --
>> > > > > Michael Wilde
>> > > > > Computation Institute, University of Chicago
>> > > > > Mathematics and Computer Science Division
>> > > > > Argonne National Laboratory
>> > > > >
>> > > > > _______________________________________________
>> > > > > Swift-devel mailing list
>> > > > > Swift-devel at ci.uchicago.edu
>> > > > > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>> > > >
>> > > > --
>> > > >
>> > > >
>> > > >
>> > > > Michael Wilde
>> > > > Computation Institute, University of Chicago
>> > > > Mathematics and Computer Science Division
>> > > > Argonne National Laboratory
>> > > >
>> > > >
>> > > >
>> > > >
>> > > > _______________________________________________
>> > > > Swift-devel mailing list
>> > > > Swift-devel at ci.uchicago.edu
>> > > > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>> > > >
>> > > >
>> > > >
>> > > >
>> > > > --
>> > > > Any intelligent fool can make things bigger and more complex... It
>> > > > takes a touch of genius - and a lot of courage to move in the
>> > > > opposite
>> > > > direction.
>> > > > - Albert Einstein
>> > > >
>> > > >
>> > > >
>> > > > _______________________________________________
>> > > > Swift-devel mailing list
>> > > > Swift-devel at ci.uchicago.edu
>> > > > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>> > >
>> > > --
>> > > Michael Wilde
>> > > Computation Institute, University of Chicago
>> > > Mathematics and Computer Science Division
>> > > Argonne National Laboratory
>> > >
>> > >
>> > >
>> > >
>> > > --
>> > >
>> > >
>> > >
>> > > Any intelligent fool can make things bigger and more complex... It
>> > > takes a touch of genius - and a lot of courage to move in the
>> > > opposite
>> > > direction.
>> > > - Albert Einstein
>> > >
>> > >
>> > >
>> > > _______________________________________________
>> > > Swift-devel mailing list
>> > > Swift-devel at ci.uchicago.edu
>> > > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>> >
>> > --
>> >
>> >
>> >
>> > Michael Wilde
>> > Computation Institute, University of Chicago
>> > Mathematics and Computer Science Division
>> > Argonne National Laboratory
>> >
>> >
>> >
>> >
>> > --
>> > Any intelligent fool can make things bigger and more complex... It
>> > takes a touch of genius - and a lot of courage to move in the opposite
>> > direction.
>> > - Albert Einstein
>>
>> --
>> Michael Wilde
>> Computation Institute, University of Chicago
>> Mathematics and Computer Science Division
>> Argonne National Laboratory
>>
>>
>
>
> --
> Any intelligent fool can make things bigger and more complex... It takes a
> touch of genius - and a lot of courage to move in the opposite direction.
> - Albert Einstein
>
>
>
--
Any intelligent fool can make things bigger and more complex... It takes a
touch of genius - and a lot of courage to move in the opposite direction.
- Albert Einstein
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From ketancmaheshwari at gmail.com Wed Apr 6 12:51:22 2011
From: ketancmaheshwari at gmail.com (Ketan Maheshwari)
Date: Wed, 6 Apr 2011 12:51:22 -0500
Subject: [Swift-devel] svn commit email
In-Reply-To:
References:
Message-ID: <161BBF70-9AD5-45B9-A6FE-FB7E4789A2C5@gmail.com>
Me too (on vdl2 repo). --ketan
On Apr 6, 2011, at 12:12 PM, Sarah Kenny wrote:
> hey all, my svn commits at the moment are generating an email saying my message (which should just be a post-commit email) is awaiting moderator approval...anyone else getting this?
>
> ~sk
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
From ketancmaheshwari at gmail.com Wed Apr 6 13:05:37 2011
From: ketancmaheshwari at gmail.com (Ketan Maheshwari)
Date: Wed, 6 Apr 2011 13:05:37 -0500
Subject: [Swift-devel] Re: Attachment too large: Fwd: Swift-devel post from
ketan@mcs.anl.gov requires approval
In-Reply-To: <2083793928.71160.1302112893032.JavaMail.root@zimbra.anl.gov>
References: <2083793928.71160.1302112893032.JavaMail.root@zimbra.anl.gov>
Message-ID:
Ohh, sorry about this, did not realize the size of log.
here is the link: http://www.mcs.anl.gov/~ketan/files/ftdock-20110401-1627-xd2zm525.log
Ketan
On Apr 6, 2011, at 1:01 PM, Michael Wilde wrote:
> Ketan, you posted an 86MB attachment to swift-devel and its pending approval.
>
> Can you resend, with a link to a URL instead? (eg from your public_html folder)
>
> - Mike
>
> ----- Forwarded Message -----
> From: swift-devel-owner at ci.uchicago.edu
> To: swift-devel-owner at ci.uchicago.edu
> Sent: Wednesday, April 6, 2011 12:00:03 PM
> Subject: Swift-devel post from ketan at mcs.anl.gov requires approval
>
> As list administrator, your authorization is requested for the
> following mailing list posting:
>
> List: Swift-devel at ci.uchicago.edu
> From: ketan at mcs.anl.gov
> Subject: Plotting From Swift Log
> Reason: Message body is too big: 89541588 bytes with a limit of 20000 KB
>
> At your convenience, visit:
>
> http://mail.ci.uchicago.edu/mailman/admindb/swift-devel
>
> to approve or deny the request.
>
> --
> Michael Wilde
> Computation Institute, University of Chicago
> Mathematics and Computer Science Division
> Argonne National Laboratory
>
From wilde at mcs.anl.gov Wed Apr 6 13:16:31 2011
From: wilde at mcs.anl.gov (Michael Wilde)
Date: Wed, 6 Apr 2011 13:16:31 -0500 (CDT)
Subject: Swift commit messages getting sent to moderator - was Re:
[Swift-devel] svn commit email
In-Reply-To:
Message-ID: <779218967.71257.1302113791047.JavaMail.root@zimbra.anl.gov>
Hi CI Support,
Commit emails for the vdl2 repository started getting flagged for approvals a few days ago. They had been working fine till then.
I looked at the swift-commit list settings at that time and saw almost no one subscribed, which I thought was strange. Then a few days later, seems like most of the group was subscribed. Im therefore not sure if I misread what I saw, or it changed somehow (manually or via some restore???) or if I looked at a different list.
Did anything change in either the swift-commit list settings or in the linkage from svn to the commit email, in the past week, that would explain problems?
Is there anything special in how the commit email list should be set up?
Thanks,
Mike
----- Original Message -----
hey all, my svn commits at the moment are generating an email saying my message (which should just be a post-commit email) is awaiting moderator approval...anyone else getting this?
~sk
_______________________________________________
Swift-devel mailing list
Swift-devel at ci.uchicago.edu
http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From wilde at mcs.anl.gov Wed Apr 6 13:19:59 2011
From: wilde at mcs.anl.gov (Michael Wilde)
Date: Wed, 6 Apr 2011 13:19:59 -0500 (CDT)
Subject: [Swift-devel] Fwd: [CI Ticketing System #12700] AutoReply: Please
replicate communicado OSG+Condor-G install to bridled
In-Reply-To:
Message-ID: <664238149.71281.1302113999812.JavaMail.root@zimbra.anl.gov>
fyi...
Hi CI Team,
The OSG install and in particular the Condor-G setup on communicado is working well.
Can you replicate that install on bridled so that we have an alternate submit host when one is down?
Thanks,
- Mike
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
From wilde at mcs.anl.gov Wed Apr 6 13:24:57 2011
From: wilde at mcs.anl.gov (Michael Wilde)
Date: Wed, 6 Apr 2011 13:24:57 -0500 (CDT)
Subject: [CI Ticketing System #12698]: Swift commit messages getting sent to
moderator - was Re: [Swift-devel] svn commit email
In-Reply-To:
Message-ID: <1846194413.71308.1302114297557.JavaMail.root@zimbra.anl.gov>
Swift Devels,
Here's the CI ticket # for this issue. Im going on the assumption that something systems-wise changed between svn and the swift-commit list to cause the routing to moderator. Maybe its a simple as the list membership changing somehow.
Did anyone do anything last week that would have resulted in mass removal of list members?
CI Team: Im assuming that everyone that wants commit messages needs to be subscribed, correct? Ie theres no other magic message routing involved here, right?
- Mike
---
Hi CI Support,
Commit emails for the vdl2 repository started getting flagged for approvals a few days ago. They had been working fine till then.
I looked at the swift-commit list settings at that time and saw almost no one subscribed, which I thought was strange. Then a few days later, seems like most of the group was subscribed. Im therefore not sure if I misread what I saw, or it changed somehow (manually or via some restore???) or if I looked at a different list.
Did anything change in either the swift-commit list settings or in the linkage from svn to the commit email, in the past week, that would explain problems?
Is there anything special in how the commit email list should be set up?
Thanks,
Mike
----- Original Message -----
hey all, my svn commits at the moment are generating an email saying my message (which should just be a post-commit email) is awaiting moderator approval...anyone else getting this?
~sk
_______________________________________________
Swift-devel mailing list
Swift-devel at ci.uchicago.edu
http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
From support at ci.uchicago.edu Wed Apr 6 13:24:59 2011
From: support at ci.uchicago.edu (Mike Wilde)
Date: Wed, 6 Apr 2011 13:24:59 -0500
Subject: [CI Ticketing System #12698]: Swift commit messages getting sent to
moderator - was Re: [Swift-devel] svn commit email
In-Reply-To: <1846194413.71308.1302114297557.JavaMail.root@zimbra.anl.gov>
References:
<1846194413.71308.1302114297557.JavaMail.root@zimbra.anl.gov>
Message-ID:
Swift Devels,
Here's the CI ticket # for this issue. Im going on the assumption that something systems-wise changed between svn and the swift-commit list to cause the routing to moderator. Maybe its a simple as the list membership changing somehow.
Did anyone do anything last week that would have resulted in mass removal of list members?
CI Team: Im assuming that everyone that wants commit messages needs to be subscribed, correct? Ie theres no other magic message routing involved here, right?
- Mike
---
Hi CI Support,
Commit emails for the vdl2 repository started getting flagged for approvals a few days ago. They had been working fine till then.
I looked at the swift-commit list settings at that time and saw almost no one subscribed, which I thought was strange. Then a few days later, seems like most of the group was subscribed. Im therefore not sure if I misread what I saw, or it changed somehow (manually or via some restore???) or if I looked at a different list.
Did anything change in either the swift-commit list settings or in the linkage from svn to the commit email, in the past week, that would explain problems?
Is there anything special in how the commit email list should be set up?
Thanks,
Mike
----- Original Message -----
hey all, my svn commits at the moment are generating an email saying my message (which should just be a post-commit email) is awaiting moderator approval...anyone else getting this?
~sk
_______________________________________________
Swift-devel mailing list
Swift-devel at ci.uchicago.edu
http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
From wilde at mcs.anl.gov Wed Apr 6 13:34:12 2011
From: wilde at mcs.anl.gov (Michael Wilde)
Date: Wed, 6 Apr 2011 13:34:12 -0500 (CDT)
Subject: [Swift-devel] Developer meeting at 4PM CDT today
In-Reply-To: <473221833.71388.1302114751296.JavaMail.root@zimbra.anl.gov>
Message-ID: <1590231453.71411.1302114852761.JavaMail.root@zimbra.anl.gov>
Lets review 0.92.1 and 0.93 plans,
bugzilla routing and ticket walkthrough
swift-devel monitoring
asciidoc
Release planner: https://sites.google.com/site/swiftdevel/release-plans
Lets keep it to 30 mins.
- Mike
From jon.monette at gmail.com Wed Apr 6 15:15:13 2011
From: jon.monette at gmail.com (Jonathan Monette)
Date: Wed, 6 Apr 2011 15:15:13 -0500
Subject: [Swift-devel] Error code 254
Message-ID:
This question carries over from [Swift-devel] Re: Can you test 0.92 branch
for 0.92.1 release? Could an error code 254 returned if the file that is
required for stageout not exist?
--
Any intelligent fool can make things bigger and more complex... It takes a
touch of genius - and a lot of courage to move in the opposite direction.
- Albert Einstein
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From wozniak at mcs.anl.gov Wed Apr 6 15:56:58 2011
From: wozniak at mcs.anl.gov (Justin M Wozniak)
Date: Wed, 6 Apr 2011 15:56:58 -0500 (CDT)
Subject: [Swift-devel] Re: Plotting From Swift Log
In-Reply-To: <3875827E-46C7-48C5-AA43-DA6A0A476BE1@mcs.anl.gov>
References: <3875827E-46C7-48C5-AA43-DA6A0A476BE1@mcs.anl.gov>
Message-ID:
I placed a first attempt in ~wozniak/load.eps .
On Wed, 6 Apr 2011, Ketan Maheshwari wrote:
> Justin,
>
> Per our talk today, please find attached logs for a 10K task Swift run
> of modFTdock on Beagle. Let's see if it is possible to get a plottable
> info from this log file.
>
> Ketan
--
Justin M Wozniak
From bugzilla-daemon at mcs.anl.gov Wed Apr 6 16:08:00 2011
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Wed, 6 Apr 2011 16:08:00 -0500 (CDT)
Subject: [Swift-devel] [Bug 239] Java 1.5 compatibility issue - @Override
In-Reply-To:
References:
Message-ID: <20110406210800.7A22D2DC68@wind.mcs.anl.gov>
https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=239
Justin Wozniak changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |wozniak at mcs.anl.gov
Resolution| |FIXED
--
Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
From ketancmaheshwari at gmail.com Wed Apr 6 18:44:49 2011
From: ketancmaheshwari at gmail.com (Ketan Maheshwari)
Date: Wed, 6 Apr 2011 18:44:49 -0500
Subject: [Swift-devel] Added asciidoc cookbook to svn
Message-ID: <9384C8A9-3DF6-4488-9917-6222FB30EBA6@gmail.com>
Hi,
Added asciidoc cookbook to svn at : https://svn.ci.uchicago.edu/svn/vdl2/www/cookbook/
Feel free to add, update.
An asciidoc cheatsheet for quick reference can be found here : http://powerman.name/doc/asciidoc
Ketan
From bugzilla-daemon at mcs.anl.gov Wed Apr 6 19:26:56 2011
From: bugzilla-daemon at mcs.anl.gov (bugzilla-daemon at mcs.anl.gov)
Date: Wed, 6 Apr 2011 19:26:56 -0500 (CDT)
Subject: [Swift-devel] [Bug 331] New: Add basic regression tests for the
twice-each bug
Message-ID:
https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=331
Summary: Add basic regression tests for the twice-each bug
Product: Swift
Version: 0.93
Platform: PC
OS/Version: Mac OS
Status: ASSIGNED
Severity: normal
Priority: P1
Component: SwiftScript language
AssignedTo: dk0966 at cs.ship.edu
ReportedBy: wilde at mcs.anl.gov
Tests were added for the symptom of this bug that caused the mapper problem -
the bugs original symptom.
We should also add simple regression tests that test the most basic aspect of
this bug directly: foreach iterations being done more than once.
Here are a few of the original tests. These could be packaged under language.
We should stress foreach() in various ways, with input arrays created in
various ways.
David: this is a good exercise for adding new tests to the test suite.
---
com$ swift ~/swift/lab/zz3.swift
Swift svn swift-r4157 cog-r3056
RunID: 20110406-1915-z3zvkba8
Progress:
SwiftScript trace: for, 1
SwiftScript trace: for, 2
SwiftScript trace: for, 1
SwiftScript trace: for, 2
Final status:
com$ more foreachsite
com$
PATH=/home/wilde/swift/src/0.92/cog/modules/swift/dist/swift-svn/bin/:$PATH
com$ swift ~/swift/lab/zz3.swift
Swift svn swift-r4252 (swift modified locally) cog-r3088 (cog modified locally)
RunID: 20110406-1916-u4mstvs2
Progress:
SwiftScript trace: for, 2
SwiftScript trace: for, 1
Final status:
com$ cat ~/swift/lab/zz3.swift
int arr[];
arr[0]=1;
arr[1]=2;
foreach a in arr {
trace("for", a);
}
com$ cat ~/swift/lab/zz6.swift
int arr[];
foreach a,i in [0:9] {
arr[i] = i;
}
trace("arr",arr);
foreach a,i in arr {
trace("for", a,i);
}
com$
--
Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the reporter.
From benc at hawaga.org.uk Thu Apr 7 10:34:39 2011
From: benc at hawaga.org.uk (Ben Clifford)
Date: Thu, 7 Apr 2011 15:34:39 +0000 (GMT)
Subject: [Swift-devel] [provenance-challenge] W3C Provenance Working Group -
call for participation (fwd)
Message-ID:
thsi might be of interest to people here who are still actively interested
in provenance work and on the delights of w3c bureaucracy.
---------- Forwarded message ----------
Date: Thu, 07 Apr 2011 14:58:39 +0200
From: Paul Groth
Reply-To: provenance-challenge at ipaw.info
To: provenance-challenge at ipaw.info
Subject: [provenance-challenge] W3C Provenance Working Group - call for
participation
Hello All:
One of the central ideas behind the Provenance Challenge series was to
understand the commonalities between provenance system and work towards
interoperability between them. Many people in this community contributed to the
W3C Provenance Incubator Group[1] and the work of this community influenced
that group greatly.
Early last year, the W3C Incubator Group concluded its
work developing a road-map for provenance on the Web, and recommended
the creation of a Working Group to define a standard for the
interchange of provenance information.
Last week, the W3C management team approved the formation of the
Provenance Working Group [2]. The aim of the group is to support the
widespread publication and use of provenance on the Web through the
creation of a simple, extensible language to exchange provenance
information.
Given the expertise within this community and more importantly the spirt of
cooperation that you show, we would be grateful if you would consider
participating in the Working Group.
Thus, we encourage you to join the Provenance Working Group and help define
this critical language for the Web. More details on joining can be found at
[4].
If you intend on contributing, please help us select a teleconference time and
first face-to-face meeting date [5].
If you have any questions don't hesitate to ask.
regards,
Luc Moreau
Paul Groth
co-chairs W3C Working Group on Provenance
team-prov-chairs at w3.org
[1] Provenance Incubator Group -
http://www.w3.org/2005/Incubator/prov/wiki/W3C_Provenance_Incubator_Group_Wiki
[2] Provenance Working Group - http://www.w3.org/2011/prov/wiki/Main_Page
[3] Charter - http://www.w3.org/2011/01/prov-wg-charter
[4] Joining - http://www.w3.org/2011/prov/wiki/How_to_Join
[5] Poll on Telecon & F2F - http://www.w3.org/2002/09/wbs/1/prov-sched-1/
From skenny at uchicago.edu Thu Apr 7 16:59:44 2011
From: skenny at uchicago.edu (Sarah Kenny)
Date: Thu, 7 Apr 2011 14:59:44 -0700
Subject: [Swift-devel] trying to build trunk
Message-ID:
BUILD FAILED
/autonfs/home/skenny/soft/cog/modules/swift/build.xml:73: The following
error occurred while executing this line:
java.io.FileNotFoundException: /autonfs/home/skenny/soft/cog/mbuild.xml (No
such file or directory)
am i missing something obvious here?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From skenny at uchicago.edu Thu Apr 7 17:05:12 2011
From: skenny at uchicago.edu (Sarah Kenny)
Date: Thu, 7 Apr 2011 15:05:12 -0700
Subject: [Swift-devel] Re: trying to build trunk
In-Reply-To:
References:
Message-ID:
sorry my bad...faulty checkout :P
On Thu, Apr 7, 2011 at 2:59 PM, Sarah Kenny wrote:
> BUILD FAILED
> /autonfs/home/skenny/soft/cog/modules/swift/build.xml:73: The following
> error occurred while executing this line:
> java.io.FileNotFoundException: /autonfs/home/skenny/soft/cog/mbuild.xml (No
> such file or directory)
>
> am i missing something obvious here?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From wilde at mcs.anl.gov Thu Apr 7 17:06:55 2011
From: wilde at mcs.anl.gov (Michael Wilde)
Date: Thu, 7 Apr 2011 17:06:55 -0500 (CDT)
Subject: [Swift-devel] trying to build trunk
In-Reply-To:
Message-ID: <98515176.80274.1302214015152.JavaMail.root@zimbra.anl.gov>
Sarah,
Do you have cog correctly checked out, under the right dir relative to your swif/ dir? It should be in /home/skenny/soft/cog.
In my trunk I see this:
com$ cd swift/src/trunk
com$ ls
cog/
com$ cd cog
com$ ls
BUGS.txt LICENSE.txt VERSION build.properties etc/ man/ modules/ qualitycontrol/ webstart/
CHANGES.txt README.txt bin/ build.xml lib/ mbuild.xml pmd/ tools/ webstart.properties
com$
Does your cog/ dir not have an mbuild.xml?
- Mike
----- Original Message -----
BUILD FAILED
/autonfs/home/skenny/soft/cog/modules/swift/build.xml:73: The following error occurred while executing this line:
java.io.FileNotFoundException: /autonfs/home/skenny/soft/cog/mbuild.xml (No such file or directory)
am i missing something obvious here?
_______________________________________________
Swift-devel mailing list
Swift-devel at ci.uchicago.edu
http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
From skenny at uchicago.edu Thu Apr 7 17:35:00 2011
From: skenny at uchicago.edu (Sarah Kenny)
Date: Thu, 7 Apr 2011 15:35:00 -0700
Subject: [Swift-devel] where to put sites.xml checker
Message-ID:
hi all, i have a script to call for checking the validity of the user's
sites.xml file...i'm not sure where the best place is to call it from. any
ideas on the best spot to drop it in? initially we'd discussed the swift
script itself but i'm thinking it should probably be where the commandline
is parsed (?)
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From wilde at mcs.anl.gov Thu Apr 7 18:24:47 2011
From: wilde at mcs.anl.gov (Michael Wilde)
Date: Thu, 7 Apr 2011 18:24:47 -0500 (CDT)
Subject: [Swift-devel] where to put sites.xml checker
In-Reply-To:
Message-ID: <1124918386.80616.1302218687642.JavaMail.root@zimbra.anl.gov>
Sarah, that sounds very reasonable. After command parsing you know where the sites file is. I think anywhere between there and before the Java app is launched.
- Mike
----- Original Message -----
> hi all, i have a script to call for checking the validity of the
> user's sites.xml file...i'm not sure where the best place is to call
> it from. any ideas on the best spot to drop it in? initially we'd
> discussed the swift script itself but i'm thinking it should probably
> be where the commandline is parsed (?)
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
From wilde at mcs.anl.gov Fri Apr 8 08:45:12 2011
From: wilde at mcs.anl.gov (Michael Wilde)
Date: Fri, 8 Apr 2011 08:45:12 -0500 (CDT)
Subject: [Swift-devel] Re: Fwd: [Dsl-seminar] Bloom/Bud released
In-Reply-To: <20110408083815.ANC27026@mstore03.uchicago.edu>
Message-ID: <875258362.81854.1302270312947.JavaMail.root@zimbra.anl.gov>
Another data flow language to look at.
Swift Team: also some nice layout inspiration and possibly some good examples of language "try it" mechanisms we can leverage in Swift.
- Mike
----- Forwarded Message -----
From: "Tim Armstrong"
To: dsl-seminar at mailman.cs.uchicago.edu
Sent: Friday, April 8, 2011 8:38:15 AM
Subject: [Dsl-seminar] Bloom/Bud released
http://www.bloom-lang.net/
_______________________________________________
DSL-seminar mailing list
DSL-seminar at mailman.cs.uchicago.edu
https://mailman.cs.uchicago.edu/mailman/listinfo/dsl-seminar
--
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory
From support at ci.uchicago.edu Fri Apr 8 10:10:58 2011
From: support at ci.uchicago.edu (David Forero)
Date: Fri, 8 Apr 2011 10:10:58 -0500
Subject: [CI Ticketing System #12698] Swift commit messages getting sent to
moderator - was Re: [Swift-devel] svn commit email
In-Reply-To: <779218967.71257.1302113791047.JavaMail.root@zimbra.anl.gov>
References:
<779218967.71257.1302113791047.JavaMail.root@zimbra.anl.gov>
Message-ID:
On Wed Apr 06 13:16:32 2011, wilde at mcs.anl.gov wrote:
> Commit emails for the vdl2 repository started getting flagged for
> approvals a few days ago. They had been working fine till then.
>
>
> I looked at the swift-commit list settings at that time and saw almost
> no one subscribed, which I thought was strange. Then a few days
> later, seems like most of the group was subscribed. Im therefore
> not sure if I misread what I saw, or it changed somehow (manually
> or via some restore???) or if I looked at a different list.
>
>
> Did anything change in either the swift-commit list settings or in the
> linkage from svn to the commit email, in the past week, that would
> explain problems?
>
>
> Is there anything special in how the commit email list should be set
> up?
Here's who's subscribed to swift commit:
foster at mcs.anl.gov
hategan at mcs.anl.gov
iraicu at cs.uchicago.edu
jon.monette at gmail.com
ketan at mcs.anl.gov
noreply at svn.ci.uchicago.edu
skenny at uchicago.edu
swift-commit at globus.org
tim.g.armstrong at gmail.com
wilde at mcs.anl.gov
wozniak at mcs.anl.gov
yongzh at cs.uchicago.edu
As far as I know there have been no changes to this list. Does it say why the
postings are being held?
--
David Forero
System Administrator
Computation Institute
University of Chicago
773-834-4102
From skenny at uchicago.edu Fri Apr 8 11:34:39 2011
From: skenny at uchicago.edu (Sarah Kenny)
Date: Fri, 8 Apr 2011 09:34:39 -0700
Subject: [CI Ticketing System #12698] Swift commit messages getting sent
to moderator - was Re: [Swift-devel] svn commit email
In-Reply-To:
References:
<779218967.71257.1302113791047.JavaMail.root@zimbra.anl.gov>
Message-ID:
i got another yesterday here's the content:
Your mail to 'Swift-commit' with the subject
r4307 - trunk/bin
Is being held until the list moderator can review it for approval.
The reason it is being held:
Post by non-member to a members-only list
Either the message will get posted to the list, or you will receive
notification of the moderator's decision. If you would like to cancel
this posting, please visit the following URL:
http://mail.ci.uchicago.edu/mailman/confirm/swift-commit/f35b402588db8e0fb5b59f561fa3dd3a640c3406
On Fri, Apr 8, 2011 at 8:10 AM, David Forero wrote:
> On Wed Apr 06 13:16:32 2011, wilde at mcs.anl.gov wrote:
> > Commit emails for the vdl2 repository started getting flagged for
> > approvals a few days ago. They had been working fine till then.
> >
> >
> > I looked at the swift-commit list settings at that time and saw almost
> > no one subscribed, which I thought was strange. Then a few days
> > later, seems like most of the group was subscribed. Im therefore
> > not sure if I misread what I saw, or it changed somehow (manually
> > or via some restore???) or if I looked at a different list.
> >
> >
> > Did anything change in either the swift-commit list settings or in the
> > linkage from svn to the commit email, in the past week, that would
> > explain problems?
> >
> >
> > Is there anything special in how the commit email list should be set
> > up?
>
> Here's who's subscribed to swift commit:
>
> foster at mcs.anl.gov
>
> hategan at mcs.anl.gov
>
> iraicu at cs.uchicago.edu
>
> jon.monette at gmail.com
>
> ketan at mcs.anl.gov
>
> noreply at svn.ci.uchicago.edu
>
> skenny at uchicago.edu
>
> swift-commit at globus.org
>
> tim.g.armstrong at gmail.com
>
> wilde at mcs.anl.gov
>
> wozniak at mcs.anl.gov
>
> yongzh at cs.uchicago.edu
>
> As far as I know there have been no changes to this list. Does it say why
> the
> postings are being held?
>
>
> --
>
> David Forero
> System Administrator
> Computation Institute
> University of Chicago
> 773-834-4102
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
From support at ci.uchicago.edu Fri Apr 8 11:34:49 2011
From: support at ci.uchicago.edu (skenny)
Date: Fri, 8 Apr 2011 11:34:49 -0500
Subject: [CI Ticketing System #12698] Swift commit messages getting sent
to moderator - was Re: [Swift-devel] svn commit email
In-Reply-To:
References:
<779218967.71257.1302113791047.JavaMail.root@zimbra.anl.gov>
Message-ID:
i got another yesterday here's the content:
Your mail to 'Swift-commit' with the subject
r4307 - trunk/bin
Is being held until the list moderator can review it for approval.
The reason it is being held:
Post by non-member to a members-only list
Either the message will get posted to the list, or you will receive
notification of the moderator's decision. If you would like to cancel
this posting, please visit the following URL:
http://mail.ci.uchicago.edu/mailman/confirm/swift-commit/f35b402588db8e0fb5b59f561fa3dd3a640c3406
On Fri, Apr 8, 2011 at 8:10 AM, David Forero wrote:
> On Wed Apr 06 13:16:32 2011, wilde at mcs.anl.gov wrote:
> > Commit emails for the vdl2 repository started getting flagged for
> > approvals a few days ago. They had been working fine till then.
> >
> >
> > I looked at the swift-commit list settings at that time and saw almost
> > no one subscribed, which I thought was strange. Then a few days
> > later, seems like most of the group was subscribed. Im therefore
> > not sure if I misread what I saw, or it changed somehow (manually
> > or via some restore???) or if I looked at a different list.
> >
> >
> > Did anything change in either the swift-commit list settings or in the
> > linkage from svn to the commit email, in the past week, that would
> > explain problems?
> >
> >
> > Is there anything special in how the commit email list should be set
> > up?
>
> Here's who's subscribed to swift commit:
>
> foster at mcs.anl.gov
>
> hategan at mcs.anl.gov
>
> iraicu at cs.uchicago.edu
>
> jon.monette at gmail.com
>
> ketan at mcs.anl.gov
>
> noreply at svn.ci.uchicago.edu
>
> skenny at uchicago.edu
>
> swift-commit at globus.org
>
> tim.g.armstrong at gmail.com
>
> wilde at mcs.anl.gov
>
> wozniak at mcs.anl.gov
>
> yongzh at cs.uchicago.edu
>
> As far as I know there have been no changes to this list. Does it say why
> the
> postings are being held?
>
>
> --
>
> David Forero
> System Administrator
> Computation Institute
> University of Chicago
> 773-834-4102
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
>
From support at ci.uchicago.edu Fri Apr 8 11:36:51 2011
From: support at ci.uchicago.edu (skenny)
Date: Fri, 8 Apr 2011 11:36:51 -0500
Subject: Fwd: [CI Ticketing System #12698] Swift commit messages getting sent
to moderator - was Re: [Swift-devel] svn commit email
In-Reply-To:
References:
<779218967.71257.1302113791047.JavaMail.root@zimbra.anl.gov>