On Mon, Mar 07, 2005 at 09:54:36AM +0100, Leopold Toetsch wrote:
> It would be very useful if tinderboxen could be revived.
>
> Thanks,
> leo
>
Until something better comes along I have installed tinderbox2
on a uml machine I have. Feel free to point any available tinderclients
at it.
URL - http://
On Mon, Mar 07, 2005 at 09:54:36AM +0100, Leopold Toetsch wrote:
> It would be very useful if tinderboxen could be revived.
>
> Thanks,
> leo
>
Do we need a separate tinderbox, or do you think it might be helpful to
integrate parrot somehow into the current perl smoke re
It would be very useful if tinderboxen could be revived.
Thanks,
leo
I checked, Zach was busy with "real life" and hadn't had time to
get back to this.
Tinderbox is a hacky PITA, imho, (although it does get the job done) and
I'd love to see an alternate and cleaner implementation. (Especially
one that keeps 100% of data inside a database.)
I
At 12:01 AM +0200 10/10/04, Jens Rieks wrote:
Hi,
does anyone know what happend with http://tinderbox.perl.org?
It is offline for quite some time now :-(
It died as part of the meltdown of onion a while back. It's on the
list 'o things to get back, but it hasn't gotten there yet. I'll go
nudge an
Hi,
does anyone know what happend with http://tinderbox.perl.org?
It is offline for quite some time now :-(
jens
# New Ticket Created by Will Coleda
# Please include the string: [perl #31158]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=31158 >
# New Ticket Created by Will Coleda
# Please include the string: [perl #31157]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=31157 >
"Add the above to tinderbox"
>From the TODO file
> >about to cvs checkout parrot:
> >/home/perlcvs: no such repository
>
> Ah, that's finally gone away. The repository path is /cvs/publoc.
> What you're using's very old, though there was a temporary symlink in
> for a while.
It's been gone for months and months.
And you mean /cvs/public.
At 4:31 PM -0500 3/30/04, Abhijit A. Mahabal wrote:
Tinderbox "aniani" is not working with the latest copy. I checked the
other boxes and they seem fine.
Part of the log:
==
about to cvs checkout parrot:
/home/perlcvs: no such repository
Ah, that's finally
Tinderbox "aniani" is not working with the latest copy. I checked the
other boxes and they seem fine.
Part of the log:
==
about to cvs checkout parrot:
/home/perlcvs: no such repository
cvs checkout: authorization failed: server cvs.perl.org rejected acces
OTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Sunday, March 28, 2004 6:05 AM
> To: Perl6 Internals
> Subject: aix tinderbox failure
>
>
> Hi,
>
> currently the aix tinderbox is failing. It chokes on
> bufstart/buflen which were hacky accessors to PMC data and
Juergen Boemmels <[EMAIL PROTECTED]> wrote:
> currently the aix tinderbox is failing. It chokes on bufstart/buflen
Thanks, applied.
leo
Hi,
currently the aix tinderbox is failing. It chokes on bufstart/buflen
which were hacky accessors to PMC data and were removed recently. I
think changing jit_debug_xcoff.c would remove at last this error. Can
someone on AIX check this ?
bö
Index: src/jit_debug_xcoff.c
On Fri, 19 Sep 2003, Nicholas Clark wrote:
> On Fri, Sep 19, 2003 at 02:24:12PM -0400, Dan Sugalski wrote:
> > Looking at my install here, I see I've got gcc 2.95, 3.0, 3.2, and 3.3
> > installed, with 3.3 being the default gcc. Is it worth running tinders
> > with different versions of gcc, or
On Fri, Sep 19, 2003 at 02:24:12PM -0400, Dan Sugalski wrote:
> Looking at my install here, I see I've got gcc 2.95, 3.0, 3.2, and 3.3
> installed, with 3.3 being the default gcc. Is it worth running tinders
> with different versions of gcc, or shall I just leave things as-is and
> assume earlie
Looking at my install here, I see I've got gcc 2.95, 3.0, 3.2, and 3.3
installed, with 3.3 being the default gcc. Is it worth running tinders
with different versions of gcc, or shall I just leave things as-is and
assume earlier versions can manage to sort themselves out?
nt me at them (and how to get the
> appropriate accounts, etc)
>
> --Josh
>
> At 14:29 on 03/10/2003 PST, Ask Bjoern Hansen <[EMAIL PROTECTED]> wrote:
>
> >
> > The tinderbox is all in flames.
> >
> > http://xrl.us/dxm (Link to tinderbox.perl.org)
I'm not sure who owns the TD scripts, but I'd be willing to try to get
them working again if someone could point me at them (and how to get the
appropriate accounts, etc)
--Josh
At 14:29 on 03/10/2003 PST, Ask Bjoern Hansen <[EMAIL PROTECTED]> wrote:
>
> The tind
> Slightly related, I think we could use some more tinderbox testers.
> Someone was running the tests on Compaq's test drive boxes, but that
> seems to have stopped?
I've restarted my Sparc/Solaris 8 tinderbox. Defining a list of needed test platforms
might be a good idea. I
The tinderbox is all in flames.
http://xrl.us/dxm (Link to tinderbox.perl.org)
At least the "miette", "moof" and "rh80smoketest" boxes should be
okay; and they are not. :-) Sunday afternoon (PST) seems to be the
hour of the big arson. However there are also indi
uot; <[EMAIL PROTECTED]> wrote:
> Leopold Toetsch wrote:
>
> Again same problem:
>
>> Proxy Error
>> The proxy server received an invalid response from an upstream server.
>>
>> The proxy server could not handle the request GET
>> /tinderbox/bdshowbuil
Leopold Toetsch wrote:
Again same problem:
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET
/tinderbox/bdshowbuild.cgi.
Reason: Could not connect to remote machine: Operation timed out
Apache/1.3.26 Server
> Strange. I can ssh in, and apachectl claims that the webserver is running,
> but I'm getting that error too.
>
> Ask, Robert: any ideas?
Looks like the apache had hung somewhere. I shut it down and started
it up, and it seems ok.
-R
nse from an upstream server.
>
> The proxy server could not handle the request GET
> /tinderbox/bdshowbuild.cgi.
>
> Reason: Could not connect to remote machine: Operation timed out
>
> Apache/1.3.26 Server at tinderbox.perl.org Port 80
>
>
> TIA,
> leo
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET
/tinderbox/bdshowbuild.cgi.
Reason: Could not connect to remote machine: Operation timed out
Apache/1.3.26 Server at tinderbox.perl.org Port 80
TIA,
leo
At 4:40 PM +0100 1/21/03, Leopold Toetsch wrote:
Seems to be some missing dependency. 'make realclean' should do it.
jit_cpu.c:603: structure has no member named `number'
That's mine--I'll go get it cleaned up. I'm not sure it'll help that
much, as I'm seeing multiply-defined symbol issues at
Seems to be some missing dependency. 'make realclean' should do it.
jit_cpu.c:603: structure has no member named `number'
This file is generated by jit2h.pl which uses OpTrans::C and there is
u.number for 'nc'.
leo
Leopold Toetsch wrote:
Dan Sugalski wrote:
Three? Every test fails under OS X because of this...
If not done yet, I'll fix this tomorrow.
Done.
leo
Dan Sugalski wrote:
I think we can stand 3 failing tests for one or two days, when the
reason is well known.
Three? Every test fails under OS X because of this...
Oops, dynamic vs static NCI..., sorry.
If not done yet, I'll fix this tomorrow.
leo
ts; everything else
fails :-). That's one reason I didn't find your earlier message
describing this problem. It wasn't obvious to me that this massive
failure of nearly everything was due to "eval", so I didn't think to look
for messages in that thread.
What I was actual
At 9:38 PM +0100 1/17/03, Leopold Toetsch wrote:
Andy Dougherty (via RT) wrote:
In this case, I suspect it's failing to match "pIt", which was recently
added to interpeter.c:setup_default_compreg().
Nothing to suspect here ;-)
In "[CVS ci] eval #1" I wrote:
Missing and left for an exercise fo
Andy Dougherty (via RT) wrote:
In this case, I suspect it's failing to match "pIt", which was recently
added to interpeter.c:setup_default_compreg().
Nothing to suspect here ;-)
In "[CVS ci] eval #1" I wrote:
Missing and left for an exercise for Joe Other Parrothacker:
build_nativecall.pl lac
At 6:42 PM + 1/17/03, Andy Dougherty (via RT) wrote:
# New Ticket Created by Andy Dougherty
# Please include the string: [perl #20374]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=20374 >
The Solaris tinderboxes are fa
# New Ticket Created by Andy Dougherty
# Please include the string: [perl #20374]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=20374 >
The Solaris tinderboxes are failing with the unhelpful message
"PANIC: Unknown signat
At 7:55 PM -0800 12/8/02, Steve Fink wrote:
I've gotten tired of endlessly clicking on tinderbox links to try to
figure out what's generally going wrong, so I made my computer do it
for me. Yes, I should have just made a script that runs on the
tinderbox machine or something instead
d measure, I wiped out parrot on drinky-drinky and for both of
the frivolous configurations (gcc + SUNWspro) and am doing a manual
run of the tinderbox client for all three.
blair.
On Dec-09, Josh Wilmes wrote:
>
> At 19:55 on 12/08/2002 PST, Steve Fink <[EMAIL PROTECTED]> wrote:
>
> > You can see the results here: http://foxglove.dnsalias.org/parrot/
>
> I'm getting a 404 on that.
Well, of course you would! Don't you know anything about the web? You
should have figured o
At 19:55 on 12/08/2002 PST, Steve Fink <[EMAIL PROTECTED]> wrote:
> You can see the results here: http://foxglove.dnsalias.org/parrot/
I'm getting a 404 on that.
--Josh
I've gotten tired of endlessly clicking on tinderbox links to try to
figure out what's generally going wrong, so I made my computer do it
for me. Yes, I should have just made a script that runs on the
tinderbox machine or something instead of parsing Data::Dumper output,
but I didn
Simon Glover wrote:
On Tue, 19 Nov 2002, Steve Fink wrote:
t/op/lexicals.t 6 1536 66 100.00% 1-6
t/pmc/multiarra 2 512 32 66.67% 2-3
t/pmc/scratchpa 3 768 33 100.00% 1-3
I can get these
On Thu, Nov 21, 2002 at 11:59:36AM -0500, Andy Dougherty wrote:
> While compiling, I did get the warnings:
>
> "cpu_dep.c", line 24: warning: initializer does not fit or is out of
> range: 0x91d02003
> "cpu_dep.c", line 26: warning: initializer does not fit or is out of
> range: 0x81c3e008
That
On Thu, 21 Nov 2002, Dan Sugalski wrote:
> At 9:53 AM -0500 11/21/02, Jason Gloudon wrote:
> >On Thu, Nov 21, 2002 at 08:34:04AM +0100, Leopold Toetsch wrote:
> >
> >My patch in 16237 has the code to flush register windows on v8 and
> >older and v9
> >(64-bit) SPARC systems, which is what one is
On Thu, Nov 21, 2002 at 10:28:42AM -0500, Andy Dougherty wrote:
> > +#ifdef HAS_HEADER_SETJMP
> > +jmp_buf env;
> > +
> > +/* this should put registers in env, which then get marked in
> > + * trace_system_stack below
> > + */
> > +setjmp(env);
> > +#endif
>
> Alas, no, though
At 9:53 AM -0500 11/21/02, Jason Gloudon wrote:
On Thu, Nov 21, 2002 at 08:34:04AM +0100, Leopold Toetsch wrote:
My patch in 16237 has the code to flush register windows on v8 and
older and v9
(64-bit) SPARC systems, which is what one is really trying to achieve via
setjmp.
If this hasn't been
On Thu, 21 Nov 2002, Leopold Toetsch wrote:
> > A bit more ... In particular, on Solaris, I've been able to track down
> > one way of triggering the the t/op/lexicals.t failure to list.c. If I
> > compile list.c without any optimization, the test passes. If I compile
> > just the list_new functi
On Thu, Nov 21, 2002 at 08:34:04AM +0100, Leopold Toetsch wrote:
My patch in 16237 has the code to flush register windows on v8 and older and v9
(64-bit) SPARC systems, which is what one is really trying to achieve via
setjmp.
--
Jason
Andy Dougherty wrote:
A bit more ... In particular, on Solaris, I've been able to track down
one way of triggering the the t/op/lexicals.t failure to list.c. If I
compile list.c without any optimization, the test passes. If I compile
just the list_new function in list.c with the lowest optimiz
On Wed, 20 Nov 2002, Blair Christensen wrote:
> On Tue, Nov 19, 2002 at 09:33:10PM -0800, Steve Fink wrote:
> > ### frivolous (Solaris 9 on Sparc; gcc-3.1) ###
> >
> > Looks like it crashed in the hashtable test. Why???
> >
> > Failed Test Stat Wstat Total Fail Failed List of Failed
> >
me to examine this more closely
right now (as I've got a flight to catch), but next week, once work is
less hectic and I'm back in the office, I'll look at this again.
In addition, I'll be installing the latest Sun Workshop Pro compiler on
frivolous and running that as anoth
On Wed, 20 Nov 2002, Simon Glover wrote:
> On Tue, 19 Nov 2002, Steve Fink wrote:
> >
> > t/op/lexicals.t 6 1536 66 100.00% 1-6
> > t/pmc/multiarra 2 512 32 66.67% 2-3
> > t/pmc/scratchpa 3 768 3
On Tue, 19 Nov 2002, Steve Fink wrote:
>
> t/op/lexicals.t 6 1536 66 100.00% 1-6
> t/pmc/multiarra 2 512 32 66.67% 2-3
> t/pmc/scratchpa 3 768 33 100.00% 1-3
I can get these to fail on Li
Steve Fink wrote:
Looks like somebody gave the TD-* machines the correct input. Yay! We
can actually see some green again!
t/op/interp.t 1 256 21 50.00% 2
unimp restart on PPC
t/op/lexicals.t6 1536 66 100.00% 1-6
t/pmc/scratchpad.t
In article <[EMAIL PROTECTED]>,
[EMAIL PROTECTED] (Steve Fink) wrote:
[snip]
> ### glastig (Mac OS X 10.1) ###
>
> I've seen this message before, but I thought it was fixed now:
> "find_type returned 0 for illegal wanted -68". The next failure is
> similar: "Sub PMCs should be type 17 but have i
At 21:33 on 11/19/2002 PST, Steve Fink <[EMAIL PROTECTED]> wrote:
> ### galactic-lcc (Debian x86, lcc 4.1) ###
>
> Failed the "mod_n" test in number.t, and the "pushn & popn (deep)"
> test in stacks.t.
Not sure what the story is with pushn/popn, but the mod_n failure is normal
for lcc- it appear
At 9:33 PM -0800 11/19/02, Steve Fink wrote:
### glastig (Mac OS X 10.1) ###
I've seen this message before, but I thought it was fixed now:
"find_type returned 0 for illegal wanted -68". The next failure is
similar: "Sub PMCs should be type 17 but have incorrect type 16".
That's a test I added wh
Looks like somebody gave the TD-* machines the correct input. Yay! We
can actually see some green again!
On the other hand, everything else is still failing. I tried compiling
on a Solaris box, but the darned thing worked flawlessly. Here's a
summary of what's going wrong on the various tinderboxe
Here's a message I got from a nice admin at HP.
--
Andy Dougherty [EMAIL PROTECTED]
-- Forwarded message --
Date: Mon, 23 Sep 2002 14:53:34 -0400
From: James Chamberlain <[EMAIL PROTECTED]>
To: Andy Dougherty <[EMAIL PROTECTED]>
Subject:
o Compaq.
>
> > Yes, I had noticed that. And that struct me as strange, particularly
>
> Too much C programming, eh? :)
>
> > because that machine had worked before, but isn't working now. I'll remove
> > it from the list of machines it connects to.
>
t me as strange, particularly
Too much C programming, eh? :)
> because that machine had worked before, but isn't working now. I'll remove
> it from the list of machines it connects to.
>From our current tinderbox list, we're...oddly...all green.
Closer observation, though,
27; in the
> $PATH being used, so the log file looks like this:
>
> ...
>
> Obviously it's not going to work. If there is a perl installed on
> that machine, then perhaps the full pathname to perl should be used.
> If there's no perl, then perhaps the machine sh
d on
that machine, then perhaps the full pathname to perl should be used.
If there's no perl, then perhaps the machine should be removed from the
tinderbox.
--
Andy Dougherty [EMAIL PROTECTED]
Andy Dougherty wrote:
>
> On Thu, 5 Sep 2002, Andy Dougherty wrote:
>
> > Ok, with the alignment hack now in (see resources.c) and lots of various
> > and sundry portability fixes, it looks like we're on our way to turning
> > the tinderbox a lovely shade of
and sundry portability fixes, it looks like we're on our way to turning
> > > the tinderbox a lovely shade of green.
> >
> > AARGH! It appears I spoke too soon. I don't have easy access to check,
> > but it looks like my alignment patch (resources.c, header.h)
On Fri, Sep 06, 2002 at 09:32:27PM -0400, Andy Dougherty wrote:
> On Thu, 5 Sep 2002, Andy Dougherty wrote:
>
> > Ok, with the alignment hack now in (see resources.c) and lots of various
> > and sundry portability fixes, it looks like we're on our way to turning
> >
On Thu, 5 Sep 2002, Andy Dougherty wrote:
> Ok, with the alignment hack now in (see resources.c) and lots of various
> and sundry portability fixes, it looks like we're on our way to turning
> the tinderbox a lovely shade of green.
AARGH! It appears I spoke too soon. I don'
On Thu, 5 Sep 2002, Andy Dougherty wrote:
> Ok, with the alignment hack now in (see resources.c) and lots of various
> and sundry portability fixes, it looks like we're on our way to turning
> the tinderbox a lovely shade of green. (The solaris failures are timeouts
> unrelat
Ok, with the alignment hack now in (see resources.c) and lots of various
and sundry portability fixes, it looks like we're on our way to turning
the tinderbox a lovely shade of green. (The solaris failures are timeouts
unrelated to parrot, and the other failures are due to MANIFEST hiccough
Steve Fink:
# Which brings me to my question: is there some way of getting
# machine-readable output from tinderbox? I'd really like to
# alias my cvs commit to something that automatically monitors
# the tinderbox for the next hour and a half so it screams at
# me when I increase the cu
On Wed, 22 May 2002, Steve Fink wrote:
> Which brings me to my question: is there some way of getting
> machine-readable output from tinderbox? I'd really like to alias my cvs
> commit to something that automatically monitors the tinderbox for the
> next hour and a half so it s
ifferently with respect to sizeof(HASHBUCKET)
> > boundaries (32 bytes on linux-ppc), it will adjust pointers by a
> > multiple of sizeof(HASHBUCKET), causing wierd segfaults. I believe
> > the included patch fixes it. I didn't look for similar issues
> > elsewhere, but t
On Wed, 20 Mar 2002, Ask Bjoern Hansen wrote:
> Would anyone get terribly upset if I nuked say everything older than
> a month?
Too late now. :-) When it's done deleting then log lookups should
be a lot faster.
Robert said he'd work on a new tinderbox system (with help fro
we have the log output from more than 15 tinderbox builds of
parrot. In the current system they are each stored as a separate
file (in the same directory no less).
Would anyone get terribly upset if I nuked say everything older than
a month?
- ask
--
ask bjoern hansen, http
I just committed the fix for that Dan, disregard.
-Melvin
>Checking some things by compiling and running another small C program (this
>could take a while):
>
> Building ./testparrotsizes.cfrom testparrotsizes_c.in...
>In file included from include/parrot/string.h:18,
>
Enjoy. :)
-Melvin
Checking some things by compiling and running another small C program (this
could take a while):
Building ./testparrotsizes.cfrom testparrotsizes_c.in...
In file included from include/parrot/string.h:18,
from include/parrot/parrot.h:85,
fferent colors mean. There are also no clients for windows or other rare
>> OS's now. It would be great if we could get one going. I'll do the best that
>> I can to help get it setup.
>
> I remember trying a month or so ago and it appeared that the Tinderbox
> modu
>different colors mean. There are also no clients for windows or other rare
>OS's now. It would be great if we could get one going. I'll do the best that
>I can to help get it setup.
I remember trying a month or so ago and it appeared that the Tinderbox
module used sendmail
I just wanted to give everyone a quick summary of the status of tinderbox
and bonsai. Tinderbox is up and running at tinderbox.perl.org. If people
would like, I can configure a little bot for #parrot so that it will let
everyone know if the tinderbox state changes (but won't annoy people in
>include/parrot/string.h:40: parse error before `;'
>include/parrot/string.h:44: two or more data types in declaration of
>`BUFFER_flags'
>include/parrot/string.h:44: warning: duplicate `typedef'
>C compiler died! at Configure.pl line 836.
>
>Also, the
arrot/string.h:44: two or more data types in declaration of `BUFFER_flags'
include/parrot/string.h:44: warning: duplicate `typedef'
C compiler died! at Configure.pl line 836.
Also, the tinderbox is in flames for the same reason.
Thanks,
-Jesse
--
"Oh, bother," said Pooh, as he hid Piglet's mangled corpse.
I'm removing this more common configuration because of the increased time
it takes to build Parrot these days. If someone else wants to pick it up,
cool, but until then I'm figuring that if the other two (mixed 32/64-bit
and pure 64-bit) work, 32-bit probably does too.
- D
<[EMAIL PROTECTED]>
> Sent: Tuesday, January 01, 2002 11:29 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Color codes in tinderbox (All tests pass!!!)
>
>
> "Sterin, Ilya" wrote:
> > I wonder if it matters what current perl version you are
> using? Also
> > what VC++ and Servi
"Sterin, Ilya" wrote:
> I wonder if it matters what current perl version you are using?
> Also what VC++ and Service Pack are you using as well as your OS.
MS Windows 2000 Profession, SP-2
MS VisualStudio 6 SP-4 (installing SP-5 soon)
c:\home>perl -V
Summary of my perl5 (revision 5 version 6
"might be" before going deeper.
Ilya
> -Original Message-
> From: Sebastian Bergmann [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 01, 2002 10:34 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Color codes in tinderbox (All tests pass!!!)
>
>
> "
"Sterin, Ilya" wrote:
> Mine pass fine...
Current CVS, same crash: http://www.sebastian-bergmann.de/parrot.txt
--
Sebastian Bergmann
http://sebastian-bergmann.de/ http://phpOpenTracker.de/
Did I help you? Consider a gift: http://wishlist.sebastian-bergmann.de/
Re: Color codes in tinderbox
>
>
> "Sterin, Ilya" wrote:
> > I haven't done any testing yet, though.
>
> It compiles here, too. But 'nmake test' runs as far as
>
> t/op/basic..ok
> t/op/bitwiseok
> t/op/debuginfo..ok
>
At 05:24 PM 1/1/2002 +0100, Sebastian Bergmann wrote:
>Simon Cozens wrote:
> > You'll kick yourself.
> >
> > perl Configure.pl -debugging
>
> perl Configure.pl --debugging
>
> seems to have no effect on Win32, as of now.
Odd. It should add debugging flags. The hints file hints/mswin32.p
Simon Cozens wrote:
> You'll kick yourself.
>
> perl Configure.pl -debugging
perl Configure.pl --debugging
seems to have no effect on Win32, as of now.
--
Sebastian Bergmann
http://sebastian-bergmann.de/ http://phpOpenTracker.de/
Did I help you? Consider a gift
On Tue, Jan 01, 2002 at 02:46:44PM +0100, Sebastian Bergmann wrote:
> By the way: How do I build a debug version of Parrot, so that I could
> provide a stacktrace?
You'll kick yourself.
perl Configure.pl -debugging
--
`First Up Against The Wall When The Revolution Comes! Woohoo!
S
Sebastian Bergmann wrote:
> and then test_parrot.exe crashes.
By the way: How do I build a debug version of Parrot, so that I could
provide a stacktrace? Using MSVC's debugger with the test_parrot.exe
that nmake produces unusable results, because no debugging information
is in the execu
"Sterin, Ilya" wrote:
> I haven't done any testing yet, though.
It compiles here, too. But 'nmake test' runs as far as
t/op/basic..ok
t/op/bitwiseok
t/op/debuginfo..ok
t/op/hacks..ok
t/op/integerok
t/op/interp.ok
t/op/macro..ok
t/op/number...
> -Original Message-
> From: Bryan C. Warnock [mailto:[EMAIL PROTECTED]]
> Sent: Monday, December 31, 2001 7:10 PM
> To: Sterin, Ilya; 'Dan Sugalski'; [EMAIL PROTECTED]
> Subject: Re: Color codes in tinderbox
>
>
> On Monday 31 December 2001 11:58 pm
On Monday 31 December 2001 11:58 pm, Sterin, Ilya wrote:
> Straight out of the box:-) I'll be recompiling now daily to make sure
> all patches and new development does not break it.
I don't think daily recompilation is going to prevent that. ;-)
--
Bryan C. Warnock
[EMAIL PROTECTED]
i [mailto:[EMAIL PROTECTED]]
> Sent: Monday, December 31, 2001 4:59 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Color codes in tinderbox
>
>
> On Mon, 31 Dec 2001, Sterin, Ilya wrote:
>
> > Just to let you know, the latest CVS compiled on Win32 VC++ 6.0
> > Enterprise SP
On Mon, 31 Dec 2001, Sterin, Ilya wrote:
> Just to let you know, the latest CVS compiled on Win32 VC++ 6.0
> Enterprise SP 5. There are quite a few warning, though it's a big
> progress from yesterday's problems. I haven't done any testing yet,
> though.
Did you need to abuse the makefile any
Just to let you know, the latest CVS compiled on Win32 VC++ 6.0
Enterprise SP 5. There are quite a few warning, though it's a big
progress from yesterday's problems. I haven't done any testing yet,
though.
Ilya
On Mon, 31 Dec 2001, David M. Lloyd wrote:
> When I look at the tinderbox screen, there's green, orange, yellow, and
> red. What to the colors mean? There's no key.
Green means tests passed OK. Orange means tests failed, yellow means a run
has started but not finished (there&
When I look at the tinderbox screen, there's green, orange, yellow, and
red. What to the colors mean? There's no key.
You know, it's kind of fun to watch. There should be like an auto-refresh
every 5 minutes or something. :-)
- D
<[EMAIL PROTECTED]>
At 05:07 PM 12/31/2001 -0600, David M. Lloyd wrote:
>On Mon, 31 Dec 2001, Dan Sugalski wrote:
>
> > > > Could you throw the system into tinderbox? It'll give us logs of the
> > > > zillions of errors or so...
> > >
> > >I am working on it
ing for p5p folks that might have machines they
> > could enlist if it didn't take any effort on their part. :)
> >
> > I installed the patch, too, thanks.
> >
> > Could you throw the system into tinderbox? It'll give us logs of the
> > zillions of err
1 - 100 of 110 matches
Mail list logo
