Re: Preparing for the next release: call for testing

2016-07-26 Thread Dmitry V. Levin
On Tue, Jul 26, 2016 at 10:50:47AM +0800, Yun-Chih Chen wrote: > Here's another build on qemu-system-mips and qemu-system-mips64el: > Qemu version: 2.3 > Architecture: mips, mipsel > Kernel: both 3.16.0-4-5kc-malta > gcc: both 4.9.2 > strace commit hash: 197829aa45837a1e7d5d20d7b6027e2ab3c17f9e >

Re: Preparing for the next release: call for testing

2016-07-25 Thread Yun-Chih Chen
Here's another build on qemu-system-mips and qemu-system-mips64el: Qemu version: 2.3 Architecture: mips, mipsel Kernel: both 3.16.0-4-5kc-malta gcc: both 4.9.2 strace commit hash: 197829aa45837a1e7d5d20d7b6027e2ab3c17f9e Failed with two testcases. SKIP: bpf = + ../strace -V + TIMEOUT=time

Re: Preparing for the next release: call for testing

2016-07-25 Thread Dmitry V. Levin
On Mon, Jul 25, 2016 at 08:49:42PM +0800, Yun-Chih Chen wrote: > Try to build strace on mips and mipsel on qemu-system-mips, > qemu-system-mips64el in the following configuration: > > Qemu version: 2.3 > Architecture: mips, mipsel > Kernel: both 3.2.0-4-kc-malta > gcc: both 4.6.3 > > failed to bu

Re: Preparing for the next release: call for testing

2016-06-06 Thread Dmitry V. Levin
On Sat, Jun 04, 2016 at 02:23:53PM +0100, Steve McIntyre wrote: [...] > * The strace -S test fails when building/running using a 32-bit >userspace and a 64-bit kernel - the output includes both 64-bit and >32-bit tracing which confuses the test. I have a hacky fix. Thanks Steve. Since st

Re: Preparing for the next release: call for testing

2016-06-04 Thread Steve McIntyre
On Wed, Jun 01, 2016 at 02:26:14PM +0100, Steve McIntyre wrote: > >I never did get around to working out the last few test case failures >with 4.11 on s390x, so I'm happy with 4.12 I won't have to! :-) Minor tweaks from the Debian side for 4.12: * I've dropped the libunwind option from the build

Re: Preparing for the next release: call for testing

2016-06-01 Thread Steve McIntyre
On Mon, May 30, 2016 at 07:07:47PM +0300, Dmitry V. Levin wrote: >Hi, > >There is quite enough good stuff accumulated in strace.git >since v4.11 so I think it's time to cut a new release. > >This is going to be the most tested strace released so far, >with code coverage about 70% on x86_64. > >Stil

Re: Preparing for the next release: call for testing

2015-12-16 Thread Dmitry V. Levin
On Thu, Dec 10, 2015 at 09:37:35PM -0500, Mike Frysinger wrote: > i haven't had a chance yet to triage these. > > testing commit bab4ef4272cd2596c7390b34ea8acc086ee8fdb2 (v4.10-566-gbab4ef4) > > native (build+tests): > vFAIL: build; x86_64 ??? linux-4.1.6 kernel-headers-3.4.0

Re: Preparing for the next release: call for testing

2015-12-15 Thread Dmitry V. Levin
On Tue, Dec 15, 2015 at 07:06:33AM +0300, Dmitry V. Levin wrote: > On Tue, Dec 15, 2015 at 12:59:48AM +0300, Dmitry V. Levin wrote: > > On Mon, Dec 14, 2015 at 04:46:49PM -0500, Mike Frysinger wrote: > [...] > > > we probably should add a sanity check to the gawk script so > > > it asserts rather t

Re: Preparing for the next release: call for testing

2015-12-15 Thread Dmitry V. Levin
On Mon, Dec 14, 2015 at 04:45:33PM -0500, Mike Frysinger wrote: > On 15 Dec 2015 00:03, Dmitry V. Levin wrote: > > On Mon, Dec 14, 2015 at 03:45:40PM -0500, Mike Frysinger wrote: [...] > > > looks like strace doesn't like it when you call clock_gettime: > > > strace: syscall_228(...) in unsupported

Re: Preparing for the next release: call for testing

2015-12-15 Thread Dmitry V. Levin
On Mon, Dec 14, 2015 at 04:45:33PM -0500, Mike Frysinger wrote: > On 15 Dec 2015 00:03, Dmitry V. Levin wrote: > > On Mon, Dec 14, 2015 at 03:45:40PM -0500, Mike Frysinger wrote: > > > On 11 Dec 2015 06:30, Dmitry V. Levin wrote: > > > > On Thu, Dec 10, 2015 at 09:37:35PM -0500, Mike Frysinger wrot

Re: Preparing for the next release: call for testing

2015-12-14 Thread Dmitry V. Levin
On Tue, Dec 15, 2015 at 12:59:48AM +0300, Dmitry V. Levin wrote: > On Mon, Dec 14, 2015 at 04:46:49PM -0500, Mike Frysinger wrote: [...] > > we probably should add a sanity check to the gawk script so > > it asserts rather than OOMs. > > Sure. I've pushed a fix for this so it won't go into infini

Re: Preparing for the next release: call for testing

2015-12-14 Thread Mike Frysinger
On 15 Dec 2015 00:59, Dmitry V. Levin wrote: > On Mon, Dec 14, 2015 at 04:46:49PM -0500, Mike Frysinger wrote: > > On 15 Dec 2015 00:24, Dmitry V. Levin wrote: > > > On Mon, Dec 14, 2015 at 03:45:40PM -0500, Mike Frysinger wrote: > > > [...] > > > > the older version of gawk used seems to be unhapp

Re: Preparing for the next release: call for testing

2015-12-14 Thread Dmitry V. Levin
On Mon, Dec 14, 2015 at 04:46:49PM -0500, Mike Frysinger wrote: > On 15 Dec 2015 00:24, Dmitry V. Levin wrote: > > On Mon, Dec 14, 2015 at 03:45:40PM -0500, Mike Frysinger wrote: > > [...] > > > the older version of gawk used seems to be unhappy with the script. > > > when i run the command manuall

Re: Preparing for the next release: call for testing

2015-12-14 Thread Mike Frysinger
On 15 Dec 2015 00:24, Dmitry V. Levin wrote: > On Mon, Dec 14, 2015 at 03:45:40PM -0500, Mike Frysinger wrote: > [...] > > the older version of gawk used seems to be unhappy with the script. > > when i run the command manually: > > $ gawk -v VAR_NAME=mpers_target_var -v ARCH_FLAG=m32 -f ./mpers.awk

Re: Preparing for the next release: call for testing

2015-12-14 Thread Mike Frysinger
On 15 Dec 2015 00:03, Dmitry V. Levin wrote: > On Mon, Dec 14, 2015 at 03:45:40PM -0500, Mike Frysinger wrote: > > On 11 Dec 2015 06:30, Dmitry V. Levin wrote: > > > On Thu, Dec 10, 2015 at 09:37:35PM -0500, Mike Frysinger wrote: > [...] > > > > vFAIL: test; x86_64 32-bit/LSB linux-4.1.6

Re: Preparing for the next release: call for testing

2015-12-14 Thread Dmitry V. Levin
On Mon, Dec 14, 2015 at 03:45:40PM -0500, Mike Frysinger wrote: [...] > the older version of gawk used seems to be unhappy with the script. > when i run the command manually: > $ gawk -v VAR_NAME=mpers_target_var -v ARCH_FLAG=m32 -f ./mpers.awk > mpers-m32/kernel_dirent.d2 > #include > typedef >

Re: Preparing for the next release: call for testing

2015-12-14 Thread Dmitry V. Levin
On Mon, Dec 14, 2015 at 03:45:40PM -0500, Mike Frysinger wrote: > On 11 Dec 2015 06:30, Dmitry V. Levin wrote: > > On Thu, Dec 10, 2015 at 09:37:35PM -0500, Mike Frysinger wrote: [...] > > > vFAIL: test; x86_64 32-bit/LSB linux-4.1.6 > > > kernel-headers-4.1.0 glibc-2.21 gcc-4.9.2

Re: Preparing for the next release: call for testing

2015-12-14 Thread Mike Frysinger
On 11 Dec 2015 06:30, Dmitry V. Levin wrote: > On Thu, Dec 10, 2015 at 09:37:35PM -0500, Mike Frysinger wrote: > > i haven't had a chance yet to triage these. > > > > testing commit bab4ef4272cd2596c7390b34ea8acc086ee8fdb2 (v4.10-566-gbab4ef4) > > > > native (build+tests): > > vFAIL: build; x86

Re: Preparing for the next release: call for testing

2015-12-10 Thread enh
d'oh. yeah, adding HAVE_LINUX_IPC_H fixes it. On Thu, Dec 10, 2015 at 11:38 AM, Dmitry V. Levin wrote: > Hi, > > On Thu, Dec 10, 2015 at 10:54:55AM -0800, Elliott Hughes wrote: >> other than one small patch to build (below and attached, since gmail >> mangles these things), lgtm on Android. >> >>

Re: Preparing for the next release: call for testing

2015-12-10 Thread Dmitry V. Levin
On Thu, Dec 10, 2015 at 09:37:35PM -0500, Mike Frysinger wrote: > i haven't had a chance yet to triage these. > > testing commit bab4ef4272cd2596c7390b34ea8acc086ee8fdb2 (v4.10-566-gbab4ef4) > > native (build+tests): > vFAIL: build; x86_64 ??? linux-4.1.6 kernel-headers-3.4.0

Re: Preparing for the next release: call for testing

2015-12-10 Thread Mike Frysinger
i haven't had a chance yet to triage these. testing commit bab4ef4272cd2596c7390b34ea8acc086ee8fdb2 (v4.10-566-gbab4ef4) native (build+tests): vFAIL: build; x86_64 ??? linux-4.1.6 kernel-headers-3.4.0 glibc-2.4 gcc-4.5.4 vFAIL: test; armv7l 32-bit/LSB linux-3.4.0-vapi

Re: Preparing for the next release: call for testing

2015-12-10 Thread Dmitry V. Levin
Hi, On Thu, Dec 10, 2015 at 10:54:55AM -0800, Elliott Hughes wrote: > other than one small patch to build (below and attached, since gmail > mangles these things), lgtm on Android. > > If we build strace against the untouched Linux kernel uapi headers (as used > by bionic), the key fields are cal

Re: Preparing for the next release: call for testing

2015-12-10 Thread enh
other than one small patch to build (below and attached, since gmail mangles these things), lgtm on Android. If we build strace against the untouched Linux kernel uapi headers (as used by bionic), the key fields are called 'key', not '__key'. * ipc_msgctl.c, ipc_shmctl.c: Add #define workaround

Re: Preparing for the next release: call for testing

2015-03-05 Thread Dmitry V. Levin
On Wed, Mar 04, 2015 at 10:55:45PM -0500, Mike Frysinger wrote: > testing commit a1c5e0721fb679a550ac0cd2c9e231409ebb1e26 (v4.9-391-ga1c5e07) > vFAIL: test; parisc 32-bit/MSB linux-3.16.2-gentoo kernel-headers-3.16.0 > glibc-2.19 gcc-4.7.3 > vFAIL: test; s390x 64-bit/MSB linux-3.19.0

Re: Preparing for the next release: call for testing

2015-03-05 Thread Dmitry V. Levin
On Wed, Mar 04, 2015 at 10:55:45PM -0500, Mike Frysinger wrote: > vFAIL: test; s390x 64-bit/MSB linux-3.19.0 kernel-headers-3.16.0 > glibc-2.19 gcc-4.8.3 It's unix-yy.test again with the same issue that looks like a race condition: from time to time, print_sockaddr_by_inode fails t

Re: Preparing for the next release: call for testing

2015-03-04 Thread Mike Frysinger
On 05 Mar 2015 09:03, Dmitry V. Levin wrote: > On Wed, Mar 04, 2015 at 10:55:45PM -0500, Mike Frysinger wrote: > > testing commit a1c5e0721fb679a550ac0cd2c9e231409ebb1e26 (v4.9-391-ga1c5e07) > > > > native (build+tests): > > vFAIL: test; parisc 32-bit/MSB linux-3.16.2-gentoo > > kernel-heade

Re: Preparing for the next release: call for testing

2015-03-04 Thread Dmitry V. Levin
On Wed, Mar 04, 2015 at 10:55:45PM -0500, Mike Frysinger wrote: > testing commit a1c5e0721fb679a550ac0cd2c9e231409ebb1e26 (v4.9-391-ga1c5e07) > > native (build+tests): > vFAIL: test; parisc 32-bit/MSB linux-3.16.2-gentoo kernel-headers-3.16.0 > glibc-2.19 gcc-4.7.3 This is the architectur

Re: Preparing for the next release: call for testing

2015-03-04 Thread Mike Frysinger
On 04 Mar 2015 22:55, Mike Frysinger wrote: > build warnings: also warning on ppc64: signal.c:802:9: warning: array subscript is above array bounds [-Warray-bounds] -mike signature.asc Description: Digital signature -- D

Re: Preparing for the next release: call for testing

2015-03-04 Thread Mike Frysinger
testing commit a1c5e0721fb679a550ac0cd2c9e231409ebb1e26 (v4.9-391-ga1c5e07) native (build+tests): vFAIL: test; parisc 32-bit/MSB linux-3.16.2-gentoo kernel-headers-3.16.0 glibc-2.19 gcc-4.7.3 vFAIL: test; s390x 64-bit/MSB linux-3.19.0 kernel-headers-3.16.0 glibc-2.19 gcc-4.

Re: Preparing for the next release: call for testing

2015-03-04 Thread Dmitry V. Levin
On Tue, Mar 03, 2015 at 12:47:19PM -0500, Mike Frysinger wrote: > tl;dr: lets ship it I've made a few fixes in sigreturn/rt_sigreturn signal mask decoding. It was more or less broken on ia64, ppc, ppc64, sparc, sparc64, mips, and s390. It was not implemented on x86_64, x32, and aarch64. Now it

Re: Preparing for the next release: call for testing

2015-03-03 Thread Gabriel Laskar
On Wed, 4 Mar 2015 02:44:19 +0300 "Dmitry V. Levin" wrote: > On Tue, Mar 03, 2015 at 07:23:28PM +0100, Gabriel Laskar wrote: > > There is still an issue with ioctl request names when using strace > > on Binder calls. Some binder calls have 2 possible sizes, depending > > of being with the 32-bit

Re: Preparing for the next release: call for testing

2015-03-03 Thread Dmitry V. Levin
On Tue, Mar 03, 2015 at 07:23:28PM +0100, Gabriel Laskar wrote: > There is still an issue with ioctl request names when using strace on > Binder calls. Some binder calls have 2 possible sizes, depending of being > with the 32-bit api or the 64-bit one. > > In , there is a #ifdef BINDER_IPC_32BIT t

Re: Preparing for the next release: call for testing

2015-03-03 Thread Mike Frysinger
On 03 Mar 2015 21:46, Dmitry V. Levin wrote: > On Tue, Mar 03, 2015 at 01:23:53PM -0500, Mike Frysinger wrote: > > On 03 Mar 2015 21:01, Dmitry V. Levin wrote: > > > On Tue, Mar 03, 2015 at 12:47:19PM -0500, Mike Frysinger wrote: > > > > build warnings: > > > > there's still random -Wsign-compare w

Re: Preparing for the next release: call for testing

2015-03-03 Thread Dmitry V. Levin
On Tue, Mar 03, 2015 at 01:23:53PM -0500, Mike Frysinger wrote: > On 03 Mar 2015 21:01, Dmitry V. Levin wrote: > > On Tue, Mar 03, 2015 at 12:47:19PM -0500, Mike Frysinger wrote: > > > build warnings: > > > there's still random -Wsign-compare warnings, but i guess we don't care > > > about those >

Re: Preparing for the next release: call for testing

2015-03-03 Thread Mike Frysinger
On 03 Mar 2015 21:01, Dmitry V. Levin wrote: > On Tue, Mar 03, 2015 at 12:47:19PM -0500, Mike Frysinger wrote: > > build warnings: > > there's still random -Wsign-compare warnings, but i guess we don't care > > about those > > There are exactly 3 different -Wsign-compare warning messages: > socket

Re: Preparing for the next release: call for testing

2015-03-03 Thread Gabriel Laskar
On Wed, 25 Feb 2015 05:12:57 +0300 "Dmitry V. Levin" wrote: > I think it's time to cut a new release. > If you have pending patches to include before the release, > please submit them now. There is still an issue with ioctl request names when using strace on Binder calls. Some binder calls have

Re: Preparing for the next release: call for testing

2015-03-03 Thread Dmitry V. Levin
On Tue, Mar 03, 2015 at 12:47:19PM -0500, Mike Frysinger wrote: > build warnings: > there's still random -Wsign-compare warnings, but i guess we don't care > about those There are exactly 3 different -Wsign-compare warning messages: socketutils.c:145: warning: comparison between signed and unsigne

Re: Preparing for the next release: call for testing

2015-03-03 Thread Mike Frysinger
tl;dr: lets ship it testing commit 600eafb6edcb89d6d602073edae97089c0a1e41a (v4.9-373-g600eafb) native (build+tests): vPASS: alpha 64-bit/LSB linux-3.18.1 kernel-headers-3.19.0 glibc-2.20 gcc-4.9.2 vPASS: armv7l 32-bit/LSB linux-3.4.0-vapierkernel-headers-3.16.0 glibc-2.1

Re: Preparing for the next release: call for testing

2015-03-02 Thread Mike Frysinger
On 03 Mar 2015 03:20, Dmitry V. Levin wrote: > OK, would you like to prepare commits for pc and ipc_sem tests? OK -mike signature.asc Description: Digital signature -- Dive into the World of Parallel Programming The Go P

Re: Preparing for the next release: call for testing

2015-03-02 Thread Dmitry V. Levin
On Mon, Mar 02, 2015 at 07:03:16PM -0500, Mike Frysinger wrote: > On 03 Mar 2015 01:30, Dmitry V. Levin wrote: > > On Mon, Mar 02, 2015 at 05:26:37PM -0500, Mike Frysinger wrote: > > > On 03 Mar 2015 00:44, Dmitry V. Levin wrote: > > > > On Mon, Mar 02, 2015 at 04:13:07PM -0500, Mike Frysinger wrot

Re: Preparing for the next release: call for testing

2015-03-02 Thread Mike Frysinger
On 03 Mar 2015 01:30, Dmitry V. Levin wrote: > On Mon, Mar 02, 2015 at 05:26:37PM -0500, Mike Frysinger wrote: > > On 03 Mar 2015 00:44, Dmitry V. Levin wrote: > > > On Mon, Mar 02, 2015 at 04:13:07PM -0500, Mike Frysinger wrote: > > > > --- a/tests/pc.c > > > > +++ b/tests/pc.c > > > > @@ -12,6 +1

Re: Preparing for the next release: call for testing

2015-03-02 Thread Dmitry V. Levin
On Mon, Mar 02, 2015 at 05:26:37PM -0500, Mike Frysinger wrote: > On 03 Mar 2015 00:44, Dmitry V. Levin wrote: > > On Mon, Mar 02, 2015 at 04:13:07PM -0500, Mike Frysinger wrote: > > > --- a/tests/pc.c > > > +++ b/tests/pc.c > > > @@ -12,6 +12,14 @@ int main(void) > > > { > > > const unsigned lo

Re: Preparing for the next release: call for testing

2015-03-02 Thread Mike Frysinger
On 03 Mar 2015 00:44, Dmitry V. Levin wrote: > On Mon, Mar 02, 2015 at 04:13:07PM -0500, Mike Frysinger wrote: > > --- a/tests/pc.c > > +++ b/tests/pc.c > > @@ -12,6 +12,14 @@ int main(void) > > { > > const unsigned long pagesize = sysconf(_SC_PAGESIZE); > > > > +#ifdef __s390__ > > + /* >

Re: Preparing for the next release: call for testing

2015-03-02 Thread Dmitry V. Levin
On Mon, Mar 02, 2015 at 04:13:07PM -0500, Mike Frysinger wrote: > On 02 Mar 2015 22:22, Dmitry V. Levin wrote: > > On Mon, Mar 02, 2015 at 12:04:27PM -0500, Mike Frysinger wrote: > > > On 02 Mar 2015 14:31, Dmitry V. Levin wrote: > > > > On s390, besides kernel bug with si_addr, all printed instruc

Re: Preparing for the next release: call for testing

2015-03-02 Thread Mike Frysinger
On 02 Mar 2015 23:05, Dmitry V. Levin wrote: > On Mon, Mar 02, 2015 at 12:42:45AM -0500, Mike Frysinger wrote: > [...] > > vFAIL: test; ppc/32-bit/MSB linux-3.12.20-gentoo kernel-headers-3.13.0 > > glibc-2.21 gcc-4.8.4 > > kernel bug w/ipc > > vFAIL: test; sparc/32-bit/MSB linux-3.17.

Re: Preparing for the next release: call for testing

2015-03-02 Thread Mike Frysinger
On 02 Mar 2015 22:22, Dmitry V. Levin wrote: > On Mon, Mar 02, 2015 at 12:04:27PM -0500, Mike Frysinger wrote: > > On 02 Mar 2015 14:31, Dmitry V. Levin wrote: > > > On s390, besides kernel bug with si_addr, all printed instruction pointers > > > have 0x8000 bit set. If it isn't a kernel bug (

Re: Preparing for the next release: call for testing

2015-03-02 Thread Mike Frysinger
On 02 Mar 2015 22:42, Dmitry V. Levin wrote: > On Mon, Mar 02, 2015 at 12:04:27PM -0500, Mike Frysinger wrote: > > On 02 Mar 2015 14:31, Dmitry V. Levin wrote: > > > On Mon, Mar 02, 2015 at 12:42:45AM -0500, Mike Frysinger wrote: > > > > - x32 statfs tracing of x86 binaries fails ? > > > > > > I'

Re: Preparing for the next release: call for testing

2015-03-02 Thread Dmitry V. Levin
On Mon, Mar 02, 2015 at 12:42:45AM -0500, Mike Frysinger wrote: [...] > vFAIL: test; ppc/32-bit/MSB linux-3.12.20-gentoo kernel-headers-3.13.0 > glibc-2.21 gcc-4.8.4 > kernel bug w/ipc > vFAIL: test; sparc/32-bit/MSB linux-3.17.2 kernel-headers-3.13.0 glibc-2.19 > gcc-4.7.3 >

Re: Preparing for the next release: call for testing

2015-03-02 Thread Dmitry V. Levin
On Mon, Mar 02, 2015 at 12:04:27PM -0500, Mike Frysinger wrote: > On 02 Mar 2015 14:31, Dmitry V. Levin wrote: > > On Mon, Mar 02, 2015 at 12:42:45AM -0500, Mike Frysinger wrote: > > > - x32 statfs tracing of x86 binaries fails ? > > > > I'd like to see the log. There are two test-suite.log file

Re: Preparing for the next release: call for testing

2015-03-02 Thread Dmitry V. Levin
On Mon, Mar 02, 2015 at 12:04:27PM -0500, Mike Frysinger wrote: > On 02 Mar 2015 14:31, Dmitry V. Levin wrote: > > On s390, besides kernel bug with si_addr, all printed instruction pointers > > have 0x8000 bit set. If it isn't a kernel bug (and it doesn't look like > > one), then it's a strace

Re: Preparing for the next release: call for testing

2015-03-02 Thread Mike Frysinger
On 02 Mar 2015 14:31, Dmitry V. Levin wrote: > On Mon, Mar 02, 2015 at 12:42:45AM -0500, Mike Frysinger wrote: > > - x32 statfs tracing of x86 binaries fails ? > > I'd like to see the log. There are two test-suite.log files on x32, > but only tests/test-suite.log is printed. FAIL: statfs ==

Re: Preparing for the next release: call for testing

2015-03-02 Thread Mike Frysinger
On 02 Mar 2015 18:13, Dmitry V. Levin wrote: > On Mon, Mar 02, 2015 at 02:31:51PM +0300, Dmitry V. Levin wrote: > > On Mon, Mar 02, 2015 at 12:42:45AM -0500, Mike Frysinger wrote: > > > - x32 sysinfo.c has type warnings > > The fix seems to be as simple as "sed -i s/%l/%j/g sysinfo.c". > > No, %j

Re: Preparing for the next release: call for testing

2015-03-02 Thread Dmitry V. Levin
On Mon, Mar 02, 2015 at 02:31:51PM +0300, Dmitry V. Levin wrote: > On Mon, Mar 02, 2015 at 12:42:45AM -0500, Mike Frysinger wrote: > > - x32 sysinfo.c has type warnings > The fix seems to be as simple as "sed -i s/%l/%j/g sysinfo.c". No, %ju is not a correct fix for 32-bit architectures, I had to

Re: Preparing for the next release: call for testing

2015-03-02 Thread Dmitry V. Levin
On Mon, Mar 02, 2015 at 12:42:45AM -0500, Mike Frysinger wrote: > i think the things blocking the release now: > - net-yy/unix-yy bugs that alpha is hitting There are also some strace vs netlink races in these *-yy tests, I see them failing on x86_64 from time to time. > - x32 sysinfo.c has typ

Re: Preparing for the next release: call for testing

2015-03-01 Thread Mike Frysinger
i think the things blocking the release now: - net-yy/unix-yy bugs that alpha is hitting - x32 sysinfo.c has type warnings - x32 statfs tracing of x86 binaries fails ? -mike testing commit d819fe88fb28a93af40ca0fea3ca4e610c1edb90 (v4.9-364-gd819fe8) native (build+tests): vFAIL: test; alpha/64-

Re: Preparing for the next release: call for testing

2015-03-01 Thread Mike Frysinger
On 02 Mar 2015 02:37, Dmitry V. Levin wrote: > Can we fix all these issues by ignoring > getresuid results in subsequent calls? hmm, that also works. there needs to be a comment in there so people don't try to clean it up/optimize, but otherwise an easy way to ignore the problem. :) -mike sig

Re: Preparing for the next release: call for testing

2015-03-01 Thread Dmitry V. Levin
On Sun, Mar 01, 2015 at 02:56:41AM -0500, Mike Frysinger wrote: > but uid is not as easy because __NR_getuid might operate on 32bits in which > case > you'd corrupt vars on the stack. you could work around it by doing: > --- a/tests/uid.c > +++ b/tests/uid.c > @@ -16,15 +16,19 @@ main(void) >

Re: Preparing for the next release: call for testing

2015-02-28 Thread Mike Frysinger
On 27 Feb 2015 01:06, Mike Frysinger wrote: > vFAIL: test; s390/32-bit/MSB linux-3.18.1 kernel-headers-3.16.0 glibc-2.19 > gcc-4.8.3 > FAIL: uid > FAIL: uid16 these tests fail because: - s390 is old enough to have "real" 16bit uid syscalls - the tests are using 32bit values (int instead of shor

Re: Preparing for the next release: call for testing

2015-02-28 Thread Dmitry V. Levin
On Fri, Feb 27, 2015 at 01:06:22AM -0500, Mike Frysinger wrote: > vFAIL: test; sparc/32-bit/MSB linux-3.17.2 kernel-headers-3.13.0 glibc-2.19 > gcc-4.7.3 > FAIL: sigaction Fixed by commit 24b8eb0deebdf25e957854e065c11d0086c824d5. -- ldv pgpLpG4XDzLni.pgp Description: PGP signature --

Re: Preparing for the next release: call for testing

2015-02-28 Thread Dmitry V. Levin
On Fri, Feb 27, 2015 at 01:06:22AM -0500, Mike Frysinger wrote: > vFAIL: build; m68k/32-bit/MSB cross kernel-headers-3.19.0 glibc-2.21 gcc-4.8.0 This should be fixed by commit 7211dbcb2f8a43eb5d36bd15c7ba1267ba21e223. -- ldv pgpzLLq_tJZgI.pgp Description: PGP signature ---

Re: Preparing for the next release: call for testing

2015-02-26 Thread Mike Frysinger
On 27 Feb 2015 01:06, Mike Frysinger wrote: > i'll look into the ppc/sparc ipc_sem failures. i suspect it's a > kernel/system > config thing we need to test for and SKIP. in both cases it's a 32bit prog running under a 64bit kernel. i suspect the kernel is broken but no one noticed because wh

Re: Preparing for the next release: call for testing

2015-02-26 Thread Mike Frysinger
would help if i attached the logs ;) -mike logs.tar.xz Description: application/xz signature.asc Description: Digital signature -- Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel

Re: Preparing for the next release: call for testing

2015-02-26 Thread Mike Frysinger
the sh4 failure looks like a race probably due to a loaded system. i re-ran the one failing test when it was quiet and it passed. i'll look into the ppc/sparc ipc_sem failures. i suspect it's a kernel/system config thing we need to test for and SKIP. testing commit d32e1b9dde3fdbd723a672549d

Re: Preparing for the next release: call for testing

2015-02-26 Thread Mike Frysinger
On 27 Feb 2015 07:52, Dmitry V. Levin wrote: > On Thu, Feb 26, 2015 at 11:31:59PM -0500, Mike Frysinger wrote: > > On 27 Feb 2015 05:30, Dmitry V. Levin wrote: > > > On Thu, Feb 26, 2015 at 05:56:43PM -0500, Mike Frysinger wrote: > > > > detach-stopped.test.tmp contains just this: > > > > Process 1

Re: Preparing for the next release: call for testing

2015-02-26 Thread Dmitry V. Levin
On Thu, Feb 26, 2015 at 01:10:39AM -0500, Mike Frysinger wrote: > vFAIL: test; ppc64/64-bit/MSB linux-3.12.20-gentoo kernel-headers-3.9.0 > glibc-2.17 gcc-4.7.3 This is a test issue; hopefully fixed by commits 977550de794baac058d4368682167fcbebbdf653 and 856b7596b83d70d6e7e27eef56fa7b92a0dac4af.

Re: Preparing for the next release: call for testing

2015-02-26 Thread Dmitry V. Levin
On Thu, Feb 26, 2015 at 11:31:59PM -0500, Mike Frysinger wrote: > On 27 Feb 2015 05:30, Dmitry V. Levin wrote: > > On Thu, Feb 26, 2015 at 05:56:43PM -0500, Mike Frysinger wrote: > > > detach-stopped.test.tmp contains just this: > > > Process 1267 attached > > > restart_syscall(<... resuming interr

Re: Preparing for the next release: call for testing

2015-02-26 Thread Mike Frysinger
On 27 Feb 2015 05:30, Dmitry V. Levin wrote: > On Thu, Feb 26, 2015 at 05:56:43PM -0500, Mike Frysinger wrote: > > detach-stopped.test.tmp contains just this: > > Process 1267 attached > > restart_syscall(<... resuming interrupted call ...> > > That is, either "kill -STOP" failed to stop "sleep" o

Re: Preparing for the next release: call for testing

2015-02-26 Thread Dmitry V. Levin
On Thu, Feb 26, 2015 at 05:56:43PM -0500, Mike Frysinger wrote: > On 27 Feb 2015 01:23, Dmitry V. Levin wrote: > > On Thu, Feb 26, 2015 at 01:10:39AM -0500, Mike Frysinger wrote: > > > vFAIL: test; i686/32-bit/LSB linux-3.18.4 kernel-headers-3.3.0 glibc-2.17 > > > gcc-4.7.2 > > > > I'd like to kn

Re: Preparing for the next release: call for testing

2015-02-26 Thread Mike Frysinger
On 26 Feb 2015 01:10, Mike Frysinger wrote: > probably can ignore the superh failure too as that looks like a build system > issue. that was due to the fork bombing in the xlat script. once that was fixed, superh compiled cleanly & passed its tests. -mike signature.asc Description: Digital si

Re: Preparing for the next release: call for testing

2015-02-26 Thread Mike Frysinger
On 27 Feb 2015 01:23, Dmitry V. Levin wrote: > On Thu, Feb 26, 2015 at 01:10:39AM -0500, Mike Frysinger wrote: > > vFAIL: test; i686/32-bit/LSB linux-3.18.4 kernel-headers-3.3.0 glibc-2.17 > > gcc-4.7.2 > > I'd like to know how to reproduce this. this is just a standard 32-bit x86 userland syste

Re: Preparing for the next release: call for testing

2015-02-26 Thread Dmitry V. Levin
On Thu, Feb 26, 2015 at 01:10:39AM -0500, Mike Frysinger wrote: > vFAIL: test; i686/32-bit/LSB linux-3.18.4 kernel-headers-3.3.0 glibc-2.17 > gcc-4.7.2 I'd like to know how to reproduce this. -- ldv pgpdMcNKgs_2V.pgp Description: PGP signature

Re: Preparing for the next release: call for testing

2015-02-26 Thread Dmitry V. Levin
On Thu, Feb 26, 2015 at 01:10:39AM -0500, Mike Frysinger wrote: > vFAIL: build; x86_64/32-bit/LSB linux-3.18.4 kernel-headers-3.19.0 glibc-2.21 > gcc-4.9.2 The build was broken; hopefully fixed by commit 19fcb27764f1b6040d7c50739a26f401aa576f38. -- ldv pgpn45h8B0dyi.pgp Description: PGP sign

Re: Preparing for the next release: call for testing

2015-02-26 Thread Dmitry V. Levin
On Thu, Feb 26, 2015 at 01:10:39AM -0500, Mike Frysinger wrote: > a few signed warnings have crept in: > socketutils.c: In function 'receive_responses': > socketutils.c:145:110: warning: comparison between signed and unsigned > integer expressions [-Wsign-compare] > netlink_inet_diag.c: In f

Re: Preparing for the next release: call for testing

2015-02-25 Thread Mike Frysinger
time for another grind ;). straight out of the gate is a bit rough. a few signed warnings have crept in: socketutils.c: In function 'receive_responses': socketutils.c:145:110: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] netlink_inet_diag.c: In funct