[PATCH] vbscript/tests: Fix the name of a vbscript variable in the run test.

[Francois Gouget]

Signed-off-by: Francois Gouget 
---

I'm a bit surprised that this is not causing more trouble. But it also 
does not really look like this was an intentional typo designed to test 
error handling.

dlls/vbscript/tests/run.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dlls/vbscript/tests/run.c b/dlls/vbscript/tests/run.c
index 5fc23707e39..ab32a4213b0 100644
--- a/dlls/vbscript/tests/run.c
+++ b/dlls/vbscript/tests/run.c
@@ -2206,7 +2206,7 @@ static void test_callbacks(void)
                                               L"    on error resume next\n"
                                               L"    err.raise 2\n"
                                               L"    call test.globalCallback(new CallbackClass)\n"
-                                              L"    call ok(err.number = 2, "err.number = " & err.numner)\n"
+                                              L"    call ok(err.number = 2, "err.number = " & err.number)\n"
                                               L"end function\n",
                                               NULL, NULL, NULL, 0, 0, 0, NULL, NULL);
     ok(hres == S_OK, "ParseScriptText failed: %08x\n", hres);

[Marvin]

Hi,

While running your changed tests, 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:
https://testbot.winehq.org/JobDetails.pl?Key=61042

Your paranoid android.

=== wxppro (32 bit report) ===

vbscript:
run.c:2271: Test failed: bstrDescription = L"Unknown runtime error"

=== w2003std (32 bit report) ===

vbscript:
run.c:2271: Test failed: bstrDescription = L"Unknown runtime error"

=== wvistau64 (32 bit report) ===

vbscript:
run.c:2271: Test failed: bstrDescription = L"Unknown runtime error"

=== w2008s64 (32 bit report) ===

vbscript:
run.c:2271: Test failed: bstrDescription = L"Unknown runtime error"

=== w8 (32 bit report) ===

vbscript:
run.c:2271: Test failed: bstrDescription = L"Unknown runtime error"

=== w8adm (32 bit report) ===

vbscript:
run.c:2271: Test failed: bstrDescription = L"Unknown runtime error"

=== w864 (32 bit report) ===

vbscript:
run.c:2271: Test failed: bstrDescription = L"Unknown runtime error"

=== w1064v1507 (32 bit report) ===

vbscript:
run.c:2271: Test failed: bstrDescription = L"Unknown runtime error"

=== w1064v1809 (32 bit report) ===

vbscript:
run.c:2271: Test failed: bstrDescription = L"Unknown runtime error"

=== w1064v1809_2scr (32 bit report) ===

vbscript:
run.c:2271: Test failed: bstrDescription = L"Unknown runtime error"

=== wvistau64 (64 bit report) ===

vbscript:
run.c:2271: Test failed: bstrDescription = L"Unknown runtime error"

=== w2008s64 (64 bit report) ===

vbscript:
run.c:2271: Test failed: bstrDescription = L"Unknown runtime error"

=== w864 (64 bit report) ===

vbscript:
run.c:2271: Test failed: bstrDescription = L"Unknown runtime error"

=== w1064v1507 (64 bit report) ===

vbscript:
run.c:2271: Test failed: bstrDescription = L"Unknown runtime error"

=== w1064v1809 (64 bit report) ===

vbscript:
run.c:2271: Test failed: bstrDescription = L"Unknown runtime error"

=== debian10 (32 bit report) ===

vbscript:
run.c:2271: Test failed: bstrDescription = L"Unknown runtime error"

=== debian10 (32 bit French report) ===

vbscript:
run.c:2271: Test failed: bstrDescription = L"Unknown runtime error"

=== debian10 (32 bit Japanese:Japan report) ===

vbscript:
run.c:2271: Test failed: bstrDescription = L"Unknown runtime error"

=== debian10 (32 bit Chinese:China report) ===

vbscript:
run.c:2271: Test failed: bstrDescription = L"Unknown runtime error"

=== debian10 (32 bit WoW report) ===

vbscript:
run.c:2271: Test failed: bstrDescription = L"Unknown runtime error"

=== debian10 (64 bit WoW report) ===

vbscript:
run.c:2271: Test failed: bstrDescription = L"Unknown runtime error"