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.
7 total, 0 approved, 0 rolled up, 0 failed / /
|Sort key||#||Status||Mergeable||Title||Head ref||Assignee||Approved by||Priority||Rollup|
|1||693||yes||Support unwinding after a panic||Aaron1011:feature/panic_unwind_final||0|
|2||961||yes||Use the upstream `exact_div` implementation||rust-lang:exact_div_reuse||0|
|3||975||yes||Add clock_gettime shim||christianpoveda:clock-shim||0|
|4||980||yes||change cargo-miri.rs to fix issue #978||JOE1994:master||0|
|5||987||yes||Error when there is an unsupported flag for opening a file||christianpoveda:check-unsupported-fs-flags||0|
|6||991||yes||Change the last OS error location to a place||christianpoveda:errno-place||0|
|7||993||yes||Add OsString from/to bytes helper functions||christianpoveda:os_string_helper||0|
Open retry log