You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Elena Sayapina (JIRA)" <ji...@apache.org> on 2007/03/22 11:06:32 UTC

[jira] Created: (HARMONY-3467) Eclipse long-running scenario

Eclipse long-running scenario
-----------------------------

                 Key: HARMONY-3467
                 URL: https://issues.apache.org/jira/browse/HARMONY-3467
             Project: Harmony
          Issue Type: Test
          Components: build - test - ci
            Reporter: Elena Sayapina
            Priority: Minor
         Attachments: scenario.zip

Attached archive contains automated Eclipse 3.2.1 long-running scenario test.

The scenario basically means creation, build and debug real-life application in Eclipse.
Purpose of this test scenario is make sure that JRE implementation under test (Harmony primarily) 
is able to  run Eclipse while a user performs common developer tasks in it.

For more information see README.txt from archive.

Scenario.zip contains 'standalone'  scenario run - buildtest patch for regularly scenario run under Cruise Control will follow.



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


[jira] Commented: (HARMONY-3467) [testing] Eclipse long-running scenario

Posted by "Stepan Mishura (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HARMONY-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12504281 ] 

Stepan Mishura commented on HARMONY-3467:
-----------------------------------------

Aleksei - the patch was applied to BTI branch 2.0 at r546907. 
Please check that the patch was applied as you expected. 

> [testing] Eclipse long-running scenario
> ---------------------------------------
>
>                 Key: HARMONY-3467
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3467
>             Project: Harmony
>          Issue Type: Test
>          Components: build - test - ci
>            Reporter: Elena Sayapina
>            Assignee: Stepan Mishura
>            Priority: Minor
>         Attachments: ega_BT2.patch, scenario.zip, scenarioBT2.zip, scenarioBT2.zip, scenarioBT2.zip
>
>
> Attached archive contains automated Eclipse 3.2.1 long-running scenario test.
> The scenario basically means creation, build and debug real-life application in Eclipse.
> Purpose of this test scenario is make sure that JRE implementation under test (Harmony primarily) 
> is able to  run Eclipse while a user performs common developer tasks in it.
> For more information see README.txt from archive.
> Scenario.zip contains 'standalone'  scenario run - buildtest patch for regularly scenario run under Cruise Control will follow.

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


[jira] Updated: (HARMONY-3467) Eclipse long-running scenario

Posted by "Elena Sayapina (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HARMONY-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Elena Sayapina updated HARMONY-3467:
------------------------------------

    Attachment: scenarioBT2.zip

Attached archive scenarioBT2.zip contains scripts for executing Eclipse long-running scenario within Build Test Infrastructure 2.0 (http://issues.apache.org/jira/browse/HARMONY-3501). 
Note that running the scenario in continuous mode depends on Harmony HDK build.
Please, see ./tests/README.txt for more details.


> Eclipse long-running scenario
> -----------------------------
>
>                 Key: HARMONY-3467
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3467
>             Project: Harmony
>          Issue Type: Test
>          Components: build - test - ci
>            Reporter: Elena Sayapina
>            Priority: Minor
>         Attachments: scenario.zip, scenarioBT2.zip
>
>
> Attached archive contains automated Eclipse 3.2.1 long-running scenario test.
> The scenario basically means creation, build and debug real-life application in Eclipse.
> Purpose of this test scenario is make sure that JRE implementation under test (Harmony primarily) 
> is able to  run Eclipse while a user performs common developer tasks in it.
> For more information see README.txt from archive.
> Scenario.zip contains 'standalone'  scenario run - buildtest patch for regularly scenario run under Cruise Control will follow.

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


[jira] Assigned: (HARMONY-3467) [testing] Eclipse long-running scenario

Posted by "Stepan Mishura (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HARMONY-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stepan Mishura reassigned HARMONY-3467:
---------------------------------------

    Assignee: Stepan Mishura

> [testing] Eclipse long-running scenario
> ---------------------------------------
>
>                 Key: HARMONY-3467
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3467
>             Project: Harmony
>          Issue Type: Test
>          Components: build - test - ci
>            Reporter: Elena Sayapina
>            Assignee: Stepan Mishura
>            Priority: Minor
>         Attachments: scenario.zip, scenarioBT2.zip, scenarioBT2.zip, scenarioBT2.zip
>
>
> Attached archive contains automated Eclipse 3.2.1 long-running scenario test.
> The scenario basically means creation, build and debug real-life application in Eclipse.
> Purpose of this test scenario is make sure that JRE implementation under test (Harmony primarily) 
> is able to  run Eclipse while a user performs common developer tasks in it.
> For more information see README.txt from archive.
> Scenario.zip contains 'standalone'  scenario run - buildtest patch for regularly scenario run under Cruise Control will follow.

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


[jira] Resolved: (HARMONY-3467) [testing] Eclipse long-running scenario

Posted by "Stepan Mishura (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HARMONY-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stepan Mishura resolved HARMONY-3467.
-------------------------------------

    Resolution: Fixed

Thanks Elena, Aleksei - the patch was applied to BTI branch 2.0 at r543394. 
Please check that the patch was applied as you expected.

> [testing] Eclipse long-running scenario
> ---------------------------------------
>
>                 Key: HARMONY-3467
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3467
>             Project: Harmony
>          Issue Type: Test
>          Components: build - test - ci
>            Reporter: Elena Sayapina
>            Assignee: Stepan Mishura
>            Priority: Minor
>         Attachments: scenario.zip, scenarioBT2.zip, scenarioBT2.zip, scenarioBT2.zip
>
>
> Attached archive contains automated Eclipse 3.2.1 long-running scenario test.
> The scenario basically means creation, build and debug real-life application in Eclipse.
> Purpose of this test scenario is make sure that JRE implementation under test (Harmony primarily) 
> is able to  run Eclipse while a user performs common developer tasks in it.
> For more information see README.txt from archive.
> Scenario.zip contains 'standalone'  scenario run - buildtest patch for regularly scenario run under Cruise Control will follow.

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


[jira] Closed: (HARMONY-3467) [testing] Eclipse long-running scenario

Posted by "Stepan Mishura (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HARMONY-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stepan Mishura closed HARMONY-3467.
-----------------------------------


Verified by Aleksei.

> [testing] Eclipse long-running scenario
> ---------------------------------------
>
>                 Key: HARMONY-3467
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3467
>             Project: Harmony
>          Issue Type: Test
>          Components: build - test - ci
>            Reporter: Elena Sayapina
>            Assignee: Stepan Mishura
>            Priority: Minor
>         Attachments: ega_BT2.patch, scenario.zip, scenarioBT2.zip, scenarioBT2.zip, scenarioBT2.zip
>
>
> Attached archive contains automated Eclipse 3.2.1 long-running scenario test.
> The scenario basically means creation, build and debug real-life application in Eclipse.
> Purpose of this test scenario is make sure that JRE implementation under test (Harmony primarily) 
> is able to  run Eclipse while a user performs common developer tasks in it.
> For more information see README.txt from archive.
> Scenario.zip contains 'standalone'  scenario run - buildtest patch for regularly scenario run under Cruise Control will follow.

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


[jira] Updated: (HARMONY-3467) [testing] Eclipse long-running scenario

Posted by "Elena Sayapina (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HARMONY-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Elena Sayapina updated HARMONY-3467:
------------------------------------

    Summary: [testing] Eclipse long-running scenario  (was: Eclipse long-running scenario)

> [testing] Eclipse long-running scenario
> ---------------------------------------
>
>                 Key: HARMONY-3467
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3467
>             Project: Harmony
>          Issue Type: Test
>          Components: build - test - ci
>            Reporter: Elena Sayapina
>            Priority: Minor
>         Attachments: scenario.zip, scenarioBT2.zip
>
>
> Attached archive contains automated Eclipse 3.2.1 long-running scenario test.
> The scenario basically means creation, build and debug real-life application in Eclipse.
> Purpose of this test scenario is make sure that JRE implementation under test (Harmony primarily) 
> is able to  run Eclipse while a user performs common developer tasks in it.
> For more information see README.txt from archive.
> Scenario.zip contains 'standalone'  scenario run - buildtest patch for regularly scenario run under Cruise Control will follow.

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


[jira] Commented: (HARMONY-3467) [testing] Eclipse long-running scenario

Posted by "Ivaschenko, Aleksei V (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/HARMONY-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12504283 ] 

Ivaschenko, Aleksei V commented on HARMONY-3467:
------------------------------------------------

Thanks Stepan, the patch applied as expected.

> [testing] Eclipse long-running scenario
> ---------------------------------------
>
>                 Key: HARMONY-3467
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3467
>             Project: Harmony
>          Issue Type: Test
>          Components: build - test - ci
>            Reporter: Elena Sayapina
>            Assignee: Stepan Mishura
>            Priority: Minor
>         Attachments: ega_BT2.patch, scenario.zip, scenarioBT2.zip, scenarioBT2.zip, scenarioBT2.zip
>
>
> Attached archive contains automated Eclipse 3.2.1 long-running scenario test.
> The scenario basically means creation, build and debug real-life application in Eclipse.
> Purpose of this test scenario is make sure that JRE implementation under test (Harmony primarily) 
> is able to  run Eclipse while a user performs common developer tasks in it.
> For more information see README.txt from archive.
> Scenario.zip contains 'standalone'  scenario run - buildtest patch for regularly scenario run under Cruise Control will follow.

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


[jira] Updated: (HARMONY-3467) Eclipse long-running scenario

Posted by "Elena Sayapina (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HARMONY-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Elena Sayapina updated HARMONY-3467:
------------------------------------

    Attachment: scenario.zip

> Eclipse long-running scenario
> -----------------------------
>
>                 Key: HARMONY-3467
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3467
>             Project: Harmony
>          Issue Type: Test
>          Components: build - test - ci
>            Reporter: Elena Sayapina
>            Priority: Minor
>         Attachments: scenario.zip
>
>
> Attached archive contains automated Eclipse 3.2.1 long-running scenario test.
> The scenario basically means creation, build and debug real-life application in Eclipse.
> Purpose of this test scenario is make sure that JRE implementation under test (Harmony primarily) 
> is able to  run Eclipse while a user performs common developer tasks in it.
> For more information see README.txt from archive.
> Scenario.zip contains 'standalone'  scenario run - buildtest patch for regularly scenario run under Cruise Control will follow.

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


[jira] Updated: (HARMONY-3467) [testing] Eclipse long-running scenario

Posted by "Ivaschenko, Aleksei V (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HARMONY-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ivaschenko, Aleksei V updated HARMONY-3467:
-------------------------------------------

    Attachment: ega_BT2.patch

Hello,
I've created patch (ega_BT2.patch) which fixed EGA automation bug with updating scenario sources from SVN.


> [testing] Eclipse long-running scenario
> ---------------------------------------
>
>                 Key: HARMONY-3467
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3467
>             Project: Harmony
>          Issue Type: Test
>          Components: build - test - ci
>            Reporter: Elena Sayapina
>            Assignee: Stepan Mishura
>            Priority: Minor
>         Attachments: ega_BT2.patch, scenario.zip, scenarioBT2.zip, scenarioBT2.zip, scenarioBT2.zip
>
>
> Attached archive contains automated Eclipse 3.2.1 long-running scenario test.
> The scenario basically means creation, build and debug real-life application in Eclipse.
> Purpose of this test scenario is make sure that JRE implementation under test (Harmony primarily) 
> is able to  run Eclipse while a user performs common developer tasks in it.
> For more information see README.txt from archive.
> Scenario.zip contains 'standalone'  scenario run - buildtest patch for regularly scenario run under Cruise Control will follow.

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


[jira] Updated: (HARMONY-3467) [testing] Eclipse long-running scenario

Posted by "Ivaschenko, Aleksei V (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HARMONY-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ivaschenko, Aleksei V updated HARMONY-3467:
-------------------------------------------

    Attachment: scenarioBT2.zip

I've updated EGA scenario automation scripts according to latest BTI 2.0 requirements.

Tested on Windows ia32 and Linux ia32.


> [testing] Eclipse long-running scenario
> ---------------------------------------
>
>                 Key: HARMONY-3467
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3467
>             Project: Harmony
>          Issue Type: Test
>          Components: build - test - ci
>            Reporter: Elena Sayapina
>            Priority: Minor
>         Attachments: scenario.zip, scenarioBT2.zip, scenarioBT2.zip, scenarioBT2.zip
>
>
> Attached archive contains automated Eclipse 3.2.1 long-running scenario test.
> The scenario basically means creation, build and debug real-life application in Eclipse.
> Purpose of this test scenario is make sure that JRE implementation under test (Harmony primarily) 
> is able to  run Eclipse while a user performs common developer tasks in it.
> For more information see README.txt from archive.
> Scenario.zip contains 'standalone'  scenario run - buildtest patch for regularly scenario run under Cruise Control will follow.

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


[jira] Updated: (HARMONY-3467) [testing] Eclipse long-running scenario

Posted by "Elena Sayapina (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HARMONY-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Elena Sayapina updated HARMONY-3467:
------------------------------------

    Attachment: scenarioBT2.zip

Few updates to the archive scenarioBT2.zip:

1) Possibility to change maven version added to scenario automation.
2) Scenario script for Windows was updated to eliminate 2 stability issues.


> [testing] Eclipse long-running scenario
> ---------------------------------------
>
>                 Key: HARMONY-3467
>                 URL: https://issues.apache.org/jira/browse/HARMONY-3467
>             Project: Harmony
>          Issue Type: Test
>          Components: build - test - ci
>            Reporter: Elena Sayapina
>            Priority: Minor
>         Attachments: scenario.zip, scenarioBT2.zip, scenarioBT2.zip
>
>
> Attached archive contains automated Eclipse 3.2.1 long-running scenario test.
> The scenario basically means creation, build and debug real-life application in Eclipse.
> Purpose of this test scenario is make sure that JRE implementation under test (Harmony primarily) 
> is able to  run Eclipse while a user performs common developer tasks in it.
> For more information see README.txt from archive.
> Scenario.zip contains 'standalone'  scenario run - buildtest patch for regularly scenario run under Cruise Control will follow.

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