Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upSync WPT with upstream (23-01-2020) #25583
Conversation
…3d9cdc17d
|
@bors-servo r+ |
|
|
…wpt-sync Sync WPT with upstream (23-01-2020) Automated downstream sync of changes from upstream as of 23-01-2020. [no-wpt-sync] r? @servo-wpt-sync
|
|
|
@bors-servo retry |
…wpt-sync Sync WPT with upstream (23-01-2020) Automated downstream sync of changes from upstream as of 23-01-2020. [no-wpt-sync] r? @servo-wpt-sync
|
|
|
@bors-servo retry |
…wpt-sync Sync WPT with upstream (23-01-2020) Automated downstream sync of changes from upstream as of 23-01-2020. [no-wpt-sync] r? @servo-wpt-sync
|
|
|
@bors-servo retry |
…wpt-sync Sync WPT with upstream (23-01-2020) Automated downstream sync of changes from upstream as of 23-01-2020. [no-wpt-sync] r? @servo-wpt-sync
|
|
|
@bors-servo retry |
…wpt-sync Sync WPT with upstream (23-01-2020) Automated downstream sync of changes from upstream as of 23-01-2020. [no-wpt-sync] r? @servo-wpt-sync
|
|
|
@bors-servo retry |
…wpt-sync Sync WPT with upstream (23-01-2020) Automated downstream sync of changes from upstream as of 23-01-2020. [no-wpt-sync] r? @servo-wpt-sync
|
Is it useful to retry when there’s also #25593 in the queue? |
|
We know there's no new incorrect failures introduced in this PR, so it will successfully merge with enough retries. I'm going to close #25459 |
|
|
servo-wpt-sync commentedJan 23, 2020
Automated downstream sync of changes from upstream as of 23-01-2020.
[no-wpt-sync]
r? @servo-wpt-sync