On Tue 26 Aug 2003 14:22, Abe Timmerman <[EMAIL PROTECTED]> wrote: > > New question: How do I/we deal with starting multiple smokes on the same > > machine with the same source tree, but with different compilers? > > > > How do I control the cron process to e.g. run continuesly > > > > +-> smoke-5.8.x-cc -> smoke-5.9.x-cc -> smoke-5.8.x-gcc -> smoke-5.9.x-gcc > > -+ > > > > +-------------------------------------<------------------------------------ > >-+ > > > > No start time, no end time, but just like an endless cycle > > shell script?
That would do for the endless cycle, like --8<--- /blah/smoke/loop.sh p58.sh p59.sh at now </blah/smoke/loop.sh -->8--- But is there a way to *nicely* tell smoke about the things that come to change the compiler? Or would that just be --8<--- /blah/smoke/loop.sh p58.sh p59.sh env PATH=/my/path/to/gcc CC=gcc p58.sh env PATH=/my/path/to/gcc CC=gcc p59.sh at now </blah/smoke/loop.sh -->8--- Which will not work on HP-UX, because the compiler for 64bit is not the same as the compiler for 32bit. Now *I* caught that in my Policy.sh, but what should T::S know about this? Untill now I was running mktest and mktest-gcc in sequence, but I'm in the process of moving towards T::S as you know. -- H.Merijn Brand Amsterdam Perl Mongers (http://amsterdam.pm.org/) using perl-5.6.1, 5.8.0, & 5.9.x, and 806 on HP-UX 10.20 & 11.00, 11i, AIX 4.3, SuSE 8.2, and Win2k. http://www.cmve.net/~merijn/ http://archives.develooper.com/[EMAIL PROTECTED]/ [EMAIL PROTECTED] send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
