On Fri, 2 Jun 2023 04:29:16 GMT, Chris Plummer wrote:
>> Virtual threads are always daemon threads, so tests that previously did not
>> explicitly wait for test threads to exit sometimes fail with virtual threads
>> due to the test exiting before the test threads have exited. A join() for
>>
On Fri, 2 Jun 2023 04:29:16 GMT, Chris Plummer wrote:
>> Virtual threads are always daemon threads, so tests that previously did not
>> explicitly wait for test threads to exit sometimes fail with virtual threads
>> due to the test exiting before the test threads have exited. A join() for
>>
On Fri, 2 Jun 2023 04:29:16 GMT, Chris Plummer wrote:
>> Virtual threads are always daemon threads, so tests that previously did not
>> explicitly wait for test threads to exit sometimes fail with virtual threads
>> due to the test exiting before the test threads have exited. A join() for
>>
> Virtual threads are always daemon threads, so tests that previously did not
> explicitly wait for test threads to exit sometimes fail with virtual threads
> due to the test exiting before the test threads have exited. A join() for
> each test thread is needed to fix this issue.
>
>
On Thu, 1 Jun 2023 23:03:47 GMT, Chris Plummer wrote:
> Virtual threads are always daemon threads, so tests that previously did not
> explicitly wait for test threads to exit sometimes fail with virtual threads
> due to the test exiting before the test threads have exited. A join() for
> each
On Thu, 1 Jun 2023 23:03:47 GMT, Chris Plummer wrote:
> Virtual threads are always daemon threads, so tests that previously did not
> explicitly wait for test threads to exit sometimes fail with virtual threads
> due to the test exiting before the test threads have exited. A join() for
> each
Virtual threads are always daemon threads, so tests that previously did not
explicitly wait for test threads to exit sometimes fail with virtual threads
due to the test exiting before the test threads have exited. A join() for each
test thread is needed to fix this issue.
