Ivan PetkovandCarl Lerche b6ecfa251c signal: Add (failing) test case which exibits starvation on drop ...

* Currently, whenever a new signal stream is created we attempt to
register a global pipe with the event loop to drive events.
* We also (correctly) swallow any descriptor-already-registered errors
since the same pipe is always used
* However, we currently *deregister* the same global pipe *any time* a
Signal stream is dropped.
* This means that if 2 or more of Signal instances exist simultaneously
(even if listening for different signals) and one of them is dropped,
the remainder will starve (until any new signal is created again).

2018-09-10 11:30:05 -07:00

..

drop_then_get_a_signal.rs

signal: Split up all integration tests to run in their own process

2018-09-10 11:30:05 -07:00

dropping_does_not_deregister_other_instances.rs

signal: Add (failing) test case which exibits starvation on drop

2018-09-10 11:30:05 -07:00

multi_loop.rs

signal: Split up all integration tests to run in their own process

2018-09-10 11:30:05 -07:00

notify_both.rs

signal: Split up all integration tests to run in their own process

2018-09-10 11:30:05 -07:00

signal.rs

signal: Split up all integration tests to run in their own process

2018-09-10 11:30:05 -07:00

simple.rs

signal: Split up all integration tests to run in their own process

2018-09-10 11:30:05 -07:00

twice.rs

signal: Split up all integration tests to run in their own process

2018-09-10 11:30:05 -07:00