Page 16 of 20

Re: The SVN, nightly builds and biweekly betas

PostPosted: 24 Oct 2012, 12:08
by friarsol
Chris H. wrote:Today's snapshot build attempt ended in an error.
Could not connect to server. Unknown host ftp.cardforge.org
Sounds like the forge server was down when the snapshot build was attempted?

Re: The SVN, nightly builds and biweekly betas

PostPosted: 24 Oct 2012, 12:12
by Chris H.
friarsol wrote:
Chris H. wrote:Today's snapshot build attempt ended in an error.
Could not connect to server. Unknown host ftp.cardforge.org
Sounds like the forge server was down when the snapshot build was attempted?
 
I thought so too...

I checked http://cardforge.org/releases/snapshots/forge/forge/ and was able to access the folder for the most recent snapshot.

I then tried a second attempt at deploying the new snapshot to cardforge and got the same error. :(

And I am able to download the most recent snapshot from cardforge.

Re: The SVN, nightly builds and biweekly betas

PostPosted: 24 Oct 2012, 12:58
by timmermac
I wonder if there's a storage space limit that is being run into. Could something like that cause that error to pop up?

Re: The SVN, nightly builds and biweekly betas

PostPosted: 25 Oct 2012, 11:22
by Chris H.
I was able to do a snapshot build and deploy today.

Not sure what was wrong with cardforge yesterday but we appear to be OK at this time. :)

Re: The SVN, nightly builds and biweekly betas

PostPosted: 28 Oct 2012, 12:03
by Chris H.
Today's snapshot build attempt ended in an error.

Code: Select all
[INFO] Using Groovy-Eclipse compiler to compile both Java and Groovy files
----------
1. ERROR in /Users/chrish/Workspace_SVN/ForgeSVN/src/main/java/forge/card/spellability/Spell.java (at line 23)
   import org.testng.collections.Lists;
          ^^^^^^^^^^
The import org.testng cannot be resolved
----------
2. ERROR in /Users/chrish/Workspace_SVN/ForgeSVN/src/main/java/forge/card/spellability/Spell.java (at line 128)
   final List<Card> allp = Lists.newArrayList(Singletons.getModel().getGame().getCardsIn(ZoneType.Battlefield));
                           ^^^^^
Lists cannot be resolved
----------
2 problems (2 errors)[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] Found 2 errors and 0 warnings.
[INFO] 1 error
[INFO] -------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 21.038s
[INFO] Finished at: Sun Oct 28 07:56:40 EDT 2012
[INFO] Final Memory: 11M/81M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile (default-compile) on project forge: Compilation failure
[ERROR] Found 2 errors and 0 warnings.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
 
It looks like it may be a missed spelled import?

And there is a second error, "Lists cannot be resolved".

Re: The SVN, nightly builds and biweekly betas

PostPosted: 18 Jan 2013, 12:28
by Chris H.
My attempt to do a Maven based build and deploy for version 1.3.5 ended in a failure. :(

Code: Select all
[INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.1:deploy (default-deploy) on project forge: Error uploading site: IOException caught while attempting to upload /Users/chrish/Workspace_SVN/ForgeSVN/target/checkout/target/site/apidocs/forge/control/input/class-use/InputControl.html: Operation timed out -> [Help 1]
 
This error may be just a temporary thing and may resolve itself. But I am not sure.

I am wondering if we might have a situation at the cardforge site with an incomplete deploy but I do not have the technical know how to check the cardforge site and to fix/remove an incomplete deploy.

It looks like the pom file was updated to version 1.3.6 before the failure. I guess that I should edit this file in the Eclipse pom file editor to move this back to 1.3.5 before I try to do the next build and deploy.

Below is the terminal contents incase anyone wants to take a peek at it.
 

Re: The SVN, nightly builds and biweekly betas

PostPosted: 18 Jan 2013, 14:05
by Max mtg
Chris H. wrote:I am wondering if we might have a situation at the cardforge site with an incomplete deploy but I do not have the technical know how to check the cardforge site and to fix/remove an incomplete deploy.
I have a vast experience as a web developer - I can help with almost anything related to site.

Re: The SVN, nightly builds and biweekly betas

PostPosted: 18 Jan 2013, 15:58
by Chris H.
Max mtg wrote:
Chris H. wrote:I am wondering if we might have a situation at the cardforge site with an incomplete deploy but I do not have the technical know how to check the cardforge site and to fix/remove an incomplete deploy.
 
I have a vast experience as a web developer - I can help with almost anything related to site.
 
Thank you for the offer, it now looks like we have a partial deploy to cardforge. I viewed http://cardforge.org/releases/releases/forge/forge/ and I find a directory for forge 1.3.5 at http://cardforge.org/releases/releases/forge/forge/1.3.5/.

I spent some time looking at the terminal log and found the following:

Code: Select all
[INFO] [INFO] --- maven-deploy-plugin:2.7:deploy (default-deploy) @ forge ---
[INFO] Uploading: ftp.cardforge.org/releases/forge/forge/1.3.5/forge-1.3.5.jar
[INFO] Uploaded: ftp.cardforge.org/releases/forge/forge/1.3.5/forge-1.3.5.jar (3133 KB at 315.5 KB/sec)
[INFO] Uploading: ftp.cardforge.org/releases/forge/forge/1.3.5/forge-1.3.5.pom
[INFO] Uploaded: ftp.cardforge.org/releases/forge/forge/1.3.5/forge-1.3.5.pom (48 KB at 43.0 KB/sec)
[INFO] Downloading: ftp.cardforge.org/releases/forge/forge/maven-metadata.xml
[INFO] Downloaded: ftp.cardforge.org/releases/forge/forge/maven-metadata.xml (2 KB at 2.0 KB/sec)
[INFO] Uploading: ftp.cardforge.org/releases/forge/forge/maven-metadata.xml
[INFO] Uploaded: ftp.cardforge.org/releases/forge/forge/maven-metadata.xml (2 KB at 1.9 KB/sec)
[INFO] Uploading: ftp.cardforge.org/releases/forge/forge/1.3.5/forge-1.3.5-sources.jar
[INFO] Uploaded: ftp.cardforge.org/releases/forge/forge/1.3.5/forge-1.3.5-sources.jar (1564 KB at 436.0 KB/sec)
[INFO] Uploading: ftp.cardforge.org/releases/forge/forge/1.3.5/forge-1.3.5.tar.bz2
[INFO] Uploaded: ftp.cardforge.org/releases/forge/forge/1.3.5/forge-1.3.5.tar.bz2 (50049 KB at 266.6 KB/sec)
[INFO] Uploading: ftp.cardforge.org/releases/forge/forge/1.3.5/forge-1.3.5-osx.tar.bz2
[INFO] Uploaded: ftp.cardforge.org/releases/forge/forge/1.3.5/forge-1.3.5-osx.tar.bz2 (51188 KB at 261.5 KB/sec)
 
So it now looks like the build and deploy was successful. It appears that the deploying of the reports died in an IO error at some point likely towards the end of the process. And the reports are deployed after the forge archives are deployed.

Should I go ahead and post the release message for 1.3.5 and let the masses try it out? I think that the two forge archives are OK and it is just the reports that are incomplete.

Re: The SVN, nightly builds and biweekly betas

PostPosted: 18 Jan 2013, 16:17
by friarsol
Chris H. wrote:Should I go ahead and post the release message for 1.3.5 and let the masses try it out? I think that the two forge archives are OK and it is just the reports that are incomplete.
The reports are nice, but I wouldn't stop a release from happening because they couldn't upload.

I just downloaded the file on windows and it seems to run just fine for me.

Re: The SVN, nightly builds and biweekly betas

PostPosted: 18 Jan 2013, 16:27
by Max mtg
if all crucial distributive files are in place, there is no obstacle to release a new build.

Otherwise you can just make a local build and upload the missing files.

Re: The SVN, nightly builds and biweekly betas

PostPosted: 18 Jan 2013, 16:38
by Chris H.
friarsol wrote:The reports are nice, but I wouldn't stop a release from happening because they couldn't upload.

I just downloaded the file on windows and it seems to run just fine for me.
 
OK, the 1.3.5 beta is now released to the public and I agree that everything but the reports are good to go. :)

Re: The SVN, nightly builds and biweekly betas

PostPosted: 26 Feb 2013, 02:21
by Chris H.
I attempted to update to the head version using Eclipse on my Mac after the large change that was made earlier today. After several hours it stopped prematurely with a RA Layer request failed.

I attempted to re-sync to the head version and an earlier version prior to the large change that was made earlier today. I get the same error.

I deleted the project and attempted to re-import the project via Checkout Projects from SVN. And I get the same error it appears. I can not think of any thing else that I can do at this time.

Sorry. :(

I had deleted the project inside of Eclipse but I still had the project inside of the Workspace folder so I re-added the project to Eclipse. Attempted to sync and get:

RA layer request failed
svn: Server sent unexpected return value (413 Request Entity Too Large) in response to REPORT request for '/forge/!svn/vcc/default'
 
I get the same error when I attempt to Update to Head. Additional details follow:


org.tigris.subversion.javahl.ClientException: RA layer request failed
svn: Server sent unexpected return value (413 Request Entity Too Large) in response to REPORT request for '/forge/!svn/vcc/default'

org.tigris.subversion.javahl.ClientException: RA layer request failed
svn: Server sent unexpected return value (413 Request Entity Too Large) in response to REPORT request for '/forge/!svn/vcc/default'

Re: The SVN, nightly builds and biweekly betas

PostPosted: 26 Feb 2013, 03:01
by myk
I was reading through the diffs in websvn, and the diff for that change is too large to fit in memory (see WebSVN run out of memory trying to display the diff). It might just be too large for Eclipse to handle. I was able to update ok from the commandline (in less than a minute, I might add) on both OSX and Linux:
Code: Select all
cd forge/trunk
svn up
Edit: I was able to build the snapshot targets. If it's helpful, I can upload them somewhere for you.

Re: The SVN, nightly builds and biweekly betas

PostPosted: 26 Feb 2013, 04:11
by Chris H.
myk wrote:I was reading through the diffs in websvn, and the diff for that change is too large to fit in memory (see WebSVN run out of memory trying to display the diff). It might just be too large for Eclipse to handle. I was able to update ok from the commandline (in less than a minute, I might add) on both OSX and Linux:
Code: Select all
cd forge/trunk
svn up
Edit: I was able to build the snapshot targets. If it's helpful, I can upload them somewhere for you.
 
Thank you myk for the response.

Yeah, I CD to my local copy in my workspace and then 'svn up' on two diferent occasions and get the same response in my terminal app:

Code: Select all
CardForge:ForgeSVN chrish$ svn up
svn: Server sent unexpected return value (413 Request Entity Too Large) in response to REPORT request for '/forge/!svn/vcc/default'

Re: The SVN, nightly builds and biweekly betas

PostPosted: 26 Feb 2013, 04:33
by Max mtg