On Wed, 9 Sep 2015, at 12:45 PM, Craig Small wrote:
> Any chance of getting testsuite/ps.log out of the buildds? It will give
> me exactly what the tester is unhappy about.
Sure - I can always reproduce locally outside all of the, uhh,
reproducible stuff.
(Attached.)
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
Test Run By lamby on Wed Sep 9 12:54:05 2015
Native configuration is x86_64-pc-linux-gnu
=== ps tests ===
Schedule of variations:
unix
Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using ./config/unix.exp as tool-and-target-specific interface file.
Running ./ps.test/ps_output.exp ...
spawn /home/lamby/temp/cdt.20150909125319.AgFh6XRwrb/procps-3.3.10/ps/pscommand -o %cpu,pcpu,%mem,pmem
%CPU %CPU %MEM %MEM
0.0 0.0 0.0 0.0
PASS: ps with output flag %cpu,pcpu,%mem,pmem
spawn /home/lamby/temp/cdt.20150909125319.AgFh6XRwrb/procps-3.3.10/ps/pscommand -o blocked,sig_block,sigmask,caught,sigcatch,sig_catch
BLOCKED BLOCKED BLOCKED CAUGHT CAUGHT CATCHED
0000000000000000 0000000000000000 0000000000000000 00000001f3d1fef9 00000001f3d1fef9 00000001f3d1fef9
PASS: ps with output flag blocked,sig_block,sigmask,caught,sigcatch,sig_catch
spawn /home/lamby/temp/cdt.20150909125319.AgFh6XRwrb/procps-3.3.10/ps/pscommand -o bsdstart,start,lstart
START STARTED STARTED
12:54 12:54:05 Wed Sep 9 12:54:05 2015
PASS: ps with output flag bsdstart,start,lstart
spawn /home/lamby/temp/cdt.20150909125319.AgFh6XRwrb/procps-3.3.10/ps/pscommand -o bsdtime,cputime,etime,etimes
TIME TIME ELAPSED ELAPSED
0:00 00:00:00 00:00 0
PASS: ps with output flag bsdtime,cputime,etime,etimes
spawn /home/lamby/temp/cdt.20150909125319.AgFh6XRwrb/procps-3.3.10/ps/pscommand -o user,ruser,group,rgroup,uid,ruid,gid,rgid
USER RUSER GROUP RGROUP UID RUID GID RGID
lamby lamby lamby lamby 1000 1000 1000 1000
PASS: ps with output flag user,ruser,group,rgroup,uid,ruid,gid,rgid
testcase ./ps.test/ps_output.exp completed in 0 seconds
Running ./ps.test/ps_personality.exp ...
spawn /home/lamby/temp/cdt.20150909125319.AgFh6XRwrb/procps-3.3.10/ps/pscommand
PID TTY STAT TIME COMMAND
1 pts/5 Ss 0:00 /bin/zsh
PASS: ps with bsd personality
spawn /home/lamby/temp/cdt.20150909125319.AgFh6XRwrb/procps-3.3.10/ps/pscommand
PID TTY TIME CMD
10500 pts/6 00:00:00 lt-pscommand
PASS: ps with linux personality
spawn /home/lamby/temp/cdt.20150909125319.AgFh6XRwrb/procps-3.3.10/ps/pscommand
PID TTY STAT TIME COMMAND
1 pts/5 Ss 0:00 /bin/zsh
PASS: ps with old personality
testcase ./ps.test/ps_personality.exp completed in 0 seconds
Running ./ps.test/ps_sched_batch.exp ...
spawn /home/lamby/temp/cdt.20150909125319.AgFh6XRwrb/procps-3.3.10/testsuite/test-schedbatch 18
spawn /home/lamby/temp/cdt.20150909125319.AgFh6XRwrb/procps-3.3.10/ps/pscommand --no-header -o comm,cls,nice -a
zsh TS 0
debuild TS 0
tee TS 0
dpkg-buildpacka TS 0
rules TS 0
dh TS 0
dh_auto_test TS 0
make TS 0
make TS 0
bash TS 0
bash TS 0
make TS 0
make TS 0
bash TS 0
expect TS 0
test-schedbatch B 18
PASS: ps SCHED_BATCH scheduler
UNTESTED: ps SCHED_BATCH scheduler
testcase ./ps.test/ps_sched_batch.exp completed in 0 seconds
=== ps Summary ===
# of expected passes 9
# of untested testcases 1
runtest completed at Wed Sep 9 12:54:05 2015
