Here are the largest results sets on the master in GB. We currently store 6.8TB
of total results, going back 14 months, and 1.1TB of archives going back 1
week.
1500Apple MountainLion (Leaks)
1018Chromium Mac Release (Tests)
857 Chromium Linux Release (Tests)
532 Chromium Win
I'm surprised that chromium mac is 3x the size of Apple Mac... debug
even! Chromium build output should be much smaller... at least as of
late.
On Fri, Jan 25, 2013 at 9:30 AM, William Siegrist wsiegr...@apple.com wrote:
Here are the largest results sets on the master in GB. We currently store
This is the output of the test bots, right? I'm guessing this is due
to (a) us running pixel tests and (b) not checking in the expected
failing baselines. If I ever get back to working on supporting
-failing.png, this could go down *a lot*.
Alternatively, we could just decide to check in the
Yes, I'm referring to the test results that get uploaded to
http://build.webkit.org/results/, presumably by the test slaves. The
archives I refer to are http://build.webkit.org/archives/, which I believe
are just the binaries built by the build slaves.
-Bill
On Jan 25, 2013, at 9:42 AM, Dirk
On Fri, Jan 25, 2013 at 9:30 AM, William Siegrist wsiegr...@apple.comwrote:
Here are the largest results sets on the master in GB. We currently store
6.8TB of total results, going back 14 months, and 1.1TB of archives going
back 1 week.
1500Apple MountainLion (Leaks)
1018Chromium
build.webkit.org went down over night due to running out of disk space. I'm
working to bring it back as soon as possible.
-Bill
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo/webkit-dev
build.webkit.org is back up. I reduced the retention of build archives from 2
weeks to 1 week to regain enough space to get the master running again. I'm
still waiting on space calculations to figure out what ate up all of the space
(the server uses 9TB of space currently after deleting 1TB of
On Jun 21, 2012, at 10:43 AM, Jon Lee jon...@apple.com wrote:
Is something being upgraded right now?
No, the config file has a problem in it which is unrelated to our upgrade as
far as I can tell. I'm trying to track down what happened.
$ buildbot checkconfig
Unhandled Error
Traceback
On Jun 21, 2012, at 10:54 AM, William Siegrist wsiegr...@apple.com wrote:
On Jun 21, 2012, at 10:43 AM, Jon Lee jon...@apple.com wrote:
Is something being upgraded right now?
No, the config file has a problem in it which is unrelated to our upgrade as
far as I can tell. I'm trying to
En 21/06/12 19:54, William Siegrist escribiu:
On Jun 21, 2012, at 10:43 AM, Jon Lee jon...@apple.com wrote:
Is something being upgraded right now?
No, the config file has a problem in it which is unrelated to our upgrade as
far as I can tell. I'm trying to track down what happened.
$
One can run:
http://trac.webkit.org/browser/trunk/Tools/BuildSlaveSupport/build.webkit.org-config/mastercfg_unittest.py
to test the master locally, but that's all I know of.
On Thu, Jun 21, 2012 at 11:15 AM, Sergio Villar Senin
svil...@igalia.com wrote:
En 21/06/12 19:54, William Siegrist
Hi,
In this case we could have avoided the breakage with running this unittest.
Can we make the master somehow run this unittest before restarting itself?
br,
Ossy
Eric Seidel írta:
One can run:
The server does not run the unittests, but it does normally run `buildbot
checkconfig`. However, we had to temporarily bypass the checkconfig test during
restart due to a bug in Buildbot:
http://trac.buildbot.net/ticket/2279
The best thing to do when working on the buildbot config is to have
I'd like to see a 'test' buildbot up and running that we could use as a staging
area for trying out new changes before deploying to the production server. We
could copy /OpenSource/Tools/BuildSlaveSupport/build.webkit.org-config to
/OpenSource/Tools/BuildSlaveSupport/test.webkit.org-config,
On 2012-06-21, at 15:46, Lucas Forschler lforsch...@apple.com wrote:
I'd like to see a 'test' buildbot up and running that we could use as a
staging area for trying out new changes before deploying to the production
server. We could copy
Hi,
Sorry for the late response, I didn't have to much time last week.
But fortunately I managed to fix it today, and uploaded the proposed patches:
- Unhide login form on the build.webkit.org -
https://bugs.webkit.org/show_bug.cgi?id=88981
- Update buildbot master in autoinstaller to match
Hi Ossy,
Can you send me the bugzilla link for the ForceScheduler work?
Thanks,
Lucas
On May 31, 2012, at 9:22 AM, Lucas Forschler wrote:
HI Ossy,
I did notice the display order change as well. I think I am going to open a
bug to rename all of the Apple bots to prefix them with 'Apple'.
Lucas Forschler írta:
to 0.8.6p1
Will be back online when complete.
Lucas
Hi All,
Unfortunately there are too annoying bugs introduced
with upgrading build master to 0.8.6p1 :
Problem 1
--
Builders are alphabetically ordered on http://build.webkit.org/waterfall
instead of the given
HI Ossy,
I did notice the display order change as well. I think I am going to open a
bug to rename all of the Apple bots to prefix them with 'Apple'. We (at Apple)
would like to get our bots into a more conforming naming convention. I realize
that won't solve the problem with having a
On the other hand, this looks like a regression. Can we file a bug against
buildbot and see what they have to say about it?
On May 31, 2012 9:22 AM, Lucas Forschler lforsch...@apple.com wrote:
HI Ossy,
I did notice the display order change as well. I think I am going to open
a bug to rename
to 0.8.6p1
Will be back online when complete.
Lucas
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Yay! for 0.8.6. Hopefully it fixes the stuck-in-trigger issue :)
- Ryosuke
On Wed, May 30, 2012 at 6:20 PM, Lucas Forschler lforsch...@apple.comwrote:
to 0.8.6p1
Will be back online when complete.
Lucas
___
webkit-dev mailing list
22 matches
Mail list logo
