[00:34:47] <MirahezeRelay>	 <posix_memalign> [1/4] https://exttest.mirabeta.org/wiki/Special:ManageWiki/namespaces
[00:34:48] <MirahezeRelay>	 <posix_memalign> [2/4] Only namespaces from extensions are shown. Not reproducible on other mirabeta wikis. 
[00:34:48] <MirahezeRelay>	 <posix_memalign> [3/4] Not sure if it can be fixed easily. If not, I'll create a task on phorge.
[00:34:48] <MirahezeRelay>	 <posix_memalign> [4/4] https://cdn.discordapp.com/attachments/1006789349498699827/1391578159278850069/image.png?ex=686c67a7&is=686b1627&hm=b551a18c513a137d63da88e6442ff4c1e99845d135968a64f8e120779e21d6b6&
[01:24:44] <MirahezeRelay>	 <originalauthority> Likely an issue with inserting the namespaces on wiki creation
[01:39:06] <MirahezeRelay>	 <cosmicalpha, replying to posix_memalign> If it was created during the time I was testing something (where that didn't work) that would be why.
[07:39:54] <MirahezeRelay>	 <posix_memalign> It's not very important. An extension was broken but changing namespaces settings probably wouldn't save it.
[07:40:29] <MirahezeRelay>	 <rhinosf1> We can apply the default namespace settings
[07:41:34] <MirahezeRelay>	 <posix_memalign> This phorge comment is flooded by error logs now. https://issue-tracker.miraheze.org/T13645#279260. Should be create something like a dashboard to track them instead?
[07:42:03] <MirahezeRelay>	 <posix_memalign, replying to rhinosf1> That'll be great. Thanks!
[07:42:42] <MirahezeRelay>	 <rhinosf1, replying to posix_memalign> Stick them in a paste and add links to the task description
[07:42:56] <MirahezeRelay>	 <rhinosf1> Or set max lines
[07:43:06] <MirahezeRelay>	 <rhinosf1> To show so it goes scrollable
[07:54:44] <MirahezeRelay>	 <posix_memalign> Max lines set. It's a lot shorter now.
[07:56:42] <MirahezeRelay>	 <posix_memalign> Though the unsolved issue is tracking the status of about 20 patches. It can be any of `reported`/`patch sent`/`patch merged and ready for another test`. Hopefully the list can stop growing to reduce the workload of tracking errors.
[07:59:10] <MirahezeRelay>	 <posix_memalign> So far, about 60 extensions don't have any issues whiles more than 20 error reports were generated. This ratio does not paint a bright picture...
[08:01:05] <MirahezeRelay>	 <rhinosf1, replying to posix_memalign> No
[11:20:49] <MirahezeRelay>	 <pskyechology> if i have to fix more tests just so that a simple import patch would pass CI, i will explode
[11:58:20] <MirahezeRelay>	 <rhinosf1, replying to pskyechology> Which extension?
[12:00:34] <MirahezeRelay>	 <pskyechology, replying to rhinosf1> [1/2] createdpageslist
[12:00:34] <MirahezeRelay>	 <pskyechology, replying to rhinosf1> [2/2] https://gerrit.wikimedia.org/r/1166496
[12:01:00] <MirahezeRelay>	 <pskyechology> could use a recheck, wouldn't be surprised if it still fails :3
[12:01:24] <MirahezeRelay>	 <rhinosf1> Sigh
[12:01:38] <MirahezeRelay>	 <rhinosf1> Why don't you add yourself to the Jenkins whitelist ?
[12:01:52] <MirahezeRelay>	 <pskyechology> it's waiting for approval for someone
[12:02:04] <MirahezeRelay>	 <rhinosf1> Patch link?
[12:03:03] <MirahezeRelay>	 <pskyechology> oop nevermind it got approved
[12:03:13] <MirahezeRelay>	 <pskyechology> yay I can finally stop begging
[12:07:00] <MirahezeRelay>	 <pskyechology> oh my god it passed too
[12:09:45] <MirahezeRelay>	 <rhinosf1> Nice
[12:18:32] <MirahezeRelay>	 <rhinosf1> Do you need a +2 @pskyechology ?
[12:21:52] <MirahezeRelay>	 <pskyechology, replying to rhinosf1> sure
[12:22:05] <MirahezeRelay>	 <rhinosf1> @paladox can you do the honours?
[13:19:33] <MirahezeRelay>	 <rhinosf1> @pskyechology paladox did, do you need backports or?
[13:52:30] <MirahezeRelay>	 <pskyechology, replying to rhinosf1> [1/2] i dont think so, no
[13:52:30] <MirahezeRelay>	 <pskyechology, replying to rhinosf1> [2/2] REL1_44 cherrypick also needs approving though https://gerrit.wikimedia.org/r/1166498
[13:55:43] <MirahezeRelay>	 <rhinosf1> @paladox
[14:17:09] <MirahezeRelay>	 <pskyechology> \o/
[23:55:56] <MirahezeRelay>	 <posix_memalign> Out of curiosity: what would happen if we run `php tests/parser/parserTests.php` on Mirabeta? Will is run all parser tests for all extensions enabled on a particular wiki?
[23:56:51] <MirahezeRelay>	 <posix_memalign> If so, that should catch a lot of import errors without the need to manually invoke an extension.
[23:56:56] <MirahezeRelay>	 <pixldev> knowing mediawiki
[23:57:08] <MirahezeRelay>	 <pixldev> we may need a new cloud server
[23:57:12] <MirahezeRelay>	 <posix_memalign> Probably depends on how ManageWiki is implemented? Idk how it manages extensions for multiple wikis
[23:58:19] <MirahezeRelay>	 <posix_memalign, replying to pixldev> It shouldn't be too bad if the test is not multithreaded? Might take forever but shouldn't be a huge burden on the server.