On Oct 25, 2012, at 4:54 PM, Greg Logan <[email protected]> wrote:
> On 12-10-23 01:36 PM, Wesley Alan Wright wrote:
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] BUILD FAILURE
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 6:36.110s
>> [INFO] Finished at: Tue Oct 16 11:53:58 EDT 2012
>> [INFO] Final Memory: 44M/268M
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-surefire-plugin:2.6:test (default-test) on
>> project matterhorn-workflow-service-impl: There are test failures.
>>
>> workaround appears to be
>>
>> mvn clean install -DdeployTo=/opt/matterhorn/trunk -DskipTests
>
> Those tests tend to be for things that the system requires to function
> properly. You might be able to build, but I doubt that you would be
> able to run things correctly!
I got the idea from here:
http://lists.opencastproject.org/pipermail/matterhorn-users/2012-March/002196.html
where a guy named Tobias opined:
"If you were a developer and about to commit code to the project, you
should indeed be worried and probably hold back your commit until all tests
pass. As an adopter though, skipping the tests should not be a problem."
But yeah, passing all tests is a good thing. But if a build test fails, and you
are a mere mortal adopter, what do do? File a bug report?
> "
>> -----------------------------------------------------------------------
>>
>> Starting matterhorn,
>> /Library/LaunchDaemons/org.opencastproject.matterhorn.plist:
>>
>> o remove lines...
>>
>> <key>DYLD_LIBRARY_PATH</key>
>>
>> <string>/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ImageIO.framework/Resources:/opt/local/lib</string>
>>
>> o replace line...
>>
>> <string>--noi</key>
>> with
>> <string>--noi</string>
>>
>
> I'm not familiar with OSX at all, but are these changes going to break
> support of earlier OSX versions?
>
Who knows? Google DYLD_LIBRARY_PATH matterhorn. General consensus is leave
DYLD_LIBRARY_PATH blank.
the <string>--noi</key> thing is obvious syntax error. But might as well get
rid of it, too, as it doesn't seem to do as intended, which is append
"-Dgosh.args=--nointeractive" to the Java opts sent to felix
>>
>> Running /opt/matterhorn/trunk/docs/scripts/3rd_party/menu3p , option "a"
>> yields...
>
> A bunch of bad checksums... What happens when you run the script again
> later? Sometimes mirrors are down, but if it persists then either the
> mirror is permanently offline, or the filename has changed.
>
Tried a bunch of tricks from MacPorts documentation. nada. thought I had it by
manually installing an earlier released Portfile, but then the menu3p script
stomped all over it and I was back where I started. Filed a bug report with the
port developer.
-----------------------------------------------------------------------
| Wesley Alan Wright <mailto:[email protected]> |
| Center for Teaching and Learning __0__ |
| Room 407 Lafayette Building / \ | \ |
| University of Vermont \77 |
| Burlington, Vermont 05405-0160 USA. \\ http://www.uvm.edu/skivt-l |
| Voice: 802-656-1254 vv |
| aim:goim?screenname=maddogskideath http://www.uvm.edu/~waw/ |
-----------------------------------------------------------------------
_______________________________________________
Matterhorn-users mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
