You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by DavidSeanTaylor <da...@bluesunrise.com> on 2016/11/08 15:49:20 UTC
build errors
Im seeing these errors with my latest pull today. I ran ‘mvn clean install’
anyone else seeing the errors below?
Running org.apache.pluto.container.util.ArgumentUtilityTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec - in org.apache.pluto.container.util.ArgumentUtilityTest
Results :
Failed tests:
PortletInvokeTest.test4destroy:266 null
PortletInvokeTest.test4init:259 null
PortletInvokeTest.test4resource:306 null
PortletInvokeTest.test4action:274 null
PortletInvokeTest.test4event1:282 null
PortletInvokeTest.test4event2:290 null
PortletInvokeTest.test4render:298 null
Tests run: 1003, Failures: 7, Errors: 0, Skipped: 0
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Pluto ....................................... SUCCESS [ 1.669 s]
[INFO] Java Portlet API V3.0 .............................. SUCCESS [ 19.451 s]
[INFO] Apache Pluto Container API ......................... SUCCESS [ 0.695 s]
[INFO] Apache Pluto Portlet Container ..................... FAILURE [ 18.080 s]
Re: build errors
Posted by DavidSeanTaylor <da...@bluesunrise.com>.
Yes, I fixed the release target, its building now. But it seems to get the same error as I get locally
Failed tests:
PortletInvokeTest.test4destroy:266 null
PortletInvokeTest.test4init:259 null
PortletInvokeTest.test4resource:306 null
PortletInvokeTest.test4action:274 null
PortletInvokeTest.test4event1:282 null
PortletInvokeTest.test4event2:290 null
PortletInvokeTest.test4render:298 null
Tests run: 1003, Failures: 7, Errors: 0, Skipped
> On Nov 9, 2016, at 8:21 AM, Werner Keil <we...@gmail.com> wrote:
>
> At least that one sounds rather trivial:
>
> [ERROR] javac: invalid target release: 1.7
> Usage: javac <options> <source files>
> use -help for a list of possible options
>
>
> Maybe that is not the only reason it fails, but now that Portlet 3 targets Java SE/EE 7, the Jenkins build must be adjusted to run on Java SE 7.
>
> Werner
>
>
> On Wed, Nov 9, 2016 at 4:59 PM, David S Taylor <david@bluesunrise.com <ma...@bluesunrise.com>> wrote:
> Well, I pulled the master branch clean, same problem. Running Java
>
> java version "1.7.0_60"
> Java(TM) SE Runtime Environment (build 1.7.0_60-b19)
> Java HotSpot(TM) 64-Bit Server VM (build 24.60-b09, mixed mode)
>
> Seems that one of my methods in the AnnotatedMethodStore is not initialized correctly, it points to:
>
> class org.apache.pluto.container.reconcile.fixtures.IncompletePortlet
>
> and not the expected Portlet4
>
> "Portlet name='Portlet4', Method type='INIT', Dispatch ID=''" -> " size = 1"
>
> > On Nov 9, 2016, at 6:55 AM, Neil Griffin <neil.griffin@portletfaces.org <ma...@portletfaces.org>> wrote:
> >
> > Hi David,
> >
> > The Liferay Faces team performing builds of Pluto, but we're not seeing the error you mentioned below.
> >
> > Best Regards,
> >
> > Neil
> >
> >> On Nov 8, 2016, at 10:49 AM, DavidSeanTaylor <david@bluesunrise.com <ma...@bluesunrise.com>> wrote:
> >>
> >> Im seeing these errors with my latest pull today. I ran ‘mvn clean install’
> >> anyone else seeing the errors below?
> >>
> >> Running org.apache.pluto.container.util.ArgumentUtilityTest
> >> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec - in org.apache.pluto.container.util.ArgumentUtilityTest
> >>
> >> Results :
> >>
> >> Failed tests:
> >> PortletInvokeTest.test4destroy:266 null
> >> PortletInvokeTest.test4init:259 null
> >> PortletInvokeTest.test4resource:306 null
> >> PortletInvokeTest.test4action:274 null
> >> PortletInvokeTest.test4event1:282 null
> >> PortletInvokeTest.test4event2:290 null
> >> PortletInvokeTest.test4render:298 null
> >>
> >> Tests run: 1003, Failures: 7, Errors: 0, Skipped: 0
> >>
> >> [INFO] ------------------------------------------------------------------------
> >> [INFO] Reactor Summary:
> >> [INFO]
> >> [INFO] Apache Pluto ....................................... SUCCESS [ 1.669 s]
> >> [INFO] Java Portlet API V3.0 .............................. SUCCESS [ 19.451 s]
> >> [INFO] Apache Pluto Container API ......................... SUCCESS [ 0.695 s]
> >> [INFO] Apache Pluto Portlet Container ..................... FAILURE [ 18.080 s]
> >
>
>
Re: build errors
Posted by Werner Keil <we...@gmail.com>.
At least that one sounds rather trivial:
[ERROR] javac: invalid target release: 1.7Usage: javac <options> <source files>
use -help for a list of possible options
Maybe that is not the only reason it fails, but now that Portlet 3 targets
Java SE/EE 7, the Jenkins build must be adjusted to run on Java SE 7.
Werner
On Wed, Nov 9, 2016 at 4:59 PM, David S Taylor <da...@bluesunrise.com>
wrote:
> Well, I pulled the master branch clean, same problem. Running Java
>
> java version "1.7.0_60"
> Java(TM) SE Runtime Environment (build 1.7.0_60-b19)
> Java HotSpot(TM) 64-Bit Server VM (build 24.60-b09, mixed mode)
>
> Seems that one of my methods in the AnnotatedMethodStore is not
> initialized correctly, it points to:
>
> class org.apache.pluto.container.reconcile.fixtures.IncompletePortlet
>
> and not the expected Portlet4
>
> "Portlet name='Portlet4', Method type='INIT', Dispatch ID=''" -> " size =
> 1"
>
> > On Nov 9, 2016, at 6:55 AM, Neil Griffin <ne...@portletfaces.org>
> wrote:
> >
> > Hi David,
> >
> > The Liferay Faces team performing builds of Pluto, but we're not seeing
> the error you mentioned below.
> >
> > Best Regards,
> >
> > Neil
> >
> >> On Nov 8, 2016, at 10:49 AM, DavidSeanTaylor <da...@bluesunrise.com>
> wrote:
> >>
> >> Im seeing these errors with my latest pull today. I ran ‘mvn clean
> install’
> >> anyone else seeing the errors below?
> >>
> >> Running org.apache.pluto.container.util.ArgumentUtilityTest
> >> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002
> sec - in org.apache.pluto.container.util.ArgumentUtilityTest
> >>
> >> Results :
> >>
> >> Failed tests:
> >> PortletInvokeTest.test4destroy:266 null
> >> PortletInvokeTest.test4init:259 null
> >> PortletInvokeTest.test4resource:306 null
> >> PortletInvokeTest.test4action:274 null
> >> PortletInvokeTest.test4event1:282 null
> >> PortletInvokeTest.test4event2:290 null
> >> PortletInvokeTest.test4render:298 null
> >>
> >> Tests run: 1003, Failures: 7, Errors: 0, Skipped: 0
> >>
> >> [INFO] ------------------------------------------------------------
> ------------
> >> [INFO] Reactor Summary:
> >> [INFO]
> >> [INFO] Apache Pluto ....................................... SUCCESS [
> 1.669 s]
> >> [INFO] Java Portlet API V3.0 .............................. SUCCESS [
> 19.451 s]
> >> [INFO] Apache Pluto Container API ......................... SUCCESS [
> 0.695 s]
> >> [INFO] Apache Pluto Portlet Container ..................... FAILURE [
> 18.080 s]
> >
>
>
Re: build errors
Posted by DavidSeanTaylor <da...@bluesunrise.com>.
Hi Scott,
That fixed it, thanks. It now builds locally and on the Apache Jenkins Server:
https://builds.apache.org/job/portals-pluto-trunk/34/ <https://builds.apache.org/job/portals-pluto-trunk/34/>
I just configured Jenkins to send build status emails to pluto-dev
> On Nov 9, 2016, at 11:58 PM, Martin Scott Nicklous <Sc...@de.ibm.com> wrote:
>
> Hi David,
>
> interesting problem. I think I found it - check my latest commit. The test fixture IncompletePortlet.java was mistakenly using the portlet name "Portlet4" for the init and destroy methods rather than the correct name "IncompletePortlet". This led to duplicate init and destroy methods for "Portlet4" to be found, and which one was used depended on the order in which the class scanner found the files, which in turn depended on the order that the file system read the class files from a certain directory. On my system I was lucky I guess and it worked, while on your system, the wrong class file was found first.
>
> Anyway, if that was it, it should be fixed now.
>
> (Note that this should not happen with real portlets, since the configuration reconciliation process that combines the bean portlet configuration with the portlet.xml configuration will not take the portlet into service if duplicate init and destroy methods are found. This checking is ignored in the test code, since some of the tests handle edge cases that require a check to fail.)
>
>
> Mit freundlichen Grüßen, / Kind regards,
> Scott Nicklous
>
> WebSphere Portal Standardization Lead & Technology Consultant
> Specification Lead, JSR 362 Portlet Specification 3.0
> IBM Commerce, Digital Experience Development
> IBM Deutschland Research & Development GmbH / Vorsitzender des Aufsichtsrats: Martina Koederitz / Geschäftsführung: Dirk Wittkopp
> Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294
>
>
> <graycol.gif>David S Taylor ---09.11.2016 16:59:43---Well, I pulled the master branch clean, same problem. Running Java java version "1.7.0_60"
>
> From: David S Taylor <da...@bluesunrise.com>
> To: pluto-dev@portals.apache.org
> Date: 09.11.2016 16:59
> Subject: Re: build errors
>
>
>
>
> Well, I pulled the master branch clean, same problem. Running Java
>
> java version "1.7.0_60"
> Java(TM) SE Runtime Environment (build 1.7.0_60-b19)
> Java HotSpot(TM) 64-Bit Server VM (build 24.60-b09, mixed mode)
>
> Seems that one of my methods in the AnnotatedMethodStore is not initialized correctly, it points to:
>
> class org.apache.pluto.container.reconcile.fixtures.IncompletePortlet
>
> and not the expected Portlet4
>
> "Portlet name='Portlet4', Method type='INIT', Dispatch ID=''" -> " size = 1"
>
> > On Nov 9, 2016, at 6:55 AM, Neil Griffin <ne...@portletfaces.org> wrote:
> >
> > Hi David,
> >
> > The Liferay Faces team performing builds of Pluto, but we're not seeing the error you mentioned below.
> >
> > Best Regards,
> >
> > Neil
> >
> >> On Nov 8, 2016, at 10:49 AM, DavidSeanTaylor <da...@bluesunrise.com> wrote:
> >>
> >> Im seeing these errors with my latest pull today. I ran ‘mvn clean install’
> >> anyone else seeing the errors below?
> >>
> >> Running org.apache.pluto.container.util.ArgumentUtilityTest
> >> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec - in org.apache.pluto.container.util.ArgumentUtilityTest
> >>
> >> Results :
> >>
> >> Failed tests:
> >> PortletInvokeTest.test4destroy:266 null
> >> PortletInvokeTest.test4init:259 null
> >> PortletInvokeTest.test4resource:306 null
> >> PortletInvokeTest.test4action:274 null
> >> PortletInvokeTest.test4event1:282 null
> >> PortletInvokeTest.test4event2:290 null
> >> PortletInvokeTest.test4render:298 null
> >>
> >> Tests run: 1003, Failures: 7, Errors: 0, Skipped: 0
> >>
> >> [INFO] ------------------------------------------------------------------------
> >> [INFO] Reactor Summary:
> >> [INFO]
> >> [INFO] Apache Pluto ....................................... SUCCESS [ 1.669 s]
> >> [INFO] Java Portlet API V3.0 .............................. SUCCESS [ 19.451 s]
> >> [INFO] Apache Pluto Container API ......................... SUCCESS [ 0.695 s]
> >> [INFO] Apache Pluto Portlet Container ..................... FAILURE [ 18.080 s]
> >
>
>
>
>
Re: build errors
Posted by Martin Scott Nicklous <Sc...@de.ibm.com>.
Hi David,
interesting problem. I think I found it - check my latest commit. The test
fixture IncompletePortlet.java was mistakenly using the portlet name
"Portlet4" for the init and destroy methods rather than the correct name
"IncompletePortlet". This led to duplicate init and destroy methods for
"Portlet4" to be found, and which one was used depended on the order in
which the class scanner found the files, which in turn depended on the
order that the file system read the class files from a certain directory.
On my system I was lucky I guess and it worked, while on your system, the
wrong class file was found first.
Anyway, if that was it, it should be fixed now.
(Note that this should not happen with real portlets, since the
configuration reconciliation process that combines the bean portlet
configuration with the portlet.xml configuration will not take the portlet
into service if duplicate init and destroy methods are found. This checking
is ignored in the test code, since some of the tests handle edge cases that
require a check to fail.)
Mit freundlichen Grüßen, / Kind regards,
Scott Nicklous
WebSphere Portal Standardization Lead & Technology Consultant
Specification Lead, JSR 362 Portlet Specification 3.0
IBM Commerce, Digital Experience Development
IBM Deutschland Research & Development GmbH / Vorsitzender des
Aufsichtsrats: Martina Koederitz / Geschäftsführung: Dirk Wittkopp
Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart,
HRB 243294
From: David S Taylor <da...@bluesunrise.com>
To: pluto-dev@portals.apache.org
Date: 09.11.2016 16:59
Subject: Re: build errors
Well, I pulled the master branch clean, same problem. Running Java
java version "1.7.0_60"
Java(TM) SE Runtime Environment (build 1.7.0_60-b19)
Java HotSpot(TM) 64-Bit Server VM (build 24.60-b09, mixed mode)
Seems that one of my methods in the AnnotatedMethodStore is not initialized
correctly, it points to:
class org.apache.pluto.container.reconcile.fixtures.IncompletePortlet
and not the expected Portlet4
"Portlet name='Portlet4', Method type='INIT', Dispatch ID=''" -> " size =
1"
> On Nov 9, 2016, at 6:55 AM, Neil Griffin <ne...@portletfaces.org>
wrote:
>
> Hi David,
>
> The Liferay Faces team performing builds of Pluto, but we're not seeing
the error you mentioned below.
>
> Best Regards,
>
> Neil
>
>> On Nov 8, 2016, at 10:49 AM, DavidSeanTaylor <da...@bluesunrise.com>
wrote:
>>
>> Im seeing these errors with my latest pull today. I ran ‘mvn clean
install’
>> anyone else seeing the errors below?
>>
>> Running org.apache.pluto.container.util.ArgumentUtilityTest
>> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002
sec - in org.apache.pluto.container.util.ArgumentUtilityTest
>>
>> Results :
>>
>> Failed tests:
>> PortletInvokeTest.test4destroy:266 null
>> PortletInvokeTest.test4init:259 null
>> PortletInvokeTest.test4resource:306 null
>> PortletInvokeTest.test4action:274 null
>> PortletInvokeTest.test4event1:282 null
>> PortletInvokeTest.test4event2:290 null
>> PortletInvokeTest.test4render:298 null
>>
>> Tests run: 1003, Failures: 7, Errors: 0, Skipped: 0
>>
>> [INFO]
------------------------------------------------------------------------
>> [INFO] Reactor Summary:
>> [INFO]
>> [INFO] Apache Pluto ....................................... SUCCESS
[ 1.669 s]
>> [INFO] Java Portlet API V3.0 .............................. SUCCESS
[ 19.451 s]
>> [INFO] Apache Pluto Container API ......................... SUCCESS
[ 0.695 s]
>> [INFO] Apache Pluto Portlet Container ..................... FAILURE
[ 18.080 s]
>
Re: build errors
Posted by David S Taylor <da...@bluesunrise.com>.
Well, I pulled the master branch clean, same problem. Running Java
java version "1.7.0_60"
Java(TM) SE Runtime Environment (build 1.7.0_60-b19)
Java HotSpot(TM) 64-Bit Server VM (build 24.60-b09, mixed mode)
Seems that one of my methods in the AnnotatedMethodStore is not initialized correctly, it points to:
class org.apache.pluto.container.reconcile.fixtures.IncompletePortlet
and not the expected Portlet4
"Portlet name='Portlet4', Method type='INIT', Dispatch ID=''" -> " size = 1"
> On Nov 9, 2016, at 6:55 AM, Neil Griffin <ne...@portletfaces.org> wrote:
>
> Hi David,
>
> The Liferay Faces team performing builds of Pluto, but we're not seeing the error you mentioned below.
>
> Best Regards,
>
> Neil
>
>> On Nov 8, 2016, at 10:49 AM, DavidSeanTaylor <da...@bluesunrise.com> wrote:
>>
>> Im seeing these errors with my latest pull today. I ran ‘mvn clean install’
>> anyone else seeing the errors below?
>>
>> Running org.apache.pluto.container.util.ArgumentUtilityTest
>> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec - in org.apache.pluto.container.util.ArgumentUtilityTest
>>
>> Results :
>>
>> Failed tests:
>> PortletInvokeTest.test4destroy:266 null
>> PortletInvokeTest.test4init:259 null
>> PortletInvokeTest.test4resource:306 null
>> PortletInvokeTest.test4action:274 null
>> PortletInvokeTest.test4event1:282 null
>> PortletInvokeTest.test4event2:290 null
>> PortletInvokeTest.test4render:298 null
>>
>> Tests run: 1003, Failures: 7, Errors: 0, Skipped: 0
>>
>> [INFO] ------------------------------------------------------------------------
>> [INFO] Reactor Summary:
>> [INFO]
>> [INFO] Apache Pluto ....................................... SUCCESS [ 1.669 s]
>> [INFO] Java Portlet API V3.0 .............................. SUCCESS [ 19.451 s]
>> [INFO] Apache Pluto Container API ......................... SUCCESS [ 0.695 s]
>> [INFO] Apache Pluto Portlet Container ..................... FAILURE [ 18.080 s]
>
Re: build errors
Posted by Werner Keil <we...@gmail.com>.
I currently don't have these Jenkins roles AFAIK;-/
If someone could grant or request them for my user (wkeil) I'd appreciate
and happy to help with that.
Otherwise somebody who does would have to fix it.
Werner
On Wed, Nov 9, 2016 at 4:37 PM, David S Taylor <da...@bluesunrise.com>
wrote:
> Seems its setup to pull out of Subversion, not Git.
>
> Happy to help if I had the necessary Jenkins credentials (I know not many
> committers get them;-|)
>
>
> Sure, go for it.
>
> On Nov 9, 2016, at 7:00 AM, Werner Keil <we...@gmail.com> wrote:
>
> Is there an official CI build of Pluto on Apache Jenkins?
>
> I found several including https://builds.apache.org/job/
> portals-pluto-trunk/ but none of them were built since ~May 2015, so they
> cannot be using the most recent codebase.
> Is it possible to fix that on apache.org, too?
>
> Happy to help if I had the necessary Jenkins credentials (I know not many
> committers get them;-|)
>
> Regards,
> Werner
>
>
> On Wed, Nov 9, 2016 at 3:55 PM, Neil Griffin <
> neil.griffin@portletfaces.org> wrote:
>
>> Hi David,
>>
>> The Liferay Faces team performing builds of Pluto, but we're not seeing
>> the error you mentioned below.
>>
>> Best Regards,
>>
>> Neil
>>
>> > On Nov 8, 2016, at 10:49 AM, DavidSeanTaylor <da...@bluesunrise.com>
>> wrote:
>> >
>> > Im seeing these errors with my latest pull today. I ran ‘mvn clean
>> install’
>> > anyone else seeing the errors below?
>> >
>> > Running org.apache.pluto.container.util.ArgumentUtilityTest
>> > Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002
>> sec - in org.apache.pluto.container.util.ArgumentUtilityTest
>> >
>> > Results :
>> >
>> > Failed tests:
>> > PortletInvokeTest.test4destroy:266 null
>> > PortletInvokeTest.test4init:259 null
>> > PortletInvokeTest.test4resource:306 null
>> > PortletInvokeTest.test4action:274 null
>> > PortletInvokeTest.test4event1:282 null
>> > PortletInvokeTest.test4event2:290 null
>> > PortletInvokeTest.test4render:298 null
>> >
>> > Tests run: 1003, Failures: 7, Errors: 0, Skipped: 0
>> >
>> > [INFO] ------------------------------------------------------------
>> ------------
>> > [INFO] Reactor Summary:
>> > [INFO]
>> > [INFO] Apache Pluto ....................................... SUCCESS [
>> 1.669 s]
>> > [INFO] Java Portlet API V3.0 .............................. SUCCESS [
>> 19.451 s]
>> > [INFO] Apache Pluto Container API ......................... SUCCESS [
>> 0.695 s]
>> > [INFO] Apache Pluto Portlet Container ..................... FAILURE [
>> 18.080 s]
>>
>>
>
>
Re: build errors
Posted by David S Taylor <da...@bluesunrise.com>.
Seems its setup to pull out of Subversion, not Git.
> Happy to help if I had the necessary Jenkins credentials (I know not many committers get them;-|)
Sure, go for it.
> On Nov 9, 2016, at 7:00 AM, Werner Keil <we...@gmail.com> wrote:
>
> Is there an official CI build of Pluto on Apache Jenkins?
>
> I found several including https://builds.apache.org/job/portals-pluto-trunk/ <https://builds.apache.org/job/portals-pluto-trunk/> but none of them were built since ~May 2015, so they cannot be using the most recent codebase.
> Is it possible to fix that on apache.org <http://apache.org/>, too?
>
> Happy to help if I had the necessary Jenkins credentials (I know not many committers get them;-|)
>
> Regards,
> Werner
>
>
> On Wed, Nov 9, 2016 at 3:55 PM, Neil Griffin <neil.griffin@portletfaces.org <ma...@portletfaces.org>> wrote:
> Hi David,
>
> The Liferay Faces team performing builds of Pluto, but we're not seeing the error you mentioned below.
>
> Best Regards,
>
> Neil
>
> > On Nov 8, 2016, at 10:49 AM, DavidSeanTaylor <david@bluesunrise.com <ma...@bluesunrise.com>> wrote:
> >
> > Im seeing these errors with my latest pull today. I ran ‘mvn clean install’
> > anyone else seeing the errors below?
> >
> > Running org.apache.pluto.container.util.ArgumentUtilityTest
> > Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec - in org.apache.pluto.container.util.ArgumentUtilityTest
> >
> > Results :
> >
> > Failed tests:
> > PortletInvokeTest.test4destroy:266 null
> > PortletInvokeTest.test4init:259 null
> > PortletInvokeTest.test4resource:306 null
> > PortletInvokeTest.test4action:274 null
> > PortletInvokeTest.test4event1:282 null
> > PortletInvokeTest.test4event2:290 null
> > PortletInvokeTest.test4render:298 null
> >
> > Tests run: 1003, Failures: 7, Errors: 0, Skipped: 0
> >
> > [INFO] ------------------------------------------------------------------------
> > [INFO] Reactor Summary:
> > [INFO]
> > [INFO] Apache Pluto ....................................... SUCCESS [ 1.669 s]
> > [INFO] Java Portlet API V3.0 .............................. SUCCESS [ 19.451 s]
> > [INFO] Apache Pluto Container API ......................... SUCCESS [ 0.695 s]
> > [INFO] Apache Pluto Portlet Container ..................... FAILURE [ 18.080 s]
>
>
Re: build errors
Posted by Werner Keil <we...@gmail.com>.
Is there an official CI build of Pluto on Apache Jenkins?
I found several including https://builds.apache.org/job/portals-pluto-trunk/
but none of them were built since ~May 2015, so they cannot be using the
most recent codebase.
Is it possible to fix that on apache.org, too?
Happy to help if I had the necessary Jenkins credentials (I know not many
committers get them;-|)
Regards,
Werner
On Wed, Nov 9, 2016 at 3:55 PM, Neil Griffin <ne...@portletfaces.org>
wrote:
> Hi David,
>
> The Liferay Faces team performing builds of Pluto, but we're not seeing
> the error you mentioned below.
>
> Best Regards,
>
> Neil
>
> > On Nov 8, 2016, at 10:49 AM, DavidSeanTaylor <da...@bluesunrise.com>
> wrote:
> >
> > Im seeing these errors with my latest pull today. I ran ‘mvn clean
> install’
> > anyone else seeing the errors below?
> >
> > Running org.apache.pluto.container.util.ArgumentUtilityTest
> > Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002
> sec - in org.apache.pluto.container.util.ArgumentUtilityTest
> >
> > Results :
> >
> > Failed tests:
> > PortletInvokeTest.test4destroy:266 null
> > PortletInvokeTest.test4init:259 null
> > PortletInvokeTest.test4resource:306 null
> > PortletInvokeTest.test4action:274 null
> > PortletInvokeTest.test4event1:282 null
> > PortletInvokeTest.test4event2:290 null
> > PortletInvokeTest.test4render:298 null
> >
> > Tests run: 1003, Failures: 7, Errors: 0, Skipped: 0
> >
> > [INFO] ------------------------------------------------------------
> ------------
> > [INFO] Reactor Summary:
> > [INFO]
> > [INFO] Apache Pluto ....................................... SUCCESS [
> 1.669 s]
> > [INFO] Java Portlet API V3.0 .............................. SUCCESS [
> 19.451 s]
> > [INFO] Apache Pluto Container API ......................... SUCCESS [
> 0.695 s]
> > [INFO] Apache Pluto Portlet Container ..................... FAILURE [
> 18.080 s]
>
>
Re: build errors
Posted by Neil Griffin <ne...@portletfaces.org>.
Hi David,
The Liferay Faces team performing builds of Pluto, but we're not seeing the error you mentioned below.
Best Regards,
Neil
> On Nov 8, 2016, at 10:49 AM, DavidSeanTaylor <da...@bluesunrise.com> wrote:
>
> Im seeing these errors with my latest pull today. I ran ‘mvn clean install’
> anyone else seeing the errors below?
>
> Running org.apache.pluto.container.util.ArgumentUtilityTest
> Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec - in org.apache.pluto.container.util.ArgumentUtilityTest
>
> Results :
>
> Failed tests:
> PortletInvokeTest.test4destroy:266 null
> PortletInvokeTest.test4init:259 null
> PortletInvokeTest.test4resource:306 null
> PortletInvokeTest.test4action:274 null
> PortletInvokeTest.test4event1:282 null
> PortletInvokeTest.test4event2:290 null
> PortletInvokeTest.test4render:298 null
>
> Tests run: 1003, Failures: 7, Errors: 0, Skipped: 0
>
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Pluto ....................................... SUCCESS [ 1.669 s]
> [INFO] Java Portlet API V3.0 .............................. SUCCESS [ 19.451 s]
> [INFO] Apache Pluto Container API ......................... SUCCESS [ 0.695 s]
> [INFO] Apache Pluto Portlet Container ..................... FAILURE [ 18.080 s]