Trace number 2078028

Some explanations

A solver is run under the control of another program named runsolver. runsolver is in charge of imposing the CPU time limit and the memory limit to the solver. It also monitors some information about the process. The trace of the execution of a solver is divided into four (or five) parts:
  1. SOLVER DATA
    This is the output of the solver (stdout and stderr).
    Note that some very long lines in this section may be truncated by your web browser ! In such a case, you may want to use the "Download as text" link to get the trace as a text file.

    When the --timestamp option is passed to the runsolver program, each line output by the solver is prepended with a timestamp which indicates at what time the line was output by the solver. Times are relative to the start of the program, given in seconds. The first timestamp (if present) is estimated CPU time. The last timestamp is wall clock time.

    As some 'v lines' may be very long (sometimes several megabytes), the 'v line' output by your solver may be split on several lines to help limit the size of the trace recorded in the database. In any case, the exact output of your solver is preserved in a trace file.
  2. VERIFIER DATA
    The output of the solver is piped to a verifier program which will search a value line "v " and, if found, will check that the given interpretation satisfies all constraints.
  3. CONVERSION SCRIPT DATA (Optionnal)
    When a conversion script is used, this section shows the messages that were output by the conversion script.
  4. WATCHER DATA
    This is the informations gathered by the runsolver program. It first prints the different limits. There's a first limit on CPU time set to X seconds (see the parameters in the trace). After this time has ellapsed, runsolver sends a SIGTERM and 2 seconds later a SIGKILL to the solver. For safety, there's also another limit set to X+30 seconds which will send a SIGXPU to the solver. The last limit is on the virtual memory used by the process (see the parameters in the trace).
    Every ten seconds, the runsolver process fetches the content of /proc/loadavg, /proc/pid/stat and /proc/pid/statm (see man proc) and prints it as raw data. This is only recorded in case we need to investigate the behaviour of a solver. The memory used by the solver (vsize) is also given every ten seconds.
    When the solver exits, runsolver prints some informations such as status and time. CPU usage is the ratio CPU Time/Real Time.
  5. LAUNCHER DATA
    These informations are related to the script which will launch the solver. The most important informations are the command line given to the solver, the md5sum of the different files and the dump of the /proc/cpuinfo and /proc/meminfo which provides some useful information on the computer.

Solver answer on this benchmark

Solver NameAnswerCPU timeWall clock time
pcs 0.3.2SAT 0.759884 0.767336

DiagnosticValue
ASSIGNMENTS392

General information on the benchmark

Namecsp/primes-10/
normalized-primes-10-20-3-7.xml
MD5SUMc5e0394aaf730075c7f89be7c81fb5bb
Bench CategoryN-ARY-INT (n-ary constraints in intension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.014997
Satisfiable
(Un)Satisfiability was proved
Number of variables100
Number of constraints20
Maximum constraint arity10
Maximum domain size28
Number of constraints which are defined in extension0
Number of constraints which are defined in intension20
Global constraints used (with number of constraints)

Solver Data 

0.00/0.01	c has operations which may create big domains
0.00/0.01	c big-domain mode
0.18/0.21	c Seed is 847199513
0.18/0.21	c Constructing HOME/instance-2078028-1247716090.xml  with 278 constraints
0.18/0.21	c Solving 392 backtracks 6 restarts
0.68/0.76	s SATISFIABLE
0.68/0.76	c V0=29, V1=28, V2=29, V3=29, V4=22, V5=21, V6=16, V7=15, V8=14, V9=3, V10=23, V11=29, V12=3, V13=16, V14=2, V15=29, V16=2, V17=29, V18=6, V19=2, V20=5, V21=18, V22=12, V23=29, V24=18, V25=29, V26=2, V27=29, V28=17, V29=29, V30=2, V31=2, V32=4, V33=29, V34=29, V35=20, V36=5, V37=5, V38=14, V39=26, V40=20, V41=13, V42=14, V43=28, V44=2, V45=29, V46=2, V47=29, V48=10, V49=19, V50=2, V51=29, V52=27, V53=2, V54=2, V55=2, V56=5, V57=9, V58=5, V59=2, V60=22, V61=2, V62=6, V63=29, V64=2, V65=2, V66=29, V67=28, V68=7, V69=29, V70=10, V71=29, V72=29, V73=29, V74=25, V75=29, V76=2, V77=3, V78=2, V79=4, V80=2, V81=28, V82=28, V83=29, V84=3, V85=29, V86=3, V87=9, V88=27, V89=29, V90=29, V91=2, V92=29, V93=29, V94=23, V95=29, V96=13, V97=29, V98=2, V99=28, 
0.68/0.76	v 29 28 29 29 22 21 16 15 14 3 23 29 3 16 2 29 2 29 6 2 5 18 12 29 18 29 2 29 17 29 2 2 4 29 29 20 5 5 14 26 20 13 14 28 2 29 2 29 10 19 2 29 27 2 2 2 5 9 5 2 22 2 6 29 2 2 29 28 7 29 10 29 29 29 25 29 2 3 2 4 2 28 28 29 3 29 3 9 27 29 29 2 29 29 23 29 13 29 2 28 
0.68/0.76	d ASSIGNMENTS 392

Verifier Data 

OK

Watcher Data 

runsolver version 3.2.9 (svn:492) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2078028-1247716090/watcher-2078028-1247716090 -o /tmp/evaluation-result-2078028-1247716090/solver-2078028-1247716090 -C 1800 -W 2000 -M 900 HOME/pcssolve -s 847199513 HOME/instance-2078028-1247716090.xml 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 2000 seconds
Enforcing VSIZE limit (soft limit, will send SIGTERM then SIGKILL): 921600 KiB
Enforcing VSIZE limit (hard limit, stack expansion will fail with SIGSEGV, brk() and mmap() will return ENOMEM): 972800 KiB
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 2.18 2.19 2.16 4/81 12357
/proc/meminfo: memFree=824888/2055920 swapFree=4192812/4192956
[pid=12357] ppid=12355 vsize=5356 CPUtime=0
/proc/12357/stat : 12357 (pcssolve) R 12355 12357 10722 0 -1 4194304 273 0 0 0 0 0 0 0 20 0 1 0 58672017 5484544 241 996147200 4194304 4889804 548682068800 18446744073709551615 271894243999 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/12357/statm: 1339 241 200 169 0 50 0
[pid=12358] ppid=12357 vsize=5356 CPUtime=0
/proc/12358/stat : 12358 (pcssolve) R 12357 12357 10722 0 -1 4194368 0 0 0 0 0 0 0 0 20 0 1 0 58672018 5484544 241 996147200 4194304 4889804 548682068800 18446744073709551615 271894243999 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/12358/statm: 1339 241 200 169 0 50 0

[startup+0.098283 s]
/proc/loadavg: 2.18 2.19 2.16 4/81 12357
/proc/meminfo: memFree=824888/2055920 swapFree=4192812/4192956
[pid=12357] ppid=12355 vsize=4960 CPUtime=0.07
/proc/12357/stat : 12357 (pcs.big) R 12355 12357 10722 0 -1 4194304 949 811 0 0 7 0 0 0 18 0 1 0 58672017 5079040 558 996147200 134512640 135215973 4294956304 18446744073709551615 134611219 0 0 4096 0 0 0 0 17 1 0 0
/proc/12357/statm: 1240 558 415 171 0 165 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 4960

[startup+0.10228 s]
/proc/loadavg: 2.18 2.19 2.16 4/81 12357
/proc/meminfo: memFree=824888/2055920 swapFree=4192812/4192956
[pid=12357] ppid=12355 vsize=4960 CPUtime=0.08
/proc/12357/stat : 12357 (pcs.big) R 12355 12357 10722 0 -1 4194304 949 811 0 0 8 0 0 0 18 0 1 0 58672017 5079040 558 996147200 134512640 135215973 4294956304 18446744073709551615 4159345961 0 0 4096 0 0 0 0 17 1 0 0
/proc/12357/statm: 1240 558 415 171 0 165 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 4960

[startup+0.302299 s]
/proc/loadavg: 2.18 2.19 2.16 4/81 12357
/proc/meminfo: memFree=824888/2055920 swapFree=4192812/4192956
[pid=12357] ppid=12355 vsize=4960 CPUtime=0.28
/proc/12357/stat : 12357 (pcs.big) R 12355 12357 10722 0 -1 4194304 979 811 0 0 28 0 0 0 19 0 1 0 58672017 5079040 588 996147200 134512640 135215973 4294956304 18446744073709551615 134532714 0 0 4096 0 0 0 0 17 1 0 0
/proc/12357/statm: 1240 588 415 171 0 165 0
Current children cumulated CPU time (s) 0.28
Current children cumulated vsize (KiB) 4960

[startup+0.70134 s]
/proc/loadavg: 2.18 2.19 2.16 4/81 12357
/proc/meminfo: memFree=824888/2055920 swapFree=4192812/4192956
[pid=12357] ppid=12355 vsize=5456 CPUtime=0.68
/proc/12357/stat : 12357 (pcs.big) R 12355 12357 10722 0 -1 4194304 1069 811 0 0 68 0 0 0 23 0 1 0 58672017 5586944 678 996147200 134512640 135215973 4294956304 18446744073709551615 134583227 0 0 4096 0 0 0 0 17 1 0 0
/proc/12357/statm: 1364 678 415 171 0 289 0
Current children cumulated CPU time (s) 0.68
Current children cumulated vsize (KiB) 5456

Solver just ended. Dumping a history of the last processes samples

Child status: 0
Real time (s): 0.767336
CPU time (s): 0.759884
CPU user time (s): 0.747886
CPU system time (s): 0.011998
CPU usage (%): 99.0288
Max. virtual memory (cumulated for all children) (KiB): 5456

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.747886
system time used= 0.011998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1882
page faults= 0
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 23
involuntary context switches= 43

runsolver used 0.002999 second user time and 0.007998 second system time

The end

Launcher Data 

Begin job on node60 at 2009-07-16 05:48:10
IDJOB=2078028
IDBENCH=56704
IDSOLVER=733
FILE ID=node60/2078028-1247716090
PBS_JOBID= 9521351
Free space on /tmp= 66428 MiB

SOLVER NAME= pcs 0.2
BENCH NAME= CPAI08/csp/primes-10/normalized-primes-10-20-3-7.xml
COMMAND LINE= HOME/pcssolve -s RANDOMSEED BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2078028-1247716090/watcher-2078028-1247716090 -o /tmp/evaluation-result-2078028-1247716090/solver-2078028-1247716090 -C 1800 -W 2000 -M 900  HOME/pcssolve -s 847199513 HOME/instance-2078028-1247716090.xml

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB
MAX NB THREAD= 0

MD5SUM BENCH= c5e0394aaf730075c7f89be7c81fb5bb
RANDOM SEED=847199513

node60.alineos.net Linux 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005

/proc/cpuinfo:
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 15
model		: 4
model name	:                   Intel(R) Xeon(TM) CPU 3.00GHz
stepping	: 3
cpu MHz		: 3000.232
cache size	: 2048 KB
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5914.62
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 15
model		: 4
model name	:                   Intel(R) Xeon(TM) CPU 3.00GHz
stepping	: 3
cpu MHz		: 3000.232
cache size	: 2048 KB
fpu		: yes
fpu_exception	: yes
cpuid level	: 5
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm pni monitor ds_cpl cid cx16 xtpr
bogomips	: 5586.94
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:        825368 kB
Buffers:         75192 kB
Cached:         366672 kB
SwapCached:          0 kB
Active:         774352 kB
Inactive:       371100 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        825368 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1780 kB
Writeback:           0 kB
Mapped:         723984 kB
Slab:            68676 kB
Committed_AS:  1258660 kB
PageTables:       3404 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264952 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66428 MiB
End job on node60 at 2009-07-16 05:48:11