Alex and Julie--
It appears that the Cruisecontrol box uses a hard-coded path to the
distribution directory; this has now changed as of SVN 233004 from
apache-beehive-incubating-* to apache-beehive-*.
Can someone adjust for this change on CC?
Thanks!
Eddie
On 8/16/05, [EMAIL PROTECTED]
, August 16, 2005 11:10 AM
To: Eddie ONeil; Beehive Developers
Cc: Alex Ramirez
Subject: RE: Beehive Check-in Test (Linux) Failed
I am taking look at this now. Will keep you updated.
Julie
-Original Message-
From: Eddie ONeil [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 16, 2005 10:45
so long.
Julie
-Original Message-
From: Julie Zhuo
Sent: Tuesday, August 16, 2005 11:10 AM
To: Eddie ONeil; Beehive Developers
Cc: Alex Ramirez
Subject: RE: Beehive Check-in Test (Linux) Failed
I am taking look at this now. Will keep you updated.
Julie
-Original Message-
From
This is mine and was fixed a little while ago.
Apologies...
On 8/16/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
View results here -
http://beehive01.bea.com/cruisecontrol/buildresults?log=log20050816173406
I've crawled through the logs, and all the build/test runs are successful.
This appears to be an issue with TCH. Both
http://beehive01.bea.com/downloads/20050606221541/general/build.out and
http://beehive01.bea.com/downloads/20050606221541/general/test.dist.out
show the following error in
I'm guessing that this happened because of the website update
yesterday. It appears that the controls test infrastructure is
relying on the presence of a DTD here:
http://incubator.apache.org/beehive/dtd/gtlf/gtlf-config-2.0.dtd
and that this file no longer exists at this URL. I've put it
The new website just went live, so we'll see if CC passes next time.
On 6/7/05, Eddie ONeil [EMAIL PROTECTED] wrote:
I'm guessing that this happened because of the website update
yesterday. It appears that the controls test infrastructure is
relying on the presence of a DTD here:
Should be fixed with Rich's checkin of svn r179846.
[EMAIL PROTECTED] wrote:
View results here -
http://beehive01.bea.com/cruisecontrol/buildresults?log=log20050603113634
This is failing with the error Application already exists at path
/coreWeb. Joe, are you able to take a look? I believe this has
happened before, but if you need more info on how to fix it, let me know.
Thanks,
Rich
[EMAIL PROTECTED] wrote:
View results here -
Actually, this should be taken care of. I cleaned it up during the
last run which passed the build and dist testing. Just had a slight
snag with NetUI DRTs with coreWeb deployment on Tomcat.
Hopefully that's fixed on the next run...
Richard Feit wrote:
It looks like the svn sync is
Should be fixed with SVN 170221.
After having removed the controls-db sample from the distribution,
I've been having trouble getting a clean nightly run. Removing these
unused references takes away another possible cause of failure...
On 5/15/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hm. This passed locally and is passing on other machines I've got.
Unfortunately, it looks like something has finally tipped the scales
of an ant clean deploy drt for the CC machine.
Joe, what version of the VM is being run on that box?
Thanks.
Eddie
On 5/15/05, [EMAIL PROTECTED]
I've been looking at this OOM problem, and it appears to be related
to repeatedly re-invoking the WSM build which rebuilds every time the
runtime is deployed or the drts run.
I've got a local fix that will be committed when SVN comes back to life.
On 5/15/05, [EMAIL PROTECTED] [EMAIL
My checkin didn't cause this; the test dist is failing with this error:
/home/beehive/cc/tmpdist/beehive-test-dist/build.xml:45: The following error
occurred while executing this line:
Target `wsm.tests' does not exist in this project.
Daryoush, your patch that got submitted with revision 169934
Cc: Joe Pemberton
Subject: Re: Beehive Check-in Test (Linux) Failed
My checkin didn't cause this; the test dist is failing with this
error:
/home/beehive/cc/tmpdist/beehive-test-dist/build.xml:45: The following
error occurred while executing this line:
Target `wsm.tests' does not exist
Please ignore this failure. I am modifying the CruiseControl scripts on
this machine to run the DRTs.
-Joe
-Original Message-
From: Joe Pemberton
Sent: Friday, May 13, 2005 10:53 AM
To: beehive-dev@incubator.apache.org; Joe Pemberton
Subject: Beehive Check-in Test (Linux) Failed
View
The controls DRTs are now failing; I'm guessing that this is as a
result of SVN 170100 having added the ASF license to the .beaninfo files
which are diff'ed to determine a test's success / failure.
Should have this fixed momentarily.
[EMAIL PROTECTED] wrote:
View results here -
Should be fixed temporarily by r168995.
-James
-Original Message-
From: Joe Pemberton
Sent: Friday, May 06, 2005 5:59 PM
To: beehive-dev@incubator.apache.org; Joe Pemberton
Subject: Beehive Check-in Test (Linux) Failed
View results here -
OK, revision 168455 should fix this. I'm running the tests against the
test dist locally, but it's taking a long time. If for some reason it's
still broken, I'll know in a few minutes and will blast out another email.
Richard Feit wrote:
Yes, this is mine -- sorry for the trouble. Just
Mine, hopefully resolved by 168651.
On 5/6/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
View results here -
http://beehive01.bea.com/cruisecontrol/buildresults?log=log20050506140152
Rich:
home/beehive/cc/tmpdist/beehive-test-dist/netui/ant/testWebBuild.xml:93:
/home/beehive/cc/tmpdist/beehive-test-dist/netui/jsf/myfaces-1.0.7/lib
not found.
Is it caused by your r168410?
What needs to be change on the test-dist-build?
-James
-Original Message-
From: Joe Pemberton
Yes, this is mine -- sorry for the trouble. Just verifying that my
local fix is really a fix...
James Song wrote:
Rich:
home/beehive/cc/tmpdist/beehive-test-dist/netui/ant/testWebBuild.xml:93:
/home/beehive/cc/tmpdist/beehive-test-dist/netui/jsf/myfaces-1.0.7/lib
not found.
Is it caused by your
This failed because the CruiseControl box doesn't seem to have the
latest and greatest SVN updates from ControlHaus. Eddie had updated
the system controls there in anticipation of my changes, but these
changes aren't being pulled down.
I ran into a similar issue locally, with the distribution
Hi all,
These tests seem to be oscillating between failure/fix, without any
checkin changes. The issue seems to be this:
[junit] WARNING: failed to obtain test definitions for webapp at(
/coreWeb ) [junit] Test
Looks like a netui test failed:
http://beehive01.bea.com/downloads/20050425115531/netui/drt/html/junit-n
oframes.html
-Original Message-
From: Joe Pemberton
Sent: Monday, April 25, 2005 12:09 PM
To: beehive-dev@incubator.apache.org; Joe Pemberton
Subject: Beehive Check-in Test (Linux)
This break looks like it was caused by a recent change to the
AxisHook. The revision is here:
http://svn.apache.org/viewcvs.cgi?rev=157742view=rev
and the JUnit test break is here:
http://beehive01.bea.com/downloads/20050316054038/wsm/TEST-org.apache.beehive.wsm.axis.AxisHookTest.txt
[EMAIL
I fixed the AxisHookTest so that is passes. Can someone please review
the changes. They appear correct to me, but they should have a code
review. The change is
http://svn.apache.org/viewcvs?view=revrev=157763
Sorry for the extra bit of code cleanup in the checkin. Look at the
Hi, all.
Sorry for any inconvenience.
I forgot the drt before commit.
I'll be careful next time.
Thanks Daryl for your quick fix.
From: Daryl Olander [EMAIL PROTECTED]
Reply-To: Daryl Olander [EMAIL PROTECTED]
To: Beehive Developers beehive-dev@incubator.apache.org
Subject: Re: Beehive Check
So it appears that there is a break in the controls checkin tests that
was caused by the same checkin from this morning.
http://svn.apache.org/viewcvs.cgi?rev=157742view=rev
CC was broken at 5:26 this morning. There were two sets of failures,
the WSM Drts failed in addition the controls check
This is tracked with:
http://issues.apache.org/jira/browse/BEEHIVE-448
Eddie O'Neil wrote:
A second-order problem is that there are three tests in the TCH test
suite that were aborted (and even stack traced), but these didn't fail
the controls test suite. Look at this link and scroll
Check-in Test (Linux) Failed
A second-order problem is that there are three tests in the TCH test
suite that were aborted (and even stack traced), but these didn't fail
the controls test suite. Look at this link and scroll down to the TCH
output:
http://beehive01.bea.com/downloads
accordingly.
James may know more about this..
-Joe
-Original Message-
From: Eddie O'Neil
Sent: Wednesday, March 16, 2005 12:58 PM
To: Beehive Developers
Subject: Re: Beehive Check-in Test (Linux) Failed
My take is that those three test aborts should have failed the entire
Ant process
Sent: Wednesday, March 16, 2005 10:45 AM
To: Beehive Developers
Subject: Re: Beehive Check-in Test (Linux) Failed
A second-order problem is that there are three tests in the TCH
test
suite that were aborted (and even stack traced), but these didn't fail
the controls test suite. Look
accordingly.
James may know more about this..
-Joe
-Original Message-
From: Eddie O'Neil
Sent: Wednesday, March 16, 2005 12:58 PM
To: Beehive Developers
Subject: Re: Beehive Check-in Test (Linux) Failed
My take is that those three test aborts should have failed the entire
Ant
?
-James
-Original Message-
From: Eddie O'Neil
Sent: Wednesday, March 16, 2005 1:27 PM
To: Beehive Developers
Cc: Joe Pemberton; Zachary Smith
Subject: Re: Beehive Check-in Test (Linux) Failed
Hm. I've seen CC machine configs that can handle this sort of thing,
so we should dig
Is this showing a failure because I moved a test to a different package?
The log output shows that the tests ran fine.
Bryan
[EMAIL PROTECTED] wrote:
View results here - http://beehive01.bea.com/cruisecontrol/buildresults?log=log20050309113945
--
Bryan Che
Red Hat, Inc.
10 Technology Park Dr
Ahh...missed those. I'll fix it.
Bryan
Eddie O'Neil wrote:
Yeah, looks like it. Here's the controls test trace and it's related
to not finding WSM classes that have moved into a handlers sub package.
http://beehive01.bea.com/downloads/20050309113945/controls/tch.html
It is definitely a
Cool. Nikhil, Joe, or Zach, can someone fix the controls test
infrastructure to fail when tests are skipped?
Thanks!
Bryan Che wrote:
Ahh...missed those. I'll fix it.
Bryan
Eddie O'Neil wrote:
Yeah, looks like it. Here's the controls test trace and it's
related to not finding WSM
: Beehive Check-in Test (Linux) Failed
Ahh...missed those. I'll fix it.
Bryan
Eddie O'Neil wrote:
Yeah, looks like it. Here's the controls test trace and it's
related
to not finding WSM classes that have moved into a handlers sub
package.
http://beehive01.bea.com/downloads/20050309113945
]
Sent: Wednesday, March 09, 2005 12:15 PM
To: Beehive Developers
Cc: Joe Pemberton; Nikhil Gore
Subject: Re: Beehive Check-in Test (Linux) Failed
Ahh...missed those. I'll fix it.
Bryan
Eddie O'Neil wrote:
Yeah, looks like it. Here's the controls test trace and it's
related
to not finding WSM
This is mine. Apparently, the CC machine required this target...
Putting it back now.
[EMAIL PROTECTED] wrote:
View results here -
http://beehive01.bea.com/cruisecontrol/buildresults?log=log20050308095212
Mike was working on the dashboard I am not sure if it is this problem or
not.
Daryoush
-Original Message-
From: Kyle Marvin [mailto:[EMAIL PROTECTED]
Sent: Friday, March 04, 2005 1:12 PM
To: Beehive Developers
Cc: Joe Pemberton
Subject: Re: Beehive Check-in Test (Linux) Failed
Caused
I'm looking at this.
-Original Message-
From: Nikhil Gore
Sent: Thursday, March 03, 2005 6:26 PM
To: beehive-dev@incubator.apache.org; Joe Pemberton; Nikhil Gore
Subject: Beehive Check-in Test (Linux) Failed
View results here -
+fileset dir=samples/wsm-petstore-dashboard/
/copy
!-- Build the petstore distro --
-Original Message-
From: Nikhil Gore
Sent: Friday, March 04, 2005 3:11 PM
To: Beehive Developers; Kyle Marvin; Michael Merz
Cc: Joe Pemberton
Subject: RE: Beehive Check-in Test (Linux) Failed
This is mine -- fixed with revision 155755 (left out a file).
[EMAIL PROTECTED] wrote:
View results here -
http://beehive01.bea.com/cruisecontrol/buildresults?log=log20050228205429
This is one of those breaks due to a change in the JDBC Control. Please
be sure to look at the General Logs - build.out for details.
- jeremiah
-Original Message-
From: Nikhil Gore
Sent: Tuesday, March 01, 2005 1:36 PM
To: beehive-dev@incubator.apache.org; Joe Pemberton; Nikhil Gore
Should be fixed now, problem with the jdbc control's build file.
- Chad
-Original Message-
From: Jeremiah Johnson
Sent: Tuesday, March 01, 2005 1:33 PM
To: Beehive Developers; Joe Pemberton
Subject: RE: Beehive Check-in Test (Linux) Failed
This is one of those breaks due to a change
Appears that I did this; will have a fix shortly.
Apologies...
[EMAIL PROTECTED] wrote:
View results here -
http://beehive01.bea.com:9090/cruisecontrol/buildresults?log=log20050219102014
Hm. We seem to be in a bad state here with CC. The SVN sync isn't
succeeding because of a resources/beehive directory that was added to
coreWeb this morning. See:
http://beehive01.bea.com:9090/downloads/20050219102014/general/svn_sync.out
And as a result, the classes I've moved can't be
Most possible caused by my r154196. Investigating.
-James
-Original Message-
From: Nikhil Gore
Sent: Thursday, February 17, 2005 4:06 PM
To: beehive-dev@incubator.apache.org; Nikhil Gore
Subject: Beehive Check-in Test (Linux) Failed
View results here -
50 matches
Mail list logo
