Kaleb Barrett
Kaleb Barrett
> Do you think it would make more sense to add _LockBackCompat stuff to 1.9 and do the full switch in 2.0? Yeah probably... I'll just make the change now...
@marlonjames Which changes should be put on 1.9? Just the `.locked` change? Probably also the `.fired` deprecation and also the making private of `_cbhdl`, `_primed`, and `_sim_steps`? Seems like every...
To help us handle the pytest exceptions there is actually `pytest.raises.Exception`, `pytest.warns.Exception`, etc. rather than the dopey way we are doing it now.
Seems like some work needs to be done so that `waves` is passed to `build` and supplies those build arguments implicitly. We are open to PRs.
Waiting on outcome of whether the python installation requirements are correct.
Also have to consider pending cancellations during cleanup.
Okay. New task list. Edited above.
Also, I expect this to have a radically negative performance impact on our serial regressions =/ Every test, no matter how small, now does extra work.
Status update: I'm trying to figure out how to best clean up the scheduler's `_unschedule`, `_abort_test`, and other cleanup functions as there isn't a consistent way that tests are ended...
This is going to be totally reimplemented when other PRs are in.