|
Home About Us A-Z Index Search * Contact Us Register Login Press ShopThe Open Brand -- Problem Reporting and Interpretations System |
Problem Report 1850 Details
Show help | Quick Search | Submit a Test Suite Support Request | Click here to view your privileges
This page provides all information on Problem Report 1850.
Report 1850 Actions
Problem Report Number 1850 Submitter's Classification Test Suite problem State Resolved Resolution Test Suite Deficiency (TSD) Problem Resolution ID TSD.X.0927 Raised 2001-11-07 08:00 Updated 2003-03-13 08:00 Published 2001-11-08 08:00 Product Standard Window System Application Interface V2 Certification Program The Open Brand certification program Test Suite VSW version 5.1.2 Test Identification Xlib11/PropertyNotify 1 Linked Problem Reports MSF4W.00026, (in, old, system) Problem Summary TSD4W.00172 The test may fail on systems where long and int are not the same size, as it passes 32-bit data to XChangeProperty in an int instead of a long. Problem Text
This test fails in 64bit environments with the reasons given in a
previous request, which received a temporary waiver MSF4W.00026.
It seems to be related to the recently refused request req.4.W.00157
regarding XChangeProperty and related tests.
Our fix for PropertyNotify causes the XChangeProperty fails.
Our engineers state;
"We have two test cases here:
1. in tset/Xlib5/chngprprty/Test.c, "long" type data is passed to
XChangeProperty when format is specified as 32.
2. in tset/Xlib11/prprtyntfy/Test.c, "int" type data is passed to
XChangeProperty when format is specified as 32.
For 64-bit OS, these two test cases can't be correct at same time.
Since TOG thinks the test case 1 is correct (according to the TOG
response to the waiver request req.4.W.00157, then test case 2
must be wrong. We should claim a waiver for PropertyNotify using
exactly same reason that TOG used to refuse the waiver request
for req.4.W.00157.
We believe the previous PropertyNotify conclusion was incorrect. "
Test Output
70||"VSW5TESTSUITE CASE PropertyNotify 2"
110|1392 /tset/Xlib11/prprtyntfy/Test 14:52:17|Build Start, scenario ref 940-0
130|1392 0 14:52:18|Build End, scenario ref 940-0
10|1393 /tset/Xlib11/prprtyntfy/Test 14:52:18|TC Start, scenario ref 940-0
15|1393 3.1-lite 2|TCM Start
400|1393 1 1 14:52:23|IC Start
200|1393 1 14:52:23|TP Start
520|1393 1 00024136 1 1|VSW5TESTSUITE PURPOSE 1
520|1393 1 00024136 1 2|Assertion PropertyNotify-1.(A)
520|1393 1 00024136 1 3|When a PropertyNotify event is generated, then all clien
ts
520|1393 1 00024136 1 4|having set PropertyChangeMask event mask bits on the eve
nt
520|1393 1 00024136 1 5|window are delivered a PropertyNotify event.
520|1393 1 00024136 1 6|METH: Create clients client2 and client3.
520|1393 1 00024136 1 7|METH: Create window.
520|1393 1 00024136 1 8|METH: Select for PropertyNotify events using PropertyCha
ngeMask.
520|1393 1 00024136 1 9|METH: Select for PropertyNotify events using PropertyCha
ngeMask with client2.
520|1393 1 00024136 1 10|METH: Select for no events with client3.
520|1393 1 00024136 1 11|METH: Create atom for property.
520|1393 1 00024136 1 12|METH: Generate PropertyNotify event.
520|1393 1 00024136 1 13|METH: Verify that a PropertyNotify event was delivered.
520|1393 1 00024136 1 14|METH: Verify that event member fields are correctly set
.
520|1393 1 00024136 1 15|METH: Verify that a PropertyNotify event was delivered
to client2.
520|1393 1 00024136 1 16|METH: Verify that event member fields are correctly set
.
520|1393 1 00024136 1 17|METH: Verify that no events were delivered to client3.
520|1393 1 00024136 1 18|unexpected signal 10 (unknown signal) received
220|1393 1 2 14:52:23|UNRESOLVED
410|1393 1 1 14:52:23|IC EndReview Information
Review Type TSMA Review Start Date null Completed null Status Complete Review Recommendation No Resolution Given Review Response
This is accepted as a fault in the test suite.
As regards MSF4W.00026, I disagree with the submitter's statement "We
believe the previous PropertyNotify conclusion was incorrect". The
conclusion in MSF4W.00026 was correct, based on the information given in
the request, where the submitter stated that the problem was due to a
fault in the 64-bit X server. If the problem was in the X server then
it would still occur when a 32-bit client was used with the 64-bit
X server. With hindsight, it seems likely that the problem did not
occur in the 64-bit X server as claimed, but in the 64-bit X library.
Review Type SA Review Start Date null Completed null Status Complete Review Resolution Test Suite Deficiency (TSD) Review Conclusion
This is an agreed Test Suite Deficiency.
Problem Reporting System Options:
- View Report 1850
- List All PRs
- Search Reports
- Email the System Administrator
- View the The Open Brand Interpretations Database User Manual
Contact the Certification Authority