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.
3 total, 1 approved, 0 rolled up, 1 failed / /
|Sort key||#||Status||Mergeable||Title||Head ref||Assignee||Approved by||Priority||Rollup|
|1||207||yes||Enable specialization with aHash||tkaitchuck:specialize||0|
|2||205||no||Reduce the amount of llvm IR instantiated||Marwes:smaller_ir||0|
|3||214||failure||yes||Switch serde test to fnv to avoid 32bit issues||tkaitchuck:hashorder||Amanieu||0|
Open retry log