[PATCH v2 3/6] mf/tests: Only check sample data when length matches.

[Rémi Bernon]

On 4/5/22 10:48, Marvin wrote:
> 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=111940
> 
> Your paranoid android.
> 
> 
> === build (build log) ===
> 
> error: patch failed: dlls/mf/tests/mf.c:6892
> Task: Patch failed to apply
> 
> === debian11 (32 bit report) ===
> 
> mf:
> mf.c:6899: Test succeeded inside todo block: got length 0
> 
> === debian11 (32 bit Arabic:Morocco report) ===
> 
> mf:
> mf.c:6899: Test succeeded inside todo block: got length 0
> 
> === debian11 (32 bit German report) ===
> 
> mf:
> mf.c:6899: Test succeeded inside todo block: got length 0
> 
> === debian11 (32 bit French report) ===
> 
> mf:
> mf.c:6899: Test succeeded inside todo block: got length 0
> 
> === debian11 (32 bit Hebrew:Israel report) ===
> 
> mf:
> mf.c:6899: Test succeeded inside todo block: got length 0
> 
> === debian11 (32 bit Hindi:India report) ===
> 
> mf:
> mf.c:6899: Test succeeded inside todo block: got length 0
> 
> === debian11 (32 bit Japanese:Japan report) ===
> 
> mf:
> mf.c:6899: Test succeeded inside todo block: got length 0
> 
> === debian11 (32 bit Chinese:China report) ===
> 
> mf:
> mf.c:6899: Test succeeded inside todo block: got length 0
> 
> === debian11 (32 bit WoW report) ===
> 
> mf:
> mf.c:6899: Test succeeded inside todo block: got length 0
> 
> === debian11 (64 bit WoW report) ===
> 
> mf:
> mf.c:6899: Test succeeded inside todo block: got length 0


I think the build failure is unrelated and caused by the build VM being 
out of date.

The test spurious successes are coming from some behavior specific to 
the GStreamer version that is on the testbot, I'll fix it.
-- 
Rémi Bernon <rbernon at codeweavers.com>