Failed tests of bin/xplr.rs on CI

[sux2mfgj]

This issue is for a TODO on xplr.rs.

    // TODO: Fix running GitHub action
    ... some comment outed tests are followed.

I started to investigate this problem.

Similar problem is occurred when I add a test for a xplr runner. The test just creates runner with default parameter and calls run(). A commit of the test is here in my forked repo.

A stack trace of the error is shown in a ci log

  17:     0x557526a112d2 - xplr::explorer::explore_async::{{closure}}::{{closure}}::hb453dff62ee96be8
                               at /home/runner/work/xplr/xplr/src/explorer.rs:59:17
  18:     0x557526a579e4 - core::result::Result<T,E>::map::he62c99987df2a27f
                               at /rustc/c8dfcfe046a7680554bf4eb612bad840e7631c4b/library/core/src/result.rs:748:25
  19:     0x557526a1152f - xplr::explorer::explore_async::{{closure}}::hb4c612bd0ae2e168
                               at /home/runner/work/xplr/xplr/src/explorer.rs:57:9

I'll update this issue. If you have some related information, please update to here.
Thanks.

[sayanarijit]

Hey @sux2mfgj thanks for investigating this issue. It could be a threading related issue. It's just a guess, but I think GH runner is preventing xplr from spawning multiple threads.
It's possible to debug this by directly ssh-ing into the runners (there are github actions for that in the marketplace) and run xplr with debug logs (or just printlns).