Trace number 2080174

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.143977 0.150458

DiagnosticValue
ASSIGNMENTS33

General information on the benchmark

Namecsp/radar-8-24-3-2/
normalized-radar-8-24-3-2-21.xml
MD5SUM3da7530a420d27bc3a49cbac3ff7f368
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.039993
Satisfiable
(Un)Satisfiability was proved
Number of variables144
Number of constraints64
Maximum constraint arity16
Maximum domain size4
Number of constraints which are defined in extension0
Number of constraints which are defined in intension64
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.00/0.02	c Seed is 975430058
0.00/0.02	c Constructing HOME/instance-2080174-1247717342.xml  with 2244 constraints
0.01/0.06	c Solving 33 backtracks 1 restarts
0.07/0.14	s SATISFIABLE
0.07/0.14	c V0=3, V1=2, V2=0, V3=3, V4=3, V5=3, V6=3, V7=3, V8=3, V9=3, V10=2, V11=3, V12=3, V13=3, V14=3, V15=3, V16=3, V17=3, V18=3, V19=3, V20=0, V21=0, V22=3, V23=3, V24=0, V25=2, V26=2, V27=2, V28=3, V29=0, V30=3, V31=2, V32=3, V33=0, V34=0, V35=3, V36=0, V37=2, V38=0, V39=0, V40=3, V41=0, V42=0, V43=1, V44=3, V45=0, V46=0, V47=1, V48=3, V49=3, V50=3, V51=0, V52=1, V53=1, V54=0, V55=1, V56=3, V57=1, V58=1, V59=0, V60=1, V61=1, V62=0, V63=1, V64=0, V65=0, V66=2, V67=3, V68=3, V69=0, V70=0, V71=1, V72=1, V73=2, V74=2, V75=3, V76=0, V77=1, V78=0, V79=0, V80=1, V81=0, V82=0, V83=0, V84=0, V85=1, V86=3, V87=0, V88=0, V89=2, V90=1, V91=3, V92=3, V93=0, V94=1, V95=0, V96=1, V97=2, V98=1, V99=3, V100=3, V101=0, V102=0, V103=1, V104=1, V105=0, V106=0, V107=2, V108=0, V109=1, V110=3, V111=3, V112=3, V113=1, V114=1, V115=1, V116=3, V117=3, V118=0, V119=2, V120=1, V121=0, V122=3, V123=3, V124=0, V125=0, V126=3, V127=2, V128=3, V129=3, V130=3, V131=1, V132=0, V133=1, V134=3, V135=3, V136=0, V137=0, V138=0, V139=1, V140=3, V141=3, V142=1, V143=0, 
0.07/0.14	v 3 2 0 3 3 3 3 3 3 3 2 3 3 3 3 3 3 3 3 3 0 0 3 3 0 2 2 2 3 0 3 2 3 0 0 3 0 2 0 0 3 0 0 1 3 0 0 1 3 3 3 0 1 1 0 1 3 1 1 0 1 1 0 1 0 0 2 3 3 0 0 1 1 2 2 3 0 1 0 0 1 0 0 0 0 1 3 0 0 2 1 3 3 0 1 0 1 2 1 3 3 0 0 1 1 0 0 2 0 1 3 3 3 1 1 1 3 3 0 2 1 0 3 3 0 0 3 2 3 3 3 1 0 1 3 3 0 0 0 1 3 3 1 0 
0.07/0.14	d ASSIGNMENTS 33

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-2080174-1247717342/watcher-2080174-1247717342 -o /tmp/evaluation-result-2080174-1247717342/solver-2080174-1247717342 -C 1800 -W 2000 -M 900 HOME/pcssolve -s 975430058 HOME/instance-2080174-1247717342.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.07 2.02 2.00 4/82 15583
/proc/meminfo: memFree=1063240/2055920 swapFree=4192812/4192956
[pid=15583] ppid=15581 vsize=5356 CPUtime=0
/proc/15583/stat : 15583 (pcssolve) R 15581 15583 14901 0 -1 4194304 273 0 0 0 0 0 0 0 20 0 1 0 58801231 5484544 241 996147200 4194304 4889804 548682068800 18446744073709551615 214919867039 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/15583/statm: 1339 241 200 169 0 50 0
[pid=15584] ppid=15583 vsize=5356 CPUtime=0
/proc/15584/stat : 15584 (pcssolve) R 15583 15583 14901 0 -1 4194368 0 0 0 0 0 0 0 0 20 0 1 0 58801231 5484544 241 996147200 4194304 4889804 548682068800 18446744073709551615 214919867039 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/15584/statm: 1339 241 200 169 0 50 0

[startup+0.032982 s]
/proc/loadavg: 2.07 2.02 2.00 4/82 15583
/proc/meminfo: memFree=1063240/2055920 swapFree=4192812/4192956
[pid=15583] ppid=15581 vsize=4628 CPUtime=0.01
/proc/15583/stat : 15583 (pcs.big) R 15581 15583 14901 0 -1 4194304 842 826 0 0 1 0 0 0 25 0 1 0 58801231 4739072 451 996147200 134512640 135215973 4294956304 18446744073709551615 9340539 0 0 4096 0 0 0 0 17 1 0 0
/proc/15583/statm: 1157 451 369 171 0 82 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 4628

[startup+0.102 s]
/proc/loadavg: 2.07 2.02 2.00 4/82 15583
/proc/meminfo: memFree=1063240/2055920 swapFree=4192812/4192956
[pid=15583] ppid=15581 vsize=6308 CPUtime=0.07
/proc/15583/stat : 15583 (pcs.big) R 15581 15583 14901 0 -1 4194304 1300 826 0 0 7 0 0 0 25 0 1 0 58801231 6459392 886 996147200 134512640 135215973 4294956304 18446744073709551615 134532717 0 0 4096 0 0 0 0 17 1 0 0
/proc/15583/statm: 1577 886 408 171 0 502 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 6308

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

Child status: 0
Real time (s): 0.150458
CPU time (s): 0.143977
CPU user time (s): 0.12898
CPU system time (s): 0.014997
CPU usage (%): 95.6925
Max. virtual memory (cumulated for all children) (KiB): 6308

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.12898
system time used= 0.014997
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 2204
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= 21

runsolver used 0.002999 second user time and 0.006998 second system time

The end

Launcher Data 

Begin job on node10 at 2009-07-16 06:09:02
IDJOB=2080174
IDBENCH=57017
IDSOLVER=734
FILE ID=node10/2080174-1247717342
PBS_JOBID= 9521407
Free space on /tmp= 66364 MiB

SOLVER NAME= pcs-restart 0.2.restart
BENCH NAME= CPAI08/csp/radar-8-24-3-2/normalized-radar-8-24-3-2-21.xml
COMMAND LINE= HOME/pcssolve -s RANDOMSEED BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2080174-1247717342/watcher-2080174-1247717342 -o /tmp/evaluation-result-2080174-1247717342/solver-2080174-1247717342 -C 1800 -W 2000 -M 900  HOME/pcssolve -s 975430058 HOME/instance-2080174-1247717342.xml

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

MD5SUM BENCH= 3da7530a420d27bc3a49cbac3ff7f368
RANDOM SEED=975430058

node10.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.279
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.279
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:       1063720 kB
Buffers:         72536 kB
Cached:         222516 kB
SwapCached:          0 kB
Active:         689328 kB
Inactive:       229264 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1063720 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1780 kB
Writeback:           0 kB
Mapped:         643976 kB
Slab:            57744 kB
Committed_AS:  1370164 kB
PageTables:       2976 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= 66360 MiB
End job on node10 at 2009-07-16 06:09:02