On Mon Jun 30 13:17:20 2025 +0000, Rémi Bernon wrote:
> Fwiw in general output parameters aren't checked in the error cases,
> because it shouldn't matter what happens to them. For cases where it
> *does* matter (like whether they should be zeroed), the params are set
> before calling to some arbitrary and different value (0xdeadbeef) from
> the expected.
> In particular, at this point these tests succeed already because the
> stub doesn't change the parameter values. Same thing below.
> ```suggestion:-3+0
> hr = DevGetObjects( DevObjectTypeDeviceInterface, DevQueryFlagNone,
> 1, NULL, 0, NULL, &len, &objects );
> todo_wine ok( hr == HRESULT_FROM_WIN32( ERROR_INVALID_PARAMETER ),
> "got hr %#lx\n", hr );
> ```
Gotcha, removed the unnecessary checks in the latest revision, thanks.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/8438#note_108281
On Fri Jun 27 20:34:30 2025 +0000, Vibhav Pant wrote:
> changed this line in [version 4 of the diff](/wine/wine/-/merge_requests/8438/diffs?diff_id=189335&start_sha=047cdc41c97e2a1e39d221cc83e8b18b318c28c7#2c4a05158dcf4c9a716dbcdc3463badaebf121b3_28_28)
Ah, missed this. Thanks.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/8438#note_108279
On Fri Jun 27 20:34:30 2025 +0000, Vibhav Pant wrote:
> changed this line in [version 4 of the diff](/wine/wine/-/merge_requests/8438/diffs?diff_id=189335&start_sha=047cdc41c97e2a1e39d221cc83e8b18b318c28c7#ffd51de087e78a6f8a5f2f1d1131c2f4d41ba745_36_35)
Yup, that's easier to read. Fixed, thanks.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/8438#note_108278
The comment is added in a later change, when it really matters. For now the entries aren't cached.
Fwiw I kept a "cache" name for the stack variable but it should probably not even be named like that, it's not a cache. I don't think it matters much anyway, the code isn't so complicated.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/8445#note_108273
```
+static NTSTATUS get_inproc_sync( HANDLE handle, struct inproc_sync *cache, struct inproc_sync **out )
```
You've changed these parameter names to make them less clear, and gotten rid of the comment that explains what they're for. How is this an improvement?
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/8445#note_108272
On Fri Jun 27 15:38:57 2025 +0000, Huw Davies wrote:
> After the third commit I'm getting
> ```
> tts.c:1060: Test succeeded inside todo block: got 0.
> ```
> which is fixed after the final commit.
Fixed.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/8390#note_108256
These patches make a test case attached to the bug https://bugs.winehq.org/show_bug.cgi?id=33190 work.
--
v6: win32u: NtGdiExtTextOutW() should translate x,y from logical to device units at the last step.
win32u: Fix device<->world width/height converters.
win32u: Use slightly more readable names for DP/LP converters.
win32u: Use correct helper for converting width to device units.
gdi32/tests: Add some tests for rotated font metrics.
https://gitlab.winehq.org/wine/wine/-/merge_requests/5068
Although I have trouble reproducing it I still experience weird test failures whenever I create or updated separate MRs in a short amount of time. These failures are usually coming from unexpected display settings, although each job is running within docker in an isolated environment.
I don't have any explanation for this, and I have confirmed that separate X server are spawned. However, the prefix used for the tests is initialized to /home/gitlab/.wine and I suspect this could perhaps be mounted and shared across containers? It could also explain the failures, if, for instance wineserver starts while another instance (invisible as isolated in a separate container) is running and has updated the registry on disk with different display settings while the tests are being executed.
This is hypothetical but nonetheless I think it's better to keep the prefix in a job workspace sub-directory.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/8452