java.io.FileNotFoundException: /spare/bamboo/data/xml-data/build-dir/LW-NIGHTLY/limewire/testData/co m.limegroup.gnutella.xml.MetaFileManagerTest/settings/fileurns.cache (No such file or directory)

Atlassian JIRA | Sam Berlin | 10 years ago
  1. 0

    The XML produced by JUnit isn't parsed properly for some tests. We install an uncaughtExceptionHandler for multi-threaded tests, and forward the exceptions to TestResult object that was used to start the test. This allows multiple exceptions to happen in a single testmethod, and additional exceptions to happen before the test-proper begins and after all the tests finish. The errors outside the scope of a particular test are done by adding a new test to the suite called "LimeTestSuite - Before Test Errors" (or After Test Errors) and having that test add an error or failure to the test result object the suite is using. The XML this produces looks as follows: <testsuite errors="2" failures="0" name="com.limegroup.gnutella.xml.MetaFileManagerTest" tests="28" time="93.47"> <!-- properties --> <!-- the normal result... --> <testcase classname="com.limegroup.gnutella.xml.MetaFileManagerTest" name="testSensitiveDirectoryPredicate" time="0.035"></testcase> <!-- the abnormal result... --> <testcase classname="org.limewire.util.LimeTestSuite$1" name="LimeTestSuite - After Test Errors" time="0.02"> <error message="/spare/bamboo/data/xml-data/build-dir/LW-NIGHTLY/limewire/testData/com.limegroup.gnutella.xml.MetaFileManagerTest/settings/fileurns.cache (No such file or directory)" type="java.io.FileNotFoundException">java.io.FileNotFoundException: /spare/bamboo/data/xml-data/build-dir/LW-NIGHTLY/limewire/testData/co m.limegroup.gnutella.xml.MetaFileManagerTest/settings/fileurns.cache (No such file or directory) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.&lt;init&gt;(FileOutputStream.java:179) at java.io.FileOutputStream.&lt;init&gt;(FileOutputStream.java:131) at com.limegroup.gnutella.UrnCache.persistCache(UrnCache.java:323) at com.limegroup.gnutella.FileManager.save(FileManager.java:404) at com.limegroup.gnutella.xml.MetaFileManager.save(MetaFileManager.java:313) at com.limegroup.gnutella.xml.MetaFileManager$Saver.run(MetaFileManager.java:466) at org.limewire.concurrent.SimpleTimer$1.run(SimpleTimer.java:70) at org.limewire.concurrent.SimpleTimer$MyTimerTask.run(SimpleTimer.java:125) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) </error> </testcase> </testsuite> These abnormal errors are showing up in Bamboo as being from 'LimeTestSuite$1', so it looks like Bamboo is grouping by the classname attribute of the testcase element, whereas most other junit reporters group by the classname of the encompassing suite element. Without this fix, it's impossible to tell from looking at the Bamboo reports where one of these errors occurred.

    Atlassian JIRA | 10 years ago | Sam Berlin
    java.io.FileNotFoundException: /spare/bamboo/data/xml-data/build-dir/LW-NIGHTLY/limewire/testData/co m.limegroup.gnutella.xml.MetaFileManagerTest/settings/fileurns.cache (No such file or directory)
  2. 0

    The XML produced by JUnit isn't parsed properly for some tests. We install an uncaughtExceptionHandler for multi-threaded tests, and forward the exceptions to TestResult object that was used to start the test. This allows multiple exceptions to happen in a single testmethod, and additional exceptions to happen before the test-proper begins and after all the tests finish. The errors outside the scope of a particular test are done by adding a new test to the suite called "LimeTestSuite - Before Test Errors" (or After Test Errors) and having that test add an error or failure to the test result object the suite is using. The XML this produces looks as follows: <testsuite errors="2" failures="0" name="com.limegroup.gnutella.xml.MetaFileManagerTest" tests="28" time="93.47"> <!-- properties --> <!-- the normal result... --> <testcase classname="com.limegroup.gnutella.xml.MetaFileManagerTest" name="testSensitiveDirectoryPredicate" time="0.035"></testcase> <!-- the abnormal result... --> <testcase classname="org.limewire.util.LimeTestSuite$1" name="LimeTestSuite - After Test Errors" time="0.02"> <error message="/spare/bamboo/data/xml-data/build-dir/LW-NIGHTLY/limewire/testData/com.limegroup.gnutella.xml.MetaFileManagerTest/settings/fileurns.cache (No such file or directory)" type="java.io.FileNotFoundException">java.io.FileNotFoundException: /spare/bamboo/data/xml-data/build-dir/LW-NIGHTLY/limewire/testData/co m.limegroup.gnutella.xml.MetaFileManagerTest/settings/fileurns.cache (No such file or directory) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.&lt;init&gt;(FileOutputStream.java:179) at java.io.FileOutputStream.&lt;init&gt;(FileOutputStream.java:131) at com.limegroup.gnutella.UrnCache.persistCache(UrnCache.java:323) at com.limegroup.gnutella.FileManager.save(FileManager.java:404) at com.limegroup.gnutella.xml.MetaFileManager.save(MetaFileManager.java:313) at com.limegroup.gnutella.xml.MetaFileManager$Saver.run(MetaFileManager.java:466) at org.limewire.concurrent.SimpleTimer$1.run(SimpleTimer.java:70) at org.limewire.concurrent.SimpleTimer$MyTimerTask.run(SimpleTimer.java:125) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) </error> </testcase> </testsuite> These abnormal errors are showing up in Bamboo as being from 'LimeTestSuite$1', so it looks like Bamboo is grouping by the classname attribute of the testcase element, whereas most other junit reporters group by the classname of the encompassing suite element. Without this fix, it's impossible to tell from looking at the Bamboo reports where one of these errors occurred.

    Atlassian JIRA | 10 years ago | Sam Berlin
    java.io.FileNotFoundException: /spare/bamboo/data/xml-data/build-dir/LW-NIGHTLY/limewire/testData/co m.limegroup.gnutella.xml.MetaFileManagerTest/settings/fileurns.cache (No such file or directory)
  3. 0

    wso2 esb deploy failed on windows

    Stack Overflow | 2 years ago | Enforcer
    java.io.FileNotFoundException: C:\Java\WSO2ES~1.1\bin\..\tmp\carbonappsuploads\first-esb_1.0.0.car (Запрошенную операцию нельзя выполнить для файла с открытой пользователем сопоставленной секцией)
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Localized Windows cause save problems for Gridworks

    GitHub | 4 years ago | tfmorris
    java.io.FileNotFoundException: C:\Users\???? \AppData\Local\Gridworks\2206489941407.project\history\1273396606971.change .zip (Системе не удается найти указанный путь)
  6. 0

    Crash at Mojang screen

    GitHub | 3 years ago | crosskin
    java.io.FileNotFoundException: C:\Users\JT\Desktop\ATLauncher\Instances\CrackPack\config\CodeChickenCore.cfg (The requested operation cannot be performed on a file with a user-mapped section open)

  1. iridic 1 times, last 2 weeks ago
  2. tererecool 24 times, last 2 months ago
  3. pbabcsany 2 times, last 5 months ago
3 unregistered visitors
Not finding the right solution?
Take a tour to get the most out of Samebug.

Tired of useless tips?

Automated exception search integrated into your IDE

Root Cause Analysis

  1. java.io.FileNotFoundException

    /spare/bamboo/data/xml-data/build-dir/LW-NIGHTLY/limewire/testData/co m.limegroup.gnutella.xml.MetaFileManagerTest/settings/fileurns.cache (No such file or directory)

    at java.io.FileOutputStream.open()
  2. Java RT
    FileOutputStream.open
    1. java.io.FileOutputStream.open(Native Method)
    1 frame