1. <operating system> The {Unix} {superuser} account (with
	user name "root" and user ID 0) that overrides file
	permissions.  The term {avatar} is also used.  By extension,
	the privileged system-maintenance login on any {operating
	system}.

	See {root mode}, {go root}, {wheel}.

	[{Jargon File}]

	(1994-10-27)

	2. <operating system> {root directory}.

	(1996-11-21)

	3. <data> {root node}.

	(1998-11-14)

In {object-oriented programming} sending a message to an
	{object} (to invoke a {method}) is equivalent to calling a
	{procedure} in traditional programming languages, except that
	the actual code executed may only be selected at run time
	depending on the {class} of the object.  Thus, in response to
	the message "drawSelf", the method code invoked would be
	different if the target object were a circle or a square.

	(1995-02-16)

I'm having all sorts of issues with buildtest 2.0. Here's what I'm
running, is there anything that's out of whack?
Ubuntu 7.10 on x86_64 (AMD dual core)
Sun JAVA 1.6
Ant 1.7
SVN 1.4.4
Windows XP on x86
Sun JAVA 1.6
MSVC 2003
Ant 1.7
SVN 1.4.5
Here's what I'm doing, per the README [1].
* svn checkout -N
https://svn.apache.org/repos/asf/harmony/enhanced/buildtest/branches/2.0/
* Tweak the buildtest.sh to setup the environment variables and then
run these commands.
* ./buildtest.sh install
* ./buildtest.sh setup -Dtest.suites="classlib,drlvm,maven_test"
* ./buildtest.sh run
Here's the failure I get --
-install:
[echo]
[echo] --------
[echo] WARNING: Target setup of adaptor for Test Suite 'maven_test'
FAILED
[echo] -------- with the following exception:
[echo] The following error occurred while executing this line:
[echo] /home/nathan/harmony/bti/scripts/framework.xml:1079:
/home/nathan/harmony/bti/tests/maven_test isn't a valid directory
[delete] Deleting: /home/nathan/harmony/bti/build/temp/null1764598389
check-status:
[echo]
[echo] ------
[echo] ERROR: Setup of Test Suite 'maven_test' FAILED.
[echo] ------
BUILD FAILED
The same failure happened on windows; the paths were just a bit different.
I thought this was supposed to work out of the box.
-Nathan
[1]
https://svn.apache.org/repos/asf/harmony/enhanced/buildtest/branches/2.0/README.txt

<operating system> A {directory} in the sense of a collection
	of computer {files}.  The term is more common in systems such
	as the {Macintosh} or {Windows 95} which have a {graphical
	user interface} and provide a graphical {file browser} in
	which directories are traditionally depicted as folders (like
	small briefcases).

	(1997-03-20)

<programming> The multiple kilograms of macerated, pounded,
	steamed, bleached, and pressed trees that accompany most
	modern software or hardware products (see also {tree-killer}).
	Hackers seldom read paper documentation and (too) often resist
	writing it; they prefer theirs to be terse and {on-line}.  A
	common comment on this predilection is "You can't {grep} dead
	trees".

	See {drool-proof paper}, {verbiage}, {treeware}.

	[{Jargon File}]

	(2003-10-25)

I have tried this adaptor, it works fine here.
And once I rename the <root>/tests/maven_tests to other name, it'll fail
with the same error message as you.
The reason should be that the adaptor cannot find this directory.
So I guess you may haven't checked out the directory of
<root>/tests/maven_test .
Could you please check it out first and try again?
2007/12/21, Nathan Beyer <ndbeyer@xxxxxxxxxxx>:
>
> I'm having all sorts of issues with buildtest 2.0. Here's what I'm
> running, is there anything that's out of whack?
>
> Ubuntu 7.10 on x86_64 (AMD dual core)
> Sun JAVA 1.6
> Ant 1.7
> SVN 1.4.4
>
> Windows XP on x86
> Sun JAVA 1.6
> MSVC 2003
> Ant 1.7
> SVN 1.4.5
>
> Here's what I'm doing, per the README [1].
>
> * svn checkout -N
> https://svn.apache.org/repos/asf/harmony/enhanced/buildtest/branches/2.0/
> * Tweak the buildtest.sh to setup the environment variables and then
> run these commands.
> * ./buildtest.sh install
> * ./buildtest.sh setup -Dtest.suites="classlib,drlvm,maven_test"
> * ./buildtest.sh run
>
> Here's the failure I get --
>
>
> -install:
> [echo]
> [echo] --------
> [echo] WARNING: Target setup of adaptor for Test Suite 'maven_test'
> FAILED
> [echo] -------- with the following exception:
> [echo] The following error occurred while executing this line:
> [echo] /home/nathan/harmony/bti/scripts/framework.xml:1079:
> /home/nathan/harmony/bti/tests/maven_test isn't a valid directory
> [delete] Deleting: /home/nathan/harmony/bti/build/temp/null1764598389
>
> check-status:
> [echo]
> [echo] ------
> [echo] ERROR: Setup of Test Suite 'maven_test' FAILED.
> [echo] ------
>
> BUILD FAILED
>
> The same failure happened on windows; the paths were just a bit different.
>
> I thought this was supposed to work out of the box.
>
> -Nathan
>
> [1]
> https://svn.apache.org/repos/asf/harmony/enhanced/buildtest/branches/2.0/README.txt
>
--
Sean Qiu
http://xiaoxia.turendui.com

The README does not say I need to checkout that folder and it's very
specific about the checkout command using the "-N" to NOT check out
any sub-folder. Is the documentation wrong? I'm specifically try to
get this thing to work out of the box because we need to get buildtest
2.0 out of permanent branch and back into the trunk.

On my Windows machine, I switched to Ant 1.6.5 and ran the same
commands and a lot more is happening now; it checked out the
'tests/maven_test' folder and began a build.

-Nathan
wrote in message:
> I have tried this adaptor, it works fine here.
>
> And once I rename the <root>/tests/maven_tests to other name, it'll fail
> with the same error message as you.
> The reason should be that the adaptor cannot find this directory.
> So I guess you may haven't checked out the directory of
> <root>/tests/maven_test .
>
> Could you please check it out first and try again?
>
> 2007/12/21, Nathan Beyer <ndbeyer@xxxxxxxxxxx>:
>
> >
> > I'm having all sorts of issues with buildtest 2.0. Here's what I'm
> > running, is there anything that's out of whack?
> >
> > Ubuntu 7.10 on x86_64 (AMD dual core)
> > Sun JAVA 1.6
> > Ant 1.7
> > SVN 1.4.4
> >
> > Windows XP on x86
> > Sun JAVA 1.6
> > MSVC 2003
> > Ant 1.7
> > SVN 1.4.5
> >
> > Here's what I'm doing, per the README [1].
> >
> > * svn checkout -N
> > https://svn.apache.org/repos/asf/harmony/enhanced/buildtest/branches/2.0/
> > * Tweak the buildtest.sh to setup the environment variables and then
> > run these commands.
> > * ./buildtest.sh install
> > * ./buildtest.sh setup -Dtest.suites="classlib,drlvm,maven_test"
> > * ./buildtest.sh run
> >
> > Here's the failure I get --
> >
> >
> > -install:
> > [echo]
> > [echo] --------
> > [echo] WARNING: Target setup of adaptor for Test Suite 'maven_test'
> > FAILED
> > [echo] -------- with the following exception:
> > [echo] The following error occurred while executing this line:
> > [echo] /home/nathan/harmony/bti/scripts/framework.xml:1079:
> > /home/nathan/harmony/bti/tests/maven_test isn't a valid directory
> > [delete] Deleting: /home/nathan/harmony/bti/build/temp/null1764598389
> >
> > check-status:
> > [echo]
> > [echo] ------
> > [echo] ERROR: Setup of Test Suite 'maven_test' FAILED.
> > [echo] ------
> >
> > BUILD FAILED
> >
> > The same failure happened on windows; the paths were just a bit different.
> >
> > I thought this was supposed to work out of the box.
> >
> > -Nathan
> >
> > [1]
> > https://svn.apache.org/repos/asf/harmony/enhanced/buildtest/branches/2.0/README.txt
> >
>
>
>
> --
> Sean Qiu
> http://xiaoxia.turendui.com

<hardware> A {SCSI} device that executes a command from a
	{SCSI initiator} to perform some task.  Typically the target
	is a SCSI peripheral device but the {host adapter} can also be
	a target.

	(1999-02-10)

<jargon> To transfer data from one computer to another.
	Downloading usually refers to transfer from a larger "host"
	system (especially a {server} or {mainframe}) to a smaller
	"client" system, especially a {microcomputer} or specialised
	peripheral, and "{upload}" usually means from small to large.

	Others hold that, technically, download means "receive" and
	upload means "send", irrespective of the size of the systems
	involved.

	Note that in communications between ground and space,
	space-to-earth transmission is always "down" and the reverse
	"up", regardless of size.  So far the in-space machines have
	invariably been smaller; thus the upload/download distinction
	has been reversed from its usual sense.

	[{Jargon File}]

	(2003-11-04)

<software> 1. A temporary addition to a piece of code, usually
	as a {quick-and-dirty} remedy to an existing {bug} or
	{misfeature}.  A patch may or may not work, and may or may not
	eventually be incorporated permanently into the program.
	Distinguished from a {diff} or {mod} by the fact that a patch
	is generated by more primitive means than the rest of the
	program; the classical examples are instructions modified by
	using the front panel switches, and changes made directly to
	the binary executable of a program originally written in an
	{HLL}.  Compare {one-line fix}.

	2. To insert a patch into a piece of code.

	3. [in the Unix world] A {diff}.

	4. A set of modifications to binaries to be applied by a
	patching program.  {IBM} systems often receive updates to the
	{operating system} in the form of absolute {hexadecimal}
	patches.  If you have modified your OS, you have to
	disassemble these back to the {source code}.  The patches
	might later be corrected by other patches on top of them
	(patches were said to "grow scar tissue").  The result was
	often a convoluted {patch space} and headaches galore.

	There is a classic story of a {tiger team} penetrating a
	secure military computer that illustrates the danger inherent
	in binary patches (or, indeed, any patches that you can't - or
	don't - inspect and examine before installing).  They couldn't
	find any {trap doors} or any way to penetrate security of
	IBM's OS, so they made a site visit to an IBM office
	(remember, these were official military types who were
	purportedly on official business), swiped some IBM stationery,
	and created a fake patch.  The patch was actually the trapdoor
	they needed.  The patch was distributed at about the right
	time for an IBM patch, had official stationery and all
	accompanying documentation, and was dutifully installed.  The
	installation manager very shortly thereafter learned something
	about proper procedures.

	5. {Larry Wall}'s "patch" utility, which automatically applies
	a patch to a set of {source code} or other text files.  Patch
	accepts input in any of the four forms output by the {Unix}
	{diff} utility.  When the files being patched are not
	identical to those on which the diffs were based, patch uses
	{heuristics} to determine how to proceed.

	Diff and patch are the standard way of producing and applying
	updates under {Unix}.  Both have been ported to other
	{operating systems}.

	{Patch Home (http://www.gnu.org/software/patch/patch.html)}.

	[{Jargon File}]

	(2005-05-16)

1. <unit, text> (Sometimes abbreviated "pt") The unit of
	length used in {typography} to specify text character height,
	{rule} width, and other small measurements.

	There are six slightly different definitions: {Truchet point},
	{Didot point}, {ATA point}, {TeX point}, {Postscript point},
	and {IN point}.

	In Europe, the most commonly used is Didot and in the US, the
	formerly standard ATA point has essentially been replaced by
	the PostScript point due to the demise of traditional
	typesetting systems and rise of desktop computer based systems
	running software such as {QuarkXPress}, {Adobe InDesign} and
	{Adobe Pagemaker}.

	There are 20 {twips} in a point and 12 points in a {pica}
	(known as a "Cicero" in the Didot system).

	{Different point systems
	(http://www.vakcer.com/oberon/dtp/fonts/point.htm)}.

	(2004-12-23)

	2. <hardware> To move a {pointing device} so that the
	on-screen pointer is positioned over a certain object on the
	screen such as a {button} in a {graphical user interface}.  In
	most {window systems} it is then necessary to {click} a
	(physical) button on the pointing device to activate or select
	the object.  In some systems, just pointing to an object is
	known as "mouse-over" {event} which may cause some help text
	(called a "tool tip" in {Windows}) to be displayed.

	(2001-05-21)

1. <database> See {data dictionary}.

	2. <programming> The core of a {CASE} tool, typically a {DBMS}
	where all development documents are stored.

	(1999-04-27)

<programming> Combining software or hardware components or
	both into an overall system.

	(1996-05-22)

The README does not say I need to checkout that folder and it's very
specific about the checkout command using the "-N" to NOT check out
any sub-folder. Is the documentation wrong? I'm specifically try to
get this thing to work out of the box because we need to get buildtest
2.0 out of permanent branch and back into the trunk.
On my Windows machine, I switched to Ant 1.6.5 and ran the same
commands and a lot more is happening now; it checked out the
'tests/maven_test' folder and began a build.
-Nathan
wrote in message:
> I have tried this adaptor, it works fine here.
>
> And once I rename the <root>/tests/maven_tests to other name, it'll
fail
> with the same error message as you.
> The reason should be that the adaptor cannot find this directory.
> So I guess you may haven't checked out the directory of
> <root>/tests/maven_test .
>
> Could you please check it out first and try again?
>
> 2007/12/21, Nathan Beyer <ndbeyer@xxxxxxxxxxx>:
>
> >
> > I'm having all sorts of issues with buildtest 2.0. Here's what I'm
> > running, is there anything that's out of whack?
> >
> > Ubuntu 7.10 on x86_64 (AMD dual core)
> > Sun JAVA 1.6
> > Ant 1.7
> > SVN 1.4.4
> >
> > Windows XP on x86
> > Sun JAVA 1.6
> > MSVC 2003
> > Ant 1.7
> > SVN 1.4.5
> >
> > Here's what I'm doing, per the README [1].
> >
> > * svn checkout -N
> >
https://svn.apache.org/repos/asf/harmony/enhanced/buildtest/branches/2.0/
> > * Tweak the buildtest.sh to setup the environment variables and then
> > run these commands.
> > * ./buildtest.sh install
> > * ./buildtest.sh setup -Dtest.suites="classlib,drlvm,maven_test"
> > * ./buildtest.sh run
> >
> > Here's the failure I get --
> >
> >
> > -install:
> > [echo]
> > [echo] --------
> > [echo] WARNING: Target setup of adaptor for Test Suite
'maven_test'
> > FAILED
> > [echo] -------- with the following exception:
> > [echo] The following error occurred while executing this line:
> > [echo] /home/nathan/harmony/bti/scripts/framework.xml:1079:
> > /home/nathan/harmony/bti/tests/maven_test isn't a valid directory
> > [delete] Deleting:
/home/nathan/harmony/bti/build/temp/null1764598389
> >
> > check-status:
> > [echo]
> > [echo] ------
> > [echo] ERROR: Setup of Test Suite 'maven_test' FAILED.
> > [echo] ------
> >
> > BUILD FAILED
> >
> > The same failure happened on windows; the paths were just a bit
different.
> >
> > I thought this was supposed to work out of the box.
> >
> > -Nathan
> >
> > [1]
> >
https://svn.apache.org/repos/asf/harmony/enhanced/buildtest/branches/2.0/README.txt
> >
>
>
>
> --
> Sean Qiu
> http://xiaoxia.turendui.com
>
--

<jargon> A {marketroid} term for something he wants to sell
	you without bothering you with the often dizzying distinctions
	between {hardware}, {software}, {services}, {applications},
	{file formats}, companies, brand names and {operating
	systems}.

	"{Flash} is a perfect image-streaming solution."  "What is
	it?"  "Um...  about a thousand dollars."

	See also: {technology}.

	(1998-07-07)

"#>./buildtest.sh install" will call target update-framework[1] of
build.xml.
Update-framework only update the <root>/scripts and <root>/adaptors in
BTI,
while many tests as well as configurations are in <root>/tests directory.
Missing <root>/tests cause the build error.
The reason we don't update <root>/tests directly in install step is if we
just want to run a single test suite,
it'll be unnecessary to check out all of the tests, since it is
time-comsuming.
So the "setup" target of adaptor of each test suite is supposed to check
out individual tests themselves
within <svn-update-bt path="${test.sources.dir}/${suite.name }"/>.
And it is missing in maven adaptor, so I guess it is my fault.
Generally, I will using "svn co" rather than "svn co -N" to develop a new
adaptor.
This will download the whole tests directly, so I overlook this problem.
I'll supply a patch for maven test as well as all the other adaptors I
raised.
Thanks very much to point it out.
1. update-framework of build.xml
<target name="update-framework"
unless="framework.parameters.repository.noupdate">
<!-- do update of framework implementation and test suite
integration scripts -->
<exec executable="svn" dir="${ root.dir}" failonerror="true">
<arg line="update ${scripts.dir} ${adaptors.dir}"/>
</exec>
</target>
2007/12/21, Nathan Beyer < nbeyer@xxxxxxxxxxx>:
>
> The README does not say I need to checkout that folder and it's very
> specific about the checkout command using the "-N" to NOT check out
> any sub-folder. Is the documentation wrong? I'm specifically try to
> get this thing to work out of the box because we need to get buildtest
> 2.0 out of permanent branch and back into the trunk.
>
> On my Windows machine, I switched to Ant 1.6.5 and ran the same
> commands and a lot more is happening now; it checked out the
> 'tests/maven_test' folder and began a build.
>
> -Nathan
>
wrote in message:
> > I have tried this adaptor, it works fine here.
> >
> > And once I rename the <root>/tests/maven_tests to other name, it'll
> fail
> > with the same error message as you.
> > The reason should be that the adaptor cannot find this directory.
> > So I guess you may haven't checked out the directory of
> > <root>/tests/maven_test .
> >
> > Could you please check it out first and try again?
> >
> > 2007/12/21, Nathan Beyer <ndbeyer@xxxxxxxxxxx>:
> >
> > >
> > > I'm having all sorts of issues with buildtest 2.0. Here's what I'm
> > > running, is there anything that's out of whack?
> > >
> > > Ubuntu 7.10 on x86_64 (AMD dual core)
> > > Sun JAVA 1.6
> > > Ant 1.7
> > > SVN 1.4.4
> > >
> > > Windows XP on x86
> > > Sun JAVA 1.6
> > > MSVC 2003
> > > Ant 1.7
> > > SVN 1.4.5
> > >
> > > Here's what I'm doing, per the README [1].
> > >
> > > * svn checkout -N
> > >
> https://svn.apache.org/repos/asf/harmony/enhanced/buildtest/branches/2.0/
> > > * Tweak the buildtest.sh to setup the environment variables and then
> > > run these commands.
> > > * ./buildtest.sh install
> > > * ./buildtest.sh setup -Dtest.suites="classlib,drlvm,maven_test"
> > > * ./buildtest.sh run
> > >
> > > Here's the failure I get --
> > >
> > >
> > > -install:
> > > [echo]
> > > [echo] --------
> > > [echo] WARNING: Target setup of adaptor for Test Suite
> 'maven_test'
> > > FAILED
> > > [echo] -------- with the following exception:
> > > [echo] The following error occurred while executing this line:
> > > [echo] /home/nathan/harmony/bti/scripts/framework.xml:1079:
> > > /home/nathan/harmony/bti/tests/maven_test isn't a valid directory
> > > [delete] Deleting:
> /home/nathan/harmony/bti/build/temp/null1764598389
> > >
> > > check-status:
> > > [echo]
> > > [echo] ------
> > > [echo] ERROR: Setup of Test Suite 'maven_test' FAILED.
> > > [echo] ------
> > >
> > > BUILD FAILED
> > >
> > > The same failure happened on windows; the paths were just a bit
> different.
> > >
> > > I thought this was supposed to work out of the box.
> > >
> > > -Nathan
> > >
> > > [1]
> > >
> https://svn.apache.org/repos/asf/harmony/enhanced/buildtest/branches/2.0/README.txt
> > >
> >
> >
> >
> > --
> > Sean Qiu
> > http://xiaoxia.turendui.com
> >
>
--
Sean Qiu
http://xiaoxia.turendui.com

It seems that <svn-update-bt path="${test.sources.dir}/${suite.name }"/>
cannot check out the tests.

The gut adaptor has the same problem and fails for the same error.
I'll dive into this issues to find out a solution later.
2007/12/21, Sean Qiu <sean.xx.qiu@xxxxxxxxxxx>:
>
> "#>./buildtest.sh install" will call target update-framework[1] of
> build.xml.
> Update-framework only update the <root>/scripts and <root>/adaptors in
> BTI,
> while many tests as well as configurations are in <root>/tests directory.
> Missing <root>/tests cause the build error.
>
> The reason we don't update <root>/tests directly in install step is if we
> just want to run a single test suite,
> it'll be unnecessary to check out all of the tests, since it is
> time-comsuming.
>
> So the "setup" target of adaptor of each test suite is supposed to check
> out individual tests themselves
> within <svn-update-bt path="${test.sources.dir}/${suite.name }"/>.
> And it is missing in maven adaptor, so I guess it is my fault.
>
> Generally, I will using "svn co" rather than "svn co -N" to develop a new
> adaptor.
> This will download the whole tests directly, so I overlook this problem.
> I'll supply a patch for maven test as well as all the other adaptors I
> raised.
>
> Thanks very much to point it out.
>
> 1. update-framework of build.xml
>
> <target name="update-framework"
> unless="framework.parameters.repository.noupdate">
> <!-- do update of framework implementation and test suite
> integration scripts -->
> <exec executable="svn" dir="${ root.dir}" failonerror="true">
> <arg line="update ${scripts.dir} ${adaptors.dir}"/>
> </exec>
> </target>
>
> 2007/12/21, Nathan Beyer < nbeyer@xxxxxxxxxxx>:
> >
> > The README does not say I need to checkout that folder and it's very
> > specific about the checkout command using the "-N" to NOT check out
> > any sub-folder. Is the documentation wrong? I'm specifically try to
> > get this thing to work out of the box because we need to get buildtest
> > 2.0 out of permanent branch and back into the trunk.
> >
> > On my Windows machine, I switched to Ant 1.6.5 and ran the same
> > commands and a lot more is happening now; it checked out the
> > 'tests/maven_test' folder and began a build.
> >
> > -Nathan
> >
wrote in message:
> > > I have tried this adaptor, it works fine here.
> > >
> > > And once I rename the <root>/tests/maven_tests to other name, it'll
> > fail
> > > with the same error message as you.
> > > The reason should be that the adaptor cannot find this directory.
> > > So I guess you may haven't checked out the directory of
> > > <root>/tests/maven_test .
> > >
> > > Could you please check it out first and try again?
> > >
> > > 2007/12/21, Nathan Beyer <ndbeyer@xxxxxxxxxxx>:
> > >
> > > >
> > > > I'm having all sorts of issues with buildtest 2.0. Here's what I'm
> > > > running, is there anything that's out of whack?
> > > >
> > > > Ubuntu 7.10 on x86_64 (AMD dual core)
> > > > Sun JAVA 1.6
> > > > Ant 1.7
> > > > SVN 1.4.4
> > > >
> > > > Windows XP on x86
> > > > Sun JAVA 1.6
> > > > MSVC 2003
> > > > Ant 1.7
> > > > SVN 1.4.5
> > > >
> > > > Here's what I'm doing, per the README [1].
> > > >
> > > > * svn checkout -N
> > > >
> > https://svn.apache.org/repos/asf/harmony/enhanced/buildtest/branches/2.0/
> > > > * Tweak the buildtest.sh to setup the environment variables and then
> > > > run these commands.
> > > > * ./buildtest.sh install
> > > > * ./buildtest.sh setup -Dtest.suites="classlib,drlvm,maven_test"
> > > > * ./buildtest.sh run
> > > >
> > > > Here's the failure I get --
> > > >
> > > >
> > > > -install:
> > > > [echo]
> > > > [echo] --------
> > > > [echo] WARNING: Target setup of adaptor for Test Suite
> > 'maven_test'
> > > > FAILED
> > > > [echo] -------- with the following exception:
> > > > [echo] The following error occurred while executing this line:
> > > > [echo] /home/nathan/harmony/bti/scripts/framework.xml:1079:
> > > > /home/nathan/harmony/bti/tests/maven_test isn't a valid directory
> > > > [delete] Deleting:
> > /home/nathan/harmony/bti/build/temp/null1764598389
> > > >
> > > > check-status:
> > > > [echo]
> > > > [echo] ------
> > > > [echo] ERROR: Setup of Test Suite 'maven_test' FAILED.
> > > > [echo] ------
> > > >
> > > > BUILD FAILED
> > > >
> > > > The same failure happened on windows; the paths were just a bit
> > different.
> > > >
> > > > I thought this was supposed to work out of the box.
> > > >
> > > > -Nathan
> > > >
> > > > [1]
> > > >
> > https://svn.apache.org/repos/asf/harmony/enhanced/buildtest/branches/2.0/README.txt
> > > >
> > >
> > >
> > >
> > > --
> > > Sean Qiu
> > > http://xiaoxia.turendui.com
> > >
> >
>
>
>
> --
> Sean Qiu
> http://xiaoxia.turendui.com
>
--
Sean Qiu
http://xiaoxia.turendui.com

<file system> An element of data storage in a {file system}.

	The history of computing is rich in varied kinds of files and
	{file systems}, whether ornate (e.g., {Macintosh file system}
	for a well-known case) or deficient (e.g., many simple
	pre-1980s file systems don't allow {directories}).

	However, the prototypical file has these characteristics:

	* It is a single sequence of bytes (but consider {Macintosh}
	{resource forks}).

	* It has a finite length, unlike, e.g. a {Unix} {device}.

	* It is stored in a {non-volatile storage} medium (but see
	{ramdrive}).

	* It exists (nominally) in a {directory}.

	* It has a name that it can be referred to by in file
	operations, possibly in combination with its {path}.

	Additionally, a file system may associate other information
	with a file, such as {permission} bits or other {file
	attributes}; timestamps for file creation, last revision, and
	last access; revision numbers (a` la VMS), and other kinds of
	{magic}.

	Compare: {document}.

	(1997-04-08)

<programming> One of a sequence of copies of a program, each
	incorporating new modifications.  Each version is usually
	identified by a number, commonly of the form X.Y where X is
	the major version number and Y is the release number.
	Typically an increment in X (with Y reset to zero) signifies a
	substantial increase in the function of the program or a
	partial or total re-implementation, whereas Y increases each
	time the progam is changed in any way and re-released.

	Version numbers are useful so that the user can know if the
	program has changed ({bugs} have been fixed or new functions
	added) since he obtained his copy and the programmer can tell
	if a bug report relates to the current version.  It is thus
	always important to state the version when reporting bugs.
	Statements about compatibility between different software
	components should always say which versions they apply to.

	See {change management}.

	(1997-12-07)

<programming> Any piece of program code in a {high-level
	language} which, when (if) its execution terminates, returns a
	value.  In most programming languages, expressions consist of
	constants, variables, operators, functions, and {parentheses}.
	The operators and functions may be built-in or user defined.
	Languages differ on how expressions of different {types} may
	be combined - with some combination of explicit {casts} and
	implicit {coercions}.

	The {syntax} of expressions generally follows conventional
	mathematical notation, though some languages such as {Lisp} or
	{Forth} have their own idiosyncratic syntax.

	(2001-05-14)

> > > > > * Tweak the buildtest.sh to setup the environment variables and
then
> > > > > run these commands.
> > > > > * ./buildtest.sh install
> > > > > * ./buildtest.sh setup -Dtest.suites="classlib,drlvm,maven_test"
> > > > > * ./buildtest.sh run
> > > > >
> > > > > Here's the failure I get --
> > > > >
> > > > >
> > > > > -install:
> > > > > [echo]
> > > > > [echo] --------
> > > > > [echo] WARNING: Target setup of adaptor for Test Suite
> > > 'maven_test'
> > > > > FAILED
> > > > > [echo] -------- with the following exception:
> > > > > [echo] The following error occurred while executing this
line:
> > > > > [echo] /home/nathan/harmony/bti/scripts/framework.xml:1079:
> > > > > /home/nathan/harmony/bti/tests/maven_test isn't a valid
directory
> > > > > [delete] Deleting:
> > > /home/nathan/harmony/bti/build/temp/null1764598389
> > > > >
> > > > > check-status:
> > > > > [echo]
> > > > > [echo] ------
> > > > > [echo] ERROR: Setup of Test Suite 'maven_test' FAILED.
> > > > > [echo] ------
> > > > >
> > > > > BUILD FAILED
> > > > >
> > > > > The same failure happened on windows; the paths were just a bit
> > > different.
> > > > >
> > > > > I thought this was supposed to work out of the box.
> > > > >
> > > > > -Nathan
> > > > >
> > > > > [1]
> > > > >
> > >

> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Sean Qiu
> > > > http://xiaoxia.turendui.com
> > > >
> > >
> >
> >
> >
> > --
> > Sean Qiu
> > http://xiaoxia.turendui.com
> >
>
>
>
> --
> Sean Qiu
> http://xiaoxia.turendui.com

Yes. The root of the problem is that the behavior of task
*<xmlproperty>*is changed in ANT
1.7.0.
Loading parameters.xml [1] property file with ant, the value of "
parameter.required.noupdate" is different between version 1.6.5 and 1.7.0 of
ANT. In the case of 1.6.5, value of the property is *unset *but *"" *in
1.7.0.
So the expression in framework.xml [2] will always return false,It makes
that the "*do-svn-update-bt*" unreachable and the script cannot find the
tests directory before checking it out.
I have reported a jira [3] and supplied the patch.
1. parameters.xml
<parameters>
<required/>
<noupdate description="Turns off local BTI repository updates on
'install' and 'setup' stages."/>
</repository>
</parameters>
2. framework.xml
<if>
<and>
<not><isset property="
framework.parameters.repository.noupdate"/></not>
<not><contains string="${
framework.parameters.repository.awaited}"
substring="|${tmp.relative.path
}|"/></not>
</and>
<then>
<do-svn-update-bt path="${tmp.relative.path}"/>
</then>
</if>
3.https://issues.apache.org/jira/browse/HARMONY-5337
2007/12/21, Stepan Mishura <stepan.mishura@xxxxxxxxxxx>:
wrote in message:
> > It seems that <svn-update-bt path="${test.sources.dir}/${suite.name }"/>
> > cannot check out the tests.
>
> Do you mean fail with ANT 1.7? I assume it works OK with 1.6.5.
>
> -Stepan.
>
> > The gut adaptor has the same problem and fails for the same error.
> >
> > I'll dive into this issues to find out a solution later.
> >
> > 2007/12/21, Sean Qiu <sean.xx.qiu@xxxxxxxxxxx>:
> > >
> > > "#>./buildtest.sh install" will call target update-framework[1] of
> > > build.xml.
> > > Update-framework only update the <root>/scripts and <root>/adaptors in
> > > BTI,
> > > while many tests as well as configurations are in <root>/tests
directory.
> > > Missing <root>/tests cause the build error.
> > >
> > > The reason we don't update <root>/tests directly in install step is
if we
> > > just want to run a single test suite,
> > > it'll be unnecessary to check out all of the tests, since it is
> > > time-comsuming.
> > >
> > > So the "setup" target of adaptor of each test suite is supposed to
check
> > > out individual tests themselves
> > > within <svn-update-bt path="${test.sources.dir}/${suite.name }"/>.
> > > And it is missing in maven adaptor, so I guess it is my fault.
> > >
> > > Generally, I will using "svn co" rather than "svn co -N" to develop a
new
> > > adaptor.
> > > This will download the whole tests directly, so I overlook this
problem.
> > > I'll supply a patch for maven test as well as all the other
adaptors I
> > > raised.
> > >
> > > Thanks very much to point it out.
> > >
> > > 1. update-framework of build.xml
> > >
> > > <target name="update-framework"
> > > unless="framework.parameters.repository.noupdate">
> > > <!-- do update of framework implementation and test suite
> > > integration scripts -->
> > > <exec executable="svn" dir="${ root.dir}" failonerror="true">
> > > <arg line="update ${scripts.dir} ${adaptors.dir}"/>
> > > </exec>
> > > </target>
> > >
> > > 2007/12/21, Nathan Beyer < nbeyer@xxxxxxxxxxx>:
> > > >
> > > > The README does not say I need to checkout that folder and it's very
> > > > specific about the checkout command using the "-N" to NOT check out
> > > > any sub-folder. Is the documentation wrong? I'm specifically try to
> > > > get this thing to work out of the box because we need to get
buildtest
> > > > 2.0 out of permanent branch and back into the trunk.
> > > >
> > > > On my Windows machine, I switched to Ant 1.6.5 and ran the same
> > > > commands and a lot more is happening now; it checked out the
> > > > 'tests/maven_test' folder and began a build.
> > > >
> > > > -Nathan
> > > >
wrote in message:
> > > > > I have tried this adaptor, it works fine here.
> > > > >
> > > > > And once I rename the <root>/tests/maven_tests to other name, it
will
> > > > fail
> > > > > with the same error message as you.
> > > > > The reason should be that the adaptor cannot find this directory.
> > > > > So I guess you may haven't checked out the directory of
> > > > > <root>/tests/maven_test .
> > > > >
> > > > > Could you please check it out first and try again?
> > > > >
> > > > > 2007/12/21, Nathan Beyer <ndbeyer@xxxxxxxxxxx>:
> > > > >
> > > > > >
> > > > > > I'm having all sorts of issues with buildtest 2.0. Here's what
I'm
> > > > > > running, is there anything that's out of whack?
> > > > > >
> > > > > > Ubuntu 7.10 on x86_64 (AMD dual core)
> > > > > > Sun JAVA 1.6
> > > > > > Ant 1.7
> > > > > > SVN 1.4.4
> > > > > >
> > > > > > Windows XP on x86
> > > > > > Sun JAVA 1.6
> > > > > > MSVC 2003
> > > > > > Ant 1.7
> > > > > > SVN 1.4.5
> > > > > >
> > > > > > Here's what I'm doing, per the README [1].
> > > > > >
> > > > > > * svn checkout -N
> > > > > >
> > > >
https://svn.apache.org/repos/asf/harmony/enhanced/buildtest/branches/2.0/
> > > > > > * Tweak the buildtest.sh to setup the environment variables and
then
> > > > > > run these commands.
> > > > > > * ./buildtest.sh install
> > > > > > * ./buildtest.sh setup -Dtest.suites="classlib,drlvm,maven_test"
> > > > > > * ./buildtest.sh run
> > > > > >
> > > > > > Here's the failure I get --
> > > > > >
> > > > > >
> > > > > > -install:
> > > > > > [echo]
> > > > > > [echo] --------
> > > > > > [echo] WARNING: Target setup of adaptor for Test Suite
> > > > 'maven_test'
> > > > > > FAILED
> > > > > > [echo] -------- with the following exception:
> > > > > > [echo] The following error occurred while executing this
line:
> > > > > > [echo] /home/nathan/harmony/bti/scripts/framework.xml:1079:
> > > > > > /home/nathan/harmony/bti/tests/maven_test isn't a valid
directory
> > > > > > [delete] Deleting:
> > > > /home/nathan/harmony/bti/build/temp/null1764598389
> > > > > >
> > > > > > check-status:
> > > > > > [echo]
> > > > > > [echo] ------
> > > > > > [echo] ERROR: Setup of Test Suite 'maven_test' FAILED.
> > > > > > [echo] ------
> > > > > >
> > > > > > BUILD FAILED
> > > > > >
> > > > > > The same failure happened on windows; the paths were just a bit
> > > > different.
> > > > > >
> > > > > > I thought this was supposed to work out of the box.
> > > > > >
> > > > > > -Nathan
> > > > > >
> > > > > > [1]
> > > > > >
> > > >
https://svn.apache.org/repos/asf/harmony/enhanced/buildtest/branches/2.0/README.txt
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Sean Qiu
> > > > > http://xiaoxia.turendui.com
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Sean Qiu
> > > http://xiaoxia.turendui.com
> > >
> >
> >
> >
> > --
> > Sean Qiu
> > http://xiaoxia.turendui.com
>
--
Sean Qiu
http://xiaoxia.turendui.com

That fix seems to be helping, but I'm back to the same error I was
seeing before with the maven_test.
[JAVA] [exec] [INFO] BUILD SUCCESSFUL
[JAVA] [exec] [INFO]
------------------------------------------------------------------------
[JAVA] [exec] [INFO] Total time: 50 seconds
[JAVA] [exec] [INFO] Finished at: Mon Dec 24 21:42:49 CST 2007
[JAVA] [exec] [INFO] Final Memory: 32M/152M
[JAVA] [exec] [INFO]
------------------------------------------------------------------------
[JAVA] [echo]
work.dir:/home/nathan/harmony/bt/build/checkouts/maven_test
[JAVA]
[JAVA] restore.maven.pom:
[JAVA] [copy] Copying 1 file to
/home/nathan/harmony/bt/build/checkouts/maven_test/maven-2.0.7-src
[JAVA]
[JAVA] compose.report:
[JAVA] [delete] Deleting directory
/home/nathan/harmony/bt/build/checkouts/maven_test/logs
[JAVA] [delete] Deleting:
/home/nathan/harmony/bt/build/checkouts/maven_test/report.txt
[JAVA] [mkdir] Created dir:
/home/nathan/harmony/bt/build/checkouts/maven_test/logs
[JAVA] [copy] Copying 49 files to
/home/nathan/harmony/bt/build/checkouts/maven_test/logs
[JAVA] [copy] Copying 49 files to
/home/nathan/harmony/bt/build/results/maven_test/results/reports
[JAVA] [concat] No existing resources and no nested text, doing
nothing
[JAVA] [concat] No existing resources and no nested text, doing
nothing
[JAVA] [copy] Copying 2 files to
/home/nathan/harmony/bt/build/results/maven_test/results
[JAVA] [mkdir] Created dir:
/home/nathan/harmony/bt/build/results/maven_test/20071224_0941
[JAVA] [copy] Warning: Couldn't find file
/home/nathan/harmony/bt/build/checkouts/maven_test/tmpfile.results.txt
to copy.
[JAVA] [replaceregexp] The following file is missing:
'/home/nathan/harmony/bt/build/checkouts/maven_test/tmpfile.results.failed.error.txt'
[JAVA] [copy] Warning: Couldn't find file
/home/nathan/harmony/bt/build/checkouts/maven_test/tmpfile.results.failed.error.txt
to copy.
[JAVA] [length]
/home/nathan/harmony/bt/build/checkouts/maven_test/tmpfile.results.failed.txt
doesn't exist
[JAVA] [copy] Warning: Couldn't find file
/home/nathan/harmony/bt/build/checkouts/maven_test/tmpfile.results.failed.error.txt
to copy.
[JAVA] [length]
/home/nathan/harmony/bt/build/checkouts/maven_test/tmpfile.results.error.txt
doesn't exist
[JAVA] [concat]
/home/nathan/harmony/bt/build/checkouts/maven_test/tmpfile.results.failed.error.txt
doesn't exist.
[JAVA] [copy] Copying 51 files to
/home/nathan/harmony/bt/build/results/maven_test/20071224_0941
[JAVA]
[JAVA] check.status:
[JAVA]
[JAVA] BUILD FAILED
[JAVA] /home/nathan/harmony/bt/tests/maven_test/build.xml:311:
Maven run failed: there are test failures
[JAVA]
wrote in message:
> Yes. The root of the problem is that the behavior of task
> *<xmlproperty>*is changed in ANT
> 1.7.0.
>
> Loading parameters.xml [1] property file with ant, the value of "
> parameter.required.noupdate" is different between version 1.6.5 and
1.7.0 of
> ANT. In the case of 1.6.5, value of the property is *unset *but *"" *in
> 1.7.0.
>
> So the expression in framework.xml [2] will always return false,It makes
> that the "*do-svn-update-bt*" unreachable and the script cannot find the
> tests directory before checking it out.
>
> I have reported a jira [3] and supplied the patch.
>
> 1. parameters.xml
> <parameters>
> <required/>
> <noupdate description="Turns off local BTI repository updates on
> 'install' and 'setup' stages."/>
> </repository>
> </parameters>
>
> 2. framework.xml
> <if>
> <and>
> <not><isset property="
> framework.parameters.repository.noupdate"/></not>
> <not><contains string="${
> framework.parameters.repository.awaited}"
> substring="|${tmp.relative.path
> }|"/></not>
> </and>
> <then>
> <do-svn-update-bt path="${tmp.relative.path}"/>
> </then>
> </if>
>
> 3.https://issues.apache.org/jira/browse/HARMONY-5337
>
> 2007/12/21, Stepan Mishura <stepan.mishura@xxxxxxxxxxx>:
>
wrote in message:
> > > It seems that <svn-update-bt path="${test.sources.dir}/${suite.name}"/>
> > > cannot check out the tests.
> >
> > Do you mean fail with ANT 1.7? I assume it works OK with 1.6.5.
> >
> > -Stepan.
> >
> > > The gut adaptor has the same problem and fails for the same error.
> > >
> > > I'll dive into this issues to find out a solution later.
> > >
> > > 2007/12/21, Sean Qiu <sean.xx.qiu@xxxxxxxxxxx>:
> > > >
> > > > "#>./buildtest.sh install" will call target update-framework[1] of
> > > > build.xml.
> > > > Update-framework only update the <root>/scripts and
<root>/adaptors in
> > > > BTI,
> > > > while many tests as well as configurations are in <root>/tests
> directory.
> > > > Missing <root>/tests cause the build error.
> > > >
> > > > The reason we don't update <root>/tests directly in install step
is
> if we
> > > > just want to run a single test suite,
> > > > it'll be unnecessary to check out all of the tests, since it is
> > > > time-comsuming.
> > > >
> > > > So the "setup" target of adaptor of each test suite is supposed to
> check
> > > > out individual tests themselves
> > > > within <svn-update-bt path="${test.sources.dir}/${suite.name }"/>.
> > > > And it is missing in maven adaptor, so I guess it is my fault.
> > > >
> > > > Generally, I will using "svn co" rather than "svn co -N" to
develop a
> new
> > > > adaptor.
> > > > This will download the whole tests directly, so I overlook this
> problem.
> > > > I'll supply a patch for maven test as well as all the other
> adaptors I
> > > > raised.
> > > >
> > > > Thanks very much to point it out.
> > > >
> > > > 1. update-framework of build.xml
> > > >
> > > > <target name="update-framework"
> > > > unless="framework.parameters.repository.noupdate">
> > > > <!-- do update of framework implementation and test suite
> > > > integration scripts -->
> > > > <exec executable="svn" dir="${ root.dir}"
failonerror="true">
> > > > <arg line="update ${scripts.dir} ${adaptors.dir}"/>
> > > > </exec>
> > > > </target>
> > > >
> > > > 2007/12/21, Nathan Beyer < nbeyer@xxxxxxxxxxx>:
> > > > >
> > > > > The README does not say I need to checkout that folder and it's
very
> > > > > specific about the checkout command using the "-N" to NOT check
out
> > > > > any sub-folder. Is the documentation wrong? I'm specifically try
to
> > > > > get this thing to work out of the box because we need to get
> buildtest
> > > > > 2.0 out of permanent branch and back into the trunk.
> > > > >
> > > > > On my Windows machine, I switched to Ant 1.6.5 and ran the same
> > > > > commands and a lot more is happening now; it checked out the
> > > > > 'tests/maven_test' folder and began a build.
> > > > >
> > > > > -Nathan
> > > > >
wrote in message:
> > > > > > I have tried this adaptor, it works fine here.
> > > > > >
> > > > > > And once I rename the <root>/tests/maven_tests to other name,
it
> will
> > > > > fail
> > > > > > with the same error message as you.
> > > > > > The reason should be that the adaptor cannot find this
directory.
> > > > > > So I guess you may haven't checked out the directory of
> > > > > > <root>/tests/maven_test .
> > > > > >
> > > > > > Could you please check it out first and try again?
> > > > > >
> > > > > > 2007/12/21, Nathan Beyer <ndbeyer@xxxxxxxxxxx>:
> > > > > >
> > > > > > >
> > > > > > > I'm having all sorts of issues with buildtest 2.0. Here's
what
> I'm
> > > > > > > running, is there anything that's out of whack?
> > > > > > >
> > > > > > > Ubuntu 7.10 on x86_64 (AMD dual core)
> > > > > > > Sun JAVA 1.6
> > > > > > > Ant 1.7
> > > > > > > SVN 1.4.4
> > > > > > >
> > > > > > > Windows XP on x86
> > > > > > > Sun JAVA 1.6
> > > > > > > MSVC 2003
> > > > > > > Ant 1.7
> > > > > > > SVN 1.4.5
> > > > > > >
> > > > > > > Here's what I'm doing, per the README [1].
> > > > > > >
> > > > > > > * svn checkout -N
> > > > > > >
> > > > >
>
https://svn.apache.org/repos/asf/harmony/enhanced/buildtest/branches/2.0/
> > > > > > > * Tweak the buildtest.sh to setup the environment variables
and
> then
> > > > > > > run these commands.
> > > > > > > * ./buildtest.sh install
> > > > > > > * ./buildtest.sh setup -Dtest.suites=
"classlib,drlvm,maven_test"
> > > > > > > * ./buildtest.sh run
> > > > > > >
> > > > > > > Here's the failure I get --
> > > > > > >
> > > > > > >
> > > > > > > -install:
> > > > > > > [echo]
> > > > > > > [echo] --------
> > > > > > > [echo] WARNING: Target setup of adaptor for Test Suite
> > > > > 'maven_test'
> > > > > > > FAILED
> > > > > > > [echo] -------- with the following exception:
> > > > > > > [echo] The following error occurred while executing
this
> line:
> > > > > > > [echo]
/home/nathan/harmony/bti/scripts/framework.xml:1079:
> > > > > > > /home/nathan/harmony/bti/tests/maven_test isn't a valid
> directory
> > > > > > > [delete] Deleting:
> > > > > /home/nathan/harmony/bti/build/temp/null1764598389
> > > > > > >
> > > > > > > check-status:
> > > > > > > [echo]
> > > > > > > [echo] ------
> > > > > > > [echo] ERROR: Setup of Test Suite 'maven_test' FAILED.
> > > > > > > [echo] ------
> > > > > > >
> > > > > > > BUILD FAILED
> > > > > > >
> > > > > > > The same failure happened on windows; the paths were just a
bit
> > > > > different.
> > > > > > >
> > > > > > > I thought this was supposed to work out of the box.
> > > > > > >
> > > > > > > -Nathan
> > > > > > >
> > > > > > > [1]
> > > > > > >
> > > > >
>
https://svn.apache.org/repos/asf/harmony/enhanced/buildtest/branches/2.0/README.txt
> > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Sean Qiu
> > > > > > http://xiaoxia.turendui.com
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Sean Qiu
> > > > http://xiaoxia.turendui.com
> > > >
> > >
> > >
> > >
> > > --
> > > Sean Qiu
> > > http://xiaoxia.turendui.com
> >
>
>
>
> --
>
> Sean Qiu
> http://xiaoxia.turendui.com
>
--

It works for me and I cannot find the root problem according to your message
pasted.
Could you please check the content of
<root>/build/maven_test/results/reports.txt?
It'll summarize the test results ant the failure can be found in
<root>/build/maven_test/results/output.txt.
The failure's detail is place in xml/<Testname>.xml.
It may help to find out the actual cause that the build failed.
2007/12/25, Nathan Beyer <nbeyer@xxxxxxxxxxx>:
>
> That fix seems to be helping, but I'm back to the same error I was
> seeing before with the maven_test.
>
> [JAVA] [exec] [INFO] BUILD SUCCESSFUL
> [JAVA] [exec] [INFO]
> ------------------------------------------------------------------------
> [JAVA] [exec] [INFO] Total time: 50 seconds
> [JAVA] [exec] [INFO] Finished at: Mon Dec 24 21:42:49 CST 2007
> [JAVA] [exec] [INFO] Final Memory: 32M/152M
> [JAVA] [exec] [INFO]
> ------------------------------------------------------------------------
> [JAVA] [echo]
> work.dir:/home/nathan/harmony/bt/build/checkouts/maven_test
> [JAVA]
> [JAVA] restore.maven.pom:
> [JAVA] [copy] Copying 1 file to
> /home/nathan/harmony/bt/build/checkouts/maven_test/maven-2.0.7-src
> [JAVA]
> [JAVA] compose.report:
> [JAVA] [delete] Deleting directory
> /home/nathan/harmony/bt/build/checkouts/maven_test/logs
> [JAVA] [delete] Deleting:
> /home/nathan/harmony/bt/build/checkouts/maven_test/report.txt
> [JAVA] [mkdir] Created dir:
> /home/nathan/harmony/bt/build/checkouts/maven_test/logs
> [JAVA] [copy] Copying 49 files to
> /home/nathan/harmony/bt/build/checkouts/maven_test/logs
> [JAVA] [copy] Copying 49 files to
> /home/nathan/harmony/bt/build/results/maven_test/results/reports
> [JAVA] [concat] No existing resources and no nested text, doing
> nothing
> [JAVA] [concat] No existing resources and no nested text, doing
> nothing
> [JAVA] [copy] Copying 2 files to
> /home/nathan/harmony/bt/build/results/maven_test/results
> [JAVA] [mkdir] Created dir:
> /home/nathan/harmony/bt/build/results/maven_test/20071224_0941
> [JAVA] [copy] Warning: Couldn't find file
> /home/nathan/harmony/bt/build/checkouts/maven_test/tmpfile.results.txt
> to copy.
> [JAVA] [replaceregexp] The following file is missing:
>
> '/home/nathan/harmony/bt/build/checkouts/maven_test/tmpfile.results.failed.error.txt'
> [JAVA] [copy] Warning: Couldn't find file
>
> /home/nathan/harmony/bt/build/checkouts/maven_test/tmpfile.results.failed.error.txt
> to copy.
> [JAVA] [length]
>
> /home/nathan/harmony/bt/build/checkouts/maven_test/tmpfile.results.failed.txt
> doesn't exist
> [JAVA] [copy] Warning: Couldn't find file
>
> /home/nathan/harmony/bt/build/checkouts/maven_test/tmpfile.results.failed.error.txt
> to copy.
> [JAVA] [length]
>
> /home/nathan/harmony/bt/build/checkouts/maven_test/tmpfile.results.error.txt
> doesn't exist
> [JAVA] [concat]
>
> /home/nathan/harmony/bt/build/checkouts/maven_test/tmpfile.results.failed.error.txt
> doesn't exist.
> [JAVA] [copy] Copying 51 files to
> /home/nathan/harmony/bt/build/results/maven_test/20071224_0941
> [JAVA]
> [JAVA] check.status:
> [JAVA]
> [JAVA] BUILD FAILED
> [JAVA] /home/nathan/harmony/bt/tests/maven_test/build.xml:311:
> Maven run failed: there are test failures
> [JAVA]
>
>
>
wrote in message:
> > Yes. The root of the problem is that the behavior of task
> > *<xmlproperty>*is changed in ANT
> > 1.7.0.
> >
> > Loading parameters.xml [1] property file with ant, the value of "
> > parameter.required.noupdate" is different between version 1.6.5 and
> 1.7.0 of
> > ANT. In the case of 1.6.5, value of the property is *unset *but *"" *in
> > 1.7.0.
> >
> > So the expression in framework.xml [2] will always return false,It makes
> > that the "*do-svn-update-bt*" unreachable and the script cannot find the
> > tests directory before checking it out.
> >
> > I have reported a jira [3] and supplied the patch.
> >
> > 1. parameters.xml
> > <parameters>
> > <required/>
> > <noupdate description="Turns off local BTI repository updates on
> > 'install' and 'setup' stages."/>
> > </repository>
> > </parameters>
> >
> > 2. framework.xml
> > <if>
> > <and>
> > <not><isset property="
> > framework.parameters.repository.noupdate"/></not>
> > <not><contains string="${
> > framework.parameters.repository.awaited}"
> > substring="|${tmp.relative.path
> > }|"/></not>
> > </and>
> > <then>
> > <do-svn-update-bt path="${tmp.relative.path}"/>
> > </then>
> > </if>
> >
> > 3.https://issues.apache.org/jira/browse/HARMONY-5337
> >
> > 2007/12/21, Stepan Mishura <stepan.mishura@xxxxxxxxxxx>:
> >
wrote in message:
> > > > It seems that <svn-update-bt path="${test.sources.dir}/${suite.name}"/>
> > > > cannot check out the tests.
> > >
> > > Do you mean fail with ANT 1.7? I assume it works OK with 1.6.5.
> > >
> > > -Stepan.
> > >
> > > > The gut adaptor has the same problem and fails for the same error.
> > > >
> > > > I'll dive into this issues to find out a solution later.
> > > >
> > > > 2007/12/21, Sean Qiu <sean.xx.qiu@xxxxxxxxxxx>:
> > > > >
> > > > > "#>./buildtest.sh install" will call target update-framework[1] of
> > > > > build.xml.
> > > > > Update-framework only update the <root>/scripts and
> <root>/adaptors in
> > > > > BTI,
> > > > > while many tests as well as configurations are in <root>/tests
> > directory.
> > > > > Missing <root>/tests cause the build error.
> > > > >
> > > > > The reason we don't update <root>/tests directly in install step
> is
> > if we
> > > > > just want to run a single test suite,
> > > > > it'll be unnecessary to check out all of the tests, since it is
> > > > > time-comsuming.
> > > > >
> > > > > So the "setup" target of adaptor of each test suite is supposed to
> > check
> > > > > out individual tests themselves
> > > > > within <svn-update-bt path="${test.sources.dir}/${suite.name }"/>.
> > > > > And it is missing in maven adaptor, so I guess it is my fault.
> > > > >
> > > > > Generally, I will using "svn co" rather than "svn co -N" to
> develop a
> > new
> > > > > adaptor.
> > > > > This will download the whole tests directly, so I overlook this
> > problem.
> > > > > I'll supply a patch for maven test as well as all the other
> > adaptors I
> > > > > raised.
> > > > >
> > > > > Thanks very much to point it out.
> > > > >
> > > > > 1. update-framework of build.xml
> > > > >
> > > > > <target name="update-framework"
> > > > > unless="framework.parameters.repository.noupdate">
> > > > > <!-- do update of framework implementation and test suite
> > > > > integration scripts -->
> > > > > <exec executable="svn" dir="${ root.dir}"
> failonerror="true">
> > > > > <arg line="update ${scripts.dir} ${adaptors.dir}"/>
> > > > > </exec>
> > > > > </target>
> > > > >
> > > > > 2007/12/21, Nathan Beyer < nbeyer@xxxxxxxxxxx>:
> > > > > >
> > > > > > The README does not say I need to checkout that folder and it's
> very
> > > > > > specific about the checkout command using the "-N" to NOT check
> out
> > > > > > any sub-folder. Is the documentation wrong? I'm specifically try
> to
> > > > > > get this thing to work out of the box because we need to get
> > buildtest
> > > > > > 2.0 out of permanent branch and back into the trunk.
> > > > > >
> > > > > > On my Windows machine, I switched to Ant 1.6.5 and ran the same
> > > > > > commands and a lot more is happening now; it checked out the
> > > > > > 'tests/maven_test' folder and began a build.
> > > > > >
> > > > > > -Nathan
> > > > > >
wrote in message:
> > > > > > > I have tried this adaptor, it works fine here.
> > > > > > >
> > > > > > > And once I rename the <root>/tests/maven_tests to other name,
> it
> > will
> > > > > > fail
> > > > > > > with the same error message as you.
> > > > > > > The reason should be that the adaptor cannot find this
> directory.
> > > > > > > So I guess you may haven't checked out the directory of
> > > > > > > <root>/tests/maven_test .
> > > > > > >
> > > > > > > Could you please check it out first and try again?
> > > > > > >
> > > > > > > 2007/12/21, Nathan Beyer <ndbeyer@xxxxxxxxxxx>:
> > > > > > >
> > > > > > > >
> > > > > > > > I'm having all sorts of issues with buildtest 2.0. Here's
> what
> > I'm
> > > > > > > > running, is there anything that's out of whack?
> > > > > > > >
> > > > > > > > Ubuntu 7.10 on x86_64 (AMD dual core)
> > > > > > > > Sun JAVA 1.6
> > > > > > > > Ant 1.7
> > > > > > > > SVN 1.4.4
> > > > > > > >
> > > > > > > > Windows XP on x86
> > > > > > > > Sun JAVA 1.6
> > > > > > > > MSVC 2003
> > > > > > > > Ant 1.7
> > > > > > > > SVN 1.4.5
> > > > > > > >
> > > > > > > > Here's what I'm doing, per the README [1].
> > > > > > > >
> > > > > > > > * svn checkout -N
> > > > > > > >
> > > > > >
> >
> https://svn.apache.org/repos/asf/harmony/enhanced/buildtest/branches/2.0/
> > > > > > > > * Tweak the buildtest.sh to setup the environment variables
> and
> > then
> > > > > > > > run these commands.
> > > > > > > > * ./buildtest.sh install
> > > > > > > > * ./buildtest.sh setup -Dtest.suites=
> "classlib,drlvm,maven_test"
> > > > > > > > * ./buildtest.sh run
> > > > > > > >
> > > > > > > > Here's the failure I get --
> > > > > > > >
> > > > > > > >
> > > > > > > > -install:
> > > > > > > > [echo]
> > > > > > > > [echo] --------
> > > > > > > > [echo] WARNING: Target setup of adaptor for Test Suite
> > > > > > 'maven_test'
> > > > > > > > FAILED
> > > > > > > > [echo] -------- with the following exception:
> > > > > > > > [echo] The following error occurred while executing
> this
> > line:
> > > > > > > > [echo]
> /home/nathan/harmony/bti/scripts/framework.xml:1079:
> > > > > > > > /home/nathan/harmony/bti/tests/maven_test isn't a valid
> > directory
> > > > > > > > [delete] Deleting:
> > > > > > /home/nathan/harmony/bti/build/temp/null1764598389
> > > > > > > >
> > > > > > > > check-status:
> > > > > > > > [echo]
> > > > > > > > [echo] ------
> > > > > > > > [echo] ERROR: Setup of Test Suite 'maven_test' FAILED.
> > > > > > > > [echo] ------
> > > > > > > >
> > > > > > > > BUILD FAILED
> > > > > > > >
> > > > > > > > The same failure happened on windows; the paths were just a
> bit
> > > > > > different.
> > > > > > > >
> > > > > > > > I thought this was supposed to work out of the box.
> > > > > > > >
> > > > > > > > -Nathan
> > > > > > > >
> > > > > > > > [1]
> > > > > > > >
> > > > > >
> >
> https://svn.apache.org/repos/asf/harmony/enhanced/buildtest/branches/2.0/README.txt
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Sean Qiu
> > > > > > > http://xiaoxia.turendui.com
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Sean Qiu
> > > > > http://xiaoxia.turendui.com
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Sean Qiu
> > > > http://xiaoxia.turendui.com
> > >
> >
> >
> >
> > --
> >
> > Sean Qiu
> > http://xiaoxia.turendui.com
> >
>
--
Sean Qiu
http://xiaoxia.turendui.com