Currently, if a probe fails, it will print the line number of the [test]
block the probe is in, not the line number of the probe itself. This
makes it somewhat difficult to debug.
This commit makes it print the line number that a test fails at.
This code was actually written by @hverbeet for my first attempt at fixing this, !499.
CC @zfigura
--
v3: tests: Print the failing line numbers when a test fails.
https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/516
Many of these patches are small, but the series can be split in two if necessary.
--
v6: vkd3d-shader/spirv: Handle ITOI and UTOU in spirv_compiler_map_alu_instruction().
vkd3d-shader/spirv: Support UINT64 source in spirv_compiler_emit_bool_cast().
vkd3d-shader/spirv: Support 64-bit sources in spirv_compiler_emit_int_div().
vkd3d-shader/spirv: Introduce a UINT64 component type.
vkd3d-shader/spirv: Introduce a data_type_is_64_bit() helper function.
vkd3d-shader/spirv: Use data_type_is_integer() in spirv_compiler_emit_neg().
vkd3d: Pass int64 capability info to vkd3d-shader.
https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/490
Currently there is `NtContinue()` test only for `aarch64` so implement it for amd64 aswell.
This implementation is very similar to `aarch64` and it's very basic test.
It doesn't change/test `ContextFlags` so it won't catch https://bugs.winehq.org/show_bug.cgi?id=56050 but that can be implemented later on top of this.
--
v5: ntdll/tests: Implement test_continue() for amd64
https://gitlab.winehq.org/wine/wine/-/merge_requests/4720
I think this is a security issue. Listening to 0.0.0.0 instead of my VPN address that is not yet up is a problem.
With the fix, the bind fails if the address is invalid.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/4760
On Sat Dec 30 18:30:27 2023 +0000, Dāvis Mosāns (davispuh) wrote:
> changed this line in [version 3 of the diff](/wine/wine/-/merge_requests/4720/diffs?diff_id=91593&start_sha=7ed40b96224c3125f2ecbda44a47cf553e1cb82a#1104a825a741495a2a3c3093b4d85d95e4f8180f_4467_4468)
Are you suggesting to clear them? I don't think that's good idea since most of them will be zeros anyway. Current implementation allows to more easily see if something doesn't get restored back. They all are filled with particular pattern.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/4720#note_56500