From: Mark M. <mie...@gm...> - 2009-03-03 16:15:16
|
Hi David, It seems the build machine is down. I was just trying to build the docs on it and couldn't get to it. -- Mark Miesfeld |
From: Gil B. <gba...@al...> - 2009-03-03 18:43:16
|
Mark, Not sure how quick David will be in getting this resolved as he is at SHARE this week (luckily in Austin, his hometown). Mark Miesfeld wrote: > Hi David, > > It seems the build machine is down. I was just trying to build the > docs on it and couldn't get to it. > > -- > Mark Miesfeld > > ------------------------------------------------------------------------------ > Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA > -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise > -Strategies to boost innovation and cut costs with open source participation > -Receive a $600 discount off the registration fee with the source code: SFAD > http://p.sf.net/sfu/XcvMzF8H > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > -- Gil Barmwater |
From: Mark M. <mie...@gm...> - 2009-03-03 19:12:48
|
On Tue, Mar 3, 2009 at 10:41 AM, Gil Barmwater <gba...@al...> wrote: > Not sure how quick David will be in getting this resolved as he is at > SHARE this week (luckily in Austin, his hometown). Okay, thanks for the update Gil. I usually build the docs myself, I just temporarily could not reach my system. That's why I noticed the build machine was down. -- Mark Miesfeld |
From: David A. <dav...@gm...> - 2009-03-04 16:59:09
|
All - Unfortunately, the problem you are seeing with access to the build machine is not a problem I have direct control over. It turns out the the build machine is up and runiing just fine, but the ATT network is timing out when you try to access it. I have opened up a bug report with ATT on this and they have made me aware that this is a recent known problem. It seems to come and go. At times the build machine answers and at others it does not. Sorry about this but I am at the mercy of the ATT network :-( On another note, I just made a modification to the build machine. For some builds (Fedora and docs) it sends a request to my Linux KVM machine to perform the build. These builds happen almost twice as fast as they do on the VMware guests. Slowly but surely I will migrate all the builds to this machine and the build server will just become a web server and a repository for the build outputs. You may have noticed also that I opened a bug on the sockets external functions. I discovered this bug in trying to bring up a Fedora 10 x86_64 KVM guest. Builds on this server are controlled via a remote daemon running on the build machine. Sockets are used to communicate build requests to the KVM guests and that was how I discovered the bug. David Ashley |
From: Mark M. <mie...@gm...> - 2009-03-04 17:24:05
|
On Wed, Mar 4, 2009 at 8:58 AM, David Ashley <dav...@gm...> wrote: > Unfortunately, the problem you are seeing with access to the build > machine is not a problem I have direct control over. It turns out the > the build machine is up and runiing just fine, but the ATT network is > timing out when you try to access it. Ah, the flakey network problem. ;-) > You may have noticed also that I opened a bug on the sockets external > functions. I discovered this bug in trying to bring up a Fedora 10 > x86_64 KVM guest. I did notice that. I tried the two socket samples on XP 64-bit, sfserver / sfclient and scserver / scclient, and they seem to work okay. -- Mark Miesfeld |
From: Rony G. F. <Ron...@wu...> - 2009-03-24 16:46:39
|
David Ashley wrote: > All - > > Unfortunately, the problem you are seeing with access to the build > machine is not a problem I have direct control over. It turns out the > the build machine is up and runiing just fine, but the ATT network is > timing out when you try to access it. I have opened up a bug report with > ATT on this and they have made me aware that this is a recent known > problem. It seems to come and go. At times the build machine answers and > at others it does not. > > Sorry about this but I am at the mercy of the ATT network :-( > Unfortunately, <http://build.ooRexx.org> is still not working. :( Are there any news/updates to this? Is there a time-span ATT is promising to fix this at all? ---rony |
From: David A. <dav...@gm...> - 2009-03-24 16:55:36
|
Rony G. Flatscher wrote: > > David Ashley wrote: >> All - >> >> Unfortunately, the problem you are seeing with access to the build >> machine is not a problem I have direct control over. It turns out the >> the build machine is up and runiing just fine, but the ATT network is >> timing out when you try to access it. I have opened up a bug report with >> ATT on this and they have made me aware that this is a recent known >> problem. It seems to come and go. At times the build machine answers and >> at others it does not. >> >> Sorry about this but I am at the mercy of the ATT network :-( >> > > > > Unfortunately, <http://build.ooRexx.org> is still not working. > :( > > Are there any news/updates to this? Is there a time-span ATT is > promising to fix this at all? > > ---rony > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are > powering Web 2.0 with engaging, cross-platform capabilities. Quickly and > easily build your RIAs with Flex Builder, the Eclipse(TM)based development > software that enables intelligent coding and step-through debugging. > Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com > ------------------------------------------------------------------------ > > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > Unfortunately, ATT is not being very helpful. In my experimentation it seems that distance is a primary factor in whether or not the request to the machine times out. I have tried several wifi spots in Austin and it works just fine. But once you get out of Texas it is very spotty and inconsistent. All this is really too bad because I have made some upgrades to the machine which make at least some of the builds much faster. David Ashley |
From: Rony G. F. <Ron...@wu...> - 2009-03-24 17:21:19
|
David Ashley wrote: > Rony G. Flatscher wrote: >> >> David Ashley wrote: >>> All - >>> >>> Unfortunately, the problem you are seeing with access to the build >>> machine is not a problem I have direct control over. It turns out the >>> the build machine is up and runiing just fine, but the ATT network is >>> timing out when you try to access it. I have opened up a bug report with >>> ATT on this and they have made me aware that this is a recent known >>> problem. It seems to come and go. At times the build machine answers and >>> at others it does not. >>> >>> Sorry about this but I am at the mercy of the ATT network :-( >>> >> >> >> >> Unfortunately, <http://build.ooRexx.org> is still not working. >> :( >> >> Are there any news/updates to this? Is there a time-span ATT is >> promising to fix this at all? >> >> ---rony >> > Unfortunately, ATT is not being very helpful. In my experimentation it > seems that distance is a primary factor in whether or not the request > to the machine times out. I have tried several wifi spots in Austin > and it works just fine. But once you get out of Texas it is very > spotty and inconsistent. > > All this is really too bad because I have made some upgrades to the > machine which make at least some of the builds much faster. Hmm, very strange indeed for an Internet provider! Here a traceroute from overseas to the machine: D:\Dokumente und Einstellungen\Administrator>tracert build.oorexx.org Routenverfolgung zu build.oorexx.org [69.150.206.90] über maximal 30 Abschnitte: 1 * <1 ms * gw-1-254.wu-wien.ac.at [137.208.254.253] 2 1 ms <1 ms * box-1-19.wu-wien.ac.at [137.208.19.135] 3 * 1 ms * ex-2-9.wu-wien.ac.at [137.208.9.22] 4 * 1 ms * vlan748.wien21.aco.net [193.171.13.129] 5 * 2 ms * 212.73.203.17 6 13 ms * * ae-6-6.ebr1.Frankfurt1.Level3.net [4.69.135.34] 7 23 ms 17 ms 17 ms ae-91-91.csw4.Frankfurt1.Level3.net [4.69.140.14] 8 * * 13 ms ae-92-92.ebr2.Frankfurt1.Level3.net [4.69.140.29] 9 * * * Zeitüberschreitung der Anforderung. 10 114 ms * * ae-4-4.ebr2.Newark1.Level3.net [4.69.132.102] 11 * 108 ms 107 ms ae-24-52.car4.Newark1.Level3.net [4.68.99.40] 12 108 ms * * ex1-g8-0-1.pxatga.sbcglobal.net [151.164.248.181] 13 * * 151 ms bb1-10g14-0.aus2tx.sbcglobal.net [151.164.243.245] 14 230 ms * 152 ms dist1-t1-3.aus2tx.sbcglobal.net [151.164.188.144] 15 152 ms 154 ms * rback2-g1-0.aus2tx.sbcglobal.net [99.171.168.40] 16 * * * Zeitüberschreitung der Anforderung. 17 * * * Zeitüberschreitung der Anforderung. 18 * * * Zeitüberschreitung der Anforderung. 19 * * * Zeitüberschreitung der Anforderung. 20 * * * Zeitüberschreitung der Anforderung. 21 * * * Zeitüberschreitung der Anforderung. 22 * * * Zeitüberschreitung der Anforderung. 23 * * * Zeitüberschreitung der Anforderung. 24 * * * Zeitüberschreitung der Anforderung. 25 * * * Zeitüberschreitung der Anforderung. 26 * * * Zeitüberschreitung der Anforderung. 27 * * * Zeitüberschreitung der Anforderung. 28 * * * Zeitüberschreitung der Anforderung. 29 * * * Zeitüberschreitung der Anforderung. 30 * * * Zeitüberschreitung der Anforderung. "Zeitüberschreitung" means "timeout". ATT should be able to telnet to a remote machine (one outside of Texas :) ) and doing the same. HTH, ---rony |