I was originally going to host the FreeBSD 9 buildbot myself (in a VM)
but I now have an offer for permanent amd64/x86-64 FreeBSD 9 and
FreeBSD 10 buildbots.
It seems Christian is not available; is there anyone else who can set
up a buildslave account (ideally both FreeBSD 9 amd64 and FreeBSD 10
Sorry. Looks like I missed a mail. I'll create the account tomorrow. Who
should receive the credentials. You, Ed?
On 09/18/2013 02:57 PM, Ed Maste wrote:
I was originally going to host the FreeBSD 9 buildbot myself (in a VM)
but I now have an offer for permanent amd64/x86-64 FreeBSD 9 and
On Mon, Sep 09, 2013 at 02:15:57PM -0400, Ed Maste wrote:
On 17 July 2013 20:07, Ed Maste ema...@freebsd.org wrote:
On 8 July 2013 11:15, Ed Maste ema...@freebsd.org wrote:
Ok, as soon as I can get a password (after the buildbot disk space
issues are sorted out) I'll contribute a
On 17 July 2013 20:07, Ed Maste ema...@freebsd.org wrote:
On 8 July 2013 11:15, Ed Maste ema...@freebsd.org wrote:
Ok, as soon as I can get a password (after the buildbot disk space
issues are sorted out) I'll contribute a FreeBSD 9 amd64 builder.
It seems the disk space / inode issue is
On 8 July 2013 11:15, Ed Maste ema...@freebsd.org wrote:
Ok, as soon as I can get a password (after the buildbot disk space
issues are sorted out) I'll contribute a FreeBSD 9 amd64 builder.
It seems the disk space / inode issue is resolved; is there anything
further still in the way of adding
On 3 July 2013 04:57, Stefan Hajnoczi stefa...@gmail.com wrote:
On Tue, Jul 02, 2013 at 09:35:41AM +0200, Christian Berendt wrote:
On 07/02/2013 09:31 AM, Stefan Hajnoczi wrote:
I think the solution is to add another buildmaster administrator. I
believe Christian offered that in the past.
On Tue, Jul 02, 2013 at 09:35:41AM +0200, Christian Berendt wrote:
On 07/02/2013 09:31 AM, Stefan Hajnoczi wrote:
I think the solution is to add another buildmaster administrator. I
believe Christian offered that in the past.
Sure. I think it would be the best to have an additional admin
On Mon, Jul 01, 2013 at 08:10:34AM -0400, Ed Maste wrote:
On 1 July 2013 07:47, Stefan Hajnoczi stefa...@gmail.com wrote:
Yes, Christian Berendt admins the buildmaster. How much time has passed
since you emailed?
June 7; perhaps the email was lost. I would like to start with a
FreeBSD
Hello Stefan.
On 07/02/2013 09:31 AM, Stefan Hajnoczi wrote:
Okay, I put Christian in the To: field. Let's wait two days for a
response.
I dropped Andreas a few lines to get further information about the
missing packages.
I think the solution is to add another buildmaster administrator.
On Thu, Jun 20, 2013 at 09:58:41AM -0400, Ed Maste wrote:
On 5 June 2013 10:04, Anthony Liguori aligu...@us.ibm.com wrote:
Hi,
Below is the coverage we currently have in buildbot. It's not terribly
complete but I suspect it does reflect what people are actually testing
and care
On 1 July 2013 07:47, Stefan Hajnoczi stefa...@gmail.com wrote:
Yes, Christian Berendt admins the buildmaster. How much time has passed
since you emailed?
June 7; perhaps the email was lost. I would like to start with a
FreeBSD 9.x x86_64 instance, potentially adding i386 and FreeBSD
On 5 June 2013 10:04, Anthony Liguori aligu...@us.ibm.com wrote:
Hi,
Below is the coverage we currently have in buildbot. It's not terribly
complete but I suspect it does reflect what people are actually testing
and care about.
In terms of policy, we should consider buildbot coverage as a
Hi,
Below is the coverage we currently have in buildbot. It's not terribly
complete but I suspect it does reflect what people are actually testing
and care about.
In terms of policy, we should consider buildbot coverage as a
requirement for a platform/architecture to be fully supported. Fully
On 5 June 2013 10:04, Anthony Liguori aligu...@us.ibm.com wrote:
In terms of policy, we should consider buildbot coverage as a
requirement for a platform/architecture to be fully supported. Fully
supported means (1) that code will be rejected/reverted if it breaks one
of these platforms (2)
On 05/06/13 10:04 AM, Anthony Liguori wrote:
Hi,
Below is the coverage we currently have in buildbot. It's not terribly
complete but I suspect it does reflect what people are actually testing
and care about.
In terms of policy, we should consider buildbot coverage as a
requirement for a
15 matches
Mail list logo
