Issue Details (XML | Word | Printable)

Key: STDCXX-644
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Minor Minor
Assignee: Travis Vitek
Reporter: Travis Vitek
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
C++ Standard Library

[IBM XLC++ 9.0/AIX 5.3] SIGHUP in 19.exceptions.mt

Created: 02/Nov/07 10:30 PM   Updated: 06/May/08 12:55 AM
Return to search
Component/s: Tests
Affects Version/s: 4.2.0
Fix Version/s: 4.2.1

Time Tracking:
Original Estimate: 8h
Original Estimate - 8h
Remaining Estimate: 7h
Time Spent - 1h Remaining Estimate - 7h
Time Spent: 1h
Time Spent - 1h Remaining Estimate - 7h

Environment: AIX
Issue Links:
Blocker
 

Severity: Incorrect Behavior
Resolution Date: 27/Mar/08 06:07 AM


 Description  « Hide

The test fails because a loop counter is trounced on every iteration, preventing the loop condition from failing. A simple workaround would be to move the declaration of the loop variable so as to avoid the problem so that the test can run.

 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Martin Sebor made changes - 02/Nov/07 11:50 PM
Field Original Value New Value
Link This issue is blocked by STDCXX-643 [ STDCXX-643 ]
Martin Sebor added a comment - 02/Nov/07 11:54 PM
Right. We could work around it. At the same time, it's thanks to the test that we discovered the incompatibility (STDCXX-643), so I'm not sure we should completely wipe out all signs of the problem. I guess this is another case where we could use the Expected Failure extension to the test driver.

Travis Vitek made changes - 07/Nov/07 08:24 PM
Summary 19.exceptions.mt test fails due to STDCXX-643 [IBM XLC++ 9.0/AIX 5.3] SIGHUP in 19.exceptions.mt
Martin Sebor made changes - 21/Jan/08 06:31 PM
Original Estimate 8h [ 28800 ]
Remaining Estimate 8h [ 28800 ]
Martin Sebor made changes - 01/Feb/08 04:35 AM
Assignee Travis Vitek [ vitek ]
Travis Vitek logged work - 26/Mar/08 05:05 PM
Time Worked: 1h
Look at build results, verify test is in xfail.txt.
Travis Vitek added a comment - 27/Mar/08 06:05 AM
Well, we already have an entry in xfail.txt for this. It has been there since r607788. Unless we intend to fix or work around the problem, I think this issue is done.

Travis Vitek made changes - 27/Mar/08 06:07 AM
Resolution Fixed [ 1 ]
Status Open [ 1 ] Resolved [ 5 ]
Travis Vitek made changes - 07/Apr/08 05:06 PM
Time Spent 1h [ 3600 ]
Remaining Estimate 8h [ 28800 ] 7h [ 25200 ]
Travis Vitek made changes - 06/May/08 12:55 AM
Status Resolved [ 5 ] Closed [ 6 ]