> -----Original Message----- > From: Scott Wilson [mailto:[email protected]] > Sent: Monday, 25 January 2010 7:25 PM > To: [email protected] > Subject: Re: Testing on Buildbot > > Doh! Sorry Gav I was meaning to reply, honest!!
No problem, we are all busy, just didnt want the buildbot config to languish, so thought getting the notifications coming here would be a good start. > > Probably best to raise issues against each of these problems and work > through them until we have a clean report. Ok, thanks, done. > I know how to fix some of > them. Great! > > On publishing, I'm not sure at which point we want to actually call > the publish target as we haven't got a release yet. Yeah, I wasnt sure whether to run that test directly or not, but I see no reason not to, I was assuming publish-local was specifically created for testing prior to actual site publish/deploy, but could be wrong. Cheers Gav... > > S > > On 25 Jan 2010, at 07:47, Gav... wrote: > > > With no replies, the buildbot config now sends failure notices to > > this list. > > > > Gav... > > > > > >> -----Original Message----- > >> From: Gav... [mailto:[email protected]] > >> Sent: Monday, 18 January 2010 8:58 PM > >> To: [email protected] > >> Subject: Testing on Buildbot > >> > >> Hi Wooksters (tm), > >> > >> (Apologies, this email ended up quite long, please take the time to > >> read if > >> you can) > >> > >> As you may know, I have had the ASF Buildbot in conjunction with > RAT, > >> test > >> the license headers of the source files. Current tests show 133 > files > >> without the ASL v2.0 license. Some of these could be false > positives, > >> so to > >> make these tests more accurate, a file with a list of exclusions > >> could > >> be > >> added to Wookie svn so that Buildbot can use it. I'll send a patch > to > >> your > >> Jira shortly which makes a start that you devs can then tweak over > >> time. > >> > >> The main reason for this post however is that I thought it might be > >> useful > >> to extend the Wookie config at Buildbot to perform some other tests. > >> Having > >> looked at the build files, I have made a best guess at what you > would > >> like > >> testing, and those are: > >> > >> 'ant' , > >> 'ant compile-test' , > >> 'ant jar' , > >> 'ant publish-local' . > >> > >> Please let me know if you need any tests altering, deleting or > adding > >> to > >> that list. > >> > >> The initial (manually forced) build after adding those tests looks > >> promising, but there are some things I'd like to note straight away. > >> (When > >> notifications for failed tests come to this list I won't need to > >> point > >> them > >> out :)) > >> > >> 'ant' > >> ----- > >> > >> Test passes with warnings: > >> > >> [javac] > >> /home/buildslave2/slave2/wookie- > >> trunk/build/src/org/apache/wookie/util/HashG > >> enerator.java:26: warning: sun.misc.BASE64Encoder is Sun proprietary > >> API and > >> may be removed in a future release > >> > >> [javac] > >> /home/buildslave2/slave2/wookie- > >> trunk/build/src/org/apache/wookie/util/HashG > >> enerator.java:74: warning: sun.misc.BASE64Encoder is Sun proprietary > >> API and > >> may be removed in a future release > >> > >> In the stdio output I also get: > >> > >> [ivy:resolve] :: resolving dependencies :: > >> org.apache.incubator#wookie-server;[email protected] > >> > >> No clue if that looks ok or not?? > >> > >> [ivy:resolve] commons-email#commons-email;1.1 is relocated to > >> org.apache.commons#commons-email;1.1. Please update your > >> dependencies. > >> > >> What needs doing there? > >> > >> > >> > >> 'ant compile-test' > >> ------------------ > >> > >> Test passes with warnings: > >> > >> [javac] > >> /home/buildslave2/slave2/wookie-trunk/build/src- > >> tests/org/apache/wookie/test > >> s/ContentTypeUtilsTest.java:56: warning: unmappable character for > >> encoding > >> UTF8 > >> > >> Stdio output for that warning is: > >> > >> [javac] > >> /home/buildslave2/slave2/wookie-trunk/build/src- > >> tests/org/apache/wookie/test > >> s/ContentTypeUtilsTest.java:56: warning: unmappable character for > >> encoding > >> UTF8 > >> [javac] > >> assertFalse(ContentTypeUtils.isSupportedImageType("test.p�g")); > >> > >> > >> > >> 'ant jar' > >> --------- > >> > >> Passes without errors or warnings. > >> > >> However the resultant jar is called 'wookie.jar' where I guess we > >> should > >> start calling it 'wookie-$major.$minor-incubating.jar' > >> > >> > >> > >> 'ant publish-local' > >> ------------------- > >> > >> This test fails: > >> > >> BUILD FAILED > >> /home/buildslave2/slave2/wookie-trunk/build/ant/ivy-java- > >> common.xml:135: > >> impossible to publish artifacts for > >> org.apache.incubator#wookie-server;[email protected]: > >> java.lang.IllegalArgumentException: unknown resolver local > >> > >> > >> Any clue please on what I should be doing here, or should I not be > >> calling > >> this target directly? > >> > >> Lastly, Buildbot can send notifications via email of failed builds, > >> shall I > >> enable that feature for test results to come to this list? (Note: > >> Only > >> pass > >> to fail and fail to pass will trigger an email, repeated > >> passes/failures > >> will be ignored.) > >> > >> Also there is an irc bot available called wookie-bot I have on a > test > >> channel for triggering builds manually, and other goodies. I note > >> Wookie > >> does not currently use an irc channel. I will leave it on the test > >> channel > >> for now (email me if you want to know where it is so you can play > >> with > >> it). > >> Should you decide to open a #wookie channel, let me know and I'll > >> transfer > >> the wookie-bot there, or let me know if I should disable the bot. > >> > >> Thanks for reading. > >> > >> Gav... > >> > > > > > >
