- wine-devel - winehq.org

Re: [PATCH v2 3/5] mshtml: Implement document.doctype.
by Marvin 29 Jul '22

29 Jul '22

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=120190 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 htmldoc.c:350: Test failed: expected Exec_SETTITLE htmldoc.c:2859: Test failed: unexpected call Exec_SETTITLE

1 0

Re: [PATCH 4/5] mshtml: Implement DocumentType node's name prop.
by Marvin 29 Jul '22

29 Jul '22

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=120170 Your paranoid android. === 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: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 3/5] mshtml: Implement document.doctype.
by Marvin 29 Jul '22

29 Jul '22

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=120169 Your paranoid android. === w1064v1809 (testbot log) === WineRunTask.pl:error: The previous 1 run(s) terminated abnormally

1 0

[PATCH vkd3d 2/3] vkd3d-shader: Introduce a compile option to use Unknown format for typed UAV reads.
by Conor McCarthy 29 Jul '22

29 Jul '22

Specifying R32ui for UAVs created with a vector format, e.g. R32G32B32A32_FLOAT, results in only the red being loaded/stored, potentially causing images to contain only the red component. Signed-off-by: Conor McCarthy <cmccarthy(a)codeweavers.com> --- include/vkd3d_shader.h | 18 ++++++++++++++++++ libs/vkd3d-shader/spirv.c | 16 +++++++++++++++- 2 files changed, 33 insertions(+), 1 deletion(-) diff --git a/include/vkd3d_shader.h b/include/vkd3d_shader.h index ebddbba7..4175223f 100644 --- a/include/vkd3d_shader.h +++ b/include/vkd3d_shader.h @@ -99,6 +99,22 @@ enum vkd3d_shader_compile_option_buffer_uav VKD3D_FORCE_32_BIT_ENUM(VKD3D_SHADER_COMPILE_OPTION_BUFFER_UAV), }; +/** + * Determines how typed UAVs are declared. + */ +enum vkd3d_shader_compile_option_typed_uav +{ + /** Use R32ui format for UAVs which are read from. This is the default value. */ + VKD3D_SHADER_COMPILE_OPTION_TYPED_UAV_READ_FORMAT_R32UI = 0x00000000, + /** + * Use Unknown format for UAVs which are read from. This should only be set if + * shaderStorageImageReadWithoutFormat is enabled in the target environment. + */ + VKD3D_SHADER_COMPILE_OPTION_TYPED_UAV_READ_FORMAT_UNKNOWN = 0x00000001, + + VKD3D_FORCE_32_BIT_ENUM(VKD3D_SHADER_COMPILE_OPTION_TYPED_UAV), +}; + enum vkd3d_shader_compile_option_formatting_flags { VKD3D_SHADER_COMPILE_OPTION_FORMATTING_NONE = 0x00000000, @@ -127,6 +143,8 @@ enum vkd3d_shader_compile_option_name VKD3D_SHADER_COMPILE_OPTION_FORMATTING = 0x00000003, /** \a value is a member of enum vkd3d_shader_api_version. \since 1.3 */ VKD3D_SHADER_COMPILE_OPTION_API_VERSION = 0x00000004, + /** \a value is a member of enum vkd3d_shader_compile_option_typed_uav. \since 1.5 */ + VKD3D_SHADER_COMPILE_OPTION_TYPED_UAV = 0x00000005, VKD3D_FORCE_32_BIT_ENUM(VKD3D_SHADER_COMPILE_OPTION_NAME), }; diff --git a/libs/vkd3d-shader/spirv.c b/libs/vkd3d-shader/spirv.c index 776533cb..6450f818 100644 --- a/libs/vkd3d-shader/spirv.c +++ b/libs/vkd3d-shader/spirv.c @@ -2228,6 +2228,7 @@ struct vkd3d_dxbc_compiler bool strip_debug; bool ssbo_uavs; + bool uav_read_without_format; struct rb_tree symbol_table; uint32_t temp_id; @@ -2379,6 +2380,15 @@ struct vkd3d_dxbc_compiler *vkd3d_dxbc_compiler_create(const struct vkd3d_shader case VKD3D_SHADER_COMPILE_OPTION_API_VERSION: break; + + case VKD3D_SHADER_COMPILE_OPTION_TYPED_UAV: + if (option->value == VKD3D_SHADER_COMPILE_OPTION_TYPED_UAV_READ_FORMAT_R32UI) + compiler->uav_read_without_format = false; + else if (option->value == VKD3D_SHADER_COMPILE_OPTION_TYPED_UAV_READ_FORMAT_UNKNOWN) + compiler->uav_read_without_format = true; + else + WARN("Ignoring unrecognised value %#x for option %#x.\n", option->value, option->name); + break; } } @@ -5856,14 +5866,18 @@ static uint32_t vkd3d_dxbc_compiler_get_image_type_id(struct vkd3d_dxbc_compiler const struct vkd3d_shader_descriptor_info *d; uint32_t sampled_type_id; SpvImageFormat format; + bool uav_read; format = SpvImageFormatUnknown; if (reg->type == VKD3DSPR_UAV) { d = vkd3d_dxbc_compiler_get_descriptor_info(compiler, VKD3D_SHADER_DESCRIPTOR_TYPE_UAV, range); - if (raw_structured || (d->flags & VKD3D_SHADER_DESCRIPTOR_INFO_FLAG_UAV_READ)) + uav_read = !!(d->flags & VKD3D_SHADER_DESCRIPTOR_INFO_FLAG_UAV_READ); + if (raw_structured || (uav_read && !compiler->uav_read_without_format)) format = image_format_for_image_read(data_type); + else if (uav_read) + vkd3d_spirv_enable_capability(builder, SpvCapabilityStorageImageReadWithoutFormat); } sampled_type_id = vkd3d_spirv_get_type_id(builder, data_type, 1); -- 2.36.1

3 10

[PATCH v2] ntdll/signalx86_64: Add CFI for __wine_syscall_dispatcher
by Keno Fischer 29 Jul '22

29 Jul '22

In a debugger that is capable of loading both PE and ELF libraries (e.g. the wine-enhanced GDB version at [1]), this unwind information will allow proper unwind across the __wine_syscall_dispatcher. The CFI itself is relatively straightforward, though the implementation looks a little complex, because support for proper CFI encoding is somewhat limitied in the GNU toolchain. Essentially, as registers are stored in the rcx buffer in this function, we switch their cfi description to point at that rcx buffer, so the registers may be freely used thereafter without affecting the unwind. Eventually the rcx buffer is tracked in rbp instead at which point we pivot the CFI information as well and keep it there for most of the rest of the function. [1] https://github.com/JuliaComputing/gdb-solib-wine Signed-off-by: Keno Fischer <keno(a)juliacomputing.com> --- v2: Fix accidental build issues introduced during cleanup. (And missed in my build test, because I forgot to enable win64, sigh). dlls/ntdll/unix/signal_x86_64.c | 181 ++++++++++++++++++++++++++++++++ 1 file changed, 181 insertions(+) diff --git a/dlls/ntdll/unix/signal_x86_64.c b/dlls/ntdll/unix/signal_x86_64.c index d6f19dbfa84..2d33df8bccd 100644 --- a/dlls/ntdll/unix/signal_x86_64.c +++ b/dlls/ntdll/unix/signal_x86_64.c @@ -442,6 +442,10 @@ static USHORT fs32_sel; /* selector for %fs in 32-bit mode */ * Definitions for Dwarf unwind tables */ +/* For use in inline-assembly and other contexts where C enums are unavailable */ +#define PP_DW_CFA_def_cfa_expression 0xf +#define PP_DW_CFA_expression 0x10 + enum dwarf_call_frame_info { DW_CFA_advance_loc = 0x40, @@ -472,6 +476,14 @@ enum dwarf_call_frame_info DW_CFA_val_expression = 0x16, }; +/* DWARF State machine ops */ +#define PP_DW_OP_const1u 0x08 +#define PP_DW_OP_breg_base 0x70 +#define PP_DW_OP_minus 0x1c +#define PP_DW_OP_deref 0x06 +#define PP_DW_OP_plus 0x22 +#define PP_DW_OP_plus_uconst 0x23 + enum dwarf_operation { DW_OP_addr = 0x03, @@ -3288,35 +3300,177 @@ __ASM_GLOBAL_FUNC( signal_exit_thread, __ASM_CFI(".cfi_rel_offset %r15,8\n\t") "call *%rsi" ) + +/*********************************************************************** + * CFI Utility definitions + * + * These utility definitions help encode CFI unwind information (for consumption + * in gdb and similar debuggers), improving the accuracy of backtraces. + */ + +/* DWARF Register ordering for x86_64 */ +#define X86_64_DWARF_RAX 0x00 +#define X86_64_DWARF_RDX 0x01 +#define X86_64_DWARF_RCX 0x02 +#define X86_64_DWARF_RBX 0x03 +#define X86_64_DWARF_RSI 0x04 +#define X86_64_DWARF_RDI 0x05 +#define X86_64_DWARF_RBP 0x06 +#define X86_64_DWARF_RSP 0x07 +#define X86_64_DWARF_R8 0x08 +#define X86_64_DWARF_R9 0x09 +#define X86_64_DWARF_R10 0x0a +#define X86_64_DWARF_R11 0x0b +#define X86_64_DWARF_R12 0x0c +#define X86_64_DWARF_R13 0x0d +#define X86_64_DWARF_R14 0x0e +#define X86_64_DWARF_R15 0x0f +#define X86_64_DWARF_RIP 0x10 + +/* __ASM_REG_IS_DEREF_REF_OFFSET(REG_SAVE, REG, OFFSET) + * + * Declare that the register with DWARF register number `REG` is + * saved at offset `OFFSET` from the register with DWARF register + * number `REG_SAVE`. I.e.: + * + * REG (in previous frame) = *(%REG_SAVE + OFFSET) + */ +#define _STR(R) #R +#define __STR(R) _STR(R) +#define __ASM_REG_IS_DEREF_REF_OFFSET(REG_SAVE, REG, OFFSET) \ + ".cfi_escape " __STR(PP_DW_CFA_expression) ", " \ + _STR(REG) "," /* The register being saved */ \ + " 0x02," /* 2 bytes follow */ \ + __STR(PP_DW_OP_breg_base) " + " _STR(REG_SAVE) ", " #OFFSET ";\n\t" + +/* __ASM_REG_IS_DEREF_REF_OFFSET2(REG_SAVE, REG, OFFSET1, OFFSET2) + * + * Like __ASM_REG_IS_DEREF_REF_OFFSET, expect for offsets of more than + * 7 bits. Takes an SLEB128 encoded offset as two bytes. Thus to e.g. + * encode an offset of 0x70, convert to SLEB128 first: + * + * HEX: 0x70 + * BINARY: 01110000 + * SLEB128: 11110000 00000000 + * |||||||| |||||||| + * |||||||| \------- High bits + * |\------ Low bits + * \- Continuation Bit + * + * SLEB128: 0xf0 0x00 + */ +#define __ASM_REG_IS_DEREF_REF_OFFSET2(REG_SAVE, REG, OFFSET1, OFFSET2) \ + ".cfi_escape " __STR(PP_DW_CFA_expression) ", " \ + _STR(REG) "," /* The register being saved */ \ + " 0x03," /* 3 bytes follow */ \ + __STR(PP_DW_OP_breg_base) " + " _STR(REG_SAVE) ", " #OFFSET1 ", " #OFFSET2 ";\n\t" + +/* __ASM_REG_IS_DEREF_REF_OFFSET_MINUS(REG_SAVE, REG, OFFSET, OFFSET_SUB) + * + * Like __ASM_REG_IS_DEREF_REF_OFFSET, except encodes that the saved + * register value is at `*(%REG_SAVE + OFFSET - OFFSET_SUB). + */ +#define __ASM_REG_IS_DEREF_REF_OFFSET_MINUS(REG_SAVE, REG, OFFSET, OFFSET_SUB) \ + ".cfi_escape " __STR(PP_DW_CFA_expression) ", " \ + _STR(REG) "," /* The register being saved */ \ + " 0x05," /* 5 bytes follow */ \ + __STR(PP_DW_OP_breg_base) " + " _STR(REG_SAVE) ", " #OFFSET "," \ + __STR(PP_DW_OP_const1u) ", " #OFFSET_SUB "," __STR(PP_DW_OP_minus) ";\n\t" + +/* __ASM_CFA_AT_REG_OFFSET(REG_SAVE, OFFSET) + * + * Declares the CFA of set frame to be stored at *(REG_SAVE + OFFSET). + * Note that the CFA is ordinarily the same as the stack pointer at the end + * of the previous frame, but these are technically separate concepts. + */ +#define __ASM_CFA_AT_REG_OFFSET(REG_SAVE, OFFSET) \ + ".cfi_escape " __STR(PP_DW_CFA_def_cfa_expression) "," \ + " 0x03," /* 3 bytes follow */ \ + __STR(PP_DW_OP_breg_base) " + " _STR(REG_SAVE) ", " #OFFSET ", " \ + __STR(PP_DW_OP_deref) ";\n\t" + +/* __ASM_CFA_AT_REG_OFFSET2(REG_SAVE, OFFSET_HIGH, OFFSET_LOW) + * + * Like __ASM_CFA_AT_REG_OFFSET, except used for larger offsets. `OFFSET_LOW` encodes + * the low 7 bits of the offset. `OFFSET_HIGH` the next 7 bits. + */ +#define __ASM_CFA_AT_REG_OFFSET2(REG_SAVE, OFFSET_HIGH, OFFSET_LOW) \ + ".cfi_escape " __STR(PP_DW_CFA_def_cfa_expression) "," \ + " 0x04," /* 4 bytes follow */ \ + __STR(PP_DW_OP_breg_base) " + " _STR(REG_SAVE) ", " #OFFSET_LOW " | 0x80 , " #OFFSET_HIGH ", " \ + __STR(PP_DW_OP_deref) ";\n\t" + +#define __ASM_REG_IS_DEREF_RCX_OFFSET(REG, OFFSET) \ + __ASM_REG_IS_DEREF_REF_OFFSET(X86_64_DWARF_RCX, REG, OFFSET) +#define __ASM_REG_IS_DEREF_RCX_OFFSET2(REG, OFFSET_HIGH, OFFSET_LOW) \ + __ASM_REG_IS_DEREF_REF_OFFSET2(X86_64_DWARF_RCX, REG, OFFSET_LOW | 0x80, OFFSET_HIGH) + +/* __ASM_REGSAVE_AT_DWARF_REG_MINUS(REG_SAVE, OFFSET_SUB) + * + * Declares that a `struct syscall_frame` containing the previous frame's registers may + * be found at `*(struct syscall_frame*)(%REG_SAVE - OFFSET_SUB)` and declares both the + * CFA and saved registers may be found in the corresponding offset. + */ +#define __ASM_REGSAVE_AT_DWARF_REG_MINUS(REG_SAVE, OFFSET_SUB) \ + /* N.B.: First argument is SLEB128 encoded, so move the high bit over \ + to the subtraction */ \ + __ASM_REG_IS_DEREF_REF_OFFSET_MINUS(REG_SAVE, X86_64_DWARF_RIP, 0x00, OFFSET_SUB - 0x70) \ + __ASM_REG_IS_DEREF_REF_OFFSET_MINUS(REG_SAVE, X86_64_DWARF_RAX, 0x00, OFFSET_SUB) \ + __ASM_REG_IS_DEREF_REF_OFFSET_MINUS(REG_SAVE, X86_64_DWARF_RBX, 0x08, OFFSET_SUB) \ + __ASM_REG_IS_DEREF_REF_OFFSET_MINUS(REG_SAVE, X86_64_DWARF_RDX, 0x18, OFFSET_SUB) \ + __ASM_REG_IS_DEREF_REF_OFFSET_MINUS(REG_SAVE, X86_64_DWARF_RSI, 0x20, OFFSET_SUB) \ + __ASM_REG_IS_DEREF_REF_OFFSET_MINUS(REG_SAVE, X86_64_DWARF_RDI, 0x28, OFFSET_SUB) \ + __ASM_REG_IS_DEREF_REF_OFFSET_MINUS(REG_SAVE, X86_64_DWARF_R12, 0x00, OFFSET_SUB - 0x50) \ + __ASM_REG_IS_DEREF_REF_OFFSET_MINUS(REG_SAVE, X86_64_DWARF_R14, 0x10, OFFSET_SUB - 0x50) \ + __ASM_REG_IS_DEREF_REF_OFFSET_MINUS(REG_SAVE, X86_64_DWARF_RSP, 0x08, OFFSET_SUB - 0x80) \ + /* -0x10 in 7bit 2's complement */ \ + __ASM_CFA_AT_REG_OFFSET(REG_SAVE, 0x70) \ + __ASM_REG_IS_DEREF_REF_OFFSET_MINUS(REG_SAVE, X86_64_DWARF_RBP, 0x18, OFFSET_SUB - 0x80) + /*********************************************************************** * __wine_syscall_dispatcher */ __ASM_GLOBAL_FUNC( __wine_syscall_dispatcher, "movq %gs:0x30,%rcx\n\t" + __ASM_CFI(".cfi_undefined rcx\n\t") "movq 0x328(%rcx),%rcx\n\t" /* amd64_thread_data()->syscall_frame */ "popq 0x70(%rcx)\n\t" /* frame->rip */ + __ASM_CFI(".cfi_adjust_cfa_offset -8\n\t") + __ASM_REG_IS_DEREF_RCX_OFFSET2(X86_64_DWARF_RIP, 0x00, 0x70) "pushfq\n\t" + __ASM_CFI(".cfi_adjust_cfa_offset 8\n\t") "popq 0x80(%rcx)\n\t" + __ASM_CFI(".cfi_adjust_cfa_offset -8\n\t") "movl $0,0x94(%rcx)\n\t" /* frame->restore_flags */ ".globl " __ASM_NAME("__wine_syscall_dispatcher_prolog_end") "\n" __ASM_NAME("__wine_syscall_dispatcher_prolog_end") ":\n\t" "movq %rax,0x00(%rcx)\n\t" + __ASM_REG_IS_DEREF_RCX_OFFSET(X86_64_DWARF_RAX, 0x00) "movq %rbx,0x08(%rcx)\n\t" + __ASM_REG_IS_DEREF_RCX_OFFSET(X86_64_DWARF_RBX, 0x08) "movq %rdx,0x18(%rcx)\n\t" + __ASM_REG_IS_DEREF_RCX_OFFSET(X86_64_DWARF_RDX, 0x18) "movq %rsi,0x20(%rcx)\n\t" + __ASM_REG_IS_DEREF_RCX_OFFSET(X86_64_DWARF_RSI, 0x20) "movq %rdi,0x28(%rcx)\n\t" + __ASM_REG_IS_DEREF_RCX_OFFSET(X86_64_DWARF_RDI, 0x28) "movq %r12,0x50(%rcx)\n\t" + __ASM_REG_IS_DEREF_RCX_OFFSET2(X86_64_DWARF_R12, 0x00, 0x50) "movq %r13,0x58(%rcx)\n\t" "movq %r14,0x60(%rcx)\n\t" + __ASM_REG_IS_DEREF_RCX_OFFSET2(X86_64_DWARF_R14, 0x00, 0x60) "movq %r15,0x68(%rcx)\n\t" "movw %cs,0x78(%rcx)\n\t" "movw %ds,0x7a(%rcx)\n\t" "movw %es,0x7c(%rcx)\n\t" "movw %fs,0x7e(%rcx)\n\t" "movq %rsp,0x88(%rcx)\n\t" + __ASM_REG_IS_DEREF_RCX_OFFSET2(X86_64_DWARF_RSP, 0x01, 0x08) + __ASM_CFA_AT_REG_OFFSET2(X86_64_DWARF_RCX, 0x01, 0x08) "movw %ss,0x90(%rcx)\n\t" "movw %gs,0x92(%rcx)\n\t" "movq %rbp,0x98(%rcx)\n\t" + __ASM_REG_IS_DEREF_RCX_OFFSET2(X86_64_DWARF_RBP, 0x01, 0x18) /* Legends of Runeterra hooks the first system call return instruction, and * depends on us returning to it. Adjust the return address accordingly. */ "subq $0xb,0x70(%rcx)\n\t" @@ -3341,6 +3495,8 @@ __ASM_GLOBAL_FUNC( __wine_syscall_dispatcher, "jmp 3f\n" "2:\tfxsave64 0xc0(%rcx)\n" "3:\tleaq 0x98(%rcx),%rbp\n\t" + __ASM_CFI(".cfi_remember_state\n\t") + __ASM_REGSAVE_AT_DWARF_REG_MINUS(X86_64_DWARF_RBP, 0x98) #ifdef __linux__ "testl $12,%r14d\n\t" /* SYSCALL_HAVE_PTHREAD_TEB | SYSCALL_HAVE_WRFSGSBASE */ "jz 2f\n\t" @@ -3402,35 +3558,60 @@ __ASM_GLOBAL_FUNC( __wine_syscall_dispatcher, "jmp 4f\n" "3:\tfxrstor64 0xc0(%rcx)\n" "4:\tmovq 0x98(%rcx),%rbp\n\t" + __ASM_CFI(".cfi_restore_state\n\t") "movq 0x68(%rcx),%r15\n\t" + __ASM_CFI(".cfi_same_value r15\n\t") "movq 0x60(%rcx),%r14\n\t" + __ASM_CFI(".cfi_same_value r14\n\t") "movq 0x58(%rcx),%r13\n\t" + __ASM_CFI(".cfi_same_value r13\n\t") "movq 0x50(%rcx),%r12\n\t" + __ASM_CFI(".cfi_same_value r12\n\t") "movq 0x28(%rcx),%rdi\n\t" + __ASM_CFI(".cfi_same_value rdi\n\t") "movq 0x20(%rcx),%rsi\n\t" + __ASM_CFI(".cfi_same_value rsi\n\t") "movq 0x08(%rcx),%rbx\n\t" + __ASM_CFI(".cfi_same_value rbx\n\t") "testl $0x3,%edx\n\t" /* CONTEXT_CONTROL | CONTEXT_INTEGER */ "jnz 1f\n\t" + __ASM_CFI(".cfi_remember_state\n\t") "movq 0x80(%rcx),%r11\n\t" /* frame->eflags */ + __ASM_CFI(".cfi_same_value r11\n\t") "pushq %r11\n\t" "popfq\n\t" "movq 0x88(%rcx),%rsp\n\t" + __ASM_CFI(".cfi_same_value rsp\n\t") "movq 0x70(%rcx),%rcx\n\t" /* frame->rip */ + __ASM_CFI(".cfi_register rip, rcx\n\t") "jmpq *%rcx\n\t" "1:\tleaq 0x70(%rcx),%rsp\n\t" + __ASM_CFI(".cfi_restore_state\n\t") + __ASM_CFI(".cfi_remember_state\n\t") "testl $0x2,%edx\n\t" /* CONTEXT_INTEGER */ "jnz 1f\n\t" "movq 0x10(%rsp),%r11\n\t" /* frame->eflags */ + __ASM_CFI(".cfi_same_value r11\n\t") "movq (%rsp),%rcx\n\t" /* frame->rip */ + __ASM_CFI(".cfi_register rip, rcx\n\t") "iretq\n" "1:\tmovq 0x00(%rcx),%rax\n\t" + __ASM_CFI(".cfi_restore_state\n\t") + __ASM_CFI(".cfi_same_value rax\n\t") "movq 0x18(%rcx),%rdx\n\t" + __ASM_CFI(".cfi_same_value rdx\n\t") "movq 0x30(%rcx),%r8\n\t" + __ASM_CFI(".cfi_same_value r8\n\t") "movq 0x38(%rcx),%r9\n\t" + __ASM_CFI(".cfi_same_value r9\n\t") "movq 0x40(%rcx),%r10\n\t" + __ASM_CFI(".cfi_same_value r10\n\t") "movq 0x48(%rcx),%r11\n\t" + __ASM_CFI(".cfi_same_value r11\n\t") "movq 0x10(%rcx),%rcx\n" + __ASM_REG_IS_DEREF_REF_OFFSET(X86_64_DWARF_RSP, X86_64_DWARF_RIP, 0) "iretq\n" + __ASM_REGSAVE_AT_DWARF_REG_MINUS(X86_64_DWARF_RBP, 0x98) "5:\tmovl $0xc000000d,%edx\n\t" /* STATUS_INVALID_PARAMETER */ "movq %rsp,%rcx\n\t" ".globl " __ASM_NAME("__wine_syscall_dispatcher_return") "\n" -- 2.25.1

1 0

[PATCH] ntdll/signalx86_64: Add CFI for __wine_syscall_dispatcher
by Keno Fischer 29 Jul '22

29 Jul '22

In a debugger that is capable of loading both PE and ELF libraries (e.g. the wine-enhanced GDB version at [1]), this unwind information will allow proper unwind across the __wine_syscall_dispatcher. The CFI itself is relatively straightforward, though the implementation looks a little complex, because support for proper CFI encoding is somewhat limitied in the GNU toolchain. Essentially, as registers are stored in the rcx buffer in this function, we switch their cfi description to point at that rcx buffer, so the registers may be freely used thereafter without affecting the unwind. Eventually the rcx buffer is tracked in rbp instead at which point we pivot the CFI information as well and keep it there for most of the rest of the function. [1] https://github.com/JuliaComputing/gdb-solib-wine Signed-off-by: Keno Fischer <keno(a)juliacomputing.com> --- dlls/ntdll/unix/signal_x86_64.c | 180 ++++++++++++++++++++++++++++++++ 1 file changed, 180 insertions(+) diff --git a/dlls/ntdll/unix/signal_x86_64.c b/dlls/ntdll/unix/signal_x86_64.c index d6f19dbfa84..a6b79335fab 100644 --- a/dlls/ntdll/unix/signal_x86_64.c +++ b/dlls/ntdll/unix/signal_x86_64.c @@ -442,6 +442,10 @@ static USHORT fs32_sel; /* selector for %fs in 32-bit mode */ * Definitions for Dwarf unwind tables */ +/* For use in inline-assembly and other contexts where C enums are unavailable */ +#define PP_DW_CFA_def_cfa_expression 0xf +#define PP_DW_CFA_expression 0x10 + enum dwarf_call_frame_info { DW_CFA_advance_loc = 0x40, @@ -472,6 +476,14 @@ enum dwarf_call_frame_info DW_CFA_val_expression = 0x16, }; +/* DWARF State machine ops */ +#define PP_DW_OP_const1u 0x08 +#define PP_DW_OP_breg_base 0x70 +#define PP_DW_OP_minus 0x1c +#define PP_DW_OP_deref 0x06 +#define PP_DW_OP_plus 0x22 +#define PP_DW_OP_plus_uconst 0x23 + enum dwarf_operation { DW_OP_addr = 0x03, @@ -3288,35 +3300,176 @@ __ASM_GLOBAL_FUNC( signal_exit_thread, __ASM_CFI(".cfi_rel_offset %r15,8\n\t") "call *%rsi" ) + +/*********************************************************************** + * CFI Utility definitions + * + * These utility definitions help encode CFI unwind information (for consumption + * in gdb and similar debuggers), improving the accuracy of backtraces. + */ + +/* DWARF Register ordering for x86_64 */ +#define X86_64_DWARF_RAX 0x00 +#define X86_64_DWARF_RDX 0x01 +#define X86_64_DWARF_RCX 0x02 +#define X86_64_DWARF_RBX 0x03 +#define X86_64_DWARF_RSI 0x04 +#define X86_64_DWARF_RDI 0x05 +#define X86_64_DWARF_RBP 0x06 +#define X86_64_DWARF_RSP 0x07 +#define X86_64_DWARF_R8 0x08 +#define X86_64_DWARF_R9 0x09 +#define X86_64_DWARF_R10 0x0a +#define X86_64_DWARF_R11 0x0b +#define X86_64_DWARF_R12 0x0c +#define X86_64_DWARF_R13 0x0d +#define X86_64_DWARF_R14 0x0e +#define X86_64_DWARF_R15 0x0f +#define X86_64_DWARF_RIP 0x10 + +/* __ASM_REG_IS_DEREF_REF_OFFSET(REG_SAVE, REG, OFFSET) + * + * Declare that the register with DWARF register number `REG` is + * saved at offset `OFFSET` from the register with DWARF register + * number `REG_SAVE`. I.e.: + * + * REG (in previous frame) = *(%REG_SAVE + OFFSET) + */ +#define _STR(R) #R +#define __ASM_REG_IS_DEREF_REF_OFFSET(REG_SAVE, REG, OFFSET) \ + ".cfi_escape " #PP_DW_CFA_expression", " \ + _STR(REG) "," /* The register being saved */ \ + " 0x02," /* 2 bytes follow */ \ + #PP_DW_OP_breg_base " + " _STR(REG_SAVE) ", " #OFFSET ";\n\t" + +/* __ASM_REG_IS_DEREF_REF_OFFSET2(REG_SAVE, REG, OFFSET1, OFFSET2) + * + * Like __ASM_REG_IS_DEREF_REF_OFFSET, expect for offsets of more than + * 7 bits. Takes an SLEB128 encoded offset as two bytes. Thus to e.g. + * encode an offset of 0x70, convert to SLEB128 first: + * + * HEX: 0x70 + * BINARY: 01110000 + * SLEB128: 11110000 00000000 + * |||||||| |||||||| + * |||||||| \------- High bits + * |\------ Low bits + * \- Continuation Bit + * + * SLEB128: 0xf0 0x00 + */ +#define __ASM_REG_IS_DEREF_REF_OFFSET2(REG_SAVE, REG, OFFSET1, OFFSET2) \ + ".cfi_escape " #PP_DW_CFA_expression", " \ + _STR(REG) "," /* The register being saved */ \ + " 0x03," /* 3 bytes follow */ \ + #PP_DW_OP_breg_base " + " _STR(REG_SAVE) ", " #OFFSET1 ", " #OFFSET2 ";\n\t" + +/* __ASM_REG_IS_DEREF_REF_OFFSET_MINUS(REG_SAVE, REG, OFFSET, OFFSET_SUB) + * + * Like __ASM_REG_IS_DEREF_REF_OFFSET, except encodes that the saved + * register value is at `*(%REG_SAVE + OFFSET - OFFSET_SUB). + */ +#define __ASM_REG_IS_DEREF_REF_OFFSET_MINUS(REG_SAVE, REG, OFFSET, OFFSET_SUB) \ + ".cfi_escape " #PP_DW_CFA_expression", " \ + _STR(REG) "," /* The register being saved */ \ + " 0x05," /* 5 bytes follow */ \ + #PP_DW_OP_breg_base " + " _STR(REG_SAVE) ", " #OFFSET "," \ + #PP_DW_OP_const1u ", " #OFFSET_SUB "," #PP_DW_OP_minus ";\n\t" + +/* __ASM_CFA_AT_REG_OFFSET(REG_SAVE, OFFSET) + * + * Declares the CFA of set frame to be stored at *(REG_SAVE + OFFSET). + * Note that the CFA is ordinarily the same as the stack pointer at the end + * of the previous frame, but these are technically separate concepts. + */ +#define __ASM_CFA_AT_REG_OFFSET(REG_SAVE, OFFSET) \ + ".cfi_escape " #PP_DW_CFA_def_cfa_expression "," \ + " 0x03," /* 3 bytes follow */ \ + #PP_DW_OP_breg_base " + " _STR(REG_SAVE) ", " #OFFSET ", " \ + #PP_DW_OP_deref ";\n\t" + +/* __ASM_CFA_AT_REG_OFFSET2(REG_SAVE, OFFSET_HIGH, OFFSET_LOW) + * + * Like __ASM_CFA_AT_REG_OFFSET, except used for larger offsets. `OFFSET_LOW` encodes + * the low 7 bits of the offset. `OFFSET_HIGH` the next 7 bits. + */ +#define __ASM_CFA_AT_REG_OFFSET2(REG_SAVE, OFFSET_HIGH, OFFSET_LOW) \ + ".cfi_escape " DW_CFA_def_cfa_expression "," \ + " 0x04," /* 4 bytes follow */ \ + #PP_DW_OP_breg_base " + " _STR(REG_SAVE) ", " #OFFSET_LOW " | 0x80 , " #OFFSET_HIGH ", " \ + #PP_DW_OP_deref ";\n\t" + +#define __ASM_REG_IS_DEREF_RCX_OFFSET(REG, OFFSET) \ + __ASM_REG_IS_DEREF_REF_OFFSET(X86_64_DWARF_RCX, REG, OFFSET) +#define __ASM_REG_IS_DEREF_RCX_OFFSET2(REG, OFFSET_HIGH, OFFSET_LOW) \ + __ASM_REG_IS_DEREF_REF_OFFSET2(X86_64_DWARF_RCX, REG, OFFSET_LOW | 0x80, OFFSET_HIGH) + +/* __ASM_REGSAVE_AT_DWARF_REG_MINUS(REG_SAVE, OFFSET_SUB) + * + * Declares that a `struct syscall_frame` containing the previous frame's registers may + * be found at `*(struct syscall_frame*)(%REG_SAVE - OFFSET_SUB)` and declares both the + * CFA and saved registers may be found in the corresponding offset. + */ +#define __ASM_REGSAVE_AT_DWARF_REG_MINUS(REG_SAVE, OFFSET_SUB) \ + /* N.B.: First argument is SLEB128 encoded, so move the high bit over \ + to the subtraction */ \ + __ASM_REG_IS_DEREF_REF_OFFSET_MINUS(REG_SAVE, X86_64_DWARF_RIP, 0x00, OFFSET_SUB - 0x70) \ + __ASM_REG_IS_DEREF_REF_OFFSET_MINUS(REG_SAVE, X86_64_DWARF_RAX, 0x00, OFFSET_SUB) \ + __ASM_REG_IS_DEREF_REF_OFFSET_MINUS(REG_SAVE, X86_64_DWARF_RBX, 0x08, OFFSET_SUB) \ + __ASM_REG_IS_DEREF_REF_OFFSET_MINUS(REG_SAVE, X86_64_DWARF_RDX, 0x18, OFFSET_SUB) \ + __ASM_REG_IS_DEREF_REF_OFFSET_MINUS(REG_SAVE, X86_64_DWARF_RSI, 0x20, OFFSET_SUB) \ + __ASM_REG_IS_DEREF_REF_OFFSET_MINUS(REG_SAVE, X86_64_DWARF_RDI, 0x28, OFFSET_SUB) \ + __ASM_REG_IS_DEREF_REF_OFFSET_MINUS(REG_SAVE, X86_64_DWARF_R12, 0x00, OFFSET_SUB - 0x50) \ + __ASM_REG_IS_DEREF_REF_OFFSET_MINUS(REG_SAVE, X86_64_DWARF_R14, 0x10, OFFSET_SUB - 0x50) \ + __ASM_REG_IS_DEREF_REF_OFFSET_MINUS(REG_SAVE, X86_64_DWARF_RSP, 0x08, OFFSET_SUB - 0x80) \ + /* -0x10 in 7bit 2's complement */ \ + __ASM_CFA_AT_REG_OFFSET(REG_SAVE, 0x70) \ + __ASM_REG_IS_DEREF_REF_OFFSET_MINUS(REG_SAVE, X86_64_DWARF_RBP, 0x18, OFFSET_SUB - 0x80) + /*********************************************************************** * __wine_syscall_dispatcher */ __ASM_GLOBAL_FUNC( __wine_syscall_dispatcher, "movq %gs:0x30,%rcx\n\t" + __ASM_CFI(".cfi_undefined rcx\n\t") "movq 0x328(%rcx),%rcx\n\t" /* amd64_thread_data()->syscall_frame */ "popq 0x70(%rcx)\n\t" /* frame->rip */ + __ASM_CFI(".cfi_adjust_cfa_offset -8\n\t") + __ASM_REG_IS_DEREF_RCX_OFFSET2(X86_64_DWARF_RIP, 0x00, 0x70) "pushfq\n\t" + __ASM_CFI(".cfi_adjust_cfa_offset 8\n\t") "popq 0x80(%rcx)\n\t" + __ASM_CFI(".cfi_adjust_cfa_offset -8\n\t") "movl $0,0x94(%rcx)\n\t" /* frame->restore_flags */ ".globl " __ASM_NAME("__wine_syscall_dispatcher_prolog_end") "\n" __ASM_NAME("__wine_syscall_dispatcher_prolog_end") ":\n\t" "movq %rax,0x00(%rcx)\n\t" + __ASM_REG_IS_DEREF_RCX_OFFSET(X86_64_DWARF_RAX, 0x00) "movq %rbx,0x08(%rcx)\n\t" + __ASM_REG_IS_DEREF_RCX_OFFSET(X86_64_DWARF_RBX, 0x08) "movq %rdx,0x18(%rcx)\n\t" + __ASM_REG_IS_DEREF_RCX_OFFSET(X86_64_DWARF_RDX, 0x18) "movq %rsi,0x20(%rcx)\n\t" + __ASM_REG_IS_DEREF_RCX_OFFSET(X86_64_DWARF_RSI, 0x20) "movq %rdi,0x28(%rcx)\n\t" + __ASM_REG_IS_DEREF_RCX_OFFSET(X86_64_DWARF_RDI, 0x28) "movq %r12,0x50(%rcx)\n\t" + __ASM_REG_IS_DEREF_RCX_OFFSET2(X86_64_DWARF_R12, 0x00, 0x50) "movq %r13,0x58(%rcx)\n\t" "movq %r14,0x60(%rcx)\n\t" + __ASM_REG_IS_DEREF_RCX_OFFSET2(X86_64_DWARF_R14, 0x00, 0x60) "movq %r15,0x68(%rcx)\n\t" "movw %cs,0x78(%rcx)\n\t" "movw %ds,0x7a(%rcx)\n\t" "movw %es,0x7c(%rcx)\n\t" "movw %fs,0x7e(%rcx)\n\t" "movq %rsp,0x88(%rcx)\n\t" + __ASM_REG_IS_DEREF_RCX_OFFSET2(X86_64_DWARF_RSP, 0x01, 0x08) + __ASM_CFA_AT_REG_OFFSET2(X86_64_DWARF_RCX, 0x01, 0x08) "movw %ss,0x90(%rcx)\n\t" "movw %gs,0x92(%rcx)\n\t" "movq %rbp,0x98(%rcx)\n\t" + __ASM_REG_IS_DEREF_RCX_OFFSET2(X86_64_DWARF_RBP, 0x01, 0x18) /* Legends of Runeterra hooks the first system call return instruction, and * depends on us returning to it. Adjust the return address accordingly. */ "subq $0xb,0x70(%rcx)\n\t" @@ -3341,6 +3494,8 @@ __ASM_GLOBAL_FUNC( __wine_syscall_dispatcher, "jmp 3f\n" "2:\tfxsave64 0xc0(%rcx)\n" "3:\tleaq 0x98(%rcx),%rbp\n\t" + __ASM_CFI(".cfi_remember_state\n\t") + __ASM_REGSAVE_AT_DWARF_REG_MINUS(X86_64_DWARF_RBP, 0x98) #ifdef __linux__ "testl $12,%r14d\n\t" /* SYSCALL_HAVE_PTHREAD_TEB | SYSCALL_HAVE_WRFSGSBASE */ "jz 2f\n\t" @@ -3402,35 +3557,60 @@ __ASM_GLOBAL_FUNC( __wine_syscall_dispatcher, "jmp 4f\n" "3:\tfxrstor64 0xc0(%rcx)\n" "4:\tmovq 0x98(%rcx),%rbp\n\t" + __ASM_CFI(".cfi_restore_state\n\t") "movq 0x68(%rcx),%r15\n\t" + __ASM_CFI(".cfi_same_value r15\n\t") "movq 0x60(%rcx),%r14\n\t" + __ASM_CFI(".cfi_same_value r14\n\t") "movq 0x58(%rcx),%r13\n\t" + __ASM_CFI(".cfi_same_value r13\n\t") "movq 0x50(%rcx),%r12\n\t" + __ASM_CFI(".cfi_same_value r12\n\t") "movq 0x28(%rcx),%rdi\n\t" + __ASM_CFI(".cfi_same_value rdi\n\t") "movq 0x20(%rcx),%rsi\n\t" + __ASM_CFI(".cfi_same_value rsi\n\t") "movq 0x08(%rcx),%rbx\n\t" + __ASM_CFI(".cfi_same_value rbx\n\t") "testl $0x3,%edx\n\t" /* CONTEXT_CONTROL | CONTEXT_INTEGER */ "jnz 1f\n\t" + __ASM_CFI(".cfi_remember_state\n\t") "movq 0x80(%rcx),%r11\n\t" /* frame->eflags */ + __ASM_CFI(".cfi_same_value r11\n\t") "pushq %r11\n\t" "popfq\n\t" "movq 0x88(%rcx),%rsp\n\t" + __ASM_CFI(".cfi_same_value rsp\n\t") "movq 0x70(%rcx),%rcx\n\t" /* frame->rip */ + __ASM_CFI(".cfi_register rip, rcx\n\t") "jmpq *%rcx\n\t" "1:\tleaq 0x70(%rcx),%rsp\n\t" + __ASM_CFI(".cfi_restore_state\n\t") + __ASM_CFI(".cfi_remember_state\n\t") "testl $0x2,%edx\n\t" /* CONTEXT_INTEGER */ "jnz 1f\n\t" "movq 0x10(%rsp),%r11\n\t" /* frame->eflags */ + __ASM_CFI(".cfi_same_value r11\n\t") "movq (%rsp),%rcx\n\t" /* frame->rip */ + __ASM_CFI(".cfi_register rip, rcx\n\t") "iretq\n" "1:\tmovq 0x00(%rcx),%rax\n\t" + __ASM_CFI(".cfi_restore_state\n\t") + __ASM_CFI(".cfi_same_value rax\n\t") "movq 0x18(%rcx),%rdx\n\t" + __ASM_CFI(".cfi_same_value rdx\n\t") "movq 0x30(%rcx),%r8\n\t" + __ASM_CFI(".cfi_same_value r8\n\t") "movq 0x38(%rcx),%r9\n\t" + __ASM_CFI(".cfi_same_value r9\n\t") "movq 0x40(%rcx),%r10\n\t" + __ASM_CFI(".cfi_same_value r10\n\t") "movq 0x48(%rcx),%r11\n\t" + __ASM_CFI(".cfi_same_value r11\n\t") "movq 0x10(%rcx),%rcx\n" + __ASM_REG_IS_DEREF_REF_OFFSET(X86_64_DWARF_RSP, X86_64_DWARF_RIP, 0) "iretq\n" + __ASM_REGSAVE_AT_DWARF_REG_MINUS(X86_64_DWARF_RBP, 0x98) "5:\tmovl $0xc000000d,%edx\n\t" /* STATUS_INVALID_PARAMETER */ "movq %rsp,%rcx\n\t" ".globl " __ASM_NAME("__wine_syscall_dispatcher_return") "\n" -- 2.25.1

2 1

Re: [PATCH v4 01/11] winmm/tests: Add tests for visibility of video window.
by Marvin 28 Jul '22

28 Jul '22

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=120073 Your paranoid android. === w7u_adm (32 bit report) === winmm: midi.c:1039: Test failed: bad message 1e/0 from midiStreamOut, expect 3c9/22f940 midi.c:1048: Test failed: bad message 3c9/22f940 from midiStreamClose, expect 3c8/0 === w7u_el (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

1 0

Re: [PATCH v3 2/2] ddraw/tests: Add some video memory accounting tests.
by Marvin 28 Jul '22

28 Jul '22

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=120071 Your paranoid android. === w8adm (32 bit report) === ddraw: ddraw7.c:18888: Test failed: Got unexpected color 0x0000ff00. === w864 (32 bit report) === ddraw: ddraw7.c:18888: Test failed: Got unexpected color 0x0000ff00. === w1064_tsign (32 bit report) === ddraw: ddraw7.c:18888: Test failed: Got unexpected color 0x00000040. === debian11 (32 bit Chinese:China report) === Report validation errors: ddraw1: Timeout === debian11 (build log) === WineRunWineTest.pl:error: The task timed out

1 0

Re: [PATCH 3/3] mshtml: Implement "text" type response for XMLHttpRequest.
by Marvin 28 Jul '22

28 Jul '22

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=120063 Your paranoid android. === 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 === w10pro64_zh_CN (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

Access to graphics memory mappings on upcoming WOW64 implementation
by Derek Lesho 28 Jul '22

28 Jul '22

Hi All, In the wake of the new WOW64 implementation (recent explanation [1]), there has been discussion in informal channels about how to we are going to handle pointers to mapped graphics resource memory which we receive from the graphics API, as the possibility exists that it will fall outside of the 32-bit address space. Over time, a few creative solutions have been proposed and discussed, with a common theme being that we need changes in either the kernel or the graphics drivers to do this properly. As we already know the requirements for a solution to this problem, I think it would be responsible to hash this out now and then work with the relevant project maintainers earlier as to avoid blocking work on the wine side too long and to possibly allow more users to test the new path earlier. The solutions which I've seen laid out so far: - Use the mremap(2) interface, allowing us to duplicate the mapping we receive into the 32-bit address space. This solution would match what is already done for Crossover Mac's 32on64 support using Mac's mach_vm_remap functionality [2]. However, right now it is not possible to use the MREMAP_DONTUNMAP flag with mappings that aren't private and anonymous, which rules out there use on mapped FDs from libdrm. Due to this, a kernel change would be necessary. Pro: A uniform solution across all APIs, which could help in the future with any unforeseen need to access host-allocated memory in 32-bit windows code. Cons: Requires a kernel change, which of all the options may take the longest to get up-streamed and in the hands of users. - Work with Khronos to introduce extensions into the relevant APIs enabling us to tell drivers where in the address space we want resources mapped. Pro: Wouldn't require going around the backs of the driver, resulting in a more hardened solution. (Out there, but what if a creative driver returns a mapping without read or write permission and handles accesses through a page fault handler?) Cons: The extension would have to be implemented by each individual vendor for every relevant API. This would implicitly drop support for those with cards whose graphics drivers are no longer being updated. - Hook the driver's mmap call when we invoke memory mappings function, overriding the address to something in the 32-bit address space. Pro: Unlike the other solutions, this wouldn't require any changes to other projects, and shares the advantage of the first solution. Cons: Susceptible to breakage if the driver uses their own mapping mechanism separate from mmap. (Custom IOCTL, CPU driver returning something from the heap) 1: https://www.winehq.org/pipermail/wine-devel/2022-April/213677.html 2: https://www.codeweavers.com/crossover/source - see function `remap_memory` in `wine/dlls/winemac.drv/opengl.c`

10 15

Re: [PATCH 2/3] mshtml: Implement responseType prop for XMLHttpRequest.
by Marvin 28 Jul '22

28 Jul '22

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=120062 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:350: Test failed: expected Exec_SETTITLE htmldoc.c:2859: Test failed: unexpected call Exec_SETTITLE

1 0

Re: [PATCH 11/11] mciqtz32: Show the default video window when switching from another one.
by Marvin 28 Jul '22

28 Jul '22

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=120094 Your paranoid android. === w7u_2qxl (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (100,100)-(236,162), got (100,100)-(232,162) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (175,175)-(311,237), got (175,175)-(307,237) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (125,125)-(261,187), got (125,125)-(257,187) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w7u_adm (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (100,100)-(236,162), got (100,100)-(232,162) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (175,175)-(311,237), got (175,175)-(307,237) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (75,75)-(211,137), got (75,75)-(207,137) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w7u_el (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (75,75)-(211,137), got (75,75)-(207,137) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w8 (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w8adm (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w864 (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w864 (64 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === debian11 (32 bit report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit Arabic:Morocco report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit German report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit French report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit Hebrew:Israel report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit Hindi:India report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit Japanese:Japan report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit Chinese:China report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit WoW report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (64 bit WoW report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12)

1 0

Re: [PATCH 10/11] mciqtz32: Hide the default video window when switching to another one.
by Marvin 28 Jul '22

28 Jul '22

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=120093 Your paranoid android. === w7u_2qxl (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (100,100)-(236,162), got (100,100)-(232,162) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w7u_adm (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (100,100)-(236,162), got (100,100)-(232,162) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (175,175)-(311,237), got (175,175)-(307,237) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (75,75)-(211,137), got (75,75)-(207,137) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w7u_el (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (75,75)-(211,137), got (75,75)-(207,137) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w8 (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w8adm (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (26,26)-(162,89), got (26,26)-(166,89) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (104,104)-(240,167), got (104,104)-(244,167) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w864 (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w864 (64 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === debian11 (32 bit report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit Arabic:Morocco report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit German report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit French report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit Hebrew:Israel report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit Hindi:India report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit Japanese:Japan report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit Chinese:China report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit WoW report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (64 bit WoW report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12)

1 0

Re: [PATCH 09/11] mciqtz32: Reset the video size when switching video destination.
by Marvin 28 Jul '22

28 Jul '22

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=120092 Your paranoid android. === w7u_2qxl (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (100,100)-(236,162), got (100,100)-(232,162) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (175,175)-(311,237), got (175,175)-(307,237) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (125,125)-(261,187), got (125,125)-(257,187) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w7u_adm (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (100,100)-(236,162), got (100,100)-(232,162) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (175,175)-(311,237), got (175,175)-(307,237) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (75,75)-(211,137), got (75,75)-(207,137) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w7u_el (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (75,75)-(211,137), got (75,75)-(207,137) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w8 (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w8adm (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (26,26)-(162,89), got (26,26)-(166,89) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (104,104)-(240,167), got (104,104)-(244,167) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w864 (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w864 (64 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === debian11 (32 bit report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit Arabic:Morocco report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit German report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit French report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit Hebrew:Israel report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit Hindi:India report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit Japanese:Japan report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit Chinese:China report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit WoW report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (64 bit WoW report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12)

1 0

Re: [PATCH 08/11] mciqtz32: Correct initial video window dimensions.
by Marvin 28 Jul '22

28 Jul '22

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=120091 Your paranoid android. === w7u_2qxl (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (100,100)-(236,162), got (100,100)-(232,162) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (175,175)-(311,237), got (175,175)-(307,237) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (125,125)-(261,187), got (125,125)-(257,187) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w7u_adm (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (100,100)-(236,162), got (100,100)-(232,162) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (175,175)-(311,237), got (175,175)-(307,237) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (75,75)-(211,137), got (75,75)-(207,137) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w7u_el (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (75,75)-(211,137), got (75,75)-(207,137) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w8 (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w8adm (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (26,26)-(162,89), got (26,26)-(166,89) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (104,104)-(240,167), got (104,104)-(244,167) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w864 (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w864 (64 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64)

1 0

Re: [PATCH 07/11] mciqtz32: Fix MCI_DGV_WHERE_WINDOW behavior.
by Marvin 28 Jul '22

28 Jul '22

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=120090 Your paranoid android. === w7u_2qxl (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (100,100)-(236,162), got (100,100)-(232,162) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w7u_adm (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (100,100)-(236,162), got (100,100)-(232,162) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (175,175)-(311,237), got (175,175)-(307,237) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (75,75)-(211,137), got (75,75)-(207,137) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w7u_el (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (75,75)-(211,137), got (75,75)-(207,137) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w8 (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w8adm (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w864 (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w864 (64 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64)

1 0

Re: [PATCH 06/11] mciqtz32: Correct video window behavior by creating default window.
by Marvin 28 Jul '22

28 Jul '22

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=120089 Your paranoid android. === w7u_2qxl (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (100,100)-(236,162), got (100,100)-(232,162) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w7u_adm (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (100,100)-(236,162), got (100,100)-(232,162) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (175,175)-(311,237), got (175,175)-(307,237) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (75,75)-(211,137), got (75,75)-(207,137) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w7u_el (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (75,75)-(211,137), got (75,75)-(207,137) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w8 (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w8adm (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w864 (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w864 (64 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64)

1 0

Re: [PATCH 05/11] winmm/tests: Add tests for destination of video window.
by Marvin 28 Jul '22

28 Jul '22

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=120088 Your paranoid android. === w7u_2qxl (32 bit report) === winmm: mci.c:1606: Test failed: 0: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1606: Test failed: 1: window rectangle doesn't match, expected (100,100)-(236,162), got (100,100)-(232,162) mci.c:1606: Test failed: 2: window rectangle doesn't match, expected (175,175)-(311,237), got (175,175)-(307,237) mci.c:1606: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1606: Test failed: 4: window rectangle doesn't match, expected (125,125)-(261,187), got (125,125)-(257,187) mci.c:1606: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w7u_adm (32 bit report) === winmm: mci.c:1606: Test failed: 0: window rectangle doesn't match, expected (100,100)-(236,162), got (100,100)-(232,162) mci.c:1606: Test failed: 1: window rectangle doesn't match, expected (175,175)-(311,237), got (175,175)-(307,237) mci.c:1606: Test failed: 2: window rectangle doesn't match, expected (75,75)-(211,137), got (75,75)-(207,137) mci.c:1606: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1606: Test failed: 4: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1606: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w7u_el (32 bit report) === winmm: mci.c:1606: Test failed: 0: window rectangle doesn't match, expected (75,75)-(211,137), got (75,75)-(207,137) mci.c:1606: Test failed: 1: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1606: Test failed: 2: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1606: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1606: Test failed: 4: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1606: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w8 (32 bit report) === winmm: mci.c:1606: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1606: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1606: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1606: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1606: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1606: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w8adm (32 bit report) === winmm: mci.c:1606: Test failed: 0: window rectangle doesn't match, expected (26,26)-(162,89), got (26,26)-(166,89) mci.c:1606: Test failed: 1: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1606: Test failed: 2: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1606: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1606: Test failed: 4: window rectangle doesn't match, expected (104,104)-(240,167), got (104,104)-(244,167) mci.c:1606: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w864 (32 bit report) === winmm: mci.c:1606: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1606: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1606: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1606: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1606: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1606: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w864 (64 bit report) === winmm: mci.c:1606: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1606: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1606: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1606: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1606: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1606: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === debian11 (32 bit Arabic:Morocco report) === winmm: mci.c:1612: Test failed: 2: window command result doesn't match, expected (0,0)-(112,51), got (0,10)-(112,51) === debian11 (64 bit WoW report) === winmm: mci.c:1612: Test failed: 0: window command result doesn't match, expected (0,0)-(112,51), got (0,10)-(112,51)

1 0

Re: [PATCH 04/11] winmm/tests: Add tests for dimensions of video window.
by Marvin 28 Jul '22

28 Jul '22

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=120087 Your paranoid android. === w7u_2qxl (32 bit report) === winmm: mci.c:1601: Test failed: 0: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1601: Test failed: 1: window rectangle doesn't match, expected (100,100)-(236,162), got (100,100)-(232,162) mci.c:1601: Test failed: 2: window rectangle doesn't match, expected (175,175)-(311,237), got (175,175)-(307,237) mci.c:1601: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1601: Test failed: 4: window rectangle doesn't match, expected (125,125)-(261,187), got (125,125)-(257,187) mci.c:1601: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w7u_adm (32 bit report) === winmm: mci.c:1601: Test failed: 0: window rectangle doesn't match, expected (100,100)-(236,162), got (100,100)-(232,162) mci.c:1601: Test failed: 1: window rectangle doesn't match, expected (175,175)-(311,237), got (175,175)-(307,237) mci.c:1601: Test failed: 2: window rectangle doesn't match, expected (75,75)-(211,137), got (75,75)-(207,137) mci.c:1601: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1601: Test failed: 4: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1601: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w7u_el (32 bit report) === winmm: mci.c:1601: Test failed: 0: window rectangle doesn't match, expected (75,75)-(211,137), got (75,75)-(207,137) mci.c:1601: Test failed: 1: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1601: Test failed: 2: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1601: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1601: Test failed: 4: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1601: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w8 (32 bit report) === winmm: mci.c:1601: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1601: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1601: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1601: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1601: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1601: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w8adm (32 bit report) === winmm: mci.c:1601: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1601: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1601: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1601: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1601: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1601: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w864 (32 bit report) === winmm: mci.c:1601: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1601: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1601: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1601: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1601: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1601: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w864 (64 bit report) === winmm: mci.c:1601: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1601: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1601: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1601: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1601: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1601: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64)

1 0

Re: [PATCH v4 11/11] mciqtz32: Show the default video window when switching from another one.
by Marvin 28 Jul '22

28 Jul '22

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=120083 Your paranoid android. === w7u_2qxl (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (100,100)-(236,162), got (100,100)-(232,162) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w7u_adm (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (100,100)-(236,162), got (100,100)-(232,162) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (175,175)-(311,237), got (175,175)-(307,237) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (75,75)-(211,137), got (75,75)-(207,137) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w7u_el (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (75,75)-(211,137), got (75,75)-(207,137) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w8 (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w8adm (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w864 (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w864 (64 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === debian11 (32 bit report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit Arabic:Morocco report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit German report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit French report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit Hebrew:Israel report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit Hindi:India report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit Japanese:Japan report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit Chinese:China report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit WoW report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (64 bit WoW report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12)

1 0

Re: [PATCH v4 10/11] mciqtz32: Hide the default video window when switching to another one.
by Marvin 28 Jul '22

28 Jul '22

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=120082 Your paranoid android. === w7u_2qxl (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (100,100)-(236,162), got (100,100)-(232,162) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w7u_adm (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (100,100)-(236,162), got (100,100)-(232,162) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (175,175)-(311,237), got (175,175)-(307,237) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (75,75)-(211,137), got (75,75)-(207,137) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w7u_el (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (75,75)-(211,137), got (75,75)-(207,137) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w8 (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w8adm (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w864 (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w864 (64 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === debian11 (32 bit report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit Arabic:Morocco report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit German report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit French report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit Hebrew:Israel report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit Hindi:India report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit Japanese:Japan report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit Chinese:China report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit WoW report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (64 bit WoW report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12)

1 0

Re: [PATCH v4 09/11] mciqtz32: Reset the video size when switching video destination.
by Marvin 28 Jul '22

28 Jul '22

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=120081 Your paranoid android. === w7u_2qxl (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (100,100)-(236,162), got (100,100)-(232,162) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (175,175)-(311,237), got (175,175)-(307,237) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (125,125)-(261,187), got (125,125)-(257,187) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w7u_adm (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (100,100)-(236,162), got (100,100)-(232,162) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (175,175)-(311,237), got (175,175)-(307,237) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (75,75)-(211,137), got (75,75)-(207,137) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w7u_el (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (75,75)-(211,137), got (75,75)-(207,137) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w8 (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w8adm (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (26,26)-(162,89), got (26,26)-(166,89) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (104,104)-(240,167), got (104,104)-(244,167) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w864 (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w864 (64 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === debian11 (32 bit report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit Arabic:Morocco report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit German report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit French report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit Hebrew:Israel report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit Hindi:India report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit Japanese:Japan report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit Chinese:China report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (32 bit WoW report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12) === debian11 (64 bit WoW report) === winmm: mci.c:1657: Test failed: 0: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 1: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 2: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 3: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 4: got (0,0)-(32,24), expected (0,0)-(64,12) mci.c:1657: Test failed: 5: got (0,0)-(32,24), expected (0,0)-(64,12)

1 0

Re: [PATCH v4 08/11] mciqtz32: Correct initial video window dimensions.
by Marvin 28 Jul '22

28 Jul '22

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=120080 Your paranoid android. === w7u_2qxl (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (100,100)-(236,162), got (100,100)-(232,162) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w7u_adm (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (100,100)-(236,162), got (100,100)-(232,162) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (175,175)-(311,237), got (175,175)-(307,237) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (75,75)-(211,137), got (75,75)-(207,137) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w7u_el (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (75,75)-(211,137), got (75,75)-(207,137) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w8 (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w8adm (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (26,26)-(162,89), got (26,26)-(166,89) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (104,104)-(240,167), got (104,104)-(244,167) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w864 (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w864 (64 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64)

1 0

Re: [PATCH v4 07/11] mciqtz32: Fix MCI_DGV_WHERE_WINDOW behavior.
by Marvin 28 Jul '22

28 Jul '22

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=120079 Your paranoid android. === w7u_2qxl (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (100,100)-(236,162), got (100,100)-(232,162) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w7u_adm (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (100,100)-(236,162), got (100,100)-(232,162) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (175,175)-(311,237), got (175,175)-(307,237) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (75,75)-(211,137), got (75,75)-(207,137) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w7u_el (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (75,75)-(211,137), got (75,75)-(207,137) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w8 (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w8adm (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (26,26)-(162,89), got (26,26)-(166,89) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (104,104)-(240,167), got (104,104)-(244,167) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w864 (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w864 (64 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64)

1 0

Re: [PATCH v4 06/11] mciqtz32: Correct video window behavior by creating default window.
by Marvin 28 Jul '22

28 Jul '22

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=120078 Your paranoid android. === w7u_2qxl (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (100,100)-(236,162), got (100,100)-(232,162) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (175,175)-(311,237), got (175,175)-(307,237) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (125,125)-(261,187), got (125,125)-(257,187) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w7u_adm (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (100,100)-(236,162), got (100,100)-(232,162) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (175,175)-(311,237), got (175,175)-(307,237) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (75,75)-(211,137), got (75,75)-(207,137) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w7u_el (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (75,75)-(211,137), got (75,75)-(207,137) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w8 (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w8adm (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w864 (32 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w864 (64 bit report) === winmm: mci.c:1600: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1600: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1600: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1600: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1600: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1600: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64)

1 0

Re: [PATCH v4 05/11] winmm/tests: Add tests for destination of video window.
by Marvin 28 Jul '22

28 Jul '22

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=120077 Your paranoid android. === w7u_2qxl (32 bit report) === winmm: mci.c:1606: Test failed: 0: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1606: Test failed: 1: window rectangle doesn't match, expected (100,100)-(236,162), got (100,100)-(232,162) mci.c:1606: Test failed: 2: window rectangle doesn't match, expected (175,175)-(311,237), got (175,175)-(307,237) mci.c:1606: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1606: Test failed: 4: window rectangle doesn't match, expected (125,125)-(261,187), got (125,125)-(257,187) mci.c:1606: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w7u_adm (32 bit report) === winmm: mci.c:1606: Test failed: 0: window rectangle doesn't match, expected (100,100)-(236,162), got (100,100)-(232,162) mci.c:1606: Test failed: 1: window rectangle doesn't match, expected (175,175)-(311,237), got (175,175)-(307,237) mci.c:1606: Test failed: 2: window rectangle doesn't match, expected (75,75)-(211,137), got (75,75)-(207,137) mci.c:1606: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1606: Test failed: 4: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1606: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w7u_el (32 bit report) === winmm: mci.c:1606: Test failed: 0: window rectangle doesn't match, expected (75,75)-(211,137), got (75,75)-(207,137) mci.c:1606: Test failed: 1: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1606: Test failed: 2: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1606: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1606: Test failed: 4: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1606: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w8 (32 bit report) === winmm: mci.c:1606: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1606: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1606: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1606: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1606: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1606: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w8adm (32 bit report) === winmm: mci.c:1606: Test failed: 0: window rectangle doesn't match, expected (26,26)-(162,89), got (26,26)-(166,89) mci.c:1606: Test failed: 1: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1606: Test failed: 2: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1606: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1606: Test failed: 4: window rectangle doesn't match, expected (104,104)-(240,167), got (104,104)-(244,167) mci.c:1606: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w864 (32 bit report) === winmm: mci.c:1606: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1606: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1606: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1606: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1606: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1606: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w864 (64 bit report) === winmm: mci.c:1606: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1606: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1606: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1606: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1606: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1606: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64)

1 0

Re: [PATCH v4 04/11] winmm/tests: Add tests for dimensions of video window.
by Marvin 28 Jul '22

28 Jul '22

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=120076 Your paranoid android. === w7u_2qxl (32 bit report) === winmm: mci.c:1601: Test failed: 0: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1601: Test failed: 1: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1601: Test failed: 2: window rectangle doesn't match, expected (100,100)-(236,162), got (100,100)-(232,162) mci.c:1601: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1601: Test failed: 4: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1601: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w7u_adm (32 bit report) === winmm: mci.c:1601: Test failed: 0: window rectangle doesn't match, expected (100,100)-(236,162), got (100,100)-(232,162) mci.c:1601: Test failed: 1: window rectangle doesn't match, expected (175,175)-(311,237), got (175,175)-(307,237) mci.c:1601: Test failed: 2: window rectangle doesn't match, expected (75,75)-(211,137), got (75,75)-(207,137) mci.c:1601: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1601: Test failed: 4: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1601: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w7u_el (32 bit report) === winmm: mci.c:1601: Test failed: 0: window rectangle doesn't match, expected (75,75)-(211,137), got (75,75)-(207,137) mci.c:1601: Test failed: 1: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1601: Test failed: 2: window rectangle doesn't match, expected (25,25)-(161,87), got (25,25)-(157,87) mci.c:1601: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,62), got (0,0)-(132,62) mci.c:1601: Test failed: 4: window rectangle doesn't match, expected (150,150)-(286,212), got (150,150)-(282,212) mci.c:1601: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,63), got (1,1)-(133,63) === w8 (32 bit report) === winmm: mci.c:1601: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1601: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1601: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1601: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1601: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1601: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w8adm (32 bit report) === winmm: mci.c:1601: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1601: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1601: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1601: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1601: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1601: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w864 (32 bit report) === winmm: mci.c:1601: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1601: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1601: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1601: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1601: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1601: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64) === w864 (64 bit report) === winmm: mci.c:1601: Test failed: 0: window rectangle doesn't match, expected (156,156)-(292,219), got (156,156)-(296,219) mci.c:1601: Test failed: 1: window rectangle doesn't match, expected (52,52)-(188,115), got (52,52)-(192,115) mci.c:1601: Test failed: 2: window rectangle doesn't match, expected (130,130)-(266,193), got (130,130)-(270,193) mci.c:1601: Test failed: 3: window rectangle doesn't match, expected (0,0)-(136,63), got (0,0)-(140,63) mci.c:1601: Test failed: 4: window rectangle doesn't match, expected (78,78)-(214,141), got (78,78)-(218,141) mci.c:1601: Test failed: 5: window rectangle doesn't match, expected (1,1)-(137,64), got (1,1)-(141,64)

1 0

Re: [PATCH v3 1/2] ddraw: Don't account video memory for sysmem surfaces' draw textures.
by Marvin 28 Jul '22

28 Jul '22

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=120070 Your paranoid android. === debian11 (32 bit Chinese:China report) === Report validation errors: ddraw7: Timeout === debian11 (build log) === WineRunWineTest.pl:error: The task timed out

1 0

[PATCH v2 0/6] MR370: mciqtz32: Simplify video window management by creating default window.
by Akihiro Sagawa (＠sgwaki) 28 Jul '22

28 Jul '22

-- v2: mciqtz32: Update parent window's title instead of the video window's one. mciqtz32: Update parent window's state instead of the video window's one. winmm/tests: Add more window command tests. mciqtz32: Implement MCI_DGV_STATUS_HWND. winmm/tests: Add basic video window tests. mciqtz32: Simplify video window management by creating default window. https://gitlab.winehq.org/wine/wine/-/merge_requests/370

5 12

[PATCH] server: Write terminating '\0' in the strings.
by Dmitry Timoshkov 28 Jul '22

28 Jul '22

I have an application that creates its special registry key using NtCreateKey(parent, "Something\0"), and then expects to be able to open this key with NtOpenKey("Something\0") on start up. Currently this fails because terminating '\0' in the key name doesn't survive saving/loading the registry. parse_strW() helper already supports loading such key names. As the tests show after creating a kernel object with name "Something\0" it's possible to only open it as "Something\0", an attempt opening it as "Something" fails with STATUS_OBJECT_NAME_NOT_FOUND, and vice versa. Signed-off-by: Dmitry Timoshkov <dmitry(a)baikal.ru> --- server/unicode.c | 1 - 1 file changed, 1 deletion(-) diff --git a/server/unicode.c b/server/unicode.c index 86a1217b01f..a146677cf21 100644 --- a/server/unicode.c +++ b/server/unicode.c @@ -219,7 +219,6 @@ int dump_strW( const WCHAR *str, data_size_t len, FILE *f, const char escape[2] } if (*str < 32) /* octal or C escape */ { - if (!*str && len == 1) continue; /* do not output terminating NULL */ if (escapes[*str] != '.') pos += sprintf( pos, "\\%c", escapes[*str] ); else if (len > 1 && str[1] >= '0' && str[1] <= '7') -- 2.37.1

1 0

[PATCH 2/2] ntdll/tests: Add a bunch of tests for creating kernel objects with the names containing '\0'.
by Dmitry Timoshkov 28 Jul '22

28 Jul '22

As the tests show after creating a kernel object with name "wine_test\0" it's possible to only open it as "wine_test\0", an attempt opening it as "wine_test" fails with STATUS_OBJECT_NAME_NOT_FOUND, and vice versa. Also the tests show that "wine\0test" is a valid kernel object name. Signed-off-by: Dmitry Timoshkov <dmitry(a)baikal.ru> --- dlls/ntdll/tests/om.c | 350 +++++++++++++++++++++++++++++++++++++++++- 1 file changed, 349 insertions(+), 1 deletion(-) diff --git a/dlls/ntdll/tests/om.c b/dlls/ntdll/tests/om.c index 7fe0fb59f89..f98a8843d62 100644 --- a/dlls/ntdll/tests/om.c +++ b/dlls/ntdll/tests/om.c @@ -1580,7 +1580,8 @@ static void _test_object_name( unsigned line, HANDLE handle, const WCHAR *expect ok_(__FILE__,line)( status == STATUS_SUCCESS, "NtQueryObject failed %lx\n", status ); ok_(__FILE__,line)( len >= sizeof(OBJECT_NAME_INFORMATION) + str->Length, "unexpected len %lu\n", len ); todo_wine_if (todo) - ok_(__FILE__,line)(compare_unicode_string( str, expected_name ), "wrong name %s\n", debugstr_w( str->Buffer )); + ok_(__FILE__,line)(compare_unicode_string( str, expected_name ), "got %s, expected %s\n", + debugstr_w(str->Buffer), debugstr_w(expected_name)); } static void test_query_object(void) @@ -2722,6 +2723,352 @@ static void test_query_directory(void) pNtClose( dir ); } +#define test_object_name_with_null(a,b) _test_object_name_with_null(__LINE__,a,b) +static void _test_object_name_with_null(unsigned line, HANDLE handle, UNICODE_STRING *expect) +{ + char buffer[1024]; + UNICODE_STRING *str = (UNICODE_STRING *)buffer; + ULONG len = 0; + NTSTATUS status; + + memset(buffer, 0, sizeof(buffer)); + status = pNtQueryObject(handle, ObjectNameInformation, buffer, sizeof(buffer), &len); + ok_(__FILE__,line)(status == STATUS_SUCCESS, "got %08lx\n", status); + ok_(__FILE__,line)(len >= sizeof(OBJECT_NAME_INFORMATION) + str->Length, "got %lu\n", len); + ok_(__FILE__,line)(str->Length == expect->Length, "got %lu, expected %lu\n", str->Length, expect->Length); + ok_(__FILE__,line)(!wcsnicmp(str->Buffer, expect->Buffer, str->Length/sizeof(WCHAR)), "got %s, expected %s\n", + debugstr_w(str->Buffer), debugstr_w(expect->Buffer)); +} + +static void test_null_in_object_name(void) +{ + WCHAR name[256], name3[256], *p, *name_exp, *name3_exp; + HANDLE handle, handle2; + NTSTATUS status; + OBJECT_ATTRIBUTES attr, attr2, attr3; + UNICODE_STRING nameU, name2U, name3U, name2U_exp, name3U_exp; + LARGE_INTEGER size; +#ifndef _WIN64 + BOOL is_wow64 = FALSE; +#endif + + trace("running as %d bit\n", (int)sizeof(void *) * 8); + + swprintf(name, ARRAY_SIZE(name), L"\\Sessions\\%u\\BaseNamedObjects\\wine_test", NtCurrentTeb()->Peb->SessionId); + swprintf(name3, ARRAY_SIZE(name3), L"\\Sessions\\%u\\BaseNamedObjects\\wine_test", NtCurrentTeb()->Peb->SessionId); + p = wcsrchr(name3, '\\'); + p[5] = 0; /* => \\wine\0test */ + + RtlInitUnicodeString(&nameU, name); + InitializeObjectAttributes(&attr, &nameU, 0, 0, NULL); + + name2U = nameU; + name2U.Length += sizeof(WCHAR); /* add terminating \0 to string length */ + InitializeObjectAttributes(&attr2, &name2U, 0, 0, NULL); + + name3U = nameU; + name3U.Buffer = name3; + InitializeObjectAttributes(&attr3, &name3U, 0, 0, NULL); + + status = pNtCreateEvent(&handle, GENERIC_ALL, &attr, NotificationEvent, FALSE); + ok(!status, "got %08lx\n", status); + test_object_name(handle, name, FALSE); + status = pNtOpenEvent(&handle2, GENERIC_ALL, &attr); + ok(!status, "got %08lx\n", status); + test_object_name(handle2, name, FALSE); + pNtClose(handle2); + status = pNtOpenEvent(&handle2, GENERIC_ALL, &attr2); + ok(status == STATUS_OBJECT_NAME_NOT_FOUND, "got %08lx\n", status); + pNtClose(handle); + status = pNtCreateEvent(&handle, GENERIC_ALL, &attr2, NotificationEvent, FALSE); + ok(!status, "got %08lx\n", status); + test_object_name_with_null(handle, &name2U); + status = pNtOpenEvent(&handle2, GENERIC_ALL, &attr2); + ok(!status, "got %08lx\n", status); + test_object_name_with_null(handle2, &name2U); + pNtClose(handle2); + status = pNtOpenEvent(&handle2, GENERIC_ALL, &attr); + ok(status == STATUS_OBJECT_NAME_NOT_FOUND, "got %08lx\n", status); + pNtClose(handle); + status = pNtCreateEvent(&handle, GENERIC_ALL, &attr3, NotificationEvent, FALSE); + ok(!status, "got %08lx\n", status); + test_object_name_with_null(handle, &name3U); + status = pNtOpenEvent(&handle2, GENERIC_ALL, &attr3); + ok(!status, "got %08lx\n", status); + test_object_name_with_null(handle2, &name3U); + pNtClose(handle2); + pNtClose(handle); + + status = pNtCreateDebugObject(&handle, GENERIC_ALL, &attr, 0); + ok(!status, "got %08lx\n", status); + test_object_name(handle, name, FALSE); + pNtClose(handle); + status = pNtCreateDebugObject(&handle, GENERIC_ALL, &attr2, 0); + ok(!status, "got %08lx\n", status); + test_object_name_with_null(handle, &name2U); + pNtClose(handle); + status = pNtCreateDebugObject(&handle, GENERIC_ALL, &attr3, 0); + ok(!status, "got %08lx\n", status); + test_object_name_with_null(handle, &name3U); + pNtClose(handle); + + status = pNtCreateMutant(&handle, GENERIC_ALL, &attr, 0); + ok(!status, "got %08lx\n", status); + test_object_name(handle, name, FALSE); + status = pNtOpenMutant(&handle2, GENERIC_ALL, &attr); + ok(!status, "got %08lx\n", status); + test_object_name(handle2, name, FALSE); + pNtClose(handle2); + status = pNtOpenMutant(&handle2, GENERIC_ALL, &attr2); + ok(status == STATUS_OBJECT_NAME_NOT_FOUND, "got %08lx\n", status); + pNtClose(handle); + status = pNtCreateMutant(&handle, GENERIC_ALL, &attr2, 0); + ok(!status, "got %08lx\n", status); + test_object_name_with_null(handle, &name2U); + status = pNtOpenMutant(&handle2, GENERIC_ALL, &attr2); + ok(!status, "got %08lx\n", status); + test_object_name_with_null(handle2, &name2U); + pNtClose(handle2); + status = pNtOpenMutant(&handle2, GENERIC_ALL, &attr); + ok(status == STATUS_OBJECT_NAME_NOT_FOUND, "got %08lx\n", status); + pNtClose(handle); + status = pNtCreateMutant(&handle, GENERIC_ALL, &attr3, 0); + ok(!status, "got %08lx\n", status); + test_object_name_with_null(handle, &name3U); + status = pNtOpenMutant(&handle2, GENERIC_ALL, &attr3); + ok(!status, "got %08lx\n", status); + test_object_name_with_null(handle2, &name3U); + pNtClose(handle2); + pNtClose(handle); + + status = pNtCreateSemaphore(&handle, GENERIC_ALL, &attr, 1, 2); + ok(!status, "got %08lx\n", status); + test_object_name(handle, name, FALSE); + status = pNtOpenSemaphore(&handle2, GENERIC_ALL, &attr); + ok(!status, "got %08lx\n", status); + test_object_name(handle2, name, FALSE); + pNtClose(handle2); + status = pNtOpenSemaphore(&handle2, GENERIC_ALL, &attr2); + ok(status == STATUS_OBJECT_NAME_NOT_FOUND, "got %08lx\n", status); + pNtClose(handle); + status = pNtCreateSemaphore(&handle, GENERIC_ALL, &attr2, 1, 2); + ok(!status, "got %08lx\n", status); + test_object_name_with_null(handle, &name2U); + status = pNtOpenSemaphore(&handle2, GENERIC_ALL, &attr2); + ok(!status, "got %08lx\n", status); + test_object_name_with_null(handle2, &name2U); + pNtClose(handle2); + status = pNtOpenSemaphore(&handle2, GENERIC_ALL, &attr); + ok(status == STATUS_OBJECT_NAME_NOT_FOUND, "got %08lx\n", status); + pNtClose(handle); + status = pNtCreateSemaphore(&handle, GENERIC_ALL, &attr3, 1, 2); + ok(!status, "got %08lx\n", status); + test_object_name_with_null(handle, &name3U); + status = pNtOpenSemaphore(&handle2, GENERIC_ALL, &attr3); + ok(!status, "got %08lx\n", status); + test_object_name_with_null(handle2, &name3U); + pNtClose(handle2); + pNtClose(handle); + + status = pNtCreateKeyedEvent(&handle, GENERIC_ALL, &attr, 0); + ok(!status, "got %08lx\n", status); + test_object_name(handle, name, FALSE); + status = pNtOpenKeyedEvent(&handle2, GENERIC_ALL, &attr); + ok(!status, "got %08lx\n", status); + test_object_name(handle2, name, FALSE); + pNtClose(handle2); + status = pNtOpenKeyedEvent(&handle2, GENERIC_ALL, &attr2); + ok(status == STATUS_OBJECT_NAME_NOT_FOUND, "got %08lx\n", status); + pNtClose(handle); + status = pNtCreateKeyedEvent(&handle, GENERIC_ALL, &attr2, 0); + ok(!status, "got %08lx\n", status); + test_object_name_with_null(handle, &name2U); + status = pNtOpenKeyedEvent(&handle2, GENERIC_ALL, &attr2); + ok(!status, "got %08lx\n", status); + test_object_name_with_null(handle2, &name2U); + pNtClose(handle2); + status = pNtOpenKeyedEvent(&handle2, GENERIC_ALL, &attr); + ok(status == STATUS_OBJECT_NAME_NOT_FOUND, "got %08lx\n", status); + pNtClose(handle); + status = pNtCreateKeyedEvent(&handle, GENERIC_ALL, &attr3, 0); + ok(!status, "got %08lx\n", status); + test_object_name_with_null(handle, &name3U); + status = pNtOpenKeyedEvent(&handle2, GENERIC_ALL, &attr3); + ok(!status, "got %08lx\n", status); + test_object_name_with_null(handle2, &name3U); + pNtClose(handle2); + pNtClose(handle); + + status = pNtCreateIoCompletion(&handle, GENERIC_ALL, &attr, 0); + ok(!status, "got %08lx\n", status); + test_object_name(handle, name, FALSE); + status = pNtOpenIoCompletion(&handle2, GENERIC_ALL, &attr); + ok(!status, "got %08lx\n", status); + test_object_name(handle2, name, FALSE); + pNtClose(handle2); + pNtClose(handle); + status = pNtCreateIoCompletion(&handle, GENERIC_ALL, &attr2, 0); + ok(!status, "got %08lx\n", status); + test_object_name_with_null(handle, &name2U); + status = pNtOpenIoCompletion(&handle2, GENERIC_ALL, &attr2); + ok(!status, "got %08lx\n", status); + test_object_name_with_null(handle2, &name2U); + pNtClose(handle2); + pNtClose(handle); + status = pNtCreateIoCompletion(&handle, GENERIC_ALL, &attr3, 0); + ok(!status, "got %08lx\n", status); + test_object_name_with_null(handle, &name3U); + status = pNtOpenIoCompletion(&handle2, GENERIC_ALL, &attr3); + ok(!status, "got %08lx\n", status); + test_object_name_with_null(handle2, &name3U); + pNtClose(handle2); + pNtClose(handle); + + status = pNtCreateJobObject(&handle, GENERIC_ALL, &attr); + ok(!status, "got %08lx\n", status); + test_object_name(handle, name, FALSE); + status = pNtOpenJobObject(&handle2, GENERIC_ALL, &attr); + ok(!status, "got %08lx\n", status); + test_object_name(handle2, name, FALSE); + pNtClose(handle2); + pNtClose(handle); + status = pNtCreateJobObject(&handle, GENERIC_ALL, &attr2); + ok(!status, "got %08lx\n", status); + test_object_name_with_null(handle, &name2U); + status = pNtOpenJobObject(&handle2, GENERIC_ALL, &attr2); + ok(!status, "got %08lx\n", status); + test_object_name_with_null(handle2, &name2U); + pNtClose(handle2); + pNtClose(handle); + status = pNtCreateJobObject(&handle, GENERIC_ALL, &attr3); + ok(!status, "got %08lx\n", status); + test_object_name_with_null(handle, &name3U); + status = pNtOpenJobObject(&handle2, GENERIC_ALL, &attr3); + ok(!status, "got %08lx\n", status); + test_object_name_with_null(handle2, &name3U); + pNtClose(handle2); + pNtClose(handle); + + status = pNtCreateTimer(&handle, GENERIC_ALL, &attr, NotificationTimer); + ok(!status, "got %08lx\n", status); + test_object_name(handle, name, FALSE); + status = pNtOpenTimer(&handle2, GENERIC_ALL, &attr); + ok(!status, "got %08lx\n", status); + test_object_name(handle2, name, FALSE); + pNtClose(handle2); + pNtClose(handle); + status = pNtCreateTimer(&handle, GENERIC_ALL, &attr2, NotificationTimer); + ok(!status, "got %08lx\n", status); + test_object_name_with_null(handle, &name2U); + status = pNtOpenTimer(&handle2, GENERIC_ALL, &attr2); + ok(!status, "got %08lx\n", status); + test_object_name_with_null(handle2, &name2U); + pNtClose(handle2); + pNtClose(handle); + status = pNtCreateTimer(&handle, GENERIC_ALL, &attr3, NotificationTimer); + ok(!status, "got %08lx\n", status); + test_object_name_with_null(handle, &name3U); + status = pNtOpenTimer(&handle2, GENERIC_ALL, &attr3); + ok(!status, "got %08lx\n", status); + test_object_name_with_null(handle2, &name3U); + pNtClose(handle2); + pNtClose(handle); + + size.QuadPart = 4096; + status = pNtCreateSection(&handle, GENERIC_ALL, &attr, &size, PAGE_READWRITE, SEC_COMMIT, 0); + ok(!status, "got %08lx\n", status); + test_object_name(handle, name, FALSE); + status = pNtOpenSection(&handle2, GENERIC_ALL, &attr); + ok(!status, "got %08lx\n", status); + test_object_name(handle2, name, FALSE); + pNtClose(handle2); + pNtClose(handle); + status = pNtCreateSection(&handle, GENERIC_ALL, &attr2, &size, PAGE_READWRITE, SEC_COMMIT, 0); + ok(!status, "got %08lx\n", status); + test_object_name_with_null(handle, &name2U); + status = pNtOpenSection(&handle2, GENERIC_ALL, &attr2); + ok(!status, "got %08lx\n", status); + test_object_name_with_null(handle2, &name2U); + pNtClose(handle2); + pNtClose(handle); + status = pNtCreateSection(&handle, GENERIC_ALL, &attr3, &size, PAGE_READWRITE, SEC_COMMIT, 0); + ok(!status, "got %08lx\n", status); + test_object_name_with_null(handle, &name3U); + status = pNtOpenSection(&handle2, GENERIC_ALL, &attr3); + ok(!status, "got %08lx\n", status); + test_object_name_with_null(handle2, &name3U); + pNtClose(handle2); + pNtClose(handle); + + wcscpy(name, L"\\Registry\\Machine\\Software\\wine_test"); + wcscpy(name3, L"\\Registry\\Machine\\Software\\wine_test"); + p = wcsrchr(name3, '\\'); + p[5] = 0; /* => \\wine\0test */ + + RtlInitUnicodeString(&nameU, name); + name2U = nameU; + name3U = nameU; + name3U.Buffer = name3; +#ifdef _WIN64 + name_exp = name; + name3_exp = name3; + name2U_exp = name2U; +#else + if (IsWow64Process(GetCurrentProcess(), &is_wow64) && is_wow64) + { + name_exp = (WCHAR *)L"\\Registry\\Machine\\Software\\WOW6432Node\\wine_test"; + name3_exp =(WCHAR *) L"\\Registry\\Machine\\Software\\WOW6432Node\\wine\0test"; + } + else + { + name_exp = name; + name3_exp = name3; + } + RtlInitUnicodeString(&name2U_exp, name_exp); +#endif + name3U_exp = name2U_exp; + name3U_exp.Buffer = name3_exp; + name2U.Length += sizeof(WCHAR); /* add terminating \0 to string length */ + name2U_exp.Length += sizeof(WCHAR); /* add terminating \0 to string length */ + + status = pNtCreateKey(&handle, GENERIC_ALL, &attr, 0, NULL, 0, NULL); + ok(!status || status == STATUS_ACCESS_DENIED || broken(status == STATUS_OBJECT_PATH_NOT_FOUND) /* win8 */, "got %08lx\n", status); + if (!status) + { + test_object_name(handle, name_exp, FALSE); + status = pNtOpenKey(&handle2, GENERIC_ALL, &attr); + ok(!status, "got %08lx\n", status); + test_object_name(handle2, name_exp, FALSE); + pNtClose(handle2); + status = pNtOpenKey(&handle2, GENERIC_ALL, &attr2); + ok(status == STATUS_OBJECT_NAME_NOT_FOUND, "got %08lx\n", status); + pNtDeleteKey(handle); + pNtClose(handle); + status = pNtCreateKey(&handle, GENERIC_ALL, &attr2, 0, NULL, 0, NULL); + ok(!status, "got %08lx\n", status); + test_object_name_with_null(handle, &name2U_exp); + status = pNtOpenKey(&handle2, GENERIC_ALL, &attr2); + ok(!status, "got %08lx\n", status); + test_object_name_with_null(handle, &name2U_exp); + pNtClose(handle2); + status = pNtOpenKey(&handle2, GENERIC_ALL, &attr); + ok(status == STATUS_OBJECT_NAME_NOT_FOUND, "got %08lx\n", status); + pNtDeleteKey(handle); + pNtClose(handle); + status = pNtCreateKey(&handle, GENERIC_ALL, &attr3, 0, NULL, 0, NULL); + ok(!status, "got %08lx\n", status); + test_object_name_with_null(handle, &name3U_exp); + status = pNtOpenKey(&handle2, GENERIC_ALL, &attr3); + ok(!status, "got %08lx\n", status); + test_object_name_with_null(handle, &name3U_exp); + pNtClose(handle2); + pNtDeleteKey(handle); + pNtClose(handle); + } + else + skip("Limited access to \\Registry\\Machine\\Software key, skipping the tests\n"); +} + START_TEST(om) { HMODULE hntdll = GetModuleHandleA("ntdll.dll"); @@ -2767,6 +3114,7 @@ START_TEST(om) pNtDuplicateObject = (void *)GetProcAddress(hntdll, "NtDuplicateObject"); pNtCompareObjects = (void *)GetProcAddress(hntdll, "NtCompareObjects"); + test_null_in_object_name(); test_case_sensitive(); test_namespace_pipe(); test_name_collisions(); -- 2.37.1

1 0

[PATCH 1/2] ntdll/tests: Fix compilation with PSDK.
by Dmitry Timoshkov 28 Jul '22

28 Jul '22

Signed-off-by: Dmitry Timoshkov <dmitry(a)baikal.ru> --- dlls/ntdll/tests/om.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/dlls/ntdll/tests/om.c b/dlls/ntdll/tests/om.c index ddbdce0281c..7fe0fb59f89 100644 --- a/dlls/ntdll/tests/om.c +++ b/dlls/ntdll/tests/om.c @@ -2078,7 +2078,7 @@ static void test_token(void) status = pNtOpenThreadToken( GetCurrentThread(), TOKEN_ALL_ACCESS, TRUE, (HANDLE *)0xdeadbee0 ); ok( status == STATUS_ACCESS_VIOLATION, "NtOpenProcessToken failed: %lx\n", status); handle = (HANDLE)0xdeadbeef; - status = NtOpenProcessToken( (HANDLE)0xdead, TOKEN_ALL_ACCESS, &handle ); + status = pNtOpenProcessToken( (HANDLE)0xdead, TOKEN_ALL_ACCESS, &handle ); ok( status == STATUS_INVALID_HANDLE, "NtOpenProcessToken failed: %lx\n", status); ok( !handle || broken(handle == (HANDLE)0xdeadbeef) /* vista */, "handle set %p\n", handle ); handle = (HANDLE)0xdeadbeef; @@ -2526,7 +2526,7 @@ static void test_query_directory(void) RtlInitUnicodeString( &string, L"\\BaseNamedObjects\\winetest" ); InitializeObjectAttributes( &attr, &string, 0, 0, NULL ); - status = NtCreateDirectoryObject( &dir, DIRECTORY_QUERY, &attr ); + status = pNtCreateDirectoryObject( &dir, DIRECTORY_QUERY, &attr ); ok( !status, "got %#lx\n", status ); context = 0xdeadbeef; @@ -2717,9 +2717,9 @@ static void test_query_directory(void) ok( !memcmp( &info[1], &empty_info, sizeof(*info) ), "entry was not cleared\n" ); } - NtClose( child1 ); - NtClose( child2 ); - NtClose( dir ); + pNtClose( child1 ); + pNtClose( child2 ); + pNtClose( dir ); } START_TEST(om) -- 2.37.1

1 0

Re: [PATCH v2 2/2] ddraw/tests: Add some video memory accounting tests.
by Marvin 28 Jul '22

28 Jul '22

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=119983 Your paranoid android. === w7u_2qxl (32 bit report) === ddraw: ddraw2.c:7210: Test failed: Failed to get available video memory, hr 0x88760233. ddraw2.c:7263: Test failed: Failed to get available video memory, hr 0x88760233. ddraw2.c:7285: Test failed: Failed to get available video memory, hr 0x88760233. ddraw2.c:7263: Test failed: Failed to get available video memory, hr 0x88760233. ddraw2.c:7285: Test failed: Failed to get available video memory, hr 0x88760233. ddraw2.c:7263: Test failed: Failed to get available video memory, hr 0x88760233. ddraw2.c:7285: Test failed: Failed to get available video memory, hr 0x88760233. ddraw2.c:7263: Test failed: Failed to get available video memory, hr 0x88760233. ddraw2.c:7285: Test failed: Failed to get available video memory, hr 0x88760233. ddraw2.c:7263: Test failed: Failed to get available video memory, hr 0x88760233. ddraw2.c:7285: Test failed: Failed to get available video memory, hr 0x88760233. === w7u_adm (32 bit report) === ddraw: ddraw2.c:7210: Test failed: Failed to get available video memory, hr 0x88760233. ddraw2.c:7263: Test failed: Failed to get available video memory, hr 0x88760233. ddraw2.c:7285: Test failed: Failed to get available video memory, hr 0x88760233. ddraw2.c:7263: Test failed: Failed to get available video memory, hr 0x88760233. ddraw2.c:7285: Test failed: Failed to get available video memory, hr 0x88760233. ddraw2.c:7263: Test failed: Failed to get available video memory, hr 0x88760233. ddraw2.c:7285: Test failed: Failed to get available video memory, hr 0x88760233. ddraw2.c:7263: Test failed: Failed to get available video memory, hr 0x88760233. ddraw2.c:7285: Test failed: Failed to get available video memory, hr 0x88760233. ddraw2.c:7263: Test failed: Failed to get available video memory, hr 0x88760233. ddraw2.c:7285: Test failed: Failed to get available video memory, hr 0x88760233. === w7u_el (32 bit report) === ddraw: ddraw2.c:7210: Test failed: Failed to get available video memory, hr 0x88760233. ddraw2.c:7263: Test failed: Failed to get available video memory, hr 0x88760233. ddraw2.c:7285: Test failed: Failed to get available video memory, hr 0x88760233. ddraw2.c:7263: Test failed: Failed to get available video memory, hr 0x88760233. ddraw2.c:7285: Test failed: Failed to get available video memory, hr 0x88760233. ddraw2.c:7263: Test failed: Failed to get available video memory, hr 0x88760233. ddraw2.c:7285: Test failed: Failed to get available video memory, hr 0x88760233. ddraw2.c:7263: Test failed: Failed to get available video memory, hr 0x88760233. ddraw2.c:7285: Test failed: Failed to get available video memory, hr 0x88760233. ddraw2.c:7263: Test failed: Failed to get available video memory, hr 0x88760233. ddraw2.c:7285: Test failed: Failed to get available video memory, hr 0x88760233. === w7u_2qxl (32 bit report) === ddraw: ddraw4.c:9112: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9165: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9187: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9165: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9187: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9165: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9187: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9165: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9187: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9165: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9187: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9165: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9187: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9165: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9187: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9165: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9187: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9165: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9187: Test failed: Failed to get available video memory, hr 0x88760233. === w7u_adm (32 bit report) === ddraw: ddraw4.c:9112: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9165: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9187: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9165: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9187: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9165: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9187: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9165: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9187: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9165: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9187: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9165: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9187: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9165: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9187: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9165: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9187: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9165: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9187: Test failed: Failed to get available video memory, hr 0x88760233. === w7u_el (32 bit report) === ddraw: ddraw4.c:9112: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9165: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9187: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9165: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9187: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9165: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9187: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9165: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9187: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9165: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9187: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9165: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9187: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9165: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9187: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9165: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9187: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9165: Test failed: Failed to get available video memory, hr 0x88760233. ddraw4.c:9187: Test failed: Failed to get available video memory, hr 0x88760233. === w7u_2qxl (32 bit report) === ddraw: ddraw7.c:8952: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9008: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9030: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9008: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9030: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9008: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9030: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9008: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9030: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9008: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9030: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9008: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9030: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9008: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9030: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9008: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9030: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9008: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9030: Test failed: Failed to get available video memory, hr 0x88760233. === w7u_adm (32 bit report) === ddraw: ddraw7.c:8952: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9008: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9030: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9008: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9030: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9008: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9030: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9008: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9030: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9008: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9030: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9008: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9030: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9008: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9030: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9008: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9030: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9008: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9030: Test failed: Failed to get available video memory, hr 0x88760233. === w7u_el (32 bit report) === ddraw: ddraw7.c:8952: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9008: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9030: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9008: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9030: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9008: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9030: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9008: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9030: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9008: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9030: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9008: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9030: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9008: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9030: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9008: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9030: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9008: Test failed: Failed to get available video memory, hr 0x88760233. ddraw7.c:9030: Test failed: Failed to get available video memory, hr 0x88760233. === w1064 (32 bit report) === ddraw: ddraw7.c:18884: Test failed: Got unexpected color 0x00000040. === w1064_tsign (32 bit report) === ddraw: ddraw7.c:18884: Test failed: Got unexpected color 0x0000ff00. === debian11 (32 bit Chinese:China report) === Report validation errors: ddraw1: Timeout === debian11 (build log) === WineRunWineTest.pl:error: The task timed out

1 0

Re: [PATCH v3 5/9] mshtml: Implement lastElementChild for Elements.
by Marvin 28 Jul '22

28 Jul '22

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=119953 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 === w10pro64_ar (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 v3 4/9] mshtml: Implement hasAttributeNS for Elements.
by Marvin 28 Jul '22

28 Jul '22

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=119952 Your paranoid android. === w10pro64 (32 bit report) === mshtml: htmldoc.c:2541: Test failed: unexpected call UpdateUI htmldoc.c:2853: Test failed: unexpected call Exec_UPDATECOMMANDS === w1064_2qxl (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 === w1064_adm (64 bit report) === mshtml: script.c:3119: Test failed: ReportResult failed: 80ef0001

1 0

Re: [PATCH v3 3/9] mshtml: Implement removeAttributeNS for Elements.
by Marvin 28 Jul '22

28 Jul '22

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=119951 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 v4 1/1] d3drm/tests: Show Clear sets background color
by Marvin 28 Jul '22

28 Jul '22

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=120010 Your paranoid android. === debian11 (32 bit report) === d3drm: d3drm.c:7361: Test failed: Got unexpected color 0x007f7f7f. d3drm.c:7380: Test failed: Got unexpected color 0x007f7f7f. d3drm.c:7390: Test failed: Got unexpected color 0x007f7f7f. d3drm.c:7410: Test failed: Got unexpected color 0x007f7f7f. === debian11 (32 bit Arabic:Morocco report) === d3drm: d3drm.c:7361: Test failed: Got unexpected color 0x007f7f7f. d3drm.c:7380: Test failed: Got unexpected color 0x007f7f7f. d3drm.c:7390: Test failed: Got unexpected color 0x007f7f7f. d3drm.c:7410: Test failed: Got unexpected color 0x007f7f7f. === debian11 (32 bit German report) === d3drm: d3drm.c:7361: Test failed: Got unexpected color 0x007f7f7f. d3drm.c:7380: Test failed: Got unexpected color 0x007f7f7f. d3drm.c:7390: Test failed: Got unexpected color 0x007f7f7f. d3drm.c:7410: Test failed: Got unexpected color 0x007f7f7f. === debian11 (32 bit French report) === d3drm: d3drm.c:7361: Test failed: Got unexpected color 0x007f7f7f. d3drm.c:7380: Test failed: Got unexpected color 0x007f7f7f. d3drm.c:7390: Test failed: Got unexpected color 0x007f7f7f. d3drm.c:7410: Test failed: Got unexpected color 0x007f7f7f. === debian11 (32 bit Hebrew:Israel report) === d3drm: d3drm.c:7361: Test failed: Got unexpected color 0x007f7f7f. d3drm.c:7380: Test failed: Got unexpected color 0x007f7f7f. d3drm.c:7390: Test failed: Got unexpected color 0x007f7f7f. d3drm.c:7410: Test failed: Got unexpected color 0x007f7f7f. === debian11 (32 bit Hindi:India report) === d3drm: d3drm.c:7361: Test failed: Got unexpected color 0x007f7f7f. d3drm.c:7380: Test failed: Got unexpected color 0x007f7f7f. d3drm.c:7390: Test failed: Got unexpected color 0x007f7f7f. d3drm.c:7410: Test failed: Got unexpected color 0x007f7f7f. === debian11 (32 bit Japanese:Japan report) === d3drm: d3drm.c:7361: Test failed: Got unexpected color 0x007f7f7f. d3drm.c:7380: Test failed: Got unexpected color 0x007f7f7f. d3drm.c:7390: Test failed: Got unexpected color 0x007f7f7f. d3drm.c:7410: Test failed: Got unexpected color 0x007f7f7f. === debian11 (32 bit Chinese:China report) === d3drm: d3drm.c:7361: Test failed: Got unexpected color 0x007f7f7f. d3drm.c:7380: Test failed: Got unexpected color 0x007f7f7f. d3drm.c:7390: Test failed: Got unexpected color 0x007f7f7f. d3drm.c:7410: Test failed: Got unexpected color 0x007f7f7f. === debian11 (32 bit WoW report) === d3drm: d3drm.c:7361: Test failed: Got unexpected color 0x007f7f7f. d3drm.c:7380: Test failed: Got unexpected color 0x007f7f7f. d3drm.c:7390: Test failed: Got unexpected color 0x007f7f7f. d3drm.c:7410: Test failed: Got unexpected color 0x007f7f7f. === debian11 (64 bit WoW report) === d3drm: d3drm.c:7361: Test failed: Got unexpected color 0x007f7f7f. d3drm.c:7380: Test failed: Got unexpected color 0x007f7f7f. d3drm.c:7390: Test failed: Got unexpected color 0x007f7f7f. d3drm.c:7410: Test failed: Got unexpected color 0x007f7f7f.

1 0

Re: [PATCH v3 2/9] mshtml: Implement setAttributeNS for Elements.
by Marvin 28 Jul '22

28 Jul '22

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=119950 Your paranoid android. === w10pro64 (32 bit report) === mshtml: htmldoc.c:2541: Test failed: unexpected call UpdateUI htmldoc.c:2853: Test failed: unexpected call Exec_UPDATECOMMANDS

1 0

Re: [PATCH 5/6] comctl32/listview: Don't send LVN_ODSTATECHANGED for empty ranges.
by Marvin 28 Jul '22

28 Jul '22

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=119995 Your paranoid android. === debian11 (32 bit report) === comctl32: listview.c:3578: Test succeeded inside todo block: ownerdata select multiple notification: marked "todo_wine" but succeeds listview.c:3595: Test succeeded inside todo block: ownerdata select multiple notification: marked "todo_wine" but succeeds listview.c:3578: Test succeeded inside todo block: ownerdata select multiple notification: marked "todo_wine" but succeeds listview.c:3595: Test succeeded inside todo block: ownerdata select multiple notification: marked "todo_wine" but succeeds === debian11 (32 bit Chinese:China report) === comctl32: listview.c:3578: Test succeeded inside todo block: ownerdata select multiple notification: marked "todo_wine" but succeeds listview.c:3595: Test succeeded inside todo block: ownerdata select multiple notification: marked "todo_wine" but succeeds listview.c:3578: Test succeeded inside todo block: ownerdata select multiple notification: marked "todo_wine" but succeeds listview.c:3595: Test succeeded inside todo block: ownerdata select multiple notification: marked "todo_wine" but succeeds === debian11 (32 bit WoW report) === comctl32: listview.c:3578: Test succeeded inside todo block: ownerdata select multiple notification: marked "todo_wine" but succeeds listview.c:3595: Test succeeded inside todo block: ownerdata select multiple notification: marked "todo_wine" but succeeds listview.c:3578: Test succeeded inside todo block: ownerdata select multiple notification: marked "todo_wine" but succeeds listview.c:3595: Test succeeded inside todo block: ownerdata select multiple notification: marked "todo_wine" but succeeds === debian11 (64 bit WoW report) === comctl32: listview.c:3578: Test succeeded inside todo block: ownerdata select multiple notification: marked "todo_wine" but succeeds listview.c:3595: Test succeeded inside todo block: ownerdata select multiple notification: marked "todo_wine" but succeeds listview.c:3578: Test succeeded inside todo block: ownerdata select multiple notification: marked "todo_wine" but succeeds listview.c:3595: Test succeeded inside todo block: ownerdata select multiple notification: marked "todo_wine" but succeeds

1 0

Re: [PATCH 4/6] comctl32/listview: Send LVN_ODSTATECHANGED notification for LVS_OWNERDATA listview on selection changes.
by Marvin 28 Jul '22

28 Jul '22

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=119994 Your paranoid android. === debian11 (32 bit report) === comctl32: listview.c:3578: Test succeeded inside todo block: ownerdata select multiple notification: marked "todo_wine" but succeeds listview.c:3595: Test succeeded inside todo block: ownerdata select multiple notification: marked "todo_wine" but succeeds listview.c:3578: Test succeeded inside todo block: ownerdata select multiple notification: marked "todo_wine" but succeeds listview.c:3595: Test succeeded inside todo block: ownerdata select multiple notification: marked "todo_wine" but succeeds === debian11 (32 bit Chinese:China report) === comctl32: listview.c:3578: Test succeeded inside todo block: ownerdata select multiple notification: marked "todo_wine" but succeeds listview.c:3595: Test succeeded inside todo block: ownerdata select multiple notification: marked "todo_wine" but succeeds listview.c:3578: Test succeeded inside todo block: ownerdata select multiple notification: marked "todo_wine" but succeeds listview.c:3595: Test succeeded inside todo block: ownerdata select multiple notification: marked "todo_wine" but succeeds === debian11 (32 bit WoW report) === comctl32: listview.c:3578: Test succeeded inside todo block: ownerdata select multiple notification: marked "todo_wine" but succeeds listview.c:3595: Test succeeded inside todo block: ownerdata select multiple notification: marked "todo_wine" but succeeds listview.c:3578: Test succeeded inside todo block: ownerdata select multiple notification: marked "todo_wine" but succeeds listview.c:3595: Test succeeded inside todo block: ownerdata select multiple notification: marked "todo_wine" but succeeds === debian11 (64 bit WoW report) === comctl32: listview.c:3578: Test succeeded inside todo block: ownerdata select multiple notification: marked "todo_wine" but succeeds listview.c:3595: Test succeeded inside todo block: ownerdata select multiple notification: marked "todo_wine" but succeeds listview.c:3578: Test succeeded inside todo block: ownerdata select multiple notification: marked "todo_wine" but succeeds listview.c:3595: Test succeeded inside todo block: ownerdata select multiple notification: marked "todo_wine" but succeeds

1 0

[PATCH v4 0/7] Fix LVS_OWNERDATA list view multi select.
by Angelo Haller 28 Jul '22

28 Jul '22

From: Angelo Haller <angelo(a)szanni.org> The following patches fix sending of the LVN_ODSTATECHANGED notification for LVS_OWNERDATA list views, adding more refined tests in the process and fixing various bugs. This is v4 fixing the log buffer overflow on the debian test machine by moving some of the up/down key sequences to a later patch. Patch 1/7 still includes the necessary up/down key sequences to validate the fixes in the following patches. The matching up/down key sequences for 1/7 are then introduced in 7/7. I was sadly unable to introduce the test sequence with each fix, as this would require inventing entirely new test sequences, just to work around the debian 32KB log buffer limit. I hope this is ok as it stands. I am also attaching the my remarks from v3, as I don't know if they got ignored due to failing tests: I was sadly not able to trigger any deselect sequences through emulating mouse clicks. I was actually completely unable even send a lef mouse button down at all. Both SendMessage and SendInput fail, on wind and windows. I am unsure if programmatic mouse clicks are even supported in list views? Some forums seem to suggest, that this is only the case for buttons and similar elements. I was following the code snippets in other parts of the comctl32 tests. The other thing might be that the signal is getting caught somewhere in the test code. If anybody has any more insight in this regard, I'd be happy to add additional mouse click tests as well. The other thing I was unable to do is activate the single select tests via SHIFT/+COMMAND to show we need patch 6/6. Windows weirdly informs about the selected item twice, once to inform the item has been selected and then in another call later about the item being focused as well. This seemingly only affects LVS_OWNERDATA listviews from my tests. Warning: I have had access to the Windows Research Kernel (WRK) 1.2 ~10 years ago. These changes are regarding comctrl32 & tests which are NOT part of the WRK. As outlined in https://wiki.winehq.org/Developer_FAQ this should therefore satisfy the requirement of ONLY submitting patches to components I have NOT had access to. Angelo Haller (7): Add more test cases to ownderdata listviews: comctl32/listview: Fix deselect on LVS_OWNERDATA. comctl32/listview: Move sending LVN_ODSTATECHANGED notifications to a function. comctl32/listview: Send LVN_ODSTATECHANGED only for virtual lists. comctl32/listview: Send LVN_ODSTATECHANGED notification. comctl32/listview: Send LVN_ODSTATECHANGED only for true ranges. comctl32/tests: Expand ownerdata listview tests. dlls/comctl32/listview.c | 55 ++++--- dlls/comctl32/tests/listview.c | 253 +++++++++++++++++++++++++++++++-- 2 files changed, 281 insertions(+), 27 deletions(-) Signed-off-by: Angelo Haller <angelo(a)szanni.org> -- 2.36.1

2 11

Re: [PATCH v2 9/9] mshtml: Implement HTMLTitleElement's text property.
by Marvin 28 Jul '22

28 Jul '22

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=119867 Your paranoid android. === w10pro64_ar (64 bit report) === mshtml: htmldoc.c:2541: Test failed: unexpected call UpdateUI htmldoc.c:2853: Test failed: unexpected call Exec_UPDATECOMMANDS === w10pro64_ja (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 v2 8/9] mshtml: Implement childElementCount for Elements.
by Marvin 28 Jul '22

28 Jul '22

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=119866 Your paranoid android. === w1064v1809 (64 bit report) === mshtml: script.c:3119: Test failed: ReportResult failed: 80ef0001

1 0

Re: [PATCH v6 9/9] mshtml: Implement HTMLTitleElement's text property.
by Marvin 27 Jul '22

27 Jul '22

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=119981 Your paranoid android. === build (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4886 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4925 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6524 error: patch failed: dlls/mshtml/tests/dom.js:89 error: patch failed: dlls/mshtml/htmlelem.c:6560 error: patch failed: dlls/mshtml/tests/dom.js:94 error: patch failed: dlls/mshtml/htmlelem.c:6553 error: patch failed: dlls/mshtml/tests/dom.js:98 error: patch failed: dlls/mshtml/htmlelem.c:6611 error: patch failed: dlls/mshtml/tests/dom.js:90 error: patch failed: dlls/mshtml/htmlhead.c:103 error: patch failed: dlls/mshtml/tests/dom.js:533 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4886 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4925 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6524 error: patch failed: dlls/mshtml/tests/dom.js:89 error: patch failed: dlls/mshtml/htmlelem.c:6560 error: patch failed: dlls/mshtml/tests/dom.js:94 error: patch failed: dlls/mshtml/htmlelem.c:6553 error: patch failed: dlls/mshtml/tests/dom.js:98 error: patch failed: dlls/mshtml/htmlelem.c:6611 error: patch failed: dlls/mshtml/tests/dom.js:90 error: patch failed: dlls/mshtml/htmlhead.c:103 error: patch failed: dlls/mshtml/tests/dom.js:533 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4886 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4925 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6524 error: patch failed: dlls/mshtml/tests/dom.js:89 error: patch failed: dlls/mshtml/htmlelem.c:6560 error: patch failed: dlls/mshtml/tests/dom.js:94 error: patch failed: dlls/mshtml/htmlelem.c:6553 error: patch failed: dlls/mshtml/tests/dom.js:98 error: patch failed: dlls/mshtml/htmlelem.c:6611 error: patch failed: dlls/mshtml/tests/dom.js:90 error: patch failed: dlls/mshtml/htmlhead.c:103 error: patch failed: dlls/mshtml/tests/dom.js:533 Task: Patch failed to apply

1 0

Re: [PATCH v6 8/9] mshtml: Implement childElementCount for Elements.
by Marvin 27 Jul '22

27 Jul '22

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=119980 Your paranoid android. === build (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4886 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4925 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6524 error: patch failed: dlls/mshtml/tests/dom.js:89 error: patch failed: dlls/mshtml/htmlelem.c:6560 error: patch failed: dlls/mshtml/tests/dom.js:94 error: patch failed: dlls/mshtml/htmlelem.c:6553 error: patch failed: dlls/mshtml/tests/dom.js:98 error: patch failed: dlls/mshtml/htmlelem.c:6611 error: patch failed: dlls/mshtml/tests/dom.js:90 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4886 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4925 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6524 error: patch failed: dlls/mshtml/tests/dom.js:89 error: patch failed: dlls/mshtml/htmlelem.c:6560 error: patch failed: dlls/mshtml/tests/dom.js:94 error: patch failed: dlls/mshtml/htmlelem.c:6553 error: patch failed: dlls/mshtml/tests/dom.js:98 error: patch failed: dlls/mshtml/htmlelem.c:6611 error: patch failed: dlls/mshtml/tests/dom.js:90 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4886 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4925 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6524 error: patch failed: dlls/mshtml/tests/dom.js:89 error: patch failed: dlls/mshtml/htmlelem.c:6560 error: patch failed: dlls/mshtml/tests/dom.js:94 error: patch failed: dlls/mshtml/htmlelem.c:6553 error: patch failed: dlls/mshtml/tests/dom.js:98 error: patch failed: dlls/mshtml/htmlelem.c:6611 error: patch failed: dlls/mshtml/tests/dom.js:90 Task: Patch failed to apply

1 0

Re: [PATCH v6 7/9] mshtml: Implement previousElementSibling for Elements.
by Marvin 27 Jul '22

27 Jul '22

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=119979 Your paranoid android. === build (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4886 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4925 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6524 error: patch failed: dlls/mshtml/tests/dom.js:89 error: patch failed: dlls/mshtml/htmlelem.c:6560 error: patch failed: dlls/mshtml/tests/dom.js:94 error: patch failed: dlls/mshtml/htmlelem.c:6553 error: patch failed: dlls/mshtml/tests/dom.js:98 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4886 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4925 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6524 error: patch failed: dlls/mshtml/tests/dom.js:89 error: patch failed: dlls/mshtml/htmlelem.c:6560 error: patch failed: dlls/mshtml/tests/dom.js:94 error: patch failed: dlls/mshtml/htmlelem.c:6553 error: patch failed: dlls/mshtml/tests/dom.js:98 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4886 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4925 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6524 error: patch failed: dlls/mshtml/tests/dom.js:89 error: patch failed: dlls/mshtml/htmlelem.c:6560 error: patch failed: dlls/mshtml/tests/dom.js:94 error: patch failed: dlls/mshtml/htmlelem.c:6553 error: patch failed: dlls/mshtml/tests/dom.js:98 Task: Patch failed to apply

1 0

Re: [PATCH v6 6/9] mshtml: Implement nextElementSibling for Elements.
by Marvin 27 Jul '22

27 Jul '22

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=119978 Your paranoid android. === build (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4886 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4925 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6524 error: patch failed: dlls/mshtml/tests/dom.js:89 error: patch failed: dlls/mshtml/htmlelem.c:6560 error: patch failed: dlls/mshtml/tests/dom.js:94 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4886 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4925 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6524 error: patch failed: dlls/mshtml/tests/dom.js:89 error: patch failed: dlls/mshtml/htmlelem.c:6560 error: patch failed: dlls/mshtml/tests/dom.js:94 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4886 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4925 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6524 error: patch failed: dlls/mshtml/tests/dom.js:89 error: patch failed: dlls/mshtml/htmlelem.c:6560 error: patch failed: dlls/mshtml/tests/dom.js:94 Task: Patch failed to apply

1 0

Re: [PATCH v6 5/9] mshtml: Implement lastElementChild for Elements.
by Marvin 27 Jul '22

27 Jul '22

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=119977 Your paranoid android. === build (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4886 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4925 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6524 error: patch failed: dlls/mshtml/tests/dom.js:89 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4886 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4925 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6524 error: patch failed: dlls/mshtml/tests/dom.js:89 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4886 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4925 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6524 error: patch failed: dlls/mshtml/tests/dom.js:89 Task: Patch failed to apply

1 0

Re: [PATCH v6 4/9] mshtml: Implement hasAttributeNS for Elements.
by Marvin 27 Jul '22

27 Jul '22

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=119976 Your paranoid android. === build (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4886 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4925 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4886 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4925 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4886 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4925 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 Task: Patch failed to apply

1 0

Re: [PATCH v6 3/9] mshtml: Implement removeAttributeNS for Elements.
by Marvin 27 Jul '22

27 Jul '22

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=119975 Your paranoid android. === build (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4886 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4886 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4886 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 Task: Patch failed to apply

1 0

Re: [PATCH v6 2/9] mshtml: Implement setAttributeNS for Elements.
by Marvin 27 Jul '22

27 Jul '22

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=119974 Your paranoid android. === build (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 Task: Patch failed to apply

1 0

Re: [PATCH v2 5/6] dxgi: Build the device list only once in dxgi_output_get_display_mode_list().
by Marvin 27 Jul '22

27 Jul '22

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=119971 Your paranoid android. === debian11 (32 bit report) === dxgi: dxgi: Timeout === debian11 (32 bit Chinese:China report) === dxgi: dxgi: Timeout === debian11 (32 bit WoW report) === dxgi: dxgi: Timeout === debian11 (64 bit WoW report) === dxgi: dxgi: Timeout

1 0

Re: [PATCH v2 4/6] d3d8: Cache the output mode list.
by Marvin 27 Jul '22

27 Jul '22

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=119970 Your paranoid android. === debian11 (32 bit report) === d3d8: Unhandled exception: page fault on read access to 0x007b1000 in 32-bit code (0x714b859f). === debian11 (32 bit Chinese:China report) === Report validation errors: d3d8:device crashed (c0000005) === debian11 (64 bit WoW report) === d3d8: device: Timeout

1 0

Re: [PATCH v2 3/6] d3d9: Cache the output mode list.
by Marvin 27 Jul '22

27 Jul '22

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=119969 Your paranoid android. === debian11 (32 bit report) === dxgi: dxgi: Timeout === debian11 (32 bit Chinese:China report) === dxgi: dxgi: Timeout === debian11 (32 bit WoW report) === dxgi: dxgi: Timeout Report validation errors: d3d8:device crashed (c0000005) === debian11 (64 bit WoW report) === dxgi: dxgi.c:6776: Test failed: Adapter 0: Output 1: Got unexpected hr 0x80070057. Unhandled exception: page fault on execute access to 0x00000000001ffc80 in 64-bit code (0x000000001ffc80).

1 0

Re: [PATCH v4 9/9] mshtml: Implement HTMLTitleElement's text property.
by Marvin 27 Jul '22

27 Jul '22

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=119966 Your paranoid android. === build (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4887 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4926 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6525 error: patch failed: dlls/mshtml/tests/dom.js:89 error: patch failed: dlls/mshtml/htmlelem.c:6561 error: patch failed: dlls/mshtml/tests/dom.js:94 error: patch failed: dlls/mshtml/htmlelem.c:6554 error: patch failed: dlls/mshtml/tests/dom.js:98 error: patch failed: dlls/mshtml/htmlelem.c:6612 error: patch failed: dlls/mshtml/tests/dom.js:90 error: patch failed: dlls/mshtml/htmlhead.c:103 error: patch failed: dlls/mshtml/tests/dom.js:533 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4887 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4926 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6525 error: patch failed: dlls/mshtml/tests/dom.js:89 error: patch failed: dlls/mshtml/htmlelem.c:6561 error: patch failed: dlls/mshtml/tests/dom.js:94 error: patch failed: dlls/mshtml/htmlelem.c:6554 error: patch failed: dlls/mshtml/tests/dom.js:98 error: patch failed: dlls/mshtml/htmlelem.c:6612 error: patch failed: dlls/mshtml/tests/dom.js:90 error: patch failed: dlls/mshtml/htmlhead.c:103 error: patch failed: dlls/mshtml/tests/dom.js:533 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4887 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4926 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6525 error: patch failed: dlls/mshtml/tests/dom.js:89 error: patch failed: dlls/mshtml/htmlelem.c:6561 error: patch failed: dlls/mshtml/tests/dom.js:94 error: patch failed: dlls/mshtml/htmlelem.c:6554 error: patch failed: dlls/mshtml/tests/dom.js:98 error: patch failed: dlls/mshtml/htmlelem.c:6612 error: patch failed: dlls/mshtml/tests/dom.js:90 error: patch failed: dlls/mshtml/htmlhead.c:103 error: patch failed: dlls/mshtml/tests/dom.js:533 Task: Patch failed to apply

1 0

Re: [PATCH v4 8/9] mshtml: Implement childElementCount for Elements.
by Marvin 27 Jul '22

27 Jul '22

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=119965 Your paranoid android. === build (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4887 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4926 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6525 error: patch failed: dlls/mshtml/tests/dom.js:89 error: patch failed: dlls/mshtml/htmlelem.c:6561 error: patch failed: dlls/mshtml/tests/dom.js:94 error: patch failed: dlls/mshtml/htmlelem.c:6554 error: patch failed: dlls/mshtml/tests/dom.js:98 error: patch failed: dlls/mshtml/htmlelem.c:6612 error: patch failed: dlls/mshtml/tests/dom.js:90 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4887 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4926 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6525 error: patch failed: dlls/mshtml/tests/dom.js:89 error: patch failed: dlls/mshtml/htmlelem.c:6561 error: patch failed: dlls/mshtml/tests/dom.js:94 error: patch failed: dlls/mshtml/htmlelem.c:6554 error: patch failed: dlls/mshtml/tests/dom.js:98 error: patch failed: dlls/mshtml/htmlelem.c:6612 error: patch failed: dlls/mshtml/tests/dom.js:90 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4887 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4926 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6525 error: patch failed: dlls/mshtml/tests/dom.js:89 error: patch failed: dlls/mshtml/htmlelem.c:6561 error: patch failed: dlls/mshtml/tests/dom.js:94 error: patch failed: dlls/mshtml/htmlelem.c:6554 error: patch failed: dlls/mshtml/tests/dom.js:98 error: patch failed: dlls/mshtml/htmlelem.c:6612 error: patch failed: dlls/mshtml/tests/dom.js:90 Task: Patch failed to apply

1 0

Re: [PATCH v4 7/9] mshtml: Implement previousElementSibling for Elements.
by Marvin 27 Jul '22

27 Jul '22

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=119964 Your paranoid android. === build (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4887 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4926 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6525 error: patch failed: dlls/mshtml/tests/dom.js:89 error: patch failed: dlls/mshtml/htmlelem.c:6561 error: patch failed: dlls/mshtml/tests/dom.js:94 error: patch failed: dlls/mshtml/htmlelem.c:6554 error: patch failed: dlls/mshtml/tests/dom.js:98 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4887 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4926 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6525 error: patch failed: dlls/mshtml/tests/dom.js:89 error: patch failed: dlls/mshtml/htmlelem.c:6561 error: patch failed: dlls/mshtml/tests/dom.js:94 error: patch failed: dlls/mshtml/htmlelem.c:6554 error: patch failed: dlls/mshtml/tests/dom.js:98 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4887 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4926 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6525 error: patch failed: dlls/mshtml/tests/dom.js:89 error: patch failed: dlls/mshtml/htmlelem.c:6561 error: patch failed: dlls/mshtml/tests/dom.js:94 error: patch failed: dlls/mshtml/htmlelem.c:6554 error: patch failed: dlls/mshtml/tests/dom.js:98 Task: Patch failed to apply

1 0

Re: [PATCH v4 6/9] mshtml: Implement nextElementSibling for Elements.
by Marvin 27 Jul '22

27 Jul '22

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=119963 Your paranoid android. === build (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4887 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4926 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6525 error: patch failed: dlls/mshtml/tests/dom.js:89 error: patch failed: dlls/mshtml/htmlelem.c:6561 error: patch failed: dlls/mshtml/tests/dom.js:94 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4887 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4926 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6525 error: patch failed: dlls/mshtml/tests/dom.js:89 error: patch failed: dlls/mshtml/htmlelem.c:6561 error: patch failed: dlls/mshtml/tests/dom.js:94 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4887 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4926 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6525 error: patch failed: dlls/mshtml/tests/dom.js:89 error: patch failed: dlls/mshtml/htmlelem.c:6561 error: patch failed: dlls/mshtml/tests/dom.js:94 Task: Patch failed to apply

1 0

Re: [PATCH v4 5/9] mshtml: Implement lastElementChild for Elements.
by Marvin 27 Jul '22

27 Jul '22

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=119962 Your paranoid android. === build (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4887 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4926 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6525 error: patch failed: dlls/mshtml/tests/dom.js:89 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4887 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4926 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6525 error: patch failed: dlls/mshtml/tests/dom.js:89 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4887 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4926 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6525 error: patch failed: dlls/mshtml/tests/dom.js:89 Task: Patch failed to apply

1 0

Re: [PATCH v4 4/9] mshtml: Implement hasAttributeNS for Elements.
by Marvin 27 Jul '22

27 Jul '22

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=119961 Your paranoid android. === build (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4887 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4926 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4887 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4926 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4887 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4926 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 Task: Patch failed to apply

1 0

Re: [PATCH v4 3/9] mshtml: Implement removeAttributeNS for Elements.
by Marvin 27 Jul '22

27 Jul '22

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=119960 Your paranoid android. === build (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4887 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4887 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4887 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 Task: Patch failed to apply

1 0

Re: [PATCH v4 2/9] mshtml: Implement setAttributeNS for Elements.
by Marvin 27 Jul '22

27 Jul '22

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=119959 Your paranoid android. === build (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 Task: Patch failed to apply

1 0

Re: [PATCH v3 9/9] mshtml: Implement HTMLTitleElement's text property.
by Marvin 27 Jul '22

27 Jul '22

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=119957 Your paranoid android. === build (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4886 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4925 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6524 error: patch failed: dlls/mshtml/tests/dom.js:89 error: patch failed: dlls/mshtml/htmlelem.c:6560 error: patch failed: dlls/mshtml/tests/dom.js:94 error: patch failed: dlls/mshtml/htmlelem.c:6553 error: patch failed: dlls/mshtml/tests/dom.js:98 error: patch failed: dlls/mshtml/htmlelem.c:6611 error: patch failed: dlls/mshtml/tests/dom.js:90 error: patch failed: dlls/mshtml/htmlhead.c:103 error: patch failed: dlls/mshtml/tests/dom.js:533 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4886 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4925 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6524 error: patch failed: dlls/mshtml/tests/dom.js:89 error: patch failed: dlls/mshtml/htmlelem.c:6560 error: patch failed: dlls/mshtml/tests/dom.js:94 error: patch failed: dlls/mshtml/htmlelem.c:6553 error: patch failed: dlls/mshtml/tests/dom.js:98 error: patch failed: dlls/mshtml/htmlelem.c:6611 error: patch failed: dlls/mshtml/tests/dom.js:90 error: patch failed: dlls/mshtml/htmlhead.c:103 error: patch failed: dlls/mshtml/tests/dom.js:533 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4886 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4925 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6524 error: patch failed: dlls/mshtml/tests/dom.js:89 error: patch failed: dlls/mshtml/htmlelem.c:6560 error: patch failed: dlls/mshtml/tests/dom.js:94 error: patch failed: dlls/mshtml/htmlelem.c:6553 error: patch failed: dlls/mshtml/tests/dom.js:98 error: patch failed: dlls/mshtml/htmlelem.c:6611 error: patch failed: dlls/mshtml/tests/dom.js:90 error: patch failed: dlls/mshtml/htmlhead.c:103 error: patch failed: dlls/mshtml/tests/dom.js:533 Task: Patch failed to apply

1 0

Re: [PATCH v3 8/9] mshtml: Implement childElementCount for Elements.
by Marvin 27 Jul '22

27 Jul '22

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=119956 Your paranoid android. === build (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4886 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4925 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6524 error: patch failed: dlls/mshtml/tests/dom.js:89 error: patch failed: dlls/mshtml/htmlelem.c:6560 error: patch failed: dlls/mshtml/tests/dom.js:94 error: patch failed: dlls/mshtml/htmlelem.c:6553 error: patch failed: dlls/mshtml/tests/dom.js:98 error: patch failed: dlls/mshtml/htmlelem.c:6611 error: patch failed: dlls/mshtml/tests/dom.js:90 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4886 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4925 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6524 error: patch failed: dlls/mshtml/tests/dom.js:89 error: patch failed: dlls/mshtml/htmlelem.c:6560 error: patch failed: dlls/mshtml/tests/dom.js:94 error: patch failed: dlls/mshtml/htmlelem.c:6553 error: patch failed: dlls/mshtml/tests/dom.js:98 error: patch failed: dlls/mshtml/htmlelem.c:6611 error: patch failed: dlls/mshtml/tests/dom.js:90 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4886 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4925 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6524 error: patch failed: dlls/mshtml/tests/dom.js:89 error: patch failed: dlls/mshtml/htmlelem.c:6560 error: patch failed: dlls/mshtml/tests/dom.js:94 error: patch failed: dlls/mshtml/htmlelem.c:6553 error: patch failed: dlls/mshtml/tests/dom.js:98 error: patch failed: dlls/mshtml/htmlelem.c:6611 error: patch failed: dlls/mshtml/tests/dom.js:90 Task: Patch failed to apply

1 0

Re: [PATCH v3 7/9] mshtml: Implement previousElementSibling for Elements.
by Marvin 27 Jul '22

27 Jul '22

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=119955 Your paranoid android. === build (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4886 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4925 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6524 error: patch failed: dlls/mshtml/tests/dom.js:89 error: patch failed: dlls/mshtml/htmlelem.c:6560 error: patch failed: dlls/mshtml/tests/dom.js:94 error: patch failed: dlls/mshtml/htmlelem.c:6553 error: patch failed: dlls/mshtml/tests/dom.js:98 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4886 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4925 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6524 error: patch failed: dlls/mshtml/tests/dom.js:89 error: patch failed: dlls/mshtml/htmlelem.c:6560 error: patch failed: dlls/mshtml/tests/dom.js:94 error: patch failed: dlls/mshtml/htmlelem.c:6553 error: patch failed: dlls/mshtml/tests/dom.js:98 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4886 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4925 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6524 error: patch failed: dlls/mshtml/tests/dom.js:89 error: patch failed: dlls/mshtml/htmlelem.c:6560 error: patch failed: dlls/mshtml/tests/dom.js:94 error: patch failed: dlls/mshtml/htmlelem.c:6553 error: patch failed: dlls/mshtml/tests/dom.js:98 Task: Patch failed to apply

1 0

Re: [PATCH v3 6/9] mshtml: Implement nextElementSibling for Elements.
by Marvin 27 Jul '22

27 Jul '22

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=119954 Your paranoid android. === build (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4886 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4925 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6524 error: patch failed: dlls/mshtml/tests/dom.js:89 error: patch failed: dlls/mshtml/htmlelem.c:6560 error: patch failed: dlls/mshtml/tests/dom.js:94 Task: Patch failed to apply === debian11 (build log) === error: patch failed: dlls/mshtml/htmlelem.c:4813 error: patch failed: dlls/mshtml/nsembed.c:998 error: patch failed: dlls/mshtml/htmlelem.c:4845 error: patch failed: dlls/mshtml/tests/documentmode.js:1408 error: patch failed: dlls/mshtml/htmlelem.c:4886 error: patch failed: dlls/mshtml/tests/documentmode.js:1480 error: patch failed: dlls/mshtml/htmlelem.c:4925 error: patch failed: dlls/mshtml/tests/documentmode.js:1418 error: patch failed: dlls/mshtml/htmlelem.c:6524 error: patch failed: dlls/mshtml/tests/dom.js:89 error: patch failed: dlls/mshtml/htmlelem.c:6560 error: patch failed: dlls/mshtml/tests/dom.js:94 Task: Patch failed to apply

1 0

Re: [PATCH v2 5/9] mshtml: Implement lastElementChild for Elements.
by Marvin 27 Jul '22

27 Jul '22

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=119863 Your paranoid android. === w10pro64_zh_CN (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 === w7u_adm (32 bit report) === mshtml: script.c:644: Test failed: L"/index.html?es5.js:date_now: unexpected Date.now() result 1658941745587 expected 1658941745649"

1 0

Re: [PATCH v2 4/9] mshtml: Implement hasAttributeNS for Elements.
by Marvin 27 Jul '22

27 Jul '22

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=119862 Your paranoid android. === w10pro64_en_AE_u8 (64 bit report) === mshtml: script.c:3119: Test failed: ReportResult failed: 80ef0001

1 0

Re: [PATCH v17 6/6] tmp
by Marvin 27 Jul '22

27 Jul '22

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=119907 Your paranoid android. === debian11 (build log) === ../wine/dlls/msvcrt/cpp.c:652:2: error: #error _MSVCR_VER STRINGIFY2(_MSVCR_VER) <command-line>: error: expected identifier or ‘(’ before numeric constant Task: The win32 Wine build failed === debian11 (build log) === ../wine/dlls/msvcrt/cpp.c:652:2: error: #error _MSVCR_VER STRINGIFY2(_MSVCR_VER) <command-line>: error: expected identifier or ‘(’ before numeric constant Task: The wow64 Wine build failed

1 0

Re: [PATCH v16 6/6] tmp
by Marvin 27 Jul '22

27 Jul '22

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=119901 Your paranoid android. === debian11 (build log) === ../wine/dlls/msvcrt/cpp.c:651:19: error: _MSVCR_VER: ../wine/dlls/msvcrt/cpp.c:652:2: error: #error _MSVCR_VER STRINGIFY2(_MSVCR_VER) <command-line>: error: expected identifier or ‘(’ before numeric constant Task: The win32 Wine build failed === debian11 (build log) === ../wine/dlls/msvcrt/cpp.c:651:19: error: _MSVCR_VER: ../wine/dlls/msvcrt/cpp.c:652:2: error: #error _MSVCR_VER STRINGIFY2(_MSVCR_VER) <command-line>: error: expected identifier or ‘(’ before numeric constant Task: The wow64 Wine build failed

1 0

Re: [PATCH v2 3/9] mshtml: Implement removeAttributeNS for Elements.
by Marvin 27 Jul '22

27 Jul '22

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=119861 Your paranoid android. === 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 v2 2/9] mshtml: Implement setAttributeNS for Elements.
by Marvin 27 Jul '22

27 Jul '22

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=119860 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 === w10pro64_ar (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 v7 2/2] win32u/window: Ignore changing WS_EX_TOPMOST for message-only windows.
by Marvin 27 Jul '22

27 Jul '22

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=119828 Your paranoid android. === w10pro64_ja (64 bit report) === user32: win.c:189: Test failed: didn't get start_event win.c:10436: Test failed: WindowFromPoint returned 00000000000902BA, expected 0000000000000000 win.c:10444: Test failed: WindowFromPoint returned 00000000000902BA, expected 0000000000000000 win.c:10447: Test failed: Timed out waiting for the child process win.c:10345: Test failed: WindowFromPoint returned 00000000000302B2, expected 00000000000902BA win.c:10352: Test failed: WindowFromPoint returned 00000000000302B2, expected 00000000000401F0 win.c:10358: Test failed: CreateWindowEx failed win.c:10373: Test failed: transparent window didn't get WM_NCHITTEST message === debian11 (32 bit WoW report) === user32: win.c:9024: Test failed: Did not receive WM_KILLFOCUS

1 0

Re: [PATCH v7 1/2] user32/tests: Check that message-only windows ignore WS_EX_TOPMOST.
by Marvin 27 Jul '22

27 Jul '22

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=119827 Your paranoid android. === w8adm (32 bit report) === user32: win.c:2688: Test failed: style 0x200000: expected !100 win.c:2688: Test failed: style 0x300000: expected !100 === w1064 (64 bit report) === user32: win.c:10976: Test failed: pos = 01400154 === debian11 (32 bit report) === user32: win.c:9026: Test failed: Did not receive WM_KILLFOCUS === debian11 (32 bit WoW report) === user32: win.c:9026: Test failed: Did not receive WM_KILLFOCUS

1 0

Re: [PATCH 2/3] mfplat/tests: Test IMF2DBuffer2::Copy2DTo().
by Marvin 27 Jul '22

27 Jul '22

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=119796 Your paranoid android. === w7u_adm (32 bit report) === mfplat: 085c:mfplat: unhandled exception c0000005 at 6EFC7D1C === w7u_el (32 bit report) === mfplat: 0858:mfplat: unhandled exception c0000005 at 72117D1C

1 0

Re: [PATCH v4 1/5] dinput/tests: Wait for Acquire to complete when injecting input.
by Marvin 27 Jul '22

27 Jul '22

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=119790 Your paranoid android. === w1064_tsign (64 bit report) === dinput: joystick8.c:1606: Test failed: 0x500: WaitForSingleObject failed joystick8.c:1610: Test failed: 0x500: GetDeviceState returned: 0x8007001e joystick8.c:1668: Test failed: 0x500: GetDeviceState returned: 0x8007001e joystick8.c:1669: Test failed: 0x500: got lX 20779 joystick8.c:1670: Test failed: 0x500: got lY 20779 joystick8.c:1671: Test failed: 0x500: got lZ 32767 joystick8.c:1726: Test failed: 0x500: SetProperty DIPROP_JOYSTICKID returned 0x80004001 joystick8.c:1728: Test failed: 0x500: SetProperty DIPROP_AXISMODE returned 0x80070057 joystick8.c:1730: Test failed: 0x500: SetProperty DIPROP_BUFFERSIZE returned 0 joystick8.c:1732: Test failed: 0x500: SetProperty DIPROP_AUTOCENTER returned 0x80070057 joystick8.c:1802: Test failed: 0x500: state[0]: GetDeviceState returned: 0x8007001e joystick8.c:1806: Test failed: 0x500: state[0]: got lX 20779 joystick8.c:1807: Test failed: 0x500: state[0]: got lY 20779 joystick8.c:1809: Test failed: 0x500: state[0]: got lZ 32767 joystick8.c:1802: Test failed: 0x500: state[1]: GetDeviceState returned: 0x8007001e joystick8.c:1806: Test failed: 0x500: state[1]: got lX 20779 joystick8.c:1807: Test failed: 0x500: state[1]: got lY 20779 joystick8.c:1809: Test failed: 0x500: state[1]: got lZ 32767 joystick8.c:1822: Test failed: 0x500: state[1]: WaitForSingleObject failed joystick8.c:1802: Test failed: 0x500: state[2]: GetDeviceState returned: 0x8007001e joystick8.c:1806: Test failed: 0x500: state[2]: got lX 20779 joystick8.c:1807: Test failed: 0x500: state[2]: got lY 20779 joystick8.c:1809: Test failed: 0x500: state[2]: got lZ 32767 joystick8.c:1811: Test failed: 0x500: state[2]: got rgdwPOV[0] -1 joystick8.c:1813: Test failed: 0x500: state[2]: got rgbButtons[0] 0 joystick8.c:1814: Test failed: 0x500: state[2]: got rgbButtons[1] 0 joystick8.c:1822: Test failed: 0x500: state[2]: WaitForSingleObject failed joystick8.c:1802: Test failed: 0x500: state[3]: GetDeviceState returned: 0x8007001e joystick8.c:1806: Test failed: 0x500: state[3]: got lX 20779 joystick8.c:1807: Test failed: 0x500: state[3]: got lY 20779 joystick8.c:1809: Test failed: 0x500: state[3]: got lZ 32767 joystick8.c:1802: Test failed: 0x500: state[4]: GetDeviceState returned: 0x8007001e joystick8.c:1806: Test failed: 0x500: state[4]: got lX 20779 joystick8.c:1807: Test failed: 0x500: state[4]: got lY 20779 joystick8.c:1809: Test failed: 0x500: state[4]: got lZ 32767 joystick8.c:1822: Test failed: 0x500: state[4]: WaitForSingleObject failed joystick8.c:1802: Test failed: 0x500: state[5]: GetDeviceState returned: 0x8007001e joystick8.c:1806: Test failed: 0x500: state[5]: got lX 20779 joystick8.c:1807: Test failed: 0x500: state[5]: got lY 20779 joystick8.c:1809: Test failed: 0x500: state[5]: got lZ 32767 joystick8.c:1813: Test failed: 0x500: state[5]: got rgbButtons[0] 0 joystick8.c:1814: Test failed: 0x500: state[5]: got rgbButtons[1] 0 joystick8.c:1822: Test failed: 0x500: state[5]: WaitForSingleObject failed joystick8.c:1828: Test failed: 0x500: GetDeviceState returned: 0x8007001e joystick8.c:1830: Test failed: 0x500: state[6]: got lX 20779 joystick8.c:1831: Test failed: 0x500: state[6]: got lY 20779 joystick8.c:1832: Test failed: 0x500: state[6]: got lZ 32767 joystick8.c:1834: Test failed: 0x500: state[6]: got rgdwPOV[0] -1 joystick8.c:1836: Test failed: 0x500: state[6]: got rgbButtons[0] 0 joystick8.c:1853: Test failed: 0x500: GetDeviceState returned: 0x8007001e joystick8.c:1856: Test failed: 0x500: state[6]: got lX 20779 joystick8.c:1857: Test failed: 0x500: state[6]: got lY 20779 joystick8.c:1858: Test failed: 0x500: state[6]: got lZ 32767 joystick8.c:1870: Test failed: 0x500: WaitForSingleObject failed joystick8.c:1873: Test failed: 0x500: Unacquire returned: 0x1 joystick8.c:1957: Test failed: 0x500: state[0]: got rgdwPOV[0] -1 joystick8.c:1960: Test failed: 0x500: state[0]: got rgbButtons[1] 0x80 joystick8.c:1953: Test failed: 0x500: state[1]: got lY -25984 joystick8: Timeout

1 0

Re: [PATCH v3 4/5] win32u: Read rawinput device preparsed data using virtual memory.
by Marvin 27 Jul '22

27 Jul '22

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=119786 Your paranoid android. === debian11 (32 bit report) === dinput: joystick8.c:4317: Test failed: GetRawInputDeviceList returned 2 joystick8.c:4334: Test failed: got path L"" joystick8.c:4340: Test failed: got error 3 joystick8.c:4346: Test failed: state[0]: IOCTL_WINETEST_HID_SET_CONTEXT failed, last error 6 joystick8.c:4346: Test failed: state[0]: IOCTL_WINETEST_HID_SEND_INPUT failed, last error 6 joystick8: Timeout === debian11 (32 bit Arabic:Morocco report) === dinput: joystick8.c:4317: Test failed: GetRawInputDeviceList returned 2 joystick8.c:4334: Test failed: got path L"" joystick8.c:4340: Test failed: got error 3 joystick8.c:4346: Test failed: state[0]: IOCTL_WINETEST_HID_SET_CONTEXT failed, last error 6 joystick8.c:4346: Test failed: state[0]: IOCTL_WINETEST_HID_SEND_INPUT failed, last error 6 joystick8: Timeout === debian11 (32 bit German report) === dinput: joystick8.c:4317: Test failed: GetRawInputDeviceList returned 2 joystick8.c:4334: Test failed: got path L"" joystick8.c:4340: Test failed: got error 3 joystick8.c:4346: Test failed: state[0]: IOCTL_WINETEST_HID_SET_CONTEXT failed, last error 6 joystick8.c:4346: Test failed: state[0]: IOCTL_WINETEST_HID_SEND_INPUT failed, last error 6 joystick8: Timeout === debian11 (32 bit French report) === dinput: joystick8.c:4317: Test failed: GetRawInputDeviceList returned 2 joystick8.c:4334: Test failed: got path L"" joystick8.c:4340: Test failed: got error 3 joystick8.c:4346: Test failed: state[0]: IOCTL_WINETEST_HID_SET_CONTEXT failed, last error 6 joystick8.c:4346: Test failed: state[0]: IOCTL_WINETEST_HID_SEND_INPUT failed, last error 6 joystick8: Timeout === debian11 (32 bit Hebrew:Israel report) === dinput: joystick8.c:4317: Test failed: GetRawInputDeviceList returned 2 joystick8.c:4334: Test failed: got path L"" joystick8.c:4340: Test failed: got error 3 joystick8.c:4346: Test failed: state[0]: IOCTL_WINETEST_HID_SET_CONTEXT failed, last error 6 joystick8.c:4346: Test failed: state[0]: IOCTL_WINETEST_HID_SEND_INPUT failed, last error 6 joystick8: Timeout === debian11 (32 bit Hindi:India report) === dinput: joystick8.c:4317: Test failed: GetRawInputDeviceList returned 2 joystick8.c:4334: Test failed: got path L"" joystick8.c:4340: Test failed: got error 3 joystick8.c:4346: Test failed: state[0]: IOCTL_WINETEST_HID_SET_CONTEXT failed, last error 6 joystick8.c:4346: Test failed: state[0]: IOCTL_WINETEST_HID_SEND_INPUT failed, last error 6 joystick8: Timeout === debian11 (32 bit Japanese:Japan report) === dinput: joystick8.c:4317: Test failed: GetRawInputDeviceList returned 2 joystick8.c:4334: Test failed: got path L"" joystick8.c:4340: Test failed: got error 3 joystick8.c:4346: Test failed: state[0]: IOCTL_WINETEST_HID_SET_CONTEXT failed, last error 6 joystick8.c:4346: Test failed: state[0]: IOCTL_WINETEST_HID_SEND_INPUT failed, last error 6 joystick8: Timeout === debian11 (32 bit Chinese:China report) === dinput: joystick8.c:4317: Test failed: GetRawInputDeviceList returned 2 joystick8.c:4334: Test failed: got path L"" joystick8.c:4340: Test failed: got error 3 joystick8.c:4346: Test failed: state[0]: IOCTL_WINETEST_HID_SET_CONTEXT failed, last error 6 joystick8.c:4346: Test failed: state[0]: IOCTL_WINETEST_HID_SEND_INPUT failed, last error 6 joystick8: Timeout === debian11 (64 bit WoW report) === dinput: joystick8.c:4317: Test failed: GetRawInputDeviceList returned 2 joystick8.c:4334: Test failed: got path L"" joystick8.c:4340: Test failed: got error 3 joystick8.c:4346: Test failed: state[0]: IOCTL_WINETEST_HID_SET_CONTEXT failed, last error 6 joystick8.c:4346: Test failed: state[0]: IOCTL_WINETEST_HID_SEND_INPUT failed, last error 6 joystick8: Timeout

1 0

Re: [PATCH v2 4/5] win32u: Read rawinput device preparsed data using virtual memory.
by Marvin 27 Jul '22

27 Jul '22

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=119780 Your paranoid android. === debian11 (32 bit report) === dinput: joystick8.c:4316: Test failed: GetRawInputDeviceList returned 2 joystick8.c:4333: Test failed: got path L"" joystick8.c:4339: Test failed: got error 3 joystick8.c:4345: Test failed: state[0]: IOCTL_WINETEST_HID_SET_CONTEXT failed, last error 6 joystick8.c:4345: Test failed: state[0]: IOCTL_WINETEST_HID_SEND_INPUT failed, last error 6 joystick8: Timeout === debian11 (32 bit Arabic:Morocco report) === dinput: joystick8.c:4316: Test failed: GetRawInputDeviceList returned 2 joystick8.c:4333: Test failed: got path L"" joystick8.c:4339: Test failed: got error 3 joystick8.c:4345: Test failed: state[0]: IOCTL_WINETEST_HID_SET_CONTEXT failed, last error 6 joystick8.c:4345: Test failed: state[0]: IOCTL_WINETEST_HID_SEND_INPUT failed, last error 6 joystick8: Timeout === debian11 (32 bit German report) === dinput: joystick8.c:4316: Test failed: GetRawInputDeviceList returned 2 joystick8.c:4333: Test failed: got path L"" joystick8.c:4339: Test failed: got error 3 joystick8.c:4345: Test failed: state[0]: IOCTL_WINETEST_HID_SET_CONTEXT failed, last error 6 joystick8.c:4345: Test failed: state[0]: IOCTL_WINETEST_HID_SEND_INPUT failed, last error 6 joystick8: Timeout === debian11 (32 bit French report) === dinput: joystick8.c:4316: Test failed: GetRawInputDeviceList returned 2 joystick8.c:4333: Test failed: got path L"" joystick8.c:4339: Test failed: got error 3 joystick8.c:4345: Test failed: state[0]: IOCTL_WINETEST_HID_SET_CONTEXT failed, last error 6 joystick8.c:4345: Test failed: state[0]: IOCTL_WINETEST_HID_SEND_INPUT failed, last error 6 joystick8: Timeout === debian11 (32 bit Hebrew:Israel report) === dinput: joystick8.c:4316: Test failed: GetRawInputDeviceList returned 2 joystick8.c:4333: Test failed: got path L"" joystick8.c:4339: Test failed: got error 3 joystick8.c:4345: Test failed: state[0]: IOCTL_WINETEST_HID_SET_CONTEXT failed, last error 6 joystick8.c:4345: Test failed: state[0]: IOCTL_WINETEST_HID_SEND_INPUT failed, last error 6 joystick8: Timeout === debian11 (32 bit Hindi:India report) === dinput: joystick8.c:4316: Test failed: GetRawInputDeviceList returned 2 joystick8.c:4333: Test failed: got path L"" joystick8.c:4339: Test failed: got error 3 joystick8.c:4345: Test failed: state[0]: IOCTL_WINETEST_HID_SET_CONTEXT failed, last error 6 joystick8.c:4345: Test failed: state[0]: IOCTL_WINETEST_HID_SEND_INPUT failed, last error 6 joystick8: Timeout === debian11 (32 bit Japanese:Japan report) === dinput: joystick8.c:4316: Test failed: GetRawInputDeviceList returned 2 joystick8.c:4333: Test failed: got path L"" joystick8.c:4339: Test failed: got error 3 joystick8.c:4345: Test failed: state[0]: IOCTL_WINETEST_HID_SET_CONTEXT failed, last error 6 joystick8.c:4345: Test failed: state[0]: IOCTL_WINETEST_HID_SEND_INPUT failed, last error 6 joystick8: Timeout === debian11 (32 bit Chinese:China report) === dinput: joystick8.c:4316: Test failed: GetRawInputDeviceList returned 2 joystick8.c:4333: Test failed: got path L"" joystick8.c:4339: Test failed: got error 3 joystick8.c:4345: Test failed: state[0]: IOCTL_WINETEST_HID_SET_CONTEXT failed, last error 6 joystick8.c:4345: Test failed: state[0]: IOCTL_WINETEST_HID_SEND_INPUT failed, last error 6 joystick8: Timeout === debian11 (64 bit WoW report) === dinput: joystick8.c:4316: Test failed: GetRawInputDeviceList returned 2 joystick8.c:4333: Test failed: got path L"" joystick8.c:4339: Test failed: got error 3 joystick8.c:4345: Test failed: state[0]: IOCTL_WINETEST_HID_SET_CONTEXT failed, last error 6 joystick8.c:4345: Test failed: state[0]: IOCTL_WINETEST_HID_SEND_INPUT failed, last error 6 joystick8: Timeout

1 0

Re: [PATCH 1/5] ws2_32/tests: Test send() after TCP reset.
by Marvin 27 Jul '22

27 Jul '22

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=119771 Your paranoid android. === w10pro64_zh_CN (64 bit report) === ws2_32: sock.c:12062: Test failed: got 1. sock.c:12063: Test failed: got 0.

1 0

Re: [PATCH 5/6] dxgi: Build the device list only once in dxgi_output_get_display_mode_list().
by Marvin 27 Jul '22

27 Jul '22

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=119769 Your paranoid android. === debian11 (32 bit report) === Report validation errors: dxgi:dxgi crashed (c0000005) === debian11 (32 bit Chinese:China report) === Report validation errors: dxgi:dxgi crashed (c0000005) === debian11 (32 bit WoW report) === Report validation errors: dxgi:dxgi crashed (c0000005) === debian11 (64 bit WoW report) === dxgi: Unhandled exception: page fault on write access to 0x0000003c00000320 in 64-bit code (0x000000712b01ba).

1 0

Re: [PATCH 4/6] d3d8: Cache the output mode list.
by Marvin 27 Jul '22

27 Jul '22

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=119768 Your paranoid android. === debian11 (32 bit report) === d3d8: Unhandled exception: page fault on read access to 0x007b1000 in 32-bit code (0x714b857f). === debian11 (32 bit WoW report) === d3d8: Unhandled exception: page fault on read access to 0x00112010 in 32-bit code (0x714b857f). === debian11 (64 bit WoW report) === d3d8: device: Timeout

1 0

Re: [PATCH 3/6] d3d9: Cache the output mode list.
by Marvin 27 Jul '22

27 Jul '22

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=119767 Your paranoid android. === debian11 (32 bit report) === d3d8: Unhandled exception: page fault on write access to 0x00001000 in 32-bit code (0x714b575e). Report validation errors: dxgi:dxgi crashed (c0000005) === debian11 (32 bit Chinese:China report) === Report validation errors: dxgi:dxgi crashed (c0000005) === debian11 (32 bit WoW report) === d3d8: Unhandled exception: page fault on write access to 0x00260030 in 32-bit code (0x714b575e). Report validation errors: dxgi:dxgi crashed (c0000005) === debian11 (64 bit WoW report) === d3d8: device: Timeout d3d9: Unhandled exception: page fault on read access to 0xffffffffffffffff in 64-bit code (0x000000712b2dae). dxgi: Unhandled exception: page fault on write access to 0x0000000100000001 in 64-bit code (0x000000712b01ba).

1 0

Re: [PATCH 9/9] mshtml: Implement HTMLTitleElement's text property.
by Marvin 27 Jul '22

27 Jul '22

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=119735 Your paranoid android. === w7u_2qxl (32 bit report) === mshtml: script.c:644: Test failed: L"/index.html?es5.js:date_now: unexpected Date.now() result 1658854080136 expected 1658854080198"

1 0

Re: [PATCH 8/9] mshtml: Implement childElementCount for Elements.
by Marvin 27 Jul '22

27 Jul '22

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=119734 Your paranoid android. === w8 (32 bit report) === mshtml: htmldoc.c:2648: Test failed: unexpected call GetOverrideKeyPath htmldoc.c:2648: Test failed: unexpected call GetOverrideKeyPath htmldoc: Timeout === w1064_tsign (64 bit report) === mshtml: htmldoc: Timeout === w10pro64 (32 bit report) === mshtml: script.c:3119: Test failed: ReportResult failed: 80ef0001 === w864 (testbot log) === WineRunTask.pl:error: The previous 1 run(s) terminated abnormally

1 0

Re: [PATCH 6/9] mshtml: Implement nextElementSibling for Elements.
by Marvin 26 Jul '22

26 Jul '22

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=119732 Your paranoid android. === w10pro64 (testbot log) === WineRunTask.pl:error: The previous 1 run(s) terminated abnormally === w8 (testbot log) === WineRunTask.pl:error: The previous 1 run(s) terminated abnormally

1 0

Re: [PATCH 5/9] mshtml: Implement lastElementChild for Elements.
by Marvin 26 Jul '22

26 Jul '22

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=119731 Your paranoid android. === w1064 (testbot log) === WineRunTask.pl:error: The previous 1 run(s) terminated abnormally

1 0

Re: [PATCH 4/9] mshtml: Implement hasAttributeNS for Elements.
by Marvin 26 Jul '22

26 Jul '22

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=119730 Your paranoid android. === w10pro64_ar (testbot log) === WineRunTask.pl:error: The previous 1 run(s) terminated abnormally

1 0

Re: [PATCH 3/9] mshtml: Implement removeAttributeNS for Elements.
by Marvin 26 Jul '22

26 Jul '22

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=119729 Your paranoid android. === w1064 (testbot log) === WineRunTask.pl:error: The previous 1 run(s) terminated abnormally === w1064v1809 (testbot log) === WineRunTask.pl:error: The previous 1 run(s) terminated abnormally

1 0

Re: [PATCH v8 3/8] scrrun: Test MoveFolder with already existing destination.
by Marvin 26 Jul '22

26 Jul '22

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=119740 Your paranoid android. === w1064v1507 (testbot log) === WineRunTask.pl:error: The previous 1 run(s) terminated abnormally

1 0

Re: [PATCH v8 2/8] scrrun: Check for null and empty arguments in MoveFolder.
by Marvin 26 Jul '22

26 Jul '22

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=119739 Your paranoid android. === w864 (testbot log) === WineRunTask.pl:error: The previous 1 run(s) terminated abnormally === w10pro64_ja (testbot log) === WineRunTask.pl:error: The previous 1 run(s) terminated abnormally

1 0

Re: [PATCH v2 1/1] ntdll: Restore the timezone bias cache.
by Marvin 26 Jul '22

26 Jul '22

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=119688 Your paranoid android. === debian11 (32 bit WoW report) === ntdll: change.c:277: Test failed: should be ready

1 0

Re: [PATCH 1/1] ntdll: Restore the timezone bias cache.
by Marvin 26 Jul '22

26 Jul '22

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=119676 Your paranoid android. === debian11 (32 bit report) === ntdll: time.c:473: Test failed: got USD bias 180000000000, ntdll bias 18446744073320925184 === debian11 (32 bit Chinese:China report) === ntdll: time.c:473: Test failed: got USD bias 180000000000, ntdll bias 18446744073320925184 === debian11 (32 bit WoW report) === ntdll: time.c:473: Test failed: got USD bias 180000000000, ntdll bias 18446744073320925184

1 0

Re: [Mingw-w64-public] How to fix error with macros in d3d12?
by Zebediah Figura 26 Jul '22

26 Jul '22

(+ wine-devel) On 6/11/22 13:26, LIU Hao wrote: > 在 2022-06-12 01:59, Zebediah Figura 写道: >>> The combination of `extern` with `__gnu_inline__` is necessary to suppress generation of a function >>> body if the attached function could not be inlined when compiling as C99. >> >> Why do we need that? >> > > Otherwise there would be errors about multiple definitions. > > >>> I don't think there is >>> anything we can do with these headers. Perhaps WIDL should not generate `static` for `FORCEINLINE` >>> functions; or, if that is not an option, `static __inline__` might be a better alternative. >> >> Is it legal to use 'static __forceinline' or 'extern __forceinline' with MSVC? If so I imagine we >> should find a solution that allows them. >> > > Yes, unfortunately. I don't think there is a solution. `extern inline` and `inline` are not > equivalent in C. > > Right, so, apparently MSVC treats both "inline" and "__forceinline" as magic bullets—they can both appear with or without 'static' and 'extern'; they'll always generate a function body but can also be defined in multiple source files (in fact, if the definition differs and the functions aren't static, an arbitrary one is picked and no warning is even printed.) And for good measure you can always take the address too. [So as far as I can tell there's no difference between "inline" and "extern inline" as far as MSVC is concerned.] I guess we can't do anything about that without modifying the language. But of course in lieu of that we should probably fix our headers. I see at least three options: (1) Use "FORCEINLINE" instead of "static FORCEINLINE" for these functions. MSVC never uses FORCEINLINE with static or extern, so this would be more consistent. The downside is we'd need to provide import library definitions for all of these functions, though, which seems less than ideal. (Unless combined with option 3 below.) (2) Use "static inline" for COM wrappers. This of course drops the __always_inline__ attribute. I'm inclined to assert that's a non-issue, but then again I never really saw the point of __always_inline__ anyway. [I guess it can be used to force the compiler to inline even when -finline isn't enough, but surely that would never be the case here...] (2b) Or use "static inline __attribute((__always_inline__))", and define a new macro to encapsulate that. (3) Define __forceinline as "static inline" rather than "extern inline". I have to assume there was a reason this wasn't done in the first place, but there's no documentation in the file and I couldn't easily find discussion about it. As far as I can tell this actually matches MSVC almost exactly, except that multiple definitions will be generated if something takes the function address. That is arguably a break in behaviour which is worse than just failing to link, though. I think my preferred solution is 2 (or 2b I guess). I'm planning to send the attached patch to winehq (since we need to sync widl from there), but I'd like to hear some feedback from the mingw-w64 project first. ἔρρωσθε, Zeb

4 4

Re: [PATCH v3 10/10] mshtml: Inform Gecko of progress done via OnProgress.
by Marvin 26 Jul '22

26 Jul '22

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=119640 Your paranoid android. === w10pro64_en_AE_u8 (64 bit report) === mshtml: events: Timeout

1 0

Re: [PATCH v3 1/3] riched20/tests: When selection is out of view, the scrollbar should move.
by Marvin 25 Jul '22

25 Jul '22

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=119647 Your paranoid android. === w7u_el (32 bit report) === riched20: editor.c:6665: Test failed: wrong event mask (0x0) during WM_COMMAND

1 0

Re: [PATCH v3 07/10] mshtml: Implement ProgressEvent's lengthComputable prop.
by Marvin 25 Jul '22

25 Jul '22

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=119637 Your paranoid android. === w7u_adm (32 bit report) === mshtml: script.c:644: Test failed: L"/index.html?es5.js:date_now: unexpected Date.now() result 1658779373399 expected 1658779373461"

1 0

Re: [PATCH v3 06/10] mshtml: Fix copy-paste mistake in test message.
by Marvin 25 Jul '22

25 Jul '22

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=119636 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

1 0

Re: [PATCH v3 7/7] dinput/tests: Test GetObjectInfo() with three sliders and a proper format.
by Marvin 25 Jul '22

25 Jul '22

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=119623 Your paranoid android. === w1064_tsign (64 bit report) === dinput: joystick8: Timeout

1 0

Re: [PATCH v3 6/7] dinput/tests: Assert that we can't get info about the third slider with c_dfDIJoystick2.
by Marvin 25 Jul '22

25 Jul '22

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=119622 Your paranoid android. === w8 (32 bit report) === dinput: joystick8.c:1803: Test failed: 0x700: state[0]: WaitForSingleObject succeeded

1 0

Re: [PATCH v3 1/7] dinput: Set correct object names for dials and sliders.
by Marvin 25 Jul '22

25 Jul '22

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=119617 Your paranoid android. === w8 (32 bit report) === dinput: joystick8.c:1836: Test failed: 0x700: state[0]: WaitForSingleObject succeeded

1 0

Re: [PATCH v2 7/7] dinput/tests: Test GetObjectInfo() with three sliders and a proper format.
by Marvin 25 Jul '22

25 Jul '22

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=119555 Your paranoid android. === w8 (32 bit report) === dinput: joystick8.c:1803: Test failed: 0x700: state[0]: WaitForSingleObject succeeded

1 0

Re: [PATCH v2 6/7] dinput/tests: Assert that we can't get info about the third slider with c_dfDIJoystick2.
by Marvin 25 Jul '22

25 Jul '22

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=119554 Your paranoid android. === w8 (32 bit report) === dinput: joystick8.c:1803: Test failed: 0x500: state[0]: WaitForSingleObject succeeded

1 0

Re: [PATCH v2 5/7] dinput: Use GUID_Slider type for dials.
by Marvin 25 Jul '22

25 Jul '22

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=119553 Your paranoid android. === w8 (32 bit report) === dinput: joystick8.c:1803: Test failed: 0x700: state[0]: WaitForSingleObject succeeded

1 0

Re: [PATCH v2 3/7] dinput/tests: Use helper for checking device object instances.
by Marvin 25 Jul '22

25 Jul '22

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=119551 Your paranoid android. === w8 (32 bit report) === dinput: joystick8.c:1803: Test failed: 0x500: state[0]: WaitForSingleObject succeeded

1 0

Re: [PATCH v4 2/2] mfplat/tests: Merge and reorganize image format tests.
by Marvin 25 Jul '22

25 Jul '22

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=119548 Your paranoid android. === w7u_2qxl (32 bit report) === mfplat: 0124:mfplat: unhandled exception c0000005 at 6ECF7D1C === w7u_el (32 bit report) === mfplat: 085c:mfplat: unhandled exception c0000005 at 72297D1C

1 0

Re: [PATCH v4 1/2] mfplat/tests: Mark some tests as broken on Win 8 and 10 v1507.
by Marvin 25 Jul '22

25 Jul '22

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=119547 Your paranoid android. === w7u_adm (32 bit report) === mfplat: 0884:mfplat: unhandled exception c0000005 at 6EFB7D1C

1 0

Re: [PATCH v2 09/10] mshtml: Implement ProgressEvent's total prop.
by Marvin 23 Jul '22

23 Jul '22

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=119500 Your paranoid android. === w10pro64_ja (testbot log) === WineRunTask.pl:error: The previous 1 run(s) terminated abnormally

1 0

Testbot outage
by Jeremy White 23 Jul '22

23 Jul '22

Hi all, We are moving offices. As a result, the WineHQ testnet that powers testbot will be unavailable for some time, starting at 1:30 CDT. It will hopefully just be for the afternoon. Cheers, Jeremy

3 2

Re: [PATCH v2 07/10] mshtml: Implement ProgressEvent's lengthComputable prop.
by Marvin 22 Jul '22

22 Jul '22

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=119498 Your paranoid android. === w1064v1507 (64 bit report) === mshtml: events: Timeout

1 0

Re: [PATCH v2 1/8] dlls/msvcrt: improve support for template in methods
by Marvin 22 Jul '22

22 Jul '22

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=119463 Your paranoid android. === debian11 (32 bit report) === msvcrt: cpp.c:1310: Test failed: 136: Got name "public: __cdecl foo<double>::operator <int>int(void) __ptr64" cpp.c:1313: Test failed: 136: Expected "public: __cdecl foo<double>::operator<int> int(void) __ptr64" === debian11 (32 bit Arabic:Morocco report) === msvcrt: cpp.c:1310: Test failed: 136: Got name "public: __cdecl foo<double>::operator <int>int(void) __ptr64" cpp.c:1313: Test failed: 136: Expected "public: __cdecl foo<double>::operator<int> int(void) __ptr64" === debian11 (32 bit German report) === msvcrt: cpp.c:1310: Test failed: 136: Got name "public: __cdecl foo<double>::operator <int>int(void) __ptr64" cpp.c:1313: Test failed: 136: Expected "public: __cdecl foo<double>::operator<int> int(void) __ptr64" === debian11 (32 bit French report) === msvcrt: cpp.c:1310: Test failed: 136: Got name "public: __cdecl foo<double>::operator <int>int(void) __ptr64" cpp.c:1313: Test failed: 136: Expected "public: __cdecl foo<double>::operator<int> int(void) __ptr64" === debian11 (32 bit Hebrew:Israel report) === msvcrt: cpp.c:1310: Test failed: 136: Got name "public: __cdecl foo<double>::operator <int>int(void) __ptr64" cpp.c:1313: Test failed: 136: Expected "public: __cdecl foo<double>::operator<int> int(void) __ptr64" === debian11 (32 bit Hindi:India report) === msvcrt: cpp.c:1310: Test failed: 136: Got name "public: __cdecl foo<double>::operator <int>int(void) __ptr64" cpp.c:1313: Test failed: 136: Expected "public: __cdecl foo<double>::operator<int> int(void) __ptr64" === debian11 (32 bit Japanese:Japan report) === msvcrt: cpp.c:1310: Test failed: 136: Got name "public: __cdecl foo<double>::operator <int>int(void) __ptr64" cpp.c:1313: Test failed: 136: Expected "public: __cdecl foo<double>::operator<int> int(void) __ptr64" === debian11 (32 bit Chinese:China report) === msvcrt: cpp.c:1310: Test failed: 136: Got name "public: __cdecl foo<double>::operator <int>int(void) __ptr64" cpp.c:1313: Test failed: 136: Expected "public: __cdecl foo<double>::operator<int> int(void) __ptr64" === debian11 (32 bit WoW report) === msvcrt: cpp.c:1310: Test failed: 136: Got name "public: __cdecl foo<double>::operator <int>int(void) __ptr64" cpp.c:1313: Test failed: 136: Expected "public: __cdecl foo<double>::operator<int> int(void) __ptr64" === debian11 (64 bit WoW report) === msvcrt: cpp.c:1310: Test failed: 136: Got name "public: __cdecl foo<double>::operator <int>int(void) __ptr64" cpp.c:1313: Test failed: 136: Expected "public: __cdecl foo<double>::operator<int> int(void) __ptr64"

1 0

Re: [PATCH 2/8] dinput/test: Print the expected values in check_ macros.
by Marvin 22 Jul '22

22 Jul '22

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=119447 Your paranoid android. === w8 (32 bit report) === dinput: joystick8.c:1836: Test failed: 0x700: state[0]: WaitForSingleObject succeeded === w1064_tsign (testbot log) === WineRunTask.pl:error: The previous 1 run(s) terminated abnormally

1 0

Re: [PATCH 2/3] shell32: Add SHBindToFolderIDListParent tests.
by Marvin 22 Jul '22

22 Jul '22

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=119429 Your paranoid android. === w1064_2qxl (64 bit report) === shell32: shlfolder.c:4992: Test failed: RMDIR: expected notification type 10, got: 40000 === w1064_adm (64 bit report) === shell32: shlfolder.c:4992: Test failed: MKDIR: expected notification type 8, got: 40000 === w1064_tsign (64 bit report) === shell32: shlfolder.c:5009: Test failed: Didn't expect a WM_USER_NOTIFY message (event: 2) === debian11 (32 bit report) === shell32: shlfolder.c:5549: Test failed: got DEADBEEF === debian11 (32 bit Arabic:Morocco report) === shell32: shlfolder.c:5549: Test failed: got DEADBEEF === debian11 (32 bit German report) === shell32: shlfolder.c:5549: Test failed: got DEADBEEF === debian11 (32 bit French report) === shell32: shlfolder.c:5549: Test failed: got DEADBEEF === debian11 (32 bit Hebrew:Israel report) === shell32: shlfolder.c:5549: Test failed: got DEADBEEF === debian11 (32 bit Hindi:India report) === shell32: shlfolder.c:5549: Test failed: got DEADBEEF === debian11 (32 bit Japanese:Japan report) === shell32: shlfolder.c:5549: Test failed: got DEADBEEF === debian11 (32 bit Chinese:China report) === shell32: shlfolder.c:5549: Test failed: got DEADBEEF === debian11 (32 bit WoW report) === shell32: shlfolder.c:5549: Test failed: got DEADBEEF === debian11 (64 bit WoW report) === shell32: shlfolder.c:5549: Test failed: got 00000000DEADBEEF

1 0

Re: [PATCH 8/8] dinput/tests: Test GetObjectInfo() with three sliders and a proper format.
by Marvin 22 Jul '22

22 Jul '22

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=119453 Your paranoid android. === w8 (32 bit report) === dinput: joystick8.c:1836: Test failed: 0x500: state[0]: WaitForSingleObject succeeded

1 0

Re: [PATCH 4/8] dinputs/tests: Use helper for checking device object instances.
by Marvin 22 Jul '22

22 Jul '22

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=119449 Your paranoid android. === w8 (32 bit report) === dinput: joystick8.c:1836: Test failed: 0x700: state[0]: WaitForSingleObject succeeded

1 0

Re: [PATCH 3/4] ws2_32: Map AFD_POLL_RESET to both POLLHUP and POLLERR.
by Marvin 22 Jul '22

22 Jul '22

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=119426 Your paranoid android. === debian11 (32 bit report) === ws2_32: sock.c:12874: Test failed: got wrong events 0x12 === debian11 (32 bit Arabic:Morocco report) === ws2_32: sock.c:12874: Test failed: got wrong events 0x12 === debian11 (32 bit German report) === ws2_32: sock.c:12874: Test failed: got wrong events 0x12 === debian11 (32 bit French report) === ws2_32: sock.c:12874: Test failed: got wrong events 0x12 === debian11 (32 bit Hebrew:Israel report) === ws2_32: sock.c:12874: Test failed: got wrong events 0x12 === debian11 (32 bit Hindi:India report) === ws2_32: sock.c:12874: Test failed: got wrong events 0x12 === debian11 (32 bit Japanese:Japan report) === ws2_32: sock.c:12874: Test failed: got wrong events 0x12 === debian11 (32 bit Chinese:China report) === ws2_32: sock.c:12874: Test failed: got wrong events 0x12 === debian11 (32 bit WoW report) === ws2_32: sock.c:12874: Test failed: got wrong events 0x12 === debian11 (64 bit WoW report) === ws2_32: sock.c:12874: Test failed: got wrong events 0x12

1 0

Re: [PATCH v2 6/9] win32u/tests: Add tests for catching exceptions from timer proc.
by Marvin 22 Jul '22

22 Jul '22

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=119391 Your paranoid android. === build (build log) === error: patch failed: dlls/user32/message.c:856 error: patch failed: dlls/user32/user_private.h:89 error: patch failed: dlls/user32/winproc.c:719 error: patch failed: dlls/win32u/message.c:2952 error: patch failed: include/ntuser.h:276 error: patch failed: dlls/user32/message.c:877 error: patch failed: dlls/win32u/message.c:2496 error: patch failed: dlls/win32u/sysparams.c:4880 error: patch failed: dlls/win32u/win32u_private.h:436 error: patch failed: include/ntuser.h:902 error: patch failed: dlls/user32/message.c:597 error: patch failed: dlls/win32u/hook.c:60 error: patch failed: dlls/win32u/message.c:109 error: patch failed: dlls/win32u/tests/win32u.c:425 error: patch failed: dlls/win32u/win32u_private.h:391 error: patch failed: dlls/ntdll/signal_arm.c:533 error: patch failed: dlls/ntdll/signal_arm64.c:576 error: patch failed: dlls/ntdll/signal_i386.c:257 error: patch failed: dlls/ntdll/signal_x86_64.c:661 error: patch failed: dlls/ntdll/unix/signal_arm.c:721 error: patch failed: dlls/ntdll/unix/signal_arm64.c:730 error: patch failed: dlls/ntdll/unix/signal_i386.c:1575 error: patch failed: dlls/ntdll/unix/signal_x86_64.c:2327 error: patch failed: dlls/win32u/gdiobj.c:1158 error: patch failed: dlls/win32u/message.c:2514 error: patch failed: dlls/win32u/syscall.c:117 error: patch failed: dlls/win32u/win32u.spec:839 error: patch failed: dlls/win32u/win32u_private.h:215 error: patch failed: dlls/win32u/wrappers.c:855 error: patch failed: dlls/wow64win/syscall.h:104 error: patch failed: dlls/wow64win/user.c:78 error: patch failed: dlls/win32u/tests/win32u.c:632 Task: Patch failed to apply

1 0

Re: [PATCH v2 3/9] win32u: Avoid using client callbacks for NtUserSendMessage.
by Marvin 22 Jul '22

22 Jul '22

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=119388 Your paranoid android. === build (build log) === error: patch failed: dlls/user32/message.c:856 error: patch failed: dlls/user32/user_private.h:89 error: patch failed: dlls/user32/winproc.c:719 error: patch failed: dlls/win32u/message.c:2952 error: patch failed: include/ntuser.h:276 error: patch failed: dlls/user32/message.c:877 error: patch failed: dlls/win32u/message.c:2496 error: patch failed: dlls/win32u/sysparams.c:4880 error: patch failed: dlls/win32u/win32u_private.h:436 error: patch failed: include/ntuser.h:902 error: patch failed: dlls/user32/message.c:597 error: patch failed: dlls/win32u/hook.c:60 error: patch failed: dlls/win32u/message.c:109 error: patch failed: dlls/win32u/tests/win32u.c:425 error: patch failed: dlls/win32u/win32u_private.h:391 Task: Patch failed to apply

1 0

Re: [PATCH 3/4] server: Report the socket error in sock_poll_event() on POLLERR or POLLHUP.
by Marvin 22 Jul '22

22 Jul '22

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=119378 Your paranoid android. === build (build log) === error: patch failed: server/sock.c:1090 error: patch failed: server/sock.c:645 error: patch failed: dlls/ws2_32/tests/afd.c:162 error: patch failed: server/sock.c:1145 Task: Patch failed to apply

1 0

Re: [PATCH 1/1] d3d11: Use CRT allocation functions.
by Marvin 22 Jul '22

22 Jul '22

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=119444 Your paranoid android. === debian11 (64 bit WoW report) === d3d11: d3d11.c:1567: Test succeeded inside todo block: d3d11.c:1570: Test succeeded inside todo block: Got unexpected hr 0. d3d11.c:1570: Test succeeded inside todo block: d3d11.c:1570: Test succeeded inside todo block: Got unexpected hr 0.

1 0

Re: [PATCH 3/3] shell32: Reimplement SHBindToParent.
by Marvin 22 Jul '22

22 Jul '22

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=119430 Your paranoid android. === debian11 (32 bit report) === shell32: shlfolder.c:5549: Test failed: got DEADBEEF === debian11 (32 bit Chinese:China report) === shell32: shlfolder.c:5549: Test failed: got DEADBEEF === debian11 (32 bit WoW report) === shell32: shlfolder.c:5549: Test failed: got DEADBEEF === debian11 (64 bit WoW report) === shell32: shlfolder.c:5549: Test failed: got 00000000DEADBEEF

1 0

Re: [PATCH v4] ntdll: Add RtlGetDeviceFamilyInfoEnum and RtlConvertDeviceFamilyInfoToString
by Kacper Rączy 21 Jul '22

21 Jul '22

Is there anything else to be changed there, to get this accepted? BR, Kacper > > Wiadomość napisana przez Kacper rączy <gfw.kra(a)gmail.com> w dniu 06.07.2022, o godz. 14:10: > > >> === debian11 (64 bit WoW report) === >> ntdll: >> env.c:461: Test failed: wrong end ptr 000000000086195C/0000000000861960 > It also fails without the patch on my machine.

1 0

Re: [PATCH 1/3] wined3d: Do not try to unmap already unmapped BOs in wined3d_buffer_update_sub_resource().
by Marvin 21 Jul '22

21 Jul '22

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=119373 Your paranoid android. === debian11 (build log) === WineRunWineTest.pl:error: The previous 1 run(s) terminated abnormally

1 0

[PATCH 2/2] kernel32: Implement GetFileMUIInfo.
by Dmitry Timoshkov 21 Jul '22

21 Jul '22

Signed-off-by: Dmitry Timoshkov <dmitry(a)baikal.ru> --- dlls/kernel32/tests/resource.c | 7 ++ dlls/kernelbase/locale.c | 145 ++++++++++++++++++++++++++++++++- 2 files changed, 149 insertions(+), 3 deletions(-) diff --git a/dlls/kernel32/tests/resource.c b/dlls/kernel32/tests/resource.c index 626645a8979..f8a49990e6b 100644 --- a/dlls/kernel32/tests/resource.c +++ b/dlls/kernel32/tests/resource.c @@ -617,6 +617,7 @@ static void test_GetFileMUIInfo(void) ret = GetFileMUIInfo(0, path, info, &size); ok(!ret, "GetFileMUIInfo should fail\n"); ok(GetLastError() == ERROR_INVALID_PARAMETER, "got %lu\n", GetLastError()); + todo_wine ok(!size, "got %lu\n", size); ok(info->dwSize == sizeof(*info), "got %lu\n", info->dwSize); ok(!info->dwVersion, "got %08lx\n", info->dwVersion); @@ -653,7 +654,9 @@ static void test_GetFileMUIInfo(void) full_size = 0; SetLastError(0xdeadbeef); ret = GetFileMUIInfo(MUI_QUERY_ALL, path, NULL, &full_size); + todo_wine ok(!ret, "GetFileMUIInfo should fail\n"); + todo_wine ok(GetLastError() == ERROR_INSUFFICIENT_BUFFER, "got %lu\n", GetLastError()); memset(buf, 0, sizeof(buf)); @@ -666,7 +669,9 @@ static void test_GetFileMUIInfo(void) ok(!ret, "GetFileMUIInfo should fail\n"); ok(GetLastError() == ERROR_INVALID_PARAMETER, "got %lu\n", GetLastError()); ok(info->dwVersion == 0, "got %08lx\n", info->dwVersion); + todo_wine ok(info->dwFileType == 0, "got %08lx\n", info->dwFileType); + todo_wine ok(!memcmp(info->abBuffer, zero, 8), "got %.8s\n", info->abBuffer); memset(buf, 0, sizeof(buf)); @@ -700,8 +705,10 @@ static void test_GetFileMUIInfo(void) ret = GetFileMUIInfo(MUI_QUERY_ALL, path, info, &size); ok(!ret, "GetFileMUIInfo should fail\n"); ok(GetLastError() == ERROR_INVALID_PARAMETER, "got %lu\n", GetLastError()); + todo_wine ok(size == 0, "got %08lx\n", size); ok(info->dwVersion == 0, "got %08lx\n", info->dwVersion); + todo_wine ok(info->dwFileType == 0, "got %08lx\n", info->dwFileType); ok(!memcmp(info->abBuffer, zero, 8), "got %.8s\n", info->abBuffer); diff --git a/dlls/kernelbase/locale.c b/dlls/kernelbase/locale.c index 0c20c858a7a..19c4707cec8 100644 --- a/dlls/kernelbase/locale.c +++ b/dlls/kernelbase/locale.c @@ -5699,15 +5699,154 @@ done: } +typedef struct +{ + DWORD dwSignature; + DWORD dwSize; + DWORD dwVersion; + DWORD unknown1; + DWORD unknown2; + DWORD unknown3; + DWORD dwFileType; + BYTE pServiceChecksum[16]; + BYTE pChecksum[16]; + DWORD unknown4[6]; + DWORD dwTypeNameMainOffset; + DWORD dwTypeNameMainSize; + DWORD dwTypeIDMainOffset; + DWORD dwTypeIDMainSize; + DWORD dwTypeNameMUIOffset; + DWORD dwTypeNameMUISize; + DWORD dwTypeIDMUIOffset; + DWORD dwTypeIDMUISize; + DWORD unknown5; + DWORD unknown6; + DWORD dwLanguageNameOffset; + DWORD dwLanguageNameSize; +} MUI_RC_CONFIG; + /****************************************************************************** * GetFileMUIInfo (kernelbase.@) */ BOOL WINAPI /* DECLSPEC_HOTPATCH */ GetFileMUIInfo( DWORD flags, const WCHAR *path, FILEMUIINFO *info, DWORD *size ) { - FIXME( "stub: %lu, %s, %p, %p\n", flags, debugstr_w(path), info, size ); - SetLastError( ERROR_CALL_NOT_IMPLEMENTED ); - return FALSE; + HMODULE module; + HRSRC rsrc; + MUI_RC_CONFIG *rc_cfg; + DWORD rc_size; + + TRACE( "(%08lx,%s,%p,%p)\n", flags, debugstr_w(path), info, size ); + + if (!size) + { + SetLastError( ERROR_INVALID_PARAMETER ); + return FALSE; + } + + if (info) + { + if (*size < sizeof(FILEMUIINFO)) + { + SetLastError( ERROR_INSUFFICIENT_BUFFER ); + return FALSE; + } + + if (*size != info->dwSize || !info->dwVersion) + { + SetLastError( ERROR_INVALID_PARAMETER ); + return FALSE; + } + } + else if (*size) + { + SetLastError( ERROR_INVALID_PARAMETER ); + return FALSE; + } + + module = LoadLibraryExW( path, 0, LOAD_LIBRARY_AS_IMAGE_RESOURCE | LOAD_LIBRARY_AS_DATAFILE ); + if (!module) return FALSE; + + rsrc = FindResourceW( module, MAKEINTRESOURCEW(1), L"MUI" ); + if (!rsrc) + { + FreeLibrary( module ); + return FALSE; + } + + rc_cfg = LockResource( LoadResource( module, rsrc ) ); + + rc_size = sizeof(*info); + if (flags & MUI_QUERY_RESOURCE_TYPES) + { + rc_size += rc_cfg->dwTypeNameMainSize; + rc_size += rc_cfg->dwTypeIDMainSize; + rc_size += rc_cfg->dwTypeNameMUISize; + rc_size += rc_cfg->dwTypeIDMUISize; + } + if (flags & MUI_QUERY_LANGUAGE_NAME) + rc_size += rc_cfg->dwLanguageNameSize; + + if (info) + { + char *p = (char *)(info + 1); + DWORD offset = sizeof(*info); + + memset( (char *)info + 8, 0, *size - 8 ); /* keep original dwSize/dwVersion */ + + if (flags & MUI_QUERY_TYPE) + info->dwFileType = rc_cfg->dwFileType; + + if (flags & MUI_QUERY_CHECKSUM) + { + memcpy( info->pChecksum, rc_cfg->pChecksum, sizeof(info->pChecksum) ); + memcpy( info->pServiceChecksum, rc_cfg->pServiceChecksum, sizeof(info->pServiceChecksum) ); + } + + if (*size < rc_size) + { + FreeLibrary( module ); + SetLastError( ERROR_INSUFFICIENT_BUFFER ); + return FALSE; + } + + if (flags & MUI_QUERY_RESOURCE_TYPES) + { + info->dwTypeNameMainOffset = offset; + memcpy( p, (char *)rc_cfg + rc_cfg->dwTypeNameMainOffset, rc_cfg->dwTypeNameMainSize ); + p += rc_cfg->dwTypeNameMainSize; + offset += rc_cfg->dwTypeNameMainSize; + + info->dwTypeIDMainOffset = offset; + info->dwTypeIDMainSize = rc_cfg->dwTypeIDMainSize / sizeof(DWORD); + memcpy( p, (char *)rc_cfg + rc_cfg->dwTypeIDMainOffset, rc_cfg->dwTypeIDMainSize ); + p += rc_cfg->dwTypeIDMainSize; + offset += rc_cfg->dwTypeIDMainSize; + + info->dwTypeNameMUIOffset = offset; + memcpy( p, (char *)rc_cfg + rc_cfg->dwTypeNameMUIOffset, rc_cfg->dwTypeNameMUISize ); + p += rc_cfg->dwTypeNameMUISize; + offset += rc_cfg->dwTypeNameMUISize; + + info->dwTypeIDMUIOffset = offset; + info->dwTypeIDMUISize = rc_cfg->dwTypeIDMUISize / sizeof(DWORD); + memcpy( p, (char *)rc_cfg + rc_cfg->dwTypeIDMUIOffset, rc_cfg->dwTypeIDMUISize ); + p += rc_cfg->dwTypeIDMUISize; + offset += rc_cfg->dwTypeIDMUISize; + } + + if (flags & MUI_QUERY_LANGUAGE_NAME) + { + info->dwLanguageNameOffset = offset; + memcpy( p, (char *)rc_cfg + rc_cfg->dwLanguageNameOffset, rc_cfg->dwLanguageNameSize ); + } + } + else + *size = rc_size; + + FreeLibrary( module ); + + return TRUE; } -- 2.37.1

1 0

[PATCH 1/2] kernel32/tests: Add some tests for GetFileMUIInfo().
by Dmitry Timoshkov 21 Jul '22

21 Jul '22

MUI_RC_CONFIG layout is based on the description from http://hostagebrain.blogspot.com/2015/11/multilingual-user-interface.html Signed-off-by: Dmitry Timoshkov <dmitry(a)baikal.ru> --- dlls/kernel32/tests/resource.c | 235 ++++++++++++++++++++++++++++++++- 1 file changed, 234 insertions(+), 1 deletion(-) diff --git a/dlls/kernel32/tests/resource.c b/dlls/kernel32/tests/resource.c index 6c5bc99c0c5..626645a8979 100644 --- a/dlls/kernel32/tests/resource.c +++ b/dlls/kernel32/tests/resource.c @@ -2,6 +2,7 @@ * Unit test suite for resource functions. * * Copyright 2006 Mike McCormack + * 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 @@ -18,8 +19,10 @@ * Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301, USA */ -#include <windows.h> +#include <stdarg.h> #include <stdio.h> +#include <assert.h> +#include <windows.h> #include "wine/test.h" @@ -520,10 +523,240 @@ static void test_internal_structure(void) ok( EndUpdateResourceW( res, TRUE ), "EndUpdateResourceW failed\n"); } +typedef struct +{ + DWORD dwSignature; + DWORD dwSize; + DWORD dwVersion; + DWORD unknown1; + DWORD unknown2; + DWORD unknown3; + DWORD dwFileType; + BYTE pServiceChecksum[16]; + BYTE pChecksum[16]; + DWORD unknown4[6]; + DWORD dwTypeNameMainOffset; + DWORD dwTypeNameMainSize; + DWORD dwTypeIDMainOffset; + DWORD dwTypeIDMainSize; + DWORD dwTypeNameMUIOffset; + DWORD dwTypeNameMUISize; + DWORD dwTypeIDMUIOffset; + DWORD dwTypeIDMUISize; + DWORD unknown5; + DWORD unknown6; + DWORD dwLanguageNameOffset; + DWORD dwLanguageNameSize; +} MUI_RC_CONFIG; + +static void *offset_to_data(void *base, DWORD offset) +{ + return (char *)base + offset; +} + +static void test_GetFileMUIInfo(void) +{ +#define MUI_QUERY_ALL (MUI_QUERY_TYPE | MUI_QUERY_CHECKSUM | MUI_QUERY_LANGUAGE_NAME | MUI_QUERY_RESOURCE_TYPES) + static const BYTE zero[8]; + static const WCHAR path[] = L"urlmon.dll"; + char buf[1024]; + HRSRC rsrc; + MUI_RC_CONFIG *rc_cfg; + char *p1, *p2; + FILEMUIINFO *info = (FILEMUIINFO *)buf; + DWORD size, full_size; + HMODULE module; + int ret; + + module = LoadLibraryExW(path, 0, LOAD_LIBRARY_AS_IMAGE_RESOURCE | LOAD_LIBRARY_AS_DATAFILE); + ok(module != NULL, "LoadLibraryEx error %lu\n", GetLastError()); + rsrc = FindResourceW(module, MAKEINTRESOURCEW(1), L"MUI"); + todo_wine + ok(rsrc != 0, "MUI resource not found\n"); + if (!rsrc) + { + skip("MUI resource not found\n"); + FreeLibrary(module); + return; + } + rc_cfg = LockResource(LoadResource(module, rsrc)); + ok(rc_cfg->dwVersion == MAKELONG(0,1), "got %08lx\n", rc_cfg->dwVersion); + ok(rc_cfg->dwFileType == MUI_FILETYPE_LANGUAGE_NEUTRAL_MAIN, "got %08lx\n", rc_cfg->dwFileType); + + SetLastError(0xdeadbeef); + ret = GetFileMUIInfo(0, path, NULL, NULL); + ok(!ret, "GetFileMUIInfo should fail\n"); + ok(GetLastError() == ERROR_INVALID_PARAMETER, "got %lu\n", GetLastError()); + + info->dwSize = sizeof(*info); + SetLastError(0xdeadbeef); + ret = GetFileMUIInfo(0, path, info, NULL); + ok(!ret, "GetFileMUIInfo should fail\n"); + ok(GetLastError() == ERROR_INVALID_PARAMETER, "got %lu\n", GetLastError()); + + size = 0xdeadbeef; + SetLastError(0xdeadbeef); + ret = GetFileMUIInfo(MUI_QUERY_ALL, path, NULL, &size); + ok(!ret, "GetFileMUIInfo should fail\n"); + ok(GetLastError() == ERROR_INVALID_PARAMETER, "got %lu\n", GetLastError()); + + size = 0; + ret = GetFileMUIInfo(0, path, NULL, &size); + ok(ret, "GetFileMUIInfo error %lu\n", GetLastError()); + ok(size == sizeof(FILEMUIINFO), "got %lu bytes\n", size); + + memset(info, 0, sizeof(*info)); + size = info->dwSize = sizeof(*info) - 1; + SetLastError(0xdeadbeef); + ret = GetFileMUIInfo(0, path, info, &size); + ok(!ret, "GetFileMUIInfo should fail\n"); + ok(GetLastError() == ERROR_INSUFFICIENT_BUFFER, "got %lu\n", GetLastError()); + + memset(info, 0, sizeof(*info)); + size = info->dwSize = sizeof(*info); + ret = GetFileMUIInfo(0, path, info, &size); + ok(!ret, "GetFileMUIInfo should fail\n"); + ok(GetLastError() == ERROR_INVALID_PARAMETER, "got %lu\n", GetLastError()); + ok(!size, "got %lu\n", size); + ok(info->dwSize == sizeof(*info), "got %lu\n", info->dwSize); + ok(!info->dwVersion, "got %08lx\n", info->dwVersion); + + memset(info, 0, sizeof(*info)); + size = info->dwSize = sizeof(*info); + info->dwVersion = MUI_FILEINFO_VERSION; + ret = GetFileMUIInfo(0, path, info, &size); + ok(ret, "GetFileMUIInfo error %lu\n", GetLastError()); + + memset(buf, 0, sizeof(buf)); + size = info->dwSize = 1; + info->dwVersion = MUI_FILEINFO_VERSION; + info->dwFileType = 0xdeadbeef; + SetLastError(0xdeadbeef); + ret = GetFileMUIInfo(0, path, info, &size); + ok(!ret, "GetFileMUIInfo should fail\n"); + ok(GetLastError() == ERROR_INSUFFICIENT_BUFFER, "got %lu\n", GetLastError()); + ok(info->dwVersion == MUI_FILEINFO_VERSION, "got %08lx\n", info->dwVersion); + ok(info->dwFileType == 0xdeadbeef, "got %08lx\n", info->dwFileType); + + memset(buf, 0, sizeof(buf)); + info->dwSize = sizeof(*info); + size = sizeof(*info) + 1; + info->dwVersion = MUI_FILEINFO_VERSION; + info->dwFileType = 0xdeadbeef; + SetLastError(0xdeadbeef); + ret = GetFileMUIInfo(0, path, info, &size); + ok(!ret, "GetFileMUIInfo should fail\n"); + ok(GetLastError() == ERROR_INVALID_PARAMETER, "got %lu\n", GetLastError()); + ok(info->dwVersion == MUI_FILEINFO_VERSION, "got %08lx\n", info->dwVersion); + ok(info->dwFileType == 0xdeadbeef, "got %08lx\n", info->dwFileType); + + full_size = 0; + SetLastError(0xdeadbeef); + ret = GetFileMUIInfo(MUI_QUERY_ALL, path, NULL, &full_size); + ok(!ret, "GetFileMUIInfo should fail\n"); + ok(GetLastError() == ERROR_INSUFFICIENT_BUFFER, "got %lu\n", GetLastError()); + + memset(buf, 0, sizeof(buf)); + info->dwSize = size = sizeof(*info); + info->dwVersion = 0; + info->dwFileType = 0xdeadbeef; + memcpy(info->abBuffer, "deadbeef", 8); + SetLastError(0xdeadbeef); + ret = GetFileMUIInfo(MUI_QUERY_ALL, path, info, &size); + ok(!ret, "GetFileMUIInfo should fail\n"); + ok(GetLastError() == ERROR_INVALID_PARAMETER, "got %lu\n", GetLastError()); + ok(info->dwVersion == 0, "got %08lx\n", info->dwVersion); + ok(info->dwFileType == 0, "got %08lx\n", info->dwFileType); + ok(!memcmp(info->abBuffer, zero, 8), "got %.8s\n", info->abBuffer); + + memset(buf, 0, sizeof(buf)); + info->dwSize = size = sizeof(*info); + info->dwVersion = 0xdeadbeef; + info->dwFileType = 0xdeadbeef; + memcpy(info->abBuffer, "deadbeef", 8); + SetLastError(0xdeadbeef); + ret = GetFileMUIInfo(MUI_QUERY_ALL, path, info, &size); + ok(!ret, "GetFileMUIInfo should fail\n"); + ok(GetLastError() == ERROR_INSUFFICIENT_BUFFER, "got %lu\n", GetLastError()); + ok(info->dwVersion == 0xdeadbeef, "got %08lx\n", info->dwVersion); + ok(info->dwFileType == MUI_FILETYPE_LANGUAGE_NEUTRAL_MAIN, "got %08lx\n", info->dwFileType); + ok(!memcmp(info->abBuffer, zero, 8), "got %.8s\n", info->abBuffer); + + memset(buf, 0, sizeof(buf)); + info->dwSize = size = sizeof(*info); + info->dwVersion = 0xdeadbeef; + info->dwFileType = 0xdeadbeef; + SetLastError(0xdeadbeef); + ret = GetFileMUIInfo(MUI_QUERY_ALL, path, info, &size); + ok(!ret, "GetFileMUIInfo should fail\n"); + ok(GetLastError() == ERROR_INSUFFICIENT_BUFFER, "got %lu\n", GetLastError()); + ok(info->dwVersion == 0xdeadbeef, "got %08lx\n", info->dwVersion); + ok(info->dwFileType == MUI_FILETYPE_LANGUAGE_NEUTRAL_MAIN, "got %08lx\n", info->dwFileType); + + memset(buf, 0, sizeof(buf)); + info->dwSize = size = full_size; + info->dwVersion = 0; + info->dwFileType = 0xdeadbeef; + ret = GetFileMUIInfo(MUI_QUERY_ALL, path, info, &size); + ok(!ret, "GetFileMUIInfo should fail\n"); + ok(GetLastError() == ERROR_INVALID_PARAMETER, "got %lu\n", GetLastError()); + ok(size == 0, "got %08lx\n", size); + ok(info->dwVersion == 0, "got %08lx\n", info->dwVersion); + ok(info->dwFileType == 0, "got %08lx\n", info->dwFileType); + ok(!memcmp(info->abBuffer, zero, 8), "got %.8s\n", info->abBuffer); + + memset(buf, 0, sizeof(buf)); + info->dwSize = size = full_size; + info->dwVersion = MUI_FILEINFO_VERSION; + info->dwFileType = 0xdeadbeef; + ret = GetFileMUIInfo(MUI_QUERY_ALL, path, info, &size); + ok(ret || broken(GetLastError() == ERROR_INSUFFICIENT_BUFFER) /* Some Win10 versions */, "GetFileMUIInfo error %lu\n", GetLastError()); + while (!ret) /* Try to recover from Win10 breakage */ + { + size += 2; + assert(size <= sizeof(buf)); + info->dwSize = size; + ret = GetFileMUIInfo(MUI_QUERY_ALL, path, info, &size); + } + ok(info->dwVersion == MUI_FILEINFO_VERSION, "got %08lx\n", info->dwVersion); + ok(info->dwFileType == MUI_FILETYPE_LANGUAGE_NEUTRAL_MAIN, "got %08lx\n", info->dwFileType); + + ok(!memcmp(info->pChecksum, rc_cfg->pChecksum, 16), "Checksum doesn't match\n"); + ok(!memcmp(info->pServiceChecksum, rc_cfg->pServiceChecksum, 16), "ServiceChecksum doesn't match\n"); + + p1 = offset_to_data(rc_cfg, rc_cfg->dwLanguageNameOffset); + p2 = offset_to_data(info, info->dwLanguageNameOffset); + ok(!memcmp(p1, p2, rc_cfg->dwLanguageNameSize), "LanguageName doesn't match\n"); + + p1 = offset_to_data(rc_cfg, rc_cfg->dwTypeNameMainOffset); + p2 = offset_to_data(info, info->dwTypeNameMainOffset); + ok(!memcmp(p1, p2, rc_cfg->dwTypeNameMainSize), "TypeNameMain doesn't match\n"); + + p1 = offset_to_data(rc_cfg, rc_cfg->dwTypeIDMainOffset); + p2 = offset_to_data(info, info->dwTypeIDMainOffset); + ok(rc_cfg->dwTypeIDMainSize == info->dwTypeIDMainSize * sizeof(DWORD), "dwTypeIDMainSize %#08lx != %08lx\n", + rc_cfg->dwTypeIDMainSize, info->dwTypeIDMainSize); + ok(!memcmp(p1, p2, rc_cfg->dwTypeIDMainSize), "TypeIDMain doesn't match\n"); + + p1 = offset_to_data(rc_cfg, rc_cfg->dwTypeIDMUIOffset); + p2 = offset_to_data(info, info->dwTypeIDMUIOffset); + ok(rc_cfg->dwTypeIDMUISize == info->dwTypeIDMUISize * sizeof(DWORD), "dwTypeIDMUISize %#08lx != %08lx\n", + rc_cfg->dwTypeIDMUISize, info->dwTypeIDMUISize); + ok(!memcmp(p1, p2, rc_cfg->dwTypeIDMUISize), "TypeIDMUI doesn't match\n"); + + p1 = offset_to_data(rc_cfg, rc_cfg->dwTypeNameMUIOffset); + p2 = offset_to_data(info, info->dwTypeNameMUIOffset); + ok(!memcmp(p1, p2, rc_cfg->dwTypeNameMUISize), "TypeNameMUI doesn't match\n"); + + FreeLibrary(module); +} + START_TEST(resource) { DWORD i; + test_GetFileMUIInfo(); + DeleteFileA( filename ); update_missing_exe(); -- 2.37.1

1 0

[PATCH vkd3d 1/2] vkd3d: Delay adding a command queue to the blocked list until after the op is written.
by Conor McCarthy 20 Jul '22

20 Jul '22

Otherwise the following sequence can occur: 1. A command queue is added to the blocked list during a Wait() call. 2. An unblocking Signal() occurs on the CPU in another thread, flushing the blocked ops, but as no op has been written, the queue is removed from the blocked list. 3. The blocked op is written. 3. Another op is queued and the queue is not re-added to the blocked list because this only happens for the first op. World of Warcraft triggers this issue. Signed-off-by: Conor McCarthy <cmccarthy(a)codeweavers.com> --- libs/vkd3d/command.c | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/libs/vkd3d/command.c b/libs/vkd3d/command.c index d0782e5a..7452128c 100644 --- a/libs/vkd3d/command.c +++ b/libs/vkd3d/command.c @@ -6812,12 +6812,6 @@ static HRESULT STDMETHODCALLTYPE d3d12_command_queue_Wait(ID3D12CommandQueue *if * where multiple queues alias over the same physical queue, so effectively, * we need to manage out-of-order submits ourselves. */ - if (!command_queue->ops_count) - hr = d3d12_device_add_blocked_command_queues(command_queue->device, &command_queue, 1); - - if (FAILED(hr)) - goto done; - if (!(op = d3d12_command_queue_require_space_locked(command_queue))) { hr = E_OUTOFMEMORY; @@ -6829,6 +6823,11 @@ static HRESULT STDMETHODCALLTYPE d3d12_command_queue_Wait(ID3D12CommandQueue *if d3d12_fence_incref(fence); + /* Add the queue to the blocked list after writing the op to ensure the queue isn't + * removed again in another thread because it has no ops. */ + if (command_queue->ops_count == 1) + hr = d3d12_device_add_blocked_command_queues(command_queue->device, &command_queue, 1); + done: vkd3d_mutex_unlock(&command_queue->op_mutex); return hr; -- 2.36.1

3 4

[PATCH vkd3d v2 1/3] tests: Test float4 UAV buffer load store.
by Conor McCarthy 20 Jul '22

20 Jul '22

This currently fails if the shader loads from the UAV, because it causes vkd3d-shader to specify the R32ui format instead of Unknown. Signed-off-by: Conor McCarthy <cmccarthy(a)codeweavers.com> --- v2: Make the load/store test independent of the store test. --- tests/d3d12.c | 92 +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 92 insertions(+) diff --git a/tests/d3d12.c b/tests/d3d12.c index ec5cfb20..57e072e4 100644 --- a/tests/d3d12.c +++ b/tests/d3d12.c @@ -20947,6 +20947,56 @@ static void test_typed_buffer_uav(void) 0x00000000, 0x0002100a, 0x00004001, 0x00000020, 0x0002400a, 0x0a0000a4, 0x0011e0f2, 0x00000000, 0x00100006, 0x00000000, 0x00004002, 0x3f000000, 0x3f000000, 0x3f000000, 0x3f000000, 0x0100003e, }; + static const DWORD cs_vec4_code[] = + { +#if 0 + RWBuffer<float4> buffer; + + [numthreads(8, 1, 1)] + void main(uint3 group_id : SV_groupID, uint group_index : SV_GroupIndex) + { + uint global_index = 8 * group_id.x + group_index; + buffer[global_index] = float4(0.5f, 0.625f, 0.75f, 1.0f); + } +#endif + 0x43425844, 0x37e9fa91, 0x11ca38f4, 0x9d4a70b7, 0x4fd05c45, 0x00000001, 0x000000e0, 0x00000003, + 0x0000002c, 0x0000003c, 0x0000004c, 0x4e475349, 0x00000008, 0x00000000, 0x00000008, 0x4e47534f, + 0x00000008, 0x00000000, 0x00000008, 0x58454853, 0x0000008c, 0x00050050, 0x00000023, 0x0100086a, + 0x0400089c, 0x0011e000, 0x00000000, 0x00005555, 0x0200005f, 0x00024000, 0x0200005f, 0x00021012, + 0x02000068, 0x00000001, 0x0400009b, 0x00000008, 0x00000001, 0x00000001, 0x07000023, 0x00100012, + 0x00000000, 0x0002100a, 0x00004001, 0x00000008, 0x0002400a, 0x0a0000a4, 0x0011e0f2, 0x00000000, + 0x00100006, 0x00000000, 0x00004002, 0x3f000000, 0x3f200000, 0x3f400000, 0x3f800000, 0x0100003e, + }; + static const DWORD cs_vec4_load_code[] = + { + /* Compiled with /Od */ +#if 0 + RWBuffer<float4> buffer; + + [numthreads(4, 1, 1)] + void main(uint3 group_id : SV_groupID, uint group_index : SV_GroupIndex) + { + uint global_index = 8 * group_id.x + group_index * 2u; + buffer[global_index] = float4(0.5f, 0.625f, 0.75f, 1.0f); + buffer[global_index + 1] = buffer[global_index]; + } +#endif + 0x43425844, 0x0b7914da, 0x7379094c, 0xa3567660, 0xeb9df127, 0x00000001, 0x000001b0, 0x00000004, + 0x00000030, 0x00000040, 0x00000050, 0x000001a0, 0x4e475349, 0x00000008, 0x00000000, 0x00000008, + 0x4e47534f, 0x00000008, 0x00000000, 0x00000008, 0x58454853, 0x00000148, 0x00050050, 0x00000052, + 0x0100886a, 0x0400089c, 0x0011e000, 0x00000000, 0x00005555, 0x0200005f, 0x00024000, 0x0200005f, + 0x00021012, 0x02000068, 0x00000002, 0x0400009b, 0x00000004, 0x00000001, 0x00000001, 0x05000036, + 0x00100012, 0x00000000, 0x00004001, 0x00000008, 0x07000026, 0x0000d000, 0x00100012, 0x00000000, + 0x0010000a, 0x00000000, 0x0002100a, 0x07000026, 0x0000d000, 0x00100022, 0x00000000, 0x0002400a, + 0x00004001, 0x00000002, 0x0700001e, 0x00100012, 0x00000000, 0x0010001a, 0x00000000, 0x0010000a, + 0x00000000, 0x0a0000a4, 0x0011e0f2, 0x00000000, 0x00100006, 0x00000000, 0x00004002, 0x3f000000, + 0x3f200000, 0x3f400000, 0x3f800000, 0x05000036, 0x00100022, 0x00000000, 0x00004001, 0x00000001, + 0x0700001e, 0x00100022, 0x00000000, 0x0010001a, 0x00000000, 0x0010000a, 0x00000000, 0x890000a3, + 0x80000042, 0x00155543, 0x001000f2, 0x00000001, 0x00100006, 0x00000000, 0x0011ee46, 0x00000000, + 0x070000a4, 0x0011e0f2, 0x00000000, 0x00100556, 0x00000000, 0x00100e46, 0x00000001, 0x0100003e, + 0x30494653, 0x00000008, 0x00000800, 0x00000000, + }; + static const struct vec4 expected = {0.5f, 0.625f, 0.75f, 1.0f}; if (!init_compute_test_context(&context)) return; @@ -21004,6 +21054,48 @@ static void test_typed_buffer_uav(void) check_readback_data_float(&rb.rb, NULL, 0.5f, 0); release_resource_readback(&rb); + reset_command_list(command_list, context.allocator); + transition_sub_resource_state(command_list, resource, 0, + D3D12_RESOURCE_STATE_COPY_SOURCE, D3D12_RESOURCE_STATE_UNORDERED_ACCESS); + ID3D12PipelineState_Release(pipeline_state); + pipeline_state = create_compute_pipeline_state(device, root_signature, + shader_bytecode(cs_vec4_code, sizeof(cs_vec4_code))); + + uav_desc.Format = DXGI_FORMAT_R32G32B32A32_FLOAT; + uav_desc.Buffer.NumElements = 16; + ID3D12Device_CreateUnorderedAccessView(device, resource, NULL, &uav_desc, cpu_descriptor_handle); + + ID3D12GraphicsCommandList_SetPipelineState(command_list, pipeline_state); + ID3D12GraphicsCommandList_SetComputeRootSignature(command_list, root_signature); + ID3D12GraphicsCommandList_SetComputeRootDescriptorTable(command_list, 0, gpu_descriptor_handle); + ID3D12GraphicsCommandList_Dispatch(command_list, 2, 1, 1); + + transition_sub_resource_state(command_list, resource, 0, + D3D12_RESOURCE_STATE_UNORDERED_ACCESS, D3D12_RESOURCE_STATE_COPY_SOURCE); + + get_buffer_readback_with_command_list(resource, uav_desc.Format, &rb, queue, command_list); + check_readback_data_vec4(&rb.rb, NULL, &expected, 0); + release_resource_readback(&rb); + + reset_command_list(command_list, context.allocator); + transition_sub_resource_state(command_list, resource, 0, + D3D12_RESOURCE_STATE_COPY_SOURCE, D3D12_RESOURCE_STATE_UNORDERED_ACCESS); + ID3D12PipelineState_Release(pipeline_state); + pipeline_state = create_compute_pipeline_state(device, root_signature, + shader_bytecode(cs_vec4_load_code, sizeof(cs_vec4_load_code))); + + ID3D12GraphicsCommandList_SetPipelineState(command_list, pipeline_state); + ID3D12GraphicsCommandList_SetComputeRootSignature(command_list, root_signature); + ID3D12GraphicsCommandList_SetComputeRootDescriptorTable(command_list, 0, gpu_descriptor_handle); + ID3D12GraphicsCommandList_Dispatch(command_list, 2, 1, 1); + + transition_sub_resource_state(command_list, resource, 0, + D3D12_RESOURCE_STATE_UNORDERED_ACCESS, D3D12_RESOURCE_STATE_COPY_SOURCE); + + get_buffer_readback_with_command_list(resource, uav_desc.Format, &rb, queue, command_list); + todo check_readback_data_vec4(&rb.rb, NULL, &expected, 0); + release_resource_readback(&rb); + ID3D12Resource_Release(resource); ID3D12RootSignature_Release(root_signature); ID3D12PipelineState_Release(pipeline_state); -- 2.36.1

2 1

How to propagate Linux device ready for read FD state to Wine proxy WDM driver
by Pavel Pisa 20 Jul '22

20 Jul '22

Dear wine developers, I monitor from time to time Wine development state. I have significant interrest to use it for our open-source chromatography processing and control system CHROMuLAN http://pikron.com/pages/products/hplc/chromulan.html . It runs well under wine for years except for minor problem with excessive size of new analysis setup dialog, it is old Delphi 6 app. If somebody is willing to look at it I give more information or setup issue. But uLAN driver access is required to control real devices and acquire data http://ulan.sourceforge.net/ Driver is available in source form from 1996 year and it has been developed and is maintained on GNU/Linux system but with CHROMuLAN windows build from the same sources is used from Windows NT 3.5 days. I have idea in 2013 year to try implement proxy driver which allows to access native Linux kernel driver from Windows application. I have found at that time that Wine protocol is able to deliver data between wine server driver and application only for IOCTLs, read and write calls has not been implemented for device driver file handle type and I have documented problem on WineHQ list https://www.winehq.org/pipermail/wine-devel/2013-July/thread.html#100409 But when I looked into latest Wine sources I have noticed, that it should not be problem anymore. So I have cleaned from the dust old experiment and updated it for actual Wine. Linux driver interaction has been separated from WDM proxy part and marked (ul_l_drv.c) #if 0 #pragma makedep unix #endif unix calls conversion has been added (ul_l_exports.c) const unixlib_entry_t __wine_unix_call_funcs[] = and real WDM has been used as base for the proxy driver (ul_drv.c, device.c). Both originally based on some Wine driver to emulate disk and other behavior. The code is available there https://cmp.felk.cvut.cz/~pisa/ulan/wine/ul_drv.sys/ and it works with whole CHROMuLAN system. Yes, there is lot of space for cleanups, service is started in manual mode unconditionally etc.. [System\\CurrentControlSet\\Services\\ul_drv] 1658091793 ... "Start"=dword:00000001 etc... There is one missing feature and it is wait for arrival of the new messages without periodic polling. It is easy on Linux side, select, poll, epoll can be used for ready for read. In Windows world select does not work for device drivers so IOCTL is used which marks IoMarkIrpPending, then user can wait for associated overlapped event for example by WaitForSingleObject. I have implemented logic in Wine proxy driver and IRP is marked by IoMarkIrpPending, cancellation and all other stuff seems to work. But I need somehow bind event on Linux native file descriptor which is maintained in makedep unix with some way to mark corresponding IRP in Windows driver part as complete IoCompleteRequest(old_irp,IO_NO_INCREMENT); What are the options? Should, can I can start service thread in makedep unix part and call IoCompleteRequest from there? In the fact I would prefer even more only register callback in the Wise server main loop which would be called when Linux device file descriptor is ready to read. Is there some example how to do something like that? What are locking requirements and limitations? It is more for curiosity now, we experimental port to FPC/Lazarus which runs on Linux and Windows now, but on the other hand there are still some features missing in that build, Lazarus with Gtk does not implement MDI in really usable form etc... So there is still some potential for this and other applications using uLAN to be run under Wine. Thanks for your time and best wishes, Pavel -- Pavel Pisa phone: +420 603531357 e-mail: pisa(a)cmp.felk.cvut.cz Department of Control Engineering FEE CVUT Karlovo namesti 13, 121 35, Prague 2 university: https://control.fel.cvut.cz/ company: https://www.pikron.com/ personal: https://cmp.felk.cvut.cz/~pisa projects: https://www.openhub.net/accounts/ppisa CAN related:http://canbus.pages.fel.cvut.cz/ RISC-V education: https://comparch.edu.cvut.cz/ Open Technologies Research Education and Exchange Services https://gitlab.fel.cvut.cz/otrees/org/-/wikis/home

2 1

Re: [PATCH v3 3/3] mfplat/tests: Merge and reorganize image format tests.
by Marvin 20 Jul '22

20 Jul '22

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=119352 Your paranoid android. === w7u_adm (32 bit report) === mfplat: 0864:mfplat: unhandled exception c0000005 at 6ED77D1C === w7u_el (32 bit report) === mfplat: 0858:mfplat: unhandled exception c0000005 at 72467D24

1 0

Re: [PATCH v3 1/3] mfplat/tests: Mark some tests as broken on Win 8 and 10 v1507.
by Marvin 20 Jul '22

20 Jul '22

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=119350 Your paranoid android. === w7u_el (32 bit report) === mfplat: 089c:mfplat: unhandled exception c0000005 at 722C7D1C

1 0

Re: [PATCH 1/4] ws2_32/tests: Test listen() after a failed connect().
by Marvin 20 Jul '22

20 Jul '22

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=119329 Your paranoid android. === w10pro64_ar (64 bit report) === ws2_32: sock.c:6964: Test failed: got apc_count 1.

1 0

Re: [PATCH 6/6] uiautomationcore: Add support for ProviderOptions_UseComThreading flag.
by Marvin 20 Jul '22

20 Jul '22

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=119322 Your paranoid android. === debian11 (32 bit report) === uiautomationcore: uiautomation.c:3850: Test failed: Unexpected hr 0x80004002. uiautomation.c:3851: Test failed: Unexpected refcnt 1 uiautomation.c:3784: Test failed: Unexpected hr 0x80070057 uiautomation.c:3789: Test failed: Unexpected hr 0x80070057 uiautomation.c:4217: Test failed: Unexpected VT 0 uiautomation.c:4222: Test failed: Unexpected I4 0 uiautomation.c:4223: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3803: Test failed: Unexpected hr 0x80070057 uiautomation.c:4273: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 272 uiautomation.c:4281: Test failed: Unexpected I4 0x23 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3809: Test failed: Unexpected hr 0x80070057 uiautomation.c:4273: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 272 uiautomation.c:4281: Test failed: Unexpected I4 0x23 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3867: Test failed: UiaNodeRelease returned FALSE === debian11 (32 bit Arabic:Morocco report) === uiautomationcore: uiautomation.c:3850: Test failed: Unexpected hr 0x80004002. uiautomation.c:3851: Test failed: Unexpected refcnt 1 uiautomation.c:3784: Test failed: Unexpected hr 0x80070057 uiautomation.c:3789: Test failed: Unexpected hr 0x80070057 uiautomation.c:4217: Test failed: Unexpected VT 0 uiautomation.c:4222: Test failed: Unexpected I4 0 uiautomation.c:4223: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3803: Test failed: Unexpected hr 0x80070057 uiautomation.c:4273: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 272 uiautomation.c:4281: Test failed: Unexpected I4 0x23 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3809: Test failed: Unexpected hr 0x80070057 uiautomation.c:4273: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 272 uiautomation.c:4281: Test failed: Unexpected I4 0x23 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3867: Test failed: UiaNodeRelease returned FALSE === debian11 (32 bit German report) === uiautomationcore: uiautomation.c:3850: Test failed: Unexpected hr 0x80004002. uiautomation.c:3851: Test failed: Unexpected refcnt 1 uiautomation.c:3784: Test failed: Unexpected hr 0x80070057 uiautomation.c:3789: Test failed: Unexpected hr 0x80070057 uiautomation.c:4217: Test failed: Unexpected VT 0 uiautomation.c:4222: Test failed: Unexpected I4 0 uiautomation.c:4223: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3803: Test failed: Unexpected hr 0x80070057 uiautomation.c:4273: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 272 uiautomation.c:4281: Test failed: Unexpected I4 0x23 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3809: Test failed: Unexpected hr 0x80070057 uiautomation.c:4273: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 272 uiautomation.c:4281: Test failed: Unexpected I4 0x23 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3867: Test failed: UiaNodeRelease returned FALSE === debian11 (32 bit French report) === uiautomationcore: uiautomation.c:3850: Test failed: Unexpected hr 0x80004002. uiautomation.c:3851: Test failed: Unexpected refcnt 1 uiautomation.c:3784: Test failed: Unexpected hr 0x80070057 uiautomation.c:3789: Test failed: Unexpected hr 0x80070057 uiautomation.c:4217: Test failed: Unexpected VT 0 uiautomation.c:4222: Test failed: Unexpected I4 0 uiautomation.c:4223: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3803: Test failed: Unexpected hr 0x80070057 uiautomation.c:4273: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 272 uiautomation.c:4281: Test failed: Unexpected I4 0x23 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3809: Test failed: Unexpected hr 0x80070057 uiautomation.c:4273: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 272 uiautomation.c:4281: Test failed: Unexpected I4 0x23 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3867: Test failed: UiaNodeRelease returned FALSE === debian11 (32 bit Hebrew:Israel report) === uiautomationcore: uiautomation.c:3850: Test failed: Unexpected hr 0x80004002. uiautomation.c:3851: Test failed: Unexpected refcnt 1 uiautomation.c:3784: Test failed: Unexpected hr 0x80070057 uiautomation.c:3789: Test failed: Unexpected hr 0x80070057 uiautomation.c:4217: Test failed: Unexpected VT 0 uiautomation.c:4222: Test failed: Unexpected I4 0 uiautomation.c:4223: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3803: Test failed: Unexpected hr 0x80070057 uiautomation.c:4273: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 272 uiautomation.c:4281: Test failed: Unexpected I4 0x23 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3809: Test failed: Unexpected hr 0x80070057 uiautomation.c:4273: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 272 uiautomation.c:4281: Test failed: Unexpected I4 0x23 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3867: Test failed: UiaNodeRelease returned FALSE === debian11 (32 bit Hindi:India report) === uiautomationcore: uiautomation.c:3850: Test failed: Unexpected hr 0x80004002. uiautomation.c:3851: Test failed: Unexpected refcnt 1 uiautomation.c:3784: Test failed: Unexpected hr 0x80070057 uiautomation.c:3789: Test failed: Unexpected hr 0x80070057 uiautomation.c:4217: Test failed: Unexpected VT 0 uiautomation.c:4222: Test failed: Unexpected I4 0 uiautomation.c:4223: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3803: Test failed: Unexpected hr 0x80070057 uiautomation.c:4273: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 272 uiautomation.c:4281: Test failed: Unexpected I4 0x23 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3809: Test failed: Unexpected hr 0x80070057 uiautomation.c:4273: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 272 uiautomation.c:4281: Test failed: Unexpected I4 0x23 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3867: Test failed: UiaNodeRelease returned FALSE === debian11 (32 bit Japanese:Japan report) === uiautomationcore: uiautomation.c:3850: Test failed: Unexpected hr 0x80004002. uiautomation.c:3851: Test failed: Unexpected refcnt 1 uiautomation.c:3784: Test failed: Unexpected hr 0x80070057 uiautomation.c:3789: Test failed: Unexpected hr 0x80070057 uiautomation.c:4217: Test failed: Unexpected VT 0 uiautomation.c:4222: Test failed: Unexpected I4 0 uiautomation.c:4223: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3803: Test failed: Unexpected hr 0x80070057 uiautomation.c:4273: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 272 uiautomation.c:4281: Test failed: Unexpected I4 0x23 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3809: Test failed: Unexpected hr 0x80070057 uiautomation.c:4273: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 272 uiautomation.c:4281: Test failed: Unexpected I4 0x23 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3867: Test failed: UiaNodeRelease returned FALSE === debian11 (32 bit Chinese:China report) === uiautomationcore: uiautomation.c:3850: Test failed: Unexpected hr 0x80004002. uiautomation.c:3851: Test failed: Unexpected refcnt 1 uiautomation.c:3784: Test failed: Unexpected hr 0x80070057 uiautomation.c:3789: Test failed: Unexpected hr 0x80070057 uiautomation.c:4217: Test failed: Unexpected VT 0 uiautomation.c:4222: Test failed: Unexpected I4 0 uiautomation.c:4223: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3803: Test failed: Unexpected hr 0x80070057 uiautomation.c:4273: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 272 uiautomation.c:4281: Test failed: Unexpected I4 0x23 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3809: Test failed: Unexpected hr 0x80070057 uiautomation.c:4273: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 272 uiautomation.c:4281: Test failed: Unexpected I4 0x23 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3867: Test failed: UiaNodeRelease returned FALSE === debian11 (32 bit WoW report) === uiautomationcore: uiautomation.c:3850: Test failed: Unexpected hr 0x80004002. uiautomation.c:3851: Test failed: Unexpected refcnt 1 uiautomation.c:3784: Test failed: Unexpected hr 0x80070057 uiautomation.c:3789: Test failed: Unexpected hr 0x80070057 uiautomation.c:4217: Test failed: Unexpected VT 0 uiautomation.c:4222: Test failed: Unexpected I4 0 uiautomation.c:4223: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3803: Test failed: Unexpected hr 0x80070057 uiautomation.c:4273: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 272 uiautomation.c:4281: Test failed: Unexpected I4 0x23 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3809: Test failed: Unexpected hr 0x80070057 uiautomation.c:4273: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 272 uiautomation.c:4281: Test failed: Unexpected I4 0x23 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3867: Test failed: UiaNodeRelease returned FALSE === debian11 (64 bit WoW report) === uiautomationcore: uiautomation.c:3850: Test failed: Unexpected hr 0x80004002. uiautomation.c:3851: Test failed: Unexpected refcnt 1 uiautomation.c:3784: Test failed: Unexpected hr 0x80070057 uiautomation.c:3789: Test failed: Unexpected hr 0x80070057 uiautomation.c:4217: Test failed: Unexpected VT 0 uiautomation.c:4222: Test failed: Unexpected I4 0 uiautomation.c:4223: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3803: Test failed: Unexpected hr 0x80070057 uiautomation.c:4270: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 0 uiautomation.c:4281: Test failed: Unexpected I4 0x75d110 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3809: Test failed: Unexpected hr 0x80070057 uiautomation.c:4270: Test failed: Unexpected VT 0 uiautomation.c:4276: Test failed: Unexpected refcnt 1 uiautomation.c:4279: Test failed: Unexpected hr 0x80070057 uiautomation.c:4280: Test failed: Unexpected VT 0 uiautomation.c:4281: Test failed: Unexpected I4 0x75d110 uiautomation.c:4283: Test failed: Failed to release node uiautomation.c:4285: Test failed: incomplete sequence: expected Provider_GetPropertyValue, got nothing uiautomation.c:3867: Test failed: UiaNodeRelease returned FALSE

1 0

Re: [PATCH 9/9] mshtml: Implement ProgressEvent's total prop.
by Marvin 19 Jul '22

19 Jul '22

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=119309 Your paranoid android. === w10pro64_ja (64 bit report) === mshtml: htmldoc.c:2541: Test failed: unexpected call UpdateUI htmldoc.c:2853: Test failed: unexpected call Exec_UPDATECOMMANDS === w1064_tsign (32 bit report) === mshtml: script.c:3119: Test failed: ReportResult failed: 80ef0001

1 0

Re: [PATCH 8/9] mshtml: Implement ProgressEvent's loaded prop.
by Marvin 19 Jul '22

19 Jul '22

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=119308 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 === w7u_2qxl (32 bit report) === mshtml: script.c:644: Test failed: L"/index.html?es5.js:date_now: unexpected Date.now() result 1658261179154 expected 1658261179216"

1 0

Re: [PATCH 7/9] mshtml: Implement ProgressEvent's lengthComputable prop.
by Marvin 19 Jul '22

19 Jul '22

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=119307 Your paranoid android. === w7u_adm (32 bit report) === mshtml: script.c:644: Test failed: L"/index.html?es5.js:date_now: unexpected Date.now() result 1658259923855 expected 1658259923918"

1 0

Re: [PATCH 6/9] mshtml: Fix copy-paste mistake in test message.
by Marvin 19 Jul '22

19 Jul '22

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=119306 Your paranoid android. === w10pro64 (32 bit report) === mshtml: htmldoc.c:2541: Test failed: unexpected call UpdateUI htmldoc.c:2853: Test failed: unexpected call Exec_UPDATECOMMANDS === w7u_2qxl (32 bit report) === mshtml: script.c:644: Test failed: L"/index.html?es5.js:date_now: unexpected Date.now() result 1658258499697 expected 1658258499760" === w7u_adm (32 bit report) === mshtml: script.c:644: Test failed: L"/index.html?es5.js:date_now: unexpected Date.now() result 1658259134369 expected 1658259134432"

1 0

Re: [PATCH v6 1/2] user32/tests: Check that message-only windows ignore WS_EX_TOPMOST.
by Marvin 19 Jul '22

19 Jul '22

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=119286 Your paranoid android. === debian11 (64 bit WoW report) === user32: win.c:11075: Test failed: Received WM_ACTIVATEAPP(0), did not expect it.

1 0

Re: [PATCH v2 1/1] shell32: Return stub bitmap in IShellItemImageFactory::GetImage.
by Marvin 18 Jul '22

18 Jul '22

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=119269 Your paranoid android. === w1064v1809 (32 bit report) === shell32: shlfolder.c:5007: Test failed: Didn't expect a WM_USER_NOTIFY message (event: 2) === w1064 (32 bit report) === shell32: shlfolder.c:5007: Test failed: Didn't expect a WM_USER_NOTIFY message (event: 2) === w1064_tsign (32 bit report) === shell32: shlfolder.c:5007: Test failed: Didn't expect a WM_USER_NOTIFY message (event: 2) === w1064v1809 (64 bit report) === shell32: shlfolder.c:4990: Test failed: RMDIR: expected notification type 10, got: 40000 === w1064_tsign (64 bit report) === shell32: shlfolder.c:4990: Test failed: RMDIR: expected notification type 10, got: 40000 === w10pro64_en_AE_u8 (64 bit report) === shell32: shlfolder.c:4990: Test failed: RMDIR: expected notification type 10, got: 40000 === w10pro64_zh_CN (64 bit report) === shell32: shlfolder.c:4990: Test failed: RMDIR: expected notification type 10, got: 40000

1 0

Re: [PATCH 2/2] advapi32/tests: Test kernel object security with the primary token as well.
by Marvin 18 Jul '22

18 Jul '22

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=119261 Your paranoid android. === w7u_2qxl (32 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w7u_adm (32 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w7u_el (32 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w8 (32 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w8adm (32 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w864 (32 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w1064v1507 (32 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w1064v1809 (32 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w1064 (32 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w1064_tsign (32 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w10pro64 (32 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w864 (64 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w1064v1507 (64 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w1064v1809 (64 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w1064 (64 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w1064_2qxl (64 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w1064_adm (64 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w1064_tsign (64 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w10pro64 (64 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w10pro64_en_AE_u8 (64 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w10pro64_ar (64 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w10pro64_ja (64 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === w10pro64_zh_CN (64 bit report) === advapi32: security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0001, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120001, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f01ff, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x120089, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x120116, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x1200a0, got 0xdeadbeef security.c:5429: Test failed: with process token: AccessCheck error 1309 security.c:5430: Test failed: with process token: expected 1, got -559038737 security.c:5431: Test failed: with process token: expected all access 0x1f0003, got 0xdeadbeef security.c:5439: Test failed: with process token: AccessCheck error 1309 security.c:5440: Test failed: with process token: expected 0, got -559038737 security.c:5441: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5449: Test failed: with process token: AccessCheck error 1309 security.c:5450: Test failed: with process token: expected 0, got -559038737 security.c:5451: Test failed: with process token: expected 0, got 0xdeadbeef security.c:5459: Test failed: with process token: AccessCheck error 1309 security.c:5460: Test failed: with process token: expected 1, got -559038737 security.c:5461: Test failed: with process token: expected read access 0x20001, got 0xdeadbeef security.c:5469: Test failed: with process token: AccessCheck error 1309 security.c:5470: Test failed: with process token: expected 1, got -559038737 security.c:5471: Test failed: with process token: expected write access 0x20002, got 0xdeadbeef security.c:5479: Test failed: with process token: AccessCheck error 1309 security.c:5480: Test failed: with process token: expected 1, got -559038737 security.c:5481: Test failed: with process token: expected execute access 0x120000, got 0xdeadbeef === debian11 (32 bit report) === Report validation errors: advapi32:security prints too much data (33046 bytes) === debian11 (32 bit Arabic:Morocco report) === Report validation errors: advapi32:security prints too much data (33476 bytes) === debian11 (32 bit German report) === Report validation errors: advapi32:security prints too much data (33476 bytes) === debian11 (32 bit French report) === Report validation errors: advapi32:security prints too much data (33476 bytes) === debian11 (32 bit Hebrew:Israel report) === Report validation errors: advapi32:security prints too much data (33476 bytes) === debian11 (32 bit Hindi:India report) === Report validation errors: advapi32:security prints too much data (33476 bytes) === debian11 (32 bit Japanese:Japan report) === Report validation errors: advapi32:security prints too much data (33476 bytes) === debian11 (32 bit Chinese:China report) === Report validation errors: advapi32:security prints too much data (33476 bytes) === debian11 (32 bit WoW report) === Report validation errors: advapi32:security prints too much data (33046 bytes) === debian11 (64 bit WoW report) === Report validation errors: advapi32:security prints too much data (33054 bytes)

1 0

Wine related spam
by Fabian Maurer 18 Jul '22

18 Jul '22

I already told you to not spam random people with wine related mails. Seriously, I'll put you on my instant-delete list and just ignore everything in the future if you don't stop. @Others How do you deal with stuff like this? Just filter it out immediately? Regards, Fabian Maurer On Montag, 18. Juli 2022 10:20:21 CEST you wrote: > Some info from Wine 7.13

2 1

Re: [PATCH v4 2/3] riched20: Add font fallback support.
by Marvin 18 Jul '22

18 Jul '22

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=119249 Your paranoid android. === w10pro64_ar (64 bit report) === riched20: editor.c:5469: Test failed: test paste: strcmp = 1, text='testing paste

1 0

Re: [PATCH v5 2/2] win32u/window: Ignore changing WS_EX_TOPMOST for message-only windows.
by Marvin 18 Jul '22

18 Jul '22

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=119242 Your paranoid android. === w1064_tsign (64 bit report) === user32: win.c:10947: Test failed: pos = 014a015e === w10pro64 (64 bit report) === user32: win.c:10947: Test failed: pos = 014a015e === debian11 (32 bit Hindi:India report) === user32: win.c:8998: Test failed: Unexpected event was delivered

1 0

Re: [PATCH v5 1/2] user32/tests: Check that message-only windows ignore WS_EX_TOPMOST.
by Marvin 18 Jul '22

18 Jul '22

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=119241 Your paranoid android. === w10pro64_ar (64 bit report) === user32: win.c:4641: Test failed: hwnd 000000000005025C/000000000005025C message 0200 win.c:4643: Test failed: wparam 0 win.c:4654: Test failed: hwnd 000000000005025C/000000000005025C message 0203 win.c:4658: Test failed: message 0202 available === w10pro64_ja (64 bit report) === user32: win.c:10957: Test failed: msg.message = 1e

1 0

Re: [PATCH 2/2] urlmon/tests: Trace why the test file creation failed.
by Marvin 18 Jul '22

18 Jul '22

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=119218 Your paranoid android. === w7u_2qxl (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 1324 url.c:1492: Test failed: wrong thread 1324 === w7u_adm (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 2172 url.c:1492: Test failed: wrong thread 2172 === w7u_el (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 2216 url.c:1466: Test failed: progress 32: status = 200 === w8 (32 bit report) === urlmon: url.c:1466: Test failed: progress 3: status = 302 url.c:1492: Test failed: wrong thread 2780 url.c:1492: Test failed: wrong thread 2780 === w8adm (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 2804 url.c:1492: Test failed: wrong thread 2804 === w864 (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 1204 url.c:1466: Test failed: progress 64: status = 302 url.c:1466: Test failed: progress 3: status = 302 === w1064v1507 (32 bit report) === urlmon: url.c:1462: Test failed: progress 3: hres = 1, expected 0 url.c:1466: Test failed: progress 1: status = 200 url.c:1466: Test failed: progress 2: status = 200 url.c:1466: Test failed: progress 65: status = 200 === w1064v1809 (32 bit report) === urlmon: url.c:1796: Test failed: unexpected code 64 url.c:1492: Test failed: wrong thread 7740 url.c:1492: Test failed: wrong thread 7740 === w1064 (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7412 url.c:1492: Test failed: wrong thread 7412 url.c:1466: Test failed: progress 64: status = 302 === w1064_tsign (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 8140 url.c:1492: Test failed: wrong thread 8140 url.c:1466: Test failed: progress 64: status = 302 === w10pro64 (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7752 url.c:1492: Test failed: wrong thread 7752 === w864 (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 3032 url.c:1796: Test failed: unexpected code 64 url.c:1492: Test failed: wrong thread 3032 url.c:1796: Test failed: unexpected code 64 url.c:1466: Test failed: progress 64: status = 200 === w1064v1507 (64 bit report) === urlmon: url.c:1466: Test failed: progress 65: status = 200 url.c:1640: Test failed: unexpected call OnProgress_FINDINGRESOURCE === w1064v1809 (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7512 url.c:1796: Test failed: unexpected code 64 url.c:1492: Test failed: wrong thread 7512 === w1064 (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7324 url.c:1492: Test failed: wrong thread 7324 url.c:1466: Test failed: progress 64: status = 302 === w1064_2qxl (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7804 url.c:1492: Test failed: wrong thread 7804 url.c:1466: Test failed: progress 64: status = 302 === w1064_adm (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7324 url.c:1466: Test failed: progress 64: status = 302 url.c:1492: Test failed: wrong thread 7324 === w1064_tsign (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 6996 url.c:1492: Test failed: wrong thread 6996 === w10pro64 (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7652 url.c:1492: Test failed: wrong thread 7652 === w10pro64_en_AE_u8 (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 5892 url.c:1492: Test failed: wrong thread 5892 === w10pro64_ar (64 bit report) === urlmon: url.c:1492: Test failed: url.c:1662: Test failed: unexpected call OnProgress_REDIRECTING url.c:1492: Test failed: wrong thread 8292 === w10pro64_ja (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 3088 url.c:1466: Test failed: progress 64: status = 302 url.c:1466: Test failed: progress 3: status = 302 url.c:1492: Test failed: wrong thread 3088 === w10pro64_zh_CN (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 4540 url.c:1492: Test failed: wrong thread 4540

1 0

Re: [PATCH 4/5] urlmon/tests: Fix the spelling of a trace() message.
by Marvin 18 Jul '22

18 Jul '22

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=119211 Your paranoid android. === w7u_2qxl (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 1276 url.c:1492: Test failed: wrong thread 1124 === w7u_adm (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 2196 url.c:1492: Test failed: wrong thread 2200 === w7u_el (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 2212 url.c:1492: Test failed: wrong thread 2256 === w8 (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 2896 url.c:1492: Test failed: wrong thread 2896 === w8adm (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 2512 url.c:1492: Test failed: url.c:1796: Test failed: wrong thread 2512 === w864 (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 2708 url.c:1492: Test failed: wrong thread 2708 url.c:1466: Test failed: progress 64: status = 200 === w1064v1507 (32 bit report) === urlmon: url.c:1466: Test failed: progress 65: status = 200 === w1064v1809 (32 bit report) === urlmon: url.c:1796: Test failed: unexpected code 64 url.c:1492: Test failed: wrong thread 7732 url.c:1492: Test failed: wrong thread 7732 url.c:1466: Test failed: progress 64: status = 200 === w1064 (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7380 url.c:1492: Test failed: wrong thread 7380 url.c:1466: Test failed: progress 64: status = 302 === w1064_tsign (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7684 url.c:1492: Test failed: wrong thread 7684 url.c:1466: Test failed: progress 64: status = 302 === w10pro64 (32 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7752 url.c:1492: Test failed: wrong thread 7752 === w864 (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 3032 url.c:1796: Test failed: unexpected code 64 url.c:1796: Test failed: unexpected code 64 url.c:1466: Test failed: progress 3: status = 302 url.c:1492: Test failed: wrong thread 3032 === w1064v1507 (64 bit report) === urlmon: url.c:1466: Test failed: progress 3: status = 200 url.c:1466: Test failed: progress 32: status = 200 url.c:1466: Test failed: progress 1: status = 200 url.c:1466: Test failed: progress 2: status = 200 url.c:1466: Test failed: progress 65: status = 200 === w1064v1809 (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7576 url.c:1796: Test failed: unexpected code 64 url.c:1492: Test failed: wrong thread 7576 === w1064 (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7304 url.c:1466: Test failed: progress 64: status = 302 === w1064_2qxl (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7708 url.c:1466: Test failed: progress 64: status = 302 url.c:1492: Test failed: wrong thread 7708 === w1064_adm (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 5924 url.c:1492: Test failed: wrong thread 5924 === w1064_tsign (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 4076 url.c:1462: Test failed: progress 3: hres = 1, expected 0 url.c:1466: Test failed: progress 32: status = 200 url.c:1466: Test failed: progress 1: status = 200 url.c:1466: Test failed: progress 2: status = 200 url.c:1492: Test failed: wrong thread 4076 url.c:1466: Test failed: progress 64: status = 200 === w10pro64 (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 7668 url.c:1492: Test failed: wrong thread 7668 === w10pro64_en_AE_u8 (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 2848 url.c:1492: Test failed: wrong thread 2848 === w10pro64_ar (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 5872 url.c:1492: Test failed: wrong thread 5872 === w10pro64_ja (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 4472 url.c:1492: Test failed: wrong thread 4472 url.c:1466: Test failed: progress 64: status = 302 === w10pro64_zh_CN (64 bit report) === urlmon: url.c:1492: Test failed: wrong thread 8316 url.c:1492: Test failed: wrong thread 8316

1 0

'wrc' weirdness
by Gisle Vanem 17 Jul '22

17 Jul '22

Hello again list. I'm still struggling with understanding the build of Wine on Win-10 using MSVC or clang-cl. E.g. the 'wrc' program behaves rather different from MSVC's 'rc'. When for example using 'wrc' to build 'attrib.exe', the output of 'attrib.exe /?' looks like this: ATTRIB - Displays or changes file attributes. Syntax: ATTRIB [+R | -R] [+A | -A ] [+S | -S] [+H | -H] [drive:][path][filename] [/S [/D]] Where: + Sets an attribute. ---------------- All lines are doubled up (?!). But using 'rc', there is this issue: ATTRIB - Displays or changes file attributes. Syntax: ATTRIB [+R | -R] [+A | -A ] [+S | -S] [+H | -H] [drive:][path][filename] \ [/S [/D]] \Where: \ + Sets an attribute. \ - Clears an attribute. -------------- The extra '\' at each line (!?). I've tried converting 'attrib.rc' to Unix/DOS line-endings to no avail. And BTW, I used: wrc -D__WINESRC__ -I../../include --output objdir/attrib.res attrib.rc to compile it. What is going on with this, please? -- --gv

2 4

[PATCH v3 1/2] qedit/tests: Test adding a reference to the sample from ISampleGrabberCB::SampleCB().
by Zebediah Figura 17 Jul '22

17 Jul '22

From: Brendan McGrath <brendan(a)redmandi.com> Unravel Two adds a reference to the IMediaSample during its callback. This patch adds a test that checks if an application does do this, that it can free it later and the reference count will finish at zero. Wine-Bug: https://bugs.winehq.org/show_bug.cgi?id=51616 Signed-off-by: Brendan McGrath <brendan(a)redmandi.com> Signed-off-by: Zebediah Figura <zfigura(a)codeweavers.com> --- v3: Some stylistic fixups; make commit messages a bit more specific. dlls/qedit/tests/mediadet.c | 28 +++++++++++++++++++++++----- 1 file changed, 23 insertions(+), 5 deletions(-) diff --git a/dlls/qedit/tests/mediadet.c b/dlls/qedit/tests/mediadet.c index 3202baca924..6e7017f865c 100644 --- a/dlls/qedit/tests/mediadet.c +++ b/dlls/qedit/tests/mediadet.c @@ -866,6 +866,17 @@ static void test_put_filter(void) ok(!ref, "Got outstanding refcount %ld.\n", ref); } +struct test_sample +{ + IMediaSample sample; + LONG refcount; +}; + +static struct test_sample *impl_from_IMediaSample(IMediaSample *iface) +{ + return CONTAINING_RECORD(iface, struct test_sample, sample); +} + static HRESULT WINAPI ms_QueryInterface(IMediaSample *iface, REFIID riid, void **ppvObject) { @@ -874,12 +885,14 @@ static HRESULT WINAPI ms_QueryInterface(IMediaSample *iface, REFIID riid, static ULONG WINAPI ms_AddRef(IMediaSample *iface) { - return 2; + struct test_sample *sample = impl_from_IMediaSample(iface); + return InterlockedIncrement(&sample->refcount); } static ULONG WINAPI ms_Release(IMediaSample *iface) { - return 1; + struct test_sample *sample = impl_from_IMediaSample(iface); + return InterlockedDecrement(&sample->refcount); } static HRESULT WINAPI ms_GetPointer(IMediaSample *iface, BYTE **ppBuffer) @@ -989,7 +1002,7 @@ static const IMediaSampleVtbl my_sample_vt = { ms_SetMediaTime }; -static IMediaSample my_sample = { &my_sample_vt }; +static struct test_sample my_sample = { {&my_sample_vt}, 0 }; static BOOL samplecb_called = FALSE; @@ -1012,8 +1025,9 @@ static ULONG WINAPI sgcb_Release(ISampleGrabberCB *iface) static HRESULT WINAPI sgcb_SampleCB(ISampleGrabberCB *iface, double SampleTime, IMediaSample *pSample) { - ok(pSample == &my_sample, "Got wrong IMediaSample: %p, expected %p\n", pSample, &my_sample); + ok(pSample == &my_sample.sample, "Got wrong IMediaSample: %p, expected %p\n", pSample, &my_sample); samplecb_called = TRUE; + IMediaSample_AddRef(pSample); return E_NOTIMPL; } @@ -1043,6 +1057,7 @@ static void test_samplegrabber(void) IEnumPins *pins; HRESULT hr; FILTER_STATE fstate; + ULONG refcount; /* Invalid RIID */ hr = CoCreateInstance(&CLSID_SampleGrabber, NULL, CLSCTX_INPROC_SERVER, &IID_IClassFactory, @@ -1074,10 +1089,13 @@ static void test_samplegrabber(void) hr = IPin_QueryInterface(pin, &IID_IMemInputPin, (void**)&inpin); ok(hr == S_OK, "Got hr %#lx.\n", hr); - hr = IMemInputPin_Receive(inpin, &my_sample); + hr = IMemInputPin_Receive(inpin, &my_sample.sample); ok(hr == S_OK, "Got hr %#lx.\n", hr); ok(samplecb_called == TRUE, "SampleCB should have been called\n"); + refcount = IUnknown_Release(&my_sample.sample); + todo_wine ok(!refcount, "Got unexpected refcount %ld.\n", refcount); + IMemInputPin_Release(inpin); IPin_Release(pin); -- 2.36.1

3 4

Re: [PATCH v3 3/5] dlls/msvcrt: fix and cleanup undecoration of templatized functions and methods
by Marvin 16 Jul '22

16 Jul '22

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. 1 TestBot errors prevented a full analysis of your patch. If the test caused the operating system (e.g. Windows) to crash or reboot you will probably have to modify it to avoid that. Other issues should be reported to the TestBot administrators. The full results can be found at: https://testbot.winehq.org/JobDetails.pl?Key=119173 Your paranoid android. === build (build log) === WineRunBuild.pl:error: An error occurred while waiting for the build to complete: network read timed out (wait2:ListSize:0/4) WineRunBuild.pl:error: BotError: The test VM has crashed, rebooted or lost connectivity (or the TestAgent server died)

1 0

Wine staging 7.13 release
by Alistair Leslie-Hughes 16 Jul '22

16 Jul '22

Binary packages for various distributions will be available from: https://www.winehq.org/download Summary since last release * Rebased to current wine 7.13 (543 patches are applied to wine vanilla) Upstreamed (Either directly from staging or fixed with a similar patch). * None 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

Re: [PATCH v2 2/5] msvcrt: add support for C++11 operator "" in demangling
by Marvin 16 Jul '22

16 Jul '22

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=119164 Your paranoid android. === w1064v1507 (32 bit report) === ucrtbase: cpp.c:207: Test failed: unDName returned "??__K_l@@YA?AUCC@@I@Z" for #2 === w1064v1507 (64 bit report) === ucrtbase: cpp.c:207: Test failed: unDName returned "??__K_l@@YA?AUCC@@I@Z" for #2

1 0

Re: [PATCH 3/3] taskschd: Return SCHED_S_TASK_HAS_NOT_RUN from regtask_get_LastRunTime() stub.
by Marvin 16 Jul '22

16 Jul '22

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=119160 Your paranoid android. === w7u_adm (32 bit report) === taskschd: scheduler.c:791: Test failed: DeleteTask error 0x80070005 scheduler.c:787: Test failed: 1: expected 0, got 0x800700b7 scheduler.c:787: Test failed: 2: expected 0x80070002, got 0 scheduler.c:791: Test failed: DeleteTask error 0x80070005 scheduler.c:791: Test failed: DeleteTask error 0x80070005 scheduler.c:807: Test failed: RegisterTask error 0x800700b7 scheduler.c:953: Test failed: DeleteTask error 0x80070005 scheduler.c:955: Test failed: DeleteTask error 0x80070005 scheduler.c:958: Test failed: expected ERROR_FILE_NOT_FOUND, got 0x80070005

1 0

Re: [PATCH 2/3] schedsvc: Read task enable state from XML in SchRpcGetTaskInfo().
by Marvin 16 Jul '22

16 Jul '22

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=119159 Your paranoid android. === w7u_adm (32 bit report) === taskschd: scheduler.c:790: Test failed: DeleteTask error 0x80070005 scheduler.c:786: Test failed: 1: expected 0, got 0x800700b7 scheduler.c:786: Test failed: 2: expected 0x80070002, got 0 scheduler.c:790: Test failed: DeleteTask error 0x80070005 scheduler.c:790: Test failed: DeleteTask error 0x80070005 scheduler.c:806: Test failed: RegisterTask error 0x800700b7 scheduler.c:937: Test failed: DeleteTask error 0x80070005 scheduler.c:939: Test failed: DeleteTask error 0x80070005 scheduler.c:942: Test failed: expected ERROR_FILE_NOT_FOUND, got 0x80070005

1 0

Re: [PATCH 1/5] ws2_32/tests: Add more tests for SO_CONNECT_TIME.
by Marvin 15 Jul '22

15 Jul '22

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=119152 Your paranoid android. === debian11 (32 bit Japanese:Japan report) === ws2_32: sock.c:6295: Test succeeded inside todo block: expected timeout

1 0

Re: [PATCH v2 7/7] shell32: Implement SHOpenFolderAndSelectItems().
by Marvin 15 Jul '22

15 Jul '22

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=119127 Your paranoid android. === w1064_2qxl (64 bit report) === shell32: shlfolder.c:5008: Test failed: Didn't expect a WM_USER_NOTIFY message (event: 2) === w10pro64 (64 bit report) === shell32: shlfolder.c:4991: Test failed: MKDIR: expected notification type 8, got: 40000 === w10pro64_ar (64 bit report) === shell32: shlfolder.c:4991: Test failed: RMDIR: expected notification type 10, got: 40000 === w10pro64_ja (64 bit report) === shell32: shlfolder.c:4991: Test failed: RMDIR: expected notification type 10, got: 40000 shlfolder.c:4991: Test failed: MKDIR: expected notification type 8, got: 40000 === w10pro64_zh_CN (64 bit report) === shell32: shlfolder.c:4991: Test failed: RMDIR: expected notification type 10, got: 40000

1 0

Re: [PATCH v2 6/7] shell32/tests: Add SHOpenFolderAndSelectItems() tests.
by Marvin 15 Jul '22

15 Jul '22

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=119126 Your paranoid android. === w1064v1809 (32 bit report) === shell32: shlfolder.c:4991: Test failed: RMDIR: expected notification type 10, got: 40000 === w1064v1809 (64 bit report) === shell32: shlfolder.c:4991: Test failed: RMDIR: expected notification type 10, got: 40000 === w1064 (64 bit report) === shell32: shlfolder.c:4991: Test failed: MKDIR: expected notification type 8, got: 40000 === w10pro64_en_AE_u8 (64 bit report) === shell32: shlfolder.c:4991: Test failed: RMDIR: expected notification type 10, got: 40000 === w10pro64_ar (64 bit report) === shell32: shlfolder.c:4991: Test failed: MKDIR: expected notification type 8, got: 40000 === w10pro64_ja (64 bit report) === shell32: shlfolder.c:5008: Test failed: Didn't expect a WM_USER_NOTIFY message (event: 2)

1 0

Re: [PATCH v3 1/5] ws2_32: Add ipv4 raw socket protocol info.
by Marvin 15 Jul '22

15 Jul '22

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=119099 Your paranoid android. === w1064v1507 (32 bit report) === ws2_32: protocol.c:2067: Test failed: wait failed protocol.c:2069: Test failed: overlapped result is 10036 protocol.c:2071: Test failed: overlapped.Internal = 2734 protocol.c:2073: Test failed: got 0

1 0

Re: [PATCH v3 3/5] ntdll: Support SOCK_RAW / IPPROTO_ICMP fallback over SOCK_DGRAM.
by Marvin 15 Jul '22

15 Jul '22

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=119101 Your paranoid android. === debian11 (64 bit WoW report) === ntdll: change.c:241: Test failed: should be ready

1 0

Re: [PATCH 5/5] dlls/msvcrt: fix demangling of variables being an array
by Marvin 15 Jul '22

15 Jul '22

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=119098 Your paranoid android. === w7u_2qxl (32 bit report) === msvcrt: cpp.c:1308: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1311: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w7u_adm (32 bit report) === msvcrt: cpp.c:1308: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1311: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w7u_el (32 bit report) === msvcrt: cpp.c:1308: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1311: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w8 (32 bit report) === msvcrt: cpp.c:1308: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1311: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w8adm (32 bit report) === msvcrt: cpp.c:1308: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1311: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w864 (32 bit report) === msvcrt: cpp.c:1308: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1311: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064v1507 (32 bit report) === msvcrt: cpp.c:1308: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1311: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064v1809 (32 bit report) === msvcrt: cpp.c:1308: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1311: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064 (32 bit report) === msvcrt: cpp.c:1308: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1311: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064_tsign (32 bit report) === msvcrt: cpp.c:1308: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1311: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w10pro64 (32 bit report) === msvcrt: cpp.c:1308: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1311: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w864 (64 bit report) === msvcrt: cpp.c:1308: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1311: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064v1507 (64 bit report) === msvcrt: cpp.c:1308: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1311: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064v1809 (64 bit report) === msvcrt: cpp.c:1308: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1311: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064 (64 bit report) === msvcrt: cpp.c:1308: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1311: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064_2qxl (64 bit report) === msvcrt: cpp.c:1308: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1311: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064_adm (64 bit report) === msvcrt: cpp.c:1308: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1311: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064_tsign (64 bit report) === msvcrt: cpp.c:1308: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1311: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w10pro64 (64 bit report) === msvcrt: cpp.c:1308: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1311: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w10pro64_en_AE_u8 (64 bit report) === msvcrt: cpp.c:1308: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1311: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w10pro64_ar (64 bit report) === msvcrt: cpp.c:1308: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1311: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w10pro64_ja (64 bit report) === msvcrt: cpp.c:1308: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1311: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w10pro64_zh_CN (64 bit report) === msvcrt: cpp.c:1308: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1311: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)"

1 0

Re: [PATCH 4/5] dlls/msvcrt: add support for restrict and unaligned qualifiers in demangling
by Marvin 15 Jul '22

15 Jul '22

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=119097 Your paranoid android. === w7u_2qxl (32 bit report) === msvcrt: cpp.c:1307: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1310: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w7u_adm (32 bit report) === msvcrt: cpp.c:1307: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1310: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w7u_el (32 bit report) === msvcrt: cpp.c:1307: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1310: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w8 (32 bit report) === msvcrt: cpp.c:1307: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1310: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w8adm (32 bit report) === msvcrt: cpp.c:1307: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1310: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w864 (32 bit report) === msvcrt: cpp.c:1307: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1310: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064v1507 (32 bit report) === msvcrt: cpp.c:1307: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1310: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064v1809 (32 bit report) === msvcrt: cpp.c:1307: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1310: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064 (32 bit report) === msvcrt: cpp.c:1307: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1310: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064_tsign (32 bit report) === msvcrt: cpp.c:1307: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1310: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w10pro64 (32 bit report) === msvcrt: cpp.c:1307: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1310: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w864 (64 bit report) === msvcrt: cpp.c:1307: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1310: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064v1507 (64 bit report) === msvcrt: cpp.c:1307: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1310: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064v1809 (64 bit report) === msvcrt: cpp.c:1307: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1310: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064 (64 bit report) === msvcrt: cpp.c:1307: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1310: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064_2qxl (64 bit report) === msvcrt: cpp.c:1307: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1310: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064_adm (64 bit report) === msvcrt: cpp.c:1307: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1310: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064_tsign (64 bit report) === msvcrt: cpp.c:1307: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1310: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w10pro64 (64 bit report) === msvcrt: cpp.c:1307: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1310: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w10pro64_en_AE_u8 (64 bit report) === msvcrt: cpp.c:1307: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1310: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w10pro64_ar (64 bit report) === msvcrt: cpp.c:1307: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1310: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w10pro64_ja (64 bit report) === msvcrt: cpp.c:1307: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1310: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w10pro64_zh_CN (64 bit report) === msvcrt: cpp.c:1307: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1310: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)"

1 0

Re: [PATCH 3/5] dlls/msvcrt: fix and cleanup undecoration of templatized functions and methods
by Marvin 15 Jul '22

15 Jul '22

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=119096 Your paranoid android. === w7u_2qxl (32 bit report) === msvcrt: cpp.c:1306: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1309: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w7u_adm (32 bit report) === msvcrt: cpp.c:1306: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1309: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w7u_el (32 bit report) === msvcrt: cpp.c:1306: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1309: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w8 (32 bit report) === msvcrt: cpp.c:1306: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1309: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w8adm (32 bit report) === msvcrt: cpp.c:1306: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1309: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w864 (32 bit report) === msvcrt: cpp.c:1306: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1309: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064v1507 (32 bit report) === msvcrt: cpp.c:1306: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1309: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064v1809 (32 bit report) === msvcrt: cpp.c:1306: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1309: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064 (32 bit report) === msvcrt: cpp.c:1306: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1309: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064_tsign (32 bit report) === msvcrt: cpp.c:1306: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1309: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w10pro64 (32 bit report) === msvcrt: cpp.c:1306: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1309: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w864 (64 bit report) === msvcrt: cpp.c:1306: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1309: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064v1507 (64 bit report) === msvcrt: cpp.c:1306: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1309: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064v1809 (64 bit report) === msvcrt: cpp.c:1306: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1309: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064 (64 bit report) === msvcrt: cpp.c:1306: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1309: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064_2qxl (64 bit report) === msvcrt: cpp.c:1306: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1309: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064_adm (64 bit report) === msvcrt: cpp.c:1306: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1309: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064_tsign (64 bit report) === msvcrt: cpp.c:1306: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1309: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w10pro64 (64 bit report) === msvcrt: cpp.c:1306: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1309: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w10pro64_en_AE_u8 (64 bit report) === msvcrt: cpp.c:1306: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1309: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w10pro64_ar (64 bit report) === msvcrt: cpp.c:1306: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1309: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w10pro64_ja (64 bit report) === msvcrt: cpp.c:1306: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1309: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w10pro64_zh_CN (64 bit report) === msvcrt: cpp.c:1306: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1309: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)"

1 0

Re: [PATCH 2/5] msvcrt: add support for C++11 operator "" in demangling
by Marvin 15 Jul '22

15 Jul '22

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=119095 Your paranoid android. === w7u_2qxl (32 bit report) === msvcrt: cpp.c:1305: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1308: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w7u_adm (32 bit report) === msvcrt: cpp.c:1305: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1308: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w7u_el (32 bit report) === msvcrt: cpp.c:1305: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1308: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w8 (32 bit report) === msvcrt: cpp.c:1305: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1308: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w8adm (32 bit report) === msvcrt: cpp.c:1305: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1308: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w864 (32 bit report) === msvcrt: cpp.c:1305: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1308: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064v1507 (32 bit report) === msvcrt: cpp.c:1305: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1308: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064v1809 (32 bit report) === msvcrt: cpp.c:1305: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1308: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064 (32 bit report) === msvcrt: cpp.c:1305: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1308: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064_tsign (32 bit report) === msvcrt: cpp.c:1305: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1308: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w10pro64 (32 bit report) === msvcrt: cpp.c:1305: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1308: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w864 (64 bit report) === msvcrt: cpp.c:1305: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1308: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064v1507 (64 bit report) === msvcrt: cpp.c:1305: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1308: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064v1809 (64 bit report) === msvcrt: cpp.c:1305: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1308: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064 (64 bit report) === msvcrt: cpp.c:1305: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1308: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064_2qxl (64 bit report) === msvcrt: cpp.c:1305: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1308: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064_adm (64 bit report) === msvcrt: cpp.c:1305: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1308: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w1064_tsign (64 bit report) === msvcrt: cpp.c:1305: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1308: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w10pro64 (64 bit report) === msvcrt: cpp.c:1305: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1308: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w10pro64_en_AE_u8 (64 bit report) === msvcrt: cpp.c:1305: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1308: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w10pro64_ar (64 bit report) === msvcrt: cpp.c:1305: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1308: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w10pro64_ja (64 bit report) === msvcrt: cpp.c:1305: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1308: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)" === w10pro64_zh_CN (64 bit report) === msvcrt: cpp.c:1305: Test failed: 132: Got name "??__K_l@@YA?AUCC@@I@Z" cpp.c:1308: Test failed: 132: Expected "struct CC __cdecl operator "" _l(unsigned int)"

1 0

[PATCH v2] winspool.drv: Implement OpenPrinter2.
by Dmitry Timoshkov 15 Jul '22

15 Jul '22

v2: Forward OpenPrinter() to OpenPrinter2(). Signed-off-by: Dmitry Timoshkov <dmitry(a)baikal.ru> --- dlls/winspool.drv/info.c | 96 +++++++++++++++++++---------- dlls/winspool.drv/winspool.drv.spec | 2 + include/winspool.h | 29 ++++++++- 3 files changed, 92 insertions(+), 35 deletions(-) diff --git a/dlls/winspool.drv/info.c b/dlls/winspool.drv/info.c index 482f70a2235..e1cd0338207 100644 --- a/dlls/winspool.drv/info.c +++ b/dlls/winspool.drv/info.c @@ -1990,32 +1990,9 @@ BOOL WINAPI IsValidDevmodeW(PDEVMODEW dm, SIZE_T size) * See OpenPrinterW. * */ -BOOL WINAPI OpenPrinterA(LPSTR lpPrinterName,HANDLE *phPrinter, - LPPRINTER_DEFAULTSA pDefault) +BOOL WINAPI OpenPrinterA(LPSTR name, HANDLE *printer, PRINTER_DEFAULTSA *defaults) { - UNICODE_STRING lpPrinterNameW; - UNICODE_STRING usBuffer; - PRINTER_DEFAULTSW DefaultW, *pDefaultW = NULL; - PWSTR pwstrPrinterNameW; - BOOL ret; - - TRACE("%s,%p,%p\n", debugstr_a(lpPrinterName), phPrinter, pDefault); - - pwstrPrinterNameW = asciitounicode(&lpPrinterNameW,lpPrinterName); - - if(pDefault) { - DefaultW.pDatatype = asciitounicode(&usBuffer,pDefault->pDatatype); - DefaultW.pDevMode = pDefault->pDevMode ? GdiConvertToDevmodeW(pDefault->pDevMode) : NULL; - DefaultW.DesiredAccess = pDefault->DesiredAccess; - pDefaultW = &DefaultW; - } - ret = OpenPrinterW(pwstrPrinterNameW, phPrinter, pDefaultW); - if(pDefault) { - RtlFreeUnicodeString(&usBuffer); - HeapFree(GetProcessHeap(), 0, DefaultW.pDevMode); - } - RtlFreeUnicodeString(&lpPrinterNameW); - return ret; + return OpenPrinter2A(name, printer, defaults, NULL); } /****************************************************************** @@ -2045,22 +2022,73 @@ BOOL WINAPI OpenPrinterA(LPSTR lpPrinterName,HANDLE *phPrinter, *| pDefaults is ignored * */ -BOOL WINAPI OpenPrinterW(LPWSTR lpPrinterName,HANDLE *phPrinter, LPPRINTER_DEFAULTSW pDefault) +BOOL WINAPI OpenPrinterW(LPWSTR name, HANDLE *printer, PRINTER_DEFAULTSW *defaults) +{ + return OpenPrinter2W(name, printer, defaults, NULL); +} + +BOOL WINAPI OpenPrinter2A(LPSTR name, HANDLE *printer, + PRINTER_DEFAULTSA *defaults, PRINTER_OPTIONSA *options) +{ + UNICODE_STRING nameU; + UNICODE_STRING datatypeU; + PRINTER_DEFAULTSW defaultsW, *p_defaultsW = NULL; + PRINTER_OPTIONSW optionsW, *p_optionsW = NULL; + WCHAR *nameW; + BOOL ret; + + TRACE("(%s,%p,%p,%p)\n", debugstr_a(name), printer, defaults, options); + + nameW = asciitounicode(&nameU, name); + + if (options) + { + optionsW.cbSize = sizeof(optionsW); + optionsW.dwFlags = options->dwFlags; + p_optionsW = &optionsW; + } + + if (defaults) + { + defaultsW.pDatatype = asciitounicode(&datatypeU, defaults->pDatatype); + defaultsW.pDevMode = defaults->pDevMode ? GdiConvertToDevmodeW(defaults->pDevMode) : NULL; + defaultsW.DesiredAccess = defaults->DesiredAccess; + p_defaultsW = &defaultsW; + } + + ret = OpenPrinter2W(nameW, printer, p_defaultsW, p_optionsW); + + if (p_defaultsW) + { + RtlFreeUnicodeString(&datatypeU); + HeapFree(GetProcessHeap(), 0, defaultsW.pDevMode); + } + RtlFreeUnicodeString(&nameU); + + return ret; +} + +BOOL WINAPI OpenPrinter2W(LPWSTR name, HANDLE *printer, + PRINTER_DEFAULTSW *defaults, PRINTER_OPTIONSW *options) { HKEY key; - TRACE("(%s, %p, %p)\n", debugstr_w(lpPrinterName), phPrinter, pDefault); + TRACE("(%s,%p,%p,%p)\n", debugstr_w(name), printer, defaults, options); - if(!phPrinter) { + if (options) + FIXME("flags %08lx ignored\n", options->dwFlags); + + if(!printer) + { /* NT: FALSE with ERROR_INVALID_PARAMETER, 9x: TRUE */ - SetLastError(ERROR_INVALID_PARAMETER); + SetLastError( ERROR_INVALID_PARAMETER ); return FALSE; } /* Get the unique handle of the printer or Printserver */ - *phPrinter = get_opened_printer_entry(lpPrinterName, pDefault); + *printer = get_opened_printer_entry( name, defaults ); - if (*phPrinter && WINSPOOL_GetOpenedPrinterRegKey( *phPrinter, &key ) == ERROR_SUCCESS) + if (*printer && WINSPOOL_GetOpenedPrinterRegKey( *printer, &key ) == ERROR_SUCCESS) { DWORD deleting = 0, size = sizeof( deleting ), type; DWORD status; @@ -2070,12 +2098,12 @@ BOOL WINAPI OpenPrinterW(LPWSTR lpPrinterName,HANDLE *phPrinter, LPPRINTER_DEFAU set_reg_DWORD( key, L"Status", status & ~PRINTER_STATUS_DRIVER_UPDATE_NEEDED ); ReleaseMutex( init_mutex ); if (!deleting && (status & PRINTER_STATUS_DRIVER_UPDATE_NEEDED)) - update_driver( *phPrinter ); + update_driver( *printer ); RegCloseKey( key ); } - TRACE("returning %d with %lu and %p\n", *phPrinter != NULL, GetLastError(), *phPrinter); - return (*phPrinter != 0); + TRACE("returning %d with %lu and %p\n", *printer != NULL, GetLastError(), *printer); + return (*printer != NULL); } /****************************************************************** diff --git a/dlls/winspool.drv/winspool.drv.spec b/dlls/winspool.drv/winspool.drv.spec index d7bb49bd34b..39c2613a4a0 100644 --- a/dlls/winspool.drv/winspool.drv.spec +++ b/dlls/winspool.drv/winspool.drv.spec @@ -149,6 +149,8 @@ @ stdcall IsValidDevmodeW(ptr long) @ stdcall OpenPrinterA(str ptr ptr) @ stdcall OpenPrinterW(wstr ptr ptr) +@ stdcall OpenPrinter2A(str ptr ptr ptr) +@ stdcall OpenPrinter2W(wstr ptr ptr ptr) @ stdcall PerfClose() @ stdcall PerfCollect(wstr ptr ptr ptr) @ stdcall PerfOpen(wstr) diff --git a/include/winspool.h b/include/winspool.h index db8773ec418..ef39104ea30 100644 --- a/include/winspool.h +++ b/include/winspool.h @@ -1143,6 +1143,30 @@ typedef struct _BIDI_RESPONSE_CONTAINER { BIDI_RESPONSE_DATA aData[1]; } BIDI_RESPONSE_CONTAINER, *LPBIDI_RESPONSE_CONTAINER, *PBIDI_RESPONSE_CONTAINER; +typedef enum _PRINTER_OPTION_FLAGS +{ + PRINTER_OPTION_NO_CACHE = 1 << 0, + PRINTER_OPTION_CACHE = 1 << 1, + PRINTER_OPTION_CLIENT_CHANGE = 1 << 2, + PRINTER_OPTION_NO_CLIENT_DATA = 1 << 3, +} PRINTER_OPTION_FLAGS; + +typedef struct _PRINTER_OPTIONSA +{ + UINT cbSize; + DWORD dwFlags; +} PRINTER_OPTIONSA, *PPRINTER_OPTIONSA, *LPPRINTER_OPTIONSA; + +typedef struct _PRINTER_OPTIONSW +{ + UINT cbSize; + DWORD dwFlags; +} PRINTER_OPTIONSW, *PPRINTER_OPTIONSW, *LPPRINTER_OPTIONSW; + +DECL_WINELIB_TYPE_AW(PRINTER_OPTIONS) +DECL_WINELIB_TYPE_AW(PPRINTER_OPTIONS) +DECL_WINELIB_TYPE_AW(LPPRINTER_OPTIONS) + /* string constants */ #define SPLREG_DEFAULT_SPOOL_DIRECTORYA "DefaultSpoolDirectory" @@ -1400,9 +1424,12 @@ BOOL WINAPI OpenPrinterA(LPSTR lpPrinterName,HANDLE *phPrinter, LPPRINTER_DEFAULTSA pDefault); BOOL WINAPI OpenPrinterW(LPWSTR lpPrinterName,HANDLE *phPrinter, LPPRINTER_DEFAULTSW pDefault); - #define OpenPrinter WINELIB_NAME_AW(OpenPrinter) +BOOL WINAPI OpenPrinter2A(LPSTR,HANDLE *,PRINTER_DEFAULTSA *,PRINTER_OPTIONSA *); +BOOL WINAPI OpenPrinter2W(LPWSTR,HANDLE *,PRINTER_DEFAULTSW *,PRINTER_OPTIONSW *); +#define OpenPrinter2 WINELIB_NAME_AW(OpenPrinter2) + BOOL WINAPI ResetPrinterA(HANDLE hPrinter, LPPRINTER_DEFAULTSA pDefault); BOOL WINAPI ResetPrinterW(HANDLE hPrinter, LPPRINTER_DEFAULTSW pDefault); #define ResetPrinter WINELIB_NAME_AW(ResetPrinter) -- 2.36.1

2 1

[PATCH] programs/services: Start service dependencies.
by Dmitry Timoshkov 15 Jul '22

15 Jul '22

Signed-off-by: Dmitry Timoshkov <dmitry(a)baikal.ru> --- programs/services/services.c | 39 +++++++++++++++++++++++++++++++++++- 1 file changed, 38 insertions(+), 1 deletion(-) diff --git a/programs/services/services.c b/programs/services/services.c index 2edc02d300c..08b7488473b 100644 --- a/programs/services/services.c +++ b/programs/services/services.c @@ -1190,12 +1190,49 @@ static DWORD process_send_start_message(struct process_entry *process, BOOL shar return result; } +static DWORD start_service_deps(struct service_entry *service) +{ + struct service_entry *entry; + LPWSTR name; + DWORD err; + + if (!service->dependOnServices) + return ERROR_SUCCESS; + + for (name = service->dependOnServices; *name; name += lstrlenW(name) + 1) + { + entry = scmdatabase_find_service(service->db, name); + if (!entry) + { + WINE_ERR("Service %s depends on %s which doesn't exist\n", debugstr_w(service->name), debugstr_w(name)); + return ERROR_SERVICE_DEPENDENCY_DELETED; + } + + err = service_start(entry, 0, NULL); + if (err != ERROR_SUCCESS && err != ERROR_SERVICE_ALREADY_RUNNING) + { + WINE_FIXME("Dependent on service %s failed to start: %lu\n", + wine_dbgstr_w(entry->name), err); + return ERROR_SERVICE_DEPENDENCY_FAIL; + } + } + + return ERROR_SUCCESS; +} + DWORD service_start(struct service_entry *service, DWORD service_argc, LPCWSTR *service_argv) { struct process_entry *process = NULL; BOOL shared_process; DWORD err; + err = start_service_deps(service); + if (err != ERROR_SUCCESS) + { + WINE_TRACE("returning %lu\n", err); + return err; + } + err = service_start_process(service, &process, &shared_process); if (err == ERROR_SUCCESS) { @@ -1221,7 +1258,7 @@ DWORD service_start(struct service_entry *service, DWORD service_argc, LPCWSTR * release_process(process); } - WINE_TRACE("returning %ld\n", err); + WINE_TRACE("returning %lu\n", err); return err; } -- 2.36.1

2 4

[PATCH] winspool.drv: Implement OpenPrinter2.
by Dmitry Timoshkov 15 Jul '22

15 Jul '22

Signed-off-by: Dmitry Timoshkov <dmitry(a)baikal.ru> --- dlls/winspool.drv/info.c | 18 ++++++++++++++++++ dlls/winspool.drv/winspool.drv.spec | 2 ++ include/winspool.h | 29 ++++++++++++++++++++++++++++- 3 files changed, 48 insertions(+), 1 deletion(-) diff --git a/dlls/winspool.drv/info.c b/dlls/winspool.drv/info.c index 482f70a2235..c536253317b 100644 --- a/dlls/winspool.drv/info.c +++ b/dlls/winspool.drv/info.c @@ -2078,6 +2078,24 @@ BOOL WINAPI OpenPrinterW(LPWSTR lpPrinterName,HANDLE *phPrinter, LPPRINTER_DEFAU return (*phPrinter != 0); } +BOOL WINAPI OpenPrinter2A(LPSTR name, HANDLE *printer, + PRINTER_DEFAULTSA *defaults, PRINTER_OPTIONSA *options) +{ + if (options) + FIXME("flags %08lx ignored\n", options->dwFlags); + + return OpenPrinterA(name, printer, defaults); +} + +BOOL WINAPI OpenPrinter2W(LPWSTR name, HANDLE *printer, + PRINTER_DEFAULTSW *defaults, PRINTER_OPTIONSW *options) +{ + if (options) + FIXME("flags %08lx ignored\n", options->dwFlags); + + return OpenPrinterW(name, printer, defaults); +} + /****************************************************************** * AddMonitorA [WINSPOOL.@] * diff --git a/dlls/winspool.drv/winspool.drv.spec b/dlls/winspool.drv/winspool.drv.spec index d7bb49bd34b..39c2613a4a0 100644 --- a/dlls/winspool.drv/winspool.drv.spec +++ b/dlls/winspool.drv/winspool.drv.spec @@ -149,6 +149,8 @@ @ stdcall IsValidDevmodeW(ptr long) @ stdcall OpenPrinterA(str ptr ptr) @ stdcall OpenPrinterW(wstr ptr ptr) +@ stdcall OpenPrinter2A(str ptr ptr ptr) +@ stdcall OpenPrinter2W(wstr ptr ptr ptr) @ stdcall PerfClose() @ stdcall PerfCollect(wstr ptr ptr ptr) @ stdcall PerfOpen(wstr) diff --git a/include/winspool.h b/include/winspool.h index db8773ec418..ef39104ea30 100644 --- a/include/winspool.h +++ b/include/winspool.h @@ -1143,6 +1143,30 @@ typedef struct _BIDI_RESPONSE_CONTAINER { BIDI_RESPONSE_DATA aData[1]; } BIDI_RESPONSE_CONTAINER, *LPBIDI_RESPONSE_CONTAINER, *PBIDI_RESPONSE_CONTAINER; +typedef enum _PRINTER_OPTION_FLAGS +{ + PRINTER_OPTION_NO_CACHE = 1 << 0, + PRINTER_OPTION_CACHE = 1 << 1, + PRINTER_OPTION_CLIENT_CHANGE = 1 << 2, + PRINTER_OPTION_NO_CLIENT_DATA = 1 << 3, +} PRINTER_OPTION_FLAGS; + +typedef struct _PRINTER_OPTIONSA +{ + UINT cbSize; + DWORD dwFlags; +} PRINTER_OPTIONSA, *PPRINTER_OPTIONSA, *LPPRINTER_OPTIONSA; + +typedef struct _PRINTER_OPTIONSW +{ + UINT cbSize; + DWORD dwFlags; +} PRINTER_OPTIONSW, *PPRINTER_OPTIONSW, *LPPRINTER_OPTIONSW; + +DECL_WINELIB_TYPE_AW(PRINTER_OPTIONS) +DECL_WINELIB_TYPE_AW(PPRINTER_OPTIONS) +DECL_WINELIB_TYPE_AW(LPPRINTER_OPTIONS) + /* string constants */ #define SPLREG_DEFAULT_SPOOL_DIRECTORYA "DefaultSpoolDirectory" @@ -1400,9 +1424,12 @@ BOOL WINAPI OpenPrinterA(LPSTR lpPrinterName,HANDLE *phPrinter, LPPRINTER_DEFAULTSA pDefault); BOOL WINAPI OpenPrinterW(LPWSTR lpPrinterName,HANDLE *phPrinter, LPPRINTER_DEFAULTSW pDefault); - #define OpenPrinter WINELIB_NAME_AW(OpenPrinter) +BOOL WINAPI OpenPrinter2A(LPSTR,HANDLE *,PRINTER_DEFAULTSA *,PRINTER_OPTIONSA *); +BOOL WINAPI OpenPrinter2W(LPWSTR,HANDLE *,PRINTER_DEFAULTSW *,PRINTER_OPTIONSW *); +#define OpenPrinter2 WINELIB_NAME_AW(OpenPrinter2) + BOOL WINAPI ResetPrinterA(HANDLE hPrinter, LPPRINTER_DEFAULTSA pDefault); BOOL WINAPI ResetPrinterW(HANDLE hPrinter, LPPRINTER_DEFAULTSW pDefault); #define ResetPrinter WINELIB_NAME_AW(ResetPrinter) -- 2.36.1

2 2

Re: [PATCH v4 2/2] win32u/window: Ignore changing WS_EX_TOPMOST for message-only windows.
by Marvin 15 Jul '22

15 Jul '22

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=119088 Your paranoid android. === w10pro64_ja (64 bit report) === user32: win.c:189: Test failed: didn't get start_event win.c:10399: Test failed: WindowFromPoint returned 0000000000020338, expected 0000000000000000 win.c:10407: Test failed: WindowFromPoint returned 0000000000040336, expected 0000000000000000 win.c:10336: Test failed: transparent window didn't get WM_NCHITTEST message === debian11 (32 bit report) === user32: win.c:8992: Test failed: Unexpected event was delivered === debian11 (32 bit Hebrew:Israel report) === user32: win.c:8992: Test failed: Unexpected event was delivered === debian11 (32 bit Hindi:India report) === user32: win.c:8992: Test failed: Unexpected event was delivered

1 0

Re: [PATCH v4 1/2] user32/tests: Check that message-only windows ignore WS_EX_TOPMOST.
by Marvin 15 Jul '22

15 Jul '22

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=119087 Your paranoid android. === w10pro64_ja (64 bit report) === user32: win.c:4558: Test failed: hwnd 00000000000C032A/00000000000C032A message 0200 win.c:4563: Test failed: hwnd 00000000000C032A/00000000000C032A message 0203 win.c:4567: Test failed: message 0202 available

1 0

[PATCH] include: Add dxcore.idl.
by Biswapriyo Nath 15 Jul '22

15 Jul '22

4 8

Re: [PATCH v2 1/1] po: Update Korean translation.
by Marvin 15 Jul '22

15 Jul '22

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=119078 Your paranoid android. === debian11 (build log) === error: patch failed: po/ko.po:3972 Task: Patch failed to apply === debian11 (build log) === error: patch failed: po/ko.po:3972 Task: Patch failed to apply

1 0

Re: [PATCH 1/1] po: Update Korean translation.
by Marvin 15 Jul '22

15 Jul '22

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=119077 Your paranoid android. === debian11 (build log) === error: patch failed: po/ko.po:3972 Task: Patch failed to apply === debian11 (build log) === error: patch failed: po/ko.po:3972 Task: Patch failed to apply

1 0

[PATCH vkd3d 08/12] vkd3d-shader/hlsl: Print index paths in dump_deref().
by Francisco Casas 15 Jul '22

15 Jul '22

Signed-off-by: Francisco Casas <fcasas(a)codeweavers.com> --- libs/vkd3d-shader/hlsl.c | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/libs/vkd3d-shader/hlsl.c b/libs/vkd3d-shader/hlsl.c index c7416054..924121f0 100644 --- a/libs/vkd3d-shader/hlsl.c +++ b/libs/vkd3d-shader/hlsl.c @@ -1562,10 +1562,23 @@ static void dump_ir_var(struct hlsl_ctx *ctx, struct vkd3d_string_buffer *buffer static void dump_deref(struct vkd3d_string_buffer *buffer, const struct hlsl_deref *deref) { + unsigned int i; + if (deref->var) { vkd3d_string_buffer_printf(buffer, "%s", deref->var->name); - if (deref->offset.node) + if (deref->path_len) + { + vkd3d_string_buffer_printf(buffer, "["); + for (i = 0; i < deref->path_len; ++i) + { + vkd3d_string_buffer_printf(buffer, "["); + dump_src(buffer, &deref->path[i]); + vkd3d_string_buffer_printf(buffer, "]"); + } + vkd3d_string_buffer_printf(buffer, "]"); + } + else if (deref->offset.node) { vkd3d_string_buffer_printf(buffer, "["); dump_src(buffer, &deref->offset); -- 2.34.1

2 2

[PATCH vkd3d 11/12] vkd3d-shader/hlsl: Replace register offsets with index paths in input/output copies.
by Francisco Casas 15 Jul '22

15 Jul '22

Signed-off-by: Francisco Casas <fcasas(a)codeweavers.com> --- The recursive structure of prepend_input_var_copy() and append_output_var_copy() could be preserved creating additional loads to complete the paths. Otherwise we would be requiring passing whole paths as arguments. These additional loads should be handled by DCE. Still, matrix vectors are copied iteratively instead of recursively now, to avoid the boilerplate of creating new loads in this last step. Signed-off-by: Francisco Casas <fcasas(a)codeweavers.com> --- libs/vkd3d-shader/hlsl_codegen.c | 188 +++++++++++++++++++------------ 1 file changed, 114 insertions(+), 74 deletions(-) diff --git a/libs/vkd3d-shader/hlsl_codegen.c b/libs/vkd3d-shader/hlsl_codegen.c index 07c11f3f..0276fb89 100644 --- a/libs/vkd3d-shader/hlsl_codegen.c +++ b/libs/vkd3d-shader/hlsl_codegen.c @@ -239,59 +239,73 @@ static struct hlsl_ir_var *add_extern_var(struct hlsl_ctx *ctx, struct hlsl_ir_v return ext_var; } -static void prepend_input_copy(struct hlsl_ctx *ctx, struct list *instrs, struct hlsl_ir_var *var, - struct hlsl_type *type, unsigned int field_offset, unsigned int modifiers, const struct hlsl_semantic *semantic) +static void prepend_input_copy(struct hlsl_ctx *ctx, struct list *instrs, struct hlsl_ir_load *lhs, + struct hlsl_type *type, unsigned int modifiers, const struct hlsl_semantic *semantic) { - struct hlsl_ir_constant *offset; - struct hlsl_ir_store *store; - struct hlsl_ir_load *load; - struct hlsl_ir_var *input; + struct hlsl_type *vector_type = hlsl_get_vector_type(ctx, type->base_type, hlsl_type_minor_size(type)); + struct hlsl_ir_var *var = lhs->src.var; + unsigned int i; - if (type->type == HLSL_CLASS_MATRIX) + for (i = 0; i < hlsl_type_major_size(type); ++i) { - struct hlsl_type *vector_type = hlsl_get_vector_type(ctx, type->base_type, hlsl_type_minor_size(type)); - struct hlsl_semantic vector_semantic = *semantic; - unsigned int i; + struct hlsl_semantic semantic_copy = *semantic; + struct hlsl_ir_store *store; + struct hlsl_ir_constant *c; + struct hlsl_ir_var *input; + struct hlsl_ir_load *load; - for (i = 0; i < hlsl_type_major_size(type); ++i) - { - prepend_input_copy(ctx, instrs, var, vector_type, 4 * i, modifiers, &vector_semantic); - ++vector_semantic.index; - } - - return; - } + semantic_copy.index = semantic->index + i; - if (!(input = add_extern_var(ctx, var, type, modifiers, semantic, false))) - return; + if (!(input = add_extern_var(ctx, var, vector_type, modifiers, &semantic_copy, false))) + return; - if (!(load = hlsl_new_var_load(ctx, input, var->loc))) - return; - list_add_head(instrs, &load->node.entry); + if (!(load = hlsl_new_var_load(ctx, input, var->loc))) + return; + list_add_after(&lhs->node.entry, &load->node.entry); - if (!(offset = hlsl_new_uint_constant(ctx, field_offset, &var->loc))) - return; - list_add_after(&load->node.entry, &offset->node.entry); + if (type->type == HLSL_CLASS_MATRIX) + { + if (!(c = hlsl_new_uint_constant(ctx, i, &var->loc))) + return; + list_add_after(&load->node.entry, &c->node.entry); - if (!(store = hlsl_new_store(ctx, var, &offset->node, &load->node, 0, var->loc))) - return; - list_add_after(&offset->node.entry, &store->node.entry); + if (!(store = hlsl_new_store_index(ctx, &lhs->src, &c->node, &load->node, 0, var->loc))) + return; + list_add_after(&c->node.entry, &store->node.entry); + } + else + { + if (!(store = hlsl_new_store_index(ctx, &lhs->src, NULL, &load->node, 0, var->loc))) + return; + list_add_after(&load->node.entry, &store->node.entry); + } + } } -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) +static void prepend_input_struct_copy(struct hlsl_ctx *ctx, struct list *instrs, struct hlsl_ir_load *lhs, + struct hlsl_type *type) { + struct hlsl_ir_var *var = lhs->src.var; size_t i; for (i = 0; i < type->e.record.field_count; ++i) { const struct hlsl_struct_field *field = &type->e.record.fields[i]; + struct hlsl_ir_load *field_load; + struct hlsl_ir_constant *c; + + if (!(c = hlsl_new_uint_constant(ctx, i, &var->loc))) + return; + list_add_after(&lhs->node.entry, &c->node.entry); + + if (!(field_load = hlsl_new_load_index(ctx, &lhs->src, &c->node, var->loc))) + return; + list_add_after(&c->node.entry, &field_load->node.entry); if (field->type->type == HLSL_CLASS_STRUCT) - prepend_input_struct_copy(ctx, instrs, var, field->type, field_offset + field->reg_offset); + prepend_input_struct_copy(ctx, instrs, field_load, field->type); else if (field->semantic.name) - prepend_input_copy(ctx, instrs, var, field->type, - field_offset + field->reg_offset, field->modifiers, &field->semantic); + prepend_input_copy(ctx, instrs, field_load, field->type, field->modifiers, &field->semantic); else hlsl_error(ctx, &field->loc, VKD3D_SHADER_ERROR_HLSL_MISSING_SEMANTIC, "Field '%s' is missing a semantic.", field->name); @@ -302,65 +316,85 @@ static void prepend_input_struct_copy(struct hlsl_ctx *ctx, struct list *instrs, * and copy the former to the latter, so that writes to input variables work. */ static void prepend_input_var_copy(struct hlsl_ctx *ctx, struct list *instrs, struct hlsl_ir_var *var) { + struct hlsl_ir_load *load; + + if (!(load = hlsl_new_var_load(ctx, var, var->loc))) + return; + list_add_head(instrs, &load->node.entry); + if (var->data_type->type == HLSL_CLASS_STRUCT) - prepend_input_struct_copy(ctx, instrs, var, var->data_type, 0); + prepend_input_struct_copy(ctx, instrs, load, var->data_type); else if (var->semantic.name) - prepend_input_copy(ctx, instrs, var, var->data_type, 0, var->modifiers, &var->semantic); + prepend_input_copy(ctx, instrs, load, var->data_type, var->modifiers, &var->semantic); } -static void append_output_copy(struct hlsl_ctx *ctx, struct list *instrs, struct hlsl_ir_var *var, - struct hlsl_type *type, unsigned int field_offset, unsigned int modifiers, const struct hlsl_semantic *semantic) +static void append_output_copy(struct hlsl_ctx *ctx, struct list *instrs, struct hlsl_ir_load *rhs, + struct hlsl_type *type, unsigned int modifiers, const struct hlsl_semantic *semantic) { - struct hlsl_ir_constant *offset; - struct hlsl_ir_store *store; - struct hlsl_ir_var *output; - struct hlsl_ir_load *load; + struct hlsl_type *vector_type = hlsl_get_vector_type(ctx, type->base_type, hlsl_type_minor_size(type)); + struct hlsl_ir_var *var = rhs->src.var; + unsigned int i; - if (type->type == HLSL_CLASS_MATRIX) + for (i = 0; i < hlsl_type_major_size(type); ++i) { - struct hlsl_type *vector_type = hlsl_get_vector_type(ctx, type->base_type, hlsl_type_minor_size(type)); - struct hlsl_semantic vector_semantic = *semantic; - unsigned int i; - - for (i = 0; i < hlsl_type_major_size(type); ++i) - { - append_output_copy(ctx, instrs, var, vector_type, 4 * i, modifiers, &vector_semantic); - ++vector_semantic.index; - } + struct hlsl_semantic semantic_copy = *semantic; + struct hlsl_ir_store *store; + struct hlsl_ir_constant *c; + struct hlsl_ir_var *output; + struct hlsl_ir_load *load; - return; - } + semantic_copy.index = semantic->index + i; - if (!(output = add_extern_var(ctx, var, type, modifiers, semantic, true))) - return; + if (!(output = add_extern_var(ctx, var, vector_type, modifiers, &semantic_copy, true))) + return; - if (!(offset = hlsl_new_uint_constant(ctx, field_offset, &var->loc))) - return; - list_add_tail(instrs, &offset->node.entry); + if (type->type == HLSL_CLASS_MATRIX) + { + if (!(c = hlsl_new_uint_constant(ctx, i, &var->loc))) + return; + list_add_tail(instrs, &c->node.entry); - if (!(load = hlsl_new_load(ctx, var, &offset->node, type, var->loc))) - return; - list_add_after(&offset->node.entry, &load->node.entry); + if (!(load = hlsl_new_load_index(ctx, &rhs->src, &c->node, var->loc))) + return; + list_add_tail(instrs, &load->node.entry); + } + else + { + if (!(load = hlsl_new_load_index(ctx, &rhs->src, NULL, var->loc))) + return; + list_add_tail(instrs, &load->node.entry); + } - if (!(store = hlsl_new_store(ctx, output, NULL, &load->node, 0, var->loc))) - return; - list_add_after(&load->node.entry, &store->node.entry); + if (!(store = hlsl_new_simple_store(ctx, output, &load->node))) + return; + list_add_tail(instrs, &store->node.entry); + } } -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) +static void append_output_struct_copy(struct hlsl_ctx *ctx, struct list *instrs, struct hlsl_ir_load *rhs, + struct hlsl_type *type) { + struct hlsl_ir_var *var = rhs->src.var; size_t i; for (i = 0; i < type->e.record.field_count; ++i) { const struct hlsl_struct_field *field = &type->e.record.fields[i]; + struct hlsl_ir_load *field_load; + struct hlsl_ir_constant *c; + + if (!(c = hlsl_new_uint_constant(ctx, i, &var->loc))) + return; + list_add_tail(instrs, &c->node.entry); + + if (!(field_load = hlsl_new_load_index(ctx, &rhs->src, &c->node, var->loc))) + return; + list_add_tail(instrs, &field_load->node.entry); if (field->type->type == HLSL_CLASS_STRUCT) - append_output_struct_copy(ctx, instrs, var, field->type, field_offset + field->reg_offset); + append_output_struct_copy(ctx, instrs, field_load, field->type); else if (field->semantic.name) - append_output_copy(ctx, instrs, var, field->type, - field_offset + field->reg_offset, field->modifiers, &field->semantic); + append_output_copy(ctx, instrs, field_load, field->type, field->modifiers, &field->semantic); else hlsl_error(ctx, &field->loc, VKD3D_SHADER_ERROR_HLSL_MISSING_SEMANTIC, "Field '%s' is missing a semantic.", field->name); @@ -372,10 +406,16 @@ static void append_output_struct_copy(struct hlsl_ctx *ctx, struct list *instrs, * variables work. */ static void append_output_var_copy(struct hlsl_ctx *ctx, struct list *instrs, struct hlsl_ir_var *var) { + struct hlsl_ir_load *load; + + if (!(load = hlsl_new_var_load(ctx, var, var->loc))) + return; + list_add_tail(instrs, &load->node.entry); + if (var->data_type->type == HLSL_CLASS_STRUCT) - append_output_struct_copy(ctx, instrs, var, var->data_type, 0); + append_output_struct_copy(ctx, instrs, load, var->data_type); else if (var->semantic.name) - append_output_copy(ctx, instrs, var, var->data_type, 0, var->modifiers, &var->semantic); + append_output_copy(ctx, instrs, load, var->data_type, var->modifiers, &var->semantic); } static bool transform_ir(struct hlsl_ctx *ctx, bool (*func)(struct hlsl_ctx *ctx, struct hlsl_ir_node *, void *), @@ -2029,8 +2069,6 @@ int hlsl_emit_bytecode(struct hlsl_ctx *ctx, struct hlsl_ir_function_decl *entry list_move_head(&body->instrs, &ctx->static_initializers); - transform_ir(ctx, transform_deref_paths_into_offsets, body, NULL); /* TODO: move forward, remove when no longer needed */ - LIST_FOR_EACH_ENTRY(var, &ctx->globals->vars, struct hlsl_ir_var, scope_entry) { if (var->modifiers & HLSL_STORAGE_UNIFORM) @@ -2064,6 +2102,8 @@ int hlsl_emit_bytecode(struct hlsl_ctx *ctx, struct hlsl_ir_function_decl *entry append_output_var_copy(ctx, &body->instrs, entry_func->return_var); } + transform_ir(ctx, transform_deref_paths_into_offsets, body, NULL); /* TODO: move forward, remove when no longer needed */ + transform_ir(ctx, lower_broadcasts, body, NULL); while (transform_ir(ctx, fold_redundant_casts, body, NULL)); do -- 2.34.1

2 2

Re: [PATCH v2 4/5] ntdll: Fixup ICMP packet id if SOCK_DGRAM fallback is used.
by Marvin 14 Jul '22

14 Jul '22

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=119060 Your paranoid android. === build (build log) === error: patch failed: dlls/ntdll/unix/socket.c:675 error: patch failed: dlls/ntdll/unix/socket.c:581 Task: Patch failed to apply

1 0

[PATCH vkd3d 09/12] vkd3d-shader/hlsl: Move hlsl_new_offset_from_path_index() to hlsl_codegen.c.
by Francisco Casas 14 Jul '22

14 Jul '22

This can be done now, to help removing register offsets from hlsl.c and hlsl.h. Signed-off-by: Francisco Casas <fcasas(a)codeweavers.com> --- libs/vkd3d-shader/hlsl.c | 76 ------------------------------- libs/vkd3d-shader/hlsl.h | 3 -- libs/vkd3d-shader/hlsl_codegen.c | 77 ++++++++++++++++++++++++++++++++ 3 files changed, 77 insertions(+), 79 deletions(-) diff --git a/libs/vkd3d-shader/hlsl.c b/libs/vkd3d-shader/hlsl.c index 924121f0..3454e5ee 100644 --- a/libs/vkd3d-shader/hlsl.c +++ b/libs/vkd3d-shader/hlsl.c @@ -392,82 +392,6 @@ struct hlsl_type *hlsl_get_type_from_path_index(struct hlsl_ctx *ctx, const stru return NULL; } -struct hlsl_ir_node *hlsl_new_offset_from_path_index(struct hlsl_ctx *ctx, struct hlsl_block *block, - struct hlsl_type *type, struct hlsl_ir_node *offset, struct hlsl_ir_node *idx, - const struct vkd3d_shader_location *loc) -{ - struct hlsl_ir_node *idx_offset = NULL; - struct hlsl_ir_constant *c; - - list_init(&block->instrs); - - switch (type->type) - { - case HLSL_CLASS_VECTOR: - { - idx_offset = idx; - break; - } - - case HLSL_CLASS_MATRIX: - { - if (!(c = hlsl_new_uint_constant(ctx, 4, loc))) - return NULL; - list_add_tail(&block->instrs, &c->node.entry); - - if (!(idx_offset = hlsl_new_binary_expr(ctx, HLSL_OP2_MUL, &c->node, idx))) - return NULL; - list_add_tail(&block->instrs, &idx_offset->entry); - - break; - } - - case HLSL_CLASS_ARRAY: - { - unsigned int size = hlsl_type_get_array_element_reg_size(type->e.array.type); - - if (!(c = hlsl_new_uint_constant(ctx, size, loc))) - return NULL; - list_add_tail(&block->instrs, &c->node.entry); - - if (!(idx_offset = hlsl_new_binary_expr(ctx, HLSL_OP2_MUL, &c->node, idx))) - return NULL; - list_add_tail(&block->instrs, &idx_offset->entry); - - break; - } - - case HLSL_CLASS_STRUCT: - { - unsigned int field_i = hlsl_ir_constant(idx)->value[0].u; - struct hlsl_struct_field *field = &type->e.record.fields[field_i]; - - if (!(c = hlsl_new_uint_constant(ctx, field->reg_offset, loc))) - return NULL; - list_add_tail(&block->instrs, &c->node.entry); - - idx_offset = &c->node; - - break; - } - - default: - { - assert(0); - return NULL; - } - } - - if (offset) - { - if (!(idx_offset = hlsl_new_binary_expr(ctx, HLSL_OP2_ADD, offset, idx_offset))) - return NULL; - list_add_tail(&block->instrs, &idx_offset->entry); - } - - return idx_offset; -} - struct hlsl_type *hlsl_new_array_type(struct hlsl_ctx *ctx, struct hlsl_type *basic_type, unsigned int array_size) { struct hlsl_type *type; diff --git a/libs/vkd3d-shader/hlsl.h b/libs/vkd3d-shader/hlsl.h index d3885540..dd5ea1d7 100644 --- a/libs/vkd3d-shader/hlsl.h +++ b/libs/vkd3d-shader/hlsl.h @@ -737,9 +737,6 @@ struct hlsl_ir_var *hlsl_get_var(struct hlsl_scope *scope, const char *name); struct hlsl_type *hlsl_get_type_from_path_index(struct hlsl_ctx *ctx, const struct hlsl_type *type, struct hlsl_ir_node *node); -struct hlsl_ir_node *hlsl_new_offset_from_path_index(struct hlsl_ctx *ctx, struct hlsl_block *block, - struct hlsl_type *type, struct hlsl_ir_node *offset, struct hlsl_ir_node *idx, - const struct vkd3d_shader_location *loc); struct hlsl_type *hlsl_new_array_type(struct hlsl_ctx *ctx, struct hlsl_type *basic_type, unsigned int array_size); struct hlsl_ir_node *hlsl_new_binary_expr(struct hlsl_ctx *ctx, enum hlsl_ir_expr_op op, struct hlsl_ir_node *arg1, diff --git a/libs/vkd3d-shader/hlsl_codegen.c b/libs/vkd3d-shader/hlsl_codegen.c index 513e599e..67229195 100644 --- a/libs/vkd3d-shader/hlsl_codegen.c +++ b/libs/vkd3d-shader/hlsl_codegen.c @@ -21,6 +21,83 @@ #include "hlsl.h" #include <stdio.h> +/* TODO: remove when no longer needed, only used for replace_deref_path_with_offset() */ +static struct hlsl_ir_node *hlsl_new_offset_from_path_index(struct hlsl_ctx *ctx, struct hlsl_block *block, + struct hlsl_type *type, struct hlsl_ir_node *offset, struct hlsl_ir_node *idx, + const struct vkd3d_shader_location *loc) +{ + struct hlsl_ir_node *idx_offset = NULL; + struct hlsl_ir_constant *c; + + list_init(&block->instrs); + + switch (type->type) + { + case HLSL_CLASS_VECTOR: + { + idx_offset = idx; + break; + } + + case HLSL_CLASS_MATRIX: + { + if (!(c = hlsl_new_uint_constant(ctx, 4, loc))) + return NULL; + list_add_tail(&block->instrs, &c->node.entry); + + if (!(idx_offset = hlsl_new_binary_expr(ctx, HLSL_OP2_MUL, &c->node, idx))) + return NULL; + list_add_tail(&block->instrs, &idx_offset->entry); + + break; + } + + case HLSL_CLASS_ARRAY: + { + unsigned int size = hlsl_type_get_array_element_reg_size(type->e.array.type); + + if (!(c = hlsl_new_uint_constant(ctx, size, loc))) + return NULL; + list_add_tail(&block->instrs, &c->node.entry); + + if (!(idx_offset = hlsl_new_binary_expr(ctx, HLSL_OP2_MUL, &c->node, idx))) + return NULL; + list_add_tail(&block->instrs, &idx_offset->entry); + + break; + } + + case HLSL_CLASS_STRUCT: + { + unsigned int field_i = hlsl_ir_constant(idx)->value[0].u; + struct hlsl_struct_field *field = &type->e.record.fields[field_i]; + + if (!(c = hlsl_new_uint_constant(ctx, field->reg_offset, loc))) + return NULL; + list_add_tail(&block->instrs, &c->node.entry); + + idx_offset = &c->node; + + break; + } + + default: + { + assert(0); + return NULL; + } + } + + if (offset) + { + if (!(idx_offset = hlsl_new_binary_expr(ctx, HLSL_OP2_ADD, offset, idx_offset))) + return NULL; + list_add_tail(&block->instrs, &idx_offset->entry); + } + + return idx_offset; +} + /* TODO: remove when no longer needed, only used for transform_deref_paths_into_offsets() */ static void replace_deref_path_with_offset(struct hlsl_ctx *ctx, struct hlsl_deref *deref, struct hlsl_ir_node *instr) -- 2.34.1

3 5

Re: [PATCH 1/1] shell32: Return stub bitmap in IShellItemImageFactory::GetImage.
by Marvin 14 Jul '22

14 Jul '22

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=119036 Your paranoid android. === w1064 (32 bit report) === shell32: shlfolder.c:4976: Test failed: Didn't expect a WM_USER_NOTIFY message (event: 2) === w10pro64 (32 bit report) === shell32: shlfolder.c:4967: Test failed: Expected PIDL to be NULL shlfolder.c:4976: Test failed: Didn't expect a WM_USER_NOTIFY message (event: 2) === w1064v1809 (64 bit report) === shell32: shlfolder.c:4959: Test failed: RMDIR: expected notification type 10, got: 40000 === w10pro64_en_AE_u8 (64 bit report) === shell32: shlfolder.c:4976: Test failed: Didn't expect a WM_USER_NOTIFY message (event: 2) shlfolder.c:4959: Test failed: RMDIR: expected notification type 10, got: 40000 === w10pro64_ar (64 bit report) === shell32: shlfolder.c:4959: Test failed: MKDIR: expected notification type 8, got: 40000 === w10pro64_ja (64 bit report) === shell32: shlfolder.c:4959: Test failed: MKDIR: expected notification type 8, got: 40000

1 0

Re: [PATCH v3 2/2] win32u/window: Ignore changing WS_EX_TOPMOST for message-only windows.
by Marvin 14 Jul '22

14 Jul '22

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=119031 Your paranoid android. === w1064_tsign (64 bit report) === user32: win.c:10918: Test failed: pos = 014a015e === debian11 (32 bit report) === user32: win.c:8969: Test failed: Unexpected event was delivered === debian11 (32 bit German report) === user32: win.c:8969: Test failed: Unexpected event was delivered === debian11 (32 bit Hindi:India report) === user32: win.c:8969: Test failed: Unexpected event was delivered === debian11 (32 bit Japanese:Japan report) === user32: win.c:8969: Test failed: Unexpected event was delivered === debian11 (32 bit WoW report) === user32: win.c:8969: Test failed: Unexpected event was delivered === debian11 (64 bit WoW report) === user32: win.c:8969: Test failed: Unexpected event was delivered

1 0

Re: [PATCH v3 1/2] user32/tests: Check that message-only windows ignore WS_EX_TOPMOST.
by Marvin 14 Jul '22

14 Jul '22

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=119030 Your paranoid android. === w10pro64_en_AE_u8 (64 bit report) === user32: win.c:4400: Test failed: message 0200 available === debian11 (32 bit report) === user32: win.c:8961: Test failed: Last error unexpectedly set to 0 === debian11 (32 bit Arabic:Morocco report) === user32: win.c:8961: Test failed: Last error unexpectedly set to 0 === debian11 (32 bit German report) === user32: win.c:8961: Test failed: Last error unexpectedly set to 0 === debian11 (32 bit French report) === user32: win.c:8961: Test failed: Last error unexpectedly set to 0 === debian11 (32 bit Hebrew:Israel report) === user32: win.c:8961: Test failed: Last error unexpectedly set to 0 === debian11 (32 bit Hindi:India report) === user32: win.c:8961: Test failed: Last error unexpectedly set to 0 === debian11 (32 bit Japanese:Japan report) === user32: win.c:8961: Test failed: Last error unexpectedly set to 0 === debian11 (32 bit Chinese:China report) === user32: win.c:8961: Test failed: Last error unexpectedly set to 0 === debian11 (32 bit WoW report) === user32: win.c:8961: Test failed: Last error unexpectedly set to 0 === debian11 (64 bit WoW report) === user32: win.c:8961: Test failed: Last error unexpectedly set to 0

1 0

Re: [PATCH v2 1/2] rpcrt4/tests: Add I_RpcBindingInqLocalClientPID() tests.
by Marvin 14 Jul '22

14 Jul '22

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=119010 Your paranoid android. === w1064_tsign (32 bit report) === rpcrt4: server.c:2270: Test failed: RpcBindingFree === w1064_tsign (64 bit report) === rpcrt4: server.c:2270: Test failed: RpcBindingFree === w10pro64_ja (64 bit report) === rpcrt4: 14fc:server: unhandled exception 000006be at 00007FFA40864F69 === w10pro64_zh_CN (64 bit report) === rpcrt4: 2048:server: unhandled exception 000006be at 00007FFD3A124F69

1 0

Re: [PATCH v2 2/2] rpcrt4: Implement I_RpcBindingInqLocalClientPID().
by Marvin 14 Jul '22

14 Jul '22

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=119011 Your paranoid android. === w8adm (32 bit report) === rpcrt4: server.c:2263: Test failed: RpcBindingFree === w1064 (32 bit report) === rpcrt4: server.c:2263: Test failed: RpcBindingFree === w1064_tsign (32 bit report) === rpcrt4: server.c:2263: Test failed: RpcBindingFree === w10pro64 (32 bit report) === rpcrt4: server.c:2263: Test failed: RpcBindingFree === w1064_adm (64 bit report) === rpcrt4: 1ae0:server: unhandled exception 000006be at 00007FFAE69F4F69 === w1064_tsign (64 bit report) === rpcrt4: server.c:2263: Test failed: RpcBindingFree === w10pro64_en_AE_u8 (64 bit report) === rpcrt4: 0460:server: unhandled exception 000006be at 00007FF99B7B4F69 === w10pro64_zh_CN (64 bit report) === rpcrt4: 16a8:server: unhandled exception 000006be at 00007FFD3A124F69

1 0

Re: [PATCH 1/2] rpcrt4/tests: Add I_RpcBindingInqLocalClientPID() tests.
by Marvin 14 Jul '22

14 Jul '22

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=118991 Your paranoid android. === w1064_tsign (32 bit report) === rpcrt4: server.c:2270: Test failed: RpcBindingFree === w1064 (64 bit report) === rpcrt4: server.c:2270: Test failed: RpcBindingFree === w1064_2qxl (64 bit report) === rpcrt4: server.c:2270: Test failed: RpcBindingFree === w1064_tsign (64 bit report) === rpcrt4: server.c:2270: Test failed: RpcBindingFree === w10pro64 (64 bit report) === rpcrt4: server.c:2270: Test failed: RpcBindingFree === w10pro64_en_AE_u8 (64 bit report) === rpcrt4: 0958:server: unhandled exception 000006be at 00007FF99B7B4F69 === w10pro64_ja (64 bit report) === rpcrt4: 0ef4:server: unhandled exception 000006be at 00007FFA40864F69

1 0

Re: [PATCH 7/7] shell32: Implement SHOpenFolderAndSelectItems().
by Marvin 14 Jul '22

14 Jul '22

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=118986 Your paranoid android. === w1064v1809 (32 bit report) === shell32: shlfolder.c:4991: Test failed: RMDIR: expected notification type 10, got: 40000 === w1064 (32 bit report) === shell32: shlfolder.c:5008: Test failed: Didn't expect a WM_USER_NOTIFY message (event: 2) === w1064_tsign (32 bit report) === shell32: shlfolder.c:5008: Test failed: Didn't expect a WM_USER_NOTIFY message (event: 2) === w1064v1809 (64 bit report) === shell32: shlfolder.c:5008: Test failed: Didn't expect a WM_USER_NOTIFY message (event: 2) === w1064 (64 bit report) === shell32: shlfolder.c:4991: Test failed: RMDIR: expected notification type 10, got: 40000 === w10pro64_en_AE_u8 (64 bit report) === shell32: shlfolder.c:4991: Test failed: RMDIR: expected notification type 10, got: 40000 === w10pro64_ar (64 bit report) === shell32: shlfolder.c:4991: Test failed: RMDIR: expected notification type 10, got: 4000000 shlfolder.c:4999: Test failed: Expected PIDL to be NULL shlfolder.c:4991: Test failed: RMDIR: expected notification type 10, got: 40000

1 0

Re: [PATCH 6/7] shell32/tests: Add SHOpenFolderAndSelectItems() tests.
by Marvin 14 Jul '22

14 Jul '22

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=118985 Your paranoid android. === w1064v1809 (32 bit report) === shell32: shlfolder.c:5008: Test failed: Didn't expect a WM_USER_NOTIFY message (event: 2) === w1064 (64 bit report) === shell32: shlfolder.c:4991: Test failed: RMDIR: expected notification type 10, got: 40000 === w10pro64 (64 bit report) === shell32: shlfolder.c:4991: Test failed: RMDIR: expected notification type 10, got: 4000000 shlfolder.c:4999: Test failed: Expected PIDL to be NULL === w10pro64_en_AE_u8 (64 bit report) === shell32: shlfolder.c:4991: Test failed: RMDIR: expected notification type 10, got: 40000 === w10pro64_ar (64 bit report) === shell32: shlfolder.c:4991: Test failed: RMDIR: expected notification type 10, got: 40000 === w10pro64_ja (64 bit report) === shell32: shlfolder.c:4991: Test failed: RMDIR: expected notification type 10, got: 40000

1 0

Re: [PATCH v2 6/6] kernelbase: Implement PrefetchVirtualMemory.
by Marvin 14 Jul '22

14 Jul '22

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=118952 Your paranoid android. === debian11 (build log) === error: patch failed: include/winbase.h:1760 error: patch failed: include/winnt.h:788 error: patch failed: include/winternl.h:1993 error: patch failed: tools/winapi/win32.api:3245 error: patch failed: dlls/ntdll/tests/virtual.c:41 error: patch failed: dlls/ntdll/ntdll.spec:388 error: patch failed: dlls/ntdll/unix/loader.c:310 error: patch failed: dlls/wow64/struct32.h:650 error: patch failed: dlls/wow64/syscall.h:211 error: patch failed: dlls/wow64/virtual.c:33 error: patch failed: dlls/kernel32/tests/virtual.c:37 error: patch failed: dlls/kernel32/tests/virtual.c:4231 error: patch failed: dlls/kernelbase/memory.c:415 Task: Patch failed to apply === debian11 (build log) === error: patch failed: include/winbase.h:1760 error: patch failed: include/winnt.h:788 error: patch failed: include/winternl.h:1993 error: patch failed: tools/winapi/win32.api:3245 error: patch failed: dlls/ntdll/tests/virtual.c:41 error: patch failed: dlls/ntdll/ntdll.spec:388 error: patch failed: dlls/ntdll/unix/loader.c:310 error: patch failed: dlls/wow64/struct32.h:650 error: patch failed: dlls/wow64/syscall.h:211 error: patch failed: dlls/wow64/virtual.c:33 error: patch failed: dlls/kernel32/tests/virtual.c:37 error: patch failed: dlls/kernel32/tests/virtual.c:4231 error: patch failed: dlls/kernelbase/memory.c:415 Task: Patch failed to apply

1 0

Re: [PATCH v8 7/7] ntoskrnl: Set device ContainerID from driver
by Marvin 14 Jul '22

14 Jul '22

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=118939 Your paranoid android. === debian11 (32 bit Hebrew:Israel report) === ntoskrnl.exe: driver_pnp.c:706: Test failed: Got 1 remove events.

1 0

Re: [PATCH 1/4] ws2_32/tests: Add some tests for NtReadFile() and NtWriteFile() on sockets.
by Marvin 14 Jul '22

14 Jul '22

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=118995 Your paranoid android. === debian11 (32 bit Hebrew:Israel report) === ws2_32: afd.c:2716: Test failed: got size 5

1 0

Re: [PATCH 2/2] rpcrt4: Implement I_RpcBindingInqLocalClientPID().
by Marvin 14 Jul '22

14 Jul '22

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=118992 Your paranoid android. === w864 (32 bit report) === rpcrt4: server.c:2263: Test failed: RpcBindingFree === w1064 (32 bit report) === rpcrt4: server.c:2263: Test failed: RpcBindingFree === w1064_tsign (32 bit report) === rpcrt4: server.c:2263: Test failed: RpcBindingFree === w10pro64 (32 bit report) === rpcrt4: server.c:2263: Test failed: RpcBindingFree === w1064_tsign (64 bit report) === rpcrt4: server.c:2263: Test failed: RpcBindingFree === w10pro64 (64 bit report) === rpcrt4: server.c:2263: Test failed: RpcBindingFree === w10pro64_en_AE_u8 (64 bit report) === rpcrt4: 0e54:server: unhandled exception 000006be at 00007FF99B7B4F69

1 0

Re: [PATCH v8 2/7] ntoskrnl/tests: Add test for getting SPDRP_BASE_CONTAINERID from PnP driver
by Marvin 14 Jul '22

14 Jul '22

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=118934 Your paranoid android. === debian11 (32 bit Hindi:India report) === ntoskrnl.exe: driver_pnp.c:706: Test failed: Got 1 remove events.

1 0

Re: [PATCH v7 7/7] ntoskrnl: Set device ContainerID from driver
by Marvin 14 Jul '22

14 Jul '22

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=118932 Your paranoid android. === w7u_2qxl (32 bit report) === ntoskrnl.exe: ntoskrnl.c:1655: Test failed: got size 78 === w7u_el (32 bit report) === ntoskrnl.exe: ntoskrnl.c:1655: Test failed: got size 78 === w8 (32 bit report) === ntoskrnl.exe: ntoskrnl.c:1655: Test failed: got size 78 === w1064_tsign (64 bit report) === ntoskrnl.exe: ntoskrnl.c:1655: Test failed: got size 78 === debian11 (32 bit report) === ntoskrnl.exe: ntoskrnl.c:1655: Test failed: got size 39 driver_pnp.c:706: Test failed: Got 1 remove events. === debian11 (32 bit Arabic:Morocco report) === ntoskrnl.exe: ntoskrnl.c:1655: Test failed: got size 39 === debian11 (32 bit German report) === ntoskrnl.exe: ntoskrnl.c:1655: Test failed: got size 39 === debian11 (32 bit French report) === ntoskrnl.exe: ntoskrnl.c:1655: Test failed: got size 39 driver_pnp.c:706: Test failed: Got 1 remove events. === debian11 (32 bit Hebrew:Israel report) === ntoskrnl.exe: ntoskrnl.c:1655: Test failed: got size 39 === debian11 (32 bit Hindi:India report) === ntoskrnl.exe: ntoskrnl.c:1655: Test failed: got size 39 === debian11 (32 bit Japanese:Japan report) === ntoskrnl.exe: ntoskrnl.c:1655: Test failed: got size 39 === debian11 (32 bit Chinese:China report) === ntoskrnl.exe: ntoskrnl.c:1655: Test failed: got size 39 === debian11 (64 bit WoW report) === ntoskrnl.exe: ntoskrnl.c:1655: Test failed: got size 39

1 0

Re: [PATCH v7 2/7] ntoskrnl/tests: Add test for getting SPDRP_BASE_CONTAINERID from PnP driver
by Marvin 14 Jul '22

14 Jul '22

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=118927 Your paranoid android. === debian11 (32 bit French report) === ntoskrnl.exe: driver_pnp.c:736: Test failed: expected IRP_MN_REMOVE_DEVICE === debian11 (32 bit Hebrew:Israel report) === ntoskrnl.exe: driver_pnp.c:706: Test failed: Got 1 remove events. === debian11 (32 bit Hindi:India report) === ntoskrnl.exe: driver_pnp.c:706: Test failed: Got 1 remove events.

1 0

Re: [PATCH v4 4/5] mshtml: Implement overrideMimeType for XMLHttpRequest.
by Marvin 14 Jul '22

14 Jul '22

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=118924 Your paranoid android. === w7u_adm (32 bit report) === mshtml: script.c:644: Test failed: L"/index.html?es5.js:date_now: unexpected Date.now() result 1657738156862 expected 1657738156925"

1 0

Re: [PATCH 1/1] win32u: Send WM_NCPAINT as notify message in send_ncpaint().
by Marvin 14 Jul '22

14 Jul '22

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=118970 Your paranoid android. === w1064_2qxl (64 bit report) === user32: win.c:4579: Test failed: hwnd 000000000001024C/000000000001024C message 0200 win.c:4583: Test failed: hwnd 000000000001024C/000000000001024C message 0201 win.c:4592: Test failed: hwnd 00000000001002B8/00000000001002B8 message 0202 win.c:4595: Test failed: hwnd 00000000001002B8/00000000001002B8 message 0201

1 0

Re: [PATCH v4 3/5] mshtml: Check for valid XML Content-Type for responseXML in IE10+ modes.
by Marvin 14 Jul '22

14 Jul '22

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=118923 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:350: Test failed: expected Exec_SETTITLE htmldoc.c:2859: Test failed: unexpected call Exec_SETTITLE

1 0

Re: [PATCH v4 2/5] mshtml: Respect LOAD_CALL_CONTENT_SNIFFERS when using detected mime type.
by Marvin 13 Jul '22

13 Jul '22

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=118922 Your paranoid android. === w10pro64_ar (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 v3 4/5] mshtml: Implement overrideMimeType for XMLHttpRequest.
by Marvin 13 Jul '22

13 Jul '22

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=118919 Your paranoid android. === 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 === w10pro64_zh_CN (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 === w7u_adm (32 bit report) === mshtml: script.c:644: Test failed: L"/index.html?es5.js:date_now: unexpected Date.now() result 1657734051954 expected 1657734052016"

1 0

[PATCH 1/5] msvcr120/tests: Add missing newlines to messages.
by Torge Matthies 13 Jul '22

13 Jul '22

Signed-off-by: Torge Matthies <tmatthies(a)codeweavers.com> --- dlls/msvcr120/tests/msvcr120.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/dlls/msvcr120/tests/msvcr120.c b/dlls/msvcr120/tests/msvcr120.c index 88a32b382ef..ac35076af03 100644 --- a/dlls/msvcr120/tests/msvcr120.c +++ b/dlls/msvcr120/tests/msvcr120.c @@ -1375,7 +1375,7 @@ static void __cdecl chore_proc(_UnrealizedChore *_this) MSVCRT_bool canceling = call_func1( p__StructuredTaskCollection__IsCanceling, chore->chore.task_collection); - ok(!canceling, "Task is already canceling"); + ok(!canceling, "Task is already canceling\n"); } if (!chore->wait_event) @@ -1399,7 +1399,7 @@ static void __cdecl chore_proc(_UnrealizedChore *_this) MSVCRT_bool canceling = call_func1( p__StructuredTaskCollection__IsCanceling, chore->chore.task_collection); - ok(canceling, "Task is not canceling"); + ok(canceling, "Task is not canceling\n"); } } -- 2.37.0

3 9

Building with MSVC
by Gisle Vanem 13 Jul '22

13 Jul '22

Hello list. My first post here. First off, I'm not using Linux and does not want to. I'm on Win-10 and would (just for fun) try to build e.g. Wine's 'explorer.exe' and other tool using MSVC-2022 and/or clang-cl v.13. I see that the sources are full of '_MSC_VER' and assume it would be possible. I've built all 'tools/' program just fine with a set of home-brewed GNU-makefiles. But have some problems with missing symbols during link. For example these: _NtUserMessageCall@28 _DrawCaptionTempW@28 MSDN came up blank for these. But I see that 'NtUserMessageCall@28' is exported from my normal 'win32u.dll' on Win-10. But there's no entry for them in any Win-Kit library AFAICS. So are we supposed to use Wine's 'win32u.dll' as a trampoline to the real and undocumented functions? Then there is 'DrawCaptionTempW'. I find no prototype for it in the Win-Kit SDK. But I find it in TDM-MinGW's 'libuser32.a'. Ref: https://gist.github.com/wbenny/123a41973af776df9c7d5610586b9e9d I've read the FAQ so I'm not sure my effort is supported at all. Or if some MinGW-distro is required. -- --gv

2 2

Re: [PATCH v6 7/7] ntoskrnl: Set device ContainerID from driver
by Marvin 13 Jul '22

13 Jul '22

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=118911 Your paranoid android. === w7u_2qxl (32 bit report) === ntoskrnl.exe: ntoskrnl.c:1654: Test failed: got size 78 ntoskrnl.c:1655: Test failed: got container ID "{" === w7u_el (32 bit report) === ntoskrnl.exe: ntoskrnl.c:1654: Test failed: got size 78 ntoskrnl.c:1655: Test failed: got container ID "{" === w8 (32 bit report) === ntoskrnl.exe: ntoskrnl.c:1654: Test failed: got size 78 ntoskrnl.c:1655: Test failed: got container ID "{" === w1064_tsign (64 bit report) === ntoskrnl.exe: ntoskrnl.c:1654: Test failed: got size 78 ntoskrnl.c:1655: Test failed: got container ID "{"

1 0

Re: [PATCH v6 2/7] ntoskrnl/tests: Add test for getting SPDRP_BASE_CONTAINERID from PnP driver
by Marvin 13 Jul '22

13 Jul '22

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=118906 Your paranoid android. === debian11 (32 bit report) === ntoskrnl.exe: driver_pnp.c:706: Test failed: Got 1 remove events.

1 0

Re: [PATCH 2/2] ddraw/tests: Build ddraw7.c without -DWINE_NO_LONG_TYPES.
by Marvin 13 Jul '22

13 Jul '22

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=118887 Your paranoid android. === w8adm (32 bit report) === ddraw: ddraw7.c:18840: Test failed: Got unexpected color 0x00000040.

1 0

[PATCH 0/4] MR384: winsock: Support fallback to ICMP over SOCK_DGRAM on Linux
by Paul Gofman (＠gofman) 13 Jul '22

13 Jul '22

ICMP over SOCK_DGRAM is already used in ndispproxy.sys. But apps may also use ICMP directly over SOCK_RAW (Hardspace: Shipbreaker is an example) and that requires admin privileges on Linux (or setcap cap_net_raw+ep on wineserver). AF_INET / SOCK_RAW / IPPROTO_ICMP works on Windows without admin privileges. Comments: - IP, ICMP header structures and chksum() functions are taken from ndisproxy.sys:icmp_echo.c; - ICMP over DGRAM, while designed specifically to allow ICMP without admin permissions, still needs some setup Linux, /proc/sys/net/ipv4/ping_group_range controls that. Such socket creation fails on Testbot Debian machines so I left skip() path in test_icmp(); - Linux substitute local port number instead of provided ICMP packet id, while the referenced game depends on reply id matching the id it provided in request. So the last part performs the fixup. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/384

6 14

Re: [PATCH v5 7/8] ntoskrnl: Set device ContainerID from driver
by Marvin 12 Jul '22

12 Jul '22

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=118863 Your paranoid android. === w7u_2qxl (32 bit report) === ntoskrnl.exe: ntoskrnl.c:1654: Test failed: got size 78 ntoskrnl.c:1655: Test failed: got container ID "{" === w7u_el (32 bit report) === ntoskrnl.exe: ntoskrnl.c:1654: Test failed: got size 78 ntoskrnl.c:1655: Test failed: got container ID "{" === w8 (32 bit report) === ntoskrnl.exe: ntoskrnl.c:1654: Test failed: got size 78 ntoskrnl.c:1655: Test failed: got container ID "{" === w1064_tsign (64 bit report) === ntoskrnl.exe: ntoskrnl.c:1654: Test failed: got size 78 ntoskrnl.c:1655: Test failed: got container ID "{" === debian11 (32 bit Hebrew:Israel report) === ntoskrnl.exe: driver_pnp.c:706: Test failed: Got 1 remove events. === debian11 (32 bit Hindi:India report) === ntoskrnl.exe: driver_pnp.c:706: Test failed: Got 1 remove events.

1 0

Re: [PATCH v4 9/9] ntoskrnl/tests: Add test for getting SPDRP_BASE_CONTAINERID from PnP driver
by Marvin 12 Jul '22

12 Jul '22

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=118840 Your paranoid android. === w7u_2qxl (32 bit report) === ntoskrnl.exe: ntoskrnl.c:1654: Test failed: got size 78 ntoskrnl.c:1655: Test failed: got container ID "{" === w7u_el (32 bit report) === ntoskrnl.exe: ntoskrnl.c:1654: Test failed: got size 78 ntoskrnl.c:1655: Test failed: got container ID "{" === w8 (32 bit report) === ntoskrnl.exe: ntoskrnl.c:1654: Test failed: got size 78 ntoskrnl.c:1655: Test failed: got container ID "{" ntoskrnl.c:1702: Test failed: got 0 child removal messages ntoskrnl.c:1719: Test failed: got 0 child removal messages === w1064_tsign (64 bit report) === ntoskrnl.exe: ntoskrnl.c:1654: Test failed: got size 78 ntoskrnl.c:1655: Test failed: got container ID "{" === debian11 (32 bit Hebrew:Israel report) === ntoskrnl.exe: driver_pnp.c:706: Test failed: Got 1 remove events.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel