I think the next step is to keep on improving the site (: And you are right, it is probably nothing.
Renato M. 2013/5/6 Andrew Hart <[email protected]>: > Hi Renato, > > I was just looking at the same thing. On the surface it appears to be a > connection error, which suggests it should be transient. > > The strange thing is that the changes do appear to be committed (I received > the usual svn commit email for r1479693 and r861119). Furthermore, the > staging site correctly reflects the minor changes I just made: > http://gora.staging.apache.org/ > > Perhaps, if it is not just a transient connection issue, it is related to > the fact that the main Gora site is not yet using the CMS? > > In either case, I'm not sure what the next step is, since the staging server > looks good. > > -Andrew. > > On 5/6/13 1:32 PM, Renato Marroquín Mogrovejo wrote: >> >> Should we ignore this error? >> >> Sending local/websites/gora/trunk/content >> Sending local/websites/gora/trunk/content/index.html >> Transmitting file data .svn: E175002: Commit failed (details follow): >> svn: E175002: PUT of >> >> '/repos/infra/!svn/txr/861118-ihoa/websites/staging/gora/trunk/content/index.html': >> SSL handshake failed: Connection reset by peer >> (https://svn.apache.org) >> svn: E175002: DELETE of '/repos/infra/!svn/txn/861118-ihoa': could not >> connect to server (https://svn.apache.org) >> program finished with exit code 1 >> elapsedTime=1082.375686 >> >> >> Renato M. >> >> 2013/5/6 <[email protected]>: >>> >>> The Buildbot has detected a new failure on builder gora-site-staging >>> while building ASF Buildbot. >>> Full details are available at: >>> http://ci.apache.org/builders/gora-site-staging/builds/1 >>> >>> Buildbot URL: http://ci.apache.org/ >>> >>> Buildslave for this Build: bb-cms-slave >>> >>> Build Reason: scheduler >>> Build Source Stamp: [branch gora/site] 1479693 >>> Blamelist: ahart >>> >>> BUILD FAILED: failed shell >>> >>> sincerely, >>> -The Buildbot >>> >>> >>> > > > -- > Andrew F. Hart > http://people.apache.org/~ahart >
