It happens on the Jenkins server as well - it seems to be when the slave is slow (i.e. another big product is building on it).

Is there an hs_err file?
There are no System.exit calls jena-elpahas-mapreduce itself.

Surefire FAQ:
http://maven.apache.org/surefire/maven-surefire-plugin/faq.html#vm-termination

It is not a test failure in Jena code - its maven failure.

Your system may be the factor. It is not possible to produce the release with the maven release plug-in unless all the tests pass. (Twice, once for release:prepare,once for release:perform).

e.g.
https://builds.apache.org/user/andy/my-views/view/Jena/job/Jena_Development_Test/2539/consoleFull

    Andy

There does seem to be something odd about the elephas tests - there are 8 suites that take over a minute, the machine seems to be idle whereas other suites are a few seconds. Some internal timeout which may be related.

oaj.hadoop.rdf.io.output.trig.BatchedTriGOutputTest
  67.332 sec
oaj.hadoop.rdf.io.input.trix.TriXAsQuadsInputTest
  70.159 sec
oaj.hadoop.rdf.io.input.trix.TriXInputTest
  70.116 sec
oaj.hadoop.rdf.io.input.compressed.jsonld.GZippedJsonLDQuadInputTest
  61.044 sec
oaj.hadoop.rdf.io.input.compressed.jsonld.GZippedJsonLDTripleInputTest
  60.877 sec
oaj.hadoop.rdf.io.input.compressed.jsonld.DeflatedJsonLDTripleInputTest
  60.739 sec
oaj.hadoop.rdf.io.input.compressed.jsonld.BZippedJsonLDQuadInputTest
  63.501 sec
oaj.hadoop.rdf.io.input.compressed.jsonld.BZippedJsonLDTripleInputTest
  61.149 sec
oaj.hadoop.rdf.io.input.compressed.jsonld.DeflatedJsonLDQuadInputTest
  60.849 sec


On 05/11/16 19:20, Claude Warren wrote:
Anybody seen this before?  Is this because I don't have something for
Elephas set up correctly?

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test)
on project jena-elephas-mapreduce: Execution default-test of goal
org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: The
forked VM terminated without properly saying goodbye. VM crash or
System.exit called?
[ERROR] Command was /bin/sh -c cd
/home/claude/apache/jena/jena-elephas/jena-elephas-mapreduce &&
/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java -jar
/home/claude/apache/jena/jena-elephas/jena-elephas-mapreduce/target/surefire/surefirebooter4324621841576259479.jar
/home/claude/apache/jena/jena-elephas/jena-elephas-mapreduce/target/surefire/surefire2256763119866991805tmp
/home/claude/apache/jena/jena-elephas/jena-elephas-mapreduce/target/surefire/surefire_05860600514762731971tmp


On Sat, Nov 5, 2016 at 4:40 PM, Claude Warren <[email protected]> wrote:

I have gotten 2 errors while building.  Both are in elephas and both are
forked VM terminated errors.  This may be an effect of the small system I
am building on.

Claude

On Sat, Nov 5, 2016 at 9:39 AM, Andy Seaborne <[email protected]> wrote:

+1


On 04/11/16 22:43, Andy Seaborne wrote:


Hi,

Here is a vote on a release of Jena 3.1.1
(with Fuseki 2.4.1 and Fuseki 1.4.1).

This is the second proposed candidate for this release.

** My signing key has changed - to verify, use the key in   **
** https://svn.apache.org/repos/asf/jena/dist/KEYS          **
** for [email protected].                                     **

* Dependency changes:

New module:
    jena-fuseki2/jena-fuseki-embedded

Updates:
      com.github.jsonld-java:jsonld-java      0.7.0 -> 0.8.3

      org.apache.httpcomponents:httpClient    4.2.6 -> 4.5.2
      org.apache.httpcomponents:httpCache     4.2.6 -> 4.5.2
      org.apache.httpcomponents:httpCore      4.2.5 -> 4.4.4

      com.jayway.awaitility:awaitility        1.6.4 -> 1.7.0
      com.spatial4j:spatial4j                 0.4.1 -> 0.5
      org.slf4j:*                             1.7.20 -> 1.7.21
      commons-codec:commons-codec             1.9 -> 1.10
      org.apache.commons:commons-collections4 4.0 -> 4.1
      org.apache.commons:commons-csv          1.0 -> 1.3
      org.apache.commons:commons-lang3        3.3.2 -> 3.4
      org.apache.thrift:libthrift             0.9.2 -> 0.9.3
      org.apache.mrunit:mrunit                1.0.0 -> 1.1.0
      com.github.rvesse:airline               2.1.0 -> 2.1.1


Key features of the release:

* Improve JSON-LD output
     JENA-1208 - François-Paul Servant
http://jena.staging.apache.org/documentation/io/rdf-output.html#json-ld

* Completed F&O XPath3 functions
      JENA-508 - Alessandro Seganti

* ComplexPhraseQueryParser
     JENA-1180 - Andrew Dolby

* Additional vocabularies (DCAT, VoID, ROV, ORG)
      JENA-1206 - Bart Hanssens

* Improvement to the Fuseki service script for RHEL/Centos 6.
      JENA-1219 - Dan Pritts

* ORDER BY now cancelable.

* Txn : a highlevel API for working with transactions
http://jena.staging.apache.org/documentation/txn/txn.html

* Embedded Fuseki
http://jena.staging.apache.org/documentation/fuseki2/fuseki-
embedded.html

* Property path speed ups (JENA-1195)

* Upgrade to Apache HttpClient v4.3 API
     => auth changes cause API changes.


Everyone, not just committers, is invited to test and vote.

Staging repository:
https://repository.apache.org/content/repositories/orgapachejena-1015/

Proposed dist/ area:
     https://dist.apache.org/repos/dist/dev/jena/

Keys:
     https://svn.apache.org/repos/asf/jena/dist/KEYS
     ** NB signing key has changed.


Git commit (browser URL):
     https://git-wip-us.apache.org/repos/asf/jena/commit/f7b3c416

Git Commit Hash:
     f7b3c416328bba4b8044e4ea8ad80e09ac51d720

Git Commit Tag:
     jena-3.1.1-rc2

Please vote to approve this release:

     [ ] +1 Approve the release
     [ ]  0 Don't care
     [ ] -1 Don't release, because ...

This vote will be open to at least

     Monday, 7 Nov 2016, 23:59 UTC

If you expect to check the release but the 72 hour limit does not work
for you, please email within the schedule above with an expected time
and we can extend the vote period.

Thanks,

     Andy

Checking needed:

+ does everything work on Linux?
+ does everything work on MS Windows?
+ does everything work on OS X?
+ are the GPG signatures fine?
+ are the checksums correct?
+ is there a source archive?
+ can the source archive really be built?
+ is there a correct LICENSE and NOTICE file in each artifact
       (both source and binary artifacts)?
+ does the NOTICE file contain all necessary attributions?
+ have any licenses of dependencies changed due to upgrades?
        if so have LICENSE and NOTICE been upgraded appropriately?
+ does the tag/commit in the SCM contain reproducible sources?




--
I like: Like Like - The likeliest place on the web
<http://like-like.xenei.com>
LinkedIn: http://www.linkedin.com/in/claudewarren




Reply via email to