[01:16:20] <Krinkle>	 TimStarling: I think it's a couple of layers unhappily working together. We seem to use a variable prefix, which we perhaps don't need to, that might avoid it (albeit not fix it). There's also the Language destruct issue causing a PHP Notice which might be leading phpunit to report/re-enter something and thus triggering another db clone indirectly, which if we fix that might also make it go away again. But neither appear root causes for 
[01:16:21] <Krinkle>	 the actually reported exception message, in so far that it should be fine to have those other problems happen and reported as such without the db falling apart.
[01:47:47] <TimStarling>	 did you see my debug log analysis? I think I'm pretty close to fully isolating it
[01:48:18] <TimStarling>	 just had to stop for lunch, back at it now
[01:58:48] <Krinkle>	 ack yeah, something not tearing down after parser tests
[23:53:16] <TimStarling>	 user newtalk notification has been broken in core for years
[23:53:57] <TimStarling>	 when you click the notification link, it will always show another notification on the actual page view when you are viewing your own user talk page
[23:54:15] <TimStarling>	 probably since 2018
[23:56:23] <TimStarling>	 and 304 suppression is broken, so the notification will just stay there forever unless you know how to do a force refresh