You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Vladimir Beliaev (JIRA)" <ji...@apache.org> on 2007/08/01 12:26:53 UTC
[jira] Created: (HARMONY-4587) [buildtest][eut] Expected Failure
List for EUT3.3 on winx86
[buildtest][eut] Expected Failure List for EUT3.3 on winx86
-----------------------------------------------------------
Key: HARMONY-4587
URL: https://issues.apache.org/jira/browse/HARMONY-4587
Project: Harmony
Issue Type: Sub-task
Components: build - test - ci
Environment: Windows x86
Reporter: Vladimir Beliaev
One need to create an Expected Failure List file for EUT3.3 on Windows x86.
It consist in several parts:
1. refactor tests\eut\build.xml to distinguish EUT3.2 and EUT3.3 EFL-files. A set of eclipse bugs are fixed in Eclipse release 3.3, so EFL files for EUT3.2. and EUT3.3 will be different. I believe there should NOT be an "unification" like "one EFL contains failure list for both EUT versions". So it will be efl.eut32.* and efl.eut33 files set.
Also It is a good point to create the "shared" EFL files for os / arch... Right now the efl.linux.x86 = efl.windows.x86 and there will just few platform dependent failures after linux failure analysis (for EUT32) is done. So, the proposed EFL "architecture" is:
eut32.efl - shared EFL file for all arch / os
eut32.windows.efl - windows specific failures (arch independent)
eut32.windows.x86.efl - windows x86 specific failures
...
So while running on particular platform the EUT runner will concatenate shared and platform specific EFL files and get thr resulted EFL file.
2. make EUT3.3 winx86 failure analysis and create eut33.windows.x86.efl file. This part of task may be done just by putting all failed tests to this list with a comment "need to do a failure analysis" w/o JIRA posting. This should be done so because:
- there is a set of failures (including intermittent ones) which are also reproducible with RI Java (hot spot)
- there is a set of intermittent failures which are caused by "The GC did not provide gc_add_weak_root_set_entry()" message
- there is a set of failures with a minor contribution to pass rate (~ 0.1%)
Thanks
Vladimir Beliaev
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (HARMONY-4587) [buildtest][eut] Expected Failure
List for EUT3.3 on winx86
Posted by "Alexey Varlamov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Varlamov reassigned HARMONY-4587:
----------------------------------------
Assignee: Alexey Varlamov
> [buildtest][eut] Expected Failure List for EUT3.3 on winx86
> -----------------------------------------------------------
>
> Key: HARMONY-4587
> URL: https://issues.apache.org/jira/browse/HARMONY-4587
> Project: Harmony
> Issue Type: Sub-task
> Components: build - test - ci
> Environment: Windows x86
> Reporter: Vladimir Beliaev
> Assignee: Alexey Varlamov
> Attachments: HARMONY-4587-1-redo-EFL.patch, HARMONY-4587-2-rename-EFL.sh, HARMONY-4587-2-rename-EFL.sh, HARMONY-4587-3-eut33-efl.patch
>
>
> One need to create an Expected Failure List file for EUT3.3 on Windows x86.
> It consist in several parts:
> 1. refactor tests\eut\build.xml to distinguish EUT3.2 and EUT3.3 EFL-files. A set of eclipse bugs are fixed in Eclipse release 3.3, so EFL files for EUT3.2. and EUT3.3 will be different. I believe there should NOT be an "unification" like "one EFL contains failure list for both EUT versions". So it will be efl.eut32.* and efl.eut33 files set.
> Also It is a good point to create the "shared" EFL files for os / arch... Right now the efl.linux.x86 = efl.windows.x86 and there will just few platform dependent failures after linux failure analysis (for EUT32) is done. So, the proposed EFL "architecture" is:
> eut32.efl - shared EFL file for all arch / os
> eut32.windows.efl - windows specific failures (arch independent)
> eut32.windows.x86.efl - windows x86 specific failures
> ...
> So while running on particular platform the EUT runner will concatenate shared and platform specific EFL files and get thr resulted EFL file.
> 2. make EUT3.3 winx86 failure analysis and create eut33.windows.x86.efl file. This part of task may be done just by putting all failed tests to this list with a comment "need to do a failure analysis" w/o JIRA posting. This should be done so because:
> - there is a set of failures (including intermittent ones) which are also reproducible with RI Java (hot spot)
> - there is a set of intermittent failures which are caused by "The GC did not provide gc_add_weak_root_set_entry()" message
> - there is a set of failures with a minor contribution to pass rate (~ 0.1%)
> Thanks
> Vladimir Beliaev
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (HARMONY-4587) [buildtest][eut] Expected Failure
List for EUT3.3 on winx86
Posted by "Alexey Varlamov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Varlamov resolved HARMONY-4587.
--------------------------------------
Resolution: Fixed
Applied at r563457, thanks!
> [buildtest][eut] Expected Failure List for EUT3.3 on winx86
> -----------------------------------------------------------
>
> Key: HARMONY-4587
> URL: https://issues.apache.org/jira/browse/HARMONY-4587
> Project: Harmony
> Issue Type: Sub-task
> Components: build - test - ci
> Environment: Windows x86
> Reporter: Vladimir Beliaev
> Assignee: Alexey Varlamov
> Attachments: HARMONY-4587-1-redo-EFL.patch, HARMONY-4587-2-rename-EFL.sh, HARMONY-4587-2-rename-EFL.sh, HARMONY-4587-3-eut33-efl.patch
>
>
> One need to create an Expected Failure List file for EUT3.3 on Windows x86.
> It consist in several parts:
> 1. refactor tests\eut\build.xml to distinguish EUT3.2 and EUT3.3 EFL-files. A set of eclipse bugs are fixed in Eclipse release 3.3, so EFL files for EUT3.2. and EUT3.3 will be different. I believe there should NOT be an "unification" like "one EFL contains failure list for both EUT versions". So it will be efl.eut32.* and efl.eut33 files set.
> Also It is a good point to create the "shared" EFL files for os / arch... Right now the efl.linux.x86 = efl.windows.x86 and there will just few platform dependent failures after linux failure analysis (for EUT32) is done. So, the proposed EFL "architecture" is:
> eut32.efl - shared EFL file for all arch / os
> eut32.windows.efl - windows specific failures (arch independent)
> eut32.windows.x86.efl - windows x86 specific failures
> ...
> So while running on particular platform the EUT runner will concatenate shared and platform specific EFL files and get thr resulted EFL file.
> 2. make EUT3.3 winx86 failure analysis and create eut33.windows.x86.efl file. This part of task may be done just by putting all failed tests to this list with a comment "need to do a failure analysis" w/o JIRA posting. This should be done so because:
> - there is a set of failures (including intermittent ones) which are also reproducible with RI Java (hot spot)
> - there is a set of intermittent failures which are caused by "The GC did not provide gc_add_weak_root_set_entry()" message
> - there is a set of failures with a minor contribution to pass rate (~ 0.1%)
> Thanks
> Vladimir Beliaev
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HARMONY-4587) [buildtest][eut] Expected Failure
List for EUT3.3 on winx86
Posted by "Vladimir Beliaev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Beliaev updated HARMONY-4587:
--------------------------------------
Patch Info: [Patch Available]
> [buildtest][eut] Expected Failure List for EUT3.3 on winx86
> -----------------------------------------------------------
>
> Key: HARMONY-4587
> URL: https://issues.apache.org/jira/browse/HARMONY-4587
> Project: Harmony
> Issue Type: Sub-task
> Components: build - test - ci
> Environment: Windows x86
> Reporter: Vladimir Beliaev
> Attachments: HARMONY-4587-1-redo-EFL.patch, HARMONY-4587-2-rename-EFL.sh, HARMONY-4587-3-eut33-efl.patch
>
>
> One need to create an Expected Failure List file for EUT3.3 on Windows x86.
> It consist in several parts:
> 1. refactor tests\eut\build.xml to distinguish EUT3.2 and EUT3.3 EFL-files. A set of eclipse bugs are fixed in Eclipse release 3.3, so EFL files for EUT3.2. and EUT3.3 will be different. I believe there should NOT be an "unification" like "one EFL contains failure list for both EUT versions". So it will be efl.eut32.* and efl.eut33 files set.
> Also It is a good point to create the "shared" EFL files for os / arch... Right now the efl.linux.x86 = efl.windows.x86 and there will just few platform dependent failures after linux failure analysis (for EUT32) is done. So, the proposed EFL "architecture" is:
> eut32.efl - shared EFL file for all arch / os
> eut32.windows.efl - windows specific failures (arch independent)
> eut32.windows.x86.efl - windows x86 specific failures
> ...
> So while running on particular platform the EUT runner will concatenate shared and platform specific EFL files and get thr resulted EFL file.
> 2. make EUT3.3 winx86 failure analysis and create eut33.windows.x86.efl file. This part of task may be done just by putting all failed tests to this list with a comment "need to do a failure analysis" w/o JIRA posting. This should be done so because:
> - there is a set of failures (including intermittent ones) which are also reproducible with RI Java (hot spot)
> - there is a set of intermittent failures which are caused by "The GC did not provide gc_add_weak_root_set_entry()" message
> - there is a set of failures with a minor contribution to pass rate (~ 0.1%)
> Thanks
> Vladimir Beliaev
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HARMONY-4587) [buildtest][eut] Expected Failure
List for EUT3.3 on winx86
Posted by "Vladimir Beliaev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Beliaev updated HARMONY-4587:
--------------------------------------
Attachment: HARMONY-4587-2-rename-EFL.sh
Corrected script - "touch" eut33.efl before adding it...
> [buildtest][eut] Expected Failure List for EUT3.3 on winx86
> -----------------------------------------------------------
>
> Key: HARMONY-4587
> URL: https://issues.apache.org/jira/browse/HARMONY-4587
> Project: Harmony
> Issue Type: Sub-task
> Components: build - test - ci
> Environment: Windows x86
> Reporter: Vladimir Beliaev
> Attachments: HARMONY-4587-1-redo-EFL.patch, HARMONY-4587-2-rename-EFL.sh, HARMONY-4587-2-rename-EFL.sh, HARMONY-4587-3-eut33-efl.patch
>
>
> One need to create an Expected Failure List file for EUT3.3 on Windows x86.
> It consist in several parts:
> 1. refactor tests\eut\build.xml to distinguish EUT3.2 and EUT3.3 EFL-files. A set of eclipse bugs are fixed in Eclipse release 3.3, so EFL files for EUT3.2. and EUT3.3 will be different. I believe there should NOT be an "unification" like "one EFL contains failure list for both EUT versions". So it will be efl.eut32.* and efl.eut33 files set.
> Also It is a good point to create the "shared" EFL files for os / arch... Right now the efl.linux.x86 = efl.windows.x86 and there will just few platform dependent failures after linux failure analysis (for EUT32) is done. So, the proposed EFL "architecture" is:
> eut32.efl - shared EFL file for all arch / os
> eut32.windows.efl - windows specific failures (arch independent)
> eut32.windows.x86.efl - windows x86 specific failures
> ...
> So while running on particular platform the EUT runner will concatenate shared and platform specific EFL files and get thr resulted EFL file.
> 2. make EUT3.3 winx86 failure analysis and create eut33.windows.x86.efl file. This part of task may be done just by putting all failed tests to this list with a comment "need to do a failure analysis" w/o JIRA posting. This should be done so because:
> - there is a set of failures (including intermittent ones) which are also reproducible with RI Java (hot spot)
> - there is a set of intermittent failures which are caused by "The GC did not provide gc_add_weak_root_set_entry()" message
> - there is a set of failures with a minor contribution to pass rate (~ 0.1%)
> Thanks
> Vladimir Beliaev
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HARMONY-4587) [buildtest][eut] Expected Failure
List for EUT3.3 on winx86
Posted by "Vladimir Beliaev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Beliaev updated HARMONY-4587:
--------------------------------------
Attachment: HARMONY-4587-1-redo-EFL.patch
First patch for this JIRA (HARMONY-4587-1-redo-EFL.patch) - it changes a preparation of platform specfic ELF fie (and also renames tmp file efl.work to work.efl to recognize 'efl' extension).
Note:
- set of tagets went ot trash - it is just fine.
- there is no check for <something specific>.efl file availability - I've double check on winx86 - this check is not required for <concat> task, ant just prints the warning like:
[concat] File C:\tmp-vb\eut32\eut32.efl does not exist.
> [buildtest][eut] Expected Failure List for EUT3.3 on winx86
> -----------------------------------------------------------
>
> Key: HARMONY-4587
> URL: https://issues.apache.org/jira/browse/HARMONY-4587
> Project: Harmony
> Issue Type: Sub-task
> Components: build - test - ci
> Environment: Windows x86
> Reporter: Vladimir Beliaev
> Attachments: HARMONY-4587-1-redo-EFL.patch
>
>
> One need to create an Expected Failure List file for EUT3.3 on Windows x86.
> It consist in several parts:
> 1. refactor tests\eut\build.xml to distinguish EUT3.2 and EUT3.3 EFL-files. A set of eclipse bugs are fixed in Eclipse release 3.3, so EFL files for EUT3.2. and EUT3.3 will be different. I believe there should NOT be an "unification" like "one EFL contains failure list for both EUT versions". So it will be efl.eut32.* and efl.eut33 files set.
> Also It is a good point to create the "shared" EFL files for os / arch... Right now the efl.linux.x86 = efl.windows.x86 and there will just few platform dependent failures after linux failure analysis (for EUT32) is done. So, the proposed EFL "architecture" is:
> eut32.efl - shared EFL file for all arch / os
> eut32.windows.efl - windows specific failures (arch independent)
> eut32.windows.x86.efl - windows x86 specific failures
> ...
> So while running on particular platform the EUT runner will concatenate shared and platform specific EFL files and get thr resulted EFL file.
> 2. make EUT3.3 winx86 failure analysis and create eut33.windows.x86.efl file. This part of task may be done just by putting all failed tests to this list with a comment "need to do a failure analysis" w/o JIRA posting. This should be done so because:
> - there is a set of failures (including intermittent ones) which are also reproducible with RI Java (hot spot)
> - there is a set of intermittent failures which are caused by "The GC did not provide gc_add_weak_root_set_entry()" message
> - there is a set of failures with a minor contribution to pass rate (~ 0.1%)
> Thanks
> Vladimir Beliaev
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HARMONY-4587) [buildtest][eut] Expected Failure
List for EUT3.3 on winx86
Posted by "Vladimir Beliaev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Beliaev updated HARMONY-4587:
--------------------------------------
Attachment: HARMONY-4587-3-eut33-efl.patch
The final patch (HARMONY-4587-3-eut33-efl.patch) - eut33.efl file content.
Please note that:
1. with previous patch I've removed EFL file for Linux (the shared eut32.efl is to be used by system instead). This is done because for now efl.windows.x86 = efl.linux.x86, so separate failure analysis for linx86 is required.
The same is true for winx64 (the README says winx64 is enabled but this can't be a correct statement w/o platform specific EFL file available [which means the failure analysis is done]). As soon as linx86 and winx64 failure analysis is done the eut32.efl may be corrected and platform specific EFL files will be created.
2. same for eut33.efl file - it is used for winx86 run only. As soon as other platforms are enabled forr EUT3.3 with Harmony this file is corrected and platform specific files are created.
3. the content of eut33.efl may be corrected later based on failure analysis of the run on laters Harmony (the GC-related corrections are in line, new bytecode verifier is temporarily turned off)...
Thanks
Vladimir Beliaev
> [buildtest][eut] Expected Failure List for EUT3.3 on winx86
> -----------------------------------------------------------
>
> Key: HARMONY-4587
> URL: https://issues.apache.org/jira/browse/HARMONY-4587
> Project: Harmony
> Issue Type: Sub-task
> Components: build - test - ci
> Environment: Windows x86
> Reporter: Vladimir Beliaev
> Attachments: HARMONY-4587-1-redo-EFL.patch, HARMONY-4587-2-rename-EFL.sh, HARMONY-4587-3-eut33-efl.patch
>
>
> One need to create an Expected Failure List file for EUT3.3 on Windows x86.
> It consist in several parts:
> 1. refactor tests\eut\build.xml to distinguish EUT3.2 and EUT3.3 EFL-files. A set of eclipse bugs are fixed in Eclipse release 3.3, so EFL files for EUT3.2. and EUT3.3 will be different. I believe there should NOT be an "unification" like "one EFL contains failure list for both EUT versions". So it will be efl.eut32.* and efl.eut33 files set.
> Also It is a good point to create the "shared" EFL files for os / arch... Right now the efl.linux.x86 = efl.windows.x86 and there will just few platform dependent failures after linux failure analysis (for EUT32) is done. So, the proposed EFL "architecture" is:
> eut32.efl - shared EFL file for all arch / os
> eut32.windows.efl - windows specific failures (arch independent)
> eut32.windows.x86.efl - windows x86 specific failures
> ...
> So while running on particular platform the EUT runner will concatenate shared and platform specific EFL files and get thr resulted EFL file.
> 2. make EUT3.3 winx86 failure analysis and create eut33.windows.x86.efl file. This part of task may be done just by putting all failed tests to this list with a comment "need to do a failure analysis" w/o JIRA posting. This should be done so because:
> - there is a set of failures (including intermittent ones) which are also reproducible with RI Java (hot spot)
> - there is a set of intermittent failures which are caused by "The GC did not provide gc_add_weak_root_set_entry()" message
> - there is a set of failures with a minor contribution to pass rate (~ 0.1%)
> Thanks
> Vladimir Beliaev
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (HARMONY-4587) [buildtest][eut] Expected Failure
List for EUT3.3 on winx86
Posted by "Vladimir Beliaev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Beliaev updated HARMONY-4587:
--------------------------------------
Attachment: HARMONY-4587-2-rename-EFL.sh
Next "patch" (HARMONY-4587-2-rename-EFL.sh) is a simple set of 'svn' command to update existing EFL files to new scheme & add eut33.efl file.
> [buildtest][eut] Expected Failure List for EUT3.3 on winx86
> -----------------------------------------------------------
>
> Key: HARMONY-4587
> URL: https://issues.apache.org/jira/browse/HARMONY-4587
> Project: Harmony
> Issue Type: Sub-task
> Components: build - test - ci
> Environment: Windows x86
> Reporter: Vladimir Beliaev
> Attachments: HARMONY-4587-1-redo-EFL.patch, HARMONY-4587-2-rename-EFL.sh
>
>
> One need to create an Expected Failure List file for EUT3.3 on Windows x86.
> It consist in several parts:
> 1. refactor tests\eut\build.xml to distinguish EUT3.2 and EUT3.3 EFL-files. A set of eclipse bugs are fixed in Eclipse release 3.3, so EFL files for EUT3.2. and EUT3.3 will be different. I believe there should NOT be an "unification" like "one EFL contains failure list for both EUT versions". So it will be efl.eut32.* and efl.eut33 files set.
> Also It is a good point to create the "shared" EFL files for os / arch... Right now the efl.linux.x86 = efl.windows.x86 and there will just few platform dependent failures after linux failure analysis (for EUT32) is done. So, the proposed EFL "architecture" is:
> eut32.efl - shared EFL file for all arch / os
> eut32.windows.efl - windows specific failures (arch independent)
> eut32.windows.x86.efl - windows x86 specific failures
> ...
> So while running on particular platform the EUT runner will concatenate shared and platform specific EFL files and get thr resulted EFL file.
> 2. make EUT3.3 winx86 failure analysis and create eut33.windows.x86.efl file. This part of task may be done just by putting all failed tests to this list with a comment "need to do a failure analysis" w/o JIRA posting. This should be done so because:
> - there is a set of failures (including intermittent ones) which are also reproducible with RI Java (hot spot)
> - there is a set of intermittent failures which are caused by "The GC did not provide gc_add_weak_root_set_entry()" message
> - there is a set of failures with a minor contribution to pass rate (~ 0.1%)
> Thanks
> Vladimir Beliaev
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.