November 2016 - Wine-Devel - list.winehq.org

Re: [2/5] strmbase: Add validation checks when updating source rectangle.

by Andrew Eikum

On Fri, Nov 25, 2016 at 01:10:08AM +0900, Akihiro Sagawa wrote: > Thanks for reviewing. I sent v2 patch set based on your helpful comments. > It also includes fix of underlying copy-paste error. > New patches look good, thanks for working on this! Andrew

Nov. 28, 2016

Re: [PATCH 03/10] server: Use async object to transfer IRP result to client.

by Alexandre Julliard

Jacek Caban <jacek(a)codeweavers.com> writes: > diff --git a/server/file.h b/server/file.h > index c0a53a2..75a2e03 100644 > --- a/server/file.h > +++ b/server/file.h > @@ -53,6 +53,8 @@ struct fd_ops > void (*reselect_async)( struct fd *, struct async_queue *queue ); > /* cancel an async operation */ > int (*cancel_async)(struct fd *, struct process *process, struct thread *thread, client_ptr_t iosb); > + /* find an async operation in queues */ > + struct async *(*find_async)( struct fd *fd, struct process *process, client_ptr_t client_async ); > }; I think a per-process list of async/iosb would make more sense. There should be nothing file type specific about finding an async. It could probably be used to get rid of cancel_async() too. -- Alexandre Julliard julliard(a)winehq.org

Nov. 28, 2016

Re: Do we delete spammers accounts from bugzilla?

by Bruno Jesus

On Thu, Oct 13, 2016 at 11:18 PM, Sebastian Lackner <sebastian(a)fds-team.de> wrote: > Today there was so much spam that I finally decided to write a script for > it. ;) For all people interested, the script is available here: > https://github.com/slackner/bugzilla-tools/blob/master/delete_spam.py > > Usage: ./delete_spam.py ID [ID ...] > > So far the script does not implement any actual spam detection, it only > simplifies the cleanup task. The script uses the Bugzilla xmlrpc API to > disable the guilty bug creator, and also updates the bug status itself > (change title, hide comments, and so on). If someone wants to contribute > any improvements, patches and pull-requests are welcome. *g* ;) This is pure awesomeness, I'm using it from now on.

Nov. 28, 2016

Re: [v2] cmd/tests: chaining rules of pipe and else

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://testbot.winehq.org/JobDetails.pl?Key=26937 Your paranoid android. === wxppro (32 bit) === batch.c:313: Test failed: unexpected char 0x2d position 0 in line 391 (got '---', wanted 'g2:[g1,g2]') batch.c:313: Test failed: unexpected char 0x2d position 0 in line 393 (got '---', wanted 'h3:[h2:[h1,h2],h3]@or_broken(a)h3:[h2:,h3]') batch.c:313: Test failed: unexpected char 0x2d position 0 in line 395 (got '---', wanted 'i4:[i3:[i2:[i1,i2],i3],i4]@or_broken(a)i4:[i3:[i2:,i3],i4]@or_broken(a)i4:[i3:,i4]') === w2003std (32 bit) === batch.c:313: Test failed: unexpected char 0x2d position 0 in line 391 (got '---', wanted 'g2:[g1,g2]') batch.c:313: Test failed: unexpected char 0x2d position 0 in line 393 (got '---', wanted 'h3:[h2:[h1,h2],h3]@or_broken(a)h3:[h2:,h3]') batch.c:313: Test failed: unexpected char 0x2d position 0 in line 395 (got '---', wanted 'i4:[i3:[i2:[i1,i2],i3],i4]@or_broken(a)i4:[i3:[i2:,i3],i4]@or_broken(a)i4:[i3:,i4]') === wvistau64 (32 bit) === batch.c:313: Test failed: unexpected char 0x2d position 0 in line 391 (got '---', wanted 'g2:[g1,g2]') batch.c:313: Test failed: unexpected char 0x2d position 0 in line 393 (got '---', wanted 'h3:[h2:[h1,h2],h3]@or_broken(a)h3:[h2:,h3]') batch.c:313: Test failed: unexpected char 0x2d position 0 in line 395 (got '---', wanted 'i4:[i3:[i2:[i1,i2],i3],i4]@or_broken(a)i4:[i3:[i2:,i3],i4]@or_broken(a)i4:[i3:,i4]') batch.c:313: Test failed: unexpected char 0x27 position 0 in line 540 (got ''--a--c---'', wanted ''--a------'@or_broken@'--a--------'@or_broken@'%~ai'') === w2008s64 (32 bit) === batch.c:313: Test failed: unexpected char 0x2d position 0 in line 391 (got '---', wanted 'g2:[g1,g2]') batch.c:313: Test failed: unexpected char 0x2d position 0 in line 393 (got '---', wanted 'h3:[h2:[h1,h2],h3]@or_broken(a)h3:[h2:,h3]') batch.c:313: Test failed: unexpected char 0x2d position 0 in line 395 (got '---', wanted 'i4:[i3:[i2:[i1,i2],i3],i4]@or_broken(a)i4:[i3:[i2:,i3],i4]@or_broken(a)i4:[i3:,i4]') === w7u (32 bit) === batch.c:313: Test failed: unexpected char 0x2d position 0 in line 391 (got '---', wanted 'g2:[g1,g2]') batch.c:313: Test failed: unexpected char 0x2d position 0 in line 393 (got '---', wanted 'h3:[h2:[h1,h2],h3]@or_broken(a)h3:[h2:,h3]') batch.c:313: Test failed: unexpected char 0x2d position 0 in line 395 (got '---', wanted 'i4:[i3:[i2:[i1,i2],i3],i4]@or_broken(a)i4:[i3:[i2:,i3],i4]@or_broken(a)i4:[i3:,i4]') === w7pro64 (32 bit) === batch.c:313: Test failed: unexpected char 0x2d position 0 in line 391 (got '---', wanted 'g2:[g1,g2]') batch.c:313: Test failed: unexpected char 0x2d position 0 in line 393 (got '---', wanted 'h3:[h2:[h1,h2],h3]@or_broken(a)h3:[h2:,h3]') batch.c:313: Test failed: unexpected char 0x2d position 0 in line 395 (got '---', wanted 'i4:[i3:[i2:[i1,i2],i3],i4]@or_broken(a)i4:[i3:[i2:,i3],i4]@or_broken(a)i4:[i3:,i4]') === w8 (32 bit) === batch.c:313: Test failed: unexpected char 0x2d position 0 in line 391 (got '---', wanted 'g2:[g1,g2]') batch.c:313: Test failed: unexpected char 0x2d position 0 in line 393 (got '---', wanted 'h3:[h2:[h1,h2],h3]@or_broken(a)h3:[h2:,h3]') batch.c:313: Test failed: unexpected char 0x2d position 0 in line 395 (got '---', wanted 'i4:[i3:[i2:[i1,i2],i3],i4]@or_broken(a)i4:[i3:[i2:,i3],i4]@or_broken(a)i4:[i3:,i4]') === w864 (32 bit) === batch.c:313: Test failed: unexpected char 0x2d position 0 in line 391 (got '---', wanted 'g2:[g1,g2]') batch.c:313: Test failed: unexpected char 0x2d position 0 in line 393 (got '---', wanted 'h3:[h2:[h1,h2],h3]@or_broken(a)h3:[h2:,h3]') batch.c:313: Test failed: unexpected char 0x2d position 0 in line 395 (got '---', wanted 'i4:[i3:[i2:[i1,i2],i3],i4]@or_broken(a)i4:[i3:[i2:,i3],i4]@or_broken(a)i4:[i3:,i4]') === w1064 (32 bit) === batch.c:313: Test failed: unexpected char 0x2d position 0 in line 391 (got '---', wanted 'g2:[g1,g2]') batch.c:313: Test failed: unexpected char 0x2d position 0 in line 393 (got '---', wanted 'h3:[h2:[h1,h2],h3]@or_broken(a)h3:[h2:,h3]') batch.c:313: Test failed: unexpected char 0x2d position 0 in line 395 (got '---', wanted 'i4:[i3:[i2:[i1,i2],i3],i4]@or_broken(a)i4:[i3:[i2:,i3],i4]@or_broken(a)i4:[i3:,i4]') === wvistau64 (64 bit) === batch.c:313: Test failed: unexpected char 0x2d position 0 in line 391 (got '---', wanted 'g2:[g1,g2]') batch.c:313: Test failed: unexpected char 0x2d position 0 in line 393 (got '---', wanted 'h3:[h2:[h1,h2],h3]@or_broken(a)h3:[h2:,h3]') batch.c:313: Test failed: unexpected char 0x2d position 0 in line 395 (got '---', wanted 'i4:[i3:[i2:[i1,i2],i3],i4]@or_broken(a)i4:[i3:[i2:,i3],i4]@or_broken(a)i4:[i3:,i4]') batch.c:313: Test failed: unexpected char 0x27 position 0 in line 540 (got ''--a--c---'', wanted ''--a------'@or_broken@'--a--------'@or_broken@'%~ai'') === w2008s64 (64 bit) === batch.c:313: Test failed: unexpected char 0x2d position 0 in line 391 (got '---', wanted 'g2:[g1,g2]') batch.c:313: Test failed: unexpected char 0x2d position 0 in line 393 (got '---', wanted 'h3:[h2:[h1,h2],h3]@or_broken(a)h3:[h2:,h3]') batch.c:313: Test failed: unexpected char 0x2d position 0 in line 395 (got '---', wanted 'i4:[i3:[i2:[i1,i2],i3],i4]@or_broken(a)i4:[i3:[i2:,i3],i4]@or_broken(a)i4:[i3:,i4]') === w7pro64 (64 bit) === batch.c:313: Test failed: unexpected char 0x2d position 0 in line 391 (got '---', wanted 'g2:[g1,g2]') batch.c:313: Test failed: unexpected char 0x2d position 0 in line 393 (got '---', wanted 'h3:[h2:[h1,h2],h3]@or_broken(a)h3:[h2:,h3]') batch.c:313: Test failed: unexpected char 0x2d position 0 in line 395 (got '---', wanted 'i4:[i3:[i2:[i1,i2],i3],i4]@or_broken(a)i4:[i3:[i2:,i3],i4]@or_broken(a)i4:[i3:,i4]') === w864 (64 bit) === batch.c:313: Test failed: unexpected char 0x2d position 0 in line 391 (got '---', wanted 'g2:[g1,g2]') batch.c:313: Test failed: unexpected char 0x2d position 0 in line 393 (got '---', wanted 'h3:[h2:[h1,h2],h3]@or_broken(a)h3:[h2:,h3]') batch.c:313: Test failed: unexpected char 0x2d position 0 in line 395 (got '---', wanted 'i4:[i3:[i2:[i1,i2],i3],i4]@or_broken(a)i4:[i3:[i2:,i3],i4]@or_broken(a)i4:[i3:,i4]') === w1064 (64 bit) === batch.c:313: Test failed: unexpected char 0x2d position 0 in line 391 (got '---', wanted 'g2:[g1,g2]') batch.c:313: Test failed: unexpected char 0x2d position 0 in line 393 (got '---', wanted 'h3:[h2:[h1,h2],h3]@or_broken(a)h3:[h2:,h3]') batch.c:313: Test failed: unexpected char 0x2d position 0 in line 395 (got '---', wanted 'i4:[i3:[i2:[i1,i2],i3],i4]@or_broken(a)i4:[i3:[i2:,i3],i4]@or_broken(a)i4:[i3:,i4]')

Nov. 28, 2016

Serial port sniffing problem

by Bill Lionheart

Using Wine version 1.8 on Ubuntu 14.04.5 I'm trying to use a AVRT5 APRS amateur radio GPRS tracker which has a serial interface. The device is supplied with a Prolific USB serial converter which comes up as /dev/ttyUSB0 which I have sym linked to COM1 The bundled GPRS tracker config software installs and runs OK under Wine. But my attempts to sniff the serial port traffic fails using all the standard Linux methods I know. I also tried using the Windows program Serial Port Monitor under Wine http://www.eltima.com/products/serial-port-monitor/ . This program says it cannot detect any serial ports. Under Windows 7 the config program and Serial Port Monitor both work well and I can intercept all the serial traffic Any ideas please folks? Bill

Nov. 27, 2016

Re: [PATCH] cmd: Fix copying when the dest is one of the sources.

by Lauri Kenttä

Testbot reports a failure on Vista, but that is not related to my patch. -- Lauri Kenttä

Nov. 26, 2016

Re: [PATCH] cmd: Fix copying when the dest is one of the sources.

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://testbot.winehq.org/JobDetails.pl?Key=26929 Your paranoid android. === wvistau64 (32 bit) === batch.c:313: Test failed: unexpected char 0x27 position 0 in line 456 (got ''--a--c---'', wanted ''--a------'@or_broken@'--a--------'@or_broken@'%~ai'') === wvistau64 (64 bit) === batch.c:313: Test failed: unexpected char 0x27 position 0 in line 456 (got ''--a--c---'', wanted ''--a------'@or_broken@'--a--------'@or_broken@'%~ai'')

Nov. 26, 2016

Re: WineTest reference Linux machines

by Stefan Dösinger

Am 2016-11-25 um 23:41 schrieb Matteo Bruni: > The d3d9:device failure seems to have disappeared in the latest two > builds. Let's see if that sticks. The d3d9:device failure in 703080afb4c9 seems to be different from the window minimization problems: device.c:1781: Test failed: The cursor handle is 0x10022 That failure poped up in 2 of the 3 test runs of that build, and was a come-and-go in the previous tests, so I guess it is random and still needs to be fixed.

Nov. 26, 2016

Re: Testing Direct3D

by Matteo Bruni

2016-11-25 22:36 GMT+01:00 Stefan Dösinger <stefandoesinger(a)gmail.com>: > Am 2016-11-24 um 19:47 schrieb Fabian Maurer: >> AFAIK the wine TestBot is only running VMs, too. Is there any way to run a >> meaningful test without having my own windows machine? > Not really. You really want to have a real Windows machine if you want > to do d3d development. The testbot VMs do help with some things (e.g. > the d3d reference counting is implemented in Microsoft's part of the d3d > stack), but our tests are full with broken() statements that accept > behavior from VMs that are known to break games. > > If you need some one off test runs you can send me a patch and I can run > them on my Windows boxes for you. Other options, once you have a test patch you could ask on #winehackers or here on wine-devel for someone to give it a try. Still suboptimal, yeah... I think there is a plan to add support for real boxes to the Testbot, although that's probably not happening in the short term.

Nov. 25, 2016

Re: WineTest reference Linux machines

by Matteo Bruni

2016-11-24 19:00 GMT+01:00 Francois Gouget <fgouget(a)codeweavers.com>: > So we still have a failure for d3d9:device and d3d9:visual. Are those > still related to the window manager? The d3d9:device failure seems to have disappeared in the latest two builds. Let's see if that sticks. The visual test failure is not WM-related. It has to do with NaN handling in GLSL shaders and it's probably a driver bug (for reference, I can reproduce it here and it disappears when running the test with R600_DEBUG=nosb). I never got around to trying to figure out the issue, maybe I'll manage to this time...

Nov. 25, 2016