On Fri, Sep 30, 2011 at 00:33, Jerome Leclanche wrote:
> On Thu, Sep 29, 2011 at 8:59 PM, Dan Kegel wrote:
>> Do you object to Greg's existing testbot emails, too
>
> Kinda, yeah. I read wine-devel for developer comments, insights,
> development about wine, etc. Bot emails feel kind of wrong here
On Thu, Sep 29, 2011 at 8:59 PM, Dan Kegel wrote:
> Do you object to Greg's existing testbot emails, too
Kinda, yeah. I read wine-devel for developer comments, insights,
development about wine, etc. Bot emails feel kind of wrong here; I
especially dislike WTB's because a lot of them are timeout-s
On Thu, Sep 29, 2011 at 1:25 PM, Octavian Voicu
wrote:
> On Thu, Sep 29, 2011 at 12:59 PM, Dan Kegel wrote:
>> Do you object to Greg's existing testbot emails, too?
>
> They're annoying when they are spurious...
Yes. That's why I've been focusing on reducing the spurious email
rate, and won't t
Do you object to Greg's existing testbot emails, too?
Well before I flip the switch to turn on email to wine-devel,
I will have a nice history of those emails for viewing, so people
can judge the actual added noise level for themselves.
On Thu, Sep 29, 2011 at 12:20 PM, Jerome Leclanche wrote:
>
On Thu, Sep 29, 2011 at 12:59 PM, Dan Kegel wrote:
> Do you object to Greg's existing testbot emails, too?
They're annoying when they are spurious...
Octavian
How about just sending error emails to the wine-bots list, AJ and the
patch author? To be really honest I hate reading all the testbot
emails on wine-devel.
J
On Thu, Sep 29, 2011 at 7:43 PM, Dan Kegel wrote:
> The buildbot is alive and well and has been finding real
> problems of various sorts
The buildbot is alive and well and has been finding real
problems of various sorts roughly once a day for some time.
I'm not spending much time on it anymore, just watching
and tweaking occasionally.
The number of spurious failures is tapering off as I
slowly expand the blacklist and polish up the
On 09/01/2011 10:50 AM, Henri Verbeet wrote:
> Looking at this from a slightly different angle, I think that if you
> expect people to take buildbot results seriously, you should run it on
> a configuration that's known to be solid, so that people can be
> confident any failures are actual issues w
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 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
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 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 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 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
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
-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
On Wed, Aug 31, 2011 at 3:53 PM, Stefan Dösinger wrote:
> On the other hand I think having a hardware with "strange" limits in the
> testbot system can help to avoid getting bad assumptions about those limits
> into the code, so I'll spend a day or two trying to isolate the issues and at
> least f
On Sunday 28 August 2011 17:52:21 Dan Kegel wrote:
> On Sun, Aug 28, 2011 at 2:16 AM, Stefan Dösinger
wrote:
> > Is it possible to set up a slave that e.g. runs only the d3d tests? I
> > have some older machines with older GPUs that are still worth
> > covering(Radeon X1600, Geforce 7, maybe even
ernatively, avoid attaching patches containing .po or .rc files
The patch that caused the problem choked on the first line,
From: name-with-accent
So it's not just .po files that cause the problem.
I've disabled the attachment code, and am tweaking the message
formatting now. Apolo
On Mon, Aug 29, 2011 at 23:41, Dan Kegel wrote:
> On Sun, Aug 28, 2011 at 8:53 PM, Dan Kegel wrote:
>> I hope to turn on email notifications sometime this week.
>
> Buildbot is now sending email on failure. There are two caveats:
> - it's emailing directly from a cable modem, not using an smtp r
On Sun, Aug 28, 2011 at 8:53 PM, Dan Kegel wrote:
> I hope to turn on email notifications sometime this week.
Buildbot is now sending email on failure. There are two caveats:
- it's emailing directly from a cable modem, not using an smtp relay,
so some mail systems may think it's spam
- buildbot
2011/8/29 Dan Kegel :
> 011/8/29 Frédéric Delanoy :
>> On Mon, Aug 29, 2011 at 05:53, Dan Kegel wrote:
>>> The buildbot now uses ccache, which sped up builds
>>> tremendously. Cycle time of build slaves with ccache
>>> using is 10-11 minutes;
>>
>> Told you ;) From 14 mins to 10-11 mins, nice 25%
011/8/29 Frédéric Delanoy :
> On Mon, Aug 29, 2011 at 05:53, Dan Kegel wrote:
>> The buildbot now uses ccache, which sped up builds
>> tremendously. Cycle time of build slaves with ccache
>> using is 10-11 minutes;
>
> Told you ;) From 14 mins to 10-11 mins, nice 25% speed up
> Although it may ma
On Mon, Aug 29, 2011 at 05:53, Dan Kegel wrote:
> The buildbot now uses ccache, which sped up builds
> tremendously. Cycle time of build slaves with ccache
> using is 10-11 minutes;
Told you ;) From 14 mins to 10-11 mins, nice 25% speed up
Although it may make things a bit slower in general for
The buildbot now uses ccache, which sped up builds
tremendously. Cycle time of build slaves with ccache
using is 10-11 minutes; the e8400 and q9300 are almost
as fast as the i7 now. (Dunno about the celeron yet.)
A few more flaky tests are now blacklisted, and the
cluster has been running all af
On Sun, Aug 28, 2011 at 2:16 AM, Stefan Dösinger wrote:
> Is it possible to set up a slave that e.g. runs only the d3d tests? I have
> some older machines with older GPUs that are still worth covering(Radeon
> X1600, Geforce 7, maybe even the Radeon 9000 mobility), but I am not sure if
> the ma
On 08/27/2011 12:00 PM, Dan Kegel wrote:
> - stability problems
> The buildbot cluster is not ready for prime time yet.
> My ubuntu 11.04-based slaves tend
> to lock up within a day with either an OOM failure, an X livelock, or
> something else. So I brought an ubuntu 10.04.3 slave online and
> mo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Is it possible to set up a slave that e.g. runs only the d3d tests? I have some
older machines with older GPUs that are still worth covering(Radeon X1600,
Geforce 7, maybe even the Radeon 9000 mobility), but I am not sure if the
machines as a w
- stability problems
The buildbot cluster is not ready for prime time yet.
My ubuntu 11.04-based slaves tend
to lock up within a day with either an OOM failure, an X livelock, or
something else. So I brought an ubuntu 10.04.3 slave online and
moved the buildmaster off onto its own machine;
let's s
The bot found a real problem again in someone's patch today.
Mail is not yet automated, so I let the author know by hand.
Because several people asked whether they could run
headless slaves, I added headless support; now if
DISPLAY is not set, the bot won't try to run any
tests known to fail with
Hi Seth,
yum, yes, please send me your changes. I'd be happy to add gentoo
prerequisite handling.
I don't think the build slave needs any incoming connections at all,
it always connects to the master, not the other way around.
What graphics card do you have?
- Dan
On Fri, Aug 19, 2011 at 3:32 P
Dan,
Great job with this. I've got a 64bit E6300 I can setup as a build slave.
It's up and on 24/7 folding (gpu) so the cpu sites mostly idle. I've already
adapted your scripts to work with gentoo/funtoo. I just replaced the apt-get
with emerge commands. I can send those changes to you if you want
Compiler warnings - clang/gcc would be nice I guess. I have a terrible
10-line shell script to generate reports, I sent two to the mailing
list in the past.
As for hosting a buildbot, I can probably do that, I have an ubuntu
x64 8-core i7 machine on a static IP with 98% uptime. Can you ping me
on
On Thu, Aug 18, 2011 at 5:19 PM, Jerome Leclanche wrote:
> Any chances for an automated warning report as well?
What kind of warnings are you interested in - compile or runtime?
> Also, ideally, there would be one build with all --enables and one
> with all --disables for all this. Theres often
On Fri, Aug 19, 2011 at 2:29 AM, Dan Kegel wrote:
> http://buildbot.kegel.com/ caught a couple of real problems today.
>
> Remember the original patchwatcher? It died because only
> one person knew how to run it, and it was too hard to set up.
> I'm trying to not make that mistake this time.
> To
http://buildbot.kegel.com/ caught a couple of real problems today.
Remember the original patchwatcher? It died because only
one person knew how to run it, and it was too hard to set up.
I'm trying to not make that mistake this time.
To that end, I've made the process easier, and would like as
man
I brought up the proof-of-concept buildbot-based patchwatcher
on two old PCs here; its status page is http://buildbot.kegel.com/
It has caught one real problem so far this morning.
to-do list:
- make cleaner script and doc for adding a new slave
- make it start automatically after reboot
- sandbox
38 matches
Mail list logo
