I don't get this. I do the test locally, they all pass. I submit it directly to testbot and they all pass. I submit the patch and i get these nonsense failures.
"should return piX=0 not 0"? seems like 0 == 0 to me. They are both int values...
Is this just testbot being strange? -aric On 8/24/11 4:56 PM, Marvin wrote:
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at http://testbot.winehq.org/JobDetails.pl?Key=13681 Your paranoid android. === WNT4WSSP6 (32 bit usp10) === usp10.c:1931: Test failed: ScriptCPtoX trailing: iCP=8 should return piX=0 not 0 === W2KPROSP4 (32 bit usp10) === usp10.c:1931: Test failed: ScriptCPtoX trailing: iCP=8 should return piX=0 not 0 === WXPPROSP3 (32 bit usp10) === usp10.c:1931: Test failed: ScriptCPtoX trailing: iCP=8 should return piX=0 not 0 === W2K3R2SESP2 (32 bit usp10) === usp10.c:1931: Test failed: ScriptCPtoX trailing: iCP=8 should return piX=0 not 0 === WVISTAADM (32 bit usp10) === usp10.c:1931: Test failed: ScriptCPtoX trailing: iCP=8 should return piX=0 not 0 === W2K8SE (32 bit usp10) === usp10.c:1931: Test failed: ScriptCPtoX trailing: iCP=8 should return piX=0 not 0 === W7PRO (32 bit usp10) === usp10.c:1931: Test failed: ScriptCPtoX trailing: iCP=8 should return piX=0 not 0 === W7PROX64 (32 bit usp10) === usp10.c:1931: Test failed: ScriptCPtoX trailing: iCP=8 should return piX=0 not 0
