If you run `m -j blueprint_tools` does that also hang? (if so, then that should be a faster way to test it).
Do you find that it reliably hangs or only sometimes hangs?
If you run that command on its own does it produce any helpful output?
If it doesn't produce any helpful output, you could modify line 53 of build/soong/finder/finder_test.go so that instead of saying
'logger := log.New(ioutil.Discard, "", 0)'
it says
'logger := log.New(os.Stdout, "", 0)'
and then retest it (`m -j blueprint_tools`).
You could temporarily delete tests from build/soong/finder/finder_test.go until it stops hanging, in order to determine specifically which test is hanging.
I'll see if I can reproduce the problem too.