You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oodt.apache.org by "Chris A. Mattmann (JIRA)" <ji...@apache.org> on 2011/09/21 04:11:08 UTC

[jira] [Created] (OODT-318) Fix for Jenkins builds and java.io.tmpdir issue for testing via Maven

Fix for Jenkins builds and java.io.tmpdir issue for testing via Maven
---------------------------------------------------------------------

                 Key: OODT-318
                 URL: https://issues.apache.org/jira/browse/OODT-318
             Project: OODT
          Issue Type: Improvement
          Components: build proces, metadata container, pcs, push pull framework
    Affects Versions: 0.3, 0.2, 0.1-incubating
         Environment: builds.apache.org, found fix Jenkins testing on solaris, e.g., see: https://builds.apache.org/job/oodt-trunk/9/
            Reporter: Chris A. Mattmann
            Assignee: Chris A. Mattmann
             Fix For: 0.4


Our Jenkins jobs are failing every other day, basically whenever we run on a solaris box, and they are failing specifically in the following tests (e.g., see: https://builds.apache.org/job/oodt-trunk/5/)

https://builds.apache.org/job/oodt-trunk/5/org.apache.oodt$cas-metadata/testReport/
https://builds.apache.org/job/oodt-trunk/5/org.apache.oodt$oodt-commons/
https://builds.apache.org/job/oodt-trunk/5/org.apache.oodt$cas-protocol-sftp/console

Basically as pointed out by Oliver Lamly on builds@:

http://s.apache.org/XvJ

We can fix this with a custom Maven surefire-test declaration for the *java.io.tmpdir* property:

{code:xml}
 <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-surefire-plugin</artifactId>
          <version>2.9</version>
          <configuration>
            ....
            <systemPropertyVariables>
              <java.io.tmpdir>${project.build.outputDirectory}</java.io.tmpdir>
            </systemPropertyVariables>
            ....
          </configuration>
        </plugin>
{code}


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (OODT-318) Fix for Jenkins builds and java.io.tmpdir issue for testing via Maven

Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OODT-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris A. Mattmann updated OODT-318:
-----------------------------------

    Description: 
Our Jenkins jobs are failing every other day, basically whenever we run on a solaris box, and they are failing specifically in the following tests (e.g., see: https://builds.apache.org/job/oodt-trunk/5/)

https://builds.apache.org/job/oodt-trunk/5/org.apache.oodt$cas-metadata/testReport/
https://builds.apache.org/job/oodt-trunk/5/org.apache.oodt$oodt-commons/
https://builds.apache.org/job/oodt-trunk/5/org.apache.oodt$cas-protocol-sftp/console

Basically as pointed out by Oliver Lamy on builds@:

http://s.apache.org/XvJ

We can fix this with a custom Maven surefire-test declaration for the *java.io.tmpdir* property:

{code:xml}
 <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-surefire-plugin</artifactId>
          <version>2.9</version>
          <configuration>
            ....
            <systemPropertyVariables>
              <java.io.tmpdir>${project.build.outputDirectory}</java.io.tmpdir>
            </systemPropertyVariables>
            ....
          </configuration>
        </plugin>
{code}


  was:
Our Jenkins jobs are failing every other day, basically whenever we run on a solaris box, and they are failing specifically in the following tests (e.g., see: https://builds.apache.org/job/oodt-trunk/5/)

https://builds.apache.org/job/oodt-trunk/5/org.apache.oodt$cas-metadata/testReport/
https://builds.apache.org/job/oodt-trunk/5/org.apache.oodt$oodt-commons/
https://builds.apache.org/job/oodt-trunk/5/org.apache.oodt$cas-protocol-sftp/console

Basically as pointed out by Oliver Lamly on builds@:

http://s.apache.org/XvJ

We can fix this with a custom Maven surefire-test declaration for the *java.io.tmpdir* property:

{code:xml}
 <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-surefire-plugin</artifactId>
          <version>2.9</version>
          <configuration>
            ....
            <systemPropertyVariables>
              <java.io.tmpdir>${project.build.outputDirectory}</java.io.tmpdir>
            </systemPropertyVariables>
            ....
          </configuration>
        </plugin>
{code}



> Fix for Jenkins builds and java.io.tmpdir issue for testing via Maven
> ---------------------------------------------------------------------
>
>                 Key: OODT-318
>                 URL: https://issues.apache.org/jira/browse/OODT-318
>             Project: OODT
>          Issue Type: Improvement
>          Components: build proces, metadata container, pcs, push pull framework
>    Affects Versions: 0.1-incubating, 0.2, 0.3
>         Environment: builds.apache.org, found fix Jenkins testing on solaris, e.g., see: https://builds.apache.org/job/oodt-trunk/9/
>            Reporter: Chris A. Mattmann
>            Assignee: Chris A. Mattmann
>             Fix For: 0.4
>
>
> Our Jenkins jobs are failing every other day, basically whenever we run on a solaris box, and they are failing specifically in the following tests (e.g., see: https://builds.apache.org/job/oodt-trunk/5/)
> https://builds.apache.org/job/oodt-trunk/5/org.apache.oodt$cas-metadata/testReport/
> https://builds.apache.org/job/oodt-trunk/5/org.apache.oodt$oodt-commons/
> https://builds.apache.org/job/oodt-trunk/5/org.apache.oodt$cas-protocol-sftp/console
> Basically as pointed out by Oliver Lamy on builds@:
> http://s.apache.org/XvJ
> We can fix this with a custom Maven surefire-test declaration for the *java.io.tmpdir* property:
> {code:xml}
>  <plugin>
>           <groupId>org.apache.maven.plugins</groupId>
>           <artifactId>maven-surefire-plugin</artifactId>
>           <version>2.9</version>
>           <configuration>
>             ....
>             <systemPropertyVariables>
>               <java.io.tmpdir>${project.build.outputDirectory}</java.io.tmpdir>
>             </systemPropertyVariables>
>             ....
>           </configuration>
>         </plugin>
> {code}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (OODT-318) Fix for Jenkins builds and java.io.tmpdir issue for testing via Maven

Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OODT-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris A. Mattmann resolved OODT-318.
------------------------------------

    Resolution: Fixed

- fixed in r1173463.

> Fix for Jenkins builds and java.io.tmpdir issue for testing via Maven
> ---------------------------------------------------------------------
>
>                 Key: OODT-318
>                 URL: https://issues.apache.org/jira/browse/OODT-318
>             Project: OODT
>          Issue Type: Improvement
>          Components: build proces, metadata container, pcs, push pull framework
>    Affects Versions: 0.1-incubating, 0.2, 0.3
>         Environment: builds.apache.org, found fix Jenkins testing on solaris, e.g., see: https://builds.apache.org/job/oodt-trunk/9/
>            Reporter: Chris A. Mattmann
>            Assignee: Chris A. Mattmann
>             Fix For: 0.4
>
>
> Our Jenkins jobs are failing every other day, basically whenever we run on a solaris box, and they are failing specifically in the following tests (e.g., see: https://builds.apache.org/job/oodt-trunk/5/)
> https://builds.apache.org/job/oodt-trunk/5/org.apache.oodt$cas-metadata/testReport/
> https://builds.apache.org/job/oodt-trunk/5/org.apache.oodt$oodt-commons/
> https://builds.apache.org/job/oodt-trunk/5/org.apache.oodt$cas-protocol-sftp/console
> Basically as pointed out by Oliver Lamly on builds@:
> http://s.apache.org/XvJ
> We can fix this with a custom Maven surefire-test declaration for the *java.io.tmpdir* property:
> {code:xml}
>  <plugin>
>           <groupId>org.apache.maven.plugins</groupId>
>           <artifactId>maven-surefire-plugin</artifactId>
>           <version>2.9</version>
>           <configuration>
>             ....
>             <systemPropertyVariables>
>               <java.io.tmpdir>${project.build.outputDirectory}</java.io.tmpdir>
>             </systemPropertyVariables>
>             ....
>           </configuration>
>         </plugin>
> {code}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (OODT-318) Fix for Jenkins builds and java.io.tmpdir issue for testing via Maven

Posted by "Chris A. Mattmann (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OODT-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris A. Mattmann updated OODT-318:
-----------------------------------

    Description: 
Our Jenkins jobs are failing every other day, basically whenever we run on a solaris box, and they are failing specifically in the following tests (e.g., see: https://builds.apache.org/job/oodt-trunk/5/)

https://builds.apache.org/job/oodt-trunk/5/org.apache.oodt$cas-metadata/testReport/
https://builds.apache.org/job/oodt-trunk/5/org.apache.oodt$oodt-commons/
https://builds.apache.org/job/oodt-trunk/5/org.apache.oodt$cas-protocol-sftp/console

Basically as pointed out by Olivier Lamy on builds@:

http://s.apache.org/XvJ

We can fix this with a custom Maven surefire-test declaration for the *java.io.tmpdir* property:

{code:xml}
 <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-surefire-plugin</artifactId>
          <version>2.9</version>
          <configuration>
            ....
            <systemPropertyVariables>
              <java.io.tmpdir>${project.build.outputDirectory}</java.io.tmpdir>
            </systemPropertyVariables>
            ....
          </configuration>
        </plugin>
{code}


  was:
Our Jenkins jobs are failing every other day, basically whenever we run on a solaris box, and they are failing specifically in the following tests (e.g., see: https://builds.apache.org/job/oodt-trunk/5/)

https://builds.apache.org/job/oodt-trunk/5/org.apache.oodt$cas-metadata/testReport/
https://builds.apache.org/job/oodt-trunk/5/org.apache.oodt$oodt-commons/
https://builds.apache.org/job/oodt-trunk/5/org.apache.oodt$cas-protocol-sftp/console

Basically as pointed out by Oliver Lamy on builds@:

http://s.apache.org/XvJ

We can fix this with a custom Maven surefire-test declaration for the *java.io.tmpdir* property:

{code:xml}
 <plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-surefire-plugin</artifactId>
          <version>2.9</version>
          <configuration>
            ....
            <systemPropertyVariables>
              <java.io.tmpdir>${project.build.outputDirectory}</java.io.tmpdir>
            </systemPropertyVariables>
            ....
          </configuration>
        </plugin>
{code}



> Fix for Jenkins builds and java.io.tmpdir issue for testing via Maven
> ---------------------------------------------------------------------
>
>                 Key: OODT-318
>                 URL: https://issues.apache.org/jira/browse/OODT-318
>             Project: OODT
>          Issue Type: Improvement
>          Components: build proces, metadata container, pcs, push pull framework
>    Affects Versions: 0.1-incubating, 0.2, 0.3
>         Environment: builds.apache.org, found fix Jenkins testing on solaris, e.g., see: https://builds.apache.org/job/oodt-trunk/9/
>            Reporter: Chris A. Mattmann
>            Assignee: Chris A. Mattmann
>             Fix For: 0.4
>
>
> Our Jenkins jobs are failing every other day, basically whenever we run on a solaris box, and they are failing specifically in the following tests (e.g., see: https://builds.apache.org/job/oodt-trunk/5/)
> https://builds.apache.org/job/oodt-trunk/5/org.apache.oodt$cas-metadata/testReport/
> https://builds.apache.org/job/oodt-trunk/5/org.apache.oodt$oodt-commons/
> https://builds.apache.org/job/oodt-trunk/5/org.apache.oodt$cas-protocol-sftp/console
> Basically as pointed out by Olivier Lamy on builds@:
> http://s.apache.org/XvJ
> We can fix this with a custom Maven surefire-test declaration for the *java.io.tmpdir* property:
> {code:xml}
>  <plugin>
>           <groupId>org.apache.maven.plugins</groupId>
>           <artifactId>maven-surefire-plugin</artifactId>
>           <version>2.9</version>
>           <configuration>
>             ....
>             <systemPropertyVariables>
>               <java.io.tmpdir>${project.build.outputDirectory}</java.io.tmpdir>
>             </systemPropertyVariables>
>             ....
>           </configuration>
>         </plugin>
> {code}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira