August 2022 - Wine-Devel - list.winehq.org

Wine Source build on native wchar_t 4 bytes
by Mahin Pandya Dec. 5, 2022

Dec. 5, 2022

Hello All, We are trying to build Wine Source on Linux with native wchar_t size 4 bytes (instead of 2 bytes), is there any way it can be done? I started with doing following changes: diff --git a/tools/winapi/winapi_test b/tools/winapi/winapi_test index b9628e8..91daac3 100644 --- a/tools/winapi/winapi_test +++ b/tools/winapi/winapi_test @@ -206,7 +206,11 @@ sub _find_align_kind_size($) { $align = 2; $kind = "signed"; $size = 2; - } elsif (/^(?:char16_t|wchar_t|USHORT|WCHAR|WORD)$/) { + } elsif (/^(?:wchar_t|WCHAR)$/) { + $align = 4; + $kind = "unsigned"; + $size = 4; + } elsif (/^(?:char16_t|USHORT|WORD|WCHAR_nt)$/) { $align = 2; $kind = "unsigned"; $size = 2; Also started changing some of headers e.g. winnt.h - removed "typedef unsigned short WCHAR;" Any pointers/suggestion are welcome. Thanking you. regards, Mahin

6 11

[PATCH 1/2] qedit/tests: Check the Sample Grabber's buffer during and after flushing.
by Gabriel Ivăncescu Oct. 4, 2022

Oct. 4, 2022

Signed-off-by: Gabriel Ivăncescu <gabrielopcode(a)gmail.com> --- dlls/qedit/tests/samplegrabber.c | 234 +++++++++++++++++++++++++++++++ 1 file changed, 234 insertions(+) diff --git a/dlls/qedit/tests/samplegrabber.c b/dlls/qedit/tests/samplegrabber.c index 8e68e3e..e66180f 100644 --- a/dlls/qedit/tests/samplegrabber.c +++ b/dlls/qedit/tests/samplegrabber.c @@ -1036,6 +1036,239 @@ static void test_connect_pin(void) ok(!ref, "Got outstanding refcount %d.\n", ref); } +struct frame_thread_params +{ + IMemInputPin *sink; + IMediaSample *sample; + DWORD delay; +}; + +static DWORD WINAPI frame_thread(void *arg) +{ + struct frame_thread_params *params = arg; + HRESULT hr; + + if (params->delay) + { + if (winetest_debug > 1) trace("%04x: Sleeping %u ms.\n", GetCurrentThreadId(), params->delay); + Sleep(params->delay); + } + if (winetest_debug > 1) trace("%04x: Sending frame.\n", GetCurrentThreadId()); + hr = IMemInputPin_Receive(params->sink, params->sample); + if (winetest_debug > 1) trace("%04x: Returned %#x.\n", GetCurrentThreadId(), hr); + IMediaSample_Release(params->sample); + free(params); + return hr; +} + +static HANDLE send_frame_time(IMemInputPin *sink, REFERENCE_TIME start_time, unsigned char color, DWORD delay) +{ + struct frame_thread_params *params = malloc(sizeof(*params)); + IMemAllocator *allocator; + REFERENCE_TIME end_time; + IMediaSample *sample; + HANDLE thread; + HRESULT hr; + BYTE *data; + + hr = IMemInputPin_GetAllocator(sink, &allocator); + ok(hr == S_OK, "Got hr %#x.\n", hr); + + hr = IMemAllocator_GetBuffer(allocator, &sample, NULL, NULL, 0); + if (hr == VFW_E_NOT_COMMITTED) + { + IMemAllocator_Commit(allocator); + hr = IMemAllocator_GetBuffer(allocator, &sample, NULL, NULL, 0); + } + ok(hr == S_OK, "Got hr %#x.\n", hr); + + hr = IMediaSample_GetPointer(sample, &data); + ok(hr == S_OK, "Got hr %#x.\n", hr); + memset(data, 0x55, 32 * 16 * 2); + + hr = IMediaSample_SetActualDataLength(sample, 32 * 16 * 2); + ok(hr == S_OK, "Got hr %#x.\n", hr); + + start_time *= 10000000; + end_time = start_time + 10000000; + hr = IMediaSample_SetTime(sample, &start_time, &end_time); + ok(hr == S_OK, "Got hr %#x.\n", hr); + + params->sink = sink; + params->sample = sample; + params->delay = delay; + thread = CreateThread(NULL, 0, frame_thread, params, 0, NULL); + + IMemAllocator_Release(allocator); + return thread; +} + +static HANDLE send_frame(IMemInputPin *sink, DWORD delay) +{ + return send_frame_time(sink, 0, 0x55, delay); /* purple */ +} + +static HRESULT join_thread_(int line, HANDLE thread) +{ + DWORD ret; + ok_(__FILE__, line)(!WaitForSingleObject(thread, 1000), "Wait failed.\n"); + GetExitCodeThread(thread, &ret); + CloseHandle(thread); + return ret; +} +#define join_thread(a) join_thread_(__LINE__, a) + +static void test_buffer_flush(void) +{ + AM_MEDIA_TYPE req_mt = + { + .majortype = MEDIATYPE_Video, + .subtype = MEDIASUBTYPE_RGB565, + .formattype = FORMAT_VideoInfo, + .bTemporalCompression = TRUE, + }; + LONG buf[(32 * 16 * 2) / sizeof(LONG)], size = sizeof(buf); + IPin *sink, *source, *renderer_pin; + struct testfilter testsource; + ISampleGrabber *grabber; + IMediaControl *control; + IFilterGraph2 *graph; + IMemInputPin *input; + IBaseFilter *filter; + OAFilterState state; + IMediaFilter *mf; + HANDLE thread; + DWORD ticks; + unsigned i; + HRESULT hr; + ULONG ref; + + testfilter_init(&testsource); + CoCreateInstance(&CLSID_FilterGraph, NULL, CLSCTX_INPROC_SERVER, + &IID_IFilterGraph2, (void **)&graph); + CoCreateInstance(&CLSID_NullRenderer, NULL, CLSCTX_INPROC_SERVER, + &IID_IBaseFilter, (void **)&filter); + IFilterGraph2_AddFilter(graph, filter, L"sink"); + IBaseFilter_FindPin(filter, L"In", &renderer_pin); + IBaseFilter_Release(filter); + + filter = create_sample_grabber(); + IFilterGraph2_AddFilter(graph, &testsource.filter.IBaseFilter_iface, L"source"); + IFilterGraph2_AddFilter(graph, filter, L"sample grabber"); + IBaseFilter_FindPin(filter, L"In", &sink); + IBaseFilter_FindPin(filter, L"Out", &source); + IBaseFilter_QueryInterface(filter, &IID_ISampleGrabber, (void **)&grabber); + IFilterGraph2_QueryInterface(graph, &IID_IMediaControl, (void **)&control); + IPin_QueryInterface(sink, &IID_IMemInputPin, (void **)&input); + + ISampleGrabber_SetMediaType(grabber, &req_mt); + ISampleGrabber_SetBufferSamples(grabber, TRUE); + + testsource.sink_mt = &req_mt; + hr = IFilterGraph2_ConnectDirect(graph, &testsource.source.pin.IPin_iface, sink, &req_mt); + ok(hr == S_OK, "Got hr %#x.\n", hr); + hr = IFilterGraph2_ConnectDirect(graph, source, renderer_pin, &req_mt); + ok(hr == S_OK, "Got hr %#x.\n", hr); + IPin_Release(renderer_pin); + + IFilterGraph2_QueryInterface(graph, &IID_IMediaFilter, (void **)&mf); + IMediaFilter_SetSyncSource(mf, NULL); + IMediaFilter_Release(mf); + + hr = IMemInputPin_ReceiveCanBlock(input); + ok(hr == S_OK, "Got hr %#x.\n", hr); + + hr = ISampleGrabber_GetCurrentBuffer(grabber, &size, buf); + ok(hr == VFW_E_WRONG_STATE, "Got hr %#x.\n", hr); + + hr = IMediaControl_Pause(control); + ok(hr == S_FALSE, "Got hr %#x.\n", hr); + hr = IMediaControl_GetState(control, 0, &state); + ok(hr == VFW_S_STATE_INTERMEDIATE, "Got hr %#x.\n", hr); + + thread = send_frame(input, 0); + hr = IMediaControl_GetState(control, 1000, &state); + ok(hr == S_OK, "Got hr %#x.\n", hr); + ok(WaitForSingleObject(thread, 100) == WAIT_TIMEOUT, "Thread should block in Receive().\n"); + + for (i = 0; i < 3; i++) + { + ticks = GetTickCount(); + hr = ISampleGrabber_GetCurrentBuffer(grabber, &size, buf); + ticks = GetTickCount() - ticks; + ok(hr == S_OK, "Got hr %#x.\n", hr); + ok(ticks < 100, "Got %u ticks.\n", ticks); + ok(size == sizeof(buf), "Got size %d.\n", size); + } + + hr = IMediaControl_Stop(control); + ok(hr == S_OK, "Got hr %#x.\n", hr); + hr = join_thread(thread); + ok(hr == S_OK, "Got hr %#x.\n", hr); + hr = IMediaControl_GetState(control, 1000, &state); + ok(hr == S_OK, "Got hr %#x.\n", hr); + ok(state == State_Stopped, "Got state %d.\n", state); + hr = ISampleGrabber_GetCurrentBuffer(grabber, &size, buf); + ok(hr == S_OK, "Got hr %#x.\n", hr); + + hr = IMediaControl_Pause(control); + ok(hr == S_FALSE, "Got hr %#x.\n", hr); + hr = IMediaControl_GetState(control, 0, &state); + ok(hr == VFW_S_STATE_INTERMEDIATE, "Got hr %#x.\n", hr); + + thread = send_frame(input, 0); + hr = IMediaControl_GetState(control, 1000, &state); + ok(hr == S_OK, "Got hr %#x.\n", hr); + ok(WaitForSingleObject(thread, 100) == WAIT_TIMEOUT, "Thread should block in Receive().\n"); + + for (i = 0; i < 3; i++) + { + ticks = GetTickCount(); + hr = ISampleGrabber_GetCurrentBuffer(grabber, &size, buf); + ticks = GetTickCount() - ticks; + ok(hr == S_OK, "Got hr %#x.\n", hr); + ok(ticks < 100, "Got %u ticks.\n", ticks); + ok(size == sizeof(buf), "Got size %d.\n", size); + } + + IPin_BeginFlush(sink); + hr = join_thread(thread); + ok(hr == S_OK, "Got hr %#x.\n", hr); + hr = ISampleGrabber_GetCurrentBuffer(grabber, &size, buf); + ok(hr == S_OK, "Got hr %#x.\n", hr); + IPin_EndFlush(sink); + + hr = IMediaControl_GetState(control, 0, &state); + todo_wine ok(hr == VFW_S_STATE_INTERMEDIATE, "Got hr %#x.\n", hr); + + ticks = GetTickCount(); + thread = send_frame(input, 150); + hr = ISampleGrabber_GetCurrentBuffer(grabber, &size, buf); + ticks = GetTickCount() - ticks; + ok(hr == S_OK, "Got hr %#x.\n", hr); + ok(ticks < 100, "Got %u ticks.\n", ticks); + ok(size == sizeof(buf), "Got size %d.\n", size); + + hr = IMediaControl_GetState(control, 1000, &state); + ok(hr == S_OK, "Got hr %#x.\n", hr); + hr = IMediaControl_Stop(control); + ok(hr == S_OK, "Got hr %#x.\n", hr); + hr = join_thread(thread); + todo_wine ok(hr == S_OK, "Got hr %#x.\n", hr); + + IPin_Release(sink); + IPin_Release(source); + IMemInputPin_Release(input); + IMediaControl_Release(control); + ref = IFilterGraph2_Release(graph); + ok(!ref, "Got outstanding refcount %d.\n", ref); + ISampleGrabber_Release(grabber); + ref = IBaseFilter_Release(filter); + ok(!ref, "Got outstanding refcount %d.\n", ref); + ref = IBaseFilter_Release(&testsource.filter.IBaseFilter_iface); + ok(!ref, "Got outstanding refcount %d.\n", ref); +} + START_TEST(samplegrabber) { IBaseFilter *filter; @@ -1059,6 +1292,7 @@ START_TEST(samplegrabber) test_aggregation(); test_media_types(); test_connect_pin(); + test_buffer_flush(); CoUninitialize(); } -- 2.21.0

5 7

[vkd3d] Handling object components within the HLSL compiler.
by Francisco Casas Sept. 20, 2022

Sept. 20, 2022

Hello, I write this update on what I am working on, because I think it introduces some architectural changes that may be good to discuss, or at least mention. Sorry if this text is a bit dense, I hope to send all this as a merge request in a couple of days from now. Albeit we may want to avoid merging before the code freeze ends. More than a week ago, I started trying to implement SM1 resource loads. For this, in particular, it is necessary to infer each sampler's dimensions from usage (a use in a tex2D implies that the sampler is 2D, if not previously declared as such). This gets complicated when there are arrays of samplers, because each sampler component can have a different dimension, and yet being part of the same variable. For solving this I tried introducing a field to allow us to store data for each component within hlsl_ir_var. But this turned to be a complicated solution. As now, we lost the component information in the derefs once we start working with register offsets. I also wanted to have per-component data because I realized that, in general, we are not handling object components properly when they are part of a larger array/struct. But then I thought on an alternative solution: adding a compiler pass to promote each object component within a large variable to a new standalone variable, and prepend a store from this standalone variable to the the original path of the component within the large variable; relying on copy-prop and dce so that all references that refer to these components end up pointing to the new standalone variable. This allows us to use the fields of the hlsl_ir_var (in particular, the register allocation) for each object component, which solves the problem. While that strategy works, I then realized that we cannot use it when targeting SM1 profiles, because we wouldn't be replicating the CTAB (which doesn't introduce a new variable for each component in multi-dimensional object arrays, just increases its register size). SM4 on the other hand seems to do this, separating each sampler and texture as its own variable in the RDEF block. My conclusion then, is that it is a good idea to separate each object component into its own variable in SM4 (as long they are named with the correct subscripts, like "foo.tex[3]"). And while we can't do that in SM1, the good news is that SM1 doesn't allow objects as components of larger types except within (possible multi-dimensional) arrays. Samplers and Textures cannot be components of structs within SM1 profiles, so we only have to support those cases in hlsl_sm1.c. This approach also has the benefit that now, all the component register allocation information should be representable using the fields in the hlsl_ir_var struct and the register size data within hlsl_type [1], since each variable should only care about a single register type now. Storing register allocation data component-wise should not be necessary. So I am implementing a series of patches to ensure that: * When targeting SM4 profiles, all object components are separated into a sole variable. * When targeting SM1 profiles, it is not allowed to declare objects as components of structs; so they will either be a sole variable, or belong to either a (possibly multi-dimensional) array of elements of the same type, as declared within the shader. * SM1 resource loads work. My plan for this series, in terms of patches is: * Parse the tex3D() intrinsic. (already made by zf) * Parse the tex2D() intrinsic. (already made by zf) * Validate that object are not components of structs in SM1. * Properly allocate registers for object arrays for SM1. * Infer sampler register dimensions and write declarations in SM1. * Write resource loads in SM1. * Separate objects as standalone variables in SM4. * Lower combined samplers to separate sampler and texture objects for SM4. (already made by zf) * Lower separate sampler and texture objects to combined samplers for SM1. (already made by zf) It remains to check if object arrays are handled properly in the last two [2], or modify these patches accordingly. Best regards, Francisco. --- [1] I know we intend to remove this field later, when we move register allocation to each sm*_write.c, but I think we probably want to replace those precomputed register offset fields with equivalent SM-specific functions that retrieve the register offset for each component. [2] In SM1 profiles, when there are texture arrays and they are used together with samplers, only one variable is created (not one for each pair of components). This is allowed: ``` Texture2D tex[3][2]; sampler sam; float4 main() : SV_TARGET { return tex[0][1].Sample(sam, float2(1, 2)) + tex[1][0].Sample(sam, float2(1, 2)); } ``` This is allowed (but "not yet implemented" in fxc 9 and 10) ``` Texture2D tex; sampler sam[2][3]; float4 main() : SV_TARGET { return tex.Sample(sam[0][2], float2(1, 2)) + tex.Sample(sam[1][0], float2(1, 2)); } ``` This is not allowed: ``` Texture2D tex[3]; sampler sam[4]; float4 PSMain() : SV_TARGET { return tex[1].Sample(sam[1], float2(1, 2)) + tex[2].Sample(sam[0], float2(1, 2)); } ``` gives: ``` error X4581: Cannot use texture arrays on DX9 targets with multiple samplers. ```

2 5

RFC: Allow marking unreliable tests as flaky.
by Francois Gouget Sept. 2, 2022

Sept. 2, 2022

Wine has many unreliable tests which makes it hard to know whether a patch causes new failures. So one proposal was to mark unreliable tests as flaky, and have a mode where flaky failures can ignored by setting $WINETEST_ALLOW_FLAKY. So one would be able to apply a patch, run 'WINETEST_ALLOW_FLAKY=1 make test' and if that fails that means the patch introduces a new failure. The way it works is that when a flaky test fails the message is 'Flaky failed...' instead of 'Test failed...'. I also added the count of flaky failures to the summary line. So the flaky failures are not totally swept under the rug. The main difference is that if $WINETEST_ALLOW_FLAKY is set, the exit code is 0 if the only failures are flaky ones. That still leaves some open questions though: * Should the message be 'Test failed' instead of 'Flaky failed' when $WINETEST_ALLOW_FLAKY is not set? I opted for the latter because it adds information that the failed test has been marked as flaky. * Should tests that fail systematically on some platforms but not others (for instance specific Windows versions, specific locales, specific GPUs) be marked as flaky? Or should flaky be reserved for tests that fail randomly? * What about failures where the message is different every time so that the failure always looks new? Should these not be marked as flaky since it only impacts the TestBot? * On a related note the patch below has flaky_windows and flaky_wine macros. Is that too fine grained? Maybe we don't want to run the risk of marking a test as flaky_windows only to discover later that it can also fail in Wine? But conversely, wouldn't it be valuable to know that a test is only flaky in Wine and not in Windows? Note: flaky_windows is a bit long but I was worried that flaky_win would be too similar to flaky_wine. * I decided having flaky_{windows,wine}_if() macros would be overkill. * How does one know a flaky directive can be removed? * Is it allowed to submit a patch that contains new flaky directives? * Also the flaky directive cannot deal with tests that randomly crash, prematurely exit, or time out. These issues are rarer so maybe we can hope they can all be fixed? * How does this impact bug 48912, aka "Allow blacklisting unreliable and always new failures"? https://bugs.winehq.org/show_bug.cgi?id=48912 * test.winehq.org and the TestBot will need to be updated to highlight the new messages and, more importantly, to recognize the new summary line. The patch is below and I bundled it with tweaks to a few tests for illustration purposes: d3d8:device - Failure happens on Windows (rarely) and Wine. dinput:mouse - Failure happens on Windows 7 and Wine. mmdevapi:render - Timing issue. schedsvc:atsvcapi - Wine-only failure. --- dlls/d3d8/tests/device.c | 2 +- dlls/dinput/tests/mouse.c | 2 +- dlls/mmdevapi/tests/render.c | 2 +- dlls/schedsvc/tests/atsvcapi.c | 2 +- include/wine/test.h | 78 +++++++++++++++++++++++++++++----- 5 files changed, 72 insertions(+), 14 deletions(-) diff --git a/dlls/d3d8/tests/device.c b/dlls/d3d8/tests/device.c index cb1e83b64b3..f0e8c27fafd 100644 --- a/dlls/d3d8/tests/device.c +++ b/dlls/d3d8/tests/device.c @@ -3356,7 +3356,7 @@ static void test_wndproc(void) expect_messages = sc_maximize_messages; SendMessageA(focus_window, WM_SYSCOMMAND, SC_MAXIMIZE, 0); - ok(!expect_messages->message, "Expected message %#x for window %#x, but didn't receive it.\n", + flaky ok(!expect_messages->message, "Expected message %#x for window %#x, but didn't receive it.\n", expect_messages->message, expect_messages->window); expect_messages = NULL; flush_events(); diff --git a/dlls/dinput/tests/mouse.c b/dlls/dinput/tests/mouse.c index 8be808e5da6..dcb5453a825 100644 --- a/dlls/dinput/tests/mouse.c +++ b/dlls/dinput/tests/mouse.c @@ -156,7 +156,7 @@ static void test_acquire(IDirectInputA *pDI, HWND hwnd) SetActiveWindow( hwnd ); hr = IDirectInputDevice_Acquire(pMouse); - ok(hr == S_OK, "Acquire() failed: %#lx\n", hr); + flaky ok(hr == S_OK, "Acquire() failed: %#lx\n", hr); mouse_event(MOUSEEVENTF_MOVE, 10, 10, 0, 0); cnt = 1; diff --git a/dlls/mmdevapi/tests/render.c b/dlls/mmdevapi/tests/render.c index 4e19b91c5f5..882be89b7ff 100644 --- a/dlls/mmdevapi/tests/render.c +++ b/dlls/mmdevapi/tests/render.c @@ -1098,7 +1098,7 @@ static void test_clock(int share) ok(pos == 0, "GetPosition returned non-zero pos before being started\n"); hr = IAudioClient_Start(ac); /* #1 */ - ok(hr == S_OK, "Start failed: %08lx\n", hr); + flaky ok(hr == S_OK, "Start failed: %08lx\n", hr); Sleep(100); slept += 100; diff --git a/dlls/schedsvc/tests/atsvcapi.c b/dlls/schedsvc/tests/atsvcapi.c index 3aaad8b5cfe..83774804b40 100644 --- a/dlls/schedsvc/tests/atsvcapi.c +++ b/dlls/schedsvc/tests/atsvcapi.c @@ -168,7 +168,7 @@ START_TEST(atsvcapi) skip_tests_delete: ret = NetrJobDel(server_name, jobid, jobid); - ok(ret == ERROR_SUCCESS, "NetrJobDel error %lu\n", ret); + flaky_wine ok(ret == ERROR_SUCCESS, "NetrJobDel error %lu\n", ret); skip_tests: SetUnhandledExceptionFilter(old_exception_filter); diff --git a/include/wine/test.h b/include/wine/test.h index 01ba81f4857..422ba3dce38 100644 --- a/include/wine/test.h +++ b/include/wine/test.h @@ -50,6 +50,9 @@ extern int winetest_time; /* running in interactive mode? */ extern int winetest_interactive; +/* always count flaky tests as successful (BOOL) */ +extern int winetest_allow_flaky; + /* report successful tests (BOOL) */ extern int winetest_report_success; @@ -117,6 +120,13 @@ extern void winetest_pop_context(void); #define trace trace_(__FILE__, __LINE__) #define wait_child_process wait_child_process_(__FILE__, __LINE__) +#define flaky_if(is_flaky) for (winetest_start_flaky(is_flaky); \ + winetest_loop_flaky(); \ + winetest_end_flaky()) +#define flaky flaky_if(1) +#define flaky_windows flaky_if(!strcmp(winetest_platform, "windows")) +#define flaky_wine flaky_if(!strcmp(winetest_platform, "wine")) + #define todo_if(is_todo) for (winetest_start_todo(is_todo); \ winetest_loop_todo(); \ winetest_end_todo()) @@ -200,6 +210,9 @@ int winetest_interactive = 0; /* current platform */ const char *winetest_platform = "windows"; +/* always count flaky tests as successful (BOOL) */ +int winetest_allow_flaky; + /* report successful tests (BOOL) */ int winetest_report_success = 0; @@ -214,6 +227,7 @@ static const struct test *current_test; /* test currently being run */ static LONG successes; /* number of successful tests */ static LONG failures; /* number of failures */ +static LONG flaky_failures; /* number of failures inside flaky block */ static LONG skipped; /* number of skipped test chunks */ static LONG todo_successes; /* number of successful tests inside todo block */ static LONG todo_failures; /* number of failures inside todo block */ @@ -229,6 +243,8 @@ struct tls_data { const char* current_file; /* file of current check */ int current_line; /* line of current check */ + unsigned int flaky_level; /* current flaky nesting level */ + int flaky_do_loop; unsigned int todo_level; /* current todo nesting level */ int todo_do_loop; char *str_pos; /* position in debug buffer */ @@ -355,9 +371,18 @@ int winetest_vok( int condition, const char *msg, va_list args ) { if (condition) { - winetest_print_context( "Test succeeded inside todo block: " ); - vprintf(msg, args); - InterlockedIncrement(&todo_failures); + if (data->flaky_level) + { + winetest_print_context( "Flaky succeeded inside todo block: " ); + vprintf(msg, args); + InterlockedIncrement(&flaky_failures); + } + else + { + winetest_print_context( "Test succeeded inside todo block: " ); + vprintf(msg, args); + InterlockedIncrement(&todo_failures); + } return 0; } else @@ -381,9 +406,18 @@ int winetest_vok( int condition, const char *msg, va_list args ) { if (!condition) { - winetest_print_context( "Test failed: " ); - vprintf(msg, args); - InterlockedIncrement(&failures); + if (data->flaky_level) + { + winetest_print_context( "Flaky failed: " ); + vprintf(msg, args); + InterlockedIncrement(&flaky_failures); + } + else + { + winetest_print_context( "Test failed: " ); + vprintf(msg, args); + InterlockedIncrement(&failures); + } return 0; } else @@ -456,6 +490,27 @@ void winetest_win_skip( const char *msg, ... ) va_end(valist); } +void winetest_start_flaky( int is_flaky ) +{ + struct tls_data *data = get_tls_data(); + data->flaky_level = (data->flaky_level << 1) | (is_flaky != 0); + data->flaky_do_loop=1; +} + +int winetest_loop_flaky(void) +{ + struct tls_data *data = get_tls_data(); + int do_flaky=data->flaky_do_loop; + data->flaky_do_loop=0; + return do_flaky; +} + +void winetest_end_flaky(void) +{ + struct tls_data *data = get_tls_data(); + data->flaky_level >>= 1; +} + void winetest_start_todo( int is_todo ) { struct tls_data *data = get_tls_data(); @@ -601,14 +656,16 @@ static int run_test( const char *name ) printf( "%04x:%s:%s Silenced %d todos, %d skips and %d traces.\n", (UINT)GetCurrentProcessId(), test->name, winetest_elapsed(), (UINT)muted_todo_successes, (UINT)muted_skipped, (UINT)muted_traces); - printf( "%04x:%s:%s %d tests executed (%d marked as todo, %d %s), %d skipped.\n", + printf( "%04x:%s:%s %d tests executed (%d marked as todo, %d as flaky, %d %s), %d skipped.\n", (UINT)GetCurrentProcessId(), test->name, winetest_elapsed(), - (UINT)(successes + failures + todo_successes + todo_failures), - (UINT)todo_successes, (UINT)(failures + todo_failures), + (UINT)(successes + failures + flaky_failures + todo_successes + todo_failures), + (UINT)todo_successes, (UINT)flaky_failures, (UINT)(failures + todo_failures), (failures + todo_failures != 1) ? "failures" : "failure", (UINT)skipped ); } - status = (failures + todo_failures < 255) ? failures + todo_failures : 255; + status = failures + todo_failures; + if (!winetest_allow_flaky) status += flaky_failures; + if (status > 255) status = 255; return status; } @@ -665,6 +722,7 @@ int main( int argc, char **argv ) if (GetEnvironmentVariableA( "WINETEST_DEBUG", p, sizeof(p) )) winetest_debug = atoi(p); if (GetEnvironmentVariableA( "WINETEST_INTERACTIVE", p, sizeof(p) )) winetest_interactive = atoi(p); + if (GetEnvironmentVariableA( "WINETEST_ALLOW_FLAKY", p, sizeof(p) )) winetest_allow_flaky = atoi(p); if (GetEnvironmentVariableA( "WINETEST_REPORT_SUCCESS", p, sizeof(p) )) winetest_report_success = atoi(p); if (GetEnvironmentVariableA( "WINETEST_TIME", p, sizeof(p) )) winetest_time = atoi(p); winetest_last_time = winetest_start_time = GetTickCount(); -- 2.30.2

7 12

Puzzling IPrincipal:UserId check in taskschd
by Francois Gouget Aug. 31, 2022

Aug. 31, 2022

So I'm a bit puzzled by this check in taskschd/task.c's write_principal(): hr = IPrincipal_get_UserId(principal, &bstr); if (hr == S_OK && lstrlenW(bstr)) { hr = write_text_value(stream, L"UserId", bstr); What's puzzling to me is the lstrlenW(bstr) check: * write_principal() has no such check for Id, GroupId, DisplayName and RunLevel. Maybe that's because they are guaranteed to be set and non empty but I could not find any documentation saying so and they are not implemented in Wine. * write_registration_info() is very similar but checks bstr, not what is in effect *bstr: hr = IRegistrationInfo_get_Source(reginfo, &bstr); if (hr == S_OK && bstr) { hr = write_text_value(stream, L"Source", bstr); * We don't seem to have tests showing how this works. I would expect all these property getters to work the same way. So would something like that make more sense? hr = IPrincipal_get_UserId(principal, &bstr); if (hr == S_OK && bstr) { hr = write_text_value(stream, L"UserId", bstr); Dmitry: Do you remember if you wrote the lstrlenW(bstr) check because of some test you did? -- Francois Gouget <fgouget(a)free.fr> http://fgouget.free.fr/ Computers are like airconditioners They stop working properly if you open WINDOWS

2 1

Whenever i use wine this message pop up and the application doesn't run please any help
by anthonyuser33 Aug. 31, 2022

Aug. 31, 2022

Sent from my Galaxy

1 0

Wine staging 7.16 release
by Alistair Leslie-Hughes Aug. 29, 2022

Aug. 29, 2022

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 7.16 (531 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * wined3d: Use wined3d_array_reserve() in wined3d_adapter_create_output(). * dsdmo: Add Echo FX Support * dsdmo: Add Compressor FX Support * ddraw: Don't set HWTRANSFORMANDLIGHT flag on d3d7 RGB device. Added: * None Updated: * none Where can you help * Run Steam/Battle.net/GOG/UPlay/Epic * Test your favorite game. * Test your favorite applications. * Improve staging patches and get them accepted upstream. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

1 0

[PATCH 1/2] readme: Update Finnish translation.
by Lauri Kenttä Aug. 29, 2022

Aug. 29, 2022

Signed-off-by: Lauri Kenttä <lauri.kentta(a)gmail.com> --- documentation/README.fi | 10 ++-------- 1 file changed, 2 insertions(+), 8 deletions(-) diff --git a/documentation/README.fi b/documentation/README.fi index e459bbc779a..00af959c033 100644 --- a/documentation/README.fi +++ b/documentation/README.fi @@ -146,6 +146,8 @@ Kysymyksiä: Wiki: Wine Wiki on osoitteessa https://wiki.winehq.org/. +Gitlab: Winen kehitykseen voi osallistua sivustolla https://gitlab.winehq.org + Postituslistat: Winen käyttäjille ja kehittäjille on joitakin postituslistoja, sivulla https://www.winehq.org/forums kerrotaan niistä lisää. @@ -157,14 +159,6 @@ Virheet: IRC: Online-apua voi saada kanavalta #WineHQ palvelimella irc.libera.chat. -Git: Winen tämänhetkinen kehitysversio on jaossa Git-järjestelmän kautta. - Sivulla https://www.winehq.org/git kerrotaan tästä lisää. - - -Jos lisäät jotain tai korjaat jonkin virheen, lähetä toki muutoksesi -(mieluiten komennon git-format-patch avulla) listalle wine-devel(a)winehq.org, -jotta se voidaan lisätä Winen seuraavaan versioon. - -- Alkuperäisen version tekstistä on kirjoittanut Alexandre Julliard -- 2.37.2

2 2

Upcoming vkd3d 1.5 release.
by Henri Verbeet Aug. 24, 2022

Aug. 24, 2022

Hi all, As previously discussed, we'd like to release vkd3d 1.5 in about 4 weeks. Practically speaking, that means that as we're nearing that date, the vkd3d tree is going to become progressively frozen, starting today. Now is the time to test your games for any regressions, review any API changes since vkd3d 1.4, review/improve the API documentation, and so on. If you're working on any larger features or architectural changes, ideally you'd have those ready to merge shortly after the 1.5 release, so that they'll make it into the 1.6 release, tentatively planned for early December. Regards, Henri

1 0

wine-devel moved to Mailman3
by Jeremy Newman Aug. 22, 2022

Aug. 22, 2022

This list has been migrated to a new interface. To manage your subscription go here: https://www.winehq.org/mailman3/postorius/lists/wine-devel.winehq.org/ To view the archives go here: https://www.winehq.org/mailman3/hyperkitty/list/wine-devel(a)winehq.org/ The old archives will remain online to preserve links. -N

1 0

WINE and Haxial programs
by haxial Aug. 22, 2022

Aug. 22, 2022

Hi There My company produces a few programs that run on Windows and MacOS. Some of the users of these programs have been experimenting using WINE to run the programs on Linux. This is what they have been saying: "the KDX server runs FLAWLESSLY, 100% perfect, better than solitaire runs" However, there is one caveat to the above: I'm told that text input doesn't work when running KDX using WINE on Linux. I was wondering if I would be able to work with WINE developers in making KDX run perfectly on Linux using WINE. I think you would find this to be an easier task than usual because KDX only uses a *minimal* amount of windoze APIs. For example, KDX implements it's own GUI, it does not use the windoze API for that. Also, KDX even implements it's own graphics routines, it does not use the windoze GDI functions (except for the final step of getting the images onto the screen). KDX loads no obscure DLL's, it's just a single .exe file. It does not use MDI or any crap like that. It does not access the registry. It does not use MFC. So I think it would be much easier for WINE than your average windoze program. Which probably explains why it's already running well, except there is some bug, probably a minor little thing, that is preventing text input from working. The website is: http://www.haxial.com Thanks.

1 0

[PATCH 1/2] user32/tests: Add some tests for font charset returned by SPI_GETICONTITLELOGFONT and SPI_GETNONCLIENTMETRICS.
by Dmitry Timoshkov Aug. 18, 2022

Aug. 18, 2022

Signed-off-by: Dmitry Timoshkov <dmitry(a)baikal.ru> --- dlls/user32/tests/sysparams.c | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/dlls/user32/tests/sysparams.c b/dlls/user32/tests/sysparams.c index 4f2709094e9..e354ef69a94 100644 --- a/dlls/user32/tests/sysparams.c +++ b/dlls/user32/tests/sysparams.c @@ -4124,6 +4124,31 @@ static void test_GetAutoRotationState(void) ok(ret, "Expected GetAutoRotationState to succeed, error %ld\n", GetLastError()); } +static void test_LOGFONT_charset(void) +{ + CHARSETINFO csi; + LOGFONTA lf; + NONCLIENTMETRICSA ncm; + BOOL ret; + + ret = TranslateCharsetInfo(ULongToPtr(GetACP()), &csi, TCI_SRCCODEPAGE); + ok(ret, "TranslateCharsetInfo(%d) error %lu\n", GetACP(), GetLastError()); + + GetObjectA(GetStockObject(DEFAULT_GUI_FONT), sizeof(lf), &lf); + ok(lf.lfCharSet == csi.ciCharset, "got %d, expected %d\n", lf.lfCharSet, csi.ciCharset); + + ret = SystemParametersInfoA(SPI_GETICONTITLELOGFONT, sizeof(lf), &lf, FALSE); + ok(ret, "SystemParametersInfoW error %lu\n", GetLastError()); + todo_wine + ok(lf.lfCharSet == DEFAULT_CHARSET, "got %d\n", lf.lfCharSet); + + ncm.cbSize = FIELD_OFFSET(NONCLIENTMETRICSA, iPaddedBorderWidth); + ret = SystemParametersInfoA(SPI_GETNONCLIENTMETRICS, 0, &ncm, 0); + ok(ret, "SystemParametersInfoW error %lu\n", GetLastError()); + todo_wine + ok(ncm.lfCaptionFont.lfCharSet == DEFAULT_CHARSET, "got %d\n", ncm.lfCaptionFont.lfCharSet); +} + START_TEST(sysparams) { int argc; @@ -4172,6 +4197,8 @@ START_TEST(sysparams) strict=(argc >= 3 && strcmp(argv[2],"strict")==0); trace("strict=%d\n",strict); + test_LOGFONT_charset(); + trace("testing GetSystemMetrics with your current desktop settings\n"); test_GetSystemMetrics( ); test_metrics_for_dpi( 192 ); -- 2.37.2

2 2

[PATCH 2/2] user32: Set font charset to DEFAULT_CHARSET to support locale change.
by Dmitry Timoshkov Aug. 18, 2022

Aug. 18, 2022

Otherwise when the prefix was created with one locale and later an application in the prefix is running with a different locale values cached in the registry lead to broken UI. Signed-off-by: Dmitry Timoshkov <dmitry(a)baikal.ru> --- dlls/user32/tests/sysparams.c | 4 ++-- dlls/win32u/sysparams.c | 4 ++++ 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/dlls/user32/tests/sysparams.c b/dlls/user32/tests/sysparams.c index e354ef69a94..6ab7010c4ed 100644 --- a/dlls/user32/tests/sysparams.c +++ b/dlls/user32/tests/sysparams.c @@ -4139,14 +4139,13 @@ static void test_LOGFONT_charset(void) ret = SystemParametersInfoA(SPI_GETICONTITLELOGFONT, sizeof(lf), &lf, FALSE); ok(ret, "SystemParametersInfoW error %lu\n", GetLastError()); - todo_wine ok(lf.lfCharSet == DEFAULT_CHARSET, "got %d\n", lf.lfCharSet); ncm.cbSize = FIELD_OFFSET(NONCLIENTMETRICSA, iPaddedBorderWidth); ret = SystemParametersInfoA(SPI_GETNONCLIENTMETRICS, 0, &ncm, 0); ok(ret, "SystemParametersInfoW error %lu\n", GetLastError()); - todo_wine ok(ncm.lfCaptionFont.lfCharSet == DEFAULT_CHARSET, "got %d\n", ncm.lfCaptionFont.lfCharSet); + ok(ncm.lfSmCaptionFont.lfCharSet == DEFAULT_CHARSET, "got %d\n", ncm.lfSmCaptionFont.lfCharSet); } START_TEST(sysparams) diff --git a/dlls/win32u/sysparams.c b/dlls/win32u/sysparams.c index 52665f7a641..879dffb58e2 100644 --- a/dlls/win32u/sysparams.c +++ b/dlls/win32u/sysparams.c @@ -3039,12 +3039,14 @@ static BOOL get_font_entry( union sysparam_all_entry *entry, UINT int_param, voi switch (load_entry( &entry->hdr, &font, sizeof(font) )) { case sizeof(font): + font.lfCharSet = DEFAULT_CHARSET; /* Support locale change */ if (font.lfHeight > 0) /* positive height value means points ( inch/72 ) */ font.lfHeight = -muldiv( font.lfHeight, USER_DEFAULT_SCREEN_DPI, 72 ); entry->font.val = font; break; case sizeof(LOGFONT16): /* win9x-winME format */ logfont16to32( (LOGFONT16 *)&font, &entry->font.val ); + entry->font.val.lfCharSet = DEFAULT_CHARSET; /* Support locale change */ if (entry->font.val.lfHeight > 0) entry->font.val.lfHeight = -muldiv( entry->font.val.lfHeight, USER_DEFAULT_SCREEN_DPI, 72 ); break; @@ -3055,6 +3057,7 @@ static BOOL get_font_entry( union sysparam_all_entry *entry, UINT int_param, voi /* fall through */ case 0: /* use the default GUI font */ NtGdiExtGetObjectW( GetStockObject( DEFAULT_GUI_FONT ), sizeof(font), &font ); + font.lfCharSet = DEFAULT_CHARSET; /* Support locale change */ font.lfHeight = map_from_system_dpi( font.lfHeight ); font.lfWeight = entry->font.weight; entry->font.val = font; @@ -3094,6 +3097,7 @@ static BOOL set_font_entry( union sysparam_all_entry *entry, UINT int_param, voi static BOOL init_font_entry( union sysparam_all_entry *entry ) { NtGdiExtGetObjectW( GetStockObject( DEFAULT_GUI_FONT ), sizeof(entry->font.val), &entry->font.val ); + entry->font.val.lfCharSet = DEFAULT_CHARSET; /* Support locale change */ entry->font.val.lfHeight = map_from_system_dpi( entry->font.val.lfHeight ); entry->font.val.lfWeight = entry->font.weight; get_real_fontname( &entry->font.val, entry->font.fullname ); -- 2.37.2

1 0

wine-cvs renamed to wine-commits
by Jeremy Newman Aug. 17, 2022

Aug. 17, 2022

The wine-cvs mailing list for git push notifications has *finally* been renamed to wine-commits. How many years has it been since we switched away from cvs? Something like 15 years! We also migrated the list over to mailman v3 so the links to the archives and subscription management have changed. The old archives will remain online to not break links. All the lists save one have been migrated. We will be migrating wine-devel soonish(tm). Updated links to the mailing lists and archives are here: https://www.winehq.org/forums Remember to update your email filters. -N

1 0

Patch tracker
by Alexandre Julliard Aug. 16, 2022

Aug. 16, 2022

Folks, We now have an automated reviewer assignment bot in Gitlab, thanks to the work of Jeremy White, so I think it's time to retire the wine-devel patch tracker. From now on, please submit everything through merge requests; patches sent to wine-devel will no longer be applied. Some reminders about the new policies: - Adding a Signed-off-by header is no longer necessary. This is replaced by the Gitlab approval mechanism. - When a new MR is submitted, the bot will assign reviewers based on the MAINTAINERS file. If the bot got it wrong, or if you would like to request reviews from other people, feel free to modify the list of reviewers. - If you don't have permission to modify reviewers, you should request access to the Wine project. There should be a link for this on the main project page at https://gitlab.winehq.org/wine/wine - I won't merge a MR until all reviewers have approved it. If you are assigned as reviewer but are unable/unwilling to review that MR, please unassign yourself so that the MR isn't blocked waiting for your approval. - In general, approving your own MR is not necessary or useful. - As an exception to the above, if your MR contains commits authored by someone else, you are asked to explicitly approve it. The bot will assign you as an extra reviewer in that case. - Approval information is stored in git notes. You can fetch the refs/notes/commits head if you'd like to see that information in your local tree. - We now have a CI pipeline to make sure that all the commits of a MR compile cleanly. Later on, the pipeline will also run the tests. Make sure to check the pipeline results; a MR with a failed pipeline won't be merged. Questions? Comments? -- Alexandre Julliard julliard(a)winehq.org

4 7

[PATCH] qedit: Remove "ugly" work around
by Brendan McGrath Aug. 14, 2022

Aug. 14, 2022

This patch removes a work around that causes a crash in Unravel Two. There is a callback in Unravel Two that appears to add a reference to a IMediaSample, which this work around treats as a leak and releases. However, the application also releases the reference causing a negative overflow and an assertion failure on line 345 of dlls/quartz/memallocator.c. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=51616 Signed-off-by: Brendan McGrath <brendan(a)redmandi.com> --- Although I'm not convinced just deleting 12 yr old code is a great idea, the original author did describe this work around as "ugly". I would describe it as unsafe. See Wine Bug 51616. I think it may also be possible for the work around to fail in a multi-threaded scenario, where the IMediaSample is accessed in parallel to the callback; potentially with a negative overflow of its own (and looping 4294967295 times). Although I'm not familiar enough with the uses of qedit to understand if this is even plausible. Unfortunately, I've only tested the removal of this work around with the one application; Unravel Two. Also note that I've only been able to test this "fix" with a local build of Proton 7 Experimental. I couldn't get the application to run in vanilla Wine (as the Origin launcher failed to install). Definitely interested in thoughts. dlls/qedit/samplegrabber.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/dlls/qedit/samplegrabber.c b/dlls/qedit/samplegrabber.c index 9b9780e564a8..cefb2f370785 100644 --- a/dlls/qedit/samplegrabber.c +++ b/dlls/qedit/samplegrabber.c @@ -164,9 +164,6 @@ static void SampleGrabber_callback(struct sample_grabber *This, IMediaSample *sa if (ref) { ERR("(%p) Callback referenced sample %p by %lu\n", This, sample, ref); - /* ugly as hell but some apps are sooo buggy */ - while (ref--) - IMediaSample_Release(sample); } } break; -- 2.34.1

4 6

Wine staging 7.15 release
by Alistair Leslie-Hughes Aug. 13, 2022

Aug. 13, 2022

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 7.15 (536 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * xactengine3_7: Record context for each notification. * xactengine3_7: Add helper function to add entries. * xactengine3_7: Map SoundBank interfaces. * xactengine3_7: Map IXACT3Cue interfaces. * xactengine3_7: Map IXACT3Wave interfaces. * xactengine3_7: Implement callback for supported messages. Added: * [52396] ntdll: Don't use Wine frames during exception processing on x64. * [52396] dsdmo: Add more FX interfaces. * [53497] wined3d: Use wined3d_array_reserve() in wined3d_adapter_create_output() Updated: * none Where can you help * Run Steam/Battle.net/GOG/UPlay/Epic * Test your favorite game. * Test your favorite applications. * Improve staging patches and get them accepted upstream. As always, if you find a bug, please report it via https://bugs.winehq.org Best Regards Alistair.

1 0

Re: [PATCH v2 3/3] d3d11: Implement D3D11_FEATURE_FORMAT_SUPPORT.
by Marvin Aug. 12, 2022

Aug. 12, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=121155 Your paranoid android. === w1064 (32 bit report) === d3d11: d3d11.c:5914: Test failed: Got unexpected query result 0x0000000000000000. === debian11 (64 bit WoW report) === d3d11: d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:28519: Test succeeded inside todo block: Feature level 0xb000: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28528: Test succeeded inside todo block: Feature level 0xb000: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28519: Test failed: Feature level 0xa000: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28519: Test failed: Feature level 0xa100: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28528: Test failed: Feature level 0xa000: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28528: Test failed: Feature level 0xa100: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0.

1 0

Re: [PATCH v2 2/3] d3d11: Always return E_FAIL for formats which have no support flags.
by Marvin Aug. 12, 2022

Aug. 12, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=121154 Your paranoid android. === debian11 (64 bit WoW report) === d3d11: d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Test marked todo: Feature level 0xb000: Format 0x5b - display not supported, format support 0x80f3f1. d3d11.c:1571: Test succeeded inside todo block: d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: d3d11.c:1576: Test marked todo: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:9946: Test failed: d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:28489: Test succeeded inside todo block: Feature level 0xb000: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28498: Test succeeded inside todo block: Feature level 0xb000: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28489: Test failed: Feature level 0xa100: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28489: Test failed: Feature level 0xa000: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28498: Test failed: Feature level 0xa000: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28498: Test failed: Feature level 0xa100: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0.

1 0

Re: [PATCH v2 1/3] d3d11/tests: Use winetest_push_context() to print explicit feature levels.
by Marvin Aug. 12, 2022

Aug. 12, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=121153 Your paranoid android. === w10pro64 (32 bit report) === d3d11: d3d11.c:5914: Test failed: Got unexpected query result 0x0000000000000000. === debian11 (64 bit WoW report) === d3d11: d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1571: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1573: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1576: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:28486: Test succeeded inside todo block: Feature level 0xb000: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28486: Test failed: Feature level 0xa000: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28495: Test succeeded inside todo block: Feature level 0xb000: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28486: Test failed: Feature level 0xa100: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28495: Test failed: Feature level 0xa000: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28495: Test failed: Feature level 0xa100: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0.

1 0

Re: [PATCH 3/3] d3d11: Implement D3D11_FEATURE_FORMAT_SUPPORT.
by Marvin Aug. 11, 2022

Aug. 11, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=121056 Your paranoid android. === w1064_adm (64 bit report) === d3d11: d3d11.c:5910: Test failed: Got unexpected query result 0x0000000000000000. === debian11 (32 bit report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Arabic:Morocco report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit German report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit French report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Hebrew:Israel report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Hindi:India report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Japanese:Japan report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Chinese:China report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit WoW report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (64 bit WoW report) === d3d11: d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:16831: Test failed: Feature level 0: Dim 0, Test 15: At layer 0, (0,0,0), expected 0x00c01001, got 0x00000000. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:16831: Test failed: Feature level 0: Dim 1, Test 15: At layer 0, (0,0,0), expected 0x00c01001, got 0x00000000. d3d11.c:16831: Test failed: Feature level 0: Dim 2, Test 15: At layer 0, (0,0,0), expected 0x00c01001, got 0x00000000. d3d11.c:28515: Test failed: Feature level 0xa100: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28515: Test succeeded inside todo block: Feature level 0xb000: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28524: Test failed: Feature level 0xa100: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28524: Test succeeded inside todo block: Feature level 0xb000: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). d3d11.c:28515: Test failed: Feature level 0xa000: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28524: Test failed: Feature level 0xa000: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28461: Test failed: Feature level 0: Got texcoord {8.43750119e-001, 1.56249911e-001}, expected {8.43750000e-001, 1.56250000e-001} at (3, 3), offset 1.25000000e-001. d3d11.c:28461: Test failed: Feature level 0: Got texcoord {8.71093690e-001, 1.28906295e-001}, expected {8.71093750e-001, 1.28906250e-001} at (3, 3), offset 1.56250000e-002. d3d11.c:28461: Test failed: Feature level 0: Got texcoord {7.51953065e-001, 2.48046920e-001}, expected {7.51953125e-001, 2.48046875e-001} at (3, 3), offset 4.92187500e-001. d3d11.c:20298: Test failed: Feature level 0: Got {0xfffe0000, 0xfffe0000, 0xfffe0000, 0xfffe0000}, expected {0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0xfffffffe, 0xfffffffe, 0xfffffffe, 0xfffffffe}, expected {0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0x00000000, 0x00000000, 0x00000000, 0x00000000}, expected {0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0xfffffffe, 0xfffffffe, 0xfffffffe, 0xfffffffe}, expected {0x00000000, 0x00000000, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0x80000000, 0x00000000, 0x00000000, 0x00000000}, expected {0x00000000, 0xffffffff, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0x00000000, 0x80000000, 0x00000000, 0x00000000}, expected {0xffffffff, 0x00000000, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0xffffffff, 0x00000001, 0x00000000, 0x00000000}, expected {0x00000000, 0x00000001, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0x00000001, 0xffffffff, 0x00000000, 0x00000000}, expected {0x00000001, 0x00000000, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:28278: Test failed: Feature level 0: Got depth 4.99374978e-003, expected 4.99999989e-003. d3d11.c:28278: Test failed: Feature level 0: Got depth 4.99374978e-003, expected 4.99999989e-003. d3d11.c:28278: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28278: Test failed: Feature level 0: Got depth 7.48750009e-003, expected 7.49999983e-003. d3d11.c:28278: Test failed: Feature level 0: Got depth 7.48750009e-003, expected 7.49999983e-003. d3d11.c:28278: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28278: Test failed: Feature level 0: Got depth 1.24749998e-002, expected 1.24999997e-002. d3d11.c:28278: Test failed: Feature level 0: Got depth 1.24749998e-002, expected 1.24999997e-002. d3d11.c:28278: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28278: Test failed: Feature level 0: Got depth 6.40899956e-001, expected 6.42499986e-001. d3d11.c:28278: Test failed: Feature level 0: Got depth 6.40899956e-001, expected 6.42499986e-001. d3d11.c:28278: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28278: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28278: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28286: Test failed: Feature level 0: Got value 0x14745 (4.99373721e-003), expected 0x147ae (4.99999570e-003). d3d11.c:28286: Test failed: Feature level 0: Got value 0x14745 (4.99373721e-003), expected 0x147ae (4.99999570e-003). d3d11.c:28286: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28286: Test failed: Feature level 0: Got value 0x1eab3 (7.48747634e-003), expected 0x1eb85 (7.49999331e-003). d3d11.c:28286: Test failed: Feature level 0: Got value 0x1eab3 (7.48747634e-003), expected 0x1eb85 (7.49999331e-003). d3d11.c:28286: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28286: Test failed: Feature level 0: Got value 0x33190 (1.24750147e-002), expected 0x33333 (1.24999890e-002). d3d11.c:28286: Test failed: Feature level 0: Got value 0x33190 (1.24750147e-002), expected 0x33333 (1.24999890e-002). d3d11.c:28286: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28286: Test failed: Feature level 0: Got value 0xa41204 (6.40899956e-001), expected 0xa47ae0 (6.42499983e-001). d3d11.c:28286: Test failed: Feature level 0: Got value 0xa41204 (6.40899956e-001), expected 0xa47ae0 (6.42499983e-001). d3d11.c:28286: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28286: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28286: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28295: Test failed: Feature level 0: Got value 0x28e (9.97940078e-003), expected 0x290 (1.00099184e-002). d3d11.c:28295: Test failed: Feature level 0: Got value 0x28e (9.97940078e-003), expected 0x290 (1.00099184e-002). d3d11.c:28295: Test failed: Feature level 0: Got value 0x331 (1.24666207e-002), expected 0x334 (1.25123980e-002). d3d11.c:28295: Test failed: Feature level 0: Got value 0x331 (1.24666207e-002), expected 0x334 (1.25123980e-002). d3d11.c:28295: Test failed: Feature level 0: Got value 0x476 (1.74258035e-002), expected 0x47b (1.75020974e-002). d3d11.c:28295: Test failed: Feature level 0: Got value 0x476 (1.74258035e-002), expected 0x47b (1.75020974e-002). d3d11.c:28295: Test failed: Feature level 0: Got value 0xa411 (6.40894175e-001), expected 0xa47a (6.42496347e-001). d3d11.c:28295: Test failed: Feature level 0: Got value 0xa411 (6.40894175e-001), expected 0xa47a (6.42496347e-001).

1 0

Re: [PATCH 2/3] d3d11: Always return E_FAIL for formats which have no support flags.
by Marvin Aug. 11, 2022

Aug. 11, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=121055 Your paranoid android. === debian11 (32 bit report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Arabic:Morocco report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit German report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit French report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Hebrew:Israel report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Hindi:India report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Japanese:Japan report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Chinese:China report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit WoW report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (64 bit WoW report) === d3d11: d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:16831: Test failed: Feature level 0: Dim 0, Test 15: At layer 0, (0,0,0), expected 0x00c01001, got 0x00000000. d3d11.c:16831: Test failed: Feature level 0: Dim 1, Test 15: At layer 0, (0,0,0), expected 0x00c01001, got 0x00000000. d3d11.c:28485: Test succeeded inside todo block: Feature level 0xb000: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:16831: Test failed: Feature level 0: Dim 2, Test 15: At layer 0, (0,0,0), expected 0x00c01001, got 0x00000000. d3d11.c:28485: Test failed: Feature level 0xa000: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28494: Test succeeded inside todo block: Feature level 0xb000: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28494: Test failed: Feature level 0xa000: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28431: Test failed: Feature level 0: Got texcoord {8.43750119e-001, 1.56249911e-001}, expected {8.43750000e-001, 1.56250000e-001} at (3, 3), offset 1.25000000e-001. d3d11.c:28485: Test failed: Feature level 0xa100: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28494: Test failed: Feature level 0xa100: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28431: Test failed: Feature level 0: Got texcoord {8.71093690e-001, 1.28906295e-001}, expected {8.71093750e-001, 1.28906250e-001} at (3, 3), offset 1.56250000e-002. d3d11.c:28431: Test failed: Feature level 0: Got texcoord {7.51953065e-001, 2.48046920e-001}, expected {7.51953125e-001, 2.48046875e-001} at (3, 3), offset 4.92187500e-001. d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). d3d11.c:20298: Test failed: Feature level 0: Got {0xfffe0000, 0xfffe0000, 0xfffe0000, 0xfffe0000}, expected {0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0xfffffffe, 0xfffffffe, 0xfffffffe, 0xfffffffe}, expected {0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0x00000000, 0x00000000, 0x00000000, 0x00000000}, expected {0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0xfffffffe, 0xfffffffe, 0xfffffffe, 0xfffffffe}, expected {0x00000000, 0x00000000, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0x80000000, 0x00000000, 0x00000000, 0x00000000}, expected {0x00000000, 0xffffffff, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0x00000000, 0x80000000, 0x00000000, 0x00000000}, expected {0xffffffff, 0x00000000, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0xffffffff, 0x00000001, 0x00000000, 0x00000000}, expected {0x00000000, 0x00000001, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0x00000001, 0xffffffff, 0x00000000, 0x00000000}, expected {0x00000001, 0x00000000, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:28248: Test failed: Feature level 0: Got depth 4.99374978e-003, expected 4.99999989e-003. d3d11.c:28248: Test failed: Feature level 0: Got depth 4.99374978e-003, expected 4.99999989e-003. d3d11.c:28248: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28248: Test failed: Feature level 0: Got depth 7.48750009e-003, expected 7.49999983e-003. d3d11.c:28248: Test failed: Feature level 0: Got depth 7.48750009e-003, expected 7.49999983e-003. d3d11.c:28248: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28248: Test failed: Feature level 0: Got depth 1.24749998e-002, expected 1.24999997e-002. d3d11.c:28248: Test failed: Feature level 0: Got depth 1.24749998e-002, expected 1.24999997e-002. d3d11.c:28248: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28248: Test failed: Feature level 0: Got depth 6.40899956e-001, expected 6.42499986e-001. d3d11.c:28248: Test failed: Feature level 0: Got depth 6.40899956e-001, expected 6.42499986e-001. d3d11.c:28248: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28248: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28248: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28256: Test failed: Feature level 0: Got value 0x14745 (4.99373721e-003), expected 0x147ae (4.99999570e-003). d3d11.c:28256: Test failed: Feature level 0: Got value 0x14745 (4.99373721e-003), expected 0x147ae (4.99999570e-003). d3d11.c:28256: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28256: Test failed: Feature level 0: Got value 0x1eab3 (7.48747634e-003), expected 0x1eb85 (7.49999331e-003). d3d11.c:28256: Test failed: Feature level 0: Got value 0x1eab3 (7.48747634e-003), expected 0x1eb85 (7.49999331e-003). d3d11.c:28256: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28256: Test failed: Feature level 0: Got value 0x33190 (1.24750147e-002), expected 0x33333 (1.24999890e-002). d3d11.c:28256: Test failed: Feature level 0: Got value 0x33190 (1.24750147e-002), expected 0x33333 (1.24999890e-002). d3d11.c:28256: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28256: Test failed: Feature level 0: Got value 0xa41204 (6.40899956e-001), expected 0xa47ae0 (6.42499983e-001). d3d11.c:28256: Test failed: Feature level 0: Got value 0xa41204 (6.40899956e-001), expected 0xa47ae0 (6.42499983e-001). d3d11.c:28256: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28256: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28256: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28265: Test failed: Feature level 0: Got value 0x28e (9.97940078e-003), expected 0x290 (1.00099184e-002). d3d11.c:28265: Test failed: Feature level 0: Got value 0x28e (9.97940078e-003), expected 0x290 (1.00099184e-002). d3d11.c:28265: Test failed: Feature level 0: Got value 0x331 (1.24666207e-002), expected 0x334 (1.25123980e-002). d3d11.c:28265: Test failed: Feature level 0: Got value 0x331 (1.24666207e-002), expected 0x334 (1.25123980e-002). d3d11.c:28265: Test failed: Feature level 0: Got value 0x476 (1.74258035e-002), expected 0x47b (1.75020974e-002). d3d11.c:28265: Test failed: Feature level 0: Got value 0x476 (1.74258035e-002), expected 0x47b (1.75020974e-002). d3d11.c:28265: Test failed: Feature level 0: Got value 0xa411 (6.40894175e-001), expected 0xa47a (6.42496347e-001). d3d11.c:28265: Test failed: Feature level 0: Got value 0xa411 (6.40894175e-001), expected 0xa47a (6.42496347e-001).

1 0

Re: [PATCH 1/3] d3d11/tests: Use winetest_push_context() to print explicit feature levels.
by Marvin Aug. 11, 2022

Aug. 11, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=121054 Your paranoid android. === debian11 (32 bit report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Arabic:Morocco report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit German report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit French report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Hebrew:Israel report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Hindi:India report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Japanese:Japan report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit Chinese:China report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (32 bit WoW report) === d3d11: d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). === debian11 (64 bit WoW report) === d3d11: d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xb000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0xa000: d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0xa000: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9300: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9200: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1567: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1569: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:1572: Test succeeded inside todo block: Feature level 0x9100: Got unexpected hr 0. d3d11.c:16831: Test failed: Feature level 0: Dim 0, Test 15: At layer 0, (0,0,0), expected 0x00c01001, got 0x00000000. d3d11.c:16831: Test failed: Feature level 0: Dim 1, Test 15: At layer 0, (0,0,0), expected 0x00c01001, got 0x00000000. d3d11.c:28482: Test succeeded inside todo block: Feature level 0xb000: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28491: Test succeeded inside todo block: Feature level 0xb000: Got 0xffffffff, expected 0xffffffff at (640, 480, 1), sub-resource 0. d3d11.c:28482: Test failed: Feature level 0xa100: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28482: Test failed: Feature level 0xa000: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28491: Test failed: Feature level 0xa100: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28491: Test failed: Feature level 0xa000: Got 0xffffffff, expected 0xff00ff00 at (639, 479, 0), sub-resource 0. d3d11.c:28428: Test failed: Feature level 0: Got texcoord {8.43750119e-001, 1.56249911e-001}, expected {8.43750000e-001, 1.56250000e-001} at (3, 3), offset 1.25000000e-001. d3d11.c:16831: Test failed: Feature level 0: Dim 2, Test 15: At layer 0, (0,0,0), expected 0x00c01001, got 0x00000000. d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff0000ff at (0, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ffff at (1, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff00ff00 at (2, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffff00 at (3, 0). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff0000 at (0, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffff00ff at (1, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff7f7f7f at (3, 1). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (1, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (2, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 2). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xffffffff at (0, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (2, 3). d3d11.c:9942: Test failed: Feature level 0: Test 60: Got unexpected colour 0xff000000 at (3, 3). d3d11.c:28428: Test failed: Feature level 0: Got texcoord {8.71093690e-001, 1.28906295e-001}, expected {8.71093750e-001, 1.28906250e-001} at (3, 3), offset 1.56250000e-002. d3d11.c:28428: Test failed: Feature level 0: Got texcoord {7.51953065e-001, 2.48046920e-001}, expected {7.51953125e-001, 2.48046875e-001} at (3, 3), offset 4.92187500e-001. d3d11.c:20298: Test failed: Feature level 0: Got {0xfffe0000, 0xfffe0000, 0xfffe0000, 0xfffe0000}, expected {0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0xfffffffe, 0xfffffffe, 0xfffffffe, 0xfffffffe}, expected {0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0x00000000, 0x00000000, 0x00000000, 0x00000000}, expected {0xffffffff, 0xffffffff, 0xffffffff, 0xffffffff} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0xfffffffe, 0xfffffffe, 0xfffffffe, 0xfffffffe}, expected {0x00000000, 0x00000000, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0x80000000, 0x00000000, 0x00000000, 0x00000000}, expected {0x00000000, 0xffffffff, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0x00000000, 0x80000000, 0x00000000, 0x00000000}, expected {0xffffffff, 0x00000000, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0xffffffff, 0x00000001, 0x00000000, 0x00000000}, expected {0x00000000, 0x00000001, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:20298: Test failed: Feature level 0: Got {0x00000001, 0xffffffff, 0x00000000, 0x00000000}, expected {0x00000001, 0x00000000, 0x00000000, 0x00000000} at (0, 0), sub-resource 0. d3d11.c:28245: Test failed: Feature level 0: Got depth 4.99374978e-003, expected 4.99999989e-003. d3d11.c:28245: Test failed: Feature level 0: Got depth 4.99374978e-003, expected 4.99999989e-003. d3d11.c:28245: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28245: Test failed: Feature level 0: Got depth 7.48750009e-003, expected 7.49999983e-003. d3d11.c:28245: Test failed: Feature level 0: Got depth 7.48750009e-003, expected 7.49999983e-003. d3d11.c:28245: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28245: Test failed: Feature level 0: Got depth 1.24749998e-002, expected 1.24999997e-002. d3d11.c:28245: Test failed: Feature level 0: Got depth 1.24749998e-002, expected 1.24999997e-002. d3d11.c:28245: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28245: Test failed: Feature level 0: Got depth 6.40899956e-001, expected 6.42499986e-001. d3d11.c:28245: Test failed: Feature level 0: Got depth 6.40899956e-001, expected 6.42499986e-001. d3d11.c:28245: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28245: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28245: Test failed: Feature level 0: Got depth 2.50997487e-003, expected 2.50999994e-003. d3d11.c:28253: Test failed: Feature level 0: Got value 0x14745 (4.99373721e-003), expected 0x147ae (4.99999570e-003). d3d11.c:28253: Test failed: Feature level 0: Got value 0x14745 (4.99373721e-003), expected 0x147ae (4.99999570e-003). d3d11.c:28253: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28253: Test failed: Feature level 0: Got value 0x1eab3 (7.48747634e-003), expected 0x1eb85 (7.49999331e-003). d3d11.c:28253: Test failed: Feature level 0: Got value 0x1eab3 (7.48747634e-003), expected 0x1eb85 (7.49999331e-003). d3d11.c:28253: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28253: Test failed: Feature level 0: Got value 0x33190 (1.24750147e-002), expected 0x33333 (1.24999890e-002). d3d11.c:28253: Test failed: Feature level 0: Got value 0x33190 (1.24750147e-002), expected 0x33333 (1.24999890e-002). d3d11.c:28253: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28253: Test failed: Feature level 0: Got value 0xa41204 (6.40899956e-001), expected 0xa47ae0 (6.42499983e-001). d3d11.c:28253: Test failed: Feature level 0: Got value 0xa41204 (6.40899956e-001), expected 0xa47ae0 (6.42499983e-001). d3d11.c:28253: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28253: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28253: Test failed: Feature level 0: Got value 0x8528f (3.25097479e-002), expected 0x85293 (3.25099863e-002). d3d11.c:28262: Test failed: Feature level 0: Got value 0x28e (9.97940078e-003), expected 0x290 (1.00099184e-002). d3d11.c:28262: Test failed: Feature level 0: Got value 0x28e (9.97940078e-003), expected 0x290 (1.00099184e-002). d3d11.c:28262: Test failed: Feature level 0: Got value 0x331 (1.24666207e-002), expected 0x334 (1.25123980e-002). d3d11.c:28262: Test failed: Feature level 0: Got value 0x331 (1.24666207e-002), expected 0x334 (1.25123980e-002). d3d11.c:28262: Test failed: Feature level 0: Got value 0x476 (1.74258035e-002), expected 0x47b (1.75020974e-002). d3d11.c:28262: Test failed: Feature level 0: Got value 0x476 (1.74258035e-002), expected 0x47b (1.75020974e-002). d3d11.c:28262: Test failed: Feature level 0: Got value 0xa411 (6.40894175e-001), expected 0xa47a (6.42496347e-001). d3d11.c:28262: Test failed: Feature level 0: Got value 0xa411 (6.40894175e-001), expected 0xa47a (6.42496347e-001).

1 0

Re: [PATCH 1/6] mshtml: Forward Document's Invoke to InvokeEx.
by Marvin Aug. 11, 2022

Aug. 11, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=121042 Your paranoid android. === w10pro64 (64 bit report) === mshtml: htmldoc.c:350: Test failed: expected Exec_SETTITLE htmldoc.c:2859: Test failed: unexpected call Exec_SETTITLE

1 0

WineConf 2022 - Bring out your talks
by Jeremy White Aug. 11, 2022

Aug. 11, 2022

Hey folks, I've just learned that what we've done all these years is an un conference (https://en.wikipedia.org/wiki/Unconference) or a BarCamp (https://en.wikipedia.org/wiki/BarCamp) So we were cool *long* before these other cats starting copying us. However, since we are partnering with X.org on Wine Conf, and they use the slick Indico conference system, we should get with the program. I would really appreciate it if folks could submit talk ideas: https://indico.freedesktop.org/event/2/abstracts/ We have, a non zero number of scheduled presentations already, but think that number may be one. So I would really appreciate it if folks would submit abstracts. Cheers, Jeremy p.s. Other reminders: - We have funds available to sponsor travel. If cost makes you hesitate, please reach out to me privately. - There is a hotel block you can sign up for - New this year, it's nice if you sign to show you are coming: https://indico.freedesktop.org/event/2/registrations/2/.

2 1

Re: [PATCH v2 4/6] mf: Allow resolving topology with missing downstream current type.
by Marvin Aug. 11, 2022

Aug. 11, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=121023 Your paranoid android. === w10pro64_ja (64 bit report) === mf: mf: Timeout

1 0

Re: [PATCH 1/5] comctl32/tests: Add IME tests for edit control.
by Marvin Aug. 11, 2022

Aug. 11, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120932 Your paranoid android. === w10pro64 (testbot log) === WineRunTask.pl:error: The previous 1 run(s) terminated abnormally

1 0

Re: [PATCH v3 1/2] mshtml: Semi-implement non-string primitive data for postMessage.
by Marvin Aug. 10, 2022

Aug. 10, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120888 Your paranoid android. === w10pro64_zh_CN (64 bit report) === mshtml: htmldoc.c:350: Test failed: expected Exec_SETTITLE htmldoc.c:2859: Test failed: unexpected call Exec_SETTITLE

1 0

Re: [PATCH v5 01/10] winmm/tests: Add tests for visibility of video window.
by Marvin Aug. 10, 2022

Aug. 10, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120860 Your paranoid android. === w7u_adm (32 bit report) === winmm: midi.c:988: Test failed: bad message 1e/0 from midiStreamOpen, expect 3c7/0 midi.c:1039: Test failed: bad message 3c7/0 from midiStreamOut, expect 3c9/22f940 midi.c:1048: Test failed: bad message 3c9/22f940 from midiStreamClose, expect 3c8/0 === w7u_adm (testbot log) === WineRunTask.pl:error: The previous 1 run(s) terminated abnormally === w7u_adm (testbot log) === WineRunTask.pl:error: The previous 1 run(s) terminated abnormally

1 0

Re: [PATCH v4 03/13] mmdevapi: Integrate winepulse's additions in unixlib.h
by Marvin Aug. 9, 2022

Aug. 9, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120814 Your paranoid android. === debian11 (32 bit Chinese:China report) === mmdevapi: capture.c:205: Test failed: GCP 16553 past ReleaseBuffer(0) initially 16058

1 0

Re: [PATCH 1/1] d3d11: Validate layout description in d3d_input_layout_create().
by Marvin Aug. 9, 2022

Aug. 9, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120787 Your paranoid android. === w1064 (32 bit report) === d3d11: d3d11.c:5908: Test failed: Got unexpected query result 0x0000000000000000. === debian11 (64 bit WoW report) === d3d11: d3d11.c:1567: Test succeeded inside todo block: d3d11.c:1570: Test marked todo: Format 0x57 - display not supported, feature_level 0x9200, format support 0x200f3f2.

1 0

Re: [PATCH v2 1/2] mshtml: Semi-implement non-string primitive data for postMessage.
by Marvin Aug. 9, 2022

Aug. 9, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120782 Your paranoid android. === w10pro64 (64 bit report) === mshtml: htmldoc.c:350: Test failed: expected Exec_SETTITLE htmldoc.c:2859: Test failed: unexpected call Exec_SETTITLE

1 0

WinRt activable class registration
by Kacper rączy Aug. 9, 2022

Aug. 9, 2022

Hi everyone, First of all, I’m not really familiar with Windows dev environment and tools outside of wine. I’m building custom implementation of some Windows Runtime modules (separate project outside of wine-tree). Similarly to windows.gaming.input in wine, I’ve created classes.idl with `#pragma makedep register`, and using widl to compile it into classes_r.res script file. Then I’m using windres to convert to coff and link it against my dll. Then the runtime classes implemented by dll have to registered. So far I was adding registry entries with DllPath manually in regedit (in HKLM.Software.Microsoft.WindowsRuntime.ActivatableClassId.[CLASS_NAME]) for testing purposes, because I don’t really know how utilize registration script that’s already embedded in dll. So my question is, how do I register Dll for activable winrt classes? Is there a tool for that? Thanks, Kacper Rączy

1 0

Re: [PATCH 2/2] ntdll: Fix leak of mach_host_self port.
by Marvin Aug. 8, 2022

Aug. 8, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120698 Your paranoid android. === debian11 (32 bit WoW report) === ntdll: change.c:277: Test failed: should be ready

1 0

Re: [PATCH v2 1/2] mf: Handle timer time behind clock time in present_clock_schedule_timer().
by Marvin Aug. 8, 2022

Aug. 8, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120690 Your paranoid android. === w7u_el (32 bit report) === mf: mf: Timeout

1 0

[PATCH] srvsvc: Add LanmanServer stub service.
by Dmitry Timoshkov Aug. 8, 2022

Aug. 8, 2022

wine.inf already has an entry for it. Signed-off-by: Dmitry Timoshkov <dmitry(a)baikal.ru> --- configure.ac | 1 + dlls/srvsvc/Makefile.in | 5 +++ dlls/srvsvc/srvsvc.c | 87 +++++++++++++++++++++++++++++++++++++++++ dlls/srvsvc/srvsvc.spec | 1 + loader/wine.inf.in | 4 +- 5 files changed, 96 insertions(+), 2 deletions(-) create mode 100644 dlls/srvsvc/Makefile.in create mode 100644 dlls/srvsvc/srvsvc.c create mode 100644 dlls/srvsvc/srvsvc.spec diff --git a/configure.ac b/configure.ac index dd4abd39e32..bec0513c46d 100644 --- a/configure.ac +++ b/configure.ac @@ -3035,6 +3035,7 @@ WINE_CONFIG_MAKEFILE(dlls/spoolss/tests) WINE_CONFIG_MAKEFILE(dlls/sppc) WINE_CONFIG_MAKEFILE(dlls/srclient) WINE_CONFIG_MAKEFILE(dlls/srvcli) +WINE_CONFIG_MAKEFILE(dlls/srvsvc) WINE_CONFIG_MAKEFILE(dlls/sspicli) WINE_CONFIG_MAKEFILE(dlls/stdole2.tlb) WINE_CONFIG_MAKEFILE(dlls/stdole32.tlb) diff --git a/dlls/srvsvc/Makefile.in b/dlls/srvsvc/Makefile.in new file mode 100644 index 00000000000..f9c68fd12aa --- /dev/null +++ b/dlls/srvsvc/Makefile.in @@ -0,0 +1,5 @@ +MODULE = srvsvc.dll +IMPORTS = advapi32 + +C_SRCS = \ + srvsvc.c diff --git a/dlls/srvsvc/srvsvc.c b/dlls/srvsvc/srvsvc.c new file mode 100644 index 00000000000..3b2b563bc6c --- /dev/null +++ b/dlls/srvsvc/srvsvc.c @@ -0,0 +1,87 @@ +/* + * LanmanServer Service + * + * Copyright 2022 Dmitry Timoshkov + * + * This library is free software; you can redistribute it and/or + * modify it under the terms of the GNU Lesser General Public + * License as published by the Free Software Foundation; either + * version 2.1 of the License, or (at your option) any later version. + * + * This library is distributed in the hope that it will be useful, + * but WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU + * Lesser General Public License for more details. + * + * You should have received a copy of the GNU Lesser General Public + * License along with this library; if not, write to the Free Software + * Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA + */ + +#include <stdarg.h> + +#include "windef.h" +#include "winbase.h" +#include "winsvc.h" +#include "wine/debug.h" + +WINE_DEFAULT_DEBUG_CHANNEL(lanman); + +static SERVICE_STATUS_HANDLE svc_handle; +static HANDLE done_event; + +static void svc_update_status(DWORD state) +{ + SERVICE_STATUS status; + + status.dwServiceType = SERVICE_WIN32; + status.dwControlsAccepted = SERVICE_ACCEPT_STOP | SERVICE_ACCEPT_SHUTDOWN; + status.dwWin32ExitCode = 0; + status.dwServiceSpecificExitCode = 0; + status.dwCheckPoint = 0; + status.dwWaitHint = 0; + status.dwCurrentState = state; + + SetServiceStatus(svc_handle, &status); +} + +static void WINAPI svc_handler(DWORD control) +{ + TRACE("%#lx\n", control); + + switch (control) + { + case SERVICE_CONTROL_STOP: + case SERVICE_CONTROL_SHUTDOWN: + svc_update_status(SERVICE_STOP_PENDING); + SetEvent(done_event); + break; + + default: + svc_update_status(SERVICE_RUNNING); + break; + } +} + +void WINAPI ServiceMain(DWORD argc, LPWSTR *argv) +{ + TRACE("Starting LanmanServer\n"); + + svc_handle = RegisterServiceCtrlHandlerW(L"LanmanServer", svc_handler); + if (!svc_handle) + { + ERR("RegisterServiceCtrlHandler error %ld\n", GetLastError()); + return; + } + + svc_update_status(SERVICE_START_PENDING); + done_event = CreateEventW(NULL, TRUE, FALSE, NULL); + + svc_update_status(SERVICE_RUNNING); + WaitForSingleObject(done_event, INFINITE); + CloseHandle(done_event); + + svc_update_status(SERVICE_STOPPED); + + TRACE("Exiting LanmanServer\n"); +} diff --git a/dlls/srvsvc/srvsvc.spec b/dlls/srvsvc/srvsvc.spec new file mode 100644 index 00000000000..daa88578f7f --- /dev/null +++ b/dlls/srvsvc/srvsvc.spec @@ -0,0 +1 @@ +@ stdcall -private ServiceMain(long ptr) diff --git a/loader/wine.inf.in b/loader/wine.inf.in index e7b435ed0f0..d686e0b4f2f 100644 --- a/loader/wine.inf.in +++ b/loader/wine.inf.in @@ -2396,12 +2396,12 @@ Description="Lanman Server" DisplayName="Lanman Server" ServiceBinary="%11%\svchost.exe -k netsvcs" ServiceType=32 -StartType=4 +StartType=3 ErrorControl=1 [LanmanServerServiceKeys] HKR,Parameters,"ServiceDll",,"%11%\srvsvc.dll" -;; HKLM,%CurrentVersionNT%\SvcHost,"netsvcs",0x00010008,"lanmanserver" +HKLM,%CurrentVersionNT%\SvcHost,"netsvcs",0x00010008,"lanmanserver" [FontCacheService] AddReg=FontCacheServiceKeys -- 2.37.1

1 0

[PATCH] wevtsvc: Remove duplicate dwControlsAccepted initialization.
by Dmitry Timoshkov Aug. 8, 2022

Aug. 8, 2022

dwControlsAccepted is initialized a few lines earlier. Signed-off-by: Dmitry Timoshkov <dmitry(a)baikal.ru> --- dlls/wevtsvc/wevtsvc.c | 1 - 1 file changed, 1 deletion(-) diff --git a/dlls/wevtsvc/wevtsvc.c b/dlls/wevtsvc/wevtsvc.c index 2e303045740..78c68bac69b 100644 --- a/dlls/wevtsvc/wevtsvc.c +++ b/dlls/wevtsvc/wevtsvc.c @@ -40,7 +40,6 @@ static void eventlog_update_status(DWORD state) status.dwServiceSpecificExitCode = 0; status.dwCheckPoint = 0; status.dwWaitHint = 0; - status.dwControlsAccepted = 0; status.dwCurrentState = state; SetServiceStatus(svc_handle, &status); -- 2.37.1

1 0

[PATCH] schedsvc: Remove duplicate dwControlsAccepted initialization.
by Dmitry Timoshkov Aug. 8, 2022

Aug. 8, 2022

dwControlsAccepted is initialized a few lines earlier. Signed-off-by: Dmitry Timoshkov <dmitry(a)baikal.ru> --- dlls/schedsvc/svc_main.c | 1 - 1 file changed, 1 deletion(-) diff --git a/dlls/schedsvc/svc_main.c b/dlls/schedsvc/svc_main.c index 7681a220592..2250854e953 100644 --- a/dlls/schedsvc/svc_main.c +++ b/dlls/schedsvc/svc_main.c @@ -281,7 +281,6 @@ static void schedsvc_update_status(DWORD state) status.dwServiceSpecificExitCode = 0; status.dwCheckPoint = 0; status.dwWaitHint = 0; - status.dwControlsAccepted = 0; status.dwCurrentState = state; SetServiceStatus(schedsvc_handle, &status); -- 2.37.1

1 0

Re: [PATCH v8 2/5] winegstreamer: Implement IWMOutputMediaProps_SetMediaType.
by Marvin Aug. 8, 2022

Aug. 8, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120665 Your paranoid android. === debian11 (32 bit report) === wmvcore: wmvcore.c:1318: Test failed: Stream 1: Got hr 0xc00d0bc2. wmvcore.c:2590: Test failed: Output 1: Got hr 0xc00d0bc2. === debian11 (32 bit Arabic:Morocco report) === wmvcore: wmvcore.c:1318: Test failed: Stream 1: Got hr 0xc00d0bc2. wmvcore.c:2590: Test failed: Output 1: Got hr 0xc00d0bc2. === debian11 (32 bit German report) === wmvcore: wmvcore.c:1318: Test failed: Stream 1: Got hr 0xc00d0bc2. wmvcore.c:2590: Test failed: Output 1: Got hr 0xc00d0bc2. === debian11 (32 bit French report) === wmvcore: wmvcore.c:1318: Test failed: Stream 1: Got hr 0xc00d0bc2. wmvcore.c:2590: Test failed: Output 1: Got hr 0xc00d0bc2. === debian11 (32 bit Hebrew:Israel report) === wmvcore: wmvcore.c:1318: Test failed: Stream 1: Got hr 0xc00d0bc2. wmvcore.c:2590: Test failed: Output 1: Got hr 0xc00d0bc2. === debian11 (32 bit Hindi:India report) === wmvcore: wmvcore.c:1318: Test failed: Stream 1: Got hr 0xc00d0bc2. wmvcore.c:2590: Test failed: Output 1: Got hr 0xc00d0bc2. === debian11 (32 bit Japanese:Japan report) === wmvcore: wmvcore.c:1318: Test failed: Stream 1: Got hr 0xc00d0bc2. wmvcore.c:2590: Test failed: Output 1: Got hr 0xc00d0bc2. === debian11 (32 bit Chinese:China report) === wmvcore: wmvcore.c:1318: Test failed: Stream 1: Got hr 0xc00d0bc2. wmvcore.c:2590: Test failed: Output 1: Got hr 0xc00d0bc2. === debian11 (32 bit WoW report) === wmvcore: wmvcore.c:1318: Test failed: Stream 1: Got hr 0xc00d0bc2. wmvcore.c:2590: Test failed: Output 1: Got hr 0xc00d0bc2. === debian11 (64 bit WoW report) === wmvcore: wmvcore.c:1318: Test failed: Stream 1: Got hr 0xc00d0bc2. wmvcore.c:2590: Test failed: Output 1: Got hr 0xc00d0bc2.

1 0

Wine-Contribution
by Alan Aug. 7, 2022

Aug. 7, 2022

Hello There i need some help regarding to start applying patches to wine and start contributing the problem is I don't know where to start? I went to the wine website and started reading. I didn't get much useful stuff but There was some good documentation about the codebase and the structure of it , but if I want to start applying patches to wine, where should I start besides the website ? Should I start reading the codebase ? If so, where should I start reading the codebase from ? or should I just go and try to patch the bugs that's on the forks issue section? Thanks For your Time Alan

2 1

Re: [PATCH v4 09/10] mciqtz32: Hide the default video window when switching to another one.
by Marvin Aug. 6, 2022

Aug. 6, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120640 Your paranoid android. === w10pro64_en_AE_u8 (64 bit report) === winmm: mci.c:1291: Test failed: sysinfo quantity open expected 0 after auto-close, got: 1

1 0

Wine web-based translation using Weblate
by Óvári Aug. 6, 2022

Aug. 6, 2022

Hello, Can Wine please be available for translation using a browser (eg Firefox) at Weblate? https://hosted.weblate.org/ Thank you On Tue, 19 Jul 2022: [...] > I would have to reassess to be exact but the requirement that caused > issues with most of the systems I investigated was that wine requires > all patches, even translations, to be clearly accredited to a user by > full real name and email. I remember that being the main issue too. But their attribution FAQ says every change is committed under the translators name: https://docs.weblate.org/fr/latest/faq.html#how-does-weblate-credit-transla… | Every change made in Weblate is committed into VCS under the | translators name. This way every single change has proper authorship, | and you can track it down using the standard VCS tools you use for | code. It sounds like this would fulfil Wine's requirement. Also this should probably be posted on wine-devel since it concerns the whole community and would broaden the pool of people who can move forward on this.

1 0

Re: [PATCH v7 1/5] wmvcore/tests: Add some IWMOutputMediaProps_SetMediaType tests.
by Marvin Aug. 5, 2022

Aug. 5, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120582 Your paranoid android. === debian11 (32 bit report) === wmvcore: wmvcore.c:1345: Test succeeded inside todo block: Stream 0: Got hr 0. wmvcore.c:1324: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:1332: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:2631: Test succeeded inside todo block: Output 0: Got hr 0. wmvcore.c:2610: Test succeeded inside todo block: Output 1: Got hr 0. wmvcore.c:2618: Test succeeded inside todo block: Output 1: Got hr 0. === debian11 (32 bit Arabic:Morocco report) === wmvcore: wmvcore.c:1345: Test succeeded inside todo block: Stream 0: Got hr 0. wmvcore.c:1324: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:1332: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:2631: Test succeeded inside todo block: Output 0: Got hr 0. wmvcore.c:2610: Test succeeded inside todo block: Output 1: Got hr 0. wmvcore.c:2618: Test succeeded inside todo block: Output 1: Got hr 0. === debian11 (32 bit German report) === wmvcore: wmvcore.c:1345: Test succeeded inside todo block: Stream 0: Got hr 0. wmvcore.c:1324: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:1332: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:2631: Test succeeded inside todo block: Output 0: Got hr 0. wmvcore.c:2610: Test succeeded inside todo block: Output 1: Got hr 0. wmvcore.c:2618: Test succeeded inside todo block: Output 1: Got hr 0. === debian11 (32 bit French report) === wmvcore: wmvcore.c:1345: Test succeeded inside todo block: Stream 0: Got hr 0. wmvcore.c:1324: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:1332: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:2631: Test succeeded inside todo block: Output 0: Got hr 0. wmvcore.c:2610: Test succeeded inside todo block: Output 1: Got hr 0. wmvcore.c:2618: Test succeeded inside todo block: Output 1: Got hr 0. === debian11 (32 bit Hebrew:Israel report) === wmvcore: wmvcore.c:1345: Test succeeded inside todo block: Stream 0: Got hr 0. wmvcore.c:1324: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:1332: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:2631: Test succeeded inside todo block: Output 0: Got hr 0. wmvcore.c:2610: Test succeeded inside todo block: Output 1: Got hr 0. wmvcore.c:2618: Test succeeded inside todo block: Output 1: Got hr 0. === debian11 (32 bit Hindi:India report) === wmvcore: wmvcore.c:1345: Test succeeded inside todo block: Stream 0: Got hr 0. wmvcore.c:1324: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:1332: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:2631: Test succeeded inside todo block: Output 0: Got hr 0. wmvcore.c:2610: Test succeeded inside todo block: Output 1: Got hr 0. wmvcore.c:2618: Test succeeded inside todo block: Output 1: Got hr 0. === debian11 (32 bit Japanese:Japan report) === wmvcore: wmvcore.c:1345: Test succeeded inside todo block: Stream 0: Got hr 0. wmvcore.c:1324: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:1332: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:2631: Test succeeded inside todo block: Output 0: Got hr 0. wmvcore.c:2610: Test succeeded inside todo block: Output 1: Got hr 0. wmvcore.c:2618: Test succeeded inside todo block: Output 1: Got hr 0. === debian11 (32 bit Chinese:China report) === wmvcore: wmvcore.c:1345: Test succeeded inside todo block: Stream 0: Got hr 0. wmvcore.c:1324: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:1332: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:2631: Test succeeded inside todo block: Output 0: Got hr 0. wmvcore.c:2610: Test succeeded inside todo block: Output 1: Got hr 0. wmvcore.c:2618: Test succeeded inside todo block: Output 1: Got hr 0. === debian11 (32 bit WoW report) === wmvcore: wmvcore.c:1345: Test succeeded inside todo block: Stream 0: Got hr 0. wmvcore.c:1324: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:1332: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:2631: Test succeeded inside todo block: Output 0: Got hr 0. wmvcore.c:2610: Test succeeded inside todo block: Output 1: Got hr 0. wmvcore.c:2618: Test succeeded inside todo block: Output 1: Got hr 0. === debian11 (64 bit WoW report) === wmvcore: wmvcore.c:1345: Test succeeded inside todo block: Stream 0: Got hr 0. wmvcore.c:1324: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:1332: Test succeeded inside todo block: Stream 1: Got hr 0. wmvcore.c:2631: Test succeeded inside todo block: Output 0: Got hr 0. wmvcore.c:2610: Test succeeded inside todo block: Output 1: Got hr 0. wmvcore.c:2618: Test succeeded inside todo block: Output 1: Got hr 0.

1 0

Re: [PATCH vkd3d v3 13/17] vkd3d-shader/hlsl: Replace register offsets with index paths in resource loads initialization.
by Francisco Casas Aug. 4, 2022

Aug. 4, 2022

Ah, I finally see, the hlsl_src_from_node(&deref->offset, other->offset.node); indeed is a noop. I will fix it. On 25-07-22 04:11, Giovanni Mascellani wrote: > Hi, > > Il 22/07/22 20:36, Francisco Casas ha scritto: >>>> diff --git a/libs/vkd3d-shader/hlsl.c b/libs/vkd3d-shader/hlsl.c >>>> index 2d5fe40a..a4d594b7 100644 >>>> --- a/libs/vkd3d-shader/hlsl.c >>>> +++ b/libs/vkd3d-shader/hlsl.c >>>> @@ -862,6 +862,28 @@ static bool type_is_single_reg(const struct >>>> hlsl_type *type) >>>> return type->type == HLSL_CLASS_SCALAR || type->type == >>>> HLSL_CLASS_VECTOR; >>>> } >>>> +static bool deref_copy(struct hlsl_ctx *ctx, struct hlsl_deref >>>> *deref, struct hlsl_deref *other) >>>> +{ >>>> + unsigned int i; >>>> + >>>> + memset(deref, 0, sizeof(*deref)); >>>> + >>>> + if (!other) >>>> + return true; >>>> + >>>> + assert(!other->offset.node); >>>> + >>>> + if (!init_deref(ctx, deref, other->var, other->path_len)) >>>> + return false; >>>> + >>>> + for (i = 0; i < deref->path_len; ++i) >>>> + hlsl_src_from_node(&deref->path[i], other->path[i].node); >>>> + >>>> + hlsl_src_from_node(&deref->offset, other->offset.node); >>> >>> You just asserted that other->offset.node is NULL and *deref was >>> initialized to zero, so that seems to be a noop, doesn't it? >>> >> >> Hmm, sorry, I am not sure I understand. >> Initializing *deref to zero shouldn't affect >> >> assert(!other->offset.node); >> >> The idea of this assertion is to ensure that the "other" deref is in >> the index path format instead of the register offset format. > > My point is that, given that you just asserted that other->offset.node > is NULL, the effect of "hlsl_src_from_node(&deref->offset, > other->offset.node)" would be to set deref->offset.node to NULL, but > that's already ensured by the memset(). Or maybe I am getting confused > on something trivial? > > Giovanni.

1 0

[PATCH vkd3d v3 05/17] vkd3d-shader/hlsl: Introduce add_load_component().
by Francisco Casas Aug. 4, 2022

Aug. 4, 2022

Signed-off-by: Francisco Casas <fcasas(a)codeweavers.com> Signed-off-by: Giovanni Mascellani <gmascellani(a)codeweavers.com> --- v3: * Using hlsl_get_string_buffer() and hlsl_release_string_buffer(). Signed-off-by: Francisco Casas <fcasas(a)codeweavers.com> --- libs/vkd3d-shader/hlsl.y | 99 +++++++++++++++++++++++++++------------- 1 file changed, 68 insertions(+), 31 deletions(-) diff --git a/libs/vkd3d-shader/hlsl.y b/libs/vkd3d-shader/hlsl.y index bfafd981..3b3d3582 100644 --- a/libs/vkd3d-shader/hlsl.y +++ b/libs/vkd3d-shader/hlsl.y @@ -272,8 +272,8 @@ static bool implicit_compatible_data_types(struct hlsl_type *t1, struct hlsl_typ return false; } -static struct hlsl_ir_load *add_load(struct hlsl_ctx *ctx, struct list *instrs, struct hlsl_ir_node *var_node, - struct hlsl_ir_node *offset, struct hlsl_type *data_type, const struct vkd3d_shader_location loc); +static struct hlsl_ir_load *add_load_component(struct hlsl_ctx *ctx, struct list *instrs, struct hlsl_ir_node *var_node, + unsigned int comp, const struct vkd3d_shader_location *loc); static struct hlsl_ir_node *add_cast(struct hlsl_ctx *ctx, struct list *instrs, struct hlsl_ir_node *node, struct hlsl_type *dst_type, const struct vkd3d_shader_location *loc) @@ -311,8 +311,8 @@ static struct hlsl_ir_node *add_cast(struct hlsl_ctx *ctx, struct list *instrs, for (dst_idx = 0; dst_idx < dst_type->dimx * dst_type->dimy; ++dst_idx) { - struct hlsl_type *src_scalar_type, *dst_scalar_type; - unsigned int src_idx, src_offset, dst_offset; + struct hlsl_type *dst_scalar_type; + unsigned int src_idx, dst_offset; struct hlsl_ir_store *store; struct hlsl_ir_constant *c; @@ -335,13 +335,8 @@ static struct hlsl_ir_node *add_cast(struct hlsl_ctx *ctx, struct list *instrs, } dst_offset = hlsl_compute_component_offset(ctx, dst_type, dst_idx, &dst_scalar_type); - src_offset = hlsl_compute_component_offset(ctx, src_type, src_idx, &src_scalar_type); - - if (!(c = hlsl_new_uint_constant(ctx, src_offset, loc))) - return NULL; - list_add_tail(instrs, &c->node.entry); - if (!(load = add_load(ctx, instrs, node, &c->node, src_scalar_type, *loc))) + if (!(load = add_load_component(ctx, instrs, node, src_idx, loc))) return NULL; if (!(cast = hlsl_new_cast(ctx, &load->node, dst_scalar_type, loc))) @@ -668,6 +663,63 @@ static struct hlsl_ir_load *add_load(struct hlsl_ctx *ctx, struct list *instrs, return load; } +static struct hlsl_ir_load *add_load_component(struct hlsl_ctx *ctx, struct list *instrs, struct hlsl_ir_node *var_node, + unsigned int comp, const struct vkd3d_shader_location *loc) +{ + struct hlsl_type *comp_type; + struct hlsl_ir_node *offset; + struct hlsl_ir_constant *c; + struct hlsl_ir_load *load; + unsigned int comp_offset; + struct hlsl_ir_var *var; + + comp_offset = hlsl_compute_component_offset(ctx, var_node->data_type, comp, &comp_type); + + if (!(c = hlsl_new_uint_constant(ctx, comp_offset, loc))) + return NULL; + list_add_tail(instrs, &c->node.entry); + + offset = &c->node; + + if (var_node->type == HLSL_IR_LOAD) + { + const struct hlsl_deref *src = &hlsl_ir_load(var_node)->src; + struct hlsl_ir_node *add; + + var = src->var; + if (src->offset.node) + { + if (!(add = hlsl_new_binary_expr(ctx, HLSL_OP2_ADD, src->offset.node, &c->node))) + return NULL; + list_add_tail(instrs, &add->entry); + offset = add; + } + } + else + { + struct vkd3d_string_buffer *name; + struct hlsl_ir_store *store; + + if (!(name = hlsl_get_string_buffer(ctx))) + return NULL; + vkd3d_string_buffer_printf(name, "<deref-%p>", var_node); + var = hlsl_new_synthetic_var(ctx, name->buffer, var_node->data_type, var_node->loc); + hlsl_release_string_buffer(ctx, name); + if (!var) + return NULL; + + if (!(store = hlsl_new_simple_store(ctx, var, var_node))) + return NULL; + list_add_tail(instrs, &store->node.entry); + } + + if (!(load = hlsl_new_load(ctx, var, offset, comp_type, *loc))) + return NULL; + list_add_tail(instrs, &load->node.entry); + + return load; +} + static bool add_record_load(struct hlsl_ctx *ctx, struct list *instrs, struct hlsl_ir_node *record, unsigned int idx, const struct vkd3d_shader_location loc) { @@ -1766,22 +1818,17 @@ static void initialize_var_components(struct hlsl_ctx *ctx, struct list *instrs, for (k = 0; k < src_comp_count; ++k) { - struct hlsl_type *dst_comp_type, *src_comp_type; - unsigned int dst_reg_offset, src_reg_offset; + struct hlsl_type *dst_comp_type; + unsigned int dst_reg_offset; struct hlsl_ir_store *store; struct hlsl_ir_constant *c; struct hlsl_ir_load *load; struct hlsl_ir_node *conv; - dst_reg_offset = hlsl_compute_component_offset(ctx, dst->data_type, *store_index, &dst_comp_type); - src_reg_offset = hlsl_compute_component_offset(ctx, src->data_type, k, &src_comp_type); - - if (!(c = hlsl_new_uint_constant(ctx, src_reg_offset, &src->loc))) + if (!(load = add_load_component(ctx, instrs, src, k, &src->loc))) return; - list_add_tail(instrs, &c->node.entry); - if (!(load = add_load(ctx, instrs, src, &c->node, src_comp_type, src->loc))) - return; + dst_reg_offset = hlsl_compute_component_offset(ctx, dst->data_type, *store_index, &dst_comp_type); if (!(conv = add_implicit_conversion(ctx, instrs, &load->node, dst_comp_type, &src->loc))) return; @@ -2218,20 +2265,10 @@ static bool intrinsic_mul(struct hlsl_ctx *ctx, struct hlsl_ir_load *value1, *value2; struct hlsl_ir_node *mul; - offset = hlsl_compute_component_offset(ctx, cast_type1, j * cast_type1->dimx + k, &scalar_type); - if (!(c = hlsl_new_uint_constant(ctx, offset, loc))) - return false; - list_add_tail(params->instrs, &c->node.entry); - - if (!(value1 = add_load(ctx, params->instrs, cast1, &c->node, scalar_type, *loc))) - return false; - - offset = hlsl_compute_component_offset(ctx, cast_type2, k * cast_type2->dimx + i, &scalar_type); - if (!(c = hlsl_new_uint_constant(ctx, offset, loc))) + if (!(value1 = add_load_component(ctx, params->instrs, cast1, j * cast1->data_type->dimx + k, loc))) return false; - list_add_tail(params->instrs, &c->node.entry); - if (!(value2 = add_load(ctx, params->instrs, cast2, &c->node, scalar_type, *loc))) + if (!(value2 = add_load_component(ctx, params->instrs, cast2, k * cast2->data_type->dimx + i, loc))) return false; if (!(mul = add_binary_arithmetic_expr(ctx, params->instrs, HLSL_OP2_MUL, &value1->node, &value2->node, loc))) -- 2.34.1

5 31

Re: [PATCH v8 2/2] win32u/window: Ignore changing WS_EX_TOPMOST for message-only windows.
by Marvin Aug. 4, 2022

Aug. 4, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120511 Your paranoid android. === w10pro64 (32 bit report) === user32: win.c:10984: Test failed: pos = 014a015e

1 0

Re: [PATCH v8 1/2] user32/tests: Check that message-only windows ignore WS_EX_TOPMOST.
by Marvin Aug. 4, 2022

Aug. 4, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120510 Your paranoid android. === w10pro64_en_AE_u8 (64 bit report) === user32: win.c:4592: Test failed: hwnd 00000000001F0326/00000000001F0326 message 0200 win.c:4595: Test failed: hwnd 00000000001F0326/00000000001F0326 message 0201 === w10pro64_ar (64 bit report) === user32: win.c:4641: Test failed: hwnd 00000000000B02D2/00000000000B02D2 message 0200 win.c:4643: Test failed: wparam 0 win.c:4654: Test failed: hwnd 00000000000B02D2/00000000000B02D2 message 0203 win.c:4658: Test failed: message 0202 available

1 0

[PATCH vkd3d 01/17] vkd3d-shader/hlsl: Store the struct fields as an array.
by Francisco Casas Aug. 3, 2022

Aug. 3, 2022

From: Zebediah Figura <zfigura(a)codeweavers.com> Signed-off-by: Francisco Casas <fcasas(a)codeweavers.com> --- v2: * No changes. --- libs/vkd3d-shader/hlsl.c | 123 +++++++++++++++---------------- libs/vkd3d-shader/hlsl.h | 10 ++- libs/vkd3d-shader/hlsl.y | 99 ++++++++++++++----------- libs/vkd3d-shader/hlsl_codegen.c | 18 +++-- libs/vkd3d-shader/hlsl_sm1.c | 13 +++- libs/vkd3d-shader/hlsl_sm4.c | 13 +++- 6 files changed, 150 insertions(+), 126 deletions(-) diff --git a/libs/vkd3d-shader/hlsl.c b/libs/vkd3d-shader/hlsl.c index 7239b183..b349eb15 100644 --- a/libs/vkd3d-shader/hlsl.c +++ b/libs/vkd3d-shader/hlsl.c @@ -175,13 +175,14 @@ static void hlsl_type_calculate_reg_size(struct hlsl_ctx *ctx, struct hlsl_type case HLSL_CLASS_STRUCT: { - struct hlsl_struct_field *field; + unsigned int i; type->dimx = 0; type->reg_size = 0; - LIST_FOR_EACH_ENTRY(field, type->e.elements, struct hlsl_struct_field, entry) + for (i = 0; i < type->e.record.field_count; ++i) { + struct hlsl_struct_field *field = &type->e.record.fields[i]; unsigned int field_size = field->type->reg_size; assert(field_size); @@ -282,10 +283,12 @@ unsigned int hlsl_compute_component_offset(struct hlsl_ctx *ctx, struct hlsl_typ case HLSL_CLASS_STRUCT: { struct hlsl_struct_field *field; + unsigned int elem_comp_count, i; - LIST_FOR_EACH_ENTRY(field, type->e.elements, struct hlsl_struct_field, entry) + for (i = 0; i < type->e.record.field_count; ++i) { - unsigned int elem_comp_count = hlsl_type_component_count(field->type); + field = &type->e.record.fields[i]; + elem_comp_count = hlsl_type_component_count(field->type); if (idx < elem_comp_count) { @@ -331,7 +334,8 @@ struct hlsl_type *hlsl_new_array_type(struct hlsl_ctx *ctx, struct hlsl_type *ba return type; } -struct hlsl_type *hlsl_new_struct_type(struct hlsl_ctx *ctx, const char *name, struct list *fields) +struct hlsl_type *hlsl_new_struct_type(struct hlsl_ctx *ctx, const char *name, + struct hlsl_struct_field *fields, size_t field_count) { struct hlsl_type *type; @@ -341,7 +345,8 @@ struct hlsl_type *hlsl_new_struct_type(struct hlsl_ctx *ctx, const char *name, s type->base_type = HLSL_TYPE_VOID; type->name = name; type->dimy = 1; - type->e.elements = fields; + type->e.record.fields = fields; + type->e.record.field_count = field_count; hlsl_type_calculate_reg_size(ctx, type); list_add_tail(&ctx->types, &type->entry); @@ -401,8 +406,7 @@ struct hlsl_ir_function_decl *hlsl_get_func_decl(struct hlsl_ctx *ctx, const cha unsigned int hlsl_type_component_count(struct hlsl_type *type) { - struct hlsl_struct_field *field; - unsigned int count = 0; + unsigned int count = 0, i; if (type->type <= HLSL_CLASS_LAST_NUMERIC) { @@ -418,10 +422,8 @@ unsigned int hlsl_type_component_count(struct hlsl_type *type) return 0; } - LIST_FOR_EACH_ENTRY(field, type->e.elements, struct hlsl_struct_field, entry) - { - count += hlsl_type_component_count(field->type); - } + for (i = 0; i < type->e.record.field_count; ++i) + count += hlsl_type_component_count(type->e.record.fields[i].type); return count; } @@ -451,24 +453,22 @@ bool hlsl_types_are_equal(const struct hlsl_type *t1, const struct hlsl_type *t2 return false; if (t1->type == HLSL_CLASS_STRUCT) { - struct list *t1cur, *t2cur; - struct hlsl_struct_field *t1field, *t2field; + size_t i; + + if (t1->e.record.field_count != t2->e.record.field_count) + return false; - t1cur = list_head(t1->e.elements); - t2cur = list_head(t2->e.elements); - while (t1cur && t2cur) + for (i = 0; i < t1->e.record.field_count; ++i) { - t1field = LIST_ENTRY(t1cur, struct hlsl_struct_field, entry); - t2field = LIST_ENTRY(t2cur, struct hlsl_struct_field, entry); - if (!hlsl_types_are_equal(t1field->type, t2field->type)) + const struct hlsl_struct_field *field1 = &t1->e.record.fields[i]; + const struct hlsl_struct_field *field2 = &t2->e.record.fields[i]; + + if (!hlsl_types_are_equal(field1->type, field2->type)) return false; - if (strcmp(t1field->name, t2field->name)) + + if (strcmp(field1->name, field2->name)) return false; - t1cur = list_next(t1->e.elements, t1cur); - t2cur = list_next(t2->e.elements, t2cur); } - if (t1cur != t2cur) - return false; } if (t1->type == HLSL_CLASS_ARRAY) return t1->e.array.elements_count == t2->e.array.elements_count @@ -480,7 +480,6 @@ bool hlsl_types_are_equal(const struct hlsl_type *t1, const struct hlsl_type *t2 struct hlsl_type *hlsl_type_clone(struct hlsl_ctx *ctx, struct hlsl_type *old, unsigned int default_majority, unsigned int modifiers) { - struct hlsl_struct_field *old_field, *field; struct hlsl_type *type; if (!(type = hlsl_alloc(ctx, sizeof(*type)))) @@ -512,37 +511,30 @@ struct hlsl_type *hlsl_type_clone(struct hlsl_ctx *ctx, struct hlsl_type *old, case HLSL_CLASS_STRUCT: { - if (!(type->e.elements = hlsl_alloc(ctx, sizeof(*type->e.elements)))) + size_t field_count = old->e.record.field_count, i; + + type->e.record.field_count = field_count; + + if (!(type->e.record.fields = hlsl_alloc(ctx, field_count * sizeof(*type->e.record.fields)))) { vkd3d_free((void *)type->name); vkd3d_free(type); return NULL; } - list_init(type->e.elements); - LIST_FOR_EACH_ENTRY(old_field, old->e.elements, struct hlsl_struct_field, entry) + + for (i = 0; i < field_count; ++i) { - if (!(field = hlsl_alloc(ctx, sizeof(*field)))) - { - LIST_FOR_EACH_ENTRY_SAFE(field, old_field, type->e.elements, struct hlsl_struct_field, entry) - { - vkd3d_free((void *)field->semantic.name); - vkd3d_free((void *)field->name); - vkd3d_free(field); - } - vkd3d_free(type->e.elements); - vkd3d_free((void *)type->name); - vkd3d_free(type); - return NULL; - } - field->loc = old_field->loc; - field->type = hlsl_type_clone(ctx, old_field->type, default_majority, modifiers); - field->name = hlsl_strdup(ctx, old_field->name); - if (old_field->semantic.name) + const struct hlsl_struct_field *src_field = &old->e.record.fields[i]; + struct hlsl_struct_field *dst_field = &type->e.record.fields[i]; + + dst_field->loc = src_field->loc; + dst_field->type = hlsl_type_clone(ctx, src_field->type, default_majority, modifiers); + dst_field->name = hlsl_strdup(ctx, src_field->name); + if (src_field->semantic.name) { - field->semantic.name = hlsl_strdup(ctx, old_field->semantic.name); - field->semantic.index = old_field->semantic.index; + dst_field->semantic.name = hlsl_strdup(ctx, src_field->semantic.name); + dst_field->semantic.index = src_field->semantic.index; } - list_add_tail(type->e.elements, &field->entry); } break; } @@ -911,24 +903,22 @@ static int compare_param_hlsl_types(const struct hlsl_type *t1, const struct hls return r; if (t1->type == HLSL_CLASS_STRUCT) { - struct list *t1cur, *t2cur; - struct hlsl_struct_field *t1field, *t2field; + size_t i; - t1cur = list_head(t1->e.elements); - t2cur = list_head(t2->e.elements); - while (t1cur && t2cur) + if (t1->e.record.field_count != t2->e.record.field_count) + return t1->e.record.field_count - t2->e.record.field_count; + + for (i = 0; i < t1->e.record.field_count; ++i) { - t1field = LIST_ENTRY(t1cur, struct hlsl_struct_field, entry); - t2field = LIST_ENTRY(t2cur, struct hlsl_struct_field, entry); - if ((r = compare_param_hlsl_types(t1field->type, t2field->type))) + const struct hlsl_struct_field *field1 = &t1->e.record.fields[i]; + const struct hlsl_struct_field *field2 = &t2->e.record.fields[i]; + + if ((r = compare_param_hlsl_types(field1->type, field2->type))) return r; - if ((r = strcmp(t1field->name, t2field->name))) + + if ((r = strcmp(field1->name, field2->name))) return r; - t1cur = list_next(t1->e.elements, t1cur); - t2cur = list_next(t2->e.elements, t2cur); } - if (t1cur != t2cur) - return t1cur ? 1 : -1; return 0; } if (t1->type == HLSL_CLASS_ARRAY) @@ -1519,17 +1509,20 @@ void hlsl_replace_node(struct hlsl_ir_node *old, struct hlsl_ir_node *new) void hlsl_free_type(struct hlsl_type *type) { - struct hlsl_struct_field *field, *next_field; + struct hlsl_struct_field *field; + size_t i; vkd3d_free((void *)type->name); if (type->type == HLSL_CLASS_STRUCT) { - LIST_FOR_EACH_ENTRY_SAFE(field, next_field, type->e.elements, struct hlsl_struct_field, entry) + for (i = 0; i < type->e.record.field_count; ++i) { + field = &type->e.record.fields[i]; + vkd3d_free((void *)field->name); vkd3d_free((void *)field->semantic.name); - vkd3d_free(field); } + vkd3d_free((void *)type->e.record.fields); } vkd3d_free(type); } diff --git a/libs/vkd3d-shader/hlsl.h b/libs/vkd3d-shader/hlsl.h index 3c1dd08d..ce1f69df 100644 --- a/libs/vkd3d-shader/hlsl.h +++ b/libs/vkd3d-shader/hlsl.h @@ -126,7 +126,11 @@ struct hlsl_type unsigned int dimy; union { - struct list *elements; + struct + { + struct hlsl_struct_field *fields; + size_t field_count; + } record; struct { struct hlsl_type *type; @@ -147,7 +151,6 @@ struct hlsl_semantic struct hlsl_struct_field { - struct list entry; struct vkd3d_shader_location loc; struct hlsl_type *type; const char *name; @@ -752,7 +755,8 @@ struct hlsl_ir_resource_load *hlsl_new_resource_load(struct hlsl_ctx *ctx, struc struct hlsl_ir_store *hlsl_new_simple_store(struct hlsl_ctx *ctx, struct hlsl_ir_var *lhs, struct hlsl_ir_node *rhs); struct hlsl_ir_store *hlsl_new_store(struct hlsl_ctx *ctx, struct hlsl_ir_var *var, struct hlsl_ir_node *offset, struct hlsl_ir_node *rhs, unsigned int writemask, struct vkd3d_shader_location loc); -struct hlsl_type *hlsl_new_struct_type(struct hlsl_ctx *ctx, const char *name, struct list *fields); +struct hlsl_type *hlsl_new_struct_type(struct hlsl_ctx *ctx, const char *name, + struct hlsl_struct_field *fields, size_t field_count); struct hlsl_ir_swizzle *hlsl_new_swizzle(struct hlsl_ctx *ctx, DWORD s, unsigned int components, struct hlsl_ir_node *val, const struct vkd3d_shader_location *loc); struct hlsl_ir_var *hlsl_new_synthetic_var(struct hlsl_ctx *ctx, const char *name, struct hlsl_type *type, diff --git a/libs/vkd3d-shader/hlsl.y b/libs/vkd3d-shader/hlsl.y index 09a01c6d..f293b82e 100644 --- a/libs/vkd3d-shader/hlsl.y +++ b/libs/vkd3d-shader/hlsl.y @@ -28,6 +28,12 @@ #define HLSL_YYLTYPE struct vkd3d_shader_location +struct parse_fields +{ + struct hlsl_struct_field *fields; + size_t count, capacity; +}; + struct parse_parameter { struct hlsl_type *type; @@ -799,14 +805,15 @@ static bool add_array_load(struct hlsl_ctx *ctx, struct list *instrs, struct hls return !!add_load(ctx, instrs, array, index, data_type, loc); } -static struct hlsl_struct_field *get_struct_field(struct list *fields, const char *name) +static const struct hlsl_struct_field *get_struct_field(const struct hlsl_struct_field *fields, + size_t count, const char *name) { - struct hlsl_struct_field *f; + size_t i; - LIST_FOR_EACH_ENTRY(f, fields, struct hlsl_struct_field, entry) + for (i = 0; i < count; ++i) { - if (!strcmp(f->name, name)) - return f; + if (!strcmp(fields[i].name, name)) + return &fields[i]; } return NULL; } @@ -857,31 +864,28 @@ static void free_parse_variable_def(struct parse_variable_def *v) vkd3d_free(v); } -static struct list *gen_struct_fields(struct hlsl_ctx *ctx, - struct hlsl_type *type, unsigned int modifiers, struct list *fields) +static bool gen_struct_fields(struct hlsl_ctx *ctx, struct parse_fields *fields, + struct hlsl_type *type, unsigned int modifiers, struct list *defs) { struct parse_variable_def *v, *v_next; - struct hlsl_struct_field *field; - struct list *list; + size_t i = 0; if (type->type == HLSL_CLASS_MATRIX) assert(type->modifiers & HLSL_MODIFIERS_MAJORITY_MASK); - if (!(list = make_empty_list(ctx))) - return NULL; - LIST_FOR_EACH_ENTRY_SAFE(v, v_next, fields, struct parse_variable_def, entry) - { - unsigned int i; + memset(fields, 0, sizeof(*fields)); + fields->count = list_count(defs); + if (!hlsl_array_reserve(ctx, (void **)&fields->fields, &fields->capacity, fields->count, sizeof(*fields->fields))) + return false; - if (!(field = hlsl_alloc(ctx, sizeof(*field)))) - { - free_parse_variable_def(v); - continue; - } + LIST_FOR_EACH_ENTRY_SAFE(v, v_next, defs, struct parse_variable_def, entry) + { + struct hlsl_struct_field *field = &fields->fields[i++]; + unsigned int j; field->type = type; - for (i = 0; i < v->arrays.count; ++i) - field->type = hlsl_new_array_type(ctx, field->type, v->arrays.sizes[i]); + for (j = 0; j < v->arrays.count; ++j) + field->type = hlsl_new_array_type(ctx, field->type, v->arrays.sizes[j]); vkd3d_free(v->arrays.sizes); field->loc = v->loc; field->name = v->name; @@ -892,11 +896,10 @@ static struct list *gen_struct_fields(struct hlsl_ctx *ctx, hlsl_error(ctx, &v->loc, VKD3D_SHADER_ERROR_HLSL_INVALID_SYNTAX, "Illegal initializer on a struct field."); free_parse_initializer(&v->initializer); } - list_add_tail(list, &field->entry); vkd3d_free(v); } - vkd3d_free(fields); - return list; + vkd3d_free(defs); + return true; } static bool add_typedef(struct hlsl_ctx *ctx, DWORD modifiers, struct hlsl_type *orig_type, struct list *list) @@ -2681,6 +2684,7 @@ static bool add_method_call(struct hlsl_ctx *ctx, struct list *instrs, struct hl DWORD modifiers; struct hlsl_ir_node *instr; struct list *list; + struct parse_fields fields; struct parse_function function; struct parse_parameter parameter; struct parse_initializer initializer; @@ -2809,8 +2813,6 @@ static bool add_method_call(struct hlsl_ctx *ctx, struct list *instrs, struct hl %type <list> equality_expr %type <list> expr %type <list> expr_statement -%type <list> field -%type <list> fields_list %type <list> initializer_expr %type <list> jump_statement %type <list> logicand_expr @@ -2847,6 +2849,9 @@ static bool add_method_call(struct hlsl_ctx *ctx, struct list *instrs, struct hl %type <colon_attribute> colon_attribute +%type <fields> field +%type <fields> fields_list + %type <function> func_declaration %type <function> func_prototype @@ -3002,7 +3007,7 @@ named_struct_spec: { bool ret; - $$ = hlsl_new_struct_type(ctx, $2, $4); + $$ = hlsl_new_struct_type(ctx, $2, $4.fields, $4.count); if (hlsl_get_var(ctx->cur_scope, $2)) { @@ -3021,7 +3026,7 @@ named_struct_spec: unnamed_struct_spec: KW_STRUCT '{' fields_list '}' { - $$ = hlsl_new_struct_type(ctx, NULL, $3); + $$ = hlsl_new_struct_type(ctx, NULL, $3.fields, $3.count); } any_identifier: @@ -3032,30 +3037,35 @@ any_identifier: fields_list: %empty { - if (!($$ = make_empty_list(ctx))) - YYABORT; + $$.fields = NULL; + $$.count = 0; + $$.capacity = 0; } | fields_list field { - struct hlsl_struct_field *field, *next, *existing; + size_t i; - $$ = $1; - LIST_FOR_EACH_ENTRY_SAFE(field, next, $2, struct hlsl_struct_field, entry) + for (i = 0; i < $2.count; ++i) { - if ((existing = get_struct_field($$, field->name))) + const struct hlsl_struct_field *field = &$2.fields[i]; + const struct hlsl_struct_field *existing; + + if ((existing = get_struct_field($1.fields, $1.count, field->name))) { - hlsl_error(ctx, &@2, VKD3D_SHADER_ERROR_HLSL_REDEFINED, + hlsl_error(ctx, &field->loc, VKD3D_SHADER_ERROR_HLSL_REDEFINED, "Field \"%s\" is already defined.", field->name); hlsl_note(ctx, &existing->loc, VKD3D_SHADER_LOG_ERROR, "'%s' was previously defined here.", field->name); - vkd3d_free(field); - } - else - { - list_add_tail($$, &field->entry); } } - vkd3d_free($2); + + if (!hlsl_array_reserve(ctx, (void **)&$1.fields, &$1.capacity, $1.count + $2.count, sizeof(*$1.fields))) + YYABORT; + memcpy($1.fields + $1.count, $2.fields, $2.count * sizeof(*$2.fields)); + $1.count += $2.count; + vkd3d_free($2.fields); + + $$ = $1; } field_type: @@ -3079,7 +3089,8 @@ field: "Modifiers '%s' are not allowed on struct fields.", string->buffer); hlsl_release_string_buffer(ctx, string); } - $$ = gen_struct_fields(ctx, type, modifiers, $3); + if (!gen_struct_fields(ctx, &$$, type, modifiers, $3)) + YYABORT; } func_declaration: @@ -3936,9 +3947,9 @@ postfix_expr: if (node->data_type->type == HLSL_CLASS_STRUCT) { struct hlsl_type *type = node->data_type; - struct hlsl_struct_field *field; + const struct hlsl_struct_field *field; - if (!(field = get_struct_field(type->e.elements, $3))) + if (!(field = get_struct_field(type->e.record.fields, type->e.record.field_count, $3))) { hlsl_error(ctx, &@3, VKD3D_SHADER_ERROR_HLSL_NOT_DEFINED, "Field \"%s\" is not defined.", $3); YYABORT; diff --git a/libs/vkd3d-shader/hlsl_codegen.c b/libs/vkd3d-shader/hlsl_codegen.c index bc7f0a62..484b415d 100644 --- a/libs/vkd3d-shader/hlsl_codegen.c +++ b/libs/vkd3d-shader/hlsl_codegen.c @@ -137,10 +137,12 @@ static void prepend_input_copy(struct hlsl_ctx *ctx, struct list *instrs, struct static void prepend_input_struct_copy(struct hlsl_ctx *ctx, struct list *instrs, struct hlsl_ir_var *var, struct hlsl_type *type, unsigned int field_offset) { - struct hlsl_struct_field *field; + size_t i; - LIST_FOR_EACH_ENTRY(field, type->e.elements, struct hlsl_struct_field, entry) + for (i = 0; i < type->e.record.field_count; ++i) { + const struct hlsl_struct_field *field = &type->e.record.fields[i]; + if (field->type->type == HLSL_CLASS_STRUCT) prepend_input_struct_copy(ctx, instrs, var, field->type, field_offset + field->reg_offset); else if (field->semantic.name) @@ -225,10 +227,12 @@ static void append_output_copy(struct hlsl_ctx *ctx, struct list *instrs, struct static void append_output_struct_copy(struct hlsl_ctx *ctx, struct list *instrs, struct hlsl_ir_var *var, struct hlsl_type *type, unsigned int field_offset) { - struct hlsl_struct_field *field; + size_t i; - LIST_FOR_EACH_ENTRY(field, type->e.elements, struct hlsl_struct_field, entry) + for (i = 0; i < type->e.record.field_count; ++i) { + const struct hlsl_struct_field *field = &type->e.record.fields[i]; + if (field->type->type == HLSL_CLASS_STRUCT) append_output_struct_copy(ctx, instrs, var, field->type, field_offset + field->reg_offset); else if (field->semantic.name) @@ -859,10 +863,10 @@ static bool split_array_copies(struct hlsl_ctx *ctx, struct hlsl_ir_node *instr, static bool split_struct_copies(struct hlsl_ctx *ctx, struct hlsl_ir_node *instr, void *context) { - const struct hlsl_struct_field *field; const struct hlsl_ir_node *rhs; const struct hlsl_type *type; struct hlsl_ir_store *store; + size_t i; if (instr->type != HLSL_IR_STORE) return false; @@ -879,8 +883,10 @@ static bool split_struct_copies(struct hlsl_ctx *ctx, struct hlsl_ir_node *instr return false; } - LIST_FOR_EACH_ENTRY(field, type->e.elements, struct hlsl_struct_field, entry) + for (i = 0; i < type->e.record.field_count; ++i) { + const struct hlsl_struct_field *field = &type->e.record.fields[i]; + if (!split_copy(ctx, store, hlsl_ir_load(rhs), field->reg_offset, field->type)) return false; } diff --git a/libs/vkd3d-shader/hlsl_sm1.c b/libs/vkd3d-shader/hlsl_sm1.c index 0cdd3917..06313a42 100644 --- a/libs/vkd3d-shader/hlsl_sm1.c +++ b/libs/vkd3d-shader/hlsl_sm1.c @@ -243,28 +243,33 @@ static void write_sm1_type(struct vkd3d_bytecode_buffer *buffer, struct hlsl_typ { const struct hlsl_type *array_type = get_array_type(type); unsigned int array_size = get_array_size(type); - struct hlsl_struct_field *field; unsigned int field_count = 0; size_t fields_offset = 0; + size_t i; if (type->bytecode_offset) return; if (array_type->type == HLSL_CLASS_STRUCT) { - LIST_FOR_EACH_ENTRY(field, array_type->e.elements, struct hlsl_struct_field, entry) + field_count = array_type->e.record.field_count; + + for (i = 0; i < field_count; ++i) { + struct hlsl_struct_field *field = &array_type->e.record.fields[i]; + field->name_bytecode_offset = put_string(buffer, field->name); write_sm1_type(buffer, field->type, ctab_start); } fields_offset = bytecode_get_size(buffer) - ctab_start; - LIST_FOR_EACH_ENTRY(field, array_type->e.elements, struct hlsl_struct_field, entry) + for (i = 0; i < field_count; ++i) { + struct hlsl_struct_field *field = &array_type->e.record.fields[i]; + put_u32(buffer, field->name_bytecode_offset - ctab_start); put_u32(buffer, field->type->bytecode_offset - ctab_start); - ++field_count; } } diff --git a/libs/vkd3d-shader/hlsl_sm4.c b/libs/vkd3d-shader/hlsl_sm4.c index 79027169..7758555b 100644 --- a/libs/vkd3d-shader/hlsl_sm4.c +++ b/libs/vkd3d-shader/hlsl_sm4.c @@ -355,7 +355,7 @@ static void write_sm4_type(struct hlsl_ctx *ctx, struct vkd3d_bytecode_buffer *b const struct hlsl_profile_info *profile = ctx->profile; unsigned int field_count = 0, array_size = 0; size_t fields_offset = 0, name_offset = 0; - struct hlsl_struct_field *field; + size_t i; if (type->bytecode_offset) return; @@ -368,20 +368,25 @@ static void write_sm4_type(struct hlsl_ctx *ctx, struct vkd3d_bytecode_buffer *b if (array_type->type == HLSL_CLASS_STRUCT) { - LIST_FOR_EACH_ENTRY(field, array_type->e.elements, struct hlsl_struct_field, entry) + field_count = array_type->e.record.field_count; + + for (i = 0; i < field_count; ++i) { + struct hlsl_struct_field *field = &array_type->e.record.fields[i]; + field->name_bytecode_offset = put_string(buffer, field->name); write_sm4_type(ctx, buffer, field->type); } fields_offset = bytecode_get_size(buffer); - LIST_FOR_EACH_ENTRY(field, array_type->e.elements, struct hlsl_struct_field, entry) + for (i = 0; i < field_count; ++i) { + struct hlsl_struct_field *field = &array_type->e.record.fields[i]; + put_u32(buffer, field->name_bytecode_offset); put_u32(buffer, field->type->bytecode_offset); put_u32(buffer, field->reg_offset); - ++field_count; } } -- 2.34.1

6 50

Re: [PATCH 2/2] mshtml: Implement targetOrigin for postMessage.
by Marvin Aug. 3, 2022

Aug. 3, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120464 Your paranoid android. === w10pro64_en_AE_u8 (64 bit report) === mshtml: htmldoc.c:2541: Test failed: unexpected call UpdateUI htmldoc.c:2853: Test failed: unexpected call Exec_UPDATECOMMANDS

1 0

Re: [PATCH 2/5] d3d9/tests: Expand tests for valid pools in UpdateTexture().
by Marvin Aug. 3, 2022

Aug. 3, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120466 Your paranoid android. === w8 (32 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w8adm (32 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w864 (32 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w1064v1507 (32 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w1064v1809 (32 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w1064 (32 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w1064_tsign (32 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w10pro64 (32 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w864 (64 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w1064v1507 (64 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w1064v1809 (64 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w1064 (64 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w1064_2qxl (64 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. device.c:14775: Test failed: Adapter 1: Expect window rect (1024,0)-(2304,800), got (0,0)-(1280,800). === w1064_adm (64 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w1064_tsign (64 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w10pro64 (64 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w10pro64_en_AE_u8 (64 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w10pro64_ar (64 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w10pro64_ja (64 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === w10pro64_zh_CN (64 bit report) === d3d9: device.c:11937: Test failed: Got unexpected hr 0x88760868. device.c:11942: Test failed: Got unexpected hr 0x88760868. device.c:11944: Test failed: Got unexpected hr 0x88760869. device.c:11946: Test failed: Got unexpected hr 0x8876086c. === debian11 (64 bit WoW report) === d3d9: device: Timeout

1 0

Re: [PATCH 1/5] d3d8/tests: Expand tests for valid pools in UpdateTexture().
by Marvin Aug. 3, 2022

Aug. 3, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120465 Your paranoid android. === w1064v1507 (32 bit report) === d3d8: device.c:10825: Test failed: Adapter 0: SetForegroundWindow failed, error 0. === w1064v1809 (32 bit report) === d3d8: device.c:10825: Test failed: Adapter 0: SetForegroundWindow failed, error 0. === w10pro64 (32 bit report) === d3d8: device.c:10825: Test failed: Adapter 0: SetForegroundWindow failed, error 0. === debian11 (32 bit report) === d3d8: Unhandled exception: page fault on read access to 0x007b1000 in 32-bit code (0x714b859f). === debian11 (32 bit German report) === d3d8: Unhandled exception: page fault on read access to 0x002f0010 in 32-bit code (0x714b859f). === debian11 (32 bit French report) === d3d8: Unhandled exception: page fault on read access to 0x002f0010 in 32-bit code (0x714b859f). === debian11 (32 bit Chinese:China report) === d3d8: Unhandled exception: page fault on read access to 0x002f0010 in 32-bit code (0x714b859f). === debian11 (64 bit WoW report) === d3d8: Unhandled exception: page fault on read access to 0xffffffffffffffff in 64-bit code (0x000000712b2dce).

1 0

Re: [PATCH 2/3] dlls/urlmon/tests: Don't use read as a global variable.
by Marvin Aug. 3, 2022

Aug. 3, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120438 Your paranoid android. === w1064v1507 (32 bit report) === urlmon: url.c:1466: Test failed: progress 65: status = 200 === w1064v1507 (64 bit report) === urlmon: url.c:1466: Test failed: progress 65: status = 200 === w1064_adm (64 bit report) === urlmon: url.c:1466: Test failed: progress 1: status = 200 url.c:1466: Test failed: progress 2: status = 200 === debian11 (32 bit report) === urlmon: url.c:1654: Test failed: unexpected call OnProgress_CONNECTING url.c:1466: Test failed: progress 2: status = 302

1 0

Re: [PATCH 7/7] win32u: Move display placement logic out of graphics drivers.
by Marvin Aug. 3, 2022

Aug. 3, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120436 Your paranoid android. === debian11 (build log) === error: patch failed: dlls/winex11.drv/display.c:784 error: patch failed: dlls/winex11.drv/display.c:498 error: patch failed: dlls/winex11.drv/display.c:390 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/winex11.drv/display.c:784 error: patch failed: dlls/winex11.drv/display.c:498 error: patch failed: dlls/winex11.drv/display.c:390 Task: Patch failed to apply

1 0

Re: [PATCH 6/7] win32u: Use current mode position if desired mode doesn't specify it.
by Marvin Aug. 3, 2022

Aug. 3, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120435 Your paranoid android. === debian11 (build log) === error: patch failed: dlls/winex11.drv/display.c:784 error: patch failed: dlls/winex11.drv/display.c:498 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/winex11.drv/display.c:784 error: patch failed: dlls/winex11.drv/display.c:498 Task: Patch failed to apply

1 0

Re: [PATCH 5/7] win32u: Validate NtUserChangeDisplaySettings mode against available modes.
by Marvin Aug. 3, 2022

Aug. 3, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120434 Your paranoid android. === debian11 (build log) === error: patch failed: dlls/winex11.drv/display.c:784 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/winex11.drv/display.c:784 Task: Patch failed to apply

1 0

Re: [PATCH 6/6] mf: Propagate missing attributes to downstream media types.
by Marvin Aug. 3, 2022

Aug. 3, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120429 Your paranoid android. === build (build log) === error: corrupt patch at line 38 Task: Patch failed to apply === debian11 (build log) === error: corrupt patch at line 38 Task: Patch failed to apply === debian11 (build log) === error: corrupt patch at line 38 Task: Patch failed to apply

1 0

Re: [PATCH 5/6] mf: Use the MFT_CATEGORY_VIDEO_PROCESSOR category for converters.
by Marvin Aug. 3, 2022

Aug. 3, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120428 Your paranoid android. === build (build log) === error: corrupt patch at line 38 Task: Patch failed to apply === debian11 (build log) === error: corrupt patch at line 38 Task: Patch failed to apply === debian11 (build log) === error: corrupt patch at line 38 Task: Patch failed to apply

1 0

Re: [PATCH 4/6] winegstreamer: Better implement Video Processor MFT.
by Marvin Aug. 3, 2022

Aug. 3, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120427 Your paranoid android. === build (build log) === error: corrupt patch at line 38 Task: Patch failed to apply === debian11 (build log) === error: corrupt patch at line 38 Task: Patch failed to apply === debian11 (build log) === error: corrupt patch at line 38 Task: Patch failed to apply

1 0

Re: [PATCH 3/6] mf/tests: Add topology loader tests with video formats.
by Marvin Aug. 3, 2022

Aug. 3, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120426 Your paranoid android. === build (build log) === error: corrupt patch at line 38 Task: Patch failed to apply === debian11 (build log) === error: corrupt patch at line 38 Task: Patch failed to apply === debian11 (build log) === error: corrupt patch at line 38 Task: Patch failed to apply

1 0

Re: [PATCH 2/6] mf/tests: Add video processor conversion tests.
by Marvin Aug. 3, 2022

Aug. 3, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120425 Your paranoid android. === build (build log) === error: corrupt patch at line 38 Task: Patch failed to apply === debian11 (build log) === error: corrupt patch at line 38 Task: Patch failed to apply === debian11 (build log) === error: corrupt patch at line 38 Task: Patch failed to apply

1 0

Re: [PATCH 1/6] mf/tests: Rotate test videos 90° to better show vertical flips.
by Marvin Aug. 3, 2022

Aug. 3, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120424 Your paranoid android. === build (build log) === error: corrupt patch at line 38 Task: Patch failed to apply === debian11 (build log) === error: corrupt patch at line 38 Task: Patch failed to apply === debian11 (build log) === error: corrupt patch at line 38 Task: Patch failed to apply

1 0

Re: [PATCH v15 1/1] cabinet/tests: add tests for DllGetVersion & GetDllVersion expect both functions to fail in wine as a) D
by Marvin Aug. 2, 2022

Aug. 2, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120358 Your paranoid android. === debian11 (32 bit report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Arabic:Morocco report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit German report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit French report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Hebrew:Israel report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Hindi:India report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Japanese:Japan report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Chinese:China report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit WoW report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (64 bit WoW report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 64-bit code (0x0000007b0138ae).

1 0

Re: [PATCH v14 1/1] cabinet/tests: add tests for DllGetVersion & GetDllVersion expect both functions to fail in wine as a) D
by Marvin Aug. 2, 2022

Aug. 2, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120357 Your paranoid android. === debian11 (32 bit report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Arabic:Morocco report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit German report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit French report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Hebrew:Israel report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Hindi:India report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Japanese:Japan report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Chinese:China report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit WoW report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (64 bit WoW report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 64-bit code (0x0000007b0138ae).

1 0

Re: [PATCH v12 1/1] cabinet/tests: add tests for DllGetVersion & GetDllVersion expect both functions to fail in wine as a) D
by Marvin Aug. 2, 2022

Aug. 2, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120356 Your paranoid android. === debian11 (32 bit report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Arabic:Morocco report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit German report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit French report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Hebrew:Israel report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Hindi:India report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Japanese:Japan report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Chinese:China report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit WoW report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (64 bit WoW report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 64-bit code (0x0000007b0138ae).

1 0

Re: [PATCH v11 1/1] cabinet/tests: add tests for DllGetVersion & GetDllVersion expect both functions to fail in wine as a) D
by Marvin Aug. 2, 2022

Aug. 2, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120355 Your paranoid android. === w7u_2qxl (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w7u_adm (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w7u_el (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w8 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w8adm (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w864 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064v1507 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064v1809 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064_tsign (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w10pro64 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w864 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064v1507 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064v1809 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064_2qxl (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064_adm (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064_tsign (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w10pro64 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w10pro64_en_AE_u8 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w10pro64_ar (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w10pro64_ja (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w10pro64_zh_CN (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === debian11 (32 bit report) === cabinet: version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Arabic:Morocco report) === cabinet: version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit German report) === cabinet: version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit French report) === cabinet: version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Hebrew:Israel report) === cabinet: version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Hindi:India report) === cabinet: version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Japanese:Japan report) === cabinet: version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Chinese:China report) === cabinet: version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit WoW report) === cabinet: version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (64 bit WoW report) === cabinet: version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 64-bit code (0x0000007b0138ae).

1 0

Re: [PATCH v10 1/1] cabinet/tests: add tests for DllGetVersion & GetDllVersion expect both functions to fail in wine as a) D
by Marvin Aug. 2, 2022

Aug. 2, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120354 Your paranoid android. === w7u_2qxl (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w7u_adm (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w7u_el (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w8 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w8adm (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w864 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064v1507 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064v1809 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064_tsign (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w10pro64 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w864 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064v1507 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064v1809 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064_2qxl (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064_adm (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w1064_tsign (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w10pro64 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w10pro64_en_AE_u8 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w10pro64_ar (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w10pro64_ja (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === w10pro64_zh_CN (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. === debian11 (32 bit report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Arabic:Morocco report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit German report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit French report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Hebrew:Israel report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Hindi:India report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Japanese:Japan report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Chinese:China report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit WoW report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (64 bit WoW report) === cabinet: version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 64-bit code (0x0000007b0138ae).

1 0

Re: [PATCH v9 1/1] cabinet/tests: add tests for DllGetVersion & GetDllVersion expect both functions to fail in wine as a) Dl
by Marvin Aug. 2, 2022

Aug. 2, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120351 Your paranoid android. === w7u_2qxl (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w7u_adm (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w7u_el (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w8 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w8adm (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w864 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w1064v1507 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w1064v1809 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w1064 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w1064_tsign (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w10pro64 (32 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w864 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w1064v1507 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w1064v1809 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w1064 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w1064_2qxl (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w1064_adm (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w1064_tsign (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w10pro64 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w10pro64_en_AE_u8 (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w10pro64_ar (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w10pro64_ja (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127. === w10pro64_zh_CN (64 bit report) === cabinet: version.c:57: Test failed: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test failed: Function GetDllVersion in DLL not found: Error = 127.

1 0

Re: [PATCH v2 4/7] ws2_32/tests: Work around a Linux bug.
by Marvin Aug. 2, 2022

Aug. 2, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120345 Your paranoid android. === debian11 (32 bit report) === ws2_32: sock.c:8699: Test failed: got 0 === debian11 (32 bit Arabic:Morocco report) === ws2_32: sock.c:8699: Test failed: got 0 === debian11 (32 bit German report) === ws2_32: sock.c:8699: Test failed: got 0 === debian11 (32 bit French report) === ws2_32: sock.c:8699: Test failed: got 0 === debian11 (32 bit Hebrew:Israel report) === ws2_32: sock.c:8699: Test failed: got 0 === debian11 (32 bit Hindi:India report) === ws2_32: sock.c:8699: Test failed: got 0 === debian11 (32 bit Japanese:Japan report) === ws2_32: sock.c:8699: Test failed: got 0 === debian11 (32 bit Chinese:China report) === ws2_32: sock.c:8699: Test failed: got 0 === debian11 (32 bit WoW report) === ws2_32: sock.c:8699: Test failed: got 0 === debian11 (64 bit WoW report) === ws2_32: sock.c:8699: Test failed: got 0

1 0

Re: [PATCH v2 3/7] ws2_32/tests: Test send() after TCP reset.
by Marvin Aug. 2, 2022

Aug. 2, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120344 Your paranoid android. === debian11 (32 bit report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Arabic:Morocco report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit German report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit French report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Hebrew:Israel report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Hindi:India report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Japanese:Japan report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Chinese:China report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit WoW report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (64 bit WoW report) === ws2_32: sock.c:8693: Test failed: got 0

1 0

Re: [PATCH v2 1/7] ws2_32/tests: Test sending data to a peer is closed().
by Marvin Aug. 2, 2022

Aug. 2, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120342 Your paranoid android. === debian11 (32 bit report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Arabic:Morocco report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit German report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit French report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Hebrew:Israel report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Hindi:India report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Japanese:Japan report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit Chinese:China report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (32 bit WoW report) === ws2_32: sock.c:8693: Test failed: got 0 === debian11 (64 bit WoW report) === ws2_32: sock.c:8693: Test failed: got 0

1 0

Re: [PATCH v6 3/3] cabinet: Implement GetDllVersion implement GetDllVersion, use DllGetVersion as helper function to retreiv
by Marvin Aug. 1, 2022

Aug. 1, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120332 Your paranoid android. === debian11 (build log) === ../wine/dlls/cabinet/cabinet_main.c:58:13: error: conflicting types for ‘DllGetVersion’ Task: The win32 Wine build failed === debian11 (build log) === ../wine/dlls/cabinet/cabinet_main.c:58:13: error: conflicting types for ‘DllGetVersion’ Task: The wow64 Wine build failed

1 0

Re: [PATCH v6 2/3] cabinet: implement DllGetVersion correctly implement DllGetVersion with correct parameter and behaviour c
by Marvin Aug. 1, 2022

Aug. 1, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120331 Your paranoid android. === debian11 (build log) === ../wine/dlls/cabinet/cabinet_main.c:58:13: error: conflicting types for ‘DllGetVersion’ Task: The win32 Wine build failed === debian11 (build log) === ../wine/dlls/cabinet/cabinet_main.c:58:13: error: conflicting types for ‘DllGetVersion’ Task: The wow64 Wine build failed

1 0

Re: [PATCH v6 1/3] cabinet: test GetDllVersion & DllGetVersion Tests are expected to fail as: DllGetVersion isn't implemente
by Marvin Aug. 1, 2022

Aug. 1, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120330 Your paranoid android. === debian11 (32 bit report) === cabinet: version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203. version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly! version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Arabic:Morocco report) === cabinet: version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203. version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly! version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit German report) === cabinet: version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203. version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly! version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit French report) === cabinet: version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203. version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly! version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Hebrew:Israel report) === cabinet: version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203. version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly! version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Hindi:India report) === cabinet: version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203. version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly! version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Japanese:Japan report) === cabinet: version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203. version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly! version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit Chinese:China report) === cabinet: version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203. version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly! version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (32 bit WoW report) === cabinet: version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203. version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly! version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 32-bit code (0x7b0122f6). === debian11 (64 bit WoW report) === cabinet: version.c:34: Test succeeded inside todo block: Function DllGetVersion in DLL not found: Error = 203. version.c:38: Test succeeded inside todo block: Couldn't allocate memory to run tests properly! version.c:57: Test succeeded inside todo block: Cabinet struct doesn't contain correct version: Error = 203. version.c:67: Test succeeded inside todo block: Function GetDllVersion in DLL not found: Error = 203. Unhandled exception: unimplemented function cabinet.dll.GetDllVersion called in 64-bit code (0x0000007b0138ae).

1 0

Re: [PATCH 3/3] mshtml: Implement MediaQueryList's matches prop.
by Marvin Aug. 1, 2022

Aug. 1, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120307 Your paranoid android. === w1064v1809 (64 bit report) === mshtml: script.c:3119: Test failed: ReportResult failed: 80ef0001

1 0

Re: [PATCH 2/3] mshtml: Implement MediaQueryList's media prop.
by Marvin Aug. 1, 2022

Aug. 1, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120306 Your paranoid android. === w10pro64_en_AE_u8 (64 bit report) === mshtml: htmldoc.c:2541: Test failed: unexpected call UpdateUI htmldoc.c:2853: Test failed: unexpected call Exec_UPDATECOMMANDS

1 0

Re: [PATCH 6/6] widl: Use a struct list for the import stack.
by Marvin Aug. 1, 2022

Aug. 1, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120323 Your paranoid android. === debian11 (build log) === tools/widl/parser.tab.h:322:5: error: conflicting types for ‘parser_parse’ ../wine/tools/widl/widl.c:899:9: error: too many arguments to function ‘parser_parse’ Task: The win32 Wine build failed === debian11 (build log) === tools/widl/parser.tab.h:322:5: error: conflicting types for ‘parser_parse’ ../wine/tools/widl/widl.c:899:9: error: too many arguments to function ‘parser_parse’ Task: The wow64 Wine build failed

1 0

Re: [PATCH 5/6] widl: Simplify handling of already parsed imports.
by Marvin Aug. 1, 2022

Aug. 1, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120322 Your paranoid android. === debian11 (build log) === tools/widl/parser.tab.h:322:5: error: conflicting types for ‘parser_parse’ ../wine/tools/widl/widl.c:899:9: error: too many arguments to function ‘parser_parse’ Task: The win32 Wine build failed === debian11 (build log) === tools/widl/parser.tab.h:322:5: error: conflicting types for ‘parser_parse’ ../wine/tools/widl/widl.c:899:9: error: too many arguments to function ‘parser_parse’ Task: The wow64 Wine build failed

1 0

Re: [PATCH 4/6] widl: Use a struct list to keep imported files.
by Marvin Aug. 1, 2022

Aug. 1, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120321 Your paranoid android. === debian11 (build log) === tools/widl/parser.tab.h:322:5: error: conflicting types for ‘parser_parse’ ../wine/tools/widl/widl.c:899:9: error: too many arguments to function ‘parser_parse’ Task: The win32 Wine build failed === debian11 (build log) === tools/widl/parser.tab.h:322:5: error: conflicting types for ‘parser_parse’ ../wine/tools/widl/widl.c:899:9: error: too many arguments to function ‘parser_parse’ Task: The wow64 Wine build failed

1 0

Re: [PATCH 3/6] widl: Move output generation calls out of parser.y.
by Marvin Aug. 1, 2022

Aug. 1, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120320 Your paranoid android. === debian11 (build log) === tools/widl/parser.tab.h:322:5: error: conflicting types for ‘parser_parse’ ../wine/tools/widl/widl.c:899:9: error: too many arguments to function ‘parser_parse’ Task: The win32 Wine build failed === debian11 (build log) === tools/widl/parser.tab.h:322:5: error: conflicting types for ‘parser_parse’ ../wine/tools/widl/widl.c:899:9: error: too many arguments to function ‘parser_parse’ Task: The wow64 Wine build failed

1 0

Re: [PATCH 1/3] mshtml: Implement window.matchMedia() with MediaQueryList stub.
by Marvin Aug. 1, 2022

Aug. 1, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120305 Your paranoid android. === w10pro64 (64 bit report) === mshtml: htmldoc.c:2541: Test failed: unexpected call UpdateUI htmldoc.c:2853: Test failed: unexpected call Exec_UPDATECOMMANDS htmldoc.c:2541: Test failed: unexpected call UpdateUI htmldoc.c:2853: Test failed: unexpected call Exec_UPDATECOMMANDS htmldoc.c:350: Test failed: expected Exec_SETTITLE htmldoc.c:2859: Test failed: unexpected call Exec_SETTITLE === w10pro64_ja (64 bit report) === mshtml: htmldoc.c:2541: Test failed: unexpected call UpdateUI htmldoc.c:2853: Test failed: unexpected call Exec_UPDATECOMMANDS htmldoc.c:350: Test failed: expected Exec_SETTITLE htmldoc.c:2859: Test failed: unexpected call Exec_SETTITLE

1 0

Re: [PATCH 2/3] shell32: Add SHBindToFolderIDListParent tests.
by Marvin July 31, 2022

July 31, 2022

Hi, It looks like your patch introduced the new failures shown below. Please investigate and fix them before resubmitting your patch. If they are not new, fixing them anyway would help a lot. Otherwise please ask for the known failures list to be updated. The tests also ran into some preexisting test failures. If you know how to fix them that would be helpful. See the TestBot job for the details: The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=120263 Your paranoid android. === w1064v1809 (64 bit report) === shell32: shlfolder.c:4992: Test failed: RMDIR: expected notification type 10, got: 40000 === w1064_tsign (64 bit report) === shell32: shlfolder.c:5009: Test failed: Didn't expect a WM_USER_NOTIFY message (event: 2) === w10pro64_zh_CN (64 bit report) === shell32: shlfolder.c:4992: Test failed: RMDIR: expected notification type 10, got: 40000

1 0