RE: Fwd: Switching incubator.apache.org to svnpubsub?
> -Original Message- > From: Mark Thomas [mailto:ma...@apache.org] > Sent: Thursday, 4 February 2010 2:46 AM > To: Tomcat Developers List > Subject: Re: Fwd: Switching incubator.apache.org to svnpubsub? > > On 03/02/2010 13:21, Yoav Shapira wrote: > > Please see Justin's proposal below for the Incubator. (From a > > general, public list.) > > > > I think it'd be great for Tomcat to do the same. Your thoughts / > votes? > > Generally +1. Need to think about how we handle the docs (including > javadocs). Is there a better way than just checking the whole lot into > the repo? How are you handling the docs currently? Docs, including javadocs can be built using Buildbot and deployed, this way there is still the one hour delay from commit to being live, but at least generated documentation doesn't get into svn. Gav... > > Mark > > > > > > Yoav > > > > > > -- Forwarded message -- > > From: Justin Erenkrantz > > Date: Wed, Feb 3, 2010 at 1:57 AM > > Subject: Switching incubator.apache.org to svnpubsub? > > To: gene...@incubator.apache.org > > > > > > Hi general@, > > > > I'd like to suggest switching incubator.apache.org over to svnpubsub. > > (We can do so by filing a JIRA like INFRA-2349: > > http://issues.apache.org/jira/browse/INFRA-2349) > > > > This would mean that any commits made to the site-publish tree would > > automatically be deployed to the site. No more delays, no more SSH > > and SVN up fun. Yay. This does mean you trade off the fact that you > > can't delay anything - but, in general, I think that's fine for the > > incubator site and would substantially lower the barrier of entry to > > folks working on the Incubator site. Often times, people's first > > experience with the ASF is through the podlings, so I think it would > > be nice if we could make it a bit easier to publish the incubator.a.o > > site. > > > > What do folks think? -- justin > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > > For additional commands, e-mail: dev-h...@tomcat.apache.org > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
FW: buildbot failure in ASF Buildbot on tomcat-trunk
-Original Message- From: Gav... [mailto:ga...@16degrees.com.au] Sent: Sunday, 7 February 2010 10:28 AM To: 'Tomcat Developers List' Cc: bui...@apache.org Subject: RE: buildbot failure in ASF Buildbot on tomcat-trunk > -Original Message- > From: Mark Thomas [mailto:ma...@apache.org] > Sent: Sunday, 7 February 2010 8:27 AM > To: bui...@apache.org > Cc: Tomcat Developers List > Subject: Fwd: buildbot failure in ASF Buildbot on tomcat-trunk > > These are getting rather tiresome. Could you please allocate sufficient > heap to the build process so it can complete. I take it you read the email I sent to your private list explaining why these notifications are coming to the dev list? Current memory options are set at: 'ANT_OPTS': '-Xms128m -Xmx512m -XX:MaxPermSize=128m' Could you explain why there is a need to have more than 512MB allocated to complete an 'ant release' -- what are the settings that is usual for this step? In the meantime, I'll increase to 128/768/256 and see if that helps. I'm glad that tiresome has done the trick and somebody finally responded, now perhaps we can get back on track and get these buildbot configurations finished. Gav... > > Cheers, > > Mark > > Original Message > Subject: buildbot failure in ASF Buildbot on tomcat-trunk > Date: Sat, 06 Feb 2010 22:53:21 + > From: build...@apache.org > Reply-To: Tomcat Developers List > To: dev@tomcat.apache.org > > The Buildbot has detected a failed build of tomcat-trunk on ASF > Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/56 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: bb-vm_ubuntu > > Build Reason: > Build Source Stamp: [branch tomcat/trunk] 907317 > Blamelist: markt > > BUILD FAILED: failed compile_3 > > sincerely, > -The ASF Buildbot > > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
RE: buildbot failure in ASF Buildbot on tomcat-trunk
Well I have no clue, as mentioned I have upped the allocation to: 'ANT_OPTS': '-Xms128m -Xmx768m -XX:MaxPermSize=256m Does anyone else have problems running 'ant release' ? In the meantime, I'll alter the buildbot config to only send notifications when state of the build has changed from pass to fail, fail to pass. Gav... > -Original Message- > From: build...@apache.org [mailto:build...@apache.org] > Sent: Sunday, 7 February 2010 11:25 AM > To: dev@tomcat.apache.org > Subject: buildbot failure in ASF Buildbot on tomcat-trunk > > The Buildbot has detected a failed build of tomcat-trunk on ASF > Buildbot. > Full details are available at: > http://ci.apache.org/builders/tomcat-trunk/builds/58 > > Buildbot URL: http://ci.apache.org/ > > Buildslave for this Build: bb-vm_ubuntu > > Build Reason: forced: by IRC user on channel #asftest: > testing increase of mem to ant_opts > Build Source Stamp: HEAD > Blamelist: > > BUILD FAILED: failed compile_3 > > sincerely, > -The ASF Buildbot > > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
RE: buildbot failure in ASF Buildbot on tomcat-trunk
Also, I'll be on the #tomcat irc if anyone wants to go through this with me. Gav... > -Original Message- > From: Gav... [mailto:ga...@16degrees.com.au] > Sent: Sunday, 7 February 2010 10:44 AM > To: 'Tomcat Developers List' > Subject: RE: buildbot failure in ASF Buildbot on tomcat-trunk > > Well I have no clue, > > as mentioned I have upped the allocation to: > > 'ANT_OPTS': '-Xms128m -Xmx768m -XX:MaxPermSize=256m > > Does anyone else have problems running 'ant release' ? > > In the meantime, I'll alter the buildbot config to > only send notifications when state of the build has > changed from pass to fail, fail to pass. > > Gav... > > > > -Original Message- > > From: build...@apache.org [mailto:build...@apache.org] > > Sent: Sunday, 7 February 2010 11:25 AM > > To: dev@tomcat.apache.org > > Subject: buildbot failure in ASF Buildbot on tomcat-trunk > > > > The Buildbot has detected a failed build of tomcat-trunk on ASF > > Buildbot. > > Full details are available at: > > http://ci.apache.org/builders/tomcat-trunk/builds/58 > > > > Buildbot URL: http://ci.apache.org/ > > > > Buildslave for this Build: bb-vm_ubuntu > > > > Build Reason: forced: by IRC user on channel #asftest: > > testing increase of mem to ant_opts > > Build Source Stamp: HEAD > > Blamelist: > > > > BUILD FAILED: failed compile_3 > > > > sincerely, > > -The ASF Buildbot > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > > For additional commands, e-mail: dev-h...@tomcat.apache.org > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
RE: buildbot failure in ASF Buildbot on tomcat-trunk
> -Original Message- > From: Konstantin Kolinko [mailto:knst.koli...@gmail.com] > Sent: Sunday, 7 February 2010 12:22 PM > To: Tomcat Developers List > Subject: Re: buildbot failure in ASF Buildbot on tomcat-trunk > > 2010/2/7 Gav... : > >> > >> as mentioned I have upped the allocation to: > >> > >> 'ANT_OPTS': '-Xms128m -Xmx768m -XX:MaxPermSize=256m > >> > > Hi, Gavin! > > 1. Looking at stdout for compile, compile_1, compile_2, compile_3 in > http://ci.apache.org/builders/tomcat-trunk/builds/57 > > I see that ANT_OPTS setting is mentioned only in compile_1, but not in > the three other ones. yeah, I'm a dumbass, should have set it on the entire builder, not just the first step, fixed now and the build now passes, thanks! > > > 2. In the recent updates to the trunk build files Mark not only merged > our three build files into build.xml, but also configured the > dependencies. To build TC trunk release now it is sufficient to call > "ant release" and it will perform all the steps: download, > compilation, compilation of extra, bundling the release. Ah, excellent, I didn't dig into the changes enough, I've now wiped the previous steps, thanks again. Right then, we can move on to the next stages. I know I still need to add JDK 5 for Tomcat 6 'ant download' to complete. There was mention of making the produced builds available. Can you let me know what builds you want making available and I'll get on with it? Probably the contents of output/release ? or just the contents of output/release/v7.0.0-dev/src/ ? What else? Thanks Gav... > > It can be seen from compile_3 output: it does download, compilation, > and then fails from OutOfMemory. > > Thus the configuration for building the trunk can be simplified. > > The build procedure for Tomcat 6 remains the same. > > > > Thank you for your work on this. > > Best regards, > Konstantin Kolinko > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
RE: buildbot failure in ASF Buildbot on tomcat-trunk
> -Original Message- > From: Mark Thomas [mailto:ma...@apache.org] > Sent: Tuesday, 9 February 2010 8:27 PM > To: Tomcat Developers List > Cc: bui...@apache.org > Subject: Re: buildbot failure in ASF Buildbot on tomcat-trunk > > On 09/02/2010 10:25, build...@apache.org wrote: > > The Buildbot has detected a new failure of tomcat-trunk on ASF > Buildbot. > > Full details are available at: > > http://ci.apache.org/builders/tomcat-trunk/builds/83 > > > > Buildbot URL: http://ci.apache.org/ > > > > Buildslave for this Build: bb-vm_ubuntu > > > > Build Reason: > > Build Source Stamp: [branch tomcat/trunk] 907983 > > Blamelist: markt > > > > BUILD FAILED: failed compile > > The Eclipse download takes forever which seems to be the root cause of > a > number of these failures. Could the build property "jdt.home" be set to > somewhere that isn't deleted on every ci build? That should speed up > the > build process considerably - as well as not downloading a 25MB file > from > archive.eclipse.org every time we build. Actually, I haven’t set that property at all that I know of. In Buildbot it can be added as a property at build time so it's no problem. Shall I go ahead and do that? What value should it be, empty? Gav... > > Mark > - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
RE: buildbot failure in ASF Buildbot on tomcat-trunk
> -Original Message- > From: Konstantin Kolinko [mailto:knst.koli...@gmail.com] > Sent: Wednesday, 10 February 2010 10:36 PM > To: Tomcat Developers List > Cc: bui...@apache.org > Subject: Re: buildbot failure in ASF Buildbot on tomcat-trunk > > 2010/2/10 Gav... : > > > > > >> -Original Message- > >> From: Mark Thomas [mailto:ma...@apache.org] > >> Sent: Tuesday, 9 February 2010 8:27 PM > >> To: Tomcat Developers List > >> Cc: bui...@apache.org > >> Subject: Re: buildbot failure in ASF Buildbot on tomcat-trunk > >> > >> On 09/02/2010 10:25, build...@apache.org wrote: > >> > The Buildbot has detected a new failure of tomcat-trunk on ASF > >> Buildbot. > >> > Full details are available at: > >> > http://ci.apache.org/builders/tomcat-trunk/builds/83 > >> > > >> > Buildbot URL: http://ci.apache.org/ > >> > > >> > Buildslave for this Build: bb-vm_ubuntu > >> > > >> > Build Reason: > >> > Build Source Stamp: [branch tomcat/trunk] 907983 > >> > Blamelist: markt > >> > > >> > BUILD FAILED: failed compile > >> > >> The Eclipse download takes forever which seems to be the root cause > of > >> a > >> number of these failures. Could the build property "jdt.home" be set > to > >> somewhere that isn't deleted on every ci build? That should speed up > >> the > >> build process considerably - as well as not downloading a 25MB file > >> from > >> archive.eclipse.org every time we build. > > > > Actually, I havent set that property at all that I know of. > > In Buildbot it can be added as a property at build time so it's no > problem. > > > > Shall I go ahead and do that? > > > > What value should it be, empty? > > > > Gav... > > > > Not jdt.home, but base.path I think. > > The "base.path" property points to a location, where all dependent > libraries are downloaded from the net. > > The default value of it is > base.path=/usr/share/java > and as I see from stdio output from buildbot, there it is set to > /home/buildslave3/slave3/tomcat-trunk/build/basepath/ > > The problem is that all those dependencies are deleted before each run > and are redownloaded, which wastes time and, with a 40 MB download > from eclipse.org, resulted in intermittent failures. > > Can we avoid deleting those files between runs? > > > In the meanwhile, yesterday I changed dependencies in tomcat-trunk, > and now we are downloading a 1.6 MB file instead of 40 MB one. So, the > problem will be less noticeable for trunk now, but will still present > for "tomcat-6-trunk", where this change is not implemented yet. > > > The "tomcat-6-trunk" buildbot apparently has the same value of > "base.path" as the "tomcat-trunk" one. That is, it reuses libraries > downloaded by "tomcat-trunk" on its previous run. Thus it was more > rare to see errors coming from it. ah, ok thanks for the explanations. With builds, I prefer to keep the rest of the file system clean wherever possible, so over-riding base path was my solution. I can see that having it in the build dir can cause problems so I've just moved it one level above the main build dir so it doesnt get clobbered each run, but is still within the tomcat-trunk and tomcat-6-trunk directory structure. Thanks Gav... > > > Best regards, > Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: buildbot failure in on tomcat-trunk
Wierd, it passed on the same machine only 2 hours earlier:-- https://ci.apache.org/builders/tomcat-trunk/builds/3378 as an FYI gmcdonald@silvanus:~$ /home/buildslave/slave/tools/ant/latest/bin/ant -version Apache Ant(TM) version 1.10.3 compiled on March 24 2018 gmcdonald@silvanus:~$ ant -version Apache Ant(TM) version 1.9.6 compiled on July 8 2015 Your build points to ANT_HOME=/home/buildslave/slave/tools/ant/current but should be ANT_HOME=/home/buildslave/slave/tools/ant/latest If you change that in your config file then it might pick up the 1.10 version better Which doesnt explain how it has been passing all this time unless you have just added changes today that are Ant 1.9 incompatible. https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/tomcat.conf HTH Gav... On Thu, Jun 21, 2018 at 12:46 PM, Emmanuel Bourg wrote: > Le 21/06/2018 à 13:01, build...@apache.org a écrit : > > The Buildbot has detected a new failure on builder tomcat-trunk while > building . Full details are available at: > > https://ci.apache.org/builders/tomcat-trunk/builds/3379 > > It looks like Ant needs an upgrade on the builders. Is there a way to > configure the version of Ant used to build Tomcat, or should I open an > Infra ticket to get it updated? > > Emmanuel Bourg > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > > -- Gav...
Re: buildbot failure in on tomcat-trunk
I'll add 1.9.11 and ensure previous version remains also. Gav... On Thu, Jun 21, 2018 at 1:31 PM, Mark Thomas wrote: > On 21/06/18 13:14, Gav wrote: > > Wierd, it passed on the same machine only 2 hours earlier:-- > > > > https://ci.apache.org/builders/tomcat-trunk/builds/3378 > > > > as an FYI > > > > gmcdonald@silvanus:~$ /home/buildslave/slave/tools/ant/latest/bin/ant > > -version > > Apache Ant(TM) version 1.10.3 compiled on March 24 2018 > > gmcdonald@silvanus:~$ ant -version > > Apache Ant(TM) version 1.9.6 compiled on July 8 2015 > > > > Your build points to > > > > ANT_HOME=/home/buildslave/slave/tools/ant/current > > > > but should be > > > > ANT_HOME=/home/buildslave/slave/tools/ant/latest > > Hmm. > > We are going to need to be careful with this. The older Tomcat branches > need to build on old Java versions so we need to look at Ant / Java > version compatibility as well. > > /me heads off to check the Ant docs for minimum Java versions > > Mark > > ----- > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > > -- Gav...
Re: buildbot failure in on tomcat-trunk
done ;) On Thu, Jun 21, 2018 at 4:37 PM, Mark Thomas wrote: > On 21 June 2018 15:31:52 BST, Emmanuel Bourg wrote: > >Le 21/06/2018 à 16:25, Rémy Maucherat a écrit : > > > >> Is the Ant of the build platform upgradeable already ? > > > >I thought so [1] but it seems there is still an issue. > > > >Emmanuel Bourg > > > >[1] https://issues.apache.org/jira/browse/INFRA-16673 > > > >- > >To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > >For additional commands, e-mail: dev-h...@tomcat.apache.org > > I haven't switched the building script over to the updated Ant 1.9 install > yet. I'll be able to do that in an hour or so unless someone beats me to it. > > Mark > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > > -- Gav...
Files to exclude from buildbot rat tests
HI All, markt has added some exclusions recently that are preventing a successful rat run on buildbot. (More accurately the xml file produced is malformed due to inclusions of bad headers) Here are what I can see as the remaining invalid files; adding these to the rat-excludes file should enable a succesful run for tomcat 7,8 and trunk (9). tomcat-7-trunk - output/dist/src/res/side_left.bmp tomcat-7-trunk - output/dist/src/webapps/docs/tribes/leader-election-message-arrives.dia tomcat-trunk - output/dist/side_left.bmp HTH Gav...
Re: Files to exclude from buildbot rat tests
Hi, On Tue, Feb 16, 2016 at 8:15 AM, Mark Thomas wrote: > On 15/02/2016 08:04, Gav wrote: > > HI All, > > > > markt has added some exclusions recently that are preventing a successful > > rat run on buildbot. > > Huh? You told me it was failing and asked me to exclude some files. > My sentence was constructed really bad there - I meant you added some exclusions of files that were preventing a successful run, not that your exclusions caused it. > > > (More accurately the xml file produced is malformed due to inclusions of > > bad headers) > > > > Here are what I can see as the remaining invalid files; adding these to > the > > rat-excludes file should enable a succesful run for tomcat 7,8 and trunk > > (9). > > > > > > tomcat-7-trunk - output/dist/src/res/side_left.bmp > > Added **/*.bmp > > > tomcat-7-trunk - > > output/dist/src/webapps/docs/tribes/leader-election-message-arrives.dia > > Added **/*.dia > > > tomcat-trunk - output/dist/side_left.bmp > > Already excluded but I extended to to **/*.bmp > > > Great thanks. Gav... > Mark > >
