Re: FYI - Gump will be moving to Java 22 EA shortly

[Mark Thomas]

Hi all,

It took a little longer than I expected to do this. I've just switched 
vmgump to Java 22. The first run should start in ~4.5 hours.


Mark


On 24/10/2023 12:32, Mark Thomas wrote:

Hi all,

Tomcat now needs Java 22 to build the development branch so I'll be 
moving Gump to use Java 22 once it is available in the ASF package 
repository. I anticipate this move happening in the next week or so.


Mark


-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org



-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

FYI - Gump will be moving to Java 22 EA shortly

[Mark Thomas]

Hi all,

Tomcat now needs Java 22 to build the development branch so I'll be 
moving Gump to use Java 22 once it is available in the ASF package 
repository. I anticipate this move happening in the next week or so.


Mark


-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: Cron cd /srv/gump/public/gump/cron; /bin/bash gump.sh all

[Mark Thomas]

On 19/05/2023 13:00, Cron Daemon wrote:

The lock file [/srv/gump/public/gump/gump.lock] exists, and is locked..
Either Gump is still running, or it terminated very abnormally.
Please resolve this (waiting or removing the lock file) before retrying.


Looks like Tomcat test failures causing a longer run. Should be resolved 
once the Tomcat issues are fixed.


Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: Gump build switched to Java 21

[Mark Thomas]

On 11/05/2023 16:57, Stefan Bodewig wrote:

On 2023-05-10, Mark Thomas wrote:


Tomcat 11 is about to move to requiring Java 21 so I have just
switched Gump to building with the latest Java 21 EA. I am expecting
things to break and for it to take a couple of days for me to get
everything fixed.



Fingers crossed...


Thank you and good luck


... and I'm done.

We now have 3 modules that will fail regularly. The two new ones joining 
test-ant are test-junit and antunit-test. Both appear to have issues 
with a small number of tests under Java 21.


I did think about skipping those tests but I opted to leave things as 
they are.


Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Gump build switched to Java 21

[Mark Thomas]

Hi all,

Tomcat 11 is about to move to requiring Java 21 so I have just switched 
Gump to building with the latest Java 21 EA. I am expecting things to 
break and for it to take a couple of days for me to get everything fixed.


Fingers crossed...

Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Maven bumped from 3.6.2 to 3.6.3

[Mark Thomas]

Hi all,

A number (all?) of Commons projects now require Maven 3.6.3 as a minimum 
so I bumped the Maven version to 3.6.3. I thought about taking it to the 
latest 3.x release but opted for the minimal change at this point.


If this goes well, I may move Gump to Maven 3.9.1 next week.

Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: Direction of Gump

[Mark Thomas]

On 19/02/2023 11:56, Stefan Bodewig wrote:

Hi all

after Gump's last board report one of the members asked whether we
aren't disturbed by not adding any new committers for many years now
(actually I don't believe anybody who is a not a PMC member already has
posted anything to ths list for years).

>

And whether Gump really mostly is on life-support for the benefit of
Tomcat. Given that the only person who has done anything for a long time
has been Mark and he has done so for the benefit of Tomcat, this may be
a proper description of where we are.


I think it is a shame many of the projects have moved away from Gump 
over the years. But we are where we are.


Tomcat continues to get some benefit from Gump although it is mostly 
early warning of changes to default cipher suites in OpenSSL and we 
haven't have that many of those changes over the last few years.


I think it is fair to say only Tomcat is benefiting from Gump now.


TBH I don't see Gump adding new projects anymore


Agreed.


and my personal
involvement has been reduced to writing more or less the same report
every quarter - mainly checking it still accurately describes the
situation.

I'm not suggesting terminating Gump but I wonder whether there is any
benefit in keeping it as a TLP if no other project is interested
anymore.


What are the other options if it isn't a TLP? Close it down obviously. 
Anything else?


Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: Moving to Java 17

[Mark Thomas]

Looks to be back to where we were before the Java 17 update.

Mark


On 19/01/2023 09:38, Mark Thomas wrote:
Quick update, I just switched Gump over. Should start to see the impact 
with the 12.00 UTC run in ~2.5 hours time.


Mark


On 12/01/2023 07:27, Stefan Bodewig wrote:

On 2023-01-11, Mark Thomas wrote:


Once I have confirmed Java 17 has been installed, I'll switch Gump
over to Java 17 and wait to see what fails. Once everything is fixed,
I'll remove the Java 11 package.


+1

Thank you

Stefan

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org



-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org



-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: Moving to Java 17

[Mark Thomas]

Quick update, I just switched Gump over. Should start to see the impact 
with the 12.00 UTC run in ~2.5 hours time.


Mark


On 12/01/2023 07:27, Stefan Bodewig wrote:

On 2023-01-11, Mark Thomas wrote:


Once I have confirmed Java 17 has been installed, I'll switch Gump
over to Java 17 and wait to see what fails. Once everything is fixed,
I'll remove the Java 11 package.


+1

Thank you

Stefan

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org



-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Moving to Java 17

[Mark Thomas]

Hi all,

Tomcat is about to move the main development branch to Java 17. So Gump 
can continue to build Tomcat, I intend to move Gump to Java 17.


I have added Java 17 to the packages installed by Puppet (and removed 
Java 8 since we have been using Java 11 for a while now).


Once I have confirmed Java 17 has been installed, I'll switch Gump over 
to Java 17 and wait to see what fails. Once everything is fixed, I'll 
remove the Java 11 package.


Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: Problem running Apache Gump [vmgump]

[Mark Thomas]

On 11/11/2021 08:16, Mark Thomas wrote:
This will be the changes I made yesterday to add JaCoCo which it looks 
like I messed up. I'll take a look now.


Should be fixed now. Running an official run as the one at midnight failed.

Mark


On 11/11/2021 02:36, g...@gump-vm2.apache.org wrote:
There is a problem with run 'vmgump' (2021_01), location : 
http://gump-vm2.apache.org/


The log ought be at:
    http://gump-vm2.apache.org/gump_log.txt

The last (up to) 50 lines of the log are :
Document run using [XDocDocumenter]
Traceback (most recent call last):
   File "bin/integrate.py", line 114, in 
 irun()
   File "bin/integrate.py", line 91, in irun
 result = getRunner(run).perform()
   File "/srv/gump/public/gump/python/gump/core/runner/runner.py", 
line 260, in perform

 return self.performRun()
   File "/srv/gump/public/gump/python/gump/core/runner/demand.py", 
line 214, in performRun

 self.finalize()
   File "/srv/gump/public/gump/python/gump/core/runner/runner.py", 
line 240, in finalize

 self.run._dispatchEvent(FinalizeRunEvent(self.run))
   File "/srv/gump/public/gump/python/gump/core/run/gumprun.py", line 
186, in _dispatchEvent

 actor._processEvent(event)
   File "/srv/gump/public/gump/python/gump/core/run/actor.py", line 
83, in _processEvent

 self.processEvent(event)
   File "/srv/gump/public/gump/python/gump/core/run/actor.py", line 
127, in processEvent

 self._processOtherEvent(event)
   File "/srv/gump/public/gump/python/gump/core/run/actor.py", line 
184, in _processOtherEvent

 self.processOtherEvent(event)
   File 
"/srv/gump/public/gump/python/gump/actor/document/documenter.py", line 
48, in processOtherEvent

 self.document()
   File 
"/srv/gump/public/gump/python/gump/actor/document/documenter.py", line 
72, in document

 self.documentRun()
   File 
"/srv/gump/public/gump/python/gump/actor/document/xdocs/documenter.py", line 
97, in documentRun

 self.documentEverythingElse()
   File 
"/srv/gump/public/gump/python/gump/actor/document/xdocs/documenter.py", line 
481, in documentEverythingElse

 self.documentModule(module)
   File 
"/srv/gump/public/gump/python/gump/actor/document/xdocs/documenter.py", line 
1843, in documentModule

 self.documentProject(project)
   File 
"/srv/gump/public/gump/python/gump/actor/document/xdocs/documenter.py", line 
1991, in documentProject

 self.documentProjectDetails(project, realTime)
   File 
"/srv/gump/public/gump/python/gump/actor/document/xdocs/documenter.py", line 
2083, in documentProjectDetails

 depens += self.documentDependenciesList(dependencySection,
   File 
"/srv/gump/public/gump/python/gump/actor/document/xdocs/documenter.py", line 
2293, in documentDependenciesList

 self.insertLink(project, referencingObject,
   File 
"/srv/gump/public/gump/python/gump/actor/document/xdocs/documenter.py", line 
3045, in insertLink

 link = self.getLink(toObject, fromObject, state)
   File 
"/srv/gump/public/gump/python/gump/actor/document/xdocs/documenter.py", line 
3085, in getLink

 url = getRelativeLocation(toObject, fromObject,
   File 
"/srv/gump/public/gump/python/gump/actor/document/xdocs/resolver.py", 
line 109, in getRelativeLocation

 toLocation=getLocationForObject(toObject,extn)
   File 
"/srv/gump/public/gump/python/gump/actor/document/xdocs/resolver.py", 
line 127, in getLocationForObject

 getPathForObject(object),
   File 
"/srv/gump/public/gump/python/gump/actor/document/xdocs/resolver.py", 
line 83, in getPathForObject
 
path=getPathForObject(object.getModule()).getPostfixed(object.getName())
   File "/srv/gump/public/gump/python/gump/core/model/project.py", 
line 856, in getModule

 raise RuntimeError('Project [' + self.name + '] not in a module.]')
RuntimeError: Project [jacoco] not in a module.]
Process Exit Code : 1
--
Gump Version: 2.0.2-alpha-0003

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org




-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org




-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: Problem running Apache Gump [vmgump]

[Mark Thomas]

This will be the changes I made yesterday to add JaCoCo which it looks 
like I meessed up. I'll take a look now.


Mark


On 11/11/2021 02:36, g...@gump-vm2.apache.org wrote:

There is a problem with run 'vmgump' (2021_01), location : 
http://gump-vm2.apache.org/

The log ought be at:
http://gump-vm2.apache.org/gump_log.txt

The last (up to) 50 lines of the log are :
Document run using [XDocDocumenter]
Traceback (most recent call last):
   File "bin/integrate.py", line 114, in 
 irun()
   File "bin/integrate.py", line 91, in irun
 result = getRunner(run).perform()
   File "/srv/gump/public/gump/python/gump/core/runner/runner.py", line 260, in 
perform
 return self.performRun()
   File "/srv/gump/public/gump/python/gump/core/runner/demand.py", line 214, in 
performRun
 self.finalize()
   File "/srv/gump/public/gump/python/gump/core/runner/runner.py", line 240, in 
finalize
 self.run._dispatchEvent(FinalizeRunEvent(self.run))
   File "/srv/gump/public/gump/python/gump/core/run/gumprun.py", line 186, in 
_dispatchEvent
 actor._processEvent(event)
   File "/srv/gump/public/gump/python/gump/core/run/actor.py", line 83, in 
_processEvent
 self.processEvent(event)
   File "/srv/gump/public/gump/python/gump/core/run/actor.py", line 127, in 
processEvent
 self._processOtherEvent(event)
   File "/srv/gump/public/gump/python/gump/core/run/actor.py", line 184, in 
_processOtherEvent
 self.processOtherEvent(event)
   File "/srv/gump/public/gump/python/gump/actor/document/documenter.py", line 
48, in processOtherEvent
 self.document()
   File "/srv/gump/public/gump/python/gump/actor/document/documenter.py", line 
72, in document
 self.documentRun()
   File "/srv/gump/public/gump/python/gump/actor/document/xdocs/documenter.py", 
line 97, in documentRun
 self.documentEverythingElse()
   File "/srv/gump/public/gump/python/gump/actor/document/xdocs/documenter.py", 
line 481, in documentEverythingElse
 self.documentModule(module)
   File "/srv/gump/public/gump/python/gump/actor/document/xdocs/documenter.py", 
line 1843, in documentModule
 self.documentProject(project)
   File "/srv/gump/public/gump/python/gump/actor/document/xdocs/documenter.py", 
line 1991, in documentProject
 self.documentProjectDetails(project, realTime)
   File "/srv/gump/public/gump/python/gump/actor/document/xdocs/documenter.py", 
line 2083, in documentProjectDetails
 depens += self.documentDependenciesList(dependencySection,
   File "/srv/gump/public/gump/python/gump/actor/document/xdocs/documenter.py", 
line 2293, in documentDependenciesList
 self.insertLink(project, referencingObject,
   File "/srv/gump/public/gump/python/gump/actor/document/xdocs/documenter.py", 
line 3045, in insertLink
 link = self.getLink(toObject, fromObject, state)
   File "/srv/gump/public/gump/python/gump/actor/document/xdocs/documenter.py", 
line 3085, in getLink
 url = getRelativeLocation(toObject, fromObject,
   File "/srv/gump/public/gump/python/gump/actor/document/xdocs/resolver.py", 
line 109, in getRelativeLocation
 toLocation=getLocationForObject(toObject,extn)
   File "/srv/gump/public/gump/python/gump/actor/document/xdocs/resolver.py", 
line 127, in getLocationForObject
 getPathForObject(object),
   File "/srv/gump/public/gump/python/gump/actor/document/xdocs/resolver.py", 
line 83, in getPathForObject
 path=getPathForObject(object.getModule()).getPostfixed(object.getName())
   File "/srv/gump/public/gump/python/gump/core/model/project.py", line 856, in 
getModule
 raise RuntimeError('Project [' + self.name + '] not in a module.]')
RuntimeError: Project [jacoco] not in a module.]
Process Exit Code : 1
--
Gump Version: 2.0.2-alpha-0003

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org




-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: Starting to move Gump to using Java 11

[Mark Thomas]

On 20/08/2021 17:53, Mark Thomas wrote:

On 20/08/2021 09:06, Stefan Bodewig wrote:





I've already added the jar and changed the descriptors. Unfortunately I
did so before realizing that my ssh key is unknown to the current vmgump
and so I've not been able to update the working copy of packages.


Tx. I've just done the update. I'll look into your ssh access as well.


With some off-list co-ordination this has been fixed.

Thanks again for your help in getting the update to building with Java 
11 completed.


The last run was completely successful which is great.

We are seeing intermittent failures for some Tomcat tests (the tests 
themselves aren't completely reliable and looking at those is on my TODO 
list).


The apache-httpd-make job is failing intermittently as well. I think it 
is something to do with openssl creating .../dest-20210823/lib64 rather 
than .../dest-20210823/lib

I'm not sure what triggered this or how to fix it.

Finally, looking at projects that have no dependees, I see ant-contrib 
and xalan-pom. Can these be removed?


Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: Starting to move Gump to using Java 11

[Mark Thomas]

On 20/08/2021 09:06, Stefan Bodewig wrote:

On 2021-08-19, Mark Thomas wrote:


On 19/08/2021 17:53, Stefan Bodewig wrote:



Tomcat transitvely inherits antlr4*.jar but this jar doesn't seem to
contain the "runtime" package. I believe you also want
https://mvnrepository.com/artifact/org.antlr/antlr4-runtime and make
that a runtime dependency of checkstyle (not that I knew much about
antlr).



Ack. Thanks for the hint. I'm just finishing up some changes in the
latest Tomcat and then I should have some time for this.


I've already added the jar and changed the descriptors. Unfortunately I
did so before realizing that my ssh key is unknown to the current vmgump
and so I've not been able to update the working copy of packages.


Tx. I've just done the update. I'll look into your ssh access as well.

Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: Starting to move Gump to using Java 11

[Mark Thomas]

On 19/08/2021 17:53, Stefan Bodewig wrote:

On 2021-08-19, Mark Thomas wrote:


Many thanks for cleaning up the mess I created.


You didn't create a mess here, you just uncovered an undetected bug.

The -bootclasspath/p problems of xml-apis and xml-resolver are probably
not really fixable. We cannot create a "patch module" easily, I'm
afraid. I think we can remove xml-apis completely and build xml-resolver
without any boot-type dependencies. We are no longer interested in
building Xerces or Xalan against a JAXP version other than the one of
the JDK anyway.


+1

I had similar thoughts about removing xml-apis.


It looks like Checkstyle may still have an issue and then I'll have
some genuine Tomcat issues to fix.


Tomcat transitvely inherits antlr4*.jar but this jar doesn't seem to
contain the "runtime" package. I believe you also want
https://mvnrepository.com/artifact/org.antlr/antlr4-runtime and make
that a runtime dependency of checkstyle (not that I knew much about
antlr).


Ack. Thanks for the hint. I'm just finishing up some changes in the 
latest Tomcat and then I should have some time for this.


Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: Starting to move Gump to using Java 11

[Mark Thomas]

On 19/08/2021 13:39, Stefan Bodewig wrote:

On 2021-08-19, Stefan Bodewig wrote:


It looks as if you may have uncovered a bug in Ant's build,


no, the Gump descriptor has been broken before.

While compiling the tests Ant didn't see the main classes it had just
compiled. It could only see those of the bootstrap-ant project.

The only explanation of why it has worked before I have is that
bootstrap-ant has contained the classes that depend on jakarta-regexp
before and now no longer does. And as Xalan contains the regex classes
(I think the build has used the "unbundled" Xalan jar which does not
contain regexp because of this, may be wrong) the classes and tests
would be compiled now.

Anyway, the "ant" project has just been built successfully. Let's see
what breaks next.


Many thanks for cleaning up the mess I created. Things are looking a lot 
better now.


It looks like Checkstyle may still have an issue and then I'll have some 
genuine Tomcat issues to fix.


Cheers,

Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: Starting to move Gump to using Java 11

[Mark Thomas]

It looks like I have broken the Ant build somehow. I can't see what I 
have done wrong. No rush, but some help on this from someone more 
familiar with the Ant build than I would be helpful.


Mark


On 12/08/2021 10:57, Mark Thomas wrote:



On 12/08/2021 10:46, Stefan Bodewig wrote:

Many thank for doing this, Mark

On 2021-08-10, Mark Thomas wrote:


Is there a way in Gump to get just some projects to build with a
different JAVA_HOME? Switching just the Tomcat 10.1.x builds to Java
11 is the minimum requirement. We can then take a harder look at the
dependency chains and see what we can do to update versions / trim
things down.


I think it should be possible to allow JAVA_HOME to be overridden on a
project by project basis but I doubt anybody is less rusty WRT Gump's
Python code base than Adam :-)

If the short term solution is to make some Tomcat builds use a different
version of Java then we'd only need to modify the Ant builder. This one
uses self.run.getEnvironment().getJavaCommand() which is what JAVA_HOME
points at. We could add a "java_home" property or something similar to
the model for  (BaseAnt) and calculate the Java command inside of
the Ant builder if this attribute is set. Making a configurable
JAVA_HOME work for Gradle and Maven as well would require a bit more of
work.

I can try to carve out some time for this next week, but I'm afraid you
want a solution more quickly.


Thanks for the offer. Things have moved on a bit and I think we are OK 
running with Java 11 everywhere. There are still a few things to clean 
up but it looks doable at this point.


I'm going to chip away at the remaining issues as I get the time. As 
always, help welcome. I'm expecting this is going to take a few more 
weeks to sort out. I think there are also some genuine failures in the 
Tomcat test runs so Java 11 may not be responsible for all the current 
issues.


Cheers,

Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org



-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: Starting to move Gump to using Java 11

[Mark Thomas]

On 12/08/2021 10:46, Stefan Bodewig wrote:

Many thank for doing this, Mark

On 2021-08-10, Mark Thomas wrote:


Is there a way in Gump to get just some projects to build with a
different JAVA_HOME? Switching just the Tomcat 10.1.x builds to Java
11 is the minimum requirement. We can then take a harder look at the
dependency chains and see what we can do to update versions / trim
things down.


I think it should be possible to allow JAVA_HOME to be overridden on a
project by project basis but I doubt anybody is less rusty WRT Gump's
Python code base than Adam :-)

If the short term solution is to make some Tomcat builds use a different
version of Java then we'd only need to modify the Ant builder. This one
uses self.run.getEnvironment().getJavaCommand() which is what JAVA_HOME
points at. We could add a "java_home" property or something similar to
the model for  (BaseAnt) and calculate the Java command inside of
the Ant builder if this attribute is set. Making a configurable
JAVA_HOME work for Gradle and Maven as well would require a bit more of
work.

I can try to carve out some time for this next week, but I'm afraid you
want a solution more quickly.


Thanks for the offer. Things have moved on a bit and I think we are OK 
running with Java 11 everywhere. There are still a few things to clean 
up but it looks doable at this point.


I'm going to chip away at the remaining issues as I get the time. As 
always, help welcome. I'm expecting this is going to take a few more 
weeks to sort out. I think there are also some genuine failures in the 
Tomcat test runs so Java 11 may not be responsible for all the current 
issues.


Cheers,

Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: Starting to move Gump to using Java 11

[Mark Thomas]

On 11/08/2021 10:46, Mark Thomas wrote:

On 11/08/2021 09:06, Adam Jack wrote:
I am traveling home from abroad right now but I can look into things 
when I
get settled back. That said, I am sure others are far less rusty than 
me on

this. That said, from my rusty/simplistic perspective:

Would the best case be that the whole stack be built with one
compiler/language version, the newest supported, so we uncover any build
issues and then mail them to teams? Would that be helpful to getting 
those
build issues resolved, or are such notifications going unanswered? 
Meaning
do we change the Java version and then wait, rather than work around 
things?


Sorry if that is missing something obvious (I haven’t touched Java in 
well

over a decade.)


Thanks. Additional eyes on this would be good.

I agree that in an ideal world, everything would build with the latest 
version of Java. Switching from Java 8 to Java 11 was a step in that 
direction.


The complicating factor is that the chain of dependencies leads back to 
(branches of) projects that are no longer maintained and don't build 
with Java >8. In some cases, updating the dependencies to newer branches 
is an option. I managed to remove Commons Lang 2.x from the dependency 
chain that way. However, there are some dependency chains where that 
does not appear to be an option. Maybe the right answer is that we 
should just provide JARs for such projects rather than trying to build 
them.


Also, there are potentially some dependencies where we aren't building 
from source and perhaps should be such as the Eclipse JDT JAR.


Given that Tomcat is the only project really using Gump right now, I 
think I am going to start there and work backwards checking dependencies 
as I suspect some of those may be rather out of date. It might be that 
the problem will turn out to be a lot simpler than it appears, once the 
dependencies are tidied up.


Packaging log4j 1.2.x and removing a number of the old XML dependencies 
has improved things quite a bit. I think there has been sufficient 
progress to continue running with Java 11 and fix the remaining issues 
as they arise.


As part of the clean-up / simplification I am currently planning on 
pruning various optional dependencies unless the Tomcat builds require 
them. Please speak up if there are any objections to doing this.


Mark


-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: Starting to move Gump to using Java 11

[Mark Thomas]

On 11/08/2021 09:06, Adam Jack wrote:

I am traveling home from abroad right now but I can look into things when I
get settled back. That said, I am sure others are far less rusty than me on
this. That said, from my rusty/simplistic perspective:

Would the best case be that the whole stack be built with one
compiler/language version, the newest supported, so we uncover any build
issues and then mail them to teams? Would that be helpful to getting those
build issues resolved, or are such notifications going unanswered? Meaning
do we change the Java version and then wait, rather than work around things?

Sorry if that is missing something obvious (I haven’t touched Java in well
over a decade.)


Thanks. Additional eyes on this would be good.

I agree that in an ideal world, everything would build with the latest 
version of Java. Switching from Java 8 to Java 11 was a step in that 
direction.


The complicating factor is that the chain of dependencies leads back to 
(branches of) projects that are no longer maintained and don't build 
with Java >8. In some cases, updating the dependencies to newer branches 
is an option. I managed to remove Commons Lang 2.x from the dependency 
chain that way. However, there are some dependency chains where that 
does not appear to be an option. Maybe the right answer is that we 
should just provide JARs for such projects rather than trying to build them.


Also, there are potentially some dependencies where we aren't building 
from source and perhaps should be such as the Eclipse JDT JAR.


Given that Tomcat is the only project really using Gump right now, I 
think I am going to start there and work backwards checking dependencies 
as I suspect some of those may be rather out of date. It might be that 
the problem will turn out to be a lot simpler than it appears, once the 
dependencies are tidied up.


Mark



Regards,

Adam

On Tue, Aug 10, 2021 at 11:15 PM Mark Thomas  wrote:


On 10/08/2021 21:38, Mark Thomas wrote:

On 10/08/2021 21:17, Adam Jack wrote:

Thanks for the update. Good luck.


Thanks. I think I am going to need it. This is going to be *far* from
simple.

There is lots of code currently being built by Gump that needs changes
to build with Java 9+.

You will have seen I started to try and hack around the issues with
Commons Lang 2.4 (it was using source=1.4) but forcing source to 1.6
(the minimum Java 11 supports) just creates a different problem - the
source using "enum" as an identifier but it is a reserved word from Java
5 onwards.

I don't see a simple or quick solution for this.

Is there a way in Gump to get just some projects to build with a
different JAVA_HOME? Switching just the Tomcat 10.1.x builds to Java 11
is the minimum requirement. We can then take a harder look at the
dependency chains and see what we can do to update versions / trim
things down.


On the topic of dependency chains, log4j 1.2.x is currently blocking
progress.

I need to set the source and target to 1.6 (local testing on vmgump
suggests this will then work) but I don't know how to do that.

I see "POM overrides" in a few places But I can't figure out how to use
them. Is there a way to copy the log4j POM, store it somewhere in Gump
and then tweak it (essentially change "1.4" to "1.6")?

Mark




Mark





Adam

On Tue, Aug 10, 2021, 15:57 Mark Thomas  wrote:


All,

Since Tomcat's main development branch now requires Java 11, I have
started the process of moving Gump over to Java 11.

So far, I have added Java 11 to the packages installed by Puppet.

I want to confirm that Java 11 has been installed, then I'll switch
JAVA_HOME to point to Java 11 rather than Java 8. In theory that should
'just work'. When it doesn't (optimistic soul that I am), we'll have to
see what fails and figure out the best way to deal with each issue.

Once everything is running smoothly on Java 11, then I'll remove Java

8.


Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org






-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org



-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

--

Sent from Mobile



-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: Starting to move Gump to using Java 11

[Mark Thomas]

On 10/08/2021 21:38, Mark Thomas wrote:

On 10/08/2021 21:17, Adam Jack wrote:

Thanks for the update. Good luck.


Thanks. I think I am going to need it. This is going to be *far* from 
simple.


There is lots of code currently being built by Gump that needs changes 
to build with Java 9+.


You will have seen I started to try and hack around the issues with 
Commons Lang 2.4 (it was using source=1.4) but forcing source to 1.6 
(the minimum Java 11 supports) just creates a different problem - the 
source using "enum" as an identifier but it is a reserved word from Java 
5 onwards.


I don't see a simple or quick solution for this.

Is there a way in Gump to get just some projects to build with a 
different JAVA_HOME? Switching just the Tomcat 10.1.x builds to Java 11 
is the minimum requirement. We can then take a harder look at the 
dependency chains and see what we can do to update versions / trim 
things down.


On the topic of dependency chains, log4j 1.2.x is currently blocking 
progress.


I need to set the source and target to 1.6 (local testing on vmgump 
suggests this will then work) but I don't know how to do that.


I see "POM overrides" in a few places But I can't figure out how to use 
them. Is there a way to copy the log4j POM, store it somewhere in Gump 
and then tweak it (essentially change "1.4" to "1.6")?


Mark




Mark





Adam

On Tue, Aug 10, 2021, 15:57 Mark Thomas  wrote:


All,

Since Tomcat's main development branch now requires Java 11, I have
started the process of moving Gump over to Java 11.

So far, I have added Java 11 to the packages installed by Puppet.

I want to confirm that Java 11 has been installed, then I'll switch
JAVA_HOME to point to Java 11 rather than Java 8. In theory that should
'just work'. When it doesn't (optimistic soul that I am), we'll have to
see what fails and figure out the best way to deal with each issue.

Once everything is running smoothly on Java 11, then I'll remove Java 8.

Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org






-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org



-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Starting to move Gump to using Java 11

[Mark Thomas]

All,

Since Tomcat's main development branch now requires Java 11, I have 
started the process of moving Gump over to Java 11.


So far, I have added Java 11 to the packages installed by Puppet.

I want to confirm that Java 11 has been installed, then I'll switch 
JAVA_HOME to point to Java 11 rather than Java 8. In theory that should 
'just work'. When it doesn't (optimistic soul that I am), we'll have to 
see what fails and figure out the best way to deal with each issue.


Once everything is running smoothly on Java 11, then I'll remove Java 8.

Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: Problem running Apache Gump [vmgump]

[Mark Thomas]

On 26/04/2021 18:10, g...@gump-vm2.apache.org wrote:

There is a problem with run 'vmgump' (26042021_180001), location : 
http://gump-vm2.apache.org/


Looks like a temporary problem with network access. Subsequent runs look 
to be OK.


Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: Cron cd /srv/gump/public/gump/cron; /bin/bash gump.sh all --official

[Mark Thomas]

On 02/12/2020 00:00, Cron Daemon wrote:
> The lock file [/srv/gump/public/gump/gump.lock] exists, and is locked.. 
> Either Gump is still running, or it terminated very abnormally.
> Please resolve this (waiting or removing the lock file) before retrying.

This is expected. I started a manual run at 21:27 UTC that hadn't completed.

I've just confirmed that the 06.00 UTC cron job started correctly so, as
far as I can tell, the migration to the new VM is complete.

Huge thanks to Adam Jack who did the hard work for this.

Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: Gump, Ubuntu 20.04 and python

[Mark Thomas]

On 30/11/2020 21:50, Adam Jack wrote:
> Hey Mark,
> 
> I found the current svn merge approach is:
> 
>$ svn merge ^/branches/my-branch
> 
> So I ended up checking out 'live' and doing:
> 
>$ svn merge ^/gump/branches/python3
> 
> which looked promising so I commit. Fingers crossed we are now back live on
> python3.

Thanks. I've re-enabled Puppet which switched the VM back to the live
branch. I've triggered a manual run to check all is well. If that works,
I'll ask infra to re-enable the cron jobs and complete the DNS
switch-over etc.

> P.S. I also managed to SSH into gump-vm2.

Glad that worked. Once you set-up OPIE you should be able to use sudo:
https://cwiki.apache.org/confluence/display/INFRA/OPIE

Kind regards,

Mark


> 
> regards,
> 
> Adam
> 
> On Mon, Nov 30, 2020 at 8:01 AM Mark Thomas  wrote:
> 
>> Woot!
>>
>> The last run only had a single failure (test-ant) and that has been
>> failing for months.
>>
>> I think we are good to merge the changes in the branch back into live.
>>
>> Adam, if you can get that done, I'll get gump-vm2 moved back over to
>> live, re-enable Puppet and then get infra to re-enable the cron jobs.
>>
>> Almost there...
>>
>> Mark
>>
>>
>> On 30/11/2020 08:41, Mark Thomas wrote:
>>> On 29/11/2020 22:04, Adam Jack wrote:
>>>> Hey Mark
>>>>
>>>> It transpires that there was an "isinstance(self.value, NoneType)" that
>> got
>>>> converted to an "self.value is *not* None" reversing the intent. Fixed
>> and
>>>> commit to SVN (python3 branch) after a unit test added.
>>>
>>> Thanks. I've just started a new run. All green so far.
>>>
>>> /me waits a little while
>>>
>>> Ah. We have failures but those are genuine build failures rather than a
>>> python2 vs python3 error. (Commons Logging has some issues). Looking
>> good.
>>>
>>> What do you think about merging the changes back into gump/live vs
>>> continuing with the branch?
>>>
>>> Mark
>>>
>>>
>>>>
>>>> regards
>>>>
>>>> Adam
>>>>
>>>> On Sun, Nov 29, 2020 at 11:36 AM Mark Thomas  wrote:
>>>>
>>>>> Hi Adam,
>>>>>
>>>>> The current run started at Sun, 29 Nov 2020 18:19:38 (UTC). Details at:
>>>>> http://gump-vm2.apache.org/buildLog.html
>>>>>
>>>>> This failure looks like one you'll be able to fix much faster than me:
>>>>>
>>>>>
>> http://gump-vm2.apache.org/apr/apr-configure/gump_work/build_apr_apr-configure.html
>>>>>
>>>>> Mark
>>>>>
>>>>> On 29/11/2020 18:03, Mark Thomas wrote:
>>>>>> On 29/11/2020 15:18, Adam Jack wrote:
>>>>>>> Thanks for testing it out Mark.
>>>>>>>
>>>>>>> If you need help taking it from here, let me know, and if I can gain
>>>>> access
>>>>>>> to the VM I'll help out.
>>>>>>>
>>>>>>> [ I am away (social distancing at a family cabin) and if I have any
>>>>> access
>>>>>>> keys they'll be on some old machines that I don't have easy access
>> to. ]
>>>>>>
>>>>>> I think we are almost there. A proper run started which is further
>> than
>>>>>> it got before but gump then failed during the run (looks to be most of
>>>>>> the way through).
>>>>>>
>>>>>> I suspect there are only a handful of fixes to go but run, fail, fix
>>>>>> repeat will quickly get time consuming as the run part (when it is
>>>>>> working) takes between 8 and 12 hours. Having two of us able to check
>> on
>>>>>> it, fix the latest issue and start the next run will be a big help.
>>>>>>
>>>>>> Once everything is working we can merge the change back into trunk,
>>>>>> update the Puppet config, restart Puppet and we should be good to go.
>>>>>>
>>>>>> With that in mind, the first step to getting you access to the VM is
>>>>>> that you need to add an ssh key via id.apache.org.
>>>>>>
>>>>>> I should then be able to get you access to the machine. With access to
>>>>>> the machine you can do the OPIE/ortpasswd dance so you can use sudo.
>>>

Re: Gump, Ubuntu 20.04 and python

[Mark Thomas]

Woot!

The last run only had a single failure (test-ant) and that has been
failing for months.

I think we are good to merge the changes in the branch back into live.

Adam, if you can get that done, I'll get gump-vm2 moved back over to
live, re-enable Puppet and then get infra to re-enable the cron jobs.

Almost there...

Mark


On 30/11/2020 08:41, Mark Thomas wrote:
> On 29/11/2020 22:04, Adam Jack wrote:
>> Hey Mark
>>
>> It transpires that there was an "isinstance(self.value, NoneType)" that got
>> converted to an "self.value is *not* None" reversing the intent. Fixed and
>> commit to SVN (python3 branch) after a unit test added.
> 
> Thanks. I've just started a new run. All green so far.
> 
> /me waits a little while
> 
> Ah. We have failures but those are genuine build failures rather than a
> python2 vs python3 error. (Commons Logging has some issues). Looking good.
> 
> What do you think about merging the changes back into gump/live vs
> continuing with the branch?
> 
> Mark
> 
> 
>>
>> regards
>>
>> Adam
>>
>> On Sun, Nov 29, 2020 at 11:36 AM Mark Thomas  wrote:
>>
>>> Hi Adam,
>>>
>>> The current run started at Sun, 29 Nov 2020 18:19:38 (UTC). Details at:
>>> http://gump-vm2.apache.org/buildLog.html
>>>
>>> This failure looks like one you'll be able to fix much faster than me:
>>>
>>> http://gump-vm2.apache.org/apr/apr-configure/gump_work/build_apr_apr-configure.html
>>>
>>> Mark
>>>
>>> On 29/11/2020 18:03, Mark Thomas wrote:
>>>> On 29/11/2020 15:18, Adam Jack wrote:
>>>>> Thanks for testing it out Mark.
>>>>>
>>>>> If you need help taking it from here, let me know, and if I can gain
>>> access
>>>>> to the VM I'll help out.
>>>>>
>>>>> [ I am away (social distancing at a family cabin) and if I have any
>>> access
>>>>> keys they'll be on some old machines that I don't have easy access to. ]
>>>>
>>>> I think we are almost there. A proper run started which is further than
>>>> it got before but gump then failed during the run (looks to be most of
>>>> the way through).
>>>>
>>>> I suspect there are only a handful of fixes to go but run, fail, fix
>>>> repeat will quickly get time consuming as the run part (when it is
>>>> working) takes between 8 and 12 hours. Having two of us able to check on
>>>> it, fix the latest issue and start the next run will be a big help.
>>>>
>>>> Once everything is working we can merge the change back into trunk,
>>>> update the Puppet config, restart Puppet and we should be good to go.
>>>>
>>>> With that in mind, the first step to getting you access to the VM is
>>>> that you need to add an ssh key via id.apache.org.
>>>>
>>>> I should then be able to get you access to the machine. With access to
>>>> the machine you can do the OPIE/ortpasswd dance so you can use sudo.
>>>>
>>>> I'm just fixing the errors I can see in preparation for the next run.
>>>>
>>>> Thanks,
>>>>
>>>> Mark
>>>>
>>>>
>>>>>
>>>>> regards,
>>>>>
>>>>> Adam
>>>>>
>>>>> On Sun, Nov 29, 2020 at 2:31 AM Mark Thomas  wrote:
>>>>>
>>>>>> On 29/11/2020 01:18, Adam Jack wrote:
>>>>>>> Hey Mark,
>>>>>>>
>>>>>>> I've taken a shot (on a Macbook) at porting Gump to Python 3. I used
>>>>>> "2to3"
>>>>>>> a bunch, but then manually worked on updates continually running
>>> Gump's
>>>>>>> unit test. I don't know how complete the coverage of those tests is,
>>> but
>>>>>>> hopefully it is a start. (I couldn't seem to install 'anydbm' on my
>>> mac,
>>>>>> so
>>>>>>> I mocked it and commented it out, for now.)
>>>>>>>
>>>>>>>   Gump
>>>>>>> Performed [102] tests with [0] issues.
>>>>>>> No Problems Detected
>>>>>>>
>>>>>>> I commit to a branch:
>>>>>>>
>>>>>>>https://svn.apache.org/repos/asf/gump/branches/python3/
>>>>>>>
>>>>>>&

Re: Gump, Ubuntu 20.04 and python

[Mark Thomas]

On 29/11/2020 22:04, Adam Jack wrote:
> Hey Mark
> 
> It transpires that there was an "isinstance(self.value, NoneType)" that got
> converted to an "self.value is *not* None" reversing the intent. Fixed and
> commit to SVN (python3 branch) after a unit test added.

Thanks. I've just started a new run. All green so far.

/me waits a little while

Ah. We have failures but those are genuine build failures rather than a
python2 vs python3 error. (Commons Logging has some issues). Looking good.

What do you think about merging the changes back into gump/live vs
continuing with the branch?

Mark


> 
> regards
> 
> Adam
> 
> On Sun, Nov 29, 2020 at 11:36 AM Mark Thomas  wrote:
> 
>> Hi Adam,
>>
>> The current run started at Sun, 29 Nov 2020 18:19:38 (UTC). Details at:
>> http://gump-vm2.apache.org/buildLog.html
>>
>> This failure looks like one you'll be able to fix much faster than me:
>>
>> http://gump-vm2.apache.org/apr/apr-configure/gump_work/build_apr_apr-configure.html
>>
>> Mark
>>
>> On 29/11/2020 18:03, Mark Thomas wrote:
>>> On 29/11/2020 15:18, Adam Jack wrote:
>>>> Thanks for testing it out Mark.
>>>>
>>>> If you need help taking it from here, let me know, and if I can gain
>> access
>>>> to the VM I'll help out.
>>>>
>>>> [ I am away (social distancing at a family cabin) and if I have any
>> access
>>>> keys they'll be on some old machines that I don't have easy access to. ]
>>>
>>> I think we are almost there. A proper run started which is further than
>>> it got before but gump then failed during the run (looks to be most of
>>> the way through).
>>>
>>> I suspect there are only a handful of fixes to go but run, fail, fix
>>> repeat will quickly get time consuming as the run part (when it is
>>> working) takes between 8 and 12 hours. Having two of us able to check on
>>> it, fix the latest issue and start the next run will be a big help.
>>>
>>> Once everything is working we can merge the change back into trunk,
>>> update the Puppet config, restart Puppet and we should be good to go.
>>>
>>> With that in mind, the first step to getting you access to the VM is
>>> that you need to add an ssh key via id.apache.org.
>>>
>>> I should then be able to get you access to the machine. With access to
>>> the machine you can do the OPIE/ortpasswd dance so you can use sudo.
>>>
>>> I'm just fixing the errors I can see in preparation for the next run.
>>>
>>> Thanks,
>>>
>>> Mark
>>>
>>>
>>>>
>>>> regards,
>>>>
>>>> Adam
>>>>
>>>> On Sun, Nov 29, 2020 at 2:31 AM Mark Thomas  wrote:
>>>>
>>>>> On 29/11/2020 01:18, Adam Jack wrote:
>>>>>> Hey Mark,
>>>>>>
>>>>>> I've taken a shot (on a Macbook) at porting Gump to Python 3. I used
>>>>> "2to3"
>>>>>> a bunch, but then manually worked on updates continually running
>> Gump's
>>>>>> unit test. I don't know how complete the coverage of those tests is,
>> but
>>>>>> hopefully it is a start. (I couldn't seem to install 'anydbm' on my
>> mac,
>>>>> so
>>>>>> I mocked it and commented it out, for now.)
>>>>>>
>>>>>>   Gump
>>>>>> Performed [102] tests with [0] issues.
>>>>>> No Problems Detected
>>>>>>
>>>>>> I commit to a branch:
>>>>>>
>>>>>>https://svn.apache.org/repos/asf/gump/branches/python3/
>>>>>>
>>>>>> I'm not sure how I access the VM to try the full Gump run. Let me
>> know if
>>>>>> there is anything more I can do to complete the migration.
>>>>>
>>>>> Hi Adam,
>>>>>
>>>>> Thanks - this is great. I'll test on the VM and let you know.
>>>>>
>>>>> Mark
>>>>>
>>>>>>
>>>>>> regards,
>>>>>>
>>>>>> Adam
>>>>>>
>>>>>> On Fri, Nov 27, 2020 at 12:29 PM Mark Thomas 
>> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> Ubuntu 20.04 comes with python3. You can make python2 work but it

Re: Gump, Ubuntu 20.04 and python

[Mark Thomas]

On 29/11/2020 20:39, Adam Jack wrote:
> Yup, that is pretty much what I've copied into mine. Do I need to share it
> with you, or does me copying it into "id" field write it to the correct
> authorized_keys files?
> 
> Two thoughts:
> 
> - I didn't pass any parameters to ssh_keygen, should I have done so? I
> didn't restart anything (and don't think I should, being merely the client,
> but maybe mac needs something.)
> - Reading, I don't think SSH access is allowed to home.a.o ... do I (ajack)
> need to be allowed to vmgump2? Is that the problem?

Correct. home.a.o only allows sftp.

I'll need to add you to gump-vm2.a.o - I'll do that shortly.

Mark


> 
> regards,
> 
> Adam
> 
> On Sun, Nov 29, 2020 at 1:06 PM Mark Thomas  wrote:
> 
>> On 29/11/2020 18:50, Adam Jack wrote:
>>> Thanks Mark,
>>>
>>> I'll continue to kick off the dust/rust and investigate that. I might not
>>> be faster, but am happy to share the load, and it is a good way for me to
>>> get back into it. I'll see if I can figure out a unit test for that
>>> problem first, then fix it.
>>
>> Sounds good. Much better than my "Google the error message, try
>> something, repeat until it works approach".
>>
>>> P.S. I've made progress with id.apache.org but am getting rejected for
>> the
>>> keys I've generated. I'll keep trying.
>>
>> If it helps, mine looks like this (on a single line):
>>
>> ssh-rsa
>>
>> B3NzaC1yc2EBJQAAAQBfNKvNGpqrS80JUbbNOGZxnbIbCMdAJN3rVl3gLXtNhdPDX087vObq2O7RF/7EChUONhlZG6bMw1CQovBgWmR1a2mTxJn2+2ixSz0YeAeV+q+8G9WV21MAOpFTYZ7hPI26V3anM5BD+J8sQggtgqLD+Jl8nXpsaEYfOLHRtmPrMQ0gHTzpmSunJlJzHgsZRRt/2w2T42ZKUkydCc7gHMHYLfnl8/3Mb4GaHYUqd9JnpkiIpNKuFDRr7YfH0RyBRYTE494wd55V8+3BDqfWbrCZXtbLJ+4PWm/9ECYuwEVe9UXRceNaq0kOKK7ZGXUoHK+3Xl7OJZ/M0w3Y7p5RqJvb
>> Mark Thomas 20170112
>>
>> Cheers,
>>
>> Mark
>>
>>
>>>
>>> regards,
>>>
>>> Adam
>>>
>>> On Sun, Nov 29, 2020 at 11:36 AM Mark Thomas  wrote:
>>>
>>>> Hi Adam,
>>>>
>>>> The current run started at Sun, 29 Nov 2020 18:19:38 (UTC). Details at:
>>>> http://gump-vm2.apache.org/buildLog.html
>>>>
>>>> This failure looks like one you'll be able to fix much faster than me:
>>>>
>>>>
>> http://gump-vm2.apache.org/apr/apr-configure/gump_work/build_apr_apr-configure.html
>>>>
>>>> Mark
>>>>
>>>> On 29/11/2020 18:03, Mark Thomas wrote:
>>>>> On 29/11/2020 15:18, Adam Jack wrote:
>>>>>> Thanks for testing it out Mark.
>>>>>>
>>>>>> If you need help taking it from here, let me know, and if I can gain
>>>> access
>>>>>> to the VM I'll help out.
>>>>>>
>>>>>> [ I am away (social distancing at a family cabin) and if I have any
>>>> access
>>>>>> keys they'll be on some old machines that I don't have easy access
>> to. ]
>>>>>
>>>>> I think we are almost there. A proper run started which is further than
>>>>> it got before but gump then failed during the run (looks to be most of
>>>>> the way through).
>>>>>
>>>>> I suspect there are only a handful of fixes to go but run, fail, fix
>>>>> repeat will quickly get time consuming as the run part (when it is
>>>>> working) takes between 8 and 12 hours. Having two of us able to check
>> on
>>>>> it, fix the latest issue and start the next run will be a big help.
>>>>>
>>>>> Once everything is working we can merge the change back into trunk,
>>>>> update the Puppet config, restart Puppet and we should be good to go.
>>>>>
>>>>> With that in mind, the first step to getting you access to the VM is
>>>>> that you need to add an ssh key via id.apache.org.
>>>>>
>>>>> I should then be able to get you access to the machine. With access to
>>>>> the machine you can do the OPIE/ortpasswd dance so you can use sudo.
>>>>>
>>>>> I'm just fixing the errors I can see in preparation for the next run.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Mark
>>>>>
>>>>>
>>>>>>
>>>>>> regards,
>>>>>>
>>>>>> Adam
>>>>>>
>>>>>> On Sun, Nov 29, 2020

Re: Gump, Ubuntu 20.04 and python

[Mark Thomas]

On 29/11/2020 18:50, Adam Jack wrote:
> Thanks Mark,
> 
> I'll continue to kick off the dust/rust and investigate that. I might not
> be faster, but am happy to share the load, and it is a good way for me to
> get back into it. I'll see if I can figure out a unit test for that
> problem first, then fix it.

Sounds good. Much better than my "Google the error message, try
something, repeat until it works approach".

> P.S. I've made progress with id.apache.org but am getting rejected for the
> keys I've generated. I'll keep trying.

If it helps, mine looks like this (on a single line):

ssh-rsa
B3NzaC1yc2EBJQAAAQBfNKvNGpqrS80JUbbNOGZxnbIbCMdAJN3rVl3gLXtNhdPDX087vObq2O7RF/7EChUONhlZG6bMw1CQovBgWmR1a2mTxJn2+2ixSz0YeAeV+q+8G9WV21MAOpFTYZ7hPI26V3anM5BD+J8sQggtgqLD+Jl8nXpsaEYfOLHRtmPrMQ0gHTzpmSunJlJzHgsZRRt/2w2T42ZKUkydCc7gHMHYLfnl8/3Mb4GaHYUqd9JnpkiIpNKuFDRr7YfH0RyBRYTE494wd55V8+3BDqfWbrCZXtbLJ+4PWm/9ECYuwEVe9UXRceNaq0kOKK7ZGXUoHK+3Xl7OJZ/M0w3Y7p5RqJvb
Mark Thomas 20170112

Cheers,

Mark


> 
> regards,
> 
> Adam
> 
> On Sun, Nov 29, 2020 at 11:36 AM Mark Thomas  wrote:
> 
>> Hi Adam,
>>
>> The current run started at Sun, 29 Nov 2020 18:19:38 (UTC). Details at:
>> http://gump-vm2.apache.org/buildLog.html
>>
>> This failure looks like one you'll be able to fix much faster than me:
>>
>> http://gump-vm2.apache.org/apr/apr-configure/gump_work/build_apr_apr-configure.html
>>
>> Mark
>>
>> On 29/11/2020 18:03, Mark Thomas wrote:
>>> On 29/11/2020 15:18, Adam Jack wrote:
>>>> Thanks for testing it out Mark.
>>>>
>>>> If you need help taking it from here, let me know, and if I can gain
>> access
>>>> to the VM I'll help out.
>>>>
>>>> [ I am away (social distancing at a family cabin) and if I have any
>> access
>>>> keys they'll be on some old machines that I don't have easy access to. ]
>>>
>>> I think we are almost there. A proper run started which is further than
>>> it got before but gump then failed during the run (looks to be most of
>>> the way through).
>>>
>>> I suspect there are only a handful of fixes to go but run, fail, fix
>>> repeat will quickly get time consuming as the run part (when it is
>>> working) takes between 8 and 12 hours. Having two of us able to check on
>>> it, fix the latest issue and start the next run will be a big help.
>>>
>>> Once everything is working we can merge the change back into trunk,
>>> update the Puppet config, restart Puppet and we should be good to go.
>>>
>>> With that in mind, the first step to getting you access to the VM is
>>> that you need to add an ssh key via id.apache.org.
>>>
>>> I should then be able to get you access to the machine. With access to
>>> the machine you can do the OPIE/ortpasswd dance so you can use sudo.
>>>
>>> I'm just fixing the errors I can see in preparation for the next run.
>>>
>>> Thanks,
>>>
>>> Mark
>>>
>>>
>>>>
>>>> regards,
>>>>
>>>> Adam
>>>>
>>>> On Sun, Nov 29, 2020 at 2:31 AM Mark Thomas  wrote:
>>>>
>>>>> On 29/11/2020 01:18, Adam Jack wrote:
>>>>>> Hey Mark,
>>>>>>
>>>>>> I've taken a shot (on a Macbook) at porting Gump to Python 3. I used
>>>>> "2to3"
>>>>>> a bunch, but then manually worked on updates continually running
>> Gump's
>>>>>> unit test. I don't know how complete the coverage of those tests is,
>> but
>>>>>> hopefully it is a start. (I couldn't seem to install 'anydbm' on my
>> mac,
>>>>> so
>>>>>> I mocked it and commented it out, for now.)
>>>>>>
>>>>>>   Gump
>>>>>> Performed [102] tests with [0] issues.
>>>>>> No Problems Detected
>>>>>>
>>>>>> I commit to a branch:
>>>>>>
>>>>>>https://svn.apache.org/repos/asf/gump/branches/python3/
>>>>>>
>>>>>> I'm not sure how I access the VM to try the full Gump run. Let me
>> know if
>>>>>> there is anything more I can do to complete the migration.
>>>>>
>>>>> Hi Adam,
>>>>>
>>>>> Thanks - this is great. I'll test on the VM and let you know.
>>>>>
>>>>> Mark
>>>>>

Re: Gump, Ubuntu 20.04 and python

[Mark Thomas]

Hi Adam,

The current run started at Sun, 29 Nov 2020 18:19:38 (UTC). Details at:
http://gump-vm2.apache.org/buildLog.html

This failure looks like one you'll be able to fix much faster than me:
http://gump-vm2.apache.org/apr/apr-configure/gump_work/build_apr_apr-configure.html

Mark

On 29/11/2020 18:03, Mark Thomas wrote:
> On 29/11/2020 15:18, Adam Jack wrote:
>> Thanks for testing it out Mark.
>>
>> If you need help taking it from here, let me know, and if I can gain access
>> to the VM I'll help out.
>>
>> [ I am away (social distancing at a family cabin) and if I have any access
>> keys they'll be on some old machines that I don't have easy access to. ]
> 
> I think we are almost there. A proper run started which is further than
> it got before but gump then failed during the run (looks to be most of
> the way through).
> 
> I suspect there are only a handful of fixes to go but run, fail, fix
> repeat will quickly get time consuming as the run part (when it is
> working) takes between 8 and 12 hours. Having two of us able to check on
> it, fix the latest issue and start the next run will be a big help.
> 
> Once everything is working we can merge the change back into trunk,
> update the Puppet config, restart Puppet and we should be good to go.
> 
> With that in mind, the first step to getting you access to the VM is
> that you need to add an ssh key via id.apache.org.
> 
> I should then be able to get you access to the machine. With access to
> the machine you can do the OPIE/ortpasswd dance so you can use sudo.
> 
> I'm just fixing the errors I can see in preparation for the next run.
> 
> Thanks,
> 
> Mark
> 
> 
>>
>> regards,
>>
>> Adam
>>
>> On Sun, Nov 29, 2020 at 2:31 AM Mark Thomas  wrote:
>>
>>> On 29/11/2020 01:18, Adam Jack wrote:
>>>> Hey Mark,
>>>>
>>>> I've taken a shot (on a Macbook) at porting Gump to Python 3. I used
>>> "2to3"
>>>> a bunch, but then manually worked on updates continually running Gump's
>>>> unit test. I don't know how complete the coverage of those tests is, but
>>>> hopefully it is a start. (I couldn't seem to install 'anydbm' on my mac,
>>> so
>>>> I mocked it and commented it out, for now.)
>>>>
>>>>   Gump
>>>> Performed [102] tests with [0] issues.
>>>> No Problems Detected
>>>>
>>>> I commit to a branch:
>>>>
>>>>https://svn.apache.org/repos/asf/gump/branches/python3/
>>>>
>>>> I'm not sure how I access the VM to try the full Gump run. Let me know if
>>>> there is anything more I can do to complete the migration.
>>>
>>> Hi Adam,
>>>
>>> Thanks - this is great. I'll test on the VM and let you know.
>>>
>>> Mark
>>>
>>>>
>>>> regards,
>>>>
>>>> Adam
>>>>
>>>> On Fri, Nov 27, 2020 at 12:29 PM Mark Thomas  wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Ubuntu 20.04 comes with python3. You can make python2 work but it
>>>>> involves jumping through some hoops.
>>>>>
>>>>> Gump doesn't work with python 3. I've spent a couple of hours trying to
>>>>> fix this (patch on gump-vm2 in /home/markt) and I have reached the end
>>>>> of my (very) limited python skills.
>>>>>
>>>>> So, we have a choice. Python 2 or Python 3?
>>>>>
>>>>> Python 3 will need someone else to get Gump working on gump-vm2.
>>>>>
>>>>> Python 2 I can handle but I may take a few shortcuts and not put
>>>>> everything in Puppet on the basis we rebuild the server so infrequently
>>>>> that it is less effort to rebuild python 2 support manually than get it
>>>>> into Puppet.
>>>>>
>>>>> Or there is the other option - send Gump to the attic.
>>>>>
>>>>> Gump has been useful in the past in identifying issues other CI systems
>>>>> did not. Gump provides the Tomcat project with earlier sight of OpenSSL
>>>>> integration issues we don't get any other way. Gump going to the attic
>>>>> would be a loss to the Tomcat project but it would be a relatively small
>>>>> loss.
>>>>>
>>>>> If someone has the time and skills to get Gump onto Python 3 now then
>>>>> I'd support that. If not, my vote is for ge

Re: Gump, Ubuntu 20.04 and python

[Mark Thomas]

On 29/11/2020 15:18, Adam Jack wrote:
> Thanks for testing it out Mark.
> 
> If you need help taking it from here, let me know, and if I can gain access
> to the VM I'll help out.
> 
> [ I am away (social distancing at a family cabin) and if I have any access
> keys they'll be on some old machines that I don't have easy access to. ]

I think we are almost there. A proper run started which is further than
it got before but gump then failed during the run (looks to be most of
the way through).

I suspect there are only a handful of fixes to go but run, fail, fix
repeat will quickly get time consuming as the run part (when it is
working) takes between 8 and 12 hours. Having two of us able to check on
it, fix the latest issue and start the next run will be a big help.

Once everything is working we can merge the change back into trunk,
update the Puppet config, restart Puppet and we should be good to go.

With that in mind, the first step to getting you access to the VM is
that you need to add an ssh key via id.apache.org.

I should then be able to get you access to the machine. With access to
the machine you can do the OPIE/ortpasswd dance so you can use sudo.

I'm just fixing the errors I can see in preparation for the next run.

Thanks,

Mark


> 
> regards,
> 
> Adam
> 
> On Sun, Nov 29, 2020 at 2:31 AM Mark Thomas  wrote:
> 
>> On 29/11/2020 01:18, Adam Jack wrote:
>>> Hey Mark,
>>>
>>> I've taken a shot (on a Macbook) at porting Gump to Python 3. I used
>> "2to3"
>>> a bunch, but then manually worked on updates continually running Gump's
>>> unit test. I don't know how complete the coverage of those tests is, but
>>> hopefully it is a start. (I couldn't seem to install 'anydbm' on my mac,
>> so
>>> I mocked it and commented it out, for now.)
>>>
>>>   Gump
>>> Performed [102] tests with [0] issues.
>>> No Problems Detected
>>>
>>> I commit to a branch:
>>>
>>>https://svn.apache.org/repos/asf/gump/branches/python3/
>>>
>>> I'm not sure how I access the VM to try the full Gump run. Let me know if
>>> there is anything more I can do to complete the migration.
>>
>> Hi Adam,
>>
>> Thanks - this is great. I'll test on the VM and let you know.
>>
>> Mark
>>
>>>
>>> regards,
>>>
>>> Adam
>>>
>>> On Fri, Nov 27, 2020 at 12:29 PM Mark Thomas  wrote:
>>>
>>>> Hi,
>>>>
>>>> Ubuntu 20.04 comes with python3. You can make python2 work but it
>>>> involves jumping through some hoops.
>>>>
>>>> Gump doesn't work with python 3. I've spent a couple of hours trying to
>>>> fix this (patch on gump-vm2 in /home/markt) and I have reached the end
>>>> of my (very) limited python skills.
>>>>
>>>> So, we have a choice. Python 2 or Python 3?
>>>>
>>>> Python 3 will need someone else to get Gump working on gump-vm2.
>>>>
>>>> Python 2 I can handle but I may take a few shortcuts and not put
>>>> everything in Puppet on the basis we rebuild the server so infrequently
>>>> that it is less effort to rebuild python 2 support manually than get it
>>>> into Puppet.
>>>>
>>>> Or there is the other option - send Gump to the attic.
>>>>
>>>> Gump has been useful in the past in identifying issues other CI systems
>>>> did not. Gump provides the Tomcat project with earlier sight of OpenSSL
>>>> integration issues we don't get any other way. Gump going to the attic
>>>> would be a loss to the Tomcat project but it would be a relatively small
>>>> loss.
>>>>
>>>> If someone has the time and skills to get Gump onto Python 3 now then
>>>> I'd support that. If not, my vote is for getting python2 running in the
>>>> short term and hope someone can look at python3 support in the medium to
>>>> long term.
>>>>
>>>> Thoughts?
>>>>
>>>> Mark
>>>>
>>>> -
>>>> To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
>>>> For additional commands, e-mail: general-h...@gump.apache.org
>>>>
>>>>
>>>
>>
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
>> For additional commands, e-mail: general-h...@gump.apache.org
>>
>>
> 


-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: Gump, Ubuntu 20.04 and python

[Mark Thomas]

On 29/11/2020 01:18, Adam Jack wrote:
> Hey Mark,
> 
> I've taken a shot (on a Macbook) at porting Gump to Python 3. I used "2to3"
> a bunch, but then manually worked on updates continually running Gump's
> unit test. I don't know how complete the coverage of those tests is, but
> hopefully it is a start. (I couldn't seem to install 'anydbm' on my mac, so
> I mocked it and commented it out, for now.)
> 
>   Gump
> Performed [102] tests with [0] issues.
> No Problems Detected
> 
> I commit to a branch:
> 
>https://svn.apache.org/repos/asf/gump/branches/python3/
> 
> I'm not sure how I access the VM to try the full Gump run. Let me know if
> there is anything more I can do to complete the migration.

Hi Adam,

Thanks - this is great. I'll test on the VM and let you know.

Mark

> 
> regards,
> 
> Adam
> 
> On Fri, Nov 27, 2020 at 12:29 PM Mark Thomas  wrote:
> 
>> Hi,
>>
>> Ubuntu 20.04 comes with python3. You can make python2 work but it
>> involves jumping through some hoops.
>>
>> Gump doesn't work with python 3. I've spent a couple of hours trying to
>> fix this (patch on gump-vm2 in /home/markt) and I have reached the end
>> of my (very) limited python skills.
>>
>> So, we have a choice. Python 2 or Python 3?
>>
>> Python 3 will need someone else to get Gump working on gump-vm2.
>>
>> Python 2 I can handle but I may take a few shortcuts and not put
>> everything in Puppet on the basis we rebuild the server so infrequently
>> that it is less effort to rebuild python 2 support manually than get it
>> into Puppet.
>>
>> Or there is the other option - send Gump to the attic.
>>
>> Gump has been useful in the past in identifying issues other CI systems
>> did not. Gump provides the Tomcat project with earlier sight of OpenSSL
>> integration issues we don't get any other way. Gump going to the attic
>> would be a loss to the Tomcat project but it would be a relatively small
>> loss.
>>
>> If someone has the time and skills to get Gump onto Python 3 now then
>> I'd support that. If not, my vote is for getting python2 running in the
>> short term and hope someone can look at python3 support in the medium to
>> long term.
>>
>> Thoughts?
>>
>> Mark
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
>> For additional commands, e-mail: general-h...@gump.apache.org
>>
>>
> 


-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Gump, Ubuntu 20.04 and python

[Mark Thomas]

Hi,

Ubuntu 20.04 comes with python3. You can make python2 work but it
involves jumping through some hoops.

Gump doesn't work with python 3. I've spent a couple of hours trying to
fix this (patch on gump-vm2 in /home/markt) and I have reached the end
of my (very) limited python skills.

So, we have a choice. Python 2 or Python 3?

Python 3 will need someone else to get Gump working on gump-vm2.

Python 2 I can handle but I may take a few shortcuts and not put
everything in Puppet on the basis we rebuild the server so infrequently
that it is less effort to rebuild python 2 support manually than get it
into Puppet.

Or there is the other option - send Gump to the attic.

Gump has been useful in the past in identifying issues other CI systems
did not. Gump provides the Tomcat project with earlier sight of OpenSSL
integration issues we don't get any other way. Gump going to the attic
would be a loss to the Tomcat project but it would be a relatively small
loss.

If someone has the time and skills to get Gump onto Python 3 now then
I'd support that. If not, my vote is for getting python2 running in the
short term and hope someone can look at python3 support in the medium to
long term.

Thoughts?

Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: Board Report

[Mark Thomas]

On 09/06/2020 11:07, Stefan Bodewig wrote:
> Hi all
> 
> the board report is due tomorrow. From my POV Mark has been fixing
> things and nothing really changed. Gump works and the Tomcat community -
> i.e. Mark - makes sure it remains useful for them.

+1. Gump continues to provide value to the Tomcat project.

> This report I intend to make this a bit more explicit in the report. It
> looks as if we do have three PMC people who respond to emails but I'm
> not sure whether this rule really makes sense in a project that never
> cuts releases :-)
> 
> Back in March we seemed to agree that as long as the board isn't unhappy
> we can continue as we have done over the past years.

I think that is the simplest option.

If the board does have objections at some point then we can address them
we they are raised.

> Konstantin raised the about documentation being outdated and missing and
> Gump being difficult to approach for a newcomer, which is probably true,
> but nobody (including myself, of course) seems to find enough energy to
> change that.

Maybe for now just add a prominent note somewhere that says:
- we know there is work to do in this area
- ask on the list if anyone has a query
- we'll update the docs based on those queries and answers

Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: svn commit: r1878298 - /gump/metadata/project/jsch.xml

[Mark Thomas]

On 30/05/2020 00:34, ma...@apache.org wrote:
> Author: markt
> Date: Fri May 29 23:34:14 2020
> New Revision: 1878298
> 
> URL: http://svn.apache.org/viewvc?rev=1878298=rev
> Log:
> Update jsch to 0.1.55

This might just fix the failing ant-dist build...

...assuming I haven't forgotten a version update somewhere, which, based
on past experience, is almost certain. jsch is only used by ant-dist so
if I have got it wrong it won't break anything that isn't already broken
and I'll (try and) fix it in ~12 hours after the next run.

Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: Problem running Apache Gump [vmgump]

[Mark Thomas]

On 06/05/2020 09:48, g...@gump-vm.apache.org wrote:
> There is a problem with run 'vmgump' (06052020_01), location : 
> http://gump-vm.apache.org/
> 
> The log ought be at:
>http://gump-vm.apache.org/gump_log.txt
> 
> The last (up to) 50 lines of the log are :
> SQL Error on [INSERT INTO gump_public.gump_repository_stats (repository_name, 
> sequence_in_state) VALUES ('pcre', 195)] : (1292, "Incorrect datetime value: 
> '-00-00 00:00:00' for column 'first' at row 1")

The sql_mode has changed again. I've just restored the correct value.
Puppet is meant to be setting this. I'll look into that.

Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: Where are we going?

[Mark Thomas]

On 07/03/2020 15:35, Stefan Bodewig wrote:
> Hi all
> 
> nowadays Gump has become a tool that really only gets used by Tomcat. As
> long as it is useful for Tomcat this is probably fine. But is this the
> future of this project? Honestly, I haven't got any other vision to
> share.

It is definitely useful for Tomcat and indirectly for its dependencies.
We caught a regression in OpenSSL master that would otherwise have gone
unnoticed.

The nature of the VM Gump runs on also seems to be good at catching
various concurrency issues.

To me, at least, it is clear that keeping vmgump running is in the best
interest of the Tomcat project.

I don't have a vision that would expand Gump and/or breath new life into
the project. Maybe something will emerge with Jakarta EE and a need to
check interoperability between various projects? I don't know. Seems
like a bit of a stretch if I am honest.

> I wonder whether this in any way affects Gump's position of an Apache
> TLP. We've always been a special kind of project, more like an
> infrastructure service than a project that creates releases.

Interesting question.

As I see it the options are:

a) continue as is
b) hand over to infra to maintain
c) hand over to the Tomcat PMC to maintain

I think b) is the least likely. I don't think infra would accept it. I
might be wrong. I'll ask.

If the board is happy with a) and we have 3 PMC members then the status
quo is probably the least work.

c) probably means retiring the Gump project but with the slight twist
that ongoing maintenance of the Gump svn repo is handed over to the
Tomcat PMC rather than it being made read-only. I don't know what the
Tomcat community would say to that. I'll ask.

I don't think we need to be in any great rush to decide what to do. I
think we have the 3 PMC members (we can always do a roll-call on
private@ to confirm that if we want) so the status quo is OK.

Cheers,

Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Gump runs taking ~9 hours

[Mark Thomas]

With the creation of an additional Tomcat branch and another set of 3
unit tests, the Gump runs are now taking ~9 hours. I have reduced the
daily runs to 2: midnight (the main run) and noon UTC.

Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: BATCH: All dressed up, with nowhere to go...

[Mark Thomas]

On 05/02/2020 09:52, Mark Thomas wrote:
> The root cause of these errors is this:
> https://support.sonatype.com/hc/en-us/articles/360041287334-Central-501-HTTPS-Required
> 
> Maven central now requires https.
> 
> I'm not sure how easy a fix this is going to be.

Should be fixed now.

The next issue is why the web pages (and database?) are not getting
updated at the end of a run. I saw some errors when I ran Gump manually
yesterday. I ignored them on the basis is was related to manual running.
That may not be the case.

Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: BATCH: All dressed up, with nowhere to go...

[Mark Thomas]

The root cause of these errors is this:
https://support.sonatype.com/hc/en-us/articles/360041287334-Central-501-HTTPS-Required

Maven central now requires https.

I'm not sure how easy a fix this is going to be.

Mark


On 19/01/2020 01:21, g...@gump-vm.apache.org wrote:
> Dear Gumpmeisters,
> 
> The following 12 notifys should have been sent
> 
> *** G U M P
> [GUMP@gump-vm]: Project logging-log4j-12 (in module logging-log4j-12) failed
> [GUMP@gump-vm]: Project commons-lang (in module commons-lang-2.x) failed
> [GUMP@gump-vm]: Project commons-io (in module commons-io) failed
> [GUMP@gump-vm]: Project google-guava-parent (in module google-guava) failed
> [GUMP@gump-vm]: Project commons-net (in module commons-net) failed
> [GUMP@gump-vm]: Project google-guava (in module google-guava) failed
> [GUMP@gump-vm]: Project commons-daemon (in module commons-daemon) failed
> [GUMP@gump-vm]: Project easymock-parent (in module easymock) failed
> [GUMP@gump-vm]: Project objenesis-parent (in module objenesis) failed
> [GUMP@gump-vm]: Project commons-validator (in module commons-validator) failed
> [GUMP@gump-vm]: Project commons-lang3 (in module commons-lang-trunk) failed
> [GUMP@gump-vm]: Project commons-exec (in module commons-exec) failed
> *** G U M P
> [GUMP@gump-vm]: Project logging-log4j-12 (in module logging-log4j-12) failed
> To whom it may engage...
> 
> This is an automated request, but not an unsolicited one. For 
> more information please visit http://gump.apache.org/nagged.html, 
> and/or contact the folk at general@gump.apache.org.
> 
> Project logging-log4j-12 has an issue affecting its community integration.
> This issue affects 11 projects,
>  and has been outstanding for 10 runs.
> The current state of this project is 'Failed', with reason 'Build Failed'.
> For reference only, the following projects are affected by this:
> - checkstyle :  Java style checker
> - commons-beanutils :  Bean Utilities
> - commons-digester :  XML to Java Object Configuration
> - commons-logging :  Logging Library Package
> - commons-logging-step-1 :  Logging Library Package
> - jakarta-bsf :  Bean Scripting Framework
> - logging-log4j-12 :  Fast and flexible logging package for Java
> - logging-log4j-12-tests :  Fast and flexible logging package for Java
> - tomcat-tc7.0.x-validate :  Tomcat 7.x, a web server implementing Java 
> Servlet 3.0,
> ...
> - tomcat-tc8.5.x-validate :  Tomcat 8.x, a web server implementing the 
> Java Servlet 3.1,
> ...
> - tomcat-trunk-validate :  Tomcat 9.x, a web server implementing the Java 
> Servlet 4.0,
> ...
> 
> 
> Full details are available at:
> http://gump-vm.apache.org/logging-log4j-12/logging-log4j-12/index.html
> 
> That said, some information snippets are provided here.
> 
> The following annotations (debug/informational/warning/error messages) were 
> provided:
>  -DEBUG- (Apache Gump generated) Apache Maven Settings in: 
> /srv/gump/public/workspace/logging-log4j-12/gump_mvn_settings.xml
>  -INFO- Failed with reason build failed
>  -DEBUG- Maven POM in: /srv/gump/public/workspace/logging-log4j-12/pom.xml
>  -DEBUG- Extracted fallback artifacts from Gump Repository
> 
> 
> 
> The following work was performed:
> http://gump-vm.apache.org/logging-log4j-12/logging-log4j-12/gump_work/build_logging-log4j-12_logging-log4j-12.html
> Work Name: build_logging-log4j-12_logging-log4j-12 (Type: Build)
> Work ended in a state of : Failed
> Elapsed: 2 secs
> Command Line: /opt/maven2/bin/mvn --batch-mode -DskipTests=true 
> -Dmaven.javadoc.failOnError=false --settings 
> /srv/gump/public/workspace/logging-log4j-12/gump_mvn_settings.xml package 
> [Working Directory: /srv/gump/public/workspace/logging-log4j-12]
> M2_HOME: /opt/maven2
> -
> [INFO] Scanning for projects...
> Downloading: 
> http://localhost:8192/maven2/org/apache/felix/maven-bundle-plugin/2.1.0/maven-bundle-plugin-2.1.0.pom
> [WARNING] Unable to get resource 
> 'org.apache.felix:maven-bundle-plugin:pom:2.1.0' from repository central 
> (http://repo1.maven.org/maven2): Error transferring file: Server returned 
> HTTP response code: 501 for URL: 
> http://localhost:8192/maven2/org/apache/felix/maven-bundle-plugin/2.1.0/maven-bundle-plugin-2.1.0.pom
> Downloading: 
> http://localhost:8192/maven/2/org/apache/felix/maven-bundle-plugin/2.1.0/maven-bundle-plugin-2.1.0.pom
> 0b downloaded  (maven-bundle-plugin-2.1.0.pom)
> [WARNING] *** CHECKSUM FAILED - Invalid checksum file - RETRYING
> Downloading: 
> http://localhost:8192/maven/2/org/apache/felix/maven-bundle-plugin/2.1.0/maven-bundle-plugin-2.1.0.pom
> 0b downloaded  (maven-bundle-plugin-2.1.0.pom)
> [WARNING] *** CHECKSUM FAILED - Invalid checksum file - IGNORING
> [INFO] Unable to find resource 
> 'org.apache.felix:maven-bundle-plugin:pom:2.1.0' in 

Re: Gump CI build failing for Apache Forrest for more than 1 year

[Mark Thomas]

Hi,

I am going to assume that Forrest no longer requires the services of
Apache Gump and go ahead with the clean-up.

Mark


On 2019/06/17 12:07:56, Mark Thomas  wrote: > On
17/06/2019 12:46, Tim Williams wrote:
> > Hey Mark,
> > I suspect not... instead, we should have the dreaded attic discussion I
> > reckon.
> 
> Looking at the (lack of) mailing list activity I'd have to concur
> although the attic decision isn't my call to make.
> 
> What I can do, whether Forrest decides to got to the attic or not, is
> make the following offer:
> 
> If Forrest no longer needs the services of Apache Gump let me (via
> general@gump.apache.org) know and I'll take care of cleaning all that up
> for you.
> 
> Mark
> 
> > 
> > Thanks,
> > --tim
> > 
> > On Mon, Jun 17, 2019 at 6:55 AM Mark Thomas  wrote:
> > 
> >> All,
> >>
> >> The last successful Apache Forrest build on Gump was over 12 months ago.
> >>
> >> Looking back ~6 months I don't see any indications of the Apache Forrest
> >> community working on the build failures. Granted the issues are mostly
> >> in dependencies but that shouldn't prevent the Forrest community
> >> addressing them.
> >>
> >> The current issue is a dependency on xml-stylebook that in turn depends
> >> on JVM internals that were removed in Java 7.
> >>
> >> Are Gump builds still of interest to the Apache Forrest community?
> >>
> >> Mark
> >>
> > 
> 
> 

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: Maven updated on vmgump

[Mark Thomas]

On 20/11/2019 16:50, Mark Thomas wrote:
> Hi,
> 
> I saw the Easymock build has been failing for a while as it requires
> Maven 3.5.0 or later.
> 
> I've updated the /opt/maven3 symlink to point to the latest Maven 3.x
> (3.6.2).
> 
> I'll keep an eye on the next few builds to see what breaks.

Nothing broke because the Maven version is managed by Puppet which
reverted the symlink back to 3.3.9. I've updated Puppet this time...

Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Maven updated on vmgump

[Mark Thomas]

Hi,

I saw the Easymock build has been failing for a while as it requires
Maven 3.5.0 or later.

I've updated the /opt/maven3 symlink to point to the latest Maven 3.x
(3.6.2).

I'll keep an eye on the next few builds to see what breaks.

Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: Problem running Apache Gump [vmgump]

[Mark Thomas]

Known config issue. I think I have fixed it. Need to chat with Infra to
figure out how to make the config change persist.

Mark


On 27/07/2019 00:00, g...@gump-vm.apache.org wrote:
> There is a problem with run 'vmgump' (27072019_02), location : 
> http://gump-vm.apache.org/
> 
> The log ought be at:
>http://gump-vm.apache.org/gump_log.txt
> 
> The last (up to) 50 lines of the log are :
> Perform Subversion Checkout/Update on #[(1, 73)] : gump
> Loading prefix map from /tmp/tmpno6GXs.properties
> java.io.FileNotFoundException: /tmp/tmpno6GXs.properties (No such file or 
> directory)
>   at java.base/java.io.FileInputStream.open0(Native Method)
>   at java.base/java.io.FileInputStream.open(FileInputStream.java:219)
>   at java.base/java.io.FileInputStream.(FileInputStream.java:157)
>   at java.base/java.io.FileInputStream.(FileInputStream.java:112)
>   at org.apache.gump.mvnrepoproxy.Main.main(Main.java:98)
> Build Project: #[(1, 171)] : ant-1.6.5-pom :  [state:Unset]
> SQL Warning::(1292, "Incorrect 
> datetime value: '-00-00 00:00:00' for column 'start' at row 1")
> SQL Error on [INSERT INTO gump_public.gump_project_run (state, project_name, 
> reason, run_id) VALUES (2, 'ant-1.6.5-pom', 0, 
> '6052B41F4C8BF5BBE83552F0DB28322D')] : (1292, "Incorrect datetime value: 
> '-00-00 00:00:00' for column 'start' at row 1")
> Traceback (most recent call last):
>   File "/srv/gump/public/gump/python/gump/util/mysql.py", line 244, in insert
> affected = cursor.execute(statement)
>   File "/usr/lib/python2.7/dist-packages/MySQLdb/cursors.py", line 250, in 
> execute
> self.errorhandler(self, exc, value)
>   File "/usr/lib/python2.7/dist-packages/MySQLdb/connections.py", line 50, in 
> defaulterrorhandler
> raise errorvalue
> OperationalError: (1292, "Incorrect datetime value: '-00-00 00:00:00' for 
> column 'start' at row 1")
> Traceback (most recent call last):
>   File "bin/integrate.py", line 114, in 
> irun()
>   File "bin/integrate.py", line 91, in irun
> result = getRunner(run).perform()
>   File "/srv/gump/public/gump/python/gump/core/runner/runner.py", line 262, 
> in perform
> return self.performRun()
>   File "/srv/gump/public/gump/python/gump/core/runner/demand.py", line 199, 
> in performRun
> self.performBuild(project)
>   File "/srv/gump/public/gump/python/gump/core/runner/demand.py", line 130, 
> in performBuild
> self.run.generateEvent(project)
>   File "/srv/gump/public/gump/python/gump/core/run/gumprun.py", line 203, in 
> generateEvent
> self._dispatchEvent(EntityRunEvent(self, entity))
>   File "/srv/gump/public/gump/python/gump/core/run/gumprun.py", line 186, in 
> _dispatchEvent
> actor._processEvent(event)
>   File "/srv/gump/public/gump/python/gump/core/run/actor.py", line 83, in 
> _processEvent
> self.processEvent(event)
>   File "/srv/gump/public/gump/python/gump/core/run/actor.py", line 125, in 
> processEvent
> self._processProject(entity)
>   File "/srv/gump/public/gump/python/gump/core/run/actor.py", line 172, in 
> _processProject
> self.processProject(project)
>   File "/srv/gump/public/gump/python/gump/actor/mysql/databaser.py", line 
> 101, in processProject
> helper.insert('gump_project_run', settings)
>   File "/srv/gump/public/gump/python/gump/util/mysql.py", line 244, in insert
> affected = cursor.execute(statement)
>   File "/usr/lib/python2.7/dist-packages/MySQLdb/cursors.py", line 250, in 
> execute
> self.errorhandler(self, exc, value)
>   File "/usr/lib/python2.7/dist-packages/MySQLdb/connections.py", line 50, in 
> defaulterrorhandler
> raise errorvalue
> _mysql_exceptions.OperationalError: (1292, "Incorrect datetime value: 
> '-00-00 00:00:00' for column 'start' at row 1")
> Process Exit Code : 1
> --
> Gump Version: 2.0.2-alpha-0003
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
> For additional commands, e-mail: general-h...@gump.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: Gump CI build failing for Apache Forrest for more than 1 year

[Mark Thomas]

On 17/06/2019 12:46, Tim Williams wrote:
> Hey Mark,
> I suspect not... instead, we should have the dreaded attic discussion I
> reckon.

Looking at the (lack of) mailing list activity I'd have to concur
although the attic decision isn't my call to make.

What I can do, whether Forrest decides to got to the attic or not, is
make the following offer:

If Forrest no longer needs the services of Apache Gump let me (via
general@gump.apache.org) know and I'll take care of cleaning all that up
for you.

Mark

> 
> Thanks,
> --tim
> 
> On Mon, Jun 17, 2019 at 6:55 AM Mark Thomas  wrote:
> 
>> All,
>>
>> The last successful Apache Forrest build on Gump was over 12 months ago.
>>
>> Looking back ~6 months I don't see any indications of the Apache Forrest
>> community working on the build failures. Granted the issues are mostly
>> in dependencies but that shouldn't prevent the Forrest community
>> addressing them.
>>
>> The current issue is a dependency on xml-stylebook that in turn depends
>> on JVM internals that were removed in Java 7.
>>
>> Are Gump builds still of interest to the Apache Forrest community?
>>
>> Mark
>>
> 


-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Gump CI build failing for Apache Forrest for more than 1 year

[Mark Thomas]

All,

The last successful Apache Forrest build on Gump was over 12 months ago.

Looking back ~6 months I don't see any indications of the Apache Forrest
community working on the build failures. Granted the issues are mostly
in dependencies but that shouldn't prevent the Forrest community
addressing them.

The current issue is a dependency on xml-stylebook that in turn depends
on JVM internals that were removed in Java 7.

Are Gump builds still of interest to the Apache Forrest community?

Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: BATCH: All dressed up, with nowhere to go...

[Mark Thomas]

FYI:

The gump-vm instance (the new one) is taking a little over 6 hours for a
complete run. I am currently starting some of the runs manually to try
and get three runs a day rather than two. I will also take a look at the
machine specs and the configuration of the long running Tomcat tests to
see if the Tomcat tests can be configured to run a little faster.

Mark


On 13/06/2019 06:26, g...@gump-vm.apache.org wrote:
> Dear Gumpmeisters,
> 
> The following 5 notifys should have been sent
> 
> *** G U M P
> [GUMP@gump-vm]: Module commons-digester-2.x failed
> [GUMP@gump-vm]: Project commons-digester (in module commons-digester-2.x) 
> failed
> [GUMP@gump-vm]: Project commons-jxpath (in module commons-jxpath) failed
> [GUMP@gump-vm]: Project test-ant (in module ant) failed
> [GUMP@gump-vm]: Project commons-bcel (in module apache-commons) failed
> *** G U M P
> [GUMP@gump-vm]: Module commons-digester-2.x failed
> To whom it may engage...
> 
> This is an automated request, but not an unsolicited one. For 
> more information please visit http://gump.apache.org/nagged.html, 
> and/or contact the folk at general@gump.apache.org.
> 
> Module commons-digester-2.x has an issue affecting its community integration,
>  and has been outstanding for 72 runs.
> The current state of this module is 'Failed', with reason 'Update Failed'.
> 
> Full details are available at:
> http://gump-vm.apache.org/commons-digester-2.x/index.html
> 
> That said, some information snippets are provided here.
> 
> The following annotations (debug/informational/warning/error messages) were 
> provided:
>  -INFO- Failed with reason update failed
> 
> 
> 
> The following work was performed:
> http://gump-vm.apache.org/commons-digester-2.x/gump_work/update_commons-digester-2.x.html
> Work Name: update_commons-digester-2.x (Type: Update)
> Work ended in a state of : Failed
> Elapsed: 
> Command Line: svn --quiet checkout 
> http://svn.apache.org/repos/asf/commons/proper/digester/branches/DIGESTER_2_X 
> --non-interactive commons-digester-2.x 
> [Working Directory: /srv/gump/public/workspace/cvs]
> -
> svn: E17: URL 
> 'http://svn.apache.org/repos/asf/commons/proper/digester/branches/DIGESTER_2_X'
>  doesn't exist
> -
> 
> To subscribe to this information via syndicated feeds:
> - RSS: http://gump-vm.apache.org/commons-digester-2.x/rss.xml
> - Atom: http://gump-vm.apache.org/commons-digester-2.x/atom.xml
> 
> == Gump Tracking Only ===
> Produced by Apache Gump(TM) version 2.3.
> Gump Run 2019061306, gump-vm.apache.org:vmgump:2019061306
> Gump E-mail Identifier (unique within run) #1.
> 
> *** G U M P
> [GUMP@gump-vm]: Project commons-digester (in module commons-digester-2.x) 
> failed
> To whom it may engage...
> 
> This is an automated request, but not an unsolicited one. For 
> more information please visit http://gump.apache.org/nagged.html, 
> and/or contact the folk at general@gump.apache.org.
> 
> Project commons-digester has an issue affecting its community integration,
>  and has been outstanding for 72 runs.
> The current state of this project is 'Failed', with reason 'Update Failed'.
> 
> Full details are available at:
> http://gump-vm.apache.org/commons-digester-2.x/commons-digester/index.html
> 
> That said, some information snippets are provided here.
> 
> The following annotations (debug/informational/warning/error messages) were 
> provided:
>  -DEBUG- Sole jar output [commons-digester-2.2-SNAPSHOT.jar] identifier set 
> to project name
>  -WARNING- Bad *Optional* Dependency. Project: velocity-engine : unknown to 
> *this* workspace
>  -INFO- Failed with reason update failed
>  -INFO- Failed to extract fallback artifacts from Gump Repository
> 
> To subscribe to this information via syndicated feeds:
> - RSS: http://gump-vm.apache.org/commons-digester-2.x/commons-digester/rss.xml
> - Atom: 
> http://gump-vm.apache.org/commons-digester-2.x/commons-digester/atom.xml
> 
> == Gump Tracking Only ===
> Produced by Apache Gump(TM) version 2.3.
> Gump Run 2019061306, gump-vm.apache.org:vmgump:2019061306
> Gump E-mail Identifier (unique within run) #2.
> 
> *** G U M P
> [GUMP@gump-vm]: Project commons-jxpath (in module commons-jxpath) failed
> To whom it may engage...
> 
> This is an automated request, but not an unsolicited one. For 
> more information please visit http://gump.apache.org/nagged.html, 
> and/or contact the folk at general@gump.apache.org.
> 
> Project commons-jxpath has an issue affecting its community integration.
> This issue affects 4 projects,
>  and has been outstanding for 72 runs.
> The 

Re: Cron /usr/bin/find /tmp -type f -ctime +6 | /usr/bin/xargs -r /bin/rm > /dev/null 2>&1

[Mark Thomas]

On 31/05/2019 14:36, Stefan Bodewig wrote:
> On 2019-05-31, Mark Thomas wrote:
> 
>> On 31/05/2019 13:22, Stefan Bodewig wrote:
>>> On 2019-05-31, sebb wrote:
> 
>>>> The command:
> 
>>>> /usr/bin/find /tmp -type f -ctime +6 | /usr/bin/xargs -r /bin/rm >
>>>> /dev/null 2>&1
> 
>>>> should perhaps be
> 
>>>> /usr/bin/find /tmp -type f -ctime +6 > /dev/null 2>&1 | /usr/bin/xargs
>>>> -r /bin/rm
> 
>>>> or maybe
> 
>>>> { /usr/bin/find /tmp -type f -ctime +6 | /usr/bin/xargs -r /bin/rm } >
>>>> /dev/null 2>&1
> 
>>> Probably,
> 
>>> Infra is in the process of setting up a new VM for us and the mails will
>>> keep coming in until somebody of us has time to complete the post-puppet
>>> setup - which may be a few weeks to be honest.
> 
>>> https://github.com/apache/infrastructure-puppet/blob/deployment/modules/gump_server/manifests/cronjobs.pp
> 
>>> contains what would need to be fixed IIRC.
> 
>> I can find some time. To be clear the issue is that the cron jobs aren't
>> quite defined correctly and those definitions need to be fixed?
> 
> *This* problem, yes. There are more of them. :-)
> 
> Basically we need to perform the steps listed in
> https://cwiki.apache.org/confluence/display/GUMP/VmgumpConfig after
> "Puppet" and before
> "https://cwiki.apache.org/confluence/display/GUMP/VmgumpConfig;
> 
> and I'm afraid we are now using Python 3 but haven't verified that -
> which might require changes to the code base.
> 
> Also some of the Ubuntu packages defined as dependencies in Puppet, in
> particular those for Mono have probably failed to install.
> 
>> And the fixes need to be made in the file quote above and then Puppet
>> will deploy the updated cron jobs to our new VM?
> 
> Here I am guessing. This is (part of) the Puppet manifest that was used
> to set up vmgump3. I believe it has been used to set up the new
> machine. 
> 
> Stefan

OK. I'll see what I can do. I'll update that wiki page as I go.

Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: Cron /usr/bin/find /tmp -type f -ctime +6 | /usr/bin/xargs -r /bin/rm > /dev/null 2>&1

[Mark Thomas]

On 31/05/2019 13:22, Stefan Bodewig wrote:
> On 2019-05-31, sebb wrote:
> 
>> The command:
> 
>> /usr/bin/find /tmp -type f -ctime +6 | /usr/bin/xargs -r /bin/rm >
>> /dev/null 2>&1
> 
>> should perhaps be
> 
>> /usr/bin/find /tmp -type f -ctime +6 > /dev/null 2>&1 | /usr/bin/xargs
>> -r /bin/rm
> 
>> or maybe
> 
>> { /usr/bin/find /tmp -type f -ctime +6 | /usr/bin/xargs -r /bin/rm } >
>> /dev/null 2>&1
> 
> Probably,
> 
> Infra is in the process of setting up a new VM for us and the mails will
> keep coming in until somebody of us has time to complete the post-puppet
> setup - which may be a few weeks to be honest.
> 
> https://github.com/apache/infrastructure-puppet/blob/deployment/modules/gump_server/manifests/cronjobs.pp
> 
> contains what would need to be fixed IIRC.

I can find some time. To be clear the issue is that the cron jobs aren't
quite defined correctly and those definitions need to be fixed? And the
fixes need to be made in the file quote above and then Puppet will
deploy the updated cron jobs to our new VM?

Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: svn commit: r1829908 - /gump/metadata/project/eclipse.xml

[Mark Thomas]

On 23/04/18 18:00, bode...@apache.org wrote:
> Author: bodewig
> Date: Mon Apr 23 17:00:37 2018
> New Revision: 1829908
> 
> URL: http://svn.apache.org/viewvc?rev=1829908=rev
> Log:
> fix filename
> 
> Modified:
> gump/metadata/project/eclipse.xml
> 
> Modified: gump/metadata/project/eclipse.xml
> URL: 
> http://svn.apache.org/viewvc/gump/metadata/project/eclipse.xml?rev=1829908=1829907=1829908=diff
> ==
> --- gump/metadata/project/eclipse.xml (original)
> +++ gump/metadata/project/eclipse.xml Mon Apr 23 17:00:37 2018
> @@ -28,7 +28,7 @@
>  
>  
>  
> -
> +

The original name was correct. Looks like I fat-fingered the on-disk
name. I'll fix that.

Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: BATCH: All dressed up, with nowhere to go...

[Mark Thomas]

On 22/04/18 20:02, Stefan Bodewig wrote:
> On 2018-04-22, Mark Thomas wrote:
> 
>> I think I've fixed this.
> 
> Don't forget to update the checked out copy on vmgump-vm3 (I forgot to
> do so for hamcrest-library :-).

All good on that one. I didn't know the packages were in svn. I added
the JAR to vmgump-vm3 first then did 'svn st' to see if it needed to be
checked it ;)

Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: BATCH: All dressed up, with nowhere to go...

[Mark Thomas]

I think I've fixed this.

Sorry for the noise.

Mark

On 22/04/18 18:46, g...@vmgump-vm3.apache.org wrote:
> Dear Gumpmeisters,
> 
> The following 1 notifys should have been sent
> 
> *** G U M P
> [GUMP@vmgump-vm3]: Project eclipse (in module eclipse) failed
> *** G U M P
> [GUMP@vmgump-vm3]: Project eclipse (in module eclipse) failed
> To whom it may engage...
> 
> This is an automated request, but not an unsolicited one. For 
> more information please visit http://gump.apache.org/nagged.html, 
> and/or contact the folk at general@gump.apache.org.
> 
> Project eclipse has an issue affecting its community integration.
> This issue affects 17 projects.
> The current state of this project is 'Failed', with reason 'Bad Package 
> Installation'.
> For reference only, the following projects are affected by this:
> - eclipse :  The Eclipse jars
> - forrest-test :  Apache Forrest software is a publishing framework that 
> trans...
> - forrest-test-basic :  Apache Forrest software is a publishing framework 
> that trans...
> - forrest-test-deploy-plugins :  Apache Forrest software is a publishing 
> framework that trans...
> - tomcat-tc7.0.x :  Tomcat 7.x, a web server implementing Java Servlet 
> 3.0,
> ...
> - tomcat-tc7.0.x-test-apr :  Tomcat 7.x, a web server implementing Java 
> Servlet 3.0,
> ...
> - tomcat-tc7.0.x-test-bio :  Tomcat 7.x, a web server implementing Java 
> Servlet 3.0,
> ...
> - tomcat-tc7.0.x-test-nio :  Tomcat 7.x, a web server implementing Java 
> Servlet 3.0,
> ...
> - tomcat-tc8.0.x :  Tomcat 8.x, a web server implementing the Java 
> Servlet 3.1,
> ...
> - tomcat-tc8.0.x-test-apr :  Tomcat 8.x, a web server implementing the 
> Java Servlet 3.1,
> ...
> - tomcat-tc8.0.x-test-bio :  Tomcat 8.x, a web server implementing the 
> Java Servlet 3.1,
> ...
> - tomcat-tc8.0.x-test-nio :  Tomcat 8.x, a web server implementing the 
> Java Servlet 3.1,
> ...
> - tomcat-tc8.0.x-test-nio2 :  Tomcat 8.x, a web server implementing the 
> Java Servlet 3.1,
> ...
> - tomcat-trunk :  Tomcat 9.x, a web server implementing the Java Servlet 
> 4.0,
> ...
> - tomcat-trunk-test-apr :  Tomcat 9.x, a web server implementing the Java 
> Servlet 4.0,
> ...
> - tomcat-trunk-test-nio :  Tomcat 9.x, a web server implementing the Java 
> Servlet 4.0,
> ...
> - tomcat-trunk-test-nio2 :  Tomcat 9.x, a web server implementing the 
> Java Servlet 4.0,
> ...
> 
> 
> Full details are available at:
> http://vmgump-vm3.apache.org/eclipse/eclipse/index.html
> 
> That said, some information snippets are provided here.
> 
> The following annotations (debug/informational/warning/error messages) were 
> provided:
>  -INFO- This is a packaged project, location: /srv/gump/packages/eclipse
>  -INFO- Failed with reason bad package installation
>  -ERROR- Missing Packaged Output: 
> /srv/gump/packages/eclipse/plugins/R-4.7.3a-201803300640/ecj-4.7.3a.jar
> 
> To subscribe to this information via syndicated feeds:
> - RSS: http://vmgump-vm3.apache.org/eclipse/eclipse/rss.xml
> - Atom: http://vmgump-vm3.apache.org/eclipse/eclipse/atom.xml
> 
> == Gump Tracking Only ===
> Produced by Apache Gump(TM) version 2.3.
> Gump Run 20180422180006, vmgump-vm3.apache.org:vmgump:20180422180006
> Gump E-mail Identifier (unique within run) #1.
> 
> 
> --
> Apache Gump
> http://gump.apache.org/ [Instance: vmgump-vm3]
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
> For additional commands, e-mail: general-h...@gump.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: BATCH: All dressed up, with nowhere to go...

[Mark Thomas]

There was an svn glitch overnight. Things should sort themselves out in
the next run.

Mark


On 15/03/18 01:23, g...@vmgump-vm3.apache.org wrote:
> Dear Gumpmeisters,
> 
> The following 24 notifys should have been sent
> 
> *** G U M P
> [GUMP@vmgump-vm3]: Module pdfbox failed
> [GUMP@vmgump-vm3]: Project pdfbox-parent (in module pdfbox) failed
> [GUMP@vmgump-vm3]: Module apache-httpd failed
> [GUMP@vmgump-vm3]: Project apache-httpd-buildconf (in module apache-httpd) 
> failed
> [GUMP@vmgump-vm3]: Module tomcat-taglibs failed
> [GUMP@vmgump-vm3]: Project apache-httpd-configure (in module apache-httpd) 
> failed
> [GUMP@vmgump-vm3]: Module xml-stylebook failed
> [GUMP@vmgump-vm3]: Project xml-stylebook2 (in module xml-stylebook) failed
> [GUMP@vmgump-vm3]: Module jakarta-servletapi-5 failed
> [GUMP@vmgump-vm3]: Project jakarta-servletapi-5-servlet (in module 
> jakarta-servletapi-5) failed
> [GUMP@vmgump-vm3]: Module commons-codec-1.x failed
> [GUMP@vmgump-vm3]: Project commons-codec (in module commons-codec-1.x) failed
> [GUMP@vmgump-vm3]: Project txt2html-task (in module jakarta-servletapi-5) 
> failed
> [GUMP@vmgump-vm3]: Module forrest failed
> [GUMP@vmgump-vm3]: Module tomcat-7.0.x failed
> [GUMP@vmgump-vm3]: Module tomcat-8.0.x failed
> [GUMP@vmgump-vm3]: Module tomcat-trunk failed
> [GUMP@vmgump-vm3]: Project compress-antlib-test (in module antlibs-compress) 
> failed
> [GUMP@vmgump-vm3]: Module jakarta-bsf failed
> [GUMP@vmgump-vm3]: Project fontbox (in module pdfbox) failed
> [GUMP@vmgump-vm3]: Module xmlgraphics-commons failed
> [GUMP@vmgump-vm3]: Module xmlsec failed
> [GUMP@vmgump-vm3]: Module commons-digester-2.x failed
> [GUMP@vmgump-vm3]: Project test-ant (in module ant) failed
> *** G U M P
> [GUMP@vmgump-vm3]: Module pdfbox failed
> To whom it may engage...
> 
> This is an automated request, but not an unsolicited one. For 
> more information please visit http://gump.apache.org/nagged.html, 
> and/or contact the folk at general@gump.apache.org.
> 
> Module pdfbox has an issue affecting its community integration,
>  and has been outstanding for 54 runs.
> The current state of this module is 'Failed', with reason 'Update Failed'.
> 
> Full details are available at:
> http://vmgump-vm3.apache.org/pdfbox/index.html
> 
> That said, some information snippets are provided here.
> 
> The following annotations (debug/informational/warning/error messages) were 
> provided:
>  -INFO- Failed with reason update failed
> 
> 
> 
> The following work was performed:
> http://vmgump-vm3.apache.org/pdfbox/gump_work/update_pdfbox.html
> Work Name: update_pdfbox (Type: Update)
> Work ended in a state of : Failed
> Elapsed: 
> Command Line: svn --quiet update --non-interactive pdfbox 
> [Working Directory: /srv/gump/public/workspace/cvs]
> -
> svn: E175013: Unable to connect to a repository at URL 
> 'http://svn.apache.org/repos/asf/pdfbox/trunk'
> svn: E175013: Access to '/repos/asf/pdfbox/trunk' forbidden
> -
> 
> To subscribe to this information via syndicated feeds:
> - RSS: http://vmgump-vm3.apache.org/pdfbox/rss.xml
> - Atom: http://vmgump-vm3.apache.org/pdfbox/atom.xml
> 
> == Gump Tracking Only ===
> Produced by Apache Gump(TM) version 2.3.
> Gump Run 2018031506, vmgump-vm3.apache.org:vmgump:2018031506
> Gump E-mail Identifier (unique within run) #1.
> 
> *** G U M P
> [GUMP@vmgump-vm3]: Project pdfbox-parent (in module pdfbox) failed
> To whom it may engage...
> 
> This is an automated request, but not an unsolicited one. For 
> more information please visit http://gump.apache.org/nagged.html, 
> and/or contact the folk at general@gump.apache.org.
> 
> Project pdfbox-parent has an issue affecting its community integration,
>  and has been outstanding for 54 runs.
> The current state of this project is 'Failed', with reason 'Update Failed'.
> 
> Full details are available at:
> http://vmgump-vm3.apache.org/pdfbox/pdfbox-parent/index.html
> 
> That said, some information snippets are provided here.
> 
> The following annotations (debug/informational/warning/error messages) were 
> provided:
>  -INFO- Failed with reason update failed
> 
> To subscribe to this information via syndicated feeds:
> - RSS: http://vmgump-vm3.apache.org/pdfbox/pdfbox-parent/rss.xml
> - Atom: http://vmgump-vm3.apache.org/pdfbox/pdfbox-parent/atom.xml
> 
> == Gump Tracking Only ===
> Produced by Apache Gump(TM) version 2.3.
> Gump Run 2018031506, vmgump-vm3.apache.org:vmgump:2018031506
> Gump E-mail Identifier (unique within run) #2.
> 
> *** G U M P
> [GUMP@vmgump-vm3]: Module apache-httpd failed
> To whom it may 

Re: Is Gump still useful for you?

[Mark Thomas]

On 23/02/18 17:52, Stefan Bodewig wrote:
> Hi all
> 
> when writing Gump's quarterly report for the Apache board we usually
> include the phrase "Gump seems to remain useful for the projects using
> it". Back in September 2017 Gump builds stopped for several weeks and
> nobody seems to have noticed or at least complained about it. So maybe
> this isn't really true anymore?
> 
> Currently the projects that have nags enabled in Gump are
> 
> * Batik
> * XMLGraphics Commons
> * Santuario
> * Tomcat
> 
> in addition to a few projects where I receive the nags myself.
> 
> Are you even aware Gump is there and do you still consider it to provide
> value to your project? This is not any request for you to get involved
> but really a curious question.

Personal view, not speaking for the project.

Yes and yes.

I know we didn't notice it when Gump stopped but I thought we'd just had
a good run of not breaking it. We do get useful reports from Gump. It
has identified, and continues to identify, areas where we need to make
the tests more robust. (Generally Gump finds errors in tests more often
than it finds errors in code but those are still useful.)

Another area that is particularly useful is the tests against the latest
OpenSSL build. Gump enables is to spot within 24 hours when OpenSSL has
added a new cipher, removed an old cipher, etc so we can update our
integration.

HTH,

Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: svn commit: r1817993 - /gump/metadata/project/tomcat-trunk.xml

[Mark Thomas]

On 14/12/17 13:18, Konstantin Kolinko wrote:
> Hi, Mark!
> 
> To dev@tomcat, cc: general@gump.
> 
> 
> The result of this change is that Gump building Tomcat downloads
> tar.gz for Commons-Daemon from mirrors.

Drat. That wasn't the intention at all.



> The "mvn package" command used by Gump does not build the src.tar.gz file.
> 
> The file can be built by "mvn assembly:single" command, [4]
> but HOWTO-RELEASE.txt file does not mention it so I wonder what is
> actually used by Commons Daemon here.

The command 'mvn deploy -Prelease' creates it. I suspect that isn't
appropriate for Gump.

> So this can be fixed by updating Gump configuration for commons-daemon to do
>  and
>   id="native-distro" />
> 
> 
> Alternatively, a question is whether the "deploy" target in Tomcat
> actually has a need to copy the *.tar.gz files to CATALINA_HOME/bin/.
> Those source file are needed when redistributing Tomcat, but they are
> not actually needed when running it.

Good point.

The Windows binaries are only copied to /bin for the dist-static target.
I can't see a reason not to treat the *.tar.gz src files the same way.

Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: Board Report

[Mark Thomas]

On 13/12/17 10:10, Stefan Bodewig wrote:
> On 2017-12-13, Mark Thomas wrote:
> 
>> On 13/12/17 09:37, Konstantin Kolinko wrote:
>>> 2017-11-30 17:21 GMT+03:00 Stefan Bodewig <bode...@apache.org>:
>>>> Hi all
> 
>>>> current draft is
>>>> https://wiki.apache.org/gump/Drafts/BoardReports/20171220 - I'll have to
>>>> submit it in about two weeks.
> 
>>>> Back when vmgump failed in September I talked about asking projects
>>>> whether they still see value in Gump but never got my act together. This
>>>> time I've put it into the report to increase the chance of actually
>>>> doing it.
> 
>>> Looks OK.
>>> I think it would be better to mention the date when hickup happened,
> 
>>> s/After a hickup the service seems to be good again./After a hickup in
>>> September 2017 the service seems to be good again./
> 
>> Nitpick. s/hickup/hiccup/
> 
> Thanks to both of you. I've changed the sentence and will submit the
> report today.
> 
>> There is probably a good(ish) reason for this unexpected spelling but I
>> have no ideas what it is.

Sorry, I just realised the above was not clear. I meant that there was
probably a good(ish) reason for the unexpectedness of the correct
English spelling. I was bemoaning the lack of logic in my native language.

> In German there is the verb "hicksen" which means "to hiccup" so I'm
> especially vulnerable here (the noun is totally different, though,
> "Schluckauf").

Interesting. I'll try and remember that although I'm not sure if I can
remember enough other German to be able to use it ;)

Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: Board Report

[Mark Thomas]

On 13/12/17 09:37, Konstantin Kolinko wrote:
> 2017-11-30 17:21 GMT+03:00 Stefan Bodewig :
>> Hi all
>>
>> current draft is
>> https://wiki.apache.org/gump/Drafts/BoardReports/20171220 - I'll have to
>> submit it in about two weeks.
>>
>> Back when vmgump failed in September I talked about asking projects
>> whether they still see value in Gump but never got my act together. This
>> time I've put it into the report to increase the chance of actually
>> doing it.
> 
> Looks OK.
> I think it would be better to mention the date when hickup happened,
> 
> s/After a hickup the service seems to be good again./After a hickup in
> September 2017 the service seems to be good again./

Nitpick. s/hickup/hiccup/

There is probably a good(ish) reason for this unexpected spelling but I
have no ideas what it is.

Mark

> 
> https://lists.apache.org/thread.html/4b9c718ee5eaa31972b072fb39213d51dc9af84c6c5d4448a9411e17@%3Cgeneral.gump.apache.org%3E
> 
> 
> Best regards,
> Konstantin Kolinko
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
> For additional commands, e-mail: general-h...@gump.apache.org
> 


-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: do we want to keep the vmgump.apache.org hostname?

[Mark Thomas]

On 08/11/2016 17:35, Stefan Bodewig wrote:
> On 2016-11-08, Mark Thomas wrote:
> 
>> On 08/11/2016 16:33, Stefan Bodewig wrote:
> 
>>> the new machine is vmgump-vm3 rather than vmgump. Do we want to keep the
>>> old name as an alias?
> 
>> -0. I don't see a need but I have no objection if someone wants that.
> 
> Same here.
> 
>> on a related issue, I can confirm I have access to the new vm.
> 
> Strange, I don't recall enabling it. Good to know anyway :-)

I get it automatically via my infra karma.

Mark


-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: do we want to keep the vmgump.apache.org hostname?

[Mark Thomas]

On 08/11/2016 16:33, Stefan Bodewig wrote:
> Hi
> 
> the new machine is vmgump-vm3 rather than vmgump. Do we want to keep the
> old name as an alias?

-0. I don't see a need but I have no objection if someone wants that.

on a related issue, I can confirm I have access to the new vm.

Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: vmgump is going to get turned off

[Mark Thomas]

On 07/11/2016 05:23, Stefan Bodewig wrote:
> Hi all
> 
> we've seen the first emails coming from vmgump-vm3 and I've just
> (hopefully) fixed the workspace definition so the nag mails contain URIs
> that point to the new machine.
> 
> As a result the migration seems to be complete and infra is going to
> turn off vmgump.

Nice work.

Mark


-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: Gump on Mac OS X is back -- sort of

[Mark Thomas]

On 30/08/2016 19:45, Sander Temme wrote:
> Dear Community,
> 
> Having been pestered with two e-mails a day about failing Gump cron
> jobs ever since I upgraded the OS on adam.apache.org to Mountain Lion
> (Mac OS X 10.8), I finally found the time this week to put the Gump
> installation back together, and it is now once again running at 6AM
> and 6PM Pacific.
> 
> http://adam.apache.org/gump/
> 
> Somewhat of a moral victory as (per e-mail convo this past February)
> Infra would like to get rid of this old hardware, but never mind.

As long as it is secure and we are using it, I think we should be OK.

Any chance you could create an account for me on that box? It is
sometimes useful to debug failing tests without the 12 hour delay
between test runs.

Cheers,

Mark


> 
> We’re now running on JDK 8 from Oracle, on Python 2.7 and on MySQL
> 5.6 from MacPorts.  It should be pretty straightforward to replicate
> this installation on the Mac Mini Infra offered in February.
> 
> S. (And when did we go from 649 projects to 193?)
> 
> -- san...@temme.net  http://www.temme.net/sander/ PGP FP:
> BCD1 6D2C 8906 C48A 540E  253E 94D3 36A3 6D15 930A
> 
> 
> 


-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: Gump is building stale Checkstyle sources (and other GitHub projects)

[Mark Thomas]

FYI.

I have manually updated openssl-master and checkstyle to the latest source.

Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: svn commit: r1728586 - /gump/live/python/gump/core/update/git.py

[Mark Thomas]

On 05/02/2016 01:58, billbar...@apache.org wrote:
> Author: billbarker
> Date: Fri Feb  5 01:58:25 2016
> New Revision: 1728586
> 
> URL: http://svn.apache.org/viewvc?rev=1728586=rev
> Log:
> revert previous attempt. We can go back to fixing corrupt files the old 
> fashoned way. Thanks to Konstantin for pointing out my stupidity

I'm wondering if the build is playing with line-endings.

I've just forced:
git fetch --all
git reset --hard origin/master

for commons-lang-trunk

I took a look at git.py but my Python fu is pretty poor and I couldn't
see how to get two commands to be executed for getUpdateCommand. Any
pointers?

Cheers,

Mark


> 
> Modified:
> gump/live/python/gump/core/update/git.py
> 
> Modified: gump/live/python/gump/core/update/git.py
> URL: 
> http://svn.apache.org/viewvc/gump/live/python/gump/core/update/git.py?rev=1728586=1728585=1728586=diff
> ==
> --- gump/live/python/gump/core/update/git.py (original)
> +++ gump/live/python/gump/core/update/git.py Fri Feb  5 01:58:25 2016
> @@ -66,7 +66,6 @@ class GitUpdater(ScmUpdater):
>  cmd = Cmd('git', 'update_' + module.getName(), 
>module.getSourceControlStagingDirectory())
>  cmd.addParameter('pull')
> -cmd.addParameter('--commit')
>  maybe_make_quiet(module, cmd)
>  cmd.addParameter(module.getScm().getRootUrl())
>  cmd.addParameter(module.getScm().getBranch())
> 
> 


-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Updating Java

[Mark Thomas]

I'm updating the version of Java that Gump runs with to the latest
Oracle Java 8 release. We may see some strange errors/failures.

Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: BATCH: All dressed up, with nowhere to go...

[Mark Thomas]

On 24/06/2015 01:31, g...@vmgump.apache.org wrote:
 Dear Gumpmeisters,
 
 The following 20 notifys should have been sent
 
 *** G U M P
 [GUMP@vmgump]: Module apache-commons failed

I've removed the broken externals caused by some components (not built
by gump) moving to Git. That should fix things for the next run.

Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: Problem running Apache Gump [vmgump]

[Mark Thomas]

On 05/05/2015 00:00, g...@vmgump.apache.org wrote:
 There is a problem with run 'vmgump' (05052015_01), location : 
 http://vmgump.apache.org/gump/public
 
 The log ought be at:
http://vmgump.apache.org/gump/public/gump_log.txt
 
 The last (up to) 50 lines of the log are :
 - GUMP run on host   : vmgump
 - GUMP run @ : 05 May 2015 00:00:01
 - GUMP run @  UTC: 05 May 2015 00:00:01
 - GUMP run by Python : '2.7.6 (default, Mar 22 2014, 22:59:56) \n[GCC 4.8.2]'
 - GUMP run by Python : '/usr/bin/python'
 - GUMP run by Gump   : 2.0.2-alpha-0003
 - GUMP run on OS : 'posix'
 - GUMP run in env: 
   GUMP_PYTHON - [/usr/bin/python]
   LOGNAME - [gump]
   MAVEN_HOME - [/opt/maven]
   M3_HOME - [/opt/maven3]
   MAILTO - []
   GUMP_HOME - [/srv/gump/public/gump]
   SHELL - [/bin/sh]
   SHLVL - [1]
   LOCAL_ENV - [local-env.sh]
   M2_HOME - [/opt/maven2]
   JAVA_HOME - [/usr/lib/jvm/java-8-oracle]
   HOME - [/home/gump]
   LANG - [en_US.utf8]
   HOST_LOCAL_ENV - [local-env-vmgump.sh]
   HOST_LOCAL_POST_RUN - [local-post-run-vmgump.sh]
   PATH - [/usr/bin:/bin:/opt/maven/bin:/opt/maven2/bin:/opt/gradle/bin]
   HOST_LOCAL_PRE_RUN - [local-pre-run-vmgump.sh]
   GIT_HOME - [/opt/git]
   _ - [/usr/bin/python]
   GRADLE_HOME - [/opt/gradle]
   GUMP_HOST - [vmgump]
   PWD - [/srv/gump/public/gump/cron]
   MVN_PROXY_HOME - [/opt/repoproxy]
   GUMP_WORKSPACE - [/srv/gump/public/gump/metadata/vmgump]
 - GUMP base directory : /srv/gump/public/workspace
 - GUMP base path  : /srv/gump/public/workspace
 - GUMP mail server: localhost
 - GUMP mail port  : 25
 - GUMP mail from  : g...@vmgump.apache.org
 - GUMP mail to: general@gump.apache.org
 - GUMP log is @   : http://vmgump.apache.org/gump/public
 - GUMP log is @   : /srv/gump/public/workspace/log
  - GUMP PYTHONPATH  :  /srv/gump/public/gump/python
 Execute : svn update --non-interactive out.txt 21
 Updating '.':
 svn: E230001: Unable to connect to a repository at URL 
 'https://svn.apache.org/repos/asf/gump/live'
 svn: E230001: Server SSL certificate verification failed: issuer is not 
 trusted
 Process Exit Code : 1

Fixed (hopefully). Fingers crossed for the next run.

Mark


-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: Switching Gump to Java 8

[Mark Thomas]

Sorry this isn't a proper reply - I'm not subscribed to the list so I am
reading the archives.

I'll go ahead and switch vmgump to Java 8.

Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Switching Gump to Java 8

[Mark Thomas]

Folks,

Work on Tomcat 9 has started which requires Java 8 as a minimum. Since
there have been a few stable Java 8 releases now would it be possible to
switch Gump over to use Java 8 rather than Java 7?

I'm assuming it isn't possible to control this on a per project basis.
If that is possible please point me to the docs and I'll configure
tomcat-trunk that way.

Thanks,

Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

JAR update request

[Mark Thomas]

Hi,

Please could the Eclipse JDT jar be updated to version P20140317-1600 as
this is now required by the Tomcat builds (to pick up Java 8 support).

I did try to do this myself but I don't have sudo on vmgump so I
couldn't make the change.

Cheers,

Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: JAR update request

[Mark Thomas]

On 20/03/2014 08:36, Stefan Bodewig wrote:
 On 2014-03-20, Mark Thomas wrote:
 
 Please could the Eclipse JDT jar be updated to version P20140317-1600 as
 this is now required by the Tomcat builds (to pick up Java 8 support).
 
 I would if I knew how to obtain it - I'm not an eclipse user myself, so
 I'd appreciate a download location that doesn't force me to download a
 full Eclipse distribution :-)

Thanks. The direct download link is:

http://download.eclipse.org/eclipse/downloads/drops4/P20140317-1600/ecj-P20140317-1600.jar

Mark


-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Investigating failing Tomcat trunk unit test

[Mark Thomas]

Hi,

I've been unable to re-create the current Tomcat trunk unit test failure
observed by Gump. Therefore, I'd like to request ssh access to vmgump in
order to be able to run the unit test in the same environment, hopefully
recreate the problem and fix it.

Looking at the infrastructure repo, I should have ssh access to vmgump.
However, it looks like this has been lost / disabled at some point. I'd
be grateful if this could be recreated/enabled.

Cheers,

Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: [GUMP@vmgump]: Project jakarta-tomcat-jasper_tc5 (in module jakarta-tomcat-jasper_tc5) failed

[Mark Thomas]

Stefan Bodewig bode...@apache.org wrote:
On 2013-08-20, Mark Thomas wrote:

 On 18/08/2013 00:42, b...@apache.org wrote:

 snip/

 build-only:
 [javac] Compiling 97 source files to
/srv/gump/public/workspace/jakarta-tomcat-jasper_tc5/build/shared/classes
 [javac]
/srv/gump/public/workspace/jakarta-tomcat-jasper_tc5/src/share/org/apache/jasper/compiler/JDTCompiler.java:86:
error: CompilationUnit is not abstract and does not override abstract
method ignoreOptionalProblems() in ICompilationUnit
 [javac] class CompilationUnit implements
ICompilationUnit {
 [javac] ^
 [javac] Note: Some input files use or override a deprecated API.
 [javac] Note: Recompile with -Xlint:deprecation for details.
 [javac] 1 error

 This isn't going to work until the right version the Eclipse JDT
 compiler (ecj-3.7.2.jar) is available in the Eclipse package.

 Is there a way I can make this happen via updating the metadata? I
 didn't see anything obvious.

No, the installed packages, i.e. stuff Gump doesn't build but
provides
as jars, can only be added by Gump PMC members.

So far I held back as I expected you to tell me that you wanted to drop
the Tomcat 5 builds :-)

Dropping the Tomcat 5 builds is fine. I assumed it was still there because 
something else you wanted to keep depended on it.

Mark



-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: [GUMP@vmgump]: Project tomcat-tc7.0.x-validate (in module tomcat-7.0.x) failed

[Mark Thomas]

On 20/08/2013 00:50, Bill Barker wrote:

snip/

 validate:
 [mkdir] Created dir: 
 /srv/gump/public/workspace/tomcat-7.0.x/output/res/checkstyle
 [checkstyle] Running Checkstyle 5.7-SNAPSHOT on 2388 files
 [checkstyle] 
 /srv/gump/public/workspace/tomcat-7.0.x/modules/jdbc-pool/src/test/java/org/apache/tomcat/jdbc/test/DefaultTestCase.java:22:1:
  Import from illegal package - junit.framework.TestCase.
 [checkstyle] 
 /srv/gump/public/workspace/tomcat-7.0.x/modules/jdbc-pool/src/test/java/org/apache/tomcat/jdbc/test/TestAsyncQueue.java:24:1:
  Import from illegal package - junit.framework.TestCase.
 [checkstyle] 
 /srv/gump/public/workspace/tomcat-7.0.x/modules/jdbc-pool/src/test/java/org/apache/tomcat/jdbc/test/TestSizePreservation.java:22:1:
  Import from illegal package - junit.framework.TestCase.
 
 BUILD FAILED
 /srv/gump/public/workspace/tomcat-7.0.x/build.xml:451: Got 3 errors and 0 
 warnings.

Gump doesn't appear to be using the latest source code for this build.
As far as I can tell, the project is set up so it should use the latest
source from svn. What am I missing?

Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org

Re: Your Gump Build(s)

[Mark Thomas]

On 24/06/2013 14:20, Stefan Bodewig wrote:
 Dear Community
 
 Apache Gump builds some of your projects and it is quite possible you
 don't know or have by now forgotten about it.
 
 More than half a year ago a technical problem has forced us to turn off
 emails on build failures as we would have been sending out lots of false
 alarms.
 
 Before we re-enable emails we'd like to know whether you are still
 interested in the service Gump provides, so please tell us. :-)

Yes please!

As an aside, there were (and probably still are) a number of projects
with dependencies on very old (and no longer supported) Tomcat versions.
It would be good to get those cleaned up. Finding the time to do that
has been on my TODO list for a while.

Mark

-
To unsubscribe, e-mail: general-unsubscr...@gump.apache.org
For additional commands, e-mail: general-h...@gump.apache.org