Bruno Faccini

> Test results look good to me :) Let's review and land the other PR then. Well looks like I will need to merge with recent master to fix the...

Hmmm, there are only 2 tests failures during `Hardware Medium` stage ... 1) the timeout during `23-./daos_test/suite.py:DaosCoreTest.test_daos_rebuild_ec`looks definitely like the issue reported in [DAOS-9860](https://daosio.atlassian.net/browse/DAOS-9860) and still under investigations , but...

Looks like the only CI test failure is a timeout during `daos_test/suite.py:DaosCoreTest.test_daos_rebuild_ec` which is unrelated to my changes and better looks as the problem described in [DAOS-9861](https://daosio.atlassian.net/browse/DAOS-9861)/[DAOS-9860](https://daosio.atlassian.net/browse/DAOS-9860) which is still...

Again, looks like the only CI test failure is a timeout during daos_test/suite.py:DaosCoreTest.test_daos_rebuild_ec that seems to be unrelated to my changes and better looks as the problem described in [DAOS-9861](https://daosio.atlassian.net/browse/DAOS-9861)/[DAOS-9860](https://daosio.atlassian.net/browse/DAOS-9860)...

@NiuYawei and @gnailzenh would be cool if you could review when you have some time ;-)

Abandoning this PR, now that problem has been identified and it is suspected to be fixed by [PR-9667](https://github.com/daos-stack/daos/pull/9667) which has landed.

Looks like these changes must be pushed finally, as found in [DAOS-11832](https://github.com/daos-stack/daos/pull/9924) associated coredumps.

The only 2 tests failures for the last CI session : ``` Existing failures - 2 Test Hardware / Functional Hardware Medium / 3-./osa/online_extend.py:OSAOnlineExtend.test_osa_online_extend_oclass;run-aggregation-checksum-container-daos_racer-extra_servers-hosts-ior-client_processes-iorflags-job_manager-loop_test-mdtest-wr_size-32K-pool-rebuild-server_config-servers-0-1-setup-test_obj_class-test_ranks-9fd5 – FTEST_osa.OSAOnlineExtend Test Hardware / Functional...

Hello, First of all, many thanks for your detailed comments/proposals. I agree that ABT_key feature/mechanism seems to allow fixing the external stack management needs upon ULT exit. And I think...

Hello Shintaro, Thanks for your precisions, so did I correctly understand that "Lazy stack allocation" is intended to behave like a one-shot "cactus stack" upon ABT_thread_yield()/ABT_mutex_lock() (and more generally upon...