Sorry for the mail storm, I've disabled mail again.
(I out running errands all afternoon/evening, or I probably would have
done that sooner.)
As it happens, there is already a nearly unused mailing list for
wine test results; I'll send results there from now on,
at least until we work out more of t
The Buildbot has detected a failed build on builder runtests while building
Wine.
Full details are available at:
http://buildbot.kegel.com/builders/runtests/builds/235
BUILD FAILED: failed shell_3
For more info about this message, see http://wiki.winehq.org/BuildBot
The Buildbot has detected a failed build on builder runtests while building
Wine.
Full details are available at:
http://buildbot.kegel.com/builders/runtests/builds/231
BUILD FAILED: failed shell_3
For more info about this message, see http://wiki.winehq.org/BuildBot
The Buildbot has detected a failed build on builder runtests while building
Wine.
Full details are available at:
http://buildbot.kegel.com/builders/runtests/builds/230
BUILD FAILED: failed shell_3
For more info about this message, see http://wiki.winehq.org/BuildBot
The Buildbot has detected a failed build on builder runtests while building
Wine.
Full details are available at:
http://buildbot.kegel.com/builders/runtests/builds/229
BUILD FAILED: failed git
For more info about this message, see http://wiki.winehq.org/BuildBot
The Buildbot has detected a failed build on builder runtests while building
Wine.
Full details are available at:
http://buildbot.kegel.com/builders/runtests/builds/228
BUILD FAILED: failed shell_3
For more info about this message, see http://wiki.winehq.org/BuildBot
The Buildbot has detected a failed build on builder runtests while building
Wine.
Full details are available at:
http://buildbot.kegel.com/builders/runtests/builds/227
BUILD FAILED: failed git
For more info about this message, see http://wiki.winehq.org/BuildBot
I think buildbot might need a bit of tweaking, it's not normal for so
many patches to fail.
On Fri, Sep 2, 2011 at 1:06 AM, Peter Urbanec wrote:
> wine-devel has been seeing more and more robot generated messages. Would it
> make sense to create wine-bots list for buildbot, testbot and friends?
>
The Buildbot has detected a failed build on builder runtests while building
Wine.
Full details are available at:
http://buildbot.kegel.com/builders/runtests/builds/223
BUILD FAILED: failed git
For more info about this message, see http://wiki.winehq.org/BuildBot
The Buildbot has detected a failed build on builder runtests while building
Wine.
Full details are available at:
http://buildbot.kegel.com/builders/runtests/builds/219
BUILD FAILED: failed shell_3
For more info about this message, see http://wiki.winehq.org/BuildBot
The Buildbot has detected a failed build on builder runtests while building
Wine.
Full details are available at:
http://buildbot.kegel.com/builders/runtests/builds/216
BUILD FAILED: failed git
For more info about this message, see http://wiki.winehq.org/BuildBot
The Buildbot has detected a failed build on builder runtests while building
Wine.
Full details are available at:
http://buildbot.kegel.com/builders/runtests/builds/218
BUILD FAILED: failed shell_3
For more info about this message, see http://wiki.winehq.org/BuildBot
The Buildbot has detected a failed build on builder runtests while building
Wine.
Full details are available at:
http://buildbot.kegel.com/builders/runtests/builds/215
BUILD FAILED: failed git
For more info about this message, see http://wiki.winehq.org/BuildBot
wine-devel has been seeing more and more robot generated messages. Would
it make sense to create wine-bots list for buildbot, testbot and
friends? Automated messages could go to author, wine-bots with Reply-To:
and Followup-To: pointing at wine-devel
That way wine-devel could be returned to hu
The Buildbot has detected a failed build on builder runtests while building
Wine.
Full details are available at:
http://buildbot.kegel.com/builders/runtests/builds/217
BUILD FAILED: failed git
For more info about this message, see http://wiki.winehq.org/BuildBot
The Buildbot has detected a failed build on builder runtests while building
Wine.
Full details are available at:
http://buildbot.kegel.com/builders/runtests/builds/214
BUILD FAILED: failed shell_3
For more info about this message, see http://wiki.winehq.org/BuildBot
On Thu, Sep 1, 2011 at 18:40, Bruno Jesus <00cp...@gmail.com> wrote:
>
> I don't get the same results here, can anyone help me to understand
> why it failed?
> 10014 = WSAEFAULT and I could not find this return value anywhere
> near, maybe due to threading?
>
> Thanks,
> Bruno
>
I see know that ne
The Buildbot has detected a failed build on builder runtests while building
Wine.
Full details are available at:
http://buildbot.kegel.com/builders/runtests/builds/213
BUILD FAILED: failed shell_3
For more info about this message, see http://wiki.winehq.org/BuildBot
On Thu, Sep 1, 2011 at 9:34 PM, Lucas Fialho Zawacki
wrote:
> +STRINGTABLE
> +BEGIN
> + IDS_ACTIONCOLUMN "Action"
> + IDS_OBJECTCOLUMN "Object"
> +END
I think you should only keep the string table in dinput.rc. The
dialog(s) should go in En.rc so they can be localized, like it's
The Buildbot has detected a failed build on builder runtests while building
Wine.
Full details are available at:
http://buildbot.kegel.com/builders/runtests/builds/212
BUILD FAILED: failed shell_3
For more info about this message, see http://wiki.winehq.org/BuildBot
On Wed, Aug 31, 2011 at 3:25 PM, Octavian Voicu wrote:
> They are not used anymore. Last change was with the release of wine 1.0.
> Sent as attachment because of the huge lines.
Alexandre,
This patch was sent before I got your reply on wine-devel, so you can ignore it.
Probably was in the moderat
The Buildbot has detected a failed build on builder runtests while building
Wine.
Full details are available at:
http://buildbot.kegel.com/builders/runtests/builds/211
BUILD FAILED: failed shell_3
For more info about this message, see http://wiki.winehq.org/BuildBot
The Buildbot has detected a failed build on builder runtests while building
Wine.
Full details are available at:
http://buildbot.kegel.com/builders/runtests/builds/209
BUILD FAILED: failed shell_3
For more info about this message, see http://wiki.winehq.org/BuildBot
On Thu, Sep 1, 2011 at 16:27, Marvin wrote:
> 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
> http://testbot
The Buildbot has detected a failed build on builder runtests while building
Wine.
Full details are available at:
http://buildbot.kegel.com/builders/runtests/builds/208
BUILD FAILED: failed shell_3
For more info about this message, see http://wiki.winehq.org/BuildBot
The Buildbot has detected a failed build on builder runtests while building
Wine.
Full details are available at:
http://buildbot.kegel.com/builders/runtests/builds/207
BUILD FAILED: failed shell_3
For more info about this message, see http://wiki.winehq.org/BuildBot
The Buildbot has detected a failed build on builder runtests while building
Wine.
Full details are available at:
http://buildbot.kegel.com/builders/runtests/builds/206
BUILD FAILED: failed shell_3
For more info about this message, see http://wiki.winehq.org/BuildBot
The Buildbot has detected a failed build on builder runtests while building
Wine.
Full details are available at:
http://buildbot.kegel.com/builders/runtests/builds/205
BUILD FAILED: failed shell_3
For more info about this message, see http://wiki.winehq.org/BuildBot
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
http://testbot.winehq.org/JobDetails.pl?Key=13895
Your paranoid android
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
http://testbot.winehq.org/JobDetails.pl?Key=13898
Your paranoid android
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
http://testbot.winehq.org/JobDetails.pl?Key=13897
Your paranoid android
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
http://testbot.winehq.org/JobDetails.pl?Key=13899
Your paranoid android
On 1 September 2011 21:02, Henri Verbeet wrote:
> I have some doubts about this being caused by this patch.
>
That said, you may want to give 78289 a try.
The Buildbot has detected a failed build on builder runtests while building
Wine.
Full details are available at:
http://buildbot.kegel.com/builders/runtests/builds/204
BUILD FAILED: failed shell_3
For more info about this message, see http://wiki.winehq.org/BuildBot
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
http://testbot.winehq.org/JobDetails.pl?Key=13896
Your paranoid android
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
http://testbot.winehq.org/JobDetails.pl?Key=13894
Your paranoid android
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
http://testbot.winehq.org/JobDetails.pl?Key=13889
Your paranoid android
The Buildbot has detected a failed build on builder runtests while building
Wine.
Full details are available at:
http://buildbot.kegel.com/builders/runtests/builds/203
BUILD FAILED: failed shell_3
For more info about this message, see http://wiki.winehq.org/BuildBot
On 1 September 2011 20:51, wrote:
> Backtrace:
> =>0 0x7bc4772c HEAP_CreateFreeBlock+0xbb(subheap=0x110014, ptr=0x130910,
> size=0xdffe8)
> [/home/dank/wineslave.dir/sandbox/slave/runtests/build/dlls/ntdll/heap.c:583]
> in ntdll (0x0032f444)
> 1 0x7bc47a57 HEAP_ShrinkBlock+0x42(subheap=0x110
1 sep 2011 kl. 03:27 skrev Dan Kegel:
> At which point it would probably be a fine idea to add -Werror by default;
> buildbot will help keep everyone in sync, even if they're using a compiler
> that doesn't catch as many warnings as the one buildbot uses.
We use -Werror at my company, but I thin
On Wed, Aug 31, 2011 at 12:20 PM, Alexandre Julliard
wrote:
> Bernhard Loos writes:
>
>> @@ -164,8 +165,16 @@ static int NTDLL_dbg_vlog( enum __wine_debug_class cls,
>> struct __wine_debug_chan
>> /* only print header if we are at the beginning of the line */
>> if (info->out_pos == in
> IMHO we should probably split it only when it's reasonably complete,
> where we'd have a broader view.
Well, it's up to you. I just made an attempt to merge my stuff into
test_builtins and gave up after 2 hours :-(
> Also, test_parsing name is probably a bit too generic (not that
> test_builti
Hi Frédéric,
> Some of those tests are already present in the test_builtins.cmd*
> (e.g. the spacing tests)
> You should probably integrated your tests in there: that makes it
> easier to spot regressions and helps prevent tests duplication
I can certainly do that if you prefer (and I will), but
Hi Ben:
Thanks for your further tests.
On 2011-08-30 08:20+1000 Ben Peddell wrote (but then later forwarded
to list so I am repeating my off-list reply to the list as well):
Some things I have seen while investigating:
I created a program which had a startup that immediately called
ExitProces
The Buildbot has detected a failed build on builder runtests while building
Wine.
Full details are available at:
http://buildbot.kegel.com/builders/runtests/builds/201
BUILD FAILED: failed shell_3
For more info about this message, see http://wiki.winehq.org/BuildBot
On Thu, Sep 1, 2011 at 8:52 AM, Dan Kegel wrote:
> On Thu, Sep 1, 2011 at 1:35 AM, Jerome Leclanche wrote:
>> Here is a warning report from a 64bit system. I get a lot of warnings
>> on both 32 and 64bit wines. Many of them are "variable set but not
>> used" (unused error returns, ...).
>>
>> htt
On 1 September 2011 19:00, Stefan Dösinger wrote:
> I had a quick look at the D3DCREATE_FPU_PRESERVE code: shouldn't we do
> something like ddraw where we set the FPU control word in every method and
> restore it afterwards? I think we can't blame the driver for crashing if we
> hand it over the F
On Thu, Sep 1, 2011 at 7:21 PM, Dan Kegel wrote:
> I just checked, and none of our .c, .h, or .po files have embedded
> CR's. I guess it would be ok to strip trailing CR's on incoming
> patches, I'll do that.
That's weird, did they blacklist the 0x0d character from the encoding
of Unicode charac
On Thursday 01 September 2011 18:46:58 Stefan Dösinger wrote:
> Fwiw, the d3d8 and d3d9 device tests fail, no idea why, the d3d9 query test
> fails(this is something we can fix). The ddraw, d3d8 and d3d9 visual tests
> can't read back the backbuffer, so they refuse to run.
This crash happens in the
Am 01.09.2011 17:52, schrieb Dan Kegel:
> On Thu, Sep 1, 2011 at 1:35 AM, Jerome Leclanche wrote:
>> Here is a warning report from a 64bit system. I get a lot of warnings
>> on both 32 and 64bit wines. Many of them are "variable set but not
>> used" (unused error returns, ...).
>>
>> http://bugs.w
Fwiw, the d3d8 and d3d9 device tests fail, no idea why, the d3d9 query test
fails(this is something we can fix). The ddraw, d3d8 and d3d9 visual tests
can't read back the backbuffer, so they refuse to run.
On Thursday 01 September 2011 18:18:11 Henri Verbeet wrote:
> On 1 September 2011 17:38, S
On Thu, Sep 1, 2011 at 7:52 AM, Octavian Voicu wrote:
> 2011/9/1 Dan Kegel :
>> This patch found a bug in my scripts - it failed to grep the patch
>> for sender and subject - but it looks like there might be something
>> wrong with the patch itself, it doesn't apply here.
>
> The patch uses dos li
On 1 September 2011 17:38, Stefan Dösinger wrote:
> On Thursday 01 September 2011 13:04:34 Henri Verbeet wrote:
>> Did the tests start passing on fglrx then?
> As far as I know they don't. But do they have to?
>
If running those tests is the point of that machine, I'd say so. With
a known broken c
On Thu, Sep 1, 2011 at 8:38 AM, Stefan Dösinger wrote:
> On Thursday 01 September 2011 13:04:34 Henri Verbeet wrote:
>> Did the tests start passing on fglrx then?
> As far as I know they don't. But do they have to?
>
> If I remember correctly Dan's previous patchwatcher scripts kept track of
> tes
On Thu, Sep 1, 2011 at 1:35 AM, Jerome Leclanche wrote:
> Here is a warning report from a 64bit system. I get a lot of warnings
> on both 32 and 64bit wines. Many of them are "variable set but not
> used" (unused error returns, ...).
>
> http://bugs.winehq.org/show_bug.cgi?id=26768 was filed a whi
On Thursday 01 September 2011 13:04:34 Henri Verbeet wrote:
> Did the tests start passing on fglrx then?
As far as I know they don't. But do they have to?
If I remember correctly Dan's previous patchwatcher scripts kept track of
tests that were failing, so they didn't require a fully successful t
On Thursday 01 September 2011 13:27:28 Henri Verbeet wrote:
> On 1 September 2011 11:01, Stefan Dösinger wrote:
> > case 32:
> > if(DDPixelFormat->u2.dwStencilBitDepth == 8)
> >
> > return WINED3DFMT_D24_UNORM_S8_
Frédéric Delanoy writes:
> + else if ((s = StrStrIW (p, lssW))) {
> +s += 3;
> +a = StrToIntW(condition);
> +b = StrToIntW(WCMD_parameter (s, 0, NULL));
I don't think you want to use strstr for that sort of thing.
--
Alexandre Julliard
julli...@winehq.org
2011/9/1 Dan Kegel :
> This patch found a bug in my scripts - it failed to grep the patch
> for sender and subject - but it looks like there might be something
> wrong with the patch itself, it doesn't apply here.
The patch uses dos line endings, that's why it doesn't apply.
Octavian
If anyone wants to have a shot at a proper fix, by all means -- I
don't have the C skills to figure this one out properly ;)
On Thu, Sep 1, 2011 at 3:24 PM, Alexandre Julliard wrote:
> Jerome Leclanche writes:
>
>> From c8a7535beebb152641330d3d1410d17345522867 Mon Sep 17 00:00:00 2001
>> From: J
Jerome Leclanche writes:
> From c8a7535beebb152641330d3d1410d17345522867 Mon Sep 17 00:00:00 2001
> From: Jerome Leclanche
> Date: Thu, 1 Sep 2011 12:51:26 +0100
> Subject: [PATCH] setupapi: Fix a few pointer cast warnings.
That's just hiding the pointer truncation bug.
--
Alexandre Julliard
On Wed, 24 Aug 2011, Eric Pouech wrote:
[...]
> you can safely provide the patches with protecting WriteConsole and friends
> with a if (!is_console_handle(???)) return FALSE; line
Would something like the attached patch be ok?
As far as I can see all the other APIs pretty much immediately pass th
On Thu, Sep 1, 2011 at 4:04 AM, Henri Verbeet wrote:
> Note that virtual desktop breaks some (iirc user32) tests, unless
> that's something that was fixed recently.
I work around it. There were only a couple.
- Dan
This patch found a bug in my scripts - it failed to grep the patch
for sender and subject - but it looks like there might be something
wrong with the patch itself, it doesn't apply here.
Buildbot said:
Full details are available at:
http://buildbot.kegel.com/builders/runtests/builds/194
BUILD FAIL
On Wed, Aug 31, 2011 at 01:25:41PM -0700, Dan Kegel wrote:
> Ah, I see you resent a fixed version, sorry for the noise.
Thanks just the same. Because of your bot's email, I was able to
know to resend the patch before I ran out the door.
Andrew
> (FWIW, the bot won't test your retry, since it was
On Thu, Sep 1, 2011 at 4:02 PM, Francois Gouget wrote:
> @@ -295,7 +295,8 @@ static void scmdatabase_autostart_services(struct
> scmdatabase *db)
> argv[0] = service->name;
> argv[1] = NULL;
> err = service_start(service, 1, argv);
> - /* FIXME: do something if the
The Buildbot has detected a failed build on builder runtests while building
Wine.
Full details are available at:
http://buildbot.kegel.com/builders/runtests/builds/194
BUILD FAILED: failed git
For more info about this message, see http://wiki.winehq.org/BuildBot
On 09/01/2011 05:05 AM, Alex Bradbury wrote:
> On 1 September 2011 10:50, Scott Ritchie wrote:
>> For an easier user testing experience, you can now install the latest
>> git as a convenient Ubuntu package.
>
> This seems very handy, thank you.
>
> As this seems like as good a place as any for U
On 09/01/2011 05:21 AM, Henri Verbeet wrote:
> On 1 September 2011 11:50, Scott Ritchie wrote:
>> The packages are versioned like wine1.3-1.3.27+daily-20110901.
>>
>> Limitations:
>> The major version number is based on the latest released version of the
>> Ubuntu
On Thu, Sep 1, 2011 at 3:05 PM, Alex Bradbury wrote:
> As this seems like as good a place as any for Ubuntu packaging of wine
> - do you see any fix in the future for gstreamer support on Wine when
> compiling on 64-bit Ubuntu? The current Wine configure script (quite
> correctly) disables support
On 1 September 2011 11:50, Scott Ritchie wrote:
> The packages are versioned like wine1.3-1.3.27+daily-20110901.
>
> Limitations:
> The major version number is based on the latest released version of the
> Ubuntu packages, so on release days you might see something like
> 1.3
On 1 September 2011 10:50, Scott Ritchie wrote:
> For an easier user testing experience, you can now install the latest
> git as a convenient Ubuntu package.
This seems very handy, thank you.
As this seems like as good a place as any for Ubuntu packaging of wine
- do you see any fix in the futur
On 1 September 2011 11:01, Stefan Dösinger wrote:
> case 32:
> if(DDPixelFormat->u2.dwStencilBitDepth == 8)
> return WINED3DFMT_D24_UNORM_S8_UINT;
> -else
> +else if (DDPixelFormat->u2.dwStencilB
On 1 September 2011 09:19, Stefan Dösinger wrote:
> The iMac would be an idea, but there's still a rather nasty issue with the
> lack of xrandr and xvidmode support on Apple's X server, and a wine hack that
> is needed with CrossOver's X server. If I read your scripts correctly you run
> the te
On 1 September 2011 09:27, Stefan Dösinger wrote:
> Am 31.08.2011 um 12:29 schrieb Henri Verbeet:
>> Well, DirectDraw 2D-only applications, but yes. All three people in
>> that situation should either install a software GL renderer or
>> explicitly set the "DirectDrawRenderer" registry key to "gdi
(resent with correct from-address, please ignore the previous one)
1 sep 2011 kl. 03:27 skrev Dan Kegel:
> At which point it would probably be a fine idea to add -Werror by default;
> buildbot will help keep everyone in sync, even if they're using a compiler
> that doesn't catch as many warnings
Dan Kegel wrote:
> (Reviving
> http://www.winehq.org/pipermail/wine-devel/2008-September/069266.html
> )
>
> After
> http://www.winehq.org/pipermail/wine-patches/2011-August/106150.html and
> http://www.winehq.org/pipermail/wine-patches/2011-August/106151.html,
> configuring with -Wall -Werror gi
nal:
sudo add-apt-repository ppa:ubuntu-wine/daily
sudo apt-get update
sudo apt-get install wine1.3
The packages are versioned like wine1.3-1.3.27+daily-20110901.
Limitations:
The major version number is based on the latest released version of the
Ubuntu packages, so on release days you might
Hi,
I've one idea left about what may have caused the 2 apply failures.
The patches are in my git queue just above wine-1.3.27 and the
unrelated Valgrind hacks, so in theory, they should work.
However the patches depend on each other, but since I reused the
subject line of patches originally subm
On Tue, Aug 30, 2011 at 09:11:33PM -0300, Lucas Zawacki wrote:
> > It doesn't make sense to pass the info as WM_INITDIALG parameter if it's
> > going to be stored in global variables anyway. A better way would be to
> > store this in the window info.
> >
>
> Any pointers on what's the set of winap
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 31.08.2011 um 12:29 schrieb Henri Verbeet:
> On 31 August 2011 10:58, Stefan Dösinger wrote:
>> This will break 2D-only apps in situations where OpenGL is not available. It
> Well, DirectDraw 2D-only applications, but yes. All three people in
> t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 01.09.2011 um 01:12 schrieb Dan Kegel:
> it'd probably be a better use of time to bring up a modern ati system?
If I had one I could use as-is, yes. My computer with a modern AMD GPU is in my
working and sleeping room, where I'd like to keep it fo
82 matches
Mail list logo
