You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@stdcxx.apache.org by "Martin Sebor (JIRA)" <ji...@apache.org> on 2008/01/19 00:35:34 UTC
[jira] Created: (STDCXX-702) move all buildlog parsing from
xbuildgen to xcomp.awk
move all buildlog parsing from xbuildgen to xcomp.awk
-----------------------------------------------------
Key: STDCXX-702
URL: https://issues.apache.org/jira/browse/STDCXX-702
Project: C++ Standard Library
Issue Type: Improvement
Components: Utilities
Reporter: Martin Sebor
Priority: Critical
The xbuildgen shell script currently parses each build log to extract from it the name of operating system, hardware architecture, compiler and number of other interesting pieces of data. The data is presented in the top table on each cross-platform build view page. Much of the data is also needed by (or would be useful in) the xcomp.awk script. This double processing is inefficient and should be eliminated. Instead, the xcomp.awk script should do all the parsing in one shot and format the top table as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (STDCXX-702) move all buildlog parsing from
xbuildgen to xcomp.awk
Posted by "Martin Sebor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STDCXX-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Sebor updated STDCXX-702:
--------------------------------
Remaining Estimate: 0.4h
Original Estimate: 0.4h
> move all buildlog parsing from xbuildgen to xcomp.awk
> -----------------------------------------------------
>
> Key: STDCXX-702
> URL: https://issues.apache.org/jira/browse/STDCXX-702
> Project: C++ Standard Library
> Issue Type: Improvement
> Components: Utilities
> Reporter: Martin Sebor
> Priority: Critical
> Original Estimate: 0.4h
> Remaining Estimate: 0.4h
>
> The xbuildgen shell script currently parses each build log to extract from it the name of operating system, hardware architecture, compiler and number of other interesting pieces of data. The data is presented in the top table on each cross-platform build view page. Much of the data is also needed by (or would be useful in) the xcomp.awk script. This double processing is inefficient and should be eliminated. Instead, the xcomp.awk script should do all the parsing in one shot and format the top table as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (STDCXX-702) move all buildlog parsing from
xbuildgen to xcomp.awk
Posted by "Martin Sebor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STDCXX-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Sebor updated STDCXX-702:
--------------------------------
Remaining Estimate: 21h (was: 0h)
> move all buildlog parsing from xbuildgen to xcomp.awk
> -----------------------------------------------------
>
> Key: STDCXX-702
> URL: https://issues.apache.org/jira/browse/STDCXX-702
> Project: C++ Standard Library
> Issue Type: Improvement
> Components: Utilities
> Reporter: Martin Sebor
> Priority: Critical
> Original Estimate: 0.4h
> Time Spent: 3h
> Remaining Estimate: 21h
>
> The xbuildgen shell script currently parses each build log to extract from it the name of operating system, hardware architecture, compiler and number of other interesting pieces of data. The data is presented in the top table on each cross-platform build view page. Much of the data is also needed by (or would be useful in) the xcomp.awk script. This double processing is inefficient and should be eliminated. Instead, the xcomp.awk script should do all the parsing in one shot and format the top table as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (STDCXX-702) move all buildlog parsing from
xbuildgen to xcomp.awk
Posted by "Martin Sebor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STDCXX-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Sebor resolved STDCXX-702.
---------------------------------
Resolution: Fixed
Fix Version/s: 4.2.1
Done in [r637269|http://svn.apache.org/viewvc?rev=637269&view=rev]. Need to merge out to 4.2.x.
> move all buildlog parsing from xbuildgen to xcomp.awk
> -----------------------------------------------------
>
> Key: STDCXX-702
> URL: https://issues.apache.org/jira/browse/STDCXX-702
> Project: C++ Standard Library
> Issue Type: Improvement
> Components: Utilities
> Reporter: Martin Sebor
> Assignee: Martin Sebor
> Priority: Critical
> Fix For: 4.2.1
>
> Original Estimate: 24h
> Time Spent: 3.13h
> Remaining Estimate: 20.87h
>
> The xbuildgen shell script currently parses each build log to extract from it the name of operating system, hardware architecture, compiler and number of other interesting pieces of data. The data is presented in the top table on each cross-platform build view page. Much of the data is also needed by (or would be useful in) the xcomp.awk script. This double processing is inefficient and should be eliminated. Instead, the xcomp.awk script should do all the parsing in one shot and format the top table as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (STDCXX-702) move all buildlog parsing from
xbuildgen to xcomp.awk
Posted by "Martin Sebor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STDCXX-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Sebor updated STDCXX-702:
--------------------------------
Remaining Estimate: 24h (was: 0.4h)
Original Estimate: 24h (was: 0.4h)
> move all buildlog parsing from xbuildgen to xcomp.awk
> -----------------------------------------------------
>
> Key: STDCXX-702
> URL: https://issues.apache.org/jira/browse/STDCXX-702
> Project: C++ Standard Library
> Issue Type: Improvement
> Components: Utilities
> Reporter: Martin Sebor
> Priority: Critical
> Original Estimate: 24h
> Time Spent: 0h
> Remaining Estimate: 24h
>
> The xbuildgen shell script currently parses each build log to extract from it the name of operating system, hardware architecture, compiler and number of other interesting pieces of data. The data is presented in the top table on each cross-platform build view page. Much of the data is also needed by (or would be useful in) the xcomp.awk script. This double processing is inefficient and should be eliminated. Instead, the xcomp.awk script should do all the parsing in one shot and format the top table as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (STDCXX-702) move all buildlog parsing from
xbuildgen to xcomp.awk
Posted by "Martin Sebor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/STDCXX-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Sebor reassigned STDCXX-702:
-----------------------------------
Assignee: Martin Sebor
> move all buildlog parsing from xbuildgen to xcomp.awk
> -----------------------------------------------------
>
> Key: STDCXX-702
> URL: https://issues.apache.org/jira/browse/STDCXX-702
> Project: C++ Standard Library
> Issue Type: Improvement
> Components: Utilities
> Reporter: Martin Sebor
> Assignee: Martin Sebor
> Priority: Critical
> Original Estimate: 24h
> Time Spent: 3h
> Remaining Estimate: 21h
>
> The xbuildgen shell script currently parses each build log to extract from it the name of operating system, hardware architecture, compiler and number of other interesting pieces of data. The data is presented in the top table on each cross-platform build view page. Much of the data is also needed by (or would be useful in) the xcomp.awk script. This double processing is inefficient and should be eliminated. Instead, the xcomp.awk script should do all the parsing in one shot and format the top table as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.