[lsb-bugs] [Bug 2636] New: /tset/Xlib8/flushgc/Test 1, 2 UNRESOLVED
bugzilla-daemon at linux-foundation.org
bugzilla-daemon at linux-foundation.org
Wed May 6 17:19:17 PDT 2009
http://bugs.linuxbase.org/show_bug.cgi?id=2636
Summary: /tset/Xlib8/flushgc/Test 1,2 UNRESOLVED
Product: Distribution Tests
Version: 4.0
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: lsb-xts5
AssignedTo: stewb at linux-foundation.org
ReportedBy: stewb at linux-foundation.org
QAContact: lsb-bugs at freestandards.org
Showing up on Mandriva 2009.0/ia32. Fresh built 4.0 tree, just today. Jeff says
it's also showing up in SLES11 submissions for cert:
/tset/Xlib8/flushgc/Test 1 UNRESOLVED
/tset/Xlib8/flushgc/Test 2 UNRESOLVED
Saw xcb messages on the console during run, which makes me think it's some
corner left from the previous xcb issues we had.
journal:
520|369 1 00019301 1 4|GCcontext argument does not name a defined GCcontext a
ca
ll
520|369 1 00019301 1 5|to XFlushGC shall generate a BadGC error.
520|369 1 00019301 1 6|PREP: Create a window.
520|369 1 00019301 1 7|PREP: Create a GC
520|369 1 00019301 1 8|PREP: Free the GC
520|369 1 00019301 1 9|TEST: Call to XFlushGC generates BadGC error
520|369 1 00019301 1 10|unexpected signal 6 (SIGABRT) received
220|369 1 2 16:55:21|UNRESOLVED
410|369 1 1 16:55:21|IC End
400|369 2 1 16:55:21|IC Start
200|369 2 16:55:21|TP Start
520|369 2 00019301 1 1|VSW5TESTSUITE PURPOSE 2
520|369 2 00019301 1 2|Assertion XFlushGC-2.(A)
520|369 2 00019301 1 3|If the implementation is X11R5 or later: A call to
XFlushGC
520|369 2 00019301 1 4|shall force cached GC changes to the server.
520|369 2 00019301 1 5|unexpected signal 6 (SIGABRT) received
220|369 2 2 16:55:21|UNRESOLVED
410|369 2 1 16:55:21|IC End
510|369|system 0: Abandoning testset: caught unexpected signal 6 (SIGABRT)
80|369 1 16:55:22|TC End, scenario ref 748-0
Running just this test, then they pass.
Reproducible with the snapshots build too.
--
Configure bugmail: http://bugs.linuxbase.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
More information about the lsb-bugs
mailing list