Due to the exporter becoming asynchronous this morning, the importer will no longer be blocked once the current exports land. I will try running the importer manually after that happens.

One thing we need to be aware of is that if a PR hits a Travis error and the exporter exports more commits after it, the changes in the PR will be reverted on Chromium master until the PR is landed. This is about to happen with:
- https://github.com/w3c/web-platform-tests/pull/5254 
- https://github.com/w3c/web-platform-tests/pull/5307

I have tried to communicate that on the respective CLs and PRs.

In the longer term, one solution is to change what information the importer uses to determine whether it can proceed. I think if we changed the importer from looking at exportable commits on Chromium master to looking at whether there are any in-flight PRs, that would be closer to what we want.

The stuck PRs have been force merged.