[PATCH v2] vbscript/tests: Test lack of newline parsing before End statements.
Marvin
testbot at winehq.org
Fri Sep 6 11:22:51 CDT 2019
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=56311
Your paranoid android.
=== debian10 (32 bit report) ===
vbscript:
run.c:2319: Test failed: expected global_success_d
run.c:2320: Test failed: expected global_success_i
run.c:2322: Test failed: parse_script failed: 80004005
=== debian10 (32 bit French report) ===
vbscript:
run.c:2319: Test failed: expected global_success_d
run.c:2320: Test failed: expected global_success_i
run.c:2322: Test failed: parse_script failed: 80004005
=== debian10 (32 bit Japanese:Japan report) ===
vbscript:
run.c:2319: Test failed: expected global_success_d
run.c:2320: Test failed: expected global_success_i
run.c:2322: Test failed: parse_script failed: 80004005
=== debian10 (32 bit Chinese:China report) ===
vbscript:
run.c:2319: Test failed: expected global_success_d
run.c:2320: Test failed: expected global_success_i
run.c:2322: Test failed: parse_script failed: 80004005
=== debian10 (32 bit WoW report) ===
vbscript:
run.c:2319: Test failed: expected global_success_d
run.c:2320: Test failed: expected global_success_i
run.c:2322: Test failed: parse_script failed: 80004005
=== debian10 (64 bit WoW report) ===
vbscript:
run.c:2319: Test failed: expected global_success_d
run.c:2320: Test failed: expected global_success_i
run.c:2322: Test failed: parse_script failed: 80004005
More information about the wine-devel
mailing list