That's a scary idea. Anybody can see what you are accessing? No,
not as far as I know. :-) Perhaps the LP guys can.

Charlie

On Tue, Oct 2, 2012 at 9:56 AM, Jv <email address hidden> wrote:
> Is not the branch pull-ed by me not visible in the lp log?
>
> Jv
>
> On Tue, Oct 2, 2012 at 9:40 PM, Charlie Poole <email address hidden> wrote:
>
>> Hi Jv,
>>
>> You have to pull and build Simone's branch from source in order to be
>> able to work on this at all. As I remember from some previous work
>> you did, you were unable to do that on your machine. Is that still
>> a problem for you?
>>
>> Charlie
>>
>> On Tue, Oct 2, 2012 at 7:56 AM, Jv <email address hidden> wrote:
>> > Hi Charlie,
>> >
>> > 1. Will start with the scenarios outlined by you plus some of my own.
>> Maybe
>> > they could feature in the help section.
>> >
>> > 2. Waiting for the merge to happen or can NUnit GUI work with Simone's
>> > commit?
>> >
>> > Because I also want to test the GCConcurrent (for previous .net versions)
>> > and serverGc (for .net 4.5) element and this can be done only through the
>> > App config file. I guess this is more important due to it being the new
>> > feature in .Net 4.5.
>> >
>> > 3. The unmanaged aspect to it, where the above configuration settings can
>> > be overridden by the requesting app.What happens in the test (this is
>> not a
>> > question) when the config settings can be overridden by a call to
>> > IsServerGC call from the unmanaged app. Is this  consideration important?
>> > And to complicate things further, some processor.architectures are not
>> > supported.
>> >
>> > I am not sure if this should be documented as a known issue in NUnit or
>> > should NUnit provide a hint when the Async tests are run or executed?
>> >
>> > 4. The SynchronizationContext and the AsynchronizationContext can be
>> quite
>> > tricky when GcCocurrent and ServerGC elements can both be used. Please
>> > comment on this with reference to #2 above.
>> >
>> > Jv
>> >
>> > On Mon, Oct 1, 2012 at 3:37 AM, Charlie Poole <email address hidden> wrote:
>> >
>> >> Sounds good! One thing we need is a test assembly built in VS2012,
>> >> which contains all sorts of combinations of test features, for example,
>> >> test cases that use an async method, methods with timeout plus async,
>> >> methods using testcasesource, etc. The existing NUnit tests have lots
>> >> of examples but of course none of them can use async.
>> >>
>> >> This is actually something that would help us implement async  tests
>> >> in all three projects... NUnit V2, NUnit 3.0 and NUnitLite
>> >>
>> >> Charlie
>> >>
>> >> On Sun, Sep 30, 2012 at 2:39 PM, Jv <email address hidden> wrote:
>> >> > Sure, Charlie, but this particular problem does require more than one
>> >> > person I thought and hence suggested to help. I will try to
>> independently
>> >> > simulate some similar async scenarios and then seek help on how it
>> can be
>> >> > merged with Simone's work.
>> >> >
>> >> > Jv
>> >> >
>> >> > On Mon, Oct 1, 2012 at 2:45 AM, Charlie Poole <email address hidden>
>> wrote:
>> >> >
>> >> >> Hi Jv,
>> >> >>
>> >> >> You should coordinate with Simone on this, since he has the
>> >> >> bug assigned. OTOH, there are tons of things to do other
>> >> >> than this if you want something of your own!
>> >> >>
>> >> >> Charlie
>> >> >>
>> >> >> On Sun, Sep 30, 2012 at 4:02 AM, Jv <email address hidden>
>> wrote:
>> >> >> > Since I am fairly free, I can work on this issue independently as a
>> >> >> > spike. Please point me to the appropriate files in NUnit v2.
>> >> >> >
>> >> >> > I will be working on finding if the async threads' context can be
>> >> >> > independently established.
>> >> >> >
>> >> >> > This will help in maintaining that tests "await"-ing a async
>> result is
>> >> >> > testing the right context and will also help in establishing the
>> >> "void"
>> >> >> > context.
>> >> >> >
>> >> >> > Jv
>> >> >> >
>> >> >> > --
>> >> >> > You received this bug notification because you are subscribed to
>> NUnit
>> >> >> > Extended Testing Platform.
>> >> >> > https://bugs.launchpad.net/bugs/1057981
>> >> >> >
>> >> >> > Title:
>> >> >> >   C#5 async tests are not supported
>> >> >> >
>> >> >> > To manage notifications about this bug go to:
>> >> >> > https://bugs.launchpad.net/nunit-3.0/+bug/1057981/+subscriptions
>> >> >>
>> >> >> --
>> >> >> You received this bug notification because you are a member of NUnit
>> >> >> Developers, which is subscribed to NUnit V2.
>> >> >> https://bugs.launchpad.net/bugs/1057981
>> >> >>
>> >> >> Title:
>> >> >>   C#5 async tests are not supported
>> >> >>
>> >> >> Status in NUnit Test Framework:
>> >> >>   Triaged
>> >> >> Status in NUnitLite Testing Framework:
>> >> >>   Triaged
>> >> >> Status in NUnit V2 Test Framework:
>> >> >>   In Progress
>> >> >>
>> >> >> Bug description:
>> >> >>   If a method is marked async, nunit does not recognise it as a test,
>> >> >>   and some test runners may incorrectly  pass it while it is still
>> >> >>   running. These methods actually return a Task not void, and the
>> test
>> >> >>   can only be passed if the task completes without a failure.
>> >> >>
>> >> >>   As detailed here
>> >> http://anthonysteele.co.uk/async-and-await-with-nunit
>> >> >>
>> >> >>   MSTest supports async tests
>> >> >>
>> >> >>
>> >>
>> http://blogs.msdn.com/b/visualstudioalm/archive/2012/03/13/what-s-new-for-mstest-unit-tests-in-visual-studio-11-beta.aspx
>> >> >>
>> >> >> To manage notifications about this bug go to:
>> >> >> https://bugs.launchpad.net/nunit-3.0/+bug/1057981/+subscriptions
>> >> >>
>> >> >
>> >> >
>> >> > --
>> >> > Regards,
>> >> >
>> >> > Ravichandran Jv
>> >> > http://ravichandranjv.blogspot.com
>> >> >
>> >> > --
>> >> > You received this bug notification because you are subscribed to NUnit
>> >> > Extended Testing Platform.
>> >> > https://bugs.launchpad.net/bugs/1057981
>> >> >
>> >> > Title:
>> >> >   C#5 async tests are not supported
>> >> >
>> >> > To manage notifications about this bug go to:
>> >> > https://bugs.launchpad.net/nunit-3.0/+bug/1057981/+subscriptions
>> >>
>> >> --
>> >> You received this bug notification because you are a member of NUnit
>> >> Developers, which is subscribed to NUnit V2.
>> >> https://bugs.launchpad.net/bugs/1057981
>> >>
>> >> Title:
>> >>   C#5 async tests are not supported
>> >>
>> >> Status in NUnit Test Framework:
>> >>   Triaged
>> >> Status in NUnitLite Testing Framework:
>> >>   Triaged
>> >> Status in NUnit V2 Test Framework:
>> >>   In Progress
>> >>
>> >> Bug description:
>> >>   If a method is marked async, nunit does not recognise it as a test,
>> >>   and some test runners may incorrectly  pass it while it is still
>> >>   running. These methods actually return a Task not void, and the test
>> >>   can only be passed if the task completes without a failure.
>> >>
>> >>   As detailed here
>> http://anthonysteele.co.uk/async-and-await-with-nunit
>> >>
>> >>   MSTest supports async tests
>> >>
>> >>
>> http://blogs.msdn.com/b/visualstudioalm/archive/2012/03/13/what-s-new-for-mstest-unit-tests-in-visual-studio-11-beta.aspx
>> >>
>> >> To manage notifications about this bug go to:
>> >> https://bugs.launchpad.net/nunit-3.0/+bug/1057981/+subscriptions
>> >>
>> >
>> >
>> > --
>> > Regards,
>> >
>> > Ravichandran Jv
>> > http://ravichandranjv.blogspot.com
>> >
>> > --
>> > You received this bug notification because you are a member of NUnit
>> > Developers, which is subscribed to NUnit V2.
>> > https://bugs.launchpad.net/bugs/1057981
>> >
>> > Title:
>> >   C#5 async tests are not supported
>> >
>> > Status in NUnit Test Framework:
>> >   Triaged
>> > Status in NUnitLite Testing Framework:
>> >   Triaged
>> > Status in NUnit V2 Test Framework:
>> >   In Progress
>> >
>> > Bug description:
>> >   If a method is marked async, nunit does not recognise it as a test,
>> >   and some test runners may incorrectly  pass it while it is still
>> >   running. These methods actually return a Task not void, and the test
>> >   can only be passed if the task completes without a failure.
>> >
>> >   As detailed here http://anthonysteele.co.uk/async-and-await-with-nunit
>> >
>> >   MSTest supports async tests
>> >
>> http://blogs.msdn.com/b/visualstudioalm/archive/2012/03/13/what-s-new-for-mstest-unit-tests-in-visual-studio-11-beta.aspx
>> >
>> > To manage notifications about this bug go to:
>> > https://bugs.launchpad.net/nunit-3.0/+bug/1057981/+subscriptions
>> >
>> > _______________________________________________
>> > Mailing list: https://launchpad.net/~nunit-core
>> > Post to     : <email address hidden>
>> > Unsubscribe : https://launchpad.net/~nunit-core
>> > More help   : https://help.launchpad.net/ListHelp
>>
>> --
>> You received this bug notification because you are a member of NUnit
>> Developers, which is subscribed to NUnit V2.
>> https://bugs.launchpad.net/bugs/1057981
>>
>> Title:
>>   C#5 async tests are not supported
>>
>> Status in NUnit Test Framework:
>>   Triaged
>> Status in NUnitLite Testing Framework:
>>   Triaged
>> Status in NUnit V2 Test Framework:
>>   In Progress
>>
>> Bug description:
>>   If a method is marked async, nunit does not recognise it as a test,
>>   and some test runners may incorrectly  pass it while it is still
>>   running. These methods actually return a Task not void, and the test
>>   can only be passed if the task completes without a failure.
>>
>>   As detailed here http://anthonysteele.co.uk/async-and-await-with-nunit
>>
>>   MSTest supports async tests
>>
>> http://blogs.msdn.com/b/visualstudioalm/archive/2012/03/13/what-s-new-for-mstest-unit-tests-in-visual-studio-11-beta.aspx
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/nunit-3.0/+bug/1057981/+subscriptions
>>
>
>
> --
> Regards,
>
> Ravichandran Jv
> http://ravichandranjv.blogspot.com
>
> --
> You received this bug notification because you are subscribed to NUnit
> Extended Testing Platform.
> https://bugs.launchpad.net/bugs/1057981
>
> Title:
>   C#5 async tests are not supported
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nunit-3.0/+bug/1057981/+subscriptions