From licquia at linuxfoundation.org  Thu Dec  3 18:36:50 2015
From: licquia at linuxfoundation.org (Jeff Licquia)
Date: Thu, 03 Dec 2015 13:36:50 -0500
Subject: [Lsb-messages] /var/www/bzr/lsb/devel/problem_db r316: First batch
 of problemreport keyword updates.
Message-ID: <20151203184008.4909CEB927@scm.linux-foundation.org>

------------------------------------------------------------
revno: 316
committer: Jeff Licquia <licquia at linuxfoundation.org>
branch nick: problem_db
timestamp: Thu 2015-12-03 13:36:50 -0500
message:
  First batch of problemreport keyword updates.
modified:
  problem_db2
-------------- next part --------------
=== modified file 'problem_db2'
--- a/problem_db2	2014-01-29 03:24:55 +0000
+++ b/problem_db2	2015-12-03 18:36:50 +0000
@@ -5560,6 +5560,7 @@
 COMMENT or <a href="http://bugs.linuxbase.org/show_bug.cgi?id=2849">LSB bug 2849</a> for more information.
 COMMENT The change was later reverted by upstream.{/noreplace}
 RESOLUTION Known Problem
+WAIVE
 END
 
 ### Problem Record #438
@@ -6621,6 +6622,7 @@
 COMMENT This issue is still under investigation.
 LINK http://bugs.linuxbase.org/show_bug.cgi?id=3153 | bug 3153
 RESOLUTION Known Problem
+WAIVE
 END
 
 ### Problem Record #520
@@ -6632,6 +6634,7 @@
 COMMENT This issue is still under investigation
 LINK http://bugs.linuxbase.org/show_bug.cgi?id=3184 | bug 3184
 RESOLUTION Known Problem
+WAIVE
 END
 
 ### Problem Record #521
@@ -7186,6 +7189,7 @@
 COMMENT and Locale::Script has been re-organized in more recent Perl, and some distributions have followed suit. In particular "use Locale::Contants" will fail on these systems. How to handle this in LSB is still undetermined.
 LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3282 | Bug 3282
 RESOLUTION Known Problem
+WAIVE
 END
 
 ### Problem Record #557
@@ -7394,9 +7398,10 @@
    MARKER Requirement failed:
    MARKER {g_main_context_iteration.01.02.01}
    MARKER may_block is TRUE, waiting for a source to become ready
-COMMENT This failure is occurring on some modern distributions. Root cause still needs to be analysed.
+COMMENT This appears to be specified somewhat ambiguously, with upstream's clarification being different from the test author.  See the bug for more details.
 LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3413 | Bug 3413
-RESOLUTION Known Problem
+RESOLUTION Test suite deficiency
+WAIVE
 END
 
 ### Problem Record #567
@@ -7870,6 +7875,7 @@
 COMMENT Locale::Constants is not available on some newer distributions. LSB still requires it.
 LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3282 | Bug 3282
 RESOLUTION Known Problem
+WAIVE
 END
 
 ### Problem Record #601
@@ -7979,9 +7985,10 @@
    MARKER Requirement failed:
    MARKER {g_closure_set_meta_marshal.01}
    MARKER Sets the meta marshaller as notifier of closure.
-COMMENT This failure is occurring on some newer distributions. The issue is still under investigation.
+COMMENT This is caused by a performance improvement on an internal struct; not being fixed upstream.
 LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3474 | Bug 3474
-RESOLUTION Known Problem
+RESOLUTION Upstream change
+WAIVE
 END
 
 ### Problem Record #609
@@ -8198,9 +8205,10 @@
 TEST /tset/LSB.os/mprotect/mprotect_P/T.mprotect_P 4
   SEVERITY failed
    MARKER write() failed, errno = 0 (NO ERROR)
-COMMENT This failure is happening on some ppc64 systems. The issue is still under investigation.
+COMMENT This failure is happening on some ppc64 systems. The issue is still under investigation, but is most likely a test bug.
 LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3569 | bug 3569
 RESOLUTION Known Problem
+WAIVE
 END
 
 ### Problem Record #624
@@ -8552,13 +8560,14 @@
 ### Problem Record #647
 STANDARD LSB
 ARCHITECTURE PPC64
-TESTSUITE olver
+TESTSUITE olver < 5.0
 TEST /olver/io/term/tests/read_tty_spec 1
   SEVERITY failed
    MARKER Requirement failed: {app.read.10} IEXTEN flag is not set
 COMMENT This issue is currently under investigation.
 LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3788 | LSB bug 3788
-RESOLUTION Known problem
+RESOLUTION Test suite deficiency
+WAIVE
 END
 
 ### Problem Record #648
@@ -8768,7 +8777,7 @@
 TEST /tset/POSIX.os/dataform/cpio/T.cpio 27
    | /tset/POSIX.os/dataform/tar/T.tar 5
   SEVERITY failed
-   MARKER file name was not resolved to "F" when extracting "///opt/lsb/test/core/tet/test_sets/TESTROOT/tset/POSIX.os/dataform/tar/d.tar/CWD/F"
+   MARKER file name was not resolved to "F"
 COMMENT As a security measure, some tar/cpio/pax implementations strip leading path separators and disallow relative path links (i.e. "/" and "..").  This should be allowed as an exception to the regular spec.
 LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3824 LSB bug 3824
 RESOLUTION Specification deficiency


From licquia at linuxfoundation.org  Thu Dec  3 21:42:17 2015
From: licquia at linuxfoundation.org (Jeff Licquia)
Date: Thu, 03 Dec 2015 16:42:17 -0500
Subject: [Lsb-messages] /var/www/bzr/lsb/devel/problem_db r317: Next batch
 of problem reports from bugs.
Message-ID: <20151203214507.9CDFAEB927@scm.linux-foundation.org>

------------------------------------------------------------
revno: 317
committer: Jeff Licquia <licquia at linuxfoundation.org>
branch nick: problem_db
timestamp: Thu 2015-12-03 16:42:17 -0500
message:
  Next batch of problem reports from bugs.
modified:
  problem_db2
-------------- next part --------------
=== modified file 'problem_db2'
--- a/problem_db2	2015-12-03 18:36:50 +0000
+++ b/problem_db2	2015-12-03 21:42:17 +0000
@@ -8875,3 +8875,102 @@
 RESOLUTION Upstream bug
 END
 
+### Problem Record #670
+STANDARD LSB
+TESTSUITE core
+TEST /tset/LSB.os/network/gethostbyaddr/T.gethostbyaddr 2
+  SEVERITY failed
+   MARKER after gethostbyaddr() for 127.0.0.2, h_errno was set to -1
+COMMENT The test does not check the return value properly.  See bug for details.
+LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3843 | Bug 3843
+RESOLUTION Test suite deficiency
+WAIVE
+END
+
+### Problem Record #671
+STANDARD LSB
+TESTSUITE desktop-t2c
+TEST /gobject-t2c/tests/gobject_gtype_instance/gobject_gtype_instance {38,40,42}
+  SEVERITY failed
+   MARKER {g_type_add_class_cache_func.01}
+COMMENT Upstream change; still investigating.
+LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3844 | LSB bug 3844
+LINK https://git.gnome.org/browse/glib/commit/?id=72df62600d1ab473125b6e8beb998e71aa63701e | Upstream patch introducing change
+LINK https://bugzilla.gnome.org/show_bug.cgi?id=693351 | Upstream bug 693351
+RESOLUTION Test suite deficiency
+WAIVE
+END
+
+### Problem Record #672
+STANDARD LSB
+TESTSUITE core
+TEST /tset/POSIX.os/devclass/tcflush/T.tcflush 4
+  SEVERITY failed
+   MARKER when TOSTOP was set
+COMMENT This is a kernel regression, fixed in more recent kernels.  See the LSB bug or the mailing list discussion for more details.
+LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3863 | LSB bug 3863
+LINK http://lkml.iu.edu/hypermail/linux/kernel/1309.3/01613.html | Kernel patch
+LINK http://lkml.iu.edu/hypermail/linux/kernel/1309.3/01277.html | LKML discussion
+RESOLUTION Kernel bug
+END
+
+### Problem Record #673
+STANDARD LSB
+TESTSUITE core
+TEST /tset/POSIX.os/procenv/setenv/T.setenv 1
+  SEVERITY unresolved
+   MARKER child process gave unexpected exit code
+TEST /tset/POSIX.os/procenv/unsetenv/T.unsetenv 1
+  SEVERITY unresolved
+   MARKER child process gave unexpected exit code
+COMMENT Bug in test code.  See bug for details.
+LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3847 | Bug 3847
+RESOLUTION Test suite deficiency
+WAIVE
+END
+
+### Problem Record #674
+STANDARD LSB
+TESTSUITE core
+TEST /tset/ANSI.os/genuts/abort/T.abort 7
+  SEVERITY unresolved
+   MARKER unexpected signal received
+TEST /tset/ANSI.os/genuts/exit/T.exit 8
+  SEVERITY unresolved
+   MARKER unexpected signal received
+TEST /tset/ANSI.os/genuts/_exit/T._exit 8
+  SEVERITY unresolved
+   MARKER unexpected signal received
+TEST /tset/POSIX.os/procprim/sigconcept/T.sigconcept 40
+  SEVERITY unresolved
+   MARKER unexpected signal received
+COMMENT This is caused by a kernel regression introduced in 3.10, and subsequently fixed.  See the LSB bug for more information, and the linux-kernel mailing list thread for a patch.
+LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3863 | LSB bug 3863
+LINK https://lkml.org/lkml/2013/9/15/63 | LKML thread about this bug
+RESOLUTION Test suite deficiency
+END
+
+### Problem Record #675
+STANDARD LSB
+TESTSUITE olver
+TEST /olver/process/meta/tests/getpriority_spec 828
+  SEVERITY failed
+   MARKER Requirement failed: {getpriority.09.02}
+COMMENT This happens inconsistently when testing on a virtual machine, and is still under investigation.
+LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3927 | Bug 3927
+RESOLUTION Known problem
+WAIVE
+END
+
+### Problem Record #676
+STANDARD LSB
+TESTSUITE core < 5.0
+TEST /tset/LSB.os/network/accept/T.accept 1
+  MARKER fcntl syscall returned error
+TEST /tset/LSB.os/network/connect/T.connect 1
+  MARKER fcntl syscall returned error
+COMMENT This is caused by a bug in the tests, which should be fixed with newer tests.
+LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3957 | Bug 3957
+RESOLUTION Test suite deficiency
+WAIVE
+END


From licquia at linuxfoundation.org  Thu Dec  3 21:54:25 2015
From: licquia at linuxfoundation.org (Jeff Licquia)
Date: Thu, 03 Dec 2015 16:54:25 -0500
Subject: [Lsb-messages] /var/www/bzr/lsb/devel/problem_db r318: Tweak some
 CUPS-related problem reports.
Message-ID: <20151203215507.45996EB927@scm.linux-foundation.org>

------------------------------------------------------------
revno: 318
committer: Jeff Licquia <licquia at linuxfoundation.org>
branch nick: problem_db
timestamp: Thu 2015-12-03 16:54:25 -0500
message:
  Tweak some CUPS-related problem reports.
modified:
  problem_db2
-------------- next part --------------
=== modified file 'problem_db2'
--- a/problem_db2	2015-12-03 21:42:17 +0000
+++ b/problem_db2	2015-12-03 21:54:25 +0000
@@ -8816,13 +8816,16 @@
 ### Problem Record #666
 STANDARD LSB
 TESTSUITE printing
-TEST /convenience/cupsConvenience {1..4}
+TEST /convenience/cupsConvenience {1,2}
   SEVERITY failed
    MARKER returned NULL, expected a value
-TEST /convenience/cupsConvenience {5..7,32}
-  SEVERITY failed
-   MARKER returned 0, expected a value
-TEST /convenience/cupsConvenience {8,9,12}
+TEST /convenience/cupsConvenience {3,4}
+  SEVERITY failed
+   MARKER returned NULL, expected a filename
+TEST /convenience/cupsConvenience {5,7-9,32}
+  SEVERITY failed
+   MARKER returned 0, expected a positive value
+TEST /convenience/cupsConvenience {6,12}
   SEVERITY unresolved
    MARKER returned 0, expected a value
 TEST /convenience/cupsConvenience 10
@@ -8974,3 +8977,14 @@
 RESOLUTION Test suite deficiency
 WAIVE
 END
+
+### Problem Record #677
+STANDARD LSB
+TESTSUITE printing
+TEST /convenience/cupsConvenience 11
+  MARKER unexpected signal 15 (SIGTERM) received
+COMMENT This appears to be an interaction problem between newer CUPS versions and our test cupsd.  It is still under investigation, but is almost certainly a test bug.
+LINK https://lsbbugs.linuxfoundation.org/show_bug.cgi?id=3964 | LSB bug 3964
+RESOLUTION Test suite deficiency
+WAIVE 
+END