Closed timvandermeij closed 3 months ago
/botio-linux preview
Command cmd_preview from @timvandermeij received. Current queue size: 0
Live output at: http://54.241.84.105:8877/cd0608f94ae4552/output.txt
Full output at http://54.241.84.105:8877/cd0608f94ae4552/output.txt
Total script time: 1.18 mins
/botio test
Command cmd_test from @timvandermeij received. Current queue size: 2
Live output at: http://54.193.163.58:8877/fc40754fda086b5/output.txt
Command cmd_test from @timvandermeij received. Current queue size: 0
Live output at: http://54.241.84.105:8877/65b7373d235b3e2/output.txt
Full output at http://54.241.84.105:8877/65b7373d235b3e2/output.txt
Total script time: 27.02 mins
errors: 730
different ref/snapshot: 50
different first/second rendering: 1
Image differences available at: http://54.241.84.105:8877/65b7373d235b3e2/reftest-analyzer.html#web=eq.log
I'm not really sure what's wrong with Chrome here: it looks like it just... stopped halfway the integration tests? I do recall having seen such weird high number of errors before, and it was usually just a one-time fluke. I'll rebase and retry it later.
Full output at http://54.193.163.58:8877/fc40754fda086b5/output.txt
Total script time: 43.46 mins
different ref/snapshot: 9
Image differences available at: http://54.193.163.58:8877/fc40754fda086b5/reftest-analyzer.html#web=eq.log
/botio-linux test
Command cmd_test from @timvandermeij received. Current queue size: 0
Live output at: http://54.241.84.105:8877/e760630018db0d7/output.txt
Full output at http://54.241.84.105:8877/e760630018db0d7/output.txt
Total script time: 28.79 mins
different ref/snapshot: 56
different first/second rendering: 1
Image differences available at: http://54.241.84.105:8877/e760630018db0d7/reftest-analyzer.html#web=eq.log
/botio-linux preview
Command cmd_preview from @timvandermeij received. Current queue size: 0
Live output at: http://54.241.84.105:8877/64a9d44e17dee7a/output.txt
Full output at http://54.241.84.105:8877/64a9d44e17dee7a/output.txt
Total script time: 1.07 mins
/botio makeref
Command cmd_makeref from @timvandermeij received. Current queue size: 0
Live output at: http://54.241.84.105:8877/de62e4d6937f0f9/output.txt
Command cmd_makeref from @timvandermeij received. Current queue size: 1
Live output at: http://54.193.163.58:8877/d56d77caf086036/output.txt
Full output at http://54.241.84.105:8877/de62e4d6937f0f9/output.txt
Total script time: 20.09 mins
Full output at http://54.193.163.58:8877/d56d77caf086036/output.txt
Total script time: 24.52 mins
The commit messages contain more details about the individual changes. Notes for the reviewer:
eslint-plugin-jasmine
update contains support for ESLint 9 (see https://github.com/tlvince/eslint-plugin-jasmine/releases/tag/v4.2.0), which brings us another step closer for #17928.@metalsmith/markdown
update is interesting because that one should already have been part of #18248. I don't know what happened exactly, but I somehow managed to mess up the version number there and probably copy/pasted the older one.puppeteer
update contains some bugfixes and Chrome updates that could benefit us (see https://github.com/puppeteer/puppeteer/releases), but note that this version does not yet contain the fix for https://github.com/GoogleChromeLabs/chromium-bidi/issues/2317 because even though it's released thechromium-bidi
bump has not been done in the Puppeteer repository yet. (This one was identified in https://github.com/mozilla/pdf.js/issues/17961#issuecomment-2167844445 and could help us get more details as to what's going wrong in the Chrome-on-BiDi PR.)