Talk:Pikmin (GC)

Anonymous tests
There's two anonymous tests on the page for and an entry for it in version compatibility. However no such revision exists on the Dolphin site if you click the link. I even went back in the master download list and found the gap where it's supposed to be, and it's not there. - Xerxes (talk) 11:48, 4 January 2018 (CET)
 * Nice find, I vote to remove them, their testing results are already sketchy. I have a crazy thought, thinking of creating a script with pretty exhaustive list of actually existing revisions and ship into template:Testing/entry, they will run through testing entries for bogus Dolphin revisions. I can feel there's massive performance hit coming if we do that. We will catch every bogus testing entries that way, then revert the changes to template:Testing/entry if we still feel scary about it. Lucario (talk) 02:06, 7 January 2018 (CET)


 * I went ahead and removed them. It may be possible to do what you're suggesting, but I highly doubt it's possible from within the wiki. There's a 200 loop limit on every page which we've been carefully skirting around. I was testing sorting algorithms on my user page for something similar (sorting test entries/dates in infobox maybe) but after around 13-15 elements in the list, I would hit the maximum loop counter. Now imagine some kind of loop going through every test revision; not going to happen. With outside scripting though, sure. - Xerxes (talk) 08:36, 7 January 2018 (CET)
 * Actually, I cannot think of good script that will do the job but it'd be badass if we can think of one. Lucario (talk) 09:52, 7 January 2018 (CET)


 * If we had an index of some sort of all valid builds, it could probably be done. Something that compares the revision number against the index to see if it's in there or not; if it is it returns a success, if not a fail. But that would need to hook into buildbot probably in order to keep the index up to date. - Xerxes (talk) 10:13, 7 January 2018 (CET)
 * Actually maybe we could just generate an index from the git repo? I've never used git so I don't know if/how it stores the revision numbers in the format Dolphin uses, or how it handles the old SVN builds. I'll try to do some research and tinkering around with it this week, it sounds fun. - Xerxes (talk) 12:15, 7 January 2018 (CET)
 * I'm making hypothetical what it'll mean when we actually got full list of valid revisions off from somewhere, I've created batch file that will output count from 1 to 9000 for /l %%i in (1,1,9000) do (echo %%i>>lol.txt) then used Notepad++'s regex to replace linebreaks to add "4.0-" and then add Wiki's regex args, apparently regex can only look for ~3500 matches each, and you're looking at ~3 seconds per regex. It'd be unimaginable what it'll mean to every test entry there are on this site. Lucario (talk) 03:34, 8 January 2018 (CET)


 * I was thinking not to use the wiki's regex tools or other extensions at all. Have the testing entry template interact with javascript and have the javascript contain the hard stuff. Maybe even do it in bash and input git commands server side so you can directly do something like, and depending on the output of git give a success/fail, then we don't have to worry about algorithms at all and can make git handle it. If you do  ,  , then   you actually get the version number back out like "5.0-6152-gdc08b73db1", but git really doesn't like referring to version numbers because of its decentralization. I couldn't even figure out how to get that style of formatting output for older builds to make an index, or how to reference builds in master by the build number (it thinks that "5.0-6152" is ambiguous, and wants you to give it some of the sha-1 hash). - Xerxes (talk) 09:09, 8 January 2018 (CET)