September 2011 - Wine-Devel

Remove the legalese from start.exe?
by Francois Gouget Sept. 22, 2011

Sept. 22, 2011

Start has the following lines at the end of its usage message: "start.exe version 0.2 Copyright (C) 2003, Dan Kegel\n" "Start comes with ABSOLUTELY NO WARRANTY; for details run with /L option.\n" "This is free software, and you are welcome to redistribute it\n" "under certain conditions; run 'start /L' for details.\n" And also this resource: "start.exe version 0.2 Copyright (C) 2003, Dan Kegel\n" "This program is free software; you can redistribute it and/or\n" "modify it under the terms of the GNU Lesser Public License\n" "as published by the Free Software Foundation; either version 2.1\n" [...] "along with this program; if not, write to the Free Software\n" "Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA.\n" "\n" "See the COPYING.LIB file for license information.\n" We also have another copy of this copyright notice in shell32 for the 'About Wine' dialog but without the 'start.exe' and 'COPYING.LIB' lines, and with 'This program' replaced with 'Wine'. One more copyright notice we have is this in msrle32.rc: "Wine MS-RLE video codec\n" "Copyright 2002 by Michael Guennewig" Now this is all legalese which is a pain to translate (weird vocabulary) and pretty scary too. And because of the small differences the copyright notice needs to be translated twice (though tools like Virtaal/Launchpad may notice the similarity and prefill a fuzzy translation). Also start.exe and msrle32.dll are the only ones to have these notices which seems pretty inconsistent. So what can we do to make this simpler? The simplest would be to remove all copyright notices from start.rc and msrle32.rc. (we would keep the ones in the source of course). I guess that would require Dan's and Michael's approval. The other options involve separating the strings that change from one tool to the next, from those that stay the same. This way the latter will only appear once in the PO file and thus need to be translated only once. The various parts can then trivially be concatenated when they are displayed. (unfortunately this does not help for the msrle32.rc case) For instance we could decide to only keep the 'COPYING.LIB' string and tack it to the end of the usage message. We could also make things more consistent by doing this in every tool. So in pseudo-code we would have something like this: /* Load the tool-specific usage message */ usage_message = load_string(IDS_USAGE); /* Load the generic copying.lib reference. This one is duplicated in * every tool but always the same. */ copying_reference = load_string(IDS_COPYING); /* Print both */ printf(usage_message); printf(copying_reference); Another option would be to reuse the exact same main copyright notice as in the About Wine dialog since we need to translate that anyway (I think it would work wrapping-wise). So the start.exe pseudo-code for showing the license would be something like this: /* Load the copyright notice header, that is: * start.exe version 0.2 Copyright (C) 2003, Dan Kegel * start.exe is part of Wine. */ notice_header = load_string(IDS_NOTICE_HEADER); /* Load the generic Wine copyright notice. Note that it * says 'Wine' like in the 'About Wine' dialog, not 'This program' * and would be the same in any other Wine tool: * Wine is free software; you can redistribute it and/or modify * ... */ notice_generic = load_string(IDS_NOTICE_GENERIC); /* Load the copyright notice trailer: * * See the COPYING.LIB file for license information. */ notice_trailer = load_string(IDS_NOTICE_TRAILER); /* Print all the parts together */ printf(notice_header); printf(notice_generic); printf(notice_trailer); -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ tcA thgirypoC muinelliM latigiD eht detaloiv tsuj evah uoY

3 4

[PATCH 3/5] winealsa.drv: Use the plughw instead of the hw interface for openening devices.
by Joerg-Cyril.Hoehle＠t-systems.com Sept. 22, 2011

Sept. 22, 2011

Henri Verbeet [becoming an audio expert now?] wrote: >The default device may for example be a set of USB speakers or an USB >microphone, in which case you'd have just an output or just an input >respectively. My testcase has been to hack mmdevdrv.c and replace "default" with "plug:dmix" or "dmix" which is an output only device. Expected test result is to behave like most testbot.winehq.org and skip capture tests. Actual output (prior to your patch) last time I tried was some failures. I.e. the mmdevapi render and capture tests suggest that there's no default device for testbots that cannot capture. How does your alsa_try_open interact with devices that clang onto the underlying HW resource for several seconds? (PA does this) Regards, Jörg Höhle

2 1

winetest: Missing test.avi and msrle.avi files
by Francois Gouget Sept. 22, 2011

Sept. 22, 2011

Two Wine tests are skipping tests because they are missing avi test files: * quartz:avisplitter needs a test.avi file: http://source.winehq.org/git/wine.git/?a=history;f=dlls/quartz/tests/avispl… avisplitter.c:210: Tests skipped: Could not read test file "test.avi", skipping test * winmm:mmio needs an msrle.avi file: http://test.winehq.org/data/b6153354dd28c57fb1f92f85df1f1ba751794fc1/mac_fg… mmio.c:77: Tests skipped: msrle.avi file is missing, skipping the test Interestingly there is a test.avi file in the Wine source tree: dlls/qedit/tests/test.avi So where can one procure these test files? Should quartz:avisplitter automatically find qedit:test's test.avi file? Can the missing files be added to Wine? -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ Avoid the Gates of Hell - use Linux.

2 2

Re: po: Update Russian translation
by Francois Gouget Sept. 21, 2011

Sept. 21, 2011

This email is likely to get mangled but the gist of it will hopefully survive. > -"Синтаксис:\tIF [NOT] EXIST файл команда\n" > +"Синтаксис: IF [NOT] EXIST файл команда\n" > "IF [NOT] \"строка1\"==\"строка2\" команда\n" > "IF [NOT] ERRORLEVEL число команда\n" I believe the last two lines should be indented. > +"[/I] Если конечный каталог отсутствует и копируется более одного файла,\n" > +"местом назначения считается каталог.\n" [...] > +"[/A] Копирует только файлы с атрибутом \"архивный\".\n" > +"[/M] Копирует только файлы с атрибутом \"архивный\",\n" > +"при этом очищает атрибут.\n" > +"[/D | /D:m-d-y] Копирует только новые файлы или файлы, измененные\n" > +"после указанной даты. Если дата не указана, заменяет все старые файлы\n" > +"существующими новыми.\n" This one too could use some extra indentation where the description wraps to the next line. Also it is missing an extra trailing '\n'. > #: wordpad.rc:174 > msgid "inch" > msgstr "inch" Based on your exchange with Nikolay Sivov it sounds like this could be translated. > #: cmd.rc:291 xcopy.rc:40 > msgctxt "Yes key" > msgid "Y" > msgstr "" [...same for 'No key'...] > #: xcopy.rc:35 > msgid "%s? (Yes|No)\n" > -msgstr "" > +msgstr "%s? (Yes (да)|No (нет))\n" I believe this one is a bit ambiguous because it does not make it clear whether to type 'Yes' or 'да' (only the first character counts as the 'Yes key' anyway). My understanding is that the two standard ways to deal with this are: * "(Yes|No)" -> "(да|нет)" and "Y" -> "д" This is used for languages where typing the translated strings presents no special challenge. * "(Yes|No)" -> "(да (Y)|нет (N))" and "Y" -> "Y" If typing the translated strings is cumbersome for some reason (but I guess it's not the case here). In truth this approach is mostly used for accelerators. I guess that's because Alt cannot be combined with characters composed through dead keys or special input methods, and also because it avoids trouble with accelerator collisions in case two translations start with the same letter (like if 'Yes' and 'No' both both translated to words starting with 'C' for instance). -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ Vote Electronique: Les gens qui votent ne décident rien. Ceux qui comptent les votes décident de tout.

3 4

Re: [PATCH 5/5] vbscript: Added const statement tests
by Marvin Sept. 21, 2011

Sept. 21, 2011

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=14433 Your paranoid android. === WNT4WSSP6 (32 bit) === No test summary line found === W2KPROSP4 (32 bit) === No test summary line found === WXPPROSP3 (32 bit) === No test summary line found === W2K3R2SESP2 (32 bit) === No test summary line found === WVISTAADM (32 bit) === No test summary line found === W2K8SE (32 bit) === No test summary line found === W7PRO (32 bit) === No test summary line found === W7PROX64 (32 bit) === No test summary line found === TEST64_W7SP1 (32 bit) === No test summary line found === W7PROX64 (64 bit) === No test summary line found === TEST64_W7SP1 (64 bit) === No test summary line found

1 0

Re: [PATCH 1/9] cmd/tests: add tests for command line parsing
by Frédéric Delanoy Sept. 21, 2011

Sept. 21, 2011

On Tue, Sep 20, 2011 at 01:51, Martin Wilck <mwilck(a)arcor.de> wrote: > This patch adds some tests for command line parsing and treatment > of quotes and special characters in the command line and in program > names and parameters. The .exp file was created using Win XP. > --- > programs/cmd/tests/rsrc.rc | 6 + > programs/cmd/tests/test_cmdline.cmd | 159 ++++++++++++++++++++++ > programs/cmd/tests/test_cmdline.cmd.exp | 219 +++++++++++++++++++++++++++++++ > 3 files changed, 384 insertions(+), 0 deletions(-) > create mode 100755 programs/cmd/tests/test_cmdline.cmd > create mode 100755 programs/cmd/tests/test_cmdline.cmd.exp You might want to do a single "@echo off" at the start of the .cmd file. Echoing every command in the .exp isn't very helpful: you don't want to replicate the .cmd contents in the .exp file. Add comments or "subsections" as is done in test_builtins.cmd if necessary, or even better use descriptive results, like e.g. 'text in single quotes' if possible (Also the @ before every rem or echo just add visual clutter IMHO but that's due to the enabled echo mode)

2 3

re: [PATCH 2/9] cmd: use GetCommandline() rather than argv
by Dan Kegel Sept. 21, 2011

Sept. 21, 2011

Hi Martin, on my i7 machine, your patch series fails every time for me when run normally. Here's the log: ]] ../../../tools/runtest -q -P wine -M cmd.exe -T ../../.. -p cmd.exe_test.exe.so batch.c && touch batch.ok ]] ... ]] wine: cannot find L"C:\\windows\\system32\\tell;1;;2.exe" ]] batch.c:301: Test succeeded inside todo block: unexpected char 0x0 position -1 in line 50 (got '0 ', wanted '0(a)space@') ]] batch.c:301: Test failed: unexpected char 0x65 position 0 in line 53 (got 'error 9009', wanted '1(a)space@') ]] batch.c:301: Test failed: unexpected char 0x65 position 0 in line 59 (got 'error 9009', wanted '1(a)space@') ]] batch.c:301: Test failed: unexpected char 0x65 position 0 in line 62 (got 'error 9009', wanted '2(a)space@') ]] batch.c:301: Test succeeded inside todo block: unexpected char 0x0 position -1 in line 75 (got '"hi"', wanted '"hi"') ]] batch.c:301: Test failed: unexpected char 0x65 position 0 in line 78 (got 'error 9009', wanted '1(a)space@') ]] batch.c:301: Test succeeded inside todo block: unexpected char 0x0 position -1 in line 81 (got '"\"\\"\\\"\\\\" "\"\\"\\\"\\\\"', wanted '"\"\\"\\\"\\\\"@space@"\"\\"\\\"\\\\"') ]] batch.c:301: Test succeeded inside todo block: unexpected char 0x0 position -1 in line 90 (got '1 ', wanted '1(a)space@') ]] batch.c:301: Test succeeded inside todo block: unexpected char 0x0 position -1 in line 93 (got '0 ', wanted '0(a)space@') ]] batch.c:301: Test succeeded inside todo block: unexpected char 0x0 position -1 in line 102 (got '3 ', wanted '3(a)space@') ]] Command exited with non-zero status 10 ]] make: *** [batch.ok] Error 10 ]] make: Target `test' not remade because of errors. When run with WINEDEBUG=warn+heap, it passes. Not sure what to make of that, but something's fishy, and the patch should not go in as is. You might try valgrind to see if it turns anything up. - Dan

3 4

Re: po: Update Russian translation
by Nikolay Sivov Sept. 21, 2011

Sept. 21, 2011

On 9/20/2011 22:33, Alexander Lakhin wrote: > English strings removed, partial translation fixed too. > #: crypt32.rc:53 cryptdlg.rc:31 > -#, fuzzy > msgctxt "Certification Practice Statement" > msgid "CPS" > -msgstr "CPS" > +msgstr "РУЦ" What does that mean exactly? I didn't find such abbreviation anywhere. > #: jscript.rc:48 > -#, fuzzy > msgid "URI to be decoded is incorrect" > msgstr "URI содержит неверные символы" That's not a translation. > #: oleview.rc:114 > msgid "Ask for an in-process handler when calling CoGetClassObject" > msgstr "" > +"Запросить использование обработчика \"в процессе\" при вызове " > +"CoGetClassObject" "Использовать" is better here IMO, you just don't say the way you translated it. > "\n" > "Например:\n" > " wineconsole cmd\n" > -"Запустить командный процессор Wine в консоли Wine\n" > +"Открывает командное приглашение Wine в консоли Wine.\n" > "\n" This was better before change. > #: wordpad.rc:173 > -#, fuzzy > msgctxt "unit: inch" > msgid "in" > -msgstr "in" > +msgstr "дм" There's no common short name for inch AFAIK, "дм" is used for decimetre. > #: wordpad.rc:175 > -#, fuzzy > msgctxt "unit: point" > msgid "pt" > -msgstr "pt" > +msgstr "пт" I'm not sure about this.

2 1

Re: [PATCH 1/2] include: add a generic class factory template
by Octavian Voicu Sept. 20, 2011

Sept. 20, 2011

On Tue, Sep 20, 2011 at 4:05 PM, Bernhard Loos <bernhardloos(a)googlemail.com> wrote: > +# define __WINE_GENERIC_CF_DLL_MAIN_CONTENT \ > + return __WINE_PS_ENTRY(DllMain(hInstDll, fdwReason, lpv)); I think __WINE_PS_ENTRY needs only be applied to DllMain, not its argument, so second line should read: + return __WINE_PS_ENTRY(DllMain)(hInstDll, fdwReason, lpv); Octavian

1 0

Daily builds of latest Git now available as Ubuntu packages
by Scott Ritchie Sept. 20, 2011

Sept. 20, 2011

For an easier user testing experience, you can now install the latest git as a convenient Ubuntu package. The instructions are very similar to using the standard Ubuntu packages, however the PPA name is different. Instead of ppa:ubuntu-wine/ppa, you add ppa:ubuntu-wine/daily. >From a terminal: sudo add-apt-repository ppa:ubuntu-wine/daily sudo apt-get update sudo apt-get install wine1.3 The packages are versioned like wine1.3-1.3.27+daily-20110901. Limitations: The major version number is based on the latest released version of the Ubuntu packages, so on release days you might see something like 1.3.27+daily-20110909 which would actually be equivalent 1.3.28. If I get especially behind and don't update the official packages after Monday, you might even see a "1.3.27+daily" that's actually ahead of 1.3.28. In all cases wine --version should return what it normally does, however - this is just the package revision that is being wonky. Possible future: These packages are a convenient way to run some tests that may be much too slow for testbot to run against every patch, such as autohotkey-based application automation. Thanks, Scott Ritchie

6 9

Re: [PATCH 1/3] shell32: Don't call SendMessage inside critical section
by Alexandre Julliard Sept. 20, 2011

Sept. 20, 2011

Piotr Caban <piotr(a)codeweavers.com> writes: > @@ -355,24 +351,34 @@ void WINAPI SHChangeNotify(LONG wEventId, UINT uFlags, LPCVOID dwItem1, LPCVOID > if( !notify ) > continue; > > - ptr->pidlSignaled = ILClone(Pidls[0]); > + item = SHAlloc(sizeof(struct notification_recipients)); > + if(!item) { > + ERR("out of memory\n"); > + continue; > + } This one is never freed. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: [2/2] shell32: Be safe against removal of entries in SHChangeNotify
by Piotr Caban Sept. 20, 2011

Sept. 20, 2011

Hi, On 09/19/11 20:52, André Hentschel wrote: > @@ -325,7 +325,7 @@ void WINAPI SHChangeNotify(LONG wEventId, UINT uFlags, LPCVOID dwItem1, LPCVOID > EnterCriticalSection(&SHELL32_ChangenotifyCS); > > /* loop through the list */ > - LIST_FOR_EACH_ENTRY( ptr,&notifications, NOTIFICATIONLIST, entry ) > + LIST_FOR_EACH_ENTRY_SAFE( ptr, next,&notifications, NOTIFICATIONLIST, entry ) The function should not call SendMessage inside critical section. Cheers, Piotr

1 0

Re: [PATCH 4/5] vbscript: Added more tests
by Marvin Sept. 20, 2011

Sept. 20, 2011

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=14413 Your paranoid android. === WNT4WSSP6 (32 bit) === No test summary line found === W2KPROSP4 (32 bit) === No test summary line found === WXPPROSP3 (32 bit) === No test summary line found === W2K3R2SESP2 (32 bit) === No test summary line found === WVISTAADM (32 bit) === No test summary line found === W2K8SE (32 bit) === No test summary line found === W7PRO (32 bit) === No test summary line found === W7PROX64 (32 bit) === No test summary line found === TEST64_W7SP1 (32 bit) === No test summary line found === W7PROX64 (64 bit) === No test summary line found === TEST64_W7SP1 (64 bit) === No test summary line found

1 0

Re: [PATCH 3/5] vbscript: Added support for short if statements
by Marvin Sept. 20, 2011

Sept. 20, 2011

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=14412 Your paranoid android. === WNT4WSSP6 (32 bit) === No test summary line found === W2KPROSP4 (32 bit) === No test summary line found === WXPPROSP3 (32 bit) === No test summary line found === W2K3R2SESP2 (32 bit) === No test summary line found === WVISTAADM (32 bit) === No test summary line found === W2K8SE (32 bit) === No test summary line found === W7PRO (32 bit) === No test summary line found === W7PROX64 (32 bit) === No test summary line found === TEST64_W7SP1 (32 bit) === No test summary line found === W7PROX64 (64 bit) === No test summary line found === TEST64_W7SP1 (64 bit) === No test summary line found

1 0

Re: [PATCH 2/5] vbscript: Added support for rem statement-like comments
by Marvin Sept. 20, 2011

Sept. 20, 2011

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=14411 Your paranoid android. === WNT4WSSP6 (32 bit) === No test summary line found === W2KPROSP4 (32 bit) === No test summary line found === WXPPROSP3 (32 bit) === No test summary line found === W2K3R2SESP2 (32 bit) === No test summary line found === WVISTAADM (32 bit) === No test summary line found === W2K8SE (32 bit) === No test summary line found === W7PRO (32 bit) === No test summary line found === W7PROX64 (32 bit) === No test summary line found === TEST64_W7SP1 (32 bit) === No test summary line found === W7PROX64 (64 bit) === No test summary line found === TEST64_W7SP1 (64 bit) === No test summary line found

1 0

Re: [PATCH 1/5] vbscript: Added support for ':' as statement separator
by Marvin Sept. 20, 2011

Sept. 20, 2011

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=14410 Your paranoid android. === WNT4WSSP6 (32 bit) === No test summary line found === W2KPROSP4 (32 bit) === No test summary line found === WXPPROSP3 (32 bit) === No test summary line found === W2K3R2SESP2 (32 bit) === No test summary line found === WVISTAADM (32 bit) === No test summary line found === W2K8SE (32 bit) === No test summary line found === W7PRO (32 bit) === No test summary line found === W7PROX64 (32 bit) === No test summary line found === TEST64_W7SP1 (32 bit) === No test summary line found === W7PROX64 (64 bit) === No test summary line found === TEST64_W7SP1 (64 bit) === No test summary line found

1 0

Re: [PATCH 3/3 try3] wshom.ocx: Added beginning WshShell object tests
by Marvin Sept. 20, 2011

Sept. 20, 2011

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=14409 Your paranoid android. === WINEBUILD (build) === Can't determine base name

1 0

Re: [PATCH 3/3 try3] wshom.ocx: Added beginning WshShell object tests
by Marvin Sept. 20, 2011

Sept. 20, 2011

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=14409 Your paranoid android. === WINEBUILD (build) === Can't determine base name

1 0

Re: [PATCH 3/3 try3] wshom.ocx: Added beginning WshShell object tests
by Marvin Sept. 20, 2011

Sept. 20, 2011

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=14409 Your paranoid android. === WINEBUILD (build) === Can't determine base name

1 0

Re: [PATCH 1/3 try2] wshom.ocx: Added WshShell class factory implementation
by Marvin Sept. 20, 2011

Sept. 20, 2011

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=14406 Your paranoid android. === WINEBUILD (build) === Can't determine base name

1 0

re: [PATCH 1/3] wshom.ocx: Added WshShell class factory implementation
by Dan Kegel Sept. 20, 2011

Sept. 20, 2011

build failed here? ../../tools/makedep -C. -S../.. -T../.. shell.c wshom_main.c wshom.rc wshom.idl wshom.idl wshom.tlb wshom_private.h: No such file or directory wshom_private.h was first included from shell.c:19 make[1]: *** [depend] Error 1 make[1]: Leaving directory `/home/bob/wineslave.dir/sandbox/slave/runtests-default/build/dlls/wshom.ocx' make: *** [dlls/wshom.ocx/__depend__] Error 2 make: *** Waiting for unfinished jobs....

2 1

Re: msi: Print the string and not the pointer in a TRACE.
by Hans Leidekker Sept. 20, 2011

Sept. 20, 2011

On Mon, 2011-09-19 at 21:24 +0200, Michael Stefaniuc wrote: > @@ -489,7 +489,7 @@ UINT WINAPI MsiGetSourcePathA( MSIHANDLE hInstall, LPCSTR szFolder, > awstring str; > UINT r; > > - TRACE("%s %p %p\n", debugstr_a(szFolder), debugstr_a(szPathBuf), pcchPathBuf); > + TRACE("%s %s %p\n", debugstr_a(szFolder), debugstr_a(szPathBuf), pcchPathBuf); szPathBuf is an output buffer.

2 2

Re: [1/2] d3dx9: Implemented D3DXWeldVertices.
by Michael Mc Donnell Sept. 20, 2011

Sept. 20, 2011

Hi Alexandre My D3DXWeldVertices patch set (see [1] and [2]) scrolled of the patches list . It has been reviewed by Stefan and others on wine-devel, so it should be ok. Do you see anything wrong with it? Should I resend it? Thanks, Michael Mc Donnell [1] http://www.winehq.org/pipermail/wine-patches/2011-August/105423.html [2] http://www.winehq.org/pipermail/wine-patches/2011-August/105422.html

1 0

Re: [PATCH 9/9] cmd/tests: adapt TODOs in test output (parameter passing)
by Marvin Sept. 20, 2011

Sept. 20, 2011

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=14400 Your paranoid android. === WNT4WSSP6 (32 bit) === batch.c:298: Test failed: excess characters on line 17 (got 'error 1', wanted '') batch.c:295: Test failed: unexpected end of line 18 (got '', wanted '>call say "one" ') batch.c:301: Test failed: unexpected char 0x3e position 0 in line 19 (got '>call say "one" ', wanted '0(a)space@') batch.c:298: Test failed: excess characters on line 20 (got '0 ', wanted '') batch.c:295: Test failed: unexpected end of line 21 (got '', wanted '>call s"ay one ') batch.c:301: Test failed: unexpected char 0x3e position 0 in line 22 (got '>call s"ay one ', wanted '1(a)space@') batch.c:298: Test failed: excess characters on line 23 (got '1 ', wanted '') batch.c:301: Test failed: unexpected char 0x65 position 0 in line 24 (got 'error 1', wanted '>call s"aytwo ') batch.c:295: Test failed: unexpected end of line 25 (got '', wanted '2(a)space@') batch.c:298: Test failed: excess characters on line 26 (got '>call s"aytwo ', wanted '') batch.c:301: Test failed: unexpected char 0x32 position 0 in line 27 (got '2 ', wanted '>call say (3) ') batch.c:301: Test failed: unexpected char 0x65 position 0 in line 28 (got 'error 1', wanted '0(a)space@') batch.c:301: Test failed: unexpected char 0x3e position 0 in line 30 (got '>call say (3) ', wanted '>call "say (3)" ') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 31 (got '0 ', wanted '3(a)space@') batch.c:301: Test failed: unexpected char 0x3e position 0 in line 33 (got '>call "say (3)" ', wanted '>call say" (3)" ') batch.c:301: Test failed: unexpected char 0x3e position 0 in line 36 (got '>call say" (3)" ', wanted '>call say" "(3) prints 4?! ') batch.c:301: Test failed: unexpected char 0x33 position 0 in line 37 (got '3 ', wanted '4(a)space@') batch.c:301: Test failed: unexpected char 0x65 position 0 in line 38 (got 'error 1', wanted '------ Testing invocation with CMD /C -------------') batch.c:301: Test failed: unexpected char 0x3e position 0 in line 40 (got '>call say" "(3) prints 4?! ', wanted '>cmd /c say one ') batch.c:301: Test failed: unexpected char 0x34 position 0 in line 41 (got '4 ', wanted '0(a)space@') batch.c:298: Test failed: excess characters on line 42 (got 'error 1', wanted '') batch.c:301: Test failed: unexpected char 0x2d position 0 in line 43 (got '------ Testing invocation with CMD /C -------------', wanted '>cmd /c "say one" ') batch.c:295: Test failed: unexpected end of line 44 (got '', wanted '1(a)space@') batch.c:298: Test failed: excess characters on line 45 (got '>cmd /c say one ', wanted '') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 46 (got '0 ', wanted '>cmd /c "say"" one" ') batch.c:295: Test failed: unexpected end of line 47 (got '', wanted '0(a)space@') batch.c:298: Test failed: excess characters on line 48 (got '>cmd /c "say one" ', wanted '') batch.c:301: Test failed: unexpected char 0x31 position 0 in line 49 (got '1 ', wanted '>cmd /c "say one ') batch.c:295: Test failed: unexpected end of line 50 (got '', wanted '0(a)space@') batch.c:298: Test failed: excess characters on line 51 (got '>cmd /c "say"" one" ', wanted '') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 52 (got '0 ', wanted '>cmd /c say" one" ') batch.c:295: Test failed: unexpected end of line 53 (got '', wanted '1(a)space@') batch.c:298: Test failed: excess characters on line 54 (got '>cmd /c "say one ', wanted '') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 55 (got '0 ', wanted '>cmd /c say "one" ') batch.c:295: Test failed: unexpected end of line 56 (got '', wanted '0(a)space@') batch.c:298: Test failed: excess characters on line 57 (got '>cmd /c say" one" ', wanted '') batch.c:301: Test failed: unexpected char 0x31 position 0 in line 58 (got '1 ', wanted '>cmd /c s"ay one ') batch.c:295: Test failed: unexpected end of line 59 (got '', wanted '1(a)space@') batch.c:298: Test failed: excess characters on line 60 (got '>cmd /c say "one" ', wanted '') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 61 (got '0 ', wanted '>cmd /c s"aytwo ') batch.c:295: Test failed: unexpected end of line 62 (got '', wanted '2(a)space@') batch.c:298: Test failed: excess characters on line 63 (got '>cmd /c s"ay one ', wanted '') batch.c:301: Test failed: unexpected char 0x31 position 0 in line 64 (got '1 ', wanted '>cmd /c say (3) ') batch.c:295: Test failed: unexpected end of line 65 (got '', wanted '0(a)space@') batch.c:298: Test failed: excess characters on line 66 (got '>cmd /c s"aytwo ', wanted '') batch.c:301: Test failed: unexpected char 0x32 position 0 in line 67 (got '2 ', wanted '>cmd /c say" (3)" ') batch.c:295: Test failed: unexpected end of line 68 (got '', wanted '3(a)space@') batch.c:298: Test failed: excess characters on line 69 (got '>cmd /c say (3) ', wanted '') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 70 (got '0 ', wanted '>cmd /c say" "(3) prints 4?! ') batch.c:295: Test failed: unexpected end of line 71 (got '', wanted '4(a)space@') batch.c:301: Test failed: unexpected char 0x3e position 0 in line 72 (got '>cmd /c say" (3)" ', wanted '---------- Testing CMD /C quoting -----------------') batch.c:298: Test failed: excess characters on line 73 (got '3 ', wanted '') batch.c:295: Test failed: unexpected end of line 74 (got '', wanted '>cmd /c @echo "hi" ') batch.c:301: Test failed: unexpected char 0x3e position 0 in line 75 (got '>cmd /c say" "(3) prints 4?! ', wanted '"hi"') batch.c:298: Test failed: excess characters on line 76 (got '4 ', wanted '') batch.c:301: Test failed: unexpected char 0x2d position 0 in line 77 (got '---------- Testing CMD /C quoting -----------------', wanted '>cmd /c say" "one ') batch.c:295: Test failed: unexpected end of line 78 (got '', wanted '1(a)space@') batch.c:298: Test failed: excess characters on line 79 (got '>cmd /c @echo "hi" ', wanted '') batch.c:301: Test failed: unexpected char 0x22 position 0 in line 80 (got '"hi"', wanted '>cmd /c @echo "\"\\"\\\"\\\\" "\"\\"\\\"\\\\" ') batch.c:295: Test failed: unexpected end of line 81 (got '', wanted '"\"\\"\\\"\\\\"@space@"\"\\"\\\"\\\\"') batch.c:298: Test failed: excess characters on line 82 (got '>cmd /c say" "one ', wanted '') batch.c:301: Test failed: unexpected char 0x31 position 0 in line 83 (got '1 ', wanted '>cmd /c "say one" ') batch.c:295: Test failed: unexpected end of line 84 (got '', wanted '1(a)space@') batch.c:298: Test failed: excess characters on line 85 (got '>cmd /c @echo "\"\\"\\\"\\\\" "\"\\"\\\"\\\\" ', wanted '') batch.c:301: Test failed: unexpected char 0x22 position 0 in line 86 (got '"\"\\"\\\"\\\\" "\"\\"\\\"\\\\"', wanted '>cmd /s/c "say one" ') batch.c:295: Test failed: unexpected end of line 87 (got '', wanted '0(a)space@') batch.c:298: Test failed: excess characters on line 88 (got '>cmd /c "say one" ', wanted '') batch.c:301: Test failed: unexpected char 0x31 position 0 in line 89 (got '1 ', wanted '>cmd /s/c ""say one"" ') batch.c:295: Test failed: unexpected end of line 90 (got '', wanted '1(a)space@') batch.c:298: Test failed: excess characters on line 91 (got '>cmd /s/c "say one" ', wanted '') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 92 (got '0 ', wanted '>cmd /c "say one ') batch.c:295: Test failed: unexpected end of line 93 (got '', wanted '0(a)space@') batch.c:298: Test failed: excess characters on line 94 (got '>cmd /s/c ""say one"" ', wanted '') batch.c:301: Test failed: unexpected char 0x31 position 0 in line 95 (got '1 ', wanted '>cmd /c "say"" one" ') batch.c:295: Test failed: unexpected end of line 96 (got '', wanted '0(a)space@') batch.c:298: Test failed: excess characters on line 97 (got '>cmd /c "say one ', wanted '') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 98 (got '0 ', wanted '>cmd /c "say (3)" ') batch.c:295: Test failed: unexpected end of line 99 (got '', wanted '0(a)space@@or_broken(a)3@space@') batch.c:298: Test failed: excess characters on line 100 (got '>cmd /c "say"" one" ', wanted '') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 101 (got '0 ', wanted '>cmd /c ""say (3)"" ') batch.c:295: Test failed: unexpected end of line 102 (got '', wanted '3(a)space@') batch.c:298: Test failed: excess characters on line 103 (got '>cmd /c "say (3)" ', wanted '') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 104 (got '0 ', wanted '>cmd /c saytwo ') batch.c:295: Test failed: unexpected end of line 105 (got '', wanted '2(a)space@') batch.c:298: Test failed: excess characters on line 106 (got '>cmd /c ""say (3)"" ', wanted '') batch.c:301: Test failed: unexpected char 0x33 position 0 in line 107 (got '3 ', wanted '>cmd /c "saytwo" ') batch.c:295: Test failed: unexpected end of line 108 (got '', wanted '2(a)space@') batch.c:298: Test failed: excess characters on line 109 (got '>cmd /c saytwo ', wanted '') batch.c:301: Test failed: unexpected char 0x32 position 0 in line 110 (got '2 ', wanted '>cmd /c "saytwo ') batch.c:295: Test failed: unexpected end of line 111 (got '', wanted '2(a)space@') batch.c:298: Test failed: excess characters on line 112 (got '>cmd /c "saytwo" ', wanted '') batch.c:301: Test failed: unexpected char 0x32 position 0 in line 113 (got '2 ', wanted '>cmd /c "say five" ') batch.c:295: Test failed: unexpected end of line 114 (got '', wanted '0(a)space@') batch.c:298: Test failed: excess characters on line 115 (got '>cmd /c "saytwo ', wanted '') batch.c:301: Test failed: unexpected char 0x32 position 0 in line 116 (got '2 ', wanted '>cmd /c "say five" ') batch.c:295: Test failed: unexpected end of line 117 (got '', wanted '5(a)space@') batch.c:301: Test failed: unexpected char 0x3e position 0 in line 118 (got '>cmd /c "say five" ', wanted '------- Testing CMD /C qualifier treatment ------------') batch.c:298: Test failed: excess characters on line 119 (got '0 ', wanted '') batch.c:295: Test failed: unexpected end of line 120 (got '', wanted '>cmd /csay one ') batch.c:301: Test failed: unexpected char 0x3e position 0 in line 121 (got '>cmd /c "say five" ', wanted '0(a)space@') batch.c:298: Test failed: excess characters on line 122 (got '5 ', wanted '') batch.c:301: Test failed: unexpected char 0x2d position 0 in line 123 (got '------- Testing CMD /C qualifier treatment ------------', wanted '>cmd /c"say one" ') batch.c:295: Test failed: unexpected end of line 124 (got '', wanted '1(a)space@') batch.c:298: Test failed: excess characters on line 125 (got '>cmd /csay one ', wanted '') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 126 (got '0 ', wanted '>cmd "/c"say one ') batch.c:295: Test failed: unexpected end of line 127 (got '', wanted '0(a)space@') batch.c:298: Test failed: excess characters on line 128 (got '>cmd /c"say one" ', wanted '') batch.c:301: Test failed: unexpected char 0x31 position 0 in line 129 (got '1 ', wanted '>cmd ignoreme/c say one ') batch.c:295: Test failed: unexpected end of line 130 (got '', wanted '0(a)space@') batch.c:301: Test failed: unexpected char 0x3e position 0 in line 131 (got '>cmd "/c"say one ', wanted '--------- Testing special characters --------------') batch.c:298: Test failed: excess characters on line 132 (got '0 ', wanted '') batch.c:295: Test failed: unexpected end of line 133 (got '', wanted '>call say ') batch.c:301: Test failed: unexpected char 0x3e position 0 in line 134 (got '>cmd ignoreme/c say one ', wanted '0(a)space@') batch.c:298: Test failed: excess characters on line 135 (got '0 ', wanted '') batch.c:301: Test failed: unexpected char 0x2d position 0 in line 136 (got '--------- Testing special characters --------------', wanted '>call say( ') batch.c:295: Test failed: unexpected end of line 137 (got '', wanted '0(a)space@') batch.c:298: Test failed: excess characters on line 138 (got '>call say ', wanted '') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 139 (got '0 ', wanted '>call say) ') batch.c:295: Test failed: unexpected end of line 140 (got '', wanted ')@space@') batch.c:298: Test failed: excess characters on line 141 (got '>call say( ', wanted '') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 142 (got '0 ', wanted '>call say[ ') batch.c:295: Test failed: unexpected end of line 143 (got '', wanted '[@space@') batch.c:298: Test failed: excess characters on line 144 (got '>call say) ', wanted '') batch.c:301: Test failed: unexpected char 0x29 position 0 in line 145 (got ') ', wanted '>call say] ') batch.c:295: Test failed: unexpected end of line 146 (got '', wanted ']@space@') batch.c:298: Test failed: excess characters on line 147 (got '>call say[ ', wanted '') batch.c:301: Test failed: unexpected char 0x5b position 0 in line 148 (got '[ ', wanted '>call say{ ') batch.c:295: Test failed: unexpected end of line 149 (got '', wanted '{@space@') batch.c:298: Test failed: excess characters on line 150 (got '>call say] ', wanted '') batch.c:301: Test failed: unexpected char 0x5d position 0 in line 151 (got '] ', wanted '>call say} ') batch.c:295: Test failed: unexpected end of line 152 (got '', wanted '}@space@') batch.c:298: Test failed: excess characters on line 153 (got '>call say{ ', wanted '') batch.c:301: Test failed: unexpected char 0x7b position 0 in line 154 (got '{ ', wanted '>call say= ') batch.c:295: Test failed: unexpected end of line 155 (got '', wanted '0(a)space@') batch.c:298: Test failed: excess characters on line 156 (got '>call say} ', wanted '') batch.c:301: Test failed: unexpected char 0x7d position 0 in line 157 (got '} ', wanted '>call say; ') batch.c:295: Test failed: unexpected end of line 158 (got '', wanted '0(a)space@') batch.c:298: Test failed: excess characters on line 159 (got '>call say= ', wanted '') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 160 (got '0 ', wanted '>call say! ') batch.c:295: Test failed: unexpected end of line 161 (got '', wanted '0(a)space@') batch.c:298: Test failed: excess characters on line 162 (got '>call say; ', wanted '') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 163 (got '0 ', wanted '>call say! ') batch.c:295: Test failed: unexpected end of line 164 (got '', wanted '!@space@') batch.c:298: Test failed: excess characters on line 165 (got '>call say! ', wanted '') batch.c:301: Test failed: unexpected char 0x21 position 0 in line 166 (got '! ', wanted '>call say% ') batch.c:295: Test failed: unexpected end of line 167 (got '', wanted '0(a)space@') batch.c:298: Test failed: excess characters on line 168 (got '>call say! ', wanted '') batch.c:301: Test failed: unexpected char 0x21 position 0 in line 169 (got '! ', wanted '>call say' ') batch.c:295: Test failed: unexpected end of line 170 (got '', wanted ''@space@') batch.c:298: Test failed: excess characters on line 171 (got '>call say% ', wanted '') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 172 (got '0 ', wanted '>call say+ ') batch.c:295: Test failed: unexpected end of line 173 (got '', wanted '+(a)space@') batch.c:298: Test failed: excess characters on line 174 (got '>call say' ', wanted '') batch.c:301: Test failed: unexpected char 0x27 position 0 in line 175 (got '' ', wanted '>call say, ') batch.c:295: Test failed: unexpected end of line 176 (got '', wanted '0(a)space@') batch.c:298: Test failed: excess characters on line 177 (got '>call say+ ', wanted '') batch.c:301: Test failed: unexpected char 0x2b position 0 in line 178 (got '+ ', wanted '>call say' ') batch.c:295: Test failed: unexpected end of line 179 (got '', wanted ''@space@') batch.c:298: Test failed: excess characters on line 180 (got '>call say, ', wanted '') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 181 (got '0 ', wanted '>call say~ ') batch.c:295: Test failed: unexpected end of line 182 (got '', wanted '~@space@') batch.c:301: Test failed: unexpected char 0x3e position 0 in line 183 (got '>call say' ', wanted '--------- Testing parameter passing --------------') batch.c:298: Test failed: excess characters on line 184 (got '' ', wanted '') batch.c:295: Test failed: unexpected end of line 185 (got '', wanted '>call tell 1 ') batch.c:301: Test failed: unexpected char 0x3e position 0 in line 186 (got '>call say~ ', wanted '1:1,2:@space@') batch.c:298: Test failed: excess characters on line 187 (got '~ ', wanted '') batch.c:301: Test failed: unexpected char 0x2d position 0 in line 188 (got '--------- Testing parameter passing --------------', wanted '>call tell (1) ') batch.c:295: Test failed: unexpected end of line 189 (got '', wanted '1:(1),2:@space@') batch.c:298: Test failed: excess characters on line 190 (got '>call tell 1 ', wanted '') batch.c:301: Test failed: unexpected char 0x31 position 0 in line 191 (got '1:1,2: ', wanted '>call tell 1(2) ') batch.c:295: Test failed: unexpected end of line 192 (got '', wanted '1:1(2),2:@space@') batch.c:298: Test failed: excess characters on line 193 (got '>call tell (1) ', wanted '') batch.c:301: Test failed: unexpected char 0x31 position 0 in line 194 (got '1:(1),2: ', wanted '>call tell(1) ') batch.c:295: Test failed: unexpected end of line 195 (got '', wanted '1:(1),2:@space@') batch.c:298: Test failed: excess characters on line 196 (got '>call tell 1(2) ', wanted '') batch.c:301: Test failed: unexpected char 0x31 position 0 in line 197 (got '1:1(2),2: ', wanted '>call tell((1)) ') batch.c:295: Test failed: unexpected end of line 198 (got '', wanted '1:((1)),2:@space@') batch.c:298: Test failed: excess characters on line 199 (got '>call tell(1) ', wanted '') batch.c:301: Test failed: unexpected char 0x31 position 0 in line 200 (got '1:(1),2: ', wanted '>call tell(1)(2) ') batch.c:301: Test failed: unexpected char 0x65 position 0 in line 201 (got 'error 1', wanted '1:(1)(2),2:@space@') batch.c:301: Test failed: unexpected char 0x3e position 0 in line 203 (got '>call tell((1)) ', wanted '>call tell(1);,;(2) ') batch.c:301: Test failed: unexpected char 0x31 position 0 in line 204 (got '1:((1)),2: ', wanted '1:(1),2:(2)@space@') batch.c:298: Test failed: excess characters on line 205 (got 'error 1', wanted '') batch.c:295: Test failed: unexpected end of line 206 (got '', wanted '>call tell;1 2 ') batch.c:301: Test failed: unexpected char 0x3e position 0 in line 207 (got '>call tell(1)(2) ', wanted '1:1,2:2(a)space@') batch.c:298: Test failed: excess characters on line 208 (got '1:(1)(2),2: ', wanted '') batch.c:301: Test failed: unexpected char 0x65 position 0 in line 209 (got 'error 1', wanted '>call tell; 1, ;2 ') batch.c:295: Test failed: unexpected end of line 210 (got '', wanted '1:1,2:2(a)space@') batch.c:298: Test failed: excess characters on line 211 (got '>call tell(1);,;(2) ', wanted '') batch.c:301: Test failed: unexpected char 0x31 position 0 in line 212 (got '1:(1),2:(2) ', wanted '>call tell;1;;2 ') batch.c:301: Test failed: unexpected char 0x65 position 0 in line 213 (got 'error 1', wanted '1:1,2:2(a)space@') batch.c:301: Test failed: unexpected char 0x3e position 0 in line 215 (got '>call tell;1 2 ', wanted '>call tell "p "1 p" "2 ') batch.c:301: Test failed: unexpected char 0x31 position 0 in line 216 (got '1:1,2:2 ', wanted '1:"p(a)space@"1,2:p"@space@"2(a)space@') batch.c:298: Test failed: excess characters on line 217 (got 'error 1', wanted '') batch.c:295: Test failed: unexpected end of line 218 (got '', wanted '>call tell p"1 p";2 ') batch.c:301: Test failed: unexpected char 0x3e position 0 in line 219 (got '>call tell; 1, ;2 ', wanted '1:p"1(a)space@p",2:2(a)space@') batch.c:315: Test failed: too long output, got additional 1:1,2:2 === W2KPROSP4 (32 bit) === batch.c:301: Test failed: unexpected char 0x21 position 0 in line 161 (got '! ', wanted '0(a)space@') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 164 (got '0 ', wanted '!@space@') === WXPPROSP3 (32 bit) === batch.c:301: Test failed: unexpected char 0x21 position 0 in line 161 (got '! ', wanted '0(a)space@') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 164 (got '0 ', wanted '!@space@') === W2K3R2SESP2 (32 bit) === batch.c:301: Test failed: unexpected char 0x21 position 0 in line 161 (got '! ', wanted '0(a)space@') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 164 (got '0 ', wanted '!@space@') === WVISTAADM (32 bit) === batch.c:301: Test failed: unexpected char 0x21 position 0 in line 161 (got '! ', wanted '0(a)space@') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 164 (got '0 ', wanted '!@space@') === W2K8SE (32 bit) === batch.c:301: Test failed: unexpected char 0x21 position 0 in line 161 (got '! ', wanted '0(a)space@') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 164 (got '0 ', wanted '!@space@') === W7PRO (32 bit) === batch.c:301: Test failed: unexpected char 0x21 position 0 in line 161 (got '! ', wanted '0(a)space@') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 164 (got '0 ', wanted '!@space@') === W7PROX64 (32 bit) === batch.c:301: Test failed: unexpected char 0x21 position 0 in line 161 (got '! ', wanted '0(a)space@') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 164 (got '0 ', wanted '!@space@') === TEST64_W7SP1 (32 bit) === batch.c:301: Test failed: unexpected char 0x21 position 0 in line 161 (got '! ', wanted '0(a)space@') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 164 (got '0 ', wanted '!@space@') === W7PROX64 (64 bit) === batch.c:301: Test failed: unexpected char 0x21 position 0 in line 161 (got '! ', wanted '0(a)space@') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 164 (got '0 ', wanted '!@space@') === TEST64_W7SP1 (64 bit) === batch.c:301: Test failed: unexpected char 0x21 position 0 in line 161 (got '! ', wanted '0(a)space@') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 164 (got '0 ', wanted '!@space@')

1 0

Re: [PATCH 7/9] cmd/tests: adapt TODOs in test output (special characters)
by Marvin Sept. 20, 2011

Sept. 20, 2011

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=14399 Your paranoid android. === WNT4WSSP6 (32 bit) === batch.c:298: Test failed: excess characters on line 17 (got 'error 1', wanted '') batch.c:295: Test failed: unexpected end of line 18 (got '', wanted '>call say "one" ') batch.c:301: Test failed: unexpected char 0x3e position 0 in line 19 (got '>call say "one" ', wanted '0(a)space@') batch.c:298: Test failed: excess characters on line 20 (got '0 ', wanted '') batch.c:295: Test failed: unexpected end of line 21 (got '', wanted '>call s"ay one ') batch.c:301: Test failed: unexpected char 0x3e position 0 in line 22 (got '>call s"ay one ', wanted '1(a)space@') batch.c:298: Test failed: excess characters on line 23 (got '1 ', wanted '') batch.c:301: Test failed: unexpected char 0x65 position 0 in line 24 (got 'error 1', wanted '>call s"aytwo ') batch.c:295: Test failed: unexpected end of line 25 (got '', wanted '2(a)space@') batch.c:298: Test failed: excess characters on line 26 (got '>call s"aytwo ', wanted '') batch.c:301: Test failed: unexpected char 0x32 position 0 in line 27 (got '2 ', wanted '>call say (3) ') batch.c:301: Test failed: unexpected char 0x65 position 0 in line 28 (got 'error 1', wanted '0(a)space@') batch.c:301: Test failed: unexpected char 0x3e position 0 in line 30 (got '>call say (3) ', wanted '>call "say (3)" ') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 31 (got '0 ', wanted '3(a)space@') batch.c:301: Test failed: unexpected char 0x3e position 0 in line 33 (got '>call "say (3)" ', wanted '>call say" (3)" ') batch.c:301: Test failed: unexpected char 0x3e position 0 in line 36 (got '>call say" (3)" ', wanted '>call say" "(3) prints 4?! ') batch.c:301: Test failed: unexpected char 0x33 position 0 in line 37 (got '3 ', wanted '4(a)space@') batch.c:301: Test failed: unexpected char 0x65 position 0 in line 38 (got 'error 1', wanted '------ Testing invocation with CMD /C -------------') batch.c:301: Test failed: unexpected char 0x3e position 0 in line 40 (got '>call say" "(3) prints 4?! ', wanted '>cmd /c say one ') batch.c:301: Test failed: unexpected char 0x34 position 0 in line 41 (got '4 ', wanted '0(a)space@') batch.c:298: Test failed: excess characters on line 42 (got 'error 1', wanted '') batch.c:301: Test failed: unexpected char 0x2d position 0 in line 43 (got '------ Testing invocation with CMD /C -------------', wanted '>cmd /c "say one" ') batch.c:295: Test failed: unexpected end of line 44 (got '', wanted '1(a)space@') batch.c:298: Test failed: excess characters on line 45 (got '>cmd /c say one ', wanted '') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 46 (got '0 ', wanted '>cmd /c "say"" one" ') batch.c:295: Test failed: unexpected end of line 47 (got '', wanted '0(a)space@') batch.c:298: Test failed: excess characters on line 48 (got '>cmd /c "say one" ', wanted '') batch.c:301: Test failed: unexpected char 0x31 position 0 in line 49 (got '1 ', wanted '>cmd /c "say one ') batch.c:295: Test failed: unexpected end of line 50 (got '', wanted '0(a)space@') batch.c:298: Test failed: excess characters on line 51 (got '>cmd /c "say"" one" ', wanted '') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 52 (got '0 ', wanted '>cmd /c say" one" ') batch.c:295: Test failed: unexpected end of line 53 (got '', wanted '1(a)space@') batch.c:298: Test failed: excess characters on line 54 (got '>cmd /c "say one ', wanted '') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 55 (got '0 ', wanted '>cmd /c say "one" ') batch.c:295: Test failed: unexpected end of line 56 (got '', wanted '0(a)space@') batch.c:298: Test failed: excess characters on line 57 (got '>cmd /c say" one" ', wanted '') batch.c:301: Test failed: unexpected char 0x31 position 0 in line 58 (got '1 ', wanted '>cmd /c s"ay one ') batch.c:295: Test failed: unexpected end of line 59 (got '', wanted '1(a)space@') batch.c:298: Test failed: excess characters on line 60 (got '>cmd /c say "one" ', wanted '') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 61 (got '0 ', wanted '>cmd /c s"aytwo ') batch.c:295: Test failed: unexpected end of line 62 (got '', wanted '2(a)space@') batch.c:298: Test failed: excess characters on line 63 (got '>cmd /c s"ay one ', wanted '') batch.c:301: Test failed: unexpected char 0x31 position 0 in line 64 (got '1 ', wanted '>cmd /c say (3) ') batch.c:295: Test failed: unexpected end of line 65 (got '', wanted '0(a)space@') batch.c:298: Test failed: excess characters on line 66 (got '>cmd /c s"aytwo ', wanted '') batch.c:301: Test failed: unexpected char 0x32 position 0 in line 67 (got '2 ', wanted '>cmd /c say" (3)" ') batch.c:295: Test failed: unexpected end of line 68 (got '', wanted '3(a)space@') batch.c:298: Test failed: excess characters on line 69 (got '>cmd /c say (3) ', wanted '') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 70 (got '0 ', wanted '>cmd /c say" "(3) prints 4?! ') batch.c:295: Test failed: unexpected end of line 71 (got '', wanted '4(a)space@') batch.c:301: Test failed: unexpected char 0x3e position 0 in line 72 (got '>cmd /c say" (3)" ', wanted '---------- Testing CMD /C quoting -----------------') batch.c:298: Test failed: excess characters on line 73 (got '3 ', wanted '') batch.c:295: Test failed: unexpected end of line 74 (got '', wanted '>cmd /c @echo "hi" ') batch.c:301: Test failed: unexpected char 0x3e position 0 in line 75 (got '>cmd /c say" "(3) prints 4?! ', wanted '"hi"') batch.c:298: Test failed: excess characters on line 76 (got '4 ', wanted '') batch.c:301: Test failed: unexpected char 0x2d position 0 in line 77 (got '---------- Testing CMD /C quoting -----------------', wanted '>cmd /c say" "one ') batch.c:295: Test failed: unexpected end of line 78 (got '', wanted '1(a)space@') batch.c:298: Test failed: excess characters on line 79 (got '>cmd /c @echo "hi" ', wanted '') batch.c:301: Test failed: unexpected char 0x22 position 0 in line 80 (got '"hi"', wanted '>cmd /c @echo "\"\\"\\\"\\\\" "\"\\"\\\"\\\\" ') batch.c:295: Test failed: unexpected end of line 81 (got '', wanted '"\"\\"\\\"\\\\"@space@"\"\\"\\\"\\\\"') batch.c:298: Test failed: excess characters on line 82 (got '>cmd /c say" "one ', wanted '') batch.c:301: Test failed: unexpected char 0x31 position 0 in line 83 (got '1 ', wanted '>cmd /c "say one" ') batch.c:295: Test failed: unexpected end of line 84 (got '', wanted '1(a)space@') batch.c:298: Test failed: excess characters on line 85 (got '>cmd /c @echo "\"\\"\\\"\\\\" "\"\\"\\\"\\\\" ', wanted '') batch.c:301: Test failed: unexpected char 0x22 position 0 in line 86 (got '"\"\\"\\\"\\\\" "\"\\"\\\"\\\\"', wanted '>cmd /s/c "say one" ') batch.c:295: Test failed: unexpected end of line 87 (got '', wanted '0(a)space@') batch.c:298: Test failed: excess characters on line 88 (got '>cmd /c "say one" ', wanted '') batch.c:301: Test failed: unexpected char 0x31 position 0 in line 89 (got '1 ', wanted '>cmd /s/c ""say one"" ') batch.c:295: Test failed: unexpected end of line 90 (got '', wanted '1(a)space@') batch.c:298: Test failed: excess characters on line 91 (got '>cmd /s/c "say one" ', wanted '') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 92 (got '0 ', wanted '>cmd /c "say one ') batch.c:295: Test failed: unexpected end of line 93 (got '', wanted '0(a)space@') batch.c:298: Test failed: excess characters on line 94 (got '>cmd /s/c ""say one"" ', wanted '') batch.c:301: Test failed: unexpected char 0x31 position 0 in line 95 (got '1 ', wanted '>cmd /c "say"" one" ') batch.c:295: Test failed: unexpected end of line 96 (got '', wanted '0(a)space@') batch.c:298: Test failed: excess characters on line 97 (got '>cmd /c "say one ', wanted '') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 98 (got '0 ', wanted '>cmd /c "say (3)" ') batch.c:295: Test failed: unexpected end of line 99 (got '', wanted '0(a)space@@or_broken(a)3@space@') batch.c:298: Test failed: excess characters on line 100 (got '>cmd /c "say"" one" ', wanted '') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 101 (got '0 ', wanted '>cmd /c ""say (3)"" ') batch.c:295: Test failed: unexpected end of line 102 (got '', wanted '3(a)space@') batch.c:298: Test failed: excess characters on line 103 (got '>cmd /c "say (3)" ', wanted '') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 104 (got '0 ', wanted '>cmd /c saytwo ') batch.c:295: Test failed: unexpected end of line 105 (got '', wanted '2(a)space@') batch.c:298: Test failed: excess characters on line 106 (got '>cmd /c ""say (3)"" ', wanted '') batch.c:301: Test failed: unexpected char 0x33 position 0 in line 107 (got '3 ', wanted '>cmd /c "saytwo" ') batch.c:295: Test failed: unexpected end of line 108 (got '', wanted '2(a)space@') batch.c:298: Test failed: excess characters on line 109 (got '>cmd /c saytwo ', wanted '') batch.c:301: Test failed: unexpected char 0x32 position 0 in line 110 (got '2 ', wanted '>cmd /c "saytwo ') batch.c:295: Test failed: unexpected end of line 111 (got '', wanted '2(a)space@') batch.c:298: Test failed: excess characters on line 112 (got '>cmd /c "saytwo" ', wanted '') batch.c:301: Test failed: unexpected char 0x32 position 0 in line 113 (got '2 ', wanted '>cmd /c "say five" ') batch.c:295: Test failed: unexpected end of line 114 (got '', wanted '0(a)space@') batch.c:298: Test failed: excess characters on line 115 (got '>cmd /c "saytwo ', wanted '') batch.c:301: Test failed: unexpected char 0x32 position 0 in line 116 (got '2 ', wanted '>cmd /c "say five" ') batch.c:295: Test failed: unexpected end of line 117 (got '', wanted '5(a)space@') batch.c:301: Test failed: unexpected char 0x3e position 0 in line 118 (got '>cmd /c "say five" ', wanted '------- Testing CMD /C qualifier treatment ------------') batch.c:298: Test failed: excess characters on line 119 (got '0 ', wanted '') batch.c:295: Test failed: unexpected end of line 120 (got '', wanted '>cmd /csay one ') batch.c:301: Test failed: unexpected char 0x3e position 0 in line 121 (got '>cmd /c "say five" ', wanted '0(a)space@') batch.c:298: Test failed: excess characters on line 122 (got '5 ', wanted '') batch.c:301: Test failed: unexpected char 0x2d position 0 in line 123 (got '------- Testing CMD /C qualifier treatment ------------', wanted '>cmd /c"say one" ') batch.c:295: Test failed: unexpected end of line 124 (got '', wanted '1(a)space@') batch.c:298: Test failed: excess characters on line 125 (got '>cmd /csay one ', wanted '') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 126 (got '0 ', wanted '>cmd "/c"say one ') batch.c:295: Test failed: unexpected end of line 127 (got '', wanted '0(a)space@') batch.c:298: Test failed: excess characters on line 128 (got '>cmd /c"say one" ', wanted '') batch.c:301: Test failed: unexpected char 0x31 position 0 in line 129 (got '1 ', wanted '>cmd ignoreme/c say one ') batch.c:295: Test failed: unexpected end of line 130 (got '', wanted '0(a)space@') batch.c:301: Test failed: unexpected char 0x3e position 0 in line 131 (got '>cmd "/c"say one ', wanted '--------- Testing special characters --------------') batch.c:298: Test failed: excess characters on line 132 (got '0 ', wanted '') batch.c:295: Test failed: unexpected end of line 133 (got '', wanted '>call say ') batch.c:301: Test failed: unexpected char 0x3e position 0 in line 134 (got '>cmd ignoreme/c say one ', wanted '0(a)space@') batch.c:298: Test failed: excess characters on line 135 (got '0 ', wanted '') batch.c:301: Test failed: unexpected char 0x2d position 0 in line 136 (got '--------- Testing special characters --------------', wanted '>call say( ') batch.c:295: Test failed: unexpected end of line 137 (got '', wanted '0(a)space@') batch.c:298: Test failed: excess characters on line 138 (got '>call say ', wanted '') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 139 (got '0 ', wanted '>call say) ') batch.c:295: Test failed: unexpected end of line 140 (got '', wanted ')@space@') batch.c:298: Test failed: excess characters on line 141 (got '>call say( ', wanted '') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 142 (got '0 ', wanted '>call say[ ') batch.c:295: Test failed: unexpected end of line 143 (got '', wanted '[@space@') batch.c:298: Test failed: excess characters on line 144 (got '>call say) ', wanted '') batch.c:301: Test failed: unexpected char 0x29 position 0 in line 145 (got ') ', wanted '>call say] ') batch.c:295: Test failed: unexpected end of line 146 (got '', wanted ']@space@') batch.c:298: Test failed: excess characters on line 147 (got '>call say[ ', wanted '') batch.c:301: Test failed: unexpected char 0x5b position 0 in line 148 (got '[ ', wanted '>call say{ ') batch.c:295: Test failed: unexpected end of line 149 (got '', wanted '{@space@') batch.c:298: Test failed: excess characters on line 150 (got '>call say] ', wanted '') batch.c:301: Test failed: unexpected char 0x5d position 0 in line 151 (got '] ', wanted '>call say} ') batch.c:295: Test failed: unexpected end of line 152 (got '', wanted '}@space@') batch.c:298: Test failed: excess characters on line 153 (got '>call say{ ', wanted '') batch.c:301: Test failed: unexpected char 0x7b position 0 in line 154 (got '{ ', wanted '>call say= ') batch.c:295: Test failed: unexpected end of line 155 (got '', wanted '0(a)space@') batch.c:298: Test failed: excess characters on line 156 (got '>call say} ', wanted '') batch.c:301: Test failed: unexpected char 0x7d position 0 in line 157 (got '} ', wanted '>call say; ') batch.c:295: Test failed: unexpected end of line 158 (got '', wanted '0(a)space@') batch.c:298: Test failed: excess characters on line 159 (got '>call say= ', wanted '') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 160 (got '0 ', wanted '>call say! ') batch.c:295: Test failed: unexpected end of line 161 (got '', wanted '0(a)space@') batch.c:298: Test failed: excess characters on line 162 (got '>call say; ', wanted '') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 163 (got '0 ', wanted '>call say! ') batch.c:295: Test failed: unexpected end of line 164 (got '', wanted '!@space@') batch.c:298: Test failed: excess characters on line 165 (got '>call say! ', wanted '') batch.c:301: Test failed: unexpected char 0x21 position 0 in line 166 (got '! ', wanted '>call say% ') batch.c:295: Test failed: unexpected end of line 167 (got '', wanted '0(a)space@') batch.c:298: Test failed: excess characters on line 168 (got '>call say! ', wanted '') batch.c:301: Test failed: unexpected char 0x21 position 0 in line 169 (got '! ', wanted '>call say' ') batch.c:295: Test failed: unexpected end of line 170 (got '', wanted ''@space@') batch.c:298: Test failed: excess characters on line 171 (got '>call say% ', wanted '') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 172 (got '0 ', wanted '>call say+ ') batch.c:295: Test failed: unexpected end of line 173 (got '', wanted '+(a)space@') batch.c:298: Test failed: excess characters on line 174 (got '>call say' ', wanted '') batch.c:301: Test failed: unexpected char 0x27 position 0 in line 175 (got '' ', wanted '>call say, ') batch.c:295: Test failed: unexpected end of line 176 (got '', wanted '0(a)space@') batch.c:298: Test failed: excess characters on line 177 (got '>call say+ ', wanted '') batch.c:301: Test failed: unexpected char 0x2b position 0 in line 178 (got '+ ', wanted '>call say' ') batch.c:295: Test failed: unexpected end of line 179 (got '', wanted ''@space@') batch.c:298: Test failed: excess characters on line 180 (got '>call say, ', wanted '') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 181 (got '0 ', wanted '>call say~ ') batch.c:295: Test failed: unexpected end of line 182 (got '', wanted '~@space@') batch.c:301: Test failed: unexpected char 0x3e position 0 in line 183 (got '>call say' ', wanted '--------- Testing parameter passing --------------') batch.c:298: Test failed: excess characters on line 184 (got '' ', wanted '') batch.c:295: Test failed: unexpected end of line 185 (got '', wanted '>call tell 1 ') batch.c:301: Test failed: unexpected char 0x3e position 0 in line 186 (got '>call say~ ', wanted '1:1,2:@space@') batch.c:298: Test failed: excess characters on line 187 (got '~ ', wanted '') batch.c:301: Test failed: unexpected char 0x2d position 0 in line 188 (got '--------- Testing parameter passing --------------', wanted '>call tell (1) ') batch.c:295: Test failed: unexpected end of line 189 (got '', wanted '1:(1),2:@space@') batch.c:298: Test failed: excess characters on line 190 (got '>call tell 1 ', wanted '') batch.c:301: Test failed: unexpected char 0x31 position 0 in line 191 (got '1:1,2: ', wanted '>call tell 1(2) ') batch.c:295: Test failed: unexpected end of line 192 (got '', wanted '1:1(2),2:@space@') batch.c:298: Test failed: excess characters on line 193 (got '>call tell (1) ', wanted '') batch.c:301: Test failed: unexpected char 0x31 position 0 in line 194 (got '1:(1),2: ', wanted '>call tell(1) ') batch.c:295: Test failed: unexpected end of line 195 (got '', wanted '1:(1),2:@space@') batch.c:298: Test failed: excess characters on line 196 (got '>call tell 1(2) ', wanted '') batch.c:301: Test failed: unexpected char 0x31 position 0 in line 197 (got '1:1(2),2: ', wanted '>call tell((1)) ') batch.c:295: Test failed: unexpected end of line 198 (got '', wanted '1:((1)),2:@space@') batch.c:298: Test failed: excess characters on line 199 (got '>call tell(1) ', wanted '') batch.c:301: Test failed: unexpected char 0x31 position 0 in line 200 (got '1:(1),2: ', wanted '>call tell(1)(2) ') batch.c:301: Test failed: unexpected char 0x65 position 0 in line 201 (got 'error 1', wanted '1:(1)(2),2:@space@') batch.c:301: Test failed: unexpected char 0x3e position 0 in line 203 (got '>call tell((1)) ', wanted '>call tell(1);,;(2) ') batch.c:301: Test failed: unexpected char 0x31 position 0 in line 204 (got '1:((1)),2: ', wanted '1:(1),2:(2)@space@') batch.c:298: Test failed: excess characters on line 205 (got 'error 1', wanted '') batch.c:295: Test failed: unexpected end of line 206 (got '', wanted '>call tell;1 2 ') batch.c:301: Test failed: unexpected char 0x3e position 0 in line 207 (got '>call tell(1)(2) ', wanted '1:1,2:2(a)space@') batch.c:298: Test failed: excess characters on line 208 (got '1:(1)(2),2: ', wanted '') batch.c:301: Test failed: unexpected char 0x65 position 0 in line 209 (got 'error 1', wanted '>call tell; 1, ;2 ') batch.c:295: Test failed: unexpected end of line 210 (got '', wanted '1:1,2:2(a)space@') batch.c:298: Test failed: excess characters on line 211 (got '>call tell(1);,;(2) ', wanted '') batch.c:301: Test failed: unexpected char 0x31 position 0 in line 212 (got '1:(1),2:(2) ', wanted '>call tell;1;;2 ') batch.c:301: Test failed: unexpected char 0x65 position 0 in line 213 (got 'error 1', wanted '1:1,2:2(a)space@') batch.c:301: Test failed: unexpected char 0x3e position 0 in line 215 (got '>call tell;1 2 ', wanted '>call tell "p "1 p" "2 ') batch.c:301: Test failed: unexpected char 0x31 position 0 in line 216 (got '1:1,2:2 ', wanted '1:"p(a)space@"1,2:p"@space@"2(a)space@') batch.c:298: Test failed: excess characters on line 217 (got 'error 1', wanted '') batch.c:295: Test failed: unexpected end of line 218 (got '', wanted '>call tell p"1 p";2 ') batch.c:301: Test failed: unexpected char 0x3e position 0 in line 219 (got '>call tell; 1, ;2 ', wanted '1:p"1(a)space@p",2:2(a)space@') batch.c:315: Test failed: too long output, got additional 1:1,2:2 === W2KPROSP4 (32 bit) === batch.c:301: Test failed: unexpected char 0x21 position 0 in line 161 (got '! ', wanted '0(a)space@') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 164 (got '0 ', wanted '!@space@') === WXPPROSP3 (32 bit) === batch.c:301: Test failed: unexpected char 0x21 position 0 in line 161 (got '! ', wanted '0(a)space@') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 164 (got '0 ', wanted '!@space@') === W2K3R2SESP2 (32 bit) === batch.c:301: Test failed: unexpected char 0x21 position 0 in line 161 (got '! ', wanted '0(a)space@') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 164 (got '0 ', wanted '!@space@') === WVISTAADM (32 bit) === batch.c:301: Test failed: unexpected char 0x21 position 0 in line 161 (got '! ', wanted '0(a)space@') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 164 (got '0 ', wanted '!@space@') === W2K8SE (32 bit) === batch.c:301: Test failed: unexpected char 0x21 position 0 in line 161 (got '! ', wanted '0(a)space@') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 164 (got '0 ', wanted '!@space@') === W7PRO (32 bit) === batch.c:301: Test failed: unexpected char 0x21 position 0 in line 161 (got '! ', wanted '0(a)space@') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 164 (got '0 ', wanted '!@space@') === W7PROX64 (32 bit) === batch.c:301: Test failed: unexpected char 0x21 position 0 in line 161 (got '! ', wanted '0(a)space@') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 164 (got '0 ', wanted '!@space@') === TEST64_W7SP1 (32 bit) === batch.c:301: Test failed: unexpected char 0x21 position 0 in line 161 (got '! ', wanted '0(a)space@') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 164 (got '0 ', wanted '!@space@') === W7PROX64 (64 bit) === batch.c:301: Test failed: unexpected char 0x21 position 0 in line 161 (got '! ', wanted '0(a)space@') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 164 (got '0 ', wanted '!@space@') === TEST64_W7SP1 (64 bit) === batch.c:301: Test failed: unexpected char 0x21 position 0 in line 161 (got '! ', wanted '0(a)space@') batch.c:301: Test failed: unexpected char 0x30 position 0 in line 164 (got '0 ', wanted '!@space@')

1 0