Re: Testings on multiple architectures

> I would like to use your work to test strace on every supported architecture > you have since I have some architecture dependent code on the go. Have you any > advice on which repositories I should take? I saw that some of them got > disabled, while others are blocked or unresolvable. Please use

Re: Testings on multiple architectures

> Don't you forgot to tell how one has to add repositories in obs to get strace > tested? If I understood correctly, without adding the correct repositories > the builds don't kick in right? Thanks for the reminder. I forgot to mention that one should add repositories to his project. As for each

Re: Testings on multiple architectures

I'm writing the following blog post as a summarization of my work: https://www.csie.ntu.edu.tw/~yunchih/gsoc/ Here is also a simple step-by-step guide on how to use it: https://www.csie.ntu.edu.tw/~yunchih/gsoc/usage.html I hope these help. This week marks the final week of this year's Go

Testings on multiple architectures

Here is a list of architectures, either listed in "debian/control" or "linux/*", against which I've tested strace: * alpha: Tested on Debian Lenny, kernel:2.6, with old gcc+glibc, failed to boot custom-compiled linux-kernel+busybox * amd64: OBS native support * arm64: OBS native support * armeb: O

failed tests on sparc64

Environment: OS: Debian Wheezy on qemu-system-sparc64 Kernel: 3.2.0-4-sparc64 gcc: 4.7 configured as: CC="/usr/bin/gcc-4.7 -m64" CPPFLAGS="-I/usr/include/sparc-linux-gnu" ./configure --enable-maintainer-mode --build=sparc64-linux-gnu I'm not sure if this is the correct way to build strace on sparc

4 fail cases on mips

Environment: OS: Debian Wheezy on qemu-system-mips64 Kernel: 3.2.0-4-5kc-malta gcc: 4.7 commit hash: b9bc216 4 failed cases: prctl-seccomp-strict, setgid, setgroups, setuid The tests were run multiple times, with identical output. Thanks make check-recursive make[1]: Entering directory `/strace'

Re: Build failure on sparc with gcc4.7

> On Fri, Jul 29, 2016 at 11:00:28PM +0800, Yun-Chih Chen wrote: >> Environment: >> OS: Debian Wheezy on qemu-system-sparc64 >> Kernel: 3.2.0-4-sparc64 >> gcc: 4.7 >> >> strace commit hash: 6d3162acf, configured without --enable-gcc-Werror. >> Becaus

Build failure on sparc with gcc4.7

Environment: OS: Debian Wheezy on qemu-system-sparc64 Kernel: 3.2.0-4-sparc64 gcc: 4.7 strace commit hash: 6d3162acf, configured without --enable-gcc-Werror. Because this error happens on ./linux/sparc64/* , I suspect it is specific to sparc. Any hint on minimum gcc version? Thanks Yunchih -

Re: Preparing for the next release: call for testing

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

[GSOC] Try to run debootstrap+chroot to test strace

Hi, strace community: I am working on this project[1] and have been stuck at some points for a few days. I'm using this script [2] to setup QEMU emulation. i386 was okay. I also tried sparc [3] and mips [4]. It seems that in the case of sparc, with the combination of `debootstrap --arch spar

Re: [GSOC] 4.11, 4.12 build results on Open Build Service

On Tue, Jun 7, 2016 at 5:30 PM, Dmitry V. Levin wrote: > You can base your automation script on make-dist script > (starting with commit v4.12-14-g79ccf43). Thanks! The script is extremely helpful! On Tue, Jun 7, 2016 at 8:56 PM, Jeff Mahoney wrote: > > FYI, the build service can sync from a

Re: [GSOC] 4.11, 4.12 build results on Open Build Service

On Tue, Jun 7, 2016 at 4:11 AM, Dmitry V. Levin wrote: > > Are these files made manually or is there some kind of automation already? > These files are processed as followed: 1. download manually from source 2. run bootstrap.sh 3. manually run `./configure --enable-maintainer-mode`, `make CREDIT

[GSOC] 4.11, 4.12 build results on Open Build Service

Hi, strace community: My name is Yunchih[1], one of Strace's GSOC student this year. I mainly work on testing strace on multiple architectures. Here's [2][3] the result of building strace 4.11, 4.12, respectively, on Open Build Service against multiple platforms, in architectures including

Re: [GSOC] strace testing in docker at travis-ci.org

> My advice: do not run docker. I think this is a setting in the Travis file. > Otherwise the number of indirections becomes a tad too large: > Travis may itself run in VMs -> which runs containers --> in which > your run QEMU > A few too many moving parts IMHO. > > So your goal is to limit th

[GSOC] strace testing in docker at travis-ci.org

Hi, I'm Yun-Chih, working on the GSOC project multi-architecture testing. Here's [1] my attempt to test strace in docker at Travis CI. There are currently eight different architectures. x86_64 is okay; but others come with several issues: 1. armel, armhf, arm64: NO tests succeed

Re: [GSOC] Hello world!

Hi, I had been wondering why QEMU could run into segmentation faults in some architectures. ( and I thought it only happened on me XD ) The docker approach does seem more approachable: first crossbuild using this hub[1], then run the binary with this[2]. I have successfully built+run a hell

[GSOC] Hello world!

Hi, strace community: My name is Yun-Chih Chen. I'm luckily selected by strace to work on multi-architectural testings in GSOC this year. My main goal is to ensure strace get tested on all architectures it supports and make it convenient for our developers to test their code as ear

Some questions about strace workflow.

Hi strace developer, This is Yun-Chih Chen, a sophomore from National Taiwan University who is eager to tackle the "Multi-OS and multiarch continuous tests infrastructure" topic of this year's GSOC. Ever since my last proposal to the mailing list, I've been having some pr