[Swift-devel] Integrity of trunk in SVN (was: Re: swift 0.93 deadlock)

[Michael Wilde]

Yes, I think thats right. I suspect they are being run on one of our two lab machines bridled and communicado, likely under David's login from cron.

We just got a new CI login "swift" under which we will move all the nightly swift automated processed.  And David has all the tests for remote systems close to fully automated; he already runs them under scripts.

You can view the test suite framework and test groups in the Swift src tree:

  https://svn.ci.uchicago.edu/svn/vdl2/trunk/tests/

The remote systems tested are under tests/providers:

beagle/
crow/
fusion/
intrepid/
local/
local-coasters/
mcs/
pads/
queenbee/
surveyor/

----- Original Message -----
> From: "Daniel S. Katz" <dsk at ci.uchicago.edu>
> To: "Michael Wilde" <wilde at mcs.anl.gov>
> Cc: "David Kelly" <davidk at ci.uchicago.edu>, "Papia Rizwan" <papia.rizwan at gmail.com>, "swift-devel Devel"
> <swift-devel at ci.uchicago.edu>
> Sent: Saturday, September 17, 2011 7:25:23 AM
> Subject: Re: [Swift-devel] Integrity of trunk in SVN (was: Re: swift 0.93 deadlock)
> This is very good.
> 
> Where are the tests being run? It looks like the current tests are all
> local, is this right?
> 
> Dan
> 
> 
> On Sep 17, 2011, at 7:22 AM, Michael Wilde wrote:
> 
> >
> >> Automated tests have been running nightly for a few weeks now on
> >> 0.93
> >> and trunk.
> >>
> >> http://www.ci.uchicago.edu/swift/wwwdev/tests/tests.pl
> >
> > Thats excellent, David! Kudos and thanks to you and everyone else
> > who enhanced the test suite: Justin, Alberto, Mihael, and everyone
> > else who added tests! The HTML output looks great.
> >
> >> I will add automatic provider testing to that soon, and clean up
> >> the
> >> organization a bit.
> >
> > Cool.
> >
> > Can we also add a test to re-produce the current 0.93 Java deadlock?
> > If you can create a simpler test case that exhibits the problem,
> > then Mihael can use it when he goes after this bug.
> >
> > Papia, can you distill the failing script down to something that can
> > more readily be done in the test suite? I.e. something that runs on
> > localhost, doesnt use Octave, and has trivial built-in files? Then
> > put it in a shell script loop and see if we can make it deadlock
> > (ie, cause the hang-checker to go off)?
> >
> > Thanks,
> >
> > - Mike
> > _______________________________________________
> > Swift-devel mailing list
> > Swift-devel at ci.uchicago.edu
> > https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel
> 
> --
> Daniel S. Katz
> University of Chicago
> (773) 834-7186 (voice)
> (773) 834-6818 (fax)
> d.katz at ieee.org or dsk at ci.uchicago.edu
> http://www.ci.uchicago.edu/~dsk/

-- 
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory