You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Martin Häusler (JIRA)" <ji...@apache.org> on 2016/01/24 15:01:39 UTC
[jira] [Comment Edited] (TINKERPOP-1041) StructureStandardTestSuite
has file I/O issues on Windows
[ https://issues.apache.org/jira/browse/TINKERPOP-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15114315#comment-15114315 ]
Martin Häusler edited comment on TINKERPOP-1041 at 1/24/16 2:00 PM:
--------------------------------------------------------------------
Hi everyone, I'm sorry for the long delay.
I'm using the following setup:
- Windows 10, 64bit
- Java 8, jdk1.8.0_66, 64bit
- Spring Tool Suite 3.7.1. Release, based on Eclipse Mars 4.5.1
- TinkerPop Version: 3.1.0-Incubating (I also tried the latest snapshot once, but that gave me even more I/O errors)
The tests that currently fail for me due to I/O errors are:
- {{org.apache.tinkerpop.gremlin.structure.io.IoGraphTest}}, method = shouldReadWriteModernToFileWithHelpers, specific = graphml
- {{org.apache.tinkerpop.gremlin.structure.io.IoGraphTest}}, method = shouldReadWriteClassicToFileWithHelpers, specific = graphml
- {{org.apache.tinkerpop.gremlin.structure.io.IoGraphTest}}, method = shouldReadWriteModernToFileWithHelpers, specific = graphson
- {{org.apache.tinkerpop.gremlin.structure.io.IoGraphTest}}, method = shouldReadWriteClassicToFileWithHelpers, specific = graphson
- {{org.apache.tinkerpop.gremlin.structure.io.IoGraphTest}}, method = shouldReadWriteModernToFileWithHelpers, specific = gryo
- {{org.apache.tinkerpop.gremlin.structure.io.IoGraphTest}}, method = shouldReadWriteClassicToFileWithHelpers, specific = gryo
The list above reflects exactly my current {{@Graph.OptOut}} annotations, because they give me the IOException in the ticket description when I try to run them from within Eclipse. I never tried to run them from the command prompt, but it should not make any difference.
was (Author: martin_haeusler):
Hi everyone, I'm sorry for the long delay.
I'm using the following setup:
- Windows 10, 64bit
- Java 8, jdk1.8.0_66, 64bit
- Spring Tool Suite 3.7.1. Release, based on Eclipse Mars 4.5.1
- TinkerPop Version: 3.1.0-Incubating (I also tried the latest snapshot once, but that gave me even more I/O errors)
The tests that currently fail for me due to I/O errors are:
- {{org.apache.tinkerpop.gremlin.structure.io.IoGraphTest}}, method = shouldReadWriteModernToFileWithHelpers, specific = graphml
- {{org.apache.tinkerpop.gremlin.structure.io.IoGraphTest}}, method = shouldReadWriteClassicToFileWithHelpers, specific = graphml
- {{org.apache.tinkerpop.gremlin.structure.io.IoGraphTest}}, method = shouldReadWriteModernToFileWithHelpers, specific = graphson
- {{org.apache.tinkerpop.gremlin.structure.io.IoGraphTest}}, method = shouldReadWriteClassicToFileWithHelpers, specific = graphson
- {{org.apache.tinkerpop.gremlin.structure.io.IoGraphTest}}, method = shouldReadWriteModernToFileWithHelpers, specific = gryo
- {{org.apache.tinkerpop.gremlin.structure.io.IoGraphTest}}, method = shouldReadWriteClassicToFileWithHelpers, specific = gryo
- {{org.apache.tinkerpop.gremlin.structure.io.IoGraphTest}}, method = shouldReadWriteClassic, specific = gryo
- {{org.apache.tinkerpop.gremlin.structure.io.IoGraphTest}}, method = shouldReadWriteModern, specific = gryo
- {{org.apache.tinkerpop.gremlin.structure.io.IoGraphTest}}, method = shouldMigrateClassicGraph, specific = gryo
- {{org.apache.tinkerpop.gremlin.structure.io.IoGraphTest}}, method = shouldMigrateModernGraph, specific = gryo
The list above reflects exactly my current {{@Graph.OptOut}} annotations, because they give me the IOException in the ticket description when I try to run them from within Eclipse. I never tried to run them from the command prompt, but it should not make any difference.
> StructureStandardTestSuite has file I/O issues on Windows
> ---------------------------------------------------------
>
> Key: TINKERPOP-1041
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1041
> Project: TinkerPop
> Issue Type: Bug
> Components: test-suite
> Affects Versions: 3.0.2-incubating
> Environment: Windows 10, Java 8, TinkerPop version "3.0.2-incubating"
> Reporter: Martin Häusler
> Assignee: Jason Plurad
> Fix For: 3.1.1-incubating
>
> Original Estimate: 3h
> Remaining Estimate: 3h
>
> Most of the tests in StructureStandardTestSuite/IoGraphTest cause an unexpected java.io.IOException. The stack trace looks like this:
> {panel:title=Stack Trace}
> java.io.IOException: The the file name, directory name or volume label syntax is incorrect.
> at java.io.WinNTFileSystem.createFileExclusively(Native Method)
> at java.io.File.createTempFile(Unknown Source)
> at org.apache.tinkerpop.gremlin.TestHelper.generateTempFile(TestHelper.java:74)
> at org.apache.tinkerpop.gremlin.structure.io.IoGraphTest.shouldReadWriteModernToFileWithHelpers(IoGraphTest.java:164)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> {panel}
> I'm running the test suite from Eclipse under Java 8, on a Windows 10 x64 machine. The dependencies in my project are managed with gradle. Investigating the offinsive line (org.apache.tinkerpop.gremlin.TestHelper.java@74) in the debugger reveals the following parameters of "File.createTempFile(...)":
> {noformat}
> fileName = "shouldReadWriteModernToFileWithHelpers[graphml]"
> fileNameSuffix = ".xml"
> path = "file:\D:\guh\caches\modules-2\files-2.1\org.apache.tinkerpop\gremlin-test\3.0.2-incubating\345ec87b74923b76374111f2e4040d4d105f256\temp"
> {noformat}
> The offensive part is the "path" variable, because it contains the prefix "file:\". I tried the same thing in a dedicated JUnit test without the prefix and it works fine.
> I would be very happy to see this issue fixed, as this considerably reduces the amount of tests in the suite that I can run against my graph implementation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)