> 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/
sts successful, 2 subtests skipped.
Files=14, Tests=249, 54 wallclock secs ( 0.00 cusr + 0.00 csys = 0.00
CPU)
Ilya
> -Original Message-
> From: Sebastian Bergmann [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 01, 2002 1:10 AM
> To: [EMAIL PROTECTED]
> Subject:
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's a "build start"
16 matches
Mail list logo