Jim Garlick

The default state of nodes is down. Is there a situation where they need to be forced down after having been mocked up or actually up? (like shrinking back down)?...

This option: `--setattr=exec.test.run_duration=1ms` says instead of actually running the job, just sleep for a millisecond.

The resource.acquire protocol is described here: https://flux-framework.readthedocs.io/projects/flux-rfc/en/latest/spec_28.html Basically scheduler starts up and asks resource "what resources do I have"? Resource says here's a pile of nodes/cores whatever and none of...

I think you got it! The actual command shouldn't matter. If you mix real and fake resources, the scheduler doesn't know which is which so it'll be fine if you...

OK. I feel like we should take it out of this issue though as the original topic is pretty important and the results presented above are significant and deserve some...

That does seem like a good case for disabling the exit timeout behavior by default. FWIW, I've hit this too when running stuff that's not MPI in parallel (e.g. using...

Well maybe a topic for discussion anyway :-)

Those are sensible arguments IMHO. Well, anyway, it's a bit off topic for this issue so we can take it up elsewhere if need be. (But I'm content for now)

It would be cool to have go bindings for flux-core, especially if it worked "natively" with goroutines and so on. I'd like to propose that, while flux-core is still undergoing...

Great job running this down. Hmm, I belive the future takes a reference on the flux_t handle which for a broker module contains one end of a zeromq socket for...