perl.daily-build...Smoking from GIT by H.Merijn Brand- June 6, 2008 With git eminent after the release of perl-5.8.9, we need to discuss thebest way to continue smoking blead (and the other tracks) from git.When perforce is closed, and the move to git is final, we will not haveperforce change numbers anymore, and we do not know if rsync will stillbe available and if it will come with a .patch file.The .patch file was used not only for reporting exactly what version ofperl was used, but also to determine if a smoke is really wanted (usingsmartsmoke) and to..http://www.nntp.perl.org/group/perl.daily-build/2008/06/msg809.html RE: smokecurrent.log vs the report by Steve Hay- June 4, 2008 Dominic Dunlop wrote:> On 2008-06-03, at 23:14, H.Merijn Brand wrote:> >> On Tue, 03 Jun 2008 18:29:46 +0200, Dominic Dunlop>> <shouldbedomomac.com> wrote:>> >>> On 2008-06-03, at 15:17, H.Merijn Brand wrote:>>> >>>> I think the &39;&39;s should be either &39;F&39; or &39;X&39; here. No idea as yet>>>> why they are &39;&39;>>> >>> >>> You can specify a maximum wallclock time for a smoke test....http://www.nntp.perl.org/group/perl.daily-build/2008/06/msg808.html Re: smokecurrent.log vs the report by Dominic Dunlop- June 3, 2008 On 2008–06–03, at 23:14, H.Merijn Brand wrote:> On Tue, 03 Jun 2008 18:29:46 +0200, Dominic Dunlop> <shouldbedomomac.com> wrote:>>> On 2008–06–03, at 15:17, H.Merijn Brand wrote:>>>>> I think the &39;&39;s should be either &39;F&39; or &39;X&39; here. No idea as yet >>> why>>> they are &39;&39;>>>>>> You can specify a maximum wallclock time for a smoke test. &39;&39; is the>> reported status...http://www.nntp.perl.org/group/perl.daily-build/2008/06/msg807.html PATCH Re: Error with sync via ftp removing smoke files by Bram- June 3, 2008 Citeren Bram <daily-buildperl.wizbit.be>:> Quoting Abe Timmerman <abeltjetest-smoke.org>:>>> Bram wrote:>>> Ran into a problem setting up smoking on one machine...>>>>>> Configured the smoke to download sources via ftp.>>> The machine is behind a firewall which doesn&39;t seem to be >>> configured properly for ftp.>>> It was able to connect but all other operations timed out.>>>>>> When I...http://www.nntp.perl.org/group/perl.daily-build/2008/06/msg806.html Re: smokecurrent.log vs the report by H.Merijn Brand- June 3, 2008 On Tue, 03 Jun 2008 18:29:46 +0200, Dominic Dunlop<shouldbedomomac.com> wrote:> On 2008–06–03, at 15:17, H.Merijn Brand wrote:> > > I think the &39;&39;s should be either &39;F&39; or &39;X&39; here. No idea as yet why> > they are &39;&39;> > > You can specify a maximum wallclock time for a smoke test. &39;&39; is the > reported status for configurations that did not finish or did not get > run because the smoke was still running when the...http://www.nntp.perl.org/group/perl.daily-build/2008/06/msg805.html Re: smokecurrent.log vs the report by Bram- June 3, 2008 Citeren Dominic Dunlop <shouldbedomomac.com>:> On 2008&8211;06&8211;03, at 15:17, H.Merijn Brand wrote:>>> I think the &39;&39;s should be either &39;F&39; or &39;X&39; here. No idea as yet why>> they are &39;&39;>>> You can specify a maximum wallclock time for a smoke test. &39;&39; is the> reported status for configurations that did not finish or did not get> run because the smoke was still running when the guillotine descended.> Is that what..http://www.nntp.perl.org/group/perl.daily-build/2008/06/msg804.html Re: smokecurrent.log vs the report by Dominic Dunlop- June 3, 2008 On 2008–06–03, at 15:17, H.Merijn Brand wrote:> I think the &39;&39;s should be either &39;F&39; or &39;X&39; here. No idea as yet why> they are &39;&39;You can specify a maximum wallclock time for a smoke test. &39;&39; is the reported status for configurations that did not finish or did not get run because the smoke was still running when the guillotine descended. Is that what happened during the test in questionSee "killtime" on configsmoke.3 man page.--...http://www.nntp.perl.org/group/perl.daily-build/2008/06/msg803.html Re: smokecurrent.log vs the report by H.Merijn Brand- June 3, 2008 On Tue, 03 Jun 2008 14:59:12 +0200, Bram <daily-buildperl.wizbit.be>wrote:> smokecurrent.log ends with:> > Configuration: -Dcc=optgccbin_ccachegcc430 -Ud_getprior > -Ud_setprior -Ud_setresgid -Ud_setresuid -Dusedevel -Duse64bitint > -DDEBUGGING> ------------------------------------------------------------------------------> make distclean ...> Copy Policy.sh ...> Configure ....Configure -des -Dcc=optgccbin_ccachegcc430 > -Ud_getprior -Ud_setprior...http://www.nntp.perl.org/group/perl.daily-build/2008/06/msg802.html smokecurrent.log vs the report by Bram- June 3, 2008 smokecurrent.log ends with:Configuration: -Dcc=optgccbin_ccachegcc430 -Ud_getprior -Ud_setprior -Ud_setresgid -Ud_setresuid -Dusedevel -Duse64bitint -DDEBUGGING------------------------------------------------------------------------------make distclean ...Copy Policy.sh ...Configure ....Configure -des -Dcc=optgccbin_ccachegcc430 -Ud_getprior -Ud_setprior -Ud_setresgid -Ud_setresuid -Dusedevel -Duse64bitint -DDEBUGGINGgetconf: Unrecognized variable GNU_LIBPTHREAD_VERSION&39;make ...make .http://www.nntp.perl.org/group/perl.daily-build/2008/06/msg801.html |