Re: Output from Console.WriteLine methods is deferred
"Charlie Poole" <[email protected]> Sun, 20 Jul 2008 13:48:44 -0700
| Newsgroups | gmane.comp.windows.dotnet.nunit.user |
|---|---|
| Message-ID | <005201c8eaaa$01ba0fd0$6401a8c0@ferrari> |
It's probably related to the fact that it comes with Mono, which uses 2.2 for it's own tests - I wish it weren't so! You get a newer version - but not that new - if you install monodevelop. And as you found, there are other repositories you can use and - in a pinch - you can just take our binaries and copy them appropriately. It's all IL anyway. Charlie > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf > Of "Andrés G. Aragoneses" > Sent: Sunday, July 20, 2008 11:23 AM > To: [email protected] > Subject: Re: [Nunit-users] Output from Console.WriteLine > methods is deferred > > > Wow! I'm surprised that openSUSE11 is shipping so an outdated > version by default then (you can see this is true here [1], > if you look for "nunit" > you'll find mono-nunit-1.9 in the standard repositories). > > Luckily, it seems I can install a newer version from another > repository. > I will try that an report back here. But we should do > something about that old version shipping (I'll file a bug in > bugzilla about it...). > > Thanks! > > Andrés > > > [1] http://software.opensuse.org/search > > Charlie Poole wrote: > > Glad to hear it. :-) > > > > That release is almost four years old. I know that issues > of delayed > > printing were dealt with several times by bugs submitted > during that > > period. In fact, NUnit's internal handling of text has been > > re-designed since then. > > > > Are you in a position to upgrade the version of NUnit you > are using? > > The last release in the 2.2 series was 2.2.10, which > shipped in March > > 2007. The current release is 2.4.7, with a 2.4.8 bug fix > release about > > to come out. > > The 2.5 release is in alpha. > > > > If you upgrade, I suggest doing a side by side install > first. And when > > you finally remove 2.2, save a copy of its > nunit.framework.dll for use > > by your old tests unless you plan to recompile them. > > > > NUnit always does fixes in a new release. So, if some local policy > > keeps you from upgrading, you're pretty much stuck with the > bugs. :-( > > > > Charlie > > > >> -----Original Message----- > >> From: [email protected] > >> [mailto:[email protected]] On Behalf Of > >> "Andrés G. Aragoneses" > >> Sent: Sunday, July 20, 2008 9:34 AM > >> To: Charlie Poole > >> Cc: [email protected] > >> Subject: Re: [Nunit-users] Output from Console.WriteLine > methods is > >> deferred > >> > >> > >> I'm using NUnit version 2.2.0 and I notice the deferred printing > >> behaviour even when my unit tests behave normally (without > infinite > >> loops). > >> > >> Regards, > >> > >> Andrés > >> > >> Charlie Poole wrote: > >>> That may work, but I'm guessing not. It sounds as if your > >> program may > >>> just be taking up all the cpu cycles. > >>> > >>> This could also be a bug - in which case I hope he's using an old > >>> version of NUnit. :-) > >>> > >>> Charlie > >>> > >>>> -----Original Message----- > >>>> From: [email protected] > >>>> [mailto:[email protected]] On > >> Behalf Of Eric > >>>> Teutsch > >>>> Sent: Saturday, July 19, 2008 7:39 AM > >>>> To: '"Andrés G. Aragoneses"'; [email protected] > >>>> Subject: Re: [Nunit-users] Output from Console.WriteLine > >> methods is > >>>> deferred > >>>> > >>>> Try to put this after the Console.WriteLine: > >>>> Console.Out.Flush(); > >>>> > >>>> > >>>> > >>>> -----Original Message----- > >>>> From: [email protected] > >>>> [mailto:[email protected]] On Behalf Of > >>>> "Andrés G. > >>>> Aragoneses" > >>>> Sent: July 19, 2008 09:23 > >>>> To: [email protected] > >>>> Subject: [Nunit-users] Output from Console.WriteLine methods is > >>>> deferred > >>>> > >>>> Hello. I've been using NUnit for a long time and I think > it rocks! > >>>> Many thanks to all the devs. > >>>> > >>>> And now I would like to ask a question: I've been noticing > >> that, if > >>>> my unit tests write some text to the output > >> (Console.WriteLine), it > >>>> only gets shown when nunit-console finishes all the tests. > >> This may > >>>> be a feature and not a bug, but there's a problem with this > >>>> behaviour: it prevents easy debugging for when the unit > >> tests enter > >>>> in an infinite loop, because you cannot see what's happenning. > >>>> > >>>> Is there any command line to get direct output from the > unit tests > >>>> without being deferred? > >>>> > >>>> Thanks! > >>>> Andrés > >>>> > >>>> -- > >>>> > >>>> > >>>> -------------------------------------------------------------- > >>>> ----------- > >>>> This SF.Net email is sponsored by the Moblin Your Move > Developer's > >>>> challenge Build the coolest Linux based applications with > >> Moblin SDK > >>>> & win great prizes Grand prize is a trip for two to an > Open Source > >>>> event anywhere in the world > >>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ > >>>> _______________________________________________ > >>>> Nunit-users mailing list > >>>> [email protected] > >>>> https://lists.sourceforge.net/lists/listinfo/nunit-users > >>>> > >>>> > >>>> -------------------------------------------------------------- > >>>> ----------- > >>>> This SF.Net email is sponsored by the Moblin Your Move > Developer's > >>>> challenge Build the coolest Linux based applications with > >> Moblin SDK > >>>> & win great prizes Grand prize is a trip for two to an > Open Source > >>>> event anywhere in the world > >>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ > >>>> _______________________________________________ > >>>> Nunit-users mailing list > >>>> [email protected] > >>>> https://lists.sourceforge.net/lists/listinfo/nunit-users > >>>> > >>> > >>> > >>> > >> > --------------------------------------------------------------------- > >> - > >>> --- This SF.Net email is sponsored by the Moblin Your Move > >> Developer's > >>> challenge Build the coolest Linux based applications with > >> Moblin SDK & > >>> win great prizes Grand prize is a trip for two to an Open > >> Source event > >>> anywhere in the world > >>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ > >> > >> -------------------------------------------------------------- > >> ----------- > >> This SF.Net email is sponsored by the Moblin Your Move Developer's > >> challenge Build the coolest Linux based applications with > Moblin SDK > >> & win great prizes Grand prize is a trip for two to an Open Source > >> event anywhere in the world > >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ > >> _______________________________________________ > >> Nunit-users mailing list > >> [email protected] > >> https://lists.sourceforge.net/lists/listinfo/nunit-users > >> > > > > > > > > > ---------------------------------------------------------------------- > > --- This SF.Net email is sponsored by the Moblin Your Move > Developer's > > challenge Build the coolest Linux based applications with > Moblin SDK & > > win great prizes Grand prize is a trip for two to an Open > Source event > > anywhere in the world > > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > > > -------------------------------------------------------------- > ----------- > This SF.Net email is sponsored by the Moblin Your Move > Developer's challenge Build the coolest Linux based > applications with Moblin SDK & win great prizes Grand prize > is a trip for two to an Open Source event anywhere in the > world http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Nunit-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/nunit-users > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/