Maven - strange problem with nfs when building

I have a maven project that builds OK locally (windows). When I try to build it on our svn server (linux), it freezes when running tests.

I see the created tmp file:

nfs0000000001e9c8a900000017

in the following directory from my test module:

/ project_name-test / target / Surefire reports

Configuration in pom:

<plugin>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-surefire-plugin</artifactId>
            <dependencies/>
            <configuration>
                <systemProperties>
                    <property>
                        <name>java.io.tmpdir</name>
                        <value>${basedir}/target/tmp</value>
                    </property>
                </systemProperties>
                <skip>true</skip>
                <suiteXmlFiles>
                    <suiteXmlFile>
                        src/test/conf/testng.xml
                    </suiteXmlFile>
                </suiteXmlFiles>
                <childDelegation>true</childDelegation>
                <argLine>-Dsun.lang.ClassLoader.allowArraySyntax=true</argLine>
            </configuration>
            <executions>
                <execution>
                    <phase>integration-test</phase>
                    <goals>
                        <goal>test</goal>
                    </goals>
                    <configuration>
                        <skip>false</skip>
                    </configuration>
                </execution>
            </executions>
        </plugin>

Please note that a full check and build in the / tmp folder works fine , but on

/ var / build / builds / project_name / up-docstore / project_name / trunk / project_name-test / target / Surefire reports

not executed.

I have a feeling that the .nfs tmp file may be causing problems ... but I don’t see a workaround.

Can you give me a hint?

Thank.

:, , CTRL + Z, "fg", , ... ( )

+3
3

"" , maven NFS ( , ).

+1

.nfsXXXX " ", NFS, POSIX NFSv3 .

, , , - . , .nfsXXXX .

+3

Try fuser {filename}

Use the fuser to find the file lock process. The nfs file should go away on its own after the process stops.

You may have to kill the process, but I suspect this is your maven build on its own?

+1
source

Source: https://habr.com/ru/post/1753514/


All Articles