This will create a new pull request consisting of 0 PRs.
A rollup is useful for shortening the queue, but jumping the queue is unfair to older PRs who have waited too long.
When creating a real rollup, try to be fair to the PRs not rolled up. You may pick one of these strategies:
Always include the first approved PR in the rollup. Then give the new pull request the highest priority (p=100);
After creating the rollup, give it a fairly high priority (p=10), then assign even higher priorties (p=20, ...) to every PRs older than the oldest rolled up PR.
4 total, 0 approved, 0 rolled up, 0 failed / /
|Sort key||#||Status||Mergeable||Title||Head ref||Assignee||Approved by||Priority||Rollup|
|1||903||yes||fix discriminant handling||RalfJung:discriminant||0|
|2||905||yes||Stub out pthread_rwlock_trywrlock and pthread_rwlock_tryrdlock||Aaron1011:shim/pthread-try||0|
|3||914||yes||Use host's rng when communication is enabled||christianpoveda:use-host-rng||0|
|4||813||no||[WIP] Support for automatically shimming dynamic libraries||Aaron1011:feature/ffi||0|
Open retry log