Builds with surefire on Windows OS prevent deletion of files with output from tests. These files are created when maven.test.redirectTestOutputToFile is activated.
There is a known problem with memory mapped io on windows os:
"[...] Windows does not allow a mapped file to be deleted [...]"
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4715154
hudson.tasks.junit.SuiteResult uses memory mapped io to read the redirected test output.
I have attached a patch (noMemoryMappedIoForWindows-V2.patch), that reactivates an older implementation without memory mapped io on windows. I think this patch is only a temporary solution, because it reintroduces a memory problem. This problem was solved with memory mapped io.
- is related to
-
JENKINS-15382 Memory exhaustion parsing large test stdio from Surefire
-
- Closed
-
[JENKINS-16497] Builds with surefire on Windows OS prevent deletion of files with output from tests.
Description |
Original:
Builds with surefire reports on Windows OS prevents deletion of files with output from tests. These files are created when [maven.test.redirectTestOutputToFile|http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#redirectTestOutputToFile] is activated. There is known problem with memory mapped io on windows os. "[...] Windows does not allow a mapped file to be deleted [...]" http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4715154 hudson.tasks.junit.SuiteResult uses memory mapped io to read the redirected test output. I have attached a patch, that reactivates an older implementation without memory mapped io on windows os. |
New:
Builds with surefire reports on Windows OS prevents deletion of files with output from tests. These files are created when [maven.test.redirectTestOutputToFile|http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#redirectTestOutputToFile] is activated. There is a known problem with memory mapped io on windows os. "[...] Windows does not allow a mapped file to be deleted [...]" http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4715154 hudson.tasks.junit.SuiteResult uses memory mapped io to read the redirected test output. I have attached a patch, that reactivates an older implementation without memory mapped io on windows os. |
Description |
Original:
Builds with surefire reports on Windows OS prevents deletion of files with output from tests. These files are created when [maven.test.redirectTestOutputToFile|http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#redirectTestOutputToFile] is activated. There is a known problem with memory mapped io on windows os. "[...] Windows does not allow a mapped file to be deleted [...]" http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4715154 hudson.tasks.junit.SuiteResult uses memory mapped io to read the redirected test output. I have attached a patch, that reactivates an older implementation without memory mapped io on windows os. |
New:
Builds with surefire reports on Windows OS prevents deletion of files with output from tests. These files are created when [maven.test.redirectTestOutputToFile|http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#redirectTestOutputToFile] is activated. There is a known problem with memory mapped io on windows os: "[...] Windows does not allow a mapped file to be deleted [...]" http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4715154 _hudson.tasks.junit.SuiteResult_ uses memory mapped io to read the redirected test output. I have attached a patch, that reactivates an older implementation without memory mapped io on windows os. |
Summary | Original: Builds with surefire reports on Windows OS prevents deletion of files with output from tests. | New: Builds with surefire reports on Windows OS prevent deletion of files with output from tests. |
Description |
Original:
Builds with surefire reports on Windows OS prevents deletion of files with output from tests. These files are created when [maven.test.redirectTestOutputToFile|http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#redirectTestOutputToFile] is activated. There is a known problem with memory mapped io on windows os: "[...] Windows does not allow a mapped file to be deleted [...]" http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4715154 _hudson.tasks.junit.SuiteResult_ uses memory mapped io to read the redirected test output. I have attached a patch, that reactivates an older implementation without memory mapped io on windows os. |
New:
Builds with surefire reports on Windows OS prevent deletion of files with output from tests. These files are created when [maven.test.redirectTestOutputToFile|http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#redirectTestOutputToFile] is activated. There is a known problem with memory mapped io on windows os: "[...] Windows does not allow a mapped file to be deleted [...]" http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4715154 _hudson.tasks.junit.SuiteResult_ uses memory mapped io to read the redirected test output. I have attached a patch, that reactivates an older implementation without memory mapped io on windows os. |
Description |
Original:
Builds with surefire reports on Windows OS prevent deletion of files with output from tests. These files are created when [maven.test.redirectTestOutputToFile|http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#redirectTestOutputToFile] is activated. There is a known problem with memory mapped io on windows os: "[...] Windows does not allow a mapped file to be deleted [...]" http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4715154 _hudson.tasks.junit.SuiteResult_ uses memory mapped io to read the redirected test output. I have attached a patch, that reactivates an older implementation without memory mapped io on windows os. |
New:
Builds with surefire reports on Windows OS prevent deletion of files with output from tests. These files are created when [maven.test.redirectTestOutputToFile|http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#redirectTestOutputToFile] is activated. There is a known problem with memory mapped io on windows os: "[...] Windows does not allow a mapped file to be deleted [...]" http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4715154 _hudson.tasks.junit.SuiteResult_ uses memory mapped io to read the redirected test output. I have attached a patch, that reactivates an older implementation without memory mapped io on windows os. Memory mapped io was introduced with _fe934aac007a20c43e803de61ef8b6cf28c4434f_. |
Attachment | New: noMemoryMappedIoForWindows.patch [ 23110 ] |
Attachment | New: noMemoryMappedIoForWindows-V2.patch [ 23111 ] |
Description |
Original:
Builds with surefire reports on Windows OS prevent deletion of files with output from tests. These files are created when [maven.test.redirectTestOutputToFile|http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#redirectTestOutputToFile] is activated. There is a known problem with memory mapped io on windows os: "[...] Windows does not allow a mapped file to be deleted [...]" http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4715154 _hudson.tasks.junit.SuiteResult_ uses memory mapped io to read the redirected test output. I have attached a patch, that reactivates an older implementation without memory mapped io on windows os. Memory mapped io was introduced with _fe934aac007a20c43e803de61ef8b6cf28c4434f_. |
New:
Builds with surefire reports on Windows OS prevent deletion of files with output from tests. These files are created when [maven.test.redirectTestOutputToFile|http://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#redirectTestOutputToFile] is activated. There is a known problem with memory mapped io on windows os: "[...] Windows does not allow a mapped file to be deleted [...]" http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4715154 _hudson.tasks.junit.SuiteResult_ uses memory mapped io to read the redirected test output. I have attached a patch ([^noMemoryMappedIoForWindows-V2.patch]), that reactivates an older implementation without memory mapped io on windows os. Memory mapped io was introduced with _fe934aac007a20c43e803de61ef8b6cf28c4434f_. |
Please ignore/delete the two patch files with the name noMemoryMappedIoForWindows.patch, they are flawed.