Le 06/10/2012 06:13, Christian Costa a écrit :
Hi,
Is there a problem with Wine test bost? Jobs seem to be stuck and some
VMs show problem of memory.
Christian
Wine test bost is still stuck. Any plan to fix that problem?
Hi,
Is there a problem with Wine test bost? Jobs seem to be stuck and some
VMs show problem of memory.
Christian
On Sat, Mar 31, 2012 at 12:42, Christian Costa wrote:
> Hi,
>
> I wrote a win16 exe test file using open watcom but I cannot submit it to
> winebot. I fails saying "Unricognized file type". This is a little annoying.
> Is this a known limitation of wine test bot ?
>
Hi,
I wrote a win16 exe test file using open watcom but I cannot submit it
to winebot. I fails saying "Unricognized file type". This is a little
annoying.
Is this a known limitation of wine test bot ?
Thanks
Christian
W dniu 26.09.2010 20:27, Greg Geldorp pisze:
This is now fixed. The problem occurred when your patch contained a change
to tests/Makefile.in. The config.status invocation to create an updated
Makefile recently changed, TestBot now calls config.status with the
correct arguments again.
Greg.
Hi
T
> From: Mariusz Pluciński
>
> I also had this problem yesterday both with patches submitted manually
> and my patches transferred from wine-patches. I can confirm that
> sending executables instead worked for me, but this is possible only
> when submitting own test, and not when it is loaded from w
Travis Athougies wrote:
>
>Hi,
>
>I was trying to run my HLSL test suite patch through wine test bot and
>the build failed. However, it's not a compilation failure. Instead it
>complains about not being able to copy some executable file. Also, the
>build fails almos
On Fri, 24 Sep 2010 00:30:14 -0700, Travis Athougies
wrote:
> The results are at
> https://testbot.winehq.org/JobDetails.pl?Key=5449&log_101=1#k101
I got a similar error on my own machine just a while ago. Apparently AJ
has recently changed some variable names in the makefiles but some of
the old
> From: Mariusz Pluciński
>
> I also had this problem yesterday both with patches submitted manually
> and my patches transferred from wine-patches. I can confirm that sending
> executables instead worked for me, but this is possible only when
> submitting own test, and not when it is loaded from w
W dniu 24.09.2010 09:30, Travis Athougies pisze:
Hi,
I was trying to run my HLSL test suite patch through wine test bot and
the build failed. However, it's not a compilation failure. Instead it
complains about not being able to copy some executable file. Also, the
build fails a
On Fri, Sep 24, 2010 at 3:25 AM, Travis Athougies wrote:
> Still, I would like for it to be able to be buillt..
While the build failure is concerning, it's somewhat moot given that
the tests don't run anyway:
http://testbot.winehq.org/JobDetails.pl?Key=5450
An XP machine with NVIDIA graphics an
Still, I would like for it to be able to be buillt..
On Fri, Sep 24, 2010 at 1:20 AM, Austin English wrote:
> On Fri, Sep 24, 2010 at 12:30 AM, Travis Athougies wrote:
>> Hi,
>>
>> I was trying to run my HLSL test suite patch through wine test bot and
>> the build
On Fri, Sep 24, 2010 at 12:30 AM, Travis Athougies wrote:
> Hi,
>
> I was trying to run my HLSL test suite patch through wine test bot and
> the build failed. However, it's not a compilation failure. Instead it
> complains about not being able to copy some executable file. Als
On Fri, Sep 24, 2010 at 2:30 AM, Travis Athougies wrote:
> Hi,
>
> I was trying to run my HLSL test suite patch through wine test bot and
> the build failed. However, it's not a compilation failure. Instead it
> complains about not being able to copy some executable file. Als
Hi,
I was trying to run my HLSL test suite patch through wine test bot and
the build failed. However, it's not a compilation failure. Instead it
complains about not being able to copy some executable file. Also, the
build fails almost instantaneously. It also complains about a missing
co
Hi Alexandre,
> Ok so I could not run any test until compiling on cygwin works.
> But the idea was to be able to remotly compile wine with some of our patches
> applied.
>
> I was told "you can't do that, it will break minGW".
> The WINEBUILD VM exists but we can't use it (or tell me how to do tha
I didn't know this tool.
It looks quite interesting.
Thanks again for your advices
Patchwatcher is suppose to sort of do this. It only works for linux, not
other systems, but it will not only check your patch against compiling but
also against the test suit and mark and regressions.
Alexandre Goujon wrote:
> > For any productive Wine development you need not only working compiling
> > environment, but a working Wine binary, to run at least 'make test'.
>
>
> Ok so I could not run any test until compiling on cygwin works.
Even if compiling under Cygwin works, the tests sti
Dmitry Timoshkov wrote
> For any productive Wine development you need not only working compiling
> environment, but a working Wine binary, to run at least 'make test'.
Ok so I could not run any test until compiling on cygwin works.
But the idea was to be able to remotly compile wine with some o
Alexandre Goujon wrote:
> Currently, I can't compile on Linux and cygwin is very slow.
> So it would make my life easier if I could rely on wineTestBot...
For any productive Wine development you need not only working compiling
environment, but a working Wine binary, to run at least 'make test'.
Hi,
I have a suggestion about wineTestBot.
It's maybe the wrong place but I'm quite sure interested people read
wine-devel.
I think it would be great if we could
not only run tests (as it already does)
but also check if a patch does not break wine (on minGW, on cygwin or on MAC
for instance).
Th
22 matches
Mail list logo
