question on push pull
Hi all, I have a quick question concerning the pushpull framework : is there any way to transfer full directory trees, as opposed to single files ? And which of the currently implemented transfer protocols would allow that ? I haven't see any examples on that, though I might have missed it. thanks a lot, Luca P.S.: Cameron, thanks for writing the push-pull user guide - it's great.
Re: Heads up: OODT-396 and OODT-397
-- I'm trying to do #TDD to wrap up OODT-215 :) I ♥ #TDD. --k
Build failed in Jenkins: oodt-trunk #302
See https://builds.apache.org/job/oodt-trunk/302/changes
Changes:
[ahart] resolve OODT-373: patch applied to trunk
--
[...truncated 1562 lines...]
---
T E S T S
---
Running org.apache.oodt.cas.crawl.option.TestBooleanOptions
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.034 sec
Results :
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[JENKINS] Recording test results
[INFO] [jar:jar {execution: default-jar}]
[INFO] Building jar:
https://builds.apache.org/job/oodt-trunk/ws/crawler/target/cas-crawler-0.4-SNAPSHOT.jar
[INFO] Preparing javadoc:javadoc
[WARNING] Removing: javadoc from forked lifecycle, to prevent recursive
invocation.
[INFO] No goals needed for project - skipping
[WARNING] DEPRECATED [aggregate]: since 2.5. Use the goals
codejavadoc:aggregate/code and codejavadoc:test-aggregate/code instead.
[INFO] [javadoc:javadoc {execution: attach-javadocs}]
[INFO] [assembly:single {execution: default}]
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Processing DependencySet (output=lib)
[INFO] Building tar :
https://builds.apache.org/job/oodt-trunk/ws/crawler/target/cas-crawler-0.4-SNAPSHOT-dist.tar.gz
[INFO] Processing DependencySet (output=lib)
[INFO] Building zip:
https://builds.apache.org/job/oodt-trunk/ws/crawler/target/cas-crawler-0.4-SNAPSHOT-dist.zip
[INFO] [install:install {execution: default-install}]
[INFO] Installing
https://builds.apache.org/job/oodt-trunk/ws/crawler/target/cas-crawler-0.4-SNAPSHOT.jar
to
https://builds.apache.org/job/oodt-trunk/ws/.repository/org/apache/oodt/cas-crawler/0.4-SNAPSHOT/cas-crawler-0.4-SNAPSHOT.jar
[INFO] Installing
https://builds.apache.org/job/oodt-trunk/ws/crawler/target/cas-crawler-0.4-SNAPSHOT-dist.tar.gz
to
https://builds.apache.org/job/oodt-trunk/ws/.repository/org/apache/oodt/cas-crawler/0.4-SNAPSHOT/cas-crawler-0.4-SNAPSHOT-dist.tar.gz
[INFO] Installing
https://builds.apache.org/job/oodt-trunk/ws/crawler/target/cas-crawler-0.4-SNAPSHOT-dist.zip
to
https://builds.apache.org/job/oodt-trunk/ws/.repository/org/apache/oodt/cas-crawler/0.4-SNAPSHOT/cas-crawler-0.4-SNAPSHOT-dist.zip
[JENKINS] Archiving
https://builds.apache.org/job/oodt-trunk/ws/crawler/pom.xml to
/home/hudson/hudson/jobs/oodt-trunk/modules/org.apache.oodt$cas-crawler/builds/2012-02-28_19-14-54/archive/org.apache.oodt/cas-crawler/0.4-SNAPSHOT/cas-crawler-0.4-SNAPSHOT.pom
[JENKINS] Archiving
https://builds.apache.org/job/oodt-trunk/ws/crawler/target/cas-crawler-0.4-SNAPSHOT.jar
to
/home/hudson/hudson/jobs/oodt-trunk/modules/org.apache.oodt$cas-crawler/builds/2012-02-28_19-14-54/archive/org.apache.oodt/cas-crawler/0.4-SNAPSHOT/cas-crawler-0.4-SNAPSHOT.jar
[JENKINS] Archiving
https://builds.apache.org/job/oodt-trunk/ws/crawler/target/cas-crawler-0.4-SNAPSHOT-dist.tar.gz
to
/home/hudson/hudson/jobs/oodt-trunk/modules/org.apache.oodt$cas-crawler/builds/2012-02-28_19-14-54/archive/org.apache.oodt/cas-crawler/0.4-SNAPSHOT/cas-crawler-0.4-SNAPSHOT-dist.tar.gz
[JENKINS] Archiving
https://builds.apache.org/job/oodt-trunk/ws/crawler/target/cas-crawler-0.4-SNAPSHOT-dist.zip
to
/home/hudson/hudson/jobs/oodt-trunk/modules/org.apache.oodt$cas-crawler/builds/2012-02-28_19-14-54/archive/org.apache.oodt/cas-crawler/0.4-SNAPSHOT/cas-crawler-0.4-SNAPSHOT-dist.zip
[INFO]
[INFO] Building CAS Curation Interface
[INFO]task-segment: [install]
[INFO]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 0 resource
[INFO] Copying 3 resources
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
https://builds.apache.org/job/oodt-trunk/ws/curator/src/test/resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Nothing to compile - all classes are up to date
[INFO] [surefire:test {execution: default-test}]
[INFO] Surefire report directory:
https://builds.apache.org/job/oodt-trunk/ws/curator/target/surefire-reports
---
T E S T S
---
There are no tests to run.
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[JENKINS] Recording test results
[INFO] [war:war {execution: default-war}]
[INFO] Packaging webapp
[INFO] Assembling webapp[cas-curator] in
[https://builds.apache.org/job/oodt-trunk/ws/curator/target/cas-curator-0.4-SNAPSHOT]
[INFO]
Re: Continuing a workflow after restarting the workflow manager
Yes, you're right. Sorry for the confusion. The repo will have all the workflow instance executed so far and you can even access instances' metadata. (There's a new command line option for this in 0.4) But, as you've seen, once you restart the wmgr it doesn't track the previous instances. I think it would be nice to have that functionality in workflow manager too. I'm not aware of any other way to do this. On Tue, Feb 28, 2012 at 2:23 PM, Keith Cummings kcumm...@nrao.edu wrote: Hi Sheryl. I tried using the wmgr-client command line options to pause/resume/stop workflow instances as you suggested. It worked great; thanks for pointing me there. FYI, I'm using v0.3, if that matters. As for the repo getting wiped out when the Workflow Manager is restarted, that's not what I see. I'm using the CAS Workflow Manager Monitor Web App to view what's going on. It continues to show the partially completed workflow after multiple restarts of the Workflow Manager. So the repo is not getting wiped out, but that old workflows don't seem to be accessible. If I try to pause/resume/stop this workflow from the command line, I get the following message: WARNING: WorkflowEngine: Attempt to resume workflow instance id: 119a9ebd-625a-11e1-b564-**9bb1991d21af, however, this engine is not tracking its execution So it's still in the repo, but the current manager isn't tracking it, so can't modify it. The use case I'm concerned about is losing partially completed workflows if the server crashes or is rebooted. There are other ways to protect against this, but it would be nice if the Workflow Manager would simply start back up where it left off. Thanks, Keith Sheryl John wrote: Hi Keith, First of all welcome to the OODT world! If you restart your Workflow Manager a new repo is created and all previous workflow instances are wiped out and so, the engine does not track previous tasks in your old workflow instance. You can check this using the command line option : --getWorkflowInsts or try ./wmgr-client --help for other cmd-lne options. If you're using 0.4-SNAPSHOT you'll see the latest command line menu. If you haven't restarted you wmgr you can start, pause and resume your workflow instance ( and this should complete the tasks in that workflow) with the cmd-line options. I usually restart the wmgr after I've modified policy files or changed environment variables/locations. Hope this helps! Sheryl On Tue, Feb 28, 2012 at 8:37 AM, Keith Cummings kcumm...@nrao.edu wrote: Hello, I'm at NRAO and we are considering using OODT in the near future and I just started playing around with it, specifically the the Workflow Manager. I was wondering if the Workflow Manager is able to restart workflows that are partially complete. For example, I started a workflow that has four tasks. During the processing of the second task, I stopped the Workflow Manager, then restarted it. The Workflow Manager does NOT continue processing this task/workflow. Is there a way to have it pick up where it left off? Thanks, Keith Cummings NRAO Socorro, NM -- -Sheryl
Jenkins build is unstable: oodt-trunk #303
See https://builds.apache.org/job/oodt-trunk/303/
Re: Build failed in Jenkins...
Hey Brian,
I don't have the cycles to really look at it but I did dig up this
http://www.thinkplexx.com/learn/howto/maven2/debug/fixing-too-many-open-files-maven-problem-solution-for-teamcity-hudson-local-and-ssh-shell-environments
http://www.thinkplexx.com/learn/howto/maven2/debug/fixing-too-many-open-files-maven-problem-solution-for-teamcity-hudson-local-and-ssh-shell-environmentsThe
section on profiling the number of open file handles for our project may help
diagnose where the issue is.
Thanks,
Paul
On Feb 28, 2012, at 1:39 PM, holenoter wrote:
hey guys,
Our build keeps failing with the following errors... could you reboot the
ubuntu1,ubuntu2,ubuntu3,ubuntu4 machines?
thanks,
-brian
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to create assembly: Failed to retrieve OS environment variables.
Reason: Cannot run program env: java.io.IOException: error=24, Too many open
files
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 5 minutes 26 seconds
[INFO] Finished at: Tue Feb 28 19:20:25 UTC 2012
[INFO] Final Memory: 71M/421M
[INFO]
Waiting for Jenkins to finish collecting data
Maven failed with error.
channel stopped
Begin forwarded message:
From: Apache Jenkins Server
jenk...@builds.apache.orgmailto:jenk...@builds.apache.org
Date: February 28, 2012 11:20:27 AM
To: dev@oodt.apache.orgmailto:dev@oodt.apache.org
Subject: Build failed in Jenkins: oodt-trunk #302
See https://builds.apache.org/job/oodt-trunk/302/changes
Changes:
[ahart] resolve OODT-373: patch applied to trunk
--
[...truncated 1562 lines...]
---
T E S T S
---
Running org.apache.oodt.cas.crawl.option.TestBooleanOptions
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.034 sec
Results :
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[JENKINS] Recording test results
[INFO] [jar:jar {execution: default-jar}]
[INFO] Building jar:
https://builds.apache.org/job/oodt-trunk/ws/crawler/target/cas-crawler-0.4-SNAPSHOT.jarhttps://builds.apacheorg/job/oodt-trunk/ws/crawler/target/cas-crawler-0.4-SNAPSHOT.jar
[INFO] Preparing javadoc:javadoc
[WARNING] Removing: javadoc from forked lifecycle, to prevent recursive
invocation.
[INFO] No goals needed for project - skipping
[WARNING] DEPRECATED [aggregate]: since 2.5. Use the goals
codejavadoc:aggregate/code and codejavadoc:test-aggregate/code instead.
[INFO] [javadoc:javadoc {execution: attach-javadocs}]
[INFO] [assembly:single {execution: default}]
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Processing DependencySet (output=lib)
[INFO] Building tar :
https://builds.apache.org/job/oodt-trunk/ws/crawler/target/cas-crawler-0.4-SNAPSHOT-dist.tar.gz
[INFO] Processing DependencySet (output=lib)
[INFO] Building zip:
https://builds.apache.org/job/oodt-trunk/ws/crawler/target/cas-crawler-0.4-SNAPSHOT-dist.zip
[INFO] [install:install {execution: default-install}]
[INFO] Installing
https://builds.apache.org/job/oodt-trunk/ws/crawler/target/cas-crawler-0.4-SNAPSHOT.jar
to
https://builds.apache.org/job/oodt-trunk/ws/.repository/org/apache/oodt/cas-crawler/0.4-SNAPSHOT/cas-crawler-0.4-SNAPSHOT.jar
[INFO] Installing
https://builds.apache.org/job/oodt-trunk/ws/crawler/target/cas-crawler-0.4-SNAPSHOT-dist.tar.gz
to
https://builds.apache.org/job/oodt-trunk/ws/.repository/org/apache/oodt/cas-crawler/0.4-SNAPSHOT/cas-crawler-0.4-SNAPSHOT-dist.tar.gzhttps://builds.apache.org/job/oodt-trunk/ws/.repository/org/apache/oodt/cas-crawler/0.4-SNAPSHOT/cas-crawler-04-SNAPSHOT-dist.tar.gz
[INFO] Installing
https://builds.apache.org/job/oodt-trunk/ws/crawler/target/cas-crawler-0.4-SNAPSHOT-dist.zip
to
https://builds.apache.org/job/oodt-trunk/ws/.repository/org/apache/oodt/cas-crawler/04-SNAPSHOT/cas-crawler-0.4-SNAPSHOT-dist.ziphttps://builds.apache.org/job/oodt-trunk/ws/.repository/org/apache/oodt/cas-crawler/0.4-SNAPSHOT/cas-crawler-0.4-SNAPSHOT-dist.zip
[JENKINS] Archiving
https://builds.apache.org/job/oodt-trunk/ws/crawler/pom.xml to
/home/hudson/hudson/jobs/oodt-trunk/modules/org.apache.oodt$cas-crawler/builds/2012-02-28_19-14-54/archive/org.apache.oodt/cas-crawler/0.4-SNAPSHOT/cas-crawler-0.4-SNAPSHOT.pom
[JENKINS] Archiving
https://builds.apache.org/job/oodt-trunk/ws/crawler/target/cas-crawler-0.4-SNAPSHOT.jar
to
/home/hudson/hudson/jobs/oodt-trunk/modules/org.apache.oodt$cas-crawler/builds/2012-02-28_19-14-54/archive/org.apache.oodt/cas-crawler/0.4-SNAPSHOT/cas-crawler-0.4-SNAPSHOT.jar
[JENKINS]
Jenkins build is back to stable : oodt-trunk #304
See https://builds.apache.org/job/oodt-trunk/304/changes
Re: Review Request: OODT-361: Workflow test event fails with NPE
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/4089/#review5430 --- Ship it! - Paul On 2012-02-28 20:05:18, Ricky Nguyen wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/4089/ --- (Updated 2012-02-28 20:05:18) Review request for oodt. Summary --- When DateConvert.isoParse is given a null input, it throws NPE. Solution is throw ParseException if input is null. WorkflowInstance catches ParseException and ignores it. This addresses bug OODT-361. https://issues.apache.org/jira/browse/OODT-361 Diffs - trunk/commons/src/main/java/org/apache/oodt/commons/util/DateConvert.java 1294802 Diff: https://reviews.apache.org/r/4089/diff Testing --- Ran HelloWorld, GoodbyeWorld. Thanks, Ricky
[NOTICE] Apache OODT curation tutorial screencast online
Hey Guys, I decided to make a 2 part screen cast as part of some work that I was doing on the EDRN project at JPL on how to how to create product type (dataset) policy, how to associate metadata with products, and how to make file manager aware of the new datasets and policy, and how to use the CAS curator webapp to perform bulk file ingestion, met extraction and curation via the web. I created an Apache OODT wiki page that links to a blog post and the You Tube videos, here ya go: http://s.apache.org/M5O Enjoy! Cheers, Chris ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++
Re: Review Request: OODT-395: SerializableMetadata.toXml() doesn't set namespace on root element
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/4088/#review5436 --- trunk/metadata/src/test/org/apache/oodt/cas/metadata/TestSerializableMetadata.java https://reviews.apache.org/r/4088/#comment11840 should check that namespace is cas namespace here - brian On 2012-02-28 19:47:16, Ricky Nguyen wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/4088/ --- (Updated 2012-02-28 19:47:16) Review request for oodt. Summary --- Create metadata root element with a proper namespace and prefix. This addresses bug OODT-395. https://issues.apache.org/jira/browse/OODT-395 Diffs - trunk/metadata/src/main/java/org/apache/oodt/cas/metadata/SerializableMetadata.java 1293402 trunk/metadata/src/test/org/apache/oodt/cas/metadata/TestSerializableMetadata.java 1293402 Diff: https://reviews.apache.org/r/4088/diff Testing --- Added unit test in TestSerializableMetadata#testNamespace() to demonstrate bug and fix. Thanks, Ricky
Re: Continuing a workflow after restarting the workflow manager
Hi Brian, I was hoping this one would get you commenting and out of the woodwork on this! :) OK, so yes it's my plan to support the state restore from the WorkflowInstanceRepository and from current state information like wengine provides. I'm not sure it'll be part of 0.4 (my main goal is to support the 80% of the wengine features to run, deliver it integrated into 0.4 and then start pulling over the stuff folks want and use in 0.4.1 or 0.5). Keith: welcome! I'll reply to your original thread shortly... Cheers, Chris On Feb 28, 2012, at 9:14 PM, Brian Foster wrote: wengine supports this because wengine only ever cached small amounts of the workflows in memory, the rest was save to disk and loaded on an as needed basis, so if the server went down it, when brought back up it just re-cached and kept going... the truck workflow only persists workflow task instances, the workflow itself in not persisted... this is something Chris will have to comment on if this is being ported or not (or has already been ported)... as far as starting a failed workflow from where it left off, wengine supports changing workflow states at the task level which allowed you to just set the tasks' states back to initial state and the wengine would start running it again... again Chris would be the one to answer if this is being ported or has already been ported -Brian On Feb 28, 2012, at 8:01 PM, Ramirez, Paul M (388J) paul.m.rami...@jpl.nasa.gov wrote: Hi Keith, This type of functionality may end up getting ported back into the trunk as I believe it was available in the wengine branch. This porting is being actively worked on and can generally be tracked here https://issues.apache.org/jira/browse/OODT-215 and specifically for rollback here https://issues.apache.org/jira/browse/OODT-212. Currently, Chris is leading the charge in getting this work back into the trunk but Brian Foster may also be able to comment on what is needed to support rolling back directly. --Paul Ramirez On Feb 28, 2012, at 10:54 AM, Sheryl John wrote: Hi Keith, First of all welcome to the OODT world! If you restart your Workflow Manager a new repo is created and all previous workflow instances are wiped out and so, the engine does not track previous tasks in your old workflow instance. You can check this using the command line option : --getWorkflowInsts or try ./wmgr-client --help for other cmd-lne options. If you're using 0.4-SNAPSHOT you'll see the latest command line menu. If you haven't restarted you wmgr you can start, pause and resume your workflow instance ( and this should complete the tasks in that workflow) with the cmd-line options. I usually restart the wmgr after I've modified policy files or changed environment variables/locations. Hope this helps! Sheryl On Tue, Feb 28, 2012 at 8:37 AM, Keith Cummings kcumm...@nrao.edumailto:kcumm...@nrao.edu wrote: Hello, I'm at NRAO and we are considering using OODT in the near future and I just started playing around with it, specifically the the Workflow Manager. I was wondering if the Workflow Manager is able to restart workflows that are partially complete. For example, I started a workflow that has four tasks. During the processing of the second task, I stopped the Workflow Manager, then restarted it. The Workflow Manager does NOT continue processing this task/workflow. Is there a way to have it pick up where it left off? Thanks, Keith Cummings NRAO Socorro, NM -- -Sheryl ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++
Review Request: OODT-395: SerializableMetadata.toXml() doesn't set namespace on root element
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/4088/ --- Review request for oodt. Summary --- Create metadata root element with a proper namespace and prefix. This addresses bug OODT-395. https://issues.apache.org/jira/browse/OODT-395 Diffs - trunk/metadata/src/main/java/org/apache/oodt/cas/metadata/SerializableMetadata.java 1293402 trunk/metadata/src/test/org/apache/oodt/cas/metadata/TestSerializableMetadata.java 1293402 Diff: https://reviews.apache.org/r/4088/diff Testing --- Added unit test in TestSerializableMetadata#testNamespace() to demonstrate bug and fix. Thanks, Ricky
Review Request: OODT-361: Workflow test event fails with NPE
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/4089/ --- Review request for oodt. Summary --- When DateConvert.isoParse is given a null input, it throws NPE. Solution is throw ParseException if input is null. WorkflowInstance catches ParseException and ignores it. This addresses bug OODT-361. https://issues.apache.org/jira/browse/OODT-361 Diffs - trunk/commons/src/main/java/org/apache/oodt/commons/util/DateConvert.java 1294802 Diff: https://reviews.apache.org/r/4089/diff Testing --- Ran HelloWorld, GoodbyeWorld. Thanks, Ricky
Re: Review Request: OODT-361: Workflow test event fails with NPE
--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/4089/#review5437 --- trunk/commons/src/main/java/org/apache/oodt/commons/util/DateConvert.java https://reviews.apache.org/r/4089/#comment11841 might want to also add here ...24 characters in length or null. to the exception message. - Chris On 2012-02-28 20:05:18, Ricky Nguyen wrote: --- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/4089/ --- (Updated 2012-02-28 20:05:18) Review request for oodt. Summary --- When DateConvert.isoParse is given a null input, it throws NPE. Solution is throw ParseException if input is null. WorkflowInstance catches ParseException and ignores it. This addresses bug OODT-361. https://issues.apache.org/jira/browse/OODT-361 Diffs - trunk/commons/src/main/java/org/apache/oodt/commons/util/DateConvert.java 1294802 Diff: https://reviews.apache.org/r/4089/diff Testing --- Ran HelloWorld, GoodbyeWorld. Thanks, Ricky
Re: svn commit: r1294929 - in /oodt/trunk/cli: README.txt src/main/assembly/ src/main/assembly/assembly.xml
DUDE. Nice! I will take it upon myself to migrate this to the wiki at some point soon if no one beats me to it. Cheers, Chris On Feb 28, 2012, at 5:28 PM, bfos...@apache.org bfos...@apache.org wrote: Author: bfoster Date: Wed Feb 29 01:28:58 2012 New Revision: 1294929 URL: http://svn.apache.org/viewvc?rev=1294929view=rev Log: - The beginnings of a Help Guide for using CAS-CLI... at some point probably should work its way into a wiki somewhere... figured for now this is the easiest place to put it until it is finished. Added: [..snip..] ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++
Build failed in Jenkins: oodt-trunk #306
See https://builds.apache.org/job/oodt-trunk/306/changes
Changes:
[bfoster] - More updates to CAS-CLI help guide
--
[...truncated 1567 lines...]
[INFO] Surefire report directory:
https://builds.apache.org/job/oodt-trunk/ws/crawler/target/surefire-reports
---
T E S T S
---
Running org.apache.oodt.cas.crawl.option.TestBooleanOptions
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.051 sec
Results :
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
[JENKINS] Recording test results
[INFO] [jar:jar {execution: default-jar}]
[INFO] Building jar:
https://builds.apache.org/job/oodt-trunk/ws/crawler/target/cas-crawler-0.4-SNAPSHOT.jar
[INFO] Preparing javadoc:javadoc
[WARNING] Removing: javadoc from forked lifecycle, to prevent recursive
invocation.
[INFO] No goals needed for project - skipping
[WARNING] DEPRECATED [aggregate]: since 2.5. Use the goals
codejavadoc:aggregate/code and codejavadoc:test-aggregate/code instead.
[INFO] [javadoc:javadoc {execution: attach-javadocs}]
[INFO] [assembly:single {execution: default}]
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Processing DependencySet (output=lib)
[INFO] Building tar :
https://builds.apache.org/job/oodt-trunk/ws/crawler/target/cas-crawler-0.4-SNAPSHOT-dist.tar.gz
[INFO] Processing DependencySet (output=lib)
[INFO] Building zip:
https://builds.apache.org/job/oodt-trunk/ws/crawler/target/cas-crawler-0.4-SNAPSHOT-dist.zip
[INFO] [install:install {execution: default-install}]
[INFO] Installing
https://builds.apache.org/job/oodt-trunk/ws/crawler/target/cas-crawler-0.4-SNAPSHOT.jar
to
https://builds.apache.org/job/oodt-trunk/ws/.repository/org/apache/oodt/cas-crawler/0.4-SNAPSHOT/cas-crawler-0.4-SNAPSHOT.jar
[INFO] Installing
https://builds.apache.org/job/oodt-trunk/ws/crawler/target/cas-crawler-0.4-SNAPSHOT-dist.tar.gz
to
https://builds.apache.org/job/oodt-trunk/ws/.repository/org/apache/oodt/cas-crawler/0.4-SNAPSHOT/cas-crawler-0.4-SNAPSHOT-dist.tar.gz
[INFO] Installing
https://builds.apache.org/job/oodt-trunk/ws/crawler/target/cas-crawler-0.4-SNAPSHOT-dist.zip
to
https://builds.apache.org/job/oodt-trunk/ws/.repository/org/apache/oodt/cas-crawler/0.4-SNAPSHOT/cas-crawler-0.4-SNAPSHOT-dist.zip
[JENKINS] Archiving
https://builds.apache.org/job/oodt-trunk/ws/crawler/pom.xml to
/home/hudson/hudson/jobs/oodt-trunk/modules/org.apache.oodt$cas-crawler/builds/2012-02-29_07-23-09/archive/org.apache.oodt/cas-crawler/0.4-SNAPSHOT/cas-crawler-0.4-SNAPSHOT.pom
[JENKINS] Archiving
https://builds.apache.org/job/oodt-trunk/ws/crawler/target/cas-crawler-0.4-SNAPSHOT.jar
to
/home/hudson/hudson/jobs/oodt-trunk/modules/org.apache.oodt$cas-crawler/builds/2012-02-29_07-23-09/archive/org.apache.oodt/cas-crawler/0.4-SNAPSHOT/cas-crawler-0.4-SNAPSHOT.jar
[JENKINS] Archiving
https://builds.apache.org/job/oodt-trunk/ws/crawler/target/cas-crawler-0.4-SNAPSHOT-dist.tar.gz
to
/home/hudson/hudson/jobs/oodt-trunk/modules/org.apache.oodt$cas-crawler/builds/2012-02-29_07-23-09/archive/org.apache.oodt/cas-crawler/0.4-SNAPSHOT/cas-crawler-0.4-SNAPSHOT-dist.tar.gz
[JENKINS] Archiving
https://builds.apache.org/job/oodt-trunk/ws/crawler/target/cas-crawler-0.4-SNAPSHOT-dist.zip
to
/home/hudson/hudson/jobs/oodt-trunk/modules/org.apache.oodt$cas-crawler/builds/2012-02-29_07-23-09/archive/org.apache.oodt/cas-crawler/0.4-SNAPSHOT/cas-crawler-0.4-SNAPSHOT-dist.zip
[INFO]
[INFO] Building CAS Curation Interface
[INFO]task-segment: [install]
[INFO]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 0 resource
[INFO] Copying 3 resources
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
https://builds.apache.org/job/oodt-trunk/ws/curator/src/test/resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Nothing to compile - all classes are up to date
[INFO] [surefire:test {execution: default-test}]
[INFO] Surefire report directory:
https://builds.apache.org/job/oodt-trunk/ws/curator/target/surefire-reports
---
T E S T S
---
There are no tests to run.
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[JENKINS] Recording test results
[INFO] [war:war {execution: default-war}]
[INFO] Packaging webapp
[INFO] Assembling
