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 Wed, 19 Dec 2007 13:16:43 GMT

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

Vladimir Beliaev commented on HARMONY-5324:

Thanks, Ilya.

These tests normally passed during CC run, so we can't put it to EFL just for fun...

If you know the exat name of directory which is created by coreresources on Linux (/tmp/dirs
?) then I can add a check to tests/eut/build.xml before this suite run that such a directory
does not exist or try to remove it... 

Please also write if Windows is affacted. It would be right to show the issue in test sources
(file name, line) and file the related bug to Eclipse.org bugzilla.

> [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