harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Beliaev (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-5324) [buildtest][eut] Several coreresources tests ignore java.io.tmpdir property
Date Thu, 27 Dec 2007 12:59:44 GMT

    [ https://issues.apache.org/jira/browse/HARMONY-5324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12554566

Vladimir Beliaev commented on HARMONY-5324:

During a work on HARMONY-5303 (coreresources hang) I did not get any mess in /tmp directory
after my runs which were done with java.io.tmpdir redefined.

Also I've double checked org.eclipse.core.tests.resources_3.3.0.v20070510 sources, just one
class directly accesses tmp directory like:

      ./org/eclipse/core/tests/resources/IPathVariableTest.java:              IPath pathTwo
= new Path("/tmp/backup");

still this class tests does not create or do anyything else with these tmp directories. Instread
they test so called IPathVariableManager which is not supposed to work with real file system
(if I get it correctly), so the values like "/tmp/backup" are just fine.

I vote to close this bug as INVALID.

Vladimir Beliaev

> [buildtest][eut] Several coreresources tests ignore java.io.tmpdir property
> ---------------------------------------------------------------------------
>                 Key: HARMONY-5324
>                 URL: https://issues.apache.org/jira/browse/HARMONY-5324
>             Project: Harmony
>          Issue Type: Bug
>          Components: build - test - ci
>         Environment: Linux
>            Reporter: Ilya Berezhniuk
>            Priority: Minor
> The tests listed below (EUT 3.3 coreresources suite) ignore java.io.tmpdir property passed
to tested VM.
> On Linux these tests create files/dirs in /tmp dir. As /tmp has sticky bit, all other
users trying to run EUT on the same host get failures because they cannot access/remove these
files/dirs created by another user.
> The tests are the following:
> ---------------------
> org.eclipse.core.tests.internal.watson.TreeFlatteningTest.test0
> org.eclipse.core.tests.resources.regression.PR_1GH2B0N_Test.test_1GH2B0N
> org.eclipse.core.tests.resources.session.TestSave:test2
> org.eclipse.core.tests.resources.session.Test1G1N9GZ:test2
> org.eclipse.core.tests.resources.session.TestCloseNoSave:test2
> org.eclipse.core.tests.resources.session.TestMultiSnap:test2
> org.eclipse.core.tests.resources.session.TestSaveCreateProject:test2
> org.eclipse.core.tests.resources.session.TestSaveSnap:test2
> org.eclipse.core.tests.resources.session.TestSnapSaveSnap:test2
> org.eclipse.core.tests.resources.session.TestClosedProjectLocation.test1
> org.eclipse.core.tests.resources.session.TestClosedProjectLocation:test2
> org.eclipse.core.tests.resources.session.FindDeletedMembersTest:test4
> org.eclipse.core.tests.resources.session.FindDeletedMembersTest:test6
> org.eclipse.core.tests.resources.session.TestBug12575:test1
> org.eclipse.core.tests.resources.session.TestBug12575:test3
> org.eclipse.core.tests.resources.session.TestBug113943.test1
> org.eclipse.core.tests.resources.session.TestBug113943:test2
> org.eclipse.core.tests.resources.usecase.SnapshotTest:test2
> org.eclipse.core.tests.resources.usecase.SnapshotTest:test3
> org.eclipse.core.tests.resources.usecase.SnapshotTest:test5
> ---------------------
> I suggest adding these tests to exclude list because they are slightly incorrect and
can lead to unexpected failures in normal curcumstances.
> I did not check this problem on Windows; but I'm going to do so.

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

View raw message