[06:20:13] <Amir1>	 https://bash.toolforge.org/quip/1ywtOHkBa_6PSCT9viLy
[09:52:11] <addshore>	 We recently upped the timeouts in those tests from 10 seconds to 30 seconds to deal with the slowness of CI. thats the only cause of this flakiness that I have seen.
[09:52:43] <addshore>	 If there is still a ticket open it should probably be merged into https://phabricator.wikimedia.org/T281122
[20:47:36] <Krinkle>	 TimStarling: btw, related to critical sections - https://phabricator.wikimedia.org/T193565 - this is in "Ready for review" currently. What can/should we do next here?
[23:39:18] <ori>	 Krinkle: the prototype ChessBrowser requires JavaScript to display an interactive board. If JavaScript is disabled, we show a message "JavaScript is not enabled on this page. To view the game interactively, please enable JavaScript." Is that the right thing to do? I'm thinking it's better to not plaster that message on the page.
[23:45:27] <Krinkle>	 ori: aye, if there's some kind of useful fallback image that can be rendered in html/css that'd be great (and then maybe not bother with mentioning what more there could be). If not, I think a message like that might be fine, but I'd avoid putting it in the parser output, and instead using .client-nojs .foo to display that so that 1) it's not there in contexts where JS isn't a thing or where enabling it wouldn't help (e.g. apple 
[23:45:27] <Krinkle>	 dictionary lookup and other parsoid/html+css-only cases), and 2) making sure that it's displayed on our sites for all Grade C users, not just people with Grade A-capable browsers that intentionally turned of JS.