Re: Diagnostics?

2019-07-08 Thread Vadim Belman
If they aren't, maybe a) the docs should be more explicit, and b), the > diagnostics should say so, immediately? > > perl6 -v > This is Rakudo Star version 2019.03.1 built on MoarVM version 2019.03 >

Diagnostics?

2019-07-08 Thread Parrot Raiser
it as "an exercise for the reader". If unpaired boundary characters like these are legal, presumably there's a problem with the parser or compiler? If they aren't, maybe a) the docs should be more explicit, and b), the diagnostics should say so, immediately? perl6 -v This is Rakudo St

Re: [perl #131767] [RESOLVED] Test.pm6 should redirect diagnostics to stdout instead of stderr

2017-07-21 Thread Gabor Szabo
Thank you!

Re: [perl #131767] [RESOLVED] Test.pm6 should redirect diagnostics to stdout instead of stderr

2017-07-21 Thread Gabor Szabo via RT
Thank you!

[perl #131767] Test.pm6 should redirect diagnostics to stdout instead of stderr

2017-07-21 Thread Zoffix Znet via RT
ion IMHO the final report should also say "1 todo" > > Our repo is https://github.com/Bailador/Bailador > > I've posted this to the TAP::Harness project but Leon Timmermans > directed me to Test.pm6 > https://github.com/perl6/tap-harness6/issues/17 > > "That output has n

[perl #131767] Test.pm6 should redirect diagnostics to stdout instead of stderr

2017-07-21 Thread Zoffix Znet via RT
ion IMHO the final report should also say "1 todo" > > Our repo is https://github.com/Bailador/Bailador > > I've posted this to the TAP::Harness project but Leon Timmermans > directed me to Test.pm6 > https://github.com/perl6/tap-harness6/issues/17 > > "That output has n

[perl #131767] Test.pm6 should redirect diagnostics to stdout instead of stderr

2017-07-20 Thread Zoffix Znet via RT
On Wed, 19 Jul 2017 16:46:20 -0700, c...@zoffix.com wrote: > Gonna take care of this in the next 26hr I lied. Need more time. The fix I planned to do solved the issue, but now it's reporting the subtest as an unexpectedly-passing TODO heh :P Gonna think about it for another day or two,

[perl #131767] Test.pm6 should redirect diagnostics to stdout instead of stderr

2017-07-20 Thread Zoffix Znet via RT
On Wed, 19 Jul 2017 16:46:20 -0700, c...@zoffix.com wrote: > Gonna take care of this in the next 26hr I lied. Need more time. The fix I planned to do solved the issue, but now it's reporting the subtest as an unexpectedly-passing TODO heh :P Gonna think about it for another day or two,

[perl #131767] Test.pm6 should redirect diagnostics to stdout instead of stderr

2017-07-19 Thread Zoffix Znet via RT
ion IMHO the final report should also say "1 todo" > > Our repo is https://github.com/Bailador/Bailador > > I've posted this to the TAP::Harness project but Leon Timmermans > directed me to Test.pm6 > https://github.com/perl6/tap-harness6/issues/17 > > "That output has n

[perl #131767] Test.pm6 should redirect diagnostics to stdout instead of stderr

2017-07-19 Thread Zoffix Znet via RT
ion IMHO the final report should also say "1 todo" > > Our repo is https://github.com/Bailador/Bailador > > I've posted this to the TAP::Harness project but Leon Timmermans > directed me to Test.pm6 > https://github.com/perl6/tap-harness6/issues/17 > > "That output has n

[perl #131767] Test.pm6 should redirect diagnostics to stdout instead of stderr

2017-07-19 Thread via RT
ition IMHO the final report should also say "1 todo" Our repo is https://github.com/Bailador/Bailador I've posted this to the TAP::Harness project but Leon Timmermans directed me to Test.pm6 https://github.com/perl6/tap-harness6/issues/17 "That output has nothing to do with tod

LLVM/Clang and diagnostics

2009-10-24 Thread Aaron Sherman
This might be a useful point of reference for thinking about diagnostics and what's important to the developer working with Perl 6 in the future: http://clang.llvm.org/diagnostics.html

[perl #56470] [CAGE] new perlcritic test gives verbose not installed diagnostics.

2008-06-30 Thread via RT
# New Ticket Created by Will Coleda # Please include the string: [perl #56470] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=56470 Find a perlcritic-sane way to silence this warning for codetest: Policy

[perl #56470] [CAGE] new perlcritic test gives verbose not installed diagnostics.

2008-06-30 Thread Will Coleda via RT
On Mon Jun 30 07:53:20 2008, coke wrote: Find a perlcritic-sane way to silence this warning for codetest: Policy Perl::Critic::Policy::Bangs::ProhibitFlagComments is not installed. Fixed in r28867. -- Will Coke Coleda

[perl #39831] TGE - Needs more diagnostics on failure.

2006-07-13 Thread via RT
# New Ticket Created by Will Coleda # Please include the string: [perl #39831] # in the subject line of all future correspondence about this issue. # URL: http://rt.perl.org/rt3/Ticket/Display.html?id=39831 $ ../../parrot ../../compilers/tge/tgc.pir --output=src/grammar/ post2pir.pir

Diagnostics changed to include test description

2005-07-01 Thread Michael G Schwern
ZimMY BUSINESS IS DONE!/Zim Test diagnostics now look like this: not ok 21 - foo is bar? # Failed test 'foo is bar?' # in t/foo.t at line 40. # got: 'foo' # expected: 'bar' If there's no description it looks like this: not ok 21 # Failed test in t/foo.t at line

verbose diagnostics

2005-04-28 Thread Paul Johnson
Using Test::More, I would like to send some diagnostics to be seen only when the harness is running in verbose mode. There doesn't seem to be a way of doing this. The best I could come up with is: sub vdiag { pass(@_) } but this has little to recommend it. Thoughts? -- Paul Johnson

Re: verbose diagnostics

2005-04-28 Thread Fergal Daly
Where is TEST_VERBOSE documented? I see HARNESS_VERBOSE in http://search.cpan.org/~petdance/Test-Harness-2.48/lib/Test/Harness.pm F On 4/28/05, Adrian Howard [EMAIL PROTECTED] wrote: On 28 Apr 2005, at 14:23, Paul Johnson wrote: Using Test::More, I would like to send some diagnostics

Re: verbose diagnostics

2005-04-28 Thread Paul Johnson
On Thu, Apr 28, 2005 at 02:44:30PM +0100, Adrian Howard wrote: On 28 Apr 2005, at 14:23, Paul Johnson wrote: Using Test::More, I would like to send some diagnostics to be seen only when the harness is running in verbose mode. [snip] diag some verbose diagnostics if $ENV

Re: verbose diagnostics

2005-04-28 Thread Michael G Schwern
On Thu, Apr 28, 2005 at 02:44:30PM +0100, Adrian Howard wrote: On 28 Apr 2005, at 14:23, Paul Johnson wrote: Using Test::More, I would like to send some diagnostics to be seen only when the harness is running in verbose mode. [snip] diag some verbose diagnostics if $ENV

Re: verbose diagnostics

2005-04-28 Thread James E Keenan
Fergal Daly wrote: Where is TEST_VERBOSE documented? I see HARNESS_VERBOSE in http://search.cpan.org/~petdance/Test-Harness-2.48/lib/Test/Harness.pm F http://search.cpan.org/grep?release=Test-Harness-2.48string=TEST_VERBOSEn=1 HTH jimk

Re: verbose diagnostics

2005-04-28 Thread Michael G Schwern
On Thu, Apr 28, 2005 at 10:08:00PM -0400, James E Keenan wrote: Fergal Daly wrote: Where is TEST_VERBOSE documented? I see HARNESS_VERBOSE in http://search.cpan.org/~petdance/Test-Harness-2.48/lib/Test/Harness.pm http://search.cpan.org/grep?release=Test-Harness-2.48string=TEST_VERBOSEn=1