Trace number 2066831

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-restart 0.3.2SAT 0.26196 0.278269

DiagnosticValue
ASSIGNMENTS8

General information on the benchmark

Namecsp/pseudo/jnh/
normalized-jnh-12.xml
MD5SUMf9b1b275942b11de473142ed678dd166
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.26196
Satisfiable
(Un)Satisfiability was proved
Number of variables200
Number of constraints950
Maximum constraint arity11
Maximum domain size2
Number of constraints which are defined in extension0
Number of constraints which are defined in intension950
Global constraints used (with number of constraints)

Solver Data 

0.00/0.02	c has operations which may create big domains
0.00/0.02	c big-domain mode
0.00/0.02	c Seed is 1869012861
0.00/0.02	c Constructing HOME/instance-2066831-1247705194.xml  with 4571 constraints
0.04/0.10	c Solving 8 backtracks
0.17/0.27	s SATISFIABLE
0.17/0.27	c V0=1, V1=0, V2=0, V3=1, V4=0, V5=1, V6=0, V7=1, V8=1, V9=0, V10=1, V11=0, V12=1, V13=0, V14=0, V15=1, V16=1, V17=0, V18=0, V19=1, V20=0, V21=1, V22=0, V23=1, V24=0, V25=1, V26=0, V27=1, V28=1, V29=0, V30=0, V31=1, V32=1, V33=0, V34=1, V35=0, V36=1, V37=0, V38=1, V39=0, V40=0, V41=1, V42=0, V43=1, V44=0, V45=1, V46=0, V47=1, V48=0, V49=1, V50=0, V51=1, V52=1, V53=0, V54=1, V55=0, V56=1, V57=0, V58=0, V59=1, V60=0, V61=1, V62=0, V63=1, V64=1, V65=0, V66=1, V67=0, V68=1, V69=0, V70=1, V71=0, V72=1, V73=0, V74=0, V75=1, V76=0, V77=1, V78=1, V79=0, V80=0, V81=1, V82=1, V83=0, V84=1, V85=0, V86=1, V87=0, V88=0, V89=1, V90=1, V91=0, V92=0, V93=1, V94=0, V95=1, V96=1, V97=0, V98=0, V99=1, V100=1, V101=0, V102=0, V103=1, V104=1, V105=0, V106=1, V107=0, V108=1, V109=0, V110=1, V111=0, V112=1, V113=0, V114=0, V115=1, V116=1, V117=0, V118=0, V119=1, V120=0, V121=1, V122=1, V123=0, V124=0, V125=1, V126=1, V127=0, V128=0, V129=1, V130=1, V131=0, V132=0, V133=1, V134=1, V135=0, V136=0, V137=1, V138=0, V139=1, V140=0, V141=1, V142=1, V143=0, V144=0, V145=1, V146=0, V147=1, V148=1, V149=0, V150=1, V151=0, V152=1, V153=0, V154=1, V155=0, V156=0, V157=1, V158=0, V159=0, V160=1, V161=0, V162=1, V163=0, V164=0, V165=1, V166=1, V167=0, V168=1, V169=0, V170=0, V171=1, V172=1, V173=0, V174=0, V175=1, V176=0, V177=0, V178=1, V179=0, V180=1, V181=0, V182=1, V183=0, V184=1, V185=0, V186=0, V187=1, V188=0, V189=1, V190=1, V191=0, V192=1, V193=0, V194=1, V195=0, V196=0, V197=1, V198=1, V199=0, 
0.17/0.27	v 1 0 0 1 0 1 0 1 1 0 1 0 1 0 0 1 1 0 0 1 0 1 0 1 0 1 0 1 1 0 0 1 1 0 1 0 1 0 1 0 0 1 0 1 0 1 0 1 0 1 0 1 1 0 1 0 1 0 0 1 0 1 0 1 1 0 1 0 1 0 1 0 1 0 0 1 0 1 1 0 0 1 1 0 1 0 1 0 0 1 1 0 0 1 0 1 1 0 0 1 1 0 0 1 1 0 1 0 1 0 1 0 1 0 0 1 1 0 0 1 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 0 1 0 1 1 0 0 1 0 1 1 0 1 0 1 0 1 0 0 1 0 0 1 0 1 0 0 1 1 0 1 0 0 1 1 0 0 1 0 0 1 0 1 0 1 0 1 0 0 1 0 1 1 0 1 0 1 0 0 1 1 0 
0.17/0.27	d ASSIGNMENTS 8

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-2066831-1247705194/watcher-2066831-1247705194 -o /tmp/evaluation-result-2066831-1247705194/solver-2066831-1247705194 -C 1800 -W 2000 -M 900 HOME/pcssolve -s 1869012861 HOME/instance-2066831-1247705194.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: 1.93 1.98 1.99 4/81 16918
/proc/meminfo: memFree=1079328/2055920 swapFree=4192812/4192956
[pid=16918] ppid=16916 vsize=18576 CPUtime=0
/proc/16918/stat : 16918 (runsolver) R 16916 16918 15492 0 -1 4194368 15 0 0 0 0 0 0 0 18 0 1 0 57583329 19021824 284 996147200 4194304 4302564 548682068496 18446744073709551615 221954764071 0 0 4096 24578 0 0 0 17 1 0 0
/proc/16918/statm: 4644 284 249 26 0 2626 0

[startup+0.0775701 s]
/proc/loadavg: 1.93 1.98 1.99 4/81 16918
/proc/meminfo: memFree=1079328/2055920 swapFree=4192812/4192956
[pid=16918] ppid=16916 vsize=5508 CPUtime=0.04
/proc/16918/stat : 16918 (pcs.big) R 16916 16918 15492 0 -1 4194304 1042 826 0 0 4 0 0 0 22 0 1 0 57583329 5640192 651 996147200 134512640 135215973 4294956304 18446744073709551615 2413123 0 0 4096 0 0 0 0 17 0 0 0
/proc/16918/statm: 1377 651 385 171 0 302 0
Current children cumulated CPU time (s) 0.04
Current children cumulated vsize (KiB) 5508

[startup+0.102555 s]
/proc/loadavg: 1.93 1.98 1.99 4/81 16918
/proc/meminfo: memFree=1079328/2055920 swapFree=4192812/4192956
[pid=16918] ppid=16916 vsize=6464 CPUtime=0.07
/proc/16918/stat : 16918 (pcs.big) R 16916 16918 15492 0 -1 4194304 1291 826 0 0 7 0 0 0 22 0 1 0 57583329 6619136 829 996147200 134512640 135215973 4294956304 18446744073709551615 134635363 0 0 4096 0 0 0 0 17 0 0 0
/proc/16918/statm: 1616 829 396 171 0 541 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 6464

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

[startup+0.201587 s]
/proc/loadavg: 1.93 1.98 1.99 4/81 16918
/proc/meminfo: memFree=1079328/2055920 swapFree=4192812/4192956
[pid=16918] ppid=16916 vsize=7736 CPUtime=0.17
/proc/16918/stat : 16918 (pcs.big) R 16916 16918 15492 0 -1 4194304 1816 826 0 0 16 1 0 0 23 0 1 0 57583329 7921664 1189 996147200 134512640 135215973 4294956304 18446744073709551615 134641143 0 0 4096 0 0 0 0 17 0 0 0
/proc/16918/statm: 1934 1189 410 171 0 859 0
Current children cumulated CPU time (s) 0.17
Current children cumulated vsize (KiB) 7736

Child status: 0
Real time (s): 0.278269
CPU time (s): 0.26196
CPU user time (s): 0.235964
CPU system time (s): 0.025996
CPU usage (%): 94.1392
Max. virtual memory (cumulated for all children) (KiB): 7736

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.235964
system time used= 0.025996
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 3044
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= 22
involuntary context switches= 17

runsolver used 0.000999 second user time and 0.009998 second system time

The end

Launcher Data 

Begin job on node43 at 2009-07-16 02:46:34
IDJOB=2066831
IDBENCH=54579
IDSOLVER=734
FILE ID=node43/2066831-1247705194
PBS_JOBID= 9521224
Free space on /tmp= 66192 MiB

SOLVER NAME= pcs-restart 0.2.restart
BENCH NAME= CPAI08/csp/pseudo/jnh/normalized-jnh-12.xml
COMMAND LINE= HOME/pcssolve -s RANDOMSEED BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2066831-1247705194/watcher-2066831-1247705194 -o /tmp/evaluation-result-2066831-1247705194/solver-2066831-1247705194 -C 1800 -W 2000 -M 900  HOME/pcssolve -s 1869012861 HOME/instance-2066831-1247705194.xml

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

MD5SUM BENCH= f9b1b275942b11de473142ed678dd166
RANDOM SEED=1869012861

node43.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.213
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	: 5931.00
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.213
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:       1079808 kB
Buffers:         97372 kB
Cached:         689660 kB
SwapCached:          0 kB
Active:         223504 kB
Inactive:       650484 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1079808 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            2476 kB
Writeback:           0 kB
Mapped:         107456 kB
Slab:            87056 kB
Committed_AS:   631896 kB
PageTables:       2052 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= 66192 MiB
End job on node43 at 2009-07-16 02:46:35