Update browser-ui-test version#93597
Conversation
|
@bors r+ rollup |
|
📌 Commit 1dbdfc4 has been approved by |
…st, r=jsha Update browser-ui-test version The puppeteer version update is limited because new versions has some "interesting" flaws. r? `@jsha`
…st, r=jsha Update browser-ui-test version The puppeteer version update is limited because new versions has some "interesting" flaws. r? ``@jsha``
|
Hmmh, I think this might be responsible for this rollup failure / rustdoc test failure: |
|
@matthiaskrgr I doesn't seem related. We can keep it out of rollups if you prefer though. @bors: r=jsha |
|
📌 Commit 1dbdfc4 has been approved by |
…st, r=jsha Update browser-ui-test version The puppeteer version update is limited because new versions has some "interesting" flaws. r? `@jsha`
|
@bors rollup=never another rollup attempt failed, let's see |
|
@bors r- This PR is definitely the cause of the errors, it fails when rebased: |
1dbdfc4 to
1433b95
Compare
010619b to
ef00e3b
Compare
|
I updated a comment in a GUI test to ensure ahead of time that the test isn't failing before r+ing again. |
|
Seems like GUI tests passed so let's go! @bors: r+ |
|
📌 Commit ef00e3b has been approved by |
|
Arf forgot... @bors: r=jsha |
|
💡 This pull request was already approved, no need to approve it again.
|
|
📌 Commit ef00e3b has been approved by |
|
☀️ Test successful - checks-actions |
|
Finished benchmarking commit (291bf94): comparison url. Summary: This benchmark run did not return any relevant results. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
The puppeteer version update is limited because new versions has some "interesting" flaws.
r? @jsha