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/09/17 15:34:56 UTC
[jira] Created: (HARMONY-4807) [buildtest][eut] EUT summary
reporter
[buildtest][eut] EUT summary reporter
-------------------------------------
Key: HARMONY-4807
URL: https://issues.apache.org/jira/browse/HARMONY-4807
Project: Harmony
Issue Type: New Feature
Components: build - test - ci
Environment: any
Reporter: Vladimir Beliaev
For now EUT (both pure and w/ Harmony wrappers) does not generate HTML summary report.
To get this resolved it is recommended to develop Java-program which includes a SAX-based parser to process XML reports. This solution is preferable because:
1. one checked that (in spite of EUT run produces xml/html reports for suites exist) the junitreport tag does not actually "eat" these reports to produce the summary.
2. there are specific case for EUT - suite crash - when XML report is not generated, so no information to be put in summary report.
3. EUT does not operate with Exclude-list, instead one runs all of the EUT and then applies the Excepted Failure List (EFL) to filter out expected failures/errors. Thus two summaries are possible for EUT on Harmony - Relative Summary (which takes EFL into account) and Absolute Summary (which just show the real status of EUT run).
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-4807) [buildtest][eut] EUT summary
reporter
Posted by "Vladimir Beliaev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Beliaev updated HARMONY-4807:
--------------------------------------
Attachment: 01-H4807.zip
> [buildtest][eut] EUT summary reporter
> -------------------------------------
>
> Key: HARMONY-4807
> URL: https://issues.apache.org/jira/browse/HARMONY-4807
> Project: Harmony
> Issue Type: New Feature
> Components: build - test - ci
> Environment: any
> Reporter: Vladimir Beliaev
> Attachments: 01-H4807.zip, 02-H4807.sh
>
>
> For now EUT (both pure and w/ Harmony wrappers) does not generate HTML summary report.
> To get this resolved it is recommended to develop Java-program which includes a SAX-based parser to process XML reports. This solution is preferable because:
> 1. one checked that (in spite of EUT run produces xml/html reports for suites exist) the junitreport tag does not actually "eat" these reports to produce the summary.
> 2. there are specific case for EUT - suite crash - when XML report is not generated, so no information to be put in summary report.
> 3. EUT does not operate with Exclude-list, instead one runs all of the EUT and then applies the Excepted Failure List (EFL) to filter out expected failures/errors. Thus two summaries are possible for EUT on Harmony - Relative Summary (which takes EFL into account) and Absolute Summary (which just show the real status of EUT run).
> 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-4807) [buildtest][eut] EUT summary
reporter
Posted by "Vladimir Beliaev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Beliaev updated HARMONY-4807:
--------------------------------------
Attachment: 02-H4807.sh
> [buildtest][eut] EUT summary reporter
> -------------------------------------
>
> Key: HARMONY-4807
> URL: https://issues.apache.org/jira/browse/HARMONY-4807
> Project: Harmony
> Issue Type: New Feature
> Components: build - test - ci
> Environment: any
> Reporter: Vladimir Beliaev
> Attachments: 01-H4807.zip, 02-H4807.sh
>
>
> For now EUT (both pure and w/ Harmony wrappers) does not generate HTML summary report.
> To get this resolved it is recommended to develop Java-program which includes a SAX-based parser to process XML reports. This solution is preferable because:
> 1. one checked that (in spite of EUT run produces xml/html reports for suites exist) the junitreport tag does not actually "eat" these reports to produce the summary.
> 2. there are specific case for EUT - suite crash - when XML report is not generated, so no information to be put in summary report.
> 3. EUT does not operate with Exclude-list, instead one runs all of the EUT and then applies the Excepted Failure List (EFL) to filter out expected failures/errors. Thus two summaries are possible for EUT on Harmony - Relative Summary (which takes EFL into account) and Absolute Summary (which just show the real status of EUT run).
> 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-4807) [buildtest][eut] EUT summary
reporter
Posted by "Stepan Mishura (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stepan Mishura reassigned HARMONY-4807:
---------------------------------------
Assignee: Stepan Mishura
> [buildtest][eut] EUT summary reporter
> -------------------------------------
>
> Key: HARMONY-4807
> URL: https://issues.apache.org/jira/browse/HARMONY-4807
> Project: Harmony
> Issue Type: New Feature
> Components: build - test - ci
> Environment: any
> Reporter: Vladimir Beliaev
> Assignee: Stepan Mishura
> Attachments: 01-H4807.zip, 02-H4807.sh, 03-H4807.patch
>
>
> For now EUT (both pure and w/ Harmony wrappers) does not generate HTML summary report.
> To get this resolved it is recommended to develop Java-program which includes a SAX-based parser to process XML reports. This solution is preferable because:
> 1. one checked that (in spite of EUT run produces xml/html reports for suites exist) the junitreport tag does not actually "eat" these reports to produce the summary.
> 2. there are specific case for EUT - suite crash - when XML report is not generated, so no information to be put in summary report.
> 3. EUT does not operate with Exclude-list, instead one runs all of the EUT and then applies the Excepted Failure List (EFL) to filter out expected failures/errors. Thus two summaries are possible for EUT on Harmony - Relative Summary (which takes EFL into account) and Absolute Summary (which just show the real status of EUT run).
> 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] Commented: (HARMONY-4807) [buildtest][eut] EUT summary
reporter
Posted by "Vladimir Beliaev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12528061 ]
Vladimir Beliaev commented on HARMONY-4807:
-------------------------------------------
Also...
Right now the tests/eut/build.xml contains the sofisticate code which parses output.txt and XML reports, does regexp-based filtering and generates report.txt file.
The recommended Java-program should do this parsing and output the collected data in to form:
1. index.htm - html summary report with links to suites html reports.
2. report.txt - the text file contating failures/errors/crashes with issue output / messages / stack traces (filtered from output.txt).
Thanks
Vladimir Beliaev
> [buildtest][eut] EUT summary reporter
> -------------------------------------
>
> Key: HARMONY-4807
> URL: https://issues.apache.org/jira/browse/HARMONY-4807
> Project: Harmony
> Issue Type: New Feature
> Components: build - test - ci
> Environment: any
> Reporter: Vladimir Beliaev
>
> For now EUT (both pure and w/ Harmony wrappers) does not generate HTML summary report.
> To get this resolved it is recommended to develop Java-program which includes a SAX-based parser to process XML reports. This solution is preferable because:
> 1. one checked that (in spite of EUT run produces xml/html reports for suites exist) the junitreport tag does not actually "eat" these reports to produce the summary.
> 2. there are specific case for EUT - suite crash - when XML report is not generated, so no information to be put in summary report.
> 3. EUT does not operate with Exclude-list, instead one runs all of the EUT and then applies the Excepted Failure List (EFL) to filter out expected failures/errors. Thus two summaries are possible for EUT on Harmony - Relative Summary (which takes EFL into account) and Absolute Summary (which just show the real status of EUT run).
> 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-4807) [buildtest][eut] EUT summary
reporter
Posted by "Vladimir Beliaev (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Beliaev updated HARMONY-4807:
--------------------------------------
Attachment: 03-H4807.patch
I've attached 3 files to integrate implementation of summary reporter. Please get this data committed:
1. unpack 01-H4807.zip into tests/eut directory
2. run 02-H4807.sh script in this directory (adds/moves files by SVN)
3. apply 03-H4807.path (updates EFL and build.xml)
I've tested written stuff on several suites - looks like it works correctly. The issues are possible, so your input is welcome.
Thanks
Vladimir Beliaev
> [buildtest][eut] EUT summary reporter
> -------------------------------------
>
> Key: HARMONY-4807
> URL: https://issues.apache.org/jira/browse/HARMONY-4807
> Project: Harmony
> Issue Type: New Feature
> Components: build - test - ci
> Environment: any
> Reporter: Vladimir Beliaev
> Attachments: 01-H4807.zip, 02-H4807.sh, 03-H4807.patch
>
>
> For now EUT (both pure and w/ Harmony wrappers) does not generate HTML summary report.
> To get this resolved it is recommended to develop Java-program which includes a SAX-based parser to process XML reports. This solution is preferable because:
> 1. one checked that (in spite of EUT run produces xml/html reports for suites exist) the junitreport tag does not actually "eat" these reports to produce the summary.
> 2. there are specific case for EUT - suite crash - when XML report is not generated, so no information to be put in summary report.
> 3. EUT does not operate with Exclude-list, instead one runs all of the EUT and then applies the Excepted Failure List (EFL) to filter out expected failures/errors. Thus two summaries are possible for EUT on Harmony - Relative Summary (which takes EFL into account) and Absolute Summary (which just show the real status of EUT run).
> 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-4807) [buildtest][eut] EUT summary
reporter
Posted by "Stepan Mishura (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stepan Mishura resolved HARMONY-4807.
-------------------------------------
Resolution: Fixed
Thanks Vladimir - the patch was applied to BTI branch 2.0 at r576965.
Please check that the patch was applied as you expected.
Also I've updated Eclipse unit tests adaptors to to reflect changes in build.xml.
The adaptors set 'result.dir' property and your update renamed it to 'results.root.dir'
So I did for adaptors:
- <property name="result.dir"
+ <property name="results.root.dir"
> [buildtest][eut] EUT summary reporter
> -------------------------------------
>
> Key: HARMONY-4807
> URL: https://issues.apache.org/jira/browse/HARMONY-4807
> Project: Harmony
> Issue Type: New Feature
> Components: build - test - ci
> Environment: any
> Reporter: Vladimir Beliaev
> Assignee: Stepan Mishura
> Attachments: 01-H4807.zip, 02-H4807.sh, 03-H4807.patch
>
>
> For now EUT (both pure and w/ Harmony wrappers) does not generate HTML summary report.
> To get this resolved it is recommended to develop Java-program which includes a SAX-based parser to process XML reports. This solution is preferable because:
> 1. one checked that (in spite of EUT run produces xml/html reports for suites exist) the junitreport tag does not actually "eat" these reports to produce the summary.
> 2. there are specific case for EUT - suite crash - when XML report is not generated, so no information to be put in summary report.
> 3. EUT does not operate with Exclude-list, instead one runs all of the EUT and then applies the Excepted Failure List (EFL) to filter out expected failures/errors. Thus two summaries are possible for EUT on Harmony - Relative Summary (which takes EFL into account) and Absolute Summary (which just show the real status of EUT run).
> 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] Closed: (HARMONY-4807) [buildtest][eut] EUT summary reporter
Posted by "Stepan Mishura (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HARMONY-4807?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stepan Mishura closed HARMONY-4807.
-----------------------------------
Closing - no response from the reporter, assuming OK
> [buildtest][eut] EUT summary reporter
> -------------------------------------
>
> Key: HARMONY-4807
> URL: https://issues.apache.org/jira/browse/HARMONY-4807
> Project: Harmony
> Issue Type: New Feature
> Components: build - test - ci
> Environment: any
> Reporter: Vladimir Beliaev
> Assignee: Stepan Mishura
> Attachments: 01-H4807.zip, 02-H4807.sh, 03-H4807.patch
>
>
> For now EUT (both pure and w/ Harmony wrappers) does not generate HTML summary report.
> To get this resolved it is recommended to develop Java-program which includes a SAX-based parser to process XML reports. This solution is preferable because:
> 1. one checked that (in spite of EUT run produces xml/html reports for suites exist) the junitreport tag does not actually "eat" these reports to produce the summary.
> 2. there are specific case for EUT - suite crash - when XML report is not generated, so no information to be put in summary report.
> 3. EUT does not operate with Exclude-list, instead one runs all of the EUT and then applies the Excepted Failure List (EFL) to filter out expected failures/errors. Thus two summaries are possible for EUT on Harmony - Relative Summary (which takes EFL into account) and Absolute Summary (which just show the real status of EUT run).
> Thanks
> Vladimir Beliaev
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.