composable_guard test is broken when having more than one thread

[sithhell]

Currently, the composable guard test fails to run on more than 1 OS thread.
The main reason is because the tasks started with run_guarded can not be synchronized on, leading to the fact that the apply function gets executed after the call to hpx::finalize. I think it would be wise for those functions to return a hpx::unique_future of some sorts.

[hkaiser]

Any news on this?

[stevenrbrandt]

I added a future, as suggested.

[stevenrbrandt]

Should be fixed now.

[hkaiser]

For the records, this was fixed by 786918a and 12a9bac.

However I believe that you should still leave that call to hpx::finalize in place. Does the test even exit properly without it?

[stevenrbrandt]

It executes fine for me, but I see what you mean. 2ab6deb puts the hpx::finalize back in place.