On Mon, 3 Jun 2013, André Hentschel wrote:
[...]
> Ah, ok. Didn't know. So the question is if François will continue to
> run winetest on his NT4 machines (outside of testbot), if so, we
> should not yet remove NT4 "hacks" in the testsuite.
I will continue running them
On 06/03/2013 10:36 PM, André Hentschel wrote:
> On 03.06.2013 22:22, Alexandre Julliard wrote:
>> André Hentschel writes:
>>
>>> I haven't heard about NT4 been taking out of the requirement. I guess
>>> the NT4 machines are offline du
On 03.06.2013 22:22, Alexandre Julliard wrote:
> André Hentschel writes:
>
>> I haven't heard about NT4 been taking out of the requirement. I guess
>> the NT4 machines are offline due to the transition to the new testbot
>> (newtestbot.winehq.org). Hopefully the
André Hentschel writes:
> I haven't heard about NT4 been taking out of the requirement. I guess
> the NT4 machines are offline due to the transition to the new testbot
> (newtestbot.winehq.org). Hopefully the machines are working again on
> one of the testbots soon, let'
eping the
>> tests passing on nt4, so I noted with relief/surprise that the testbot
>> doesnt have an NT4 VM anymore.
>>
>> Is it correct that there is no longer a requirement for tests to pass on NT4
>> for submission (if it's required, I really need a nt4
On 02.06.2013 23:58, Ann and Jason Edmeades wrote:
> Hiya,
>
> Its been a while since I did some cmd work and noticed there were some new
> bugs so am doing some fiddling. The real pain for me was always keeping the
> tests passing on nt4, so I noted with relief/surprise that the
Hiya,
Its been a while since I did some cmd work and noticed there were some new
bugs so am doing some fiddling. The real pain for me was always keeping the
tests passing on nt4, so I noted with relief/surprise that the testbot
doesnt have an NT4 VM anymore.
Is it correct that there is no longer
On Wed, 17 Apr 2013, Dmitry Timoshkov wrote:
[...]
> I still need to manually enable WXPX64 and WXPPROSP2 when I send a test
> to testbot.
I thought I had switched them to base already but maybe not. I did so
again yesterday and rechecked today and it looks like it's ok now.
-
ase set of VMs.
I still need to manually enable WXPX64 and WXPPROSP2 when I send a test
to testbot.
--
Dmitry.
On Sat, 13 Apr 2013, Dmitry Timoshkov wrote:
[...]
> As I've pointed out, 64-bit XP and Vista VMs do exist and work just fine,
> please include at least them in the default VM set.
I see. I have moved WXPX64 and WVISTAX64 to the base set of VMs.
> > I'd point you to the new WineTestBot but it do
Francois Gouget wrote:
> > recently the set of VMs suggested to run the tests on by default has
> > changed.
> > It no more includes NT4, XP and Vista (although it does include win2000),
> > 32-bit VMs for NT4, XP and Vista don't even exist in the list of available
> > VMs
> > (64-bit XP and Vi
On Fri, 12 Apr 2013, Dmitry Timoshkov wrote:
> Hi all,
>
> recently the set of VMs suggested to run the tests on by default has changed.
> It no more includes NT4, XP and Vista (although it does include win2000),
> 32-bit VMs for NT4, XP and Vista don't even exist in the list of available VMs
> (
Hi all,
recently the set of VMs suggested to run the tests on by default has changed.
It no more includes NT4, XP and Vista (although it does include win2000),
32-bit VMs for NT4, XP and Vista don't even exist in the list of available VMs
(64-bit XP and Vista do exist, but for some reason are not
est daily:
there's no point since I cannot even submit the results).
> Please, PLEASE give me a (new)testbot with some w9x machines such that I can
> investigate the winmm&mci behavior that the apps written in that era
> encountered.
>
> It really slows down development o
ecause the Wine community is not interested in these.
Huh? What?
Please, PLEASE give me a (new)testbot with some w9x machines such that I can
investigate the winmm&mci behavior that the apps written in that era
encountered.
It really slows down development on my side *not* to have an easily
Hello,
the testbot does not revert patches submitted through
testbot.winehq.org after testing. As a result it is almost impossible
to test another patch affecting the same area in code as a previous
one.
Could anyone please fix it? Or at least add git reset to cron...
Regards,
Daniel
On Tue, 11 Dec 2012, Alexandre Julliard wrote:
> Francois Gouget writes:
>
> > @@ -88,12 +88,11 @@ $JobArchiveDays = 0;
> > if (!$::BuildEnv)
> > {
> >$::BuildEnv = 0;
> > - eval 'require "$::RootDir/ConfigLocal.pl";';
> > + eval 'require "$::RootDir/lib/WineTestBot/ConfigLocal.pl"';
[..
Francois Gouget writes:
> @@ -88,12 +88,11 @@ $JobArchiveDays = 0;
> if (!$::BuildEnv)
> {
>$::BuildEnv = 0;
> - eval 'require "$::RootDir/ConfigLocal.pl";';
> + eval 'require "$::RootDir/lib/WineTestBot/ConfigLocal.pl"';
>if ($@)
>{
> -print STDERR "Please create a valid $::R
On 5 December 2012 05:35, Francois Gouget wrote:
> The --directory option is not meant to specify where the Git repository lives.
> ---
>
> I'm not sure how it worked before. Maybe this use of the --directory
> option worked by chance but git changed and broke it.
>
Alternatively you could set GIT
-- By by ... Detlef
Gesendet: Samstag, 01. Dezember 2012 um 18:16 Uhr
Von: "Erich E. Hoover"
An: "Detlef Riekenberg"
Cc: wine-devel
Betreff: Re: testbot failures in advapi32 (security)
On Sat, Dec 1, 201
On Sat, Dec 1, 2012 at 4:28 AM, Detlef Riekenberg wrote:
> Hi Erich.
>
> We somewhere missed us on #winehackers.
>
> Testbot works with your patch:
> http://testbot.winehq.org/JobDetails.pl?Key=23165
>
> For an account, testbot has a menu item named "Register&q
Hi Erich.We somewhere missed us on #winehackers.Testbot works with your patch:http://testbot.winehq.org/JobDetails.pl?Key=23165For an account, testbot has a menu item named "Register":https://testbot.winehq.org/Register.pl-- By by ... Detlef
that?
> > > I'm not against improving the testbot, it was just a suggestion.
> > >
> > It's a good one.I will file a bug in bugzilla for the test bot and try
> > your suggestion.
> > Do you know any simple tool that enables to do that?
>
>
Christian Costa wrote:
> >> Indeed that would be great to be able to download some files along with the
> >> test.
> >> Typically for me avi files and dlls (or .drv) would be great ! :D
> > Just do what other tests do: embed all the required data into the test:
> > be it a PE executable, TIFF/GIF
On Mon, 15 Oct 2012, Christian Costa wrote:
[...]
> >> Why not if I can make it run the test after the extraction.
> >> That said why not improving test bot download extra files? Is there a
> >> specific reason for that?
> > I'm not against improving
any external files, or abilities in
>>>>>> the tested environment to download them.
>>>>>>
>>>>> It seems a bit complicated for a test I will run only once and not
>>>>> intended
>>>>> to be part of the test suite.
>&g
r the extraction.
That said why not improving test bot download extra files? Is there a
specific reason for that?
I'm not against improving the testbot, it was just a suggestion.
It's a good one.I will file a bug in bugzilla for the test bot and try
your suggestion.
Do you know any simple to
download them.
>>>>
>>> It seems a bit complicated for a test I will run only once and not
>>> intended
>>> to be part of the test suite.
>>
>> You could use a self extracting exe.
>>
> Why not if I can make it run the test after the extraction.
> That said why not improving test bot download extra files? Is there a
> specific reason for that?
I'm not against improving the testbot, it was just a suggestion.
--
-Austin
Le 15/10/2012 21:16, Austin English a écrit :
On Mon, Oct 15, 2012 at 12:14 PM, Christian Costa wrote:
Le 15/10/2012 18:07, Dmitry Timoshkov a écrit :
Christian Costa wrote:
Indeed that would be great to be able to download some files along with
the
test.
Typically for me avi files and dll
On Mon, Oct 15, 2012 at 12:14 PM, Christian Costa wrote:
> Le 15/10/2012 18:07, Dmitry Timoshkov a écrit :
>
>> Christian Costa wrote:
>>
>>> Indeed that would be great to be able to download some files along with
>>> the
>>> test.
>>> Typically for me avi files and dlls (or .drv) would be great
Le 15/10/2012 18:07, Dmitry Timoshkov a écrit :
Christian Costa wrote:
Indeed that would be great to be able to download some files along with the
test.
Typically for me avi files and dlls (or .drv) would be great ! :D
Just do what other tests do: embed all the required data into the test:
be
Christian Costa wrote:
> Indeed that would be great to be able to download some files along with the
> test.
> Typically for me avi files and dlls (or .drv) would be great ! :D
Just do what other tests do: embed all the required data into the test:
be it a PE executable, TIFF/GIF/PNG/etc image,
Hi François,
While your are at it. I would like to do a suggestion.
Indeed that would be great to be able to download some files along with the
test.
Typically for me avi files and dlls (or .drv) would be great ! :D
Thanks
Christian,
2012/10/15 Francois Gouget
> ---
> testbot/lib/WineT
This is caused by previously committed patches while testbot was
resting, I'll fix these failures after today series gets in if it's okay.
On Mon, 17 Sep 2012, Scott Ritchie wrote:
> Never underestimate the overeagerness of bots, I suppose...
>
> We're getting a lot of spam applications for testbot accounts now, maybe 2-3
> per day. Some are easy to discard because they put stuff like penis pills
> into the in
Never underestimate the overeagerness of bots, I suppose...
We're getting a lot of spam applications for testbot accounts now, maybe
2-3 per day. Some are easy to discard because they put stuff like penis
pills into the info field, but others look like just names. Suggestions
are we
d that works.
>
> Heh. It does add a manifest, but I don't think it works.
> See http://bugs.winehq.org/show_bug.cgi?id=31603
And I found the problem on testbot, too:
http://bugs.winehq.org/show_bug.cgi?id=31609
On Wed, Aug 8, 2012 at 7:27 AM, Dan Kegel wrote:
> Testing vcomp100 does work, but I shouldn't need to
> do that until there's some vcomp100-specific code.
>
> msvcr90/tests just adds a manifest, and that works.
Heh. It does add a manifest, but I don't think it works.
See http://bugs.winehq.org/
On Wed, 29 Aug 2012, Henri Verbeet wrote:
> On 29 August 2012 16:35, Francois Gouget wrote:
> > ---
> >
> > I think this made total sense when th WineTestBot was in its own
> > repository. Now maybe the COPYING.LIB and LICENSE files can be
> > considered to apply to all of the Wine tools and shou
On 29 August 2012 16:35, Francois Gouget wrote:
> ---
>
> I think this made total sense when th WineTestBot was in its own
> repository. Now maybe the COPYING.LIB and LICENSE files can be
> considered to apply to all of the Wine tools and should go to the
> top-level directory?
>
Not all of the co
Andre wrote:
> i'd something like in my attachment
Sorry, I should have linked to
http://testbot.winehq.org/JobDetails.pl?Key=20684
where I verified that testing vcomp100 did indeed work around the problem.
I guess that's where I'll put the tests until somebody hits me with a cluestick.
Am 08.08.2012 16:27, schrieb Dan Kegel:
> Testing vcomp100 does work, but I shouldn't need to
> do that until there's some vcomp100-specific code.
>
> msvcr90/tests just adds a manifest, and that works.
>
>
not sure why this works for msvcr90, maybe just for a minor version?
anyway, always vcom
Testing vcomp100 does work, but I shouldn't need to
do that until there's some vcomp100-specific code.
msvcr90/tests just adds a manifest, and that works.
Hello,
FWIW, comctl32 version 6 is accessible only with manifest, and there
are tests that reference it. Here's an example:
http://source.winehq.org/source/dlls/comctl32/tests/treeview.c#L1966
--
Daniel
Am 07.08.2012 06:26, schrieb Dan Kegel:
> On Mon, Aug 6, 2012 at 8:47 AM, Dan Kegel wrote:
>> On Mon, Aug 6, 2012 at 8:28 AM, Dan Kegel wrote:
>>> Is vcomp{,90,100}.dll not installed by default on Windows?
>>> If not, should we install it on a few of the VMs?
>>
>> Nevermind for the moment, I pro
On Mon, Aug 6, 2012 at 8:47 AM, Dan Kegel wrote:
> On Mon, Aug 6, 2012 at 8:28 AM, Dan Kegel wrote:
>> Is vcomp{,90,100}.dll not installed by default on Windows?
>> If not, should we install it on a few of the VMs?
>
> Nevermind for the moment, I probably have a manifest problem.
OK, I did my ho
On Mon, Aug 6, 2012 at 8:28 AM, Dan Kegel wrote:
> Is vcomp{,90,100}.dll not installed by default on Windows?
> If not, should we install it on a few of the VMs?
Nevermind for the moment, I probably have a manifest problem.
I'm trying to test a better set of stubs for vcomp.dll and its ilk,
but those dlls don't seem to be installed on testbot.
Is vcomp{,90,100}.dll not installed by default on Windows?
If not, should we install it on a few of the VMs?
It seems that WINEBUILD has taken a break two days ago, no tasks
involving building have been completed since then.
Regards,
Daniel
Hi Morten,
On 04/15/12 14:59, Morten Rønne wrote:
> Hi
>
> testbot.winehq.com certificate expired on 13-04-2012. So now the
> wininet tests in dlls/wininet/tests/http.c are failing with an error
> for me.
> I can't determine if the fault are in the test or the function called
> should handle the e
Hi
testbot.winehq.com certificate expired on 13-04-2012. So now the wininet
tests in dlls/wininet/tests/http.c are failing with an error for me.
I can't determine if the fault are in the test or the function called
should handle the error case.
The error message is:
err:wininet:NETCON_secure_
Stefan Dösinger wrote:
>When I manually submit a patch to the Wine testbot, it refuses to test it if
>the patch changes multiple tests.
I know that and live with it as follows:
- I usually keep changes to separate tests as distinct commits in my
git, so I can send them separately to t
Hi,
When I manually submit a patch to the Wine testbot, it refuses to test it if
the patch changes multiple tests. As a workaround I usually test a precompiled
.exe and submit it once for each modified test[1]. In the case of the ddraw
patch I sent today this missed test failures in 64 bit
On Sun, 2011-09-18 at 16:05 +0200, Maarten Lankhorst wrote:
> I moved the windows 7 x64 vm with sp1 applied to the base pool now. This means
> that all submitted patches will be run on that vm as well. The original win7
> vm
> is still available under its own name. Since all tests pass on that acc
On 22/09/2011 9:43 PM, Per Johansson wrote:
>
> 22 sep 2011 kl. 12:14 skrev Michael Stefaniuc:
>
>> Wow! /66? And that works? While the standard allows for that you "should
>> use /64" which everybody and his dog read it as that is the only thing
>> that needs to work and the only thing that get
Hey,
On 09/22/2011 04:54 PM, Michael Stefaniuc wrote:
> Per Johansson wrote:
>> 22 sep 2011 kl. 12:14 skrev Michael Stefaniuc:
>>
>>> Wow! /66? And that works? While the standard allows for that you "should
>>> use /64" which everybody and his dog read it as that is the only thing
>>> that needs t
Per Johansson wrote:
> 22 sep 2011 kl. 12:14 skrev Michael Stefaniuc:
>
>> Wow! /66? And that works? While the standard allows for that you "should
>> use /64" which everybody and his dog read it as that is the only thing
>> that needs to work and the only thing that get tested. IPv6 brings back
>
22 sep 2011 kl. 12:14 skrev Michael Stefaniuc:
> Wow! /66? And that works? While the standard allows for that you "should
> use /64" which everybody and his dog read it as that is the only thing
> that needs to work and the only thing that get tested. IPv6 brings back
> the class-full thinking wh
On 22/09/2011 7:56 PM, Maarten Lankhorst wrote:
> Hey,
>
> Testbot has 2 ips assigned to it:
>
> inet6 addr: 2001:888:2000:38:1000::1/66 Scope:Global
> inet6 addr: 2001:888:2000:38:1000::2/66 Scope:Global
>
> Does the ::1 work?
>
> ~Maarten
&g
0.000s
>>>>
>>>> $ time wget -6 --quiet http://testbot.winehq.org/
>>>> ... still stuck after 6+ minutes
>>>>
>>>> $ telnet -6 testbot.winehq.org
>>>> Trying 2001:888:2000:38:1000::2...
>>>> ... same thing
>>>&g
gt; ... still stuck after 6+ minutes
>>>
>>> $ telnet -6 testbot.winehq.org
>>> Trying 2001:888:2000:38:1000::2...
>>> ... same thing
>>>
>>>
>>> According to http://test-ipv6.com/ my desktop is configured just fine
>>> and I only have
:1000::2...
>> ... same thing
>>
>>
>> According to http://test-ipv6.com/ my desktop is configured just fine
>> and I only have trouble with the TestBot.
>>
>> Could this be a firewall problem? (testbot exposing an IPv6 address but
>> the firewall droppin
On Thu, 22 Sep 2011, Maarten Lankhorst wrote:
[...]
> > Could this be a firewall problem? (testbot exposing an IPv6 address but
> > the firewall dropping any IPv6 packets)
> >
> >
> > In the mean time I'm going to use my laptop which is still IPv4 only
&g
s
> sys 0m0.000s
>
> $ time wget -6 --quiet http://testbot.winehq.org/
> ... still stuck after 6+ minutes
>
> $ telnet -6 testbot.winehq.org
> Trying 2001:888:2000:38:1000::2...
> ... same thing
>
>
> According to http://test-ipv6.com/ my desktop is configured just fine
&g
On Wed, 14 Sep 2011, Francois Gouget wrote:
>
> Connecting to https://testbot.winehq.org/ over IPv6 hangs for ages :-(
> This makes accessing it from my desktop very annoying.
Hmm, I guess I really have to use the feedback form on the website :-(
--
Francois Gouget http://fgouge
Hi all,
I moved the windows 7 x64 vm with sp1 applied to the base pool now. This means
that all submitted patches will be run on that vm as well. The original win7 vm
is still available under its own name. Since all tests pass on that according
to winehq tests I'm keeping it in the base pool. I ho
after 6+ minutes
$ telnet -6 testbot.winehq.org
Trying 2001:888:2000:38:1000::2...
... same thing
According to http://test-ipv6.com/ my desktop is configured just fine
and I only have trouble with the TestBot.
Could this be a firewall problem? (testbot exposing an IPv6 address but
the firewall
DDERR_INVALIDPARAMS.
The line in question is:
*(volatile char*)0 = 2;
I can reproduce the freeze on my local system with the binaries built by the
testbot. I cannot reproduce them with my own 64 bit binaries, or with the ones
from http://test.winehq.org/builds. Thus I suspect that a problem with mingw
is
Hi all,
I've added a win7 sp1 testbot, it's currently in the extra vm's pool,
so it requires some extra actions to find it, but if you want to run
your tests against windows 7 sp1 with ie9 installed, you
should now be able to.
Happy testing!!
~Maarten
Hello Max,
I'm pretty sure you are trolling but with Alexandre on vacation it is
pretty quiet anyway, so I'll feed you...
On 08/08/2011 07:36 PM, max wrote:
> If I understand the philosophy of Wine correctly, it is to provide an
> alternative to
> the Microsoft implementation of the platform. T
Dmitry Timoshkov:
If I understand the philosophy of Wine correctly, it is to provide an
alternative to
the Microsoft implementation of the platform. The criteria for success
is that
applications written to run on the current Microsoft platform can run on
Wine. To
that end mandatory support
joerg-cyril.hoe...@t-systems.com wrote:
> However, if like me, you spend a lot of time with APIs designed and
> used in the nineties, e.g. MCI, then it makes a hell of a lot of sense
> to write tests that pass on w9x to discover how the API behaved at the
> time where the app was written.
MCI di
Hi,
>> what happened to the w9x test bots? I'd like them to run some kernel32
>> tests.
>> Testbot says "offline".
>They were hosted at Gé's house. Testbot can no longer reach them.
Ouch.
Dmitry Timoshkov wrote:
> Are there plans to 'rev
James McKenzie wrote:
> That is correct. The two are distinctly different and no further
> reports of running compliance tests against Windows9x should be
> recorded. However, insuring what functionality we do have in Wine for
> running antiquated Windows9x/ME programs should remain, if poss
On 8/7/11 6:55 AM, Dmitry Timoshkov wrote:
James McKenzie wrote:
There are functions that vary between Windows9x/ME and WindowsNT and
their ilk. People do use Wine to support Windows9x/ME programs that are
not supported, anymore, by current Windows. When we make changes to
functionality, it
James McKenzie wrote:
> There are functions that vary between Windows9x/ME and WindowsNT and
> their ilk. People do use Wine to support Windows9x/ME programs that are
> not supported, anymore, by current Windows. When we make changes to
> functionality, it is a 'good thing' to make sure we d
On 8/7/11 1:01 AM, Dmitry Timoshkov wrote:
James McKenzie wrote:
what happened to the w9x test bots? I'd like them to run some kernel32 tests.
Testbot says "offline".
They were hosted at Gé's house. Testbot can no longer reach them.
Are there plans to 'revive
Hey James,
On 08/07/2011 05:12 AM, James McKenzie wrote:
> On 8/3/11 7:10 AM, Maarten Lankhorst wrote:
>> On 08/01/2011 07:12 PM, joerg-cyril.hoe...@t-systems.com wrote:
>>> Hi,
>>>
>>> what happened to the w9x test bots? I'd like them to run some kerne
James McKenzie wrote:
> >> what happened to the w9x test bots? I'd like them to run some kernel32
> >> tests.
> >> Testbot says "offline".
> >>
> > They were hosted at Gé's house. Testbot can no longer reach them.
> >
>
On 8/3/11 7:10 AM, Maarten Lankhorst wrote:
On 08/01/2011 07:12 PM, joerg-cyril.hoe...@t-systems.com wrote:
Hi,
what happened to the w9x test bots? I'd like them to run some kernel32 tests.
Testbot says "offline".
They were hosted at Gé's house. Testbot can no longer rea
On 08/01/2011 07:12 PM, joerg-cyril.hoe...@t-systems.com wrote:
> Hi,
>
> what happened to the w9x test bots? I'd like them to run some kernel32 tests.
> Testbot says "offline".
>
They were hosted at Gé's house. Testbot can no longer reach them.
~Maarten
On Wed, Aug 3, 2011 at 10:09, wrote:
> Hi,
>
> Stefan Dösinger wrote:
>>> Testbot says "offline".
>>I think we killed w9x testing a few months ago
>
> That's not exactly right. While test.winehq.org no more performs daily w9x
> tests f
Hi,
Stefan Dösinger wrote:
>> Testbot says "offline".
>I think we killed w9x testing a few months ago
That's not exactly right. While test.winehq.org no more performs daily w9x
tests for Wine, the w9x machines have been available on testbot.winehq when
you select "
On Monday 01 August 2011 19:12:44 joerg-cyril.hoe...@t-systems.com wrote:
> Hi,
>
> what happened to the w9x test bots? I'd like them to run some kernel32
> tests. Testbot says "offline".
I think we killed w9x testing a few months ago
signature.asc
Description:
Hi,
what happened to the w9x test bots? I'd like them to run some kernel32 tests.
Testbot says "offline".
Thank you for your help,
Jörg Höhle
On Mon, Jun 6, 2011 at 03:17, Dan Kegel wrote:
> https://testbot.winehq.org/JobDetails.pl?Key=11509 shows failures and
> crashes, but the nearly identical
> https://testbot.winehq.org/JobDetails.pl?Key=11510 does not. (The latter one
> just adds a call to GetProcessMemoryInfo() in the xyz() loggi
On Mon, Jun 6, 2011 at 03:17, Dan Kegel wrote:
> https://testbot.winehq.org/JobDetails.pl?Key=11509 shows failures and
> crashes, but the nearly identical
> https://testbot.winehq.org/JobDetails.pl?Key=11510 does not. (The latter one
> just adds a call to GetProcessMemoryInfo() in the xyz() loggi
https://testbot.winehq.org/JobDetails.pl?Key=11509 shows failures and
crashes, but the nearly identical
https://testbot.winehq.org/JobDetails.pl?Key=11510 does not. (The latter one
just adds a call to GetProcessMemoryInfo() in the xyz() logging function.)
And the failure shown by the first patch
On Mon, 23 May 2011, Marvin wrote:
> VM StatusNumber of test failures
> WINEBUILDcompleted
> WNT4WSSP6completed 0
> W2KPROSP4completed 0
> WXPPROSP3completed 0
> W2K3R2SESP2 failed
> WVISTAADMcompleted 0
Also I have no problem with support
various operation systems Windows 98, NT, 2000, XP, Vista, 7. Also I have
experience with Linux Debian derivations, as well i manage with success other
Linux distributions.
I am interested to see how TestBot works, and maintain indefinitely.
I spoke with my emplo
Hi Greg,
I'm interested.
I'm pretty confident in Perl and have experience with VMware
server+player/VirtualBox/XEN so I hope to learn vSphere quickly.
Regards
Hark
On 04/ 5/11 08:23 PM, Greg Geldorp wrote:
Due to personal circumstances I won't be able to maintain the Test
Due to personal circumstances I won't be able to maintain the TestBot much
longer. I'm looking for a volunteer to take over this responsibility. I can
offer the hardware on which the bot runs for another 2 years or so. You'll get
full access to the hardware. It helps if yo
On 1/15/11 8:53 AM, Greg Geldorp wrote:
From: Alexandre Julliard
Greg Geldorp writes:
You'll have to take up the apply failure on the status page with Alexandre.
That message has nothing to do with the bot. Since the patch applied
without problems for me too, it seems you might have caught Al
From: Alexandre Julliard
> Greg Geldorp writes:
>
> > You'll have to take up the apply failure on the status page with Alexandre.
> > That message has nothing to do with the bot. Since the patch applied
> > without problems for me too, it seems you might have caught Alexandre
> > on a little mista
Greg Geldorp writes:
> You'll have to take up the apply failure on the status page with Alexandre.
> That message has nothing to do with the bot. Since the patch applied
> without problems for me too, it seems you might have caught Alexandre
> on a little mistake :-) (don't we all love it when we
From: Paul Vriens [mailto:paul.vriens.w...@gmail.com]
> On 01/14/2011 11:20 PM, Travis Athougies wrote:
> > Hi there,
> >
> > I've been trying to submit this patch to the testbot, and it keeps
> > refusing it with the error "Unrecognized file typea" (tha
On 15 January 2011 11:50, Paul Vriens wrote:
> That attached patch doesn't contain a test. Could that be it?
>
Even if it did though, I imagine naming it 1/4 when it's not actually
part of a series isn't going to help with the bot picking it up
automatically.
And of course that patch really *shou
Am 15.01.2011 11:50, schrieb Paul Vriens:
> On 01/14/2011 11:20 PM, Travis Athougies wrote:
>> Hi there,
>>
>> I've been trying to submit this patch to the testbot, and it keeps
>> refusing it with the error "Unrecognized file typea" (that's not a
&g
On 01/14/2011 11:20 PM, Travis Athougies wrote:
Hi there,
I've been trying to submit this patch to the testbot, and it keeps
refusing it with the error "Unrecognized file typea" (that's not a
typo, that's the exact error). The testbot has also refused to accept
the p
On 1/14/11 3:20 PM, Travis Athougies wrote:
Hi there,
I've been trying to submit this patch to the testbot, and it keeps
refusing it with the error "Unrecognized file typea" (that's not a
typo, that's the exact error). The testbot has also refused to accept
the patch
1 - 100 of 134 matches
Mail list logo
