Re: [stellation-res] Volunteer - Installing the core

[Dave Shields <shields@xxxxxxxxxxxxxx>]

On Fri, Dec 20, 2002 at 09:39:24AM -0500, jhoward@xxxxxxxxxxxxxxx wrote:
> Hello,
> 
> > If you want to dig into the system, I'd suggest not spending too much time
> > on 7.2.1, but moving on to a real, and open problem -- why are tests
> > failing under the new postgres release, 7.3? This was discussed in list a
> > couple of weeks back. I spent a little time on this, but was unable to sort
> > it out.
> 
> This sounds like the better option.  First, I installed PostgreSQL
> 7.2.3 in order to verify that I could run through the tests correctly.
> Because I'm likely to be moving to trying to work on the problems with
> 7.3 soon, I downloaded the stellation-core-2002-12-19-src.tar.gz file.
> In the process of building it, I found one place where I believe
> there's a bug in the build file.
> 
> When I run the build command "ant -f build-core.xml bin", I get the
> following error:
> 
> compile:
> 
> BUILD FAILED
> file:/home/jhoward/opt/stellation/build-core.xml:250: srcdir
> "/home/jhoward/opt/org.eclipse.stellation.cli/src" does not exist!
> 
> 
> Looking at build.xml, there is a property called "src.dir.cli" that's
> defined as location="../org.eclipse.stellation.cli/src".  Just to see
> what would happen, I changed the location to "src", the same location
> used as src.dir.core.  The build then worked without any unsatisfied
> dependencies, so I assume that all the files necessary are in the core
> tar.gz file.  Perhaps the reference to org.eclipse.stellation.cli is a
> holdover from the way the build system works when hosted in Eclipse
> and running against a checkout from the repository?
> 

This is probably my fault for not properly handling the recent source 
reorganization. The files that used to be all in 'core' were split up 
into 'core' and 'cli'. I noted a couple of days ago that 'cli' source 
was not included in source distribution, and I also made some changes 
related to Jonathan's addition re zip files. I'll try to sort this
out soon.

> 
> In any case, I then moved on to running the tests with PostgreSQL
> version 7.2.3.  Unfortunately, my setup still has no joy.  The test
> hangs in the same place: test 02, on the command to add dir1, dir2,
> and files 3 through 9.
> 
> To see what of probative value might pop up, I went ahead and followed
> your instructions for running the remainder of the tests with the
> following results.
> 
> 00:  Passes
> 
> 01:  Passes
> 
> 02:  Hangs on the add command
> 
> 03:  Hangs on the command to add file3, file4, ..., file9
>      I believe this is the first add command in the test.
> 
> 04:  Hangs on the command to add MissingStart, MissingEnd, MissingBoth
>      I believe this is the first add command in the test.
> 
> 05:  Hangs on the command to add a, b, and c
>      I believe this is the first add command in the test.
> 
> 06:  Passes
> 
> 07:  Passes
> 
> 08:  Passes
> 
> 09:  Hangs part way through the test.  The test had just copied
> several files, the most recent two being test/build/09/input/text.1
> and data.1 to test/build/09/ws.  The test then executes tsvc with a
> command line including "--workspace=build/09/ws synchronize".  It then
> executes the same command a second time.  That second time, the test hangs.
> 
> 10: Hangs part way through the test.  The test executes a tsvc command
> with parameters including "--workspace=build/10/ws checkin".  The test
> freezes up there.  (If the test does a checkin multiple times, I can
> try to find more context for where exactly it halts.)
> 
> 11: Failed.  The test proceeded until it ran a command including
> command line arguments of "--workspace=build/11/ws merge f"  It caught
> an exception as follows:
> 
> Exception in thread "main" java.lang.NullPointerException
>     at org.eclipse.stellation.cli.workspace.Merge.cleanCompound(Merge.java:262)
>     at org.eclipse.stellation.cli.workspace.Merge.cleanup(Merge.java:234)
>     at org.eclipse.stellation.cli.workspace.Merge.performMerge(Merge.java:169)
>     at org.eclipse.stellation.cli.workspace.Merge.command(Merge.java:64)
>     at org.eclipse.stellation.cli.workspace.Svc.command(Svc.java:106)
>     at org.eclipse.stellation.cli.workspace.Svc.run(Svc.java:625)
>     at org.eclipse.stellation.cli.workspace.Svc.main(Svc.java:377)
> 
> The next command to tsvc, with arguments of 
> "--options=CVS,SVC perform compare build/11/input2 build/11/ws"
> failed due to build/11/input2, file not found, presumably because the
> preceeding command was interrupted by an exception.
> 
> 12: Passes
> 
> 13: Hangs part way through the test, at a command including
> "--workspace=build/13/ws synchronize" that comes shortly after
> test/build/13/input/2/f is copied to test/build/13/ws/f.
> 
> 14: Passes
> 
> I wanted to rule out any bizarre coincidences of system/database
> timing or resource contention, so I ran a few of the nonterminating
> tests more than once.  They froze up in the same places each time.
> 

Yikes. This is bizarre, as I run the tests using 7.2.3 as part of the
current build process. Before digging too deeply, you might want to try
an older build, say 2002-12-10, to see if problem shows up there as well.

> Unless the test results above suggest something obvious to someone on
> this mail list, I'll start trying to trace through the code the tests
> exercise and figure out what's causing all these hangs with my
> installation.  (Of course, for that the Eclipse Java debugger would
> probably be helpful, so I may be exercising the instructions for
> working with the public CVS repository in Eclipse next...)
> 

You might want to also conduct some simple tests re add/synchronize. For
example
  tsvc create p
  tsvc checkout p
  echo "file" > a
  tsvc add a
  tsvc ci
  echo "more" > b
  tsvc sync
and so forth. If you get a hang, then rerun with -d3 to get log output.
For example,
  tsvc -d3 ci

Also, which JRE are you using?

thanks,
dave
-- 
Dave Shields, IBM Research, shields@xxxxxxxxxxxxxx.