www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Mason (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (INFRA-1555) fs related errors only on the apache hudson
Date Tue, 25 Mar 2008 09:35:24 GMT

     [ https://issues.apache.org/jira/browse/INFRA-1555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Justin Mason resolved INFRA-1555.

    Resolution: Won't Fix
      Assignee: Justin Mason

marking as WONTFIX.  I'm pretty sure this is the getcwd() thing I mentioned, and the fix there
should work.

> fs related errors only on the apache hudson
> -------------------------------------------
>                 Key: INFRA-1555
>                 URL: https://issues.apache.org/jira/browse/INFRA-1555
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: Hudson
>            Reporter: Brian Fox
>            Assignee: Justin Mason
> I'm not able to get Maven to build on the apache hudson instance, but it's building fine
everywhere else. It seems related to the way the file system is setup. It appears that /export/hudson
and /zonestorage/hudson are the same although ls -la doesn't show a link. Anyway, the system
is getting confused because see the following surefire output:
> "junit.framework.AssertionFailedError: expected:</export/home/hudson/hudson/jobs/Maven
2.0.x/workspace/maven-2.0.x/maven-project/src/test/resources/inheritance-repo/t11/p0> but
was:</zonestorage/hudson/home/hudson/hudson/jobs/Maven 2.0.x/workspace/maven-2.0.x/maven-project/src/test/resources/inheritance-repo/t11/p0>"
> from:
> http://hudson.zones.apache.org/hudson/job/Maven%202.0.x/org.apache.maven$maven-project/ws/target/surefire-reports/org.apache.maven.project.inheritance.t11.ProjectInheritanceTest.txt
> I could probably work around it in this test, but clearly something isn't right if we
are getting different paths returned from the same process. This is likely going to cause
further issues on other tests and ITs.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message