Age | Commit message (Collapse) | Author | |
---|---|---|---|
2017-11-30 | Tighten timings in dirty_*if_SUITE:dirty_scheduler_exit | John Högberg | |
There doesn't seem to be any science behind the long delays, and the (newly introduced) dry run forces us to eat them twice, so they've been shortened to more reasonable values. | |||
2017-11-30 | Fix dirty_*if_SUITE after file rewrite | John Högberg | |
Code loading is done through dirty IO now, causing the dirty_scheduler_exit tests to fail as they block their own progress by invoking erts_debug:dirty_io(wait, _); the spawned processes will exit normally before we have a chance to kill them. To get around this, we perform a dry run to ensure that all required code is loaded. It isn't particularly pretty (or fast) but it saves us the hassle of maintaining a module list (cf. embedded mode). | |||
2017-06-13 | Remove unused functions in test emulator test suites | Björn Gustavsson | |
2017-05-04 | Update copyright year | Raimo Niskanen | |
2017-01-17 | Always return info from system_info(dirty_[cpu|io]_schedulers*) | Rickard Green | |
2017-01-12 | Support for dirty BIFs | Rickard Green | |