Trace number 2059813

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.038993 0.04661

DiagnosticValue
ASSIGNMENTS1

General information on the benchmark

Namecsp/QCP-10/
normalized-qcp-10-67-6_ext.xml
MD5SUM10212c7f429b61bbe1e70a8f61030c27
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.026995
Satisfiable
(Un)Satisfiability was proved
Number of variables100
Number of constraints822
Maximum constraint arity2
Maximum domain size10
Number of constraints which are defined in extension822
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data 

0.00/0.01	c small-domain mode
0.00/0.04	c Seed is 221111802
0.00/0.04	c Constructing HOME/instance-2059813-1247696025.xml  with 4278 constraints
0.00/0.04	c Solving 1 backtracks
0.00/0.04	s SATISFIABLE
0.00/0.04	c V0=5, V1=3, V2=4, V3=2, V4=0, V5=9, V6=7, V7=8, V8=1, V9=6, V10=1, V11=9, V12=6, V13=5, V14=2, V15=7, V16=3, V17=0, V18=4, V19=8, V20=9, V21=0, V22=8, V23=6, V24=5, V25=4, V26=1, V27=7, V28=3, V29=2, V30=4, V31=5, V32=0, V33=1, V34=3, V35=8, V36=6, V37=2, V38=7, V39=9, V40=3, V41=1, V42=9, V43=7, V44=6, V45=0, V46=8, V47=4, V48=2, V49=5, V50=7, V51=4, V52=2, V53=9, V54=1, V55=5, V56=0, V57=6, V58=8, V59=3, V60=6, V61=7, V62=1, V63=3, V64=8, V65=2, V66=4, V67=9, V68=5, V69=0, V70=8, V71=2, V72=3, V73=0, V74=4, V75=1, V76=9, V77=5, V78=6, V79=7, V80=0, V81=6, V82=5, V83=8, V84=7, V85=3, V86=2, V87=1, V88=9, V89=4, V90=2, V91=8, V92=7, V93=4, V94=9, V95=6, V96=5, V97=3, V98=0, V99=1, 
0.00/0.04	v 5 3 4 2 0 9 7 8 1 6 1 9 6 5 2 7 3 0 4 8 9 0 8 6 5 4 1 7 3 2 4 5 0 1 3 8 6 2 7 9 3 1 9 7 6 0 8 4 2 5 7 4 2 9 1 5 0 6 8 3 6 7 1 3 8 2 4 9 5 0 8 2 3 0 4 1 9 5 6 7 0 6 5 8 7 3 2 1 9 4 2 8 7 4 9 6 5 3 0 1 
0.00/0.04	d ASSIGNMENTS 1

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-2059813-1247696025/watcher-2059813-1247696025 -o /tmp/evaluation-result-2059813-1247696025/solver-2059813-1247696025 -C 1800 -W 2000 -M 900 HOME/pcssolve -s 221111802 HOME/instance-2059813-1247696025.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.91 1.95 1.67 4/72 9529
/proc/meminfo: memFree=1361064/2055920 swapFree=4192812/4192956
[pid=9529] ppid=9527 vsize=18576 CPUtime=0
/proc/9529/stat : 9529 (runsolver) R 9527 9529 9343 0 -1 4194368 15 0 0 0 0 0 0 0 20 0 1 0 56669315 19021824 284 996147200 4194304 4302564 548682068496 18446744073709551615 237788261671 0 0 4096 24578 0 0 0 17 1 0 0
/proc/9529/statm: 4644 284 249 26 0 2626 0

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

Child status: 0
Real time (s): 0.04661
CPU time (s): 0.038993
CPU user time (s): 0.027995
CPU system time (s): 0.010998
CPU usage (%): 83.6581
Max. virtual memory (cumulated for all children) (KiB): 0

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

runsolver used 0.001999 second user time and 0.007998 second system time

The end

Launcher Data 

Begin job on node24 at 2009-07-16 00:13:45
IDJOB=2059813
IDBENCH=53616
IDSOLVER=734
FILE ID=node24/2059813-1247696025
PBS_JOBID= 9521260
Free space on /tmp= 66412 MiB

SOLVER NAME= pcs-restart 0.2.restart
BENCH NAME= CPAI08/csp/QCP-10/normalized-qcp-10-67-6_ext.xml
COMMAND LINE= HOME/pcssolve -s RANDOMSEED BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2059813-1247696025/watcher-2059813-1247696025 -o /tmp/evaluation-result-2059813-1247696025/solver-2059813-1247696025 -C 1800 -W 2000 -M 900  HOME/pcssolve -s 221111802 HOME/instance-2059813-1247696025.xml

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

MD5SUM BENCH= 10212c7f429b61bbe1e70a8f61030c27
RANDOM SEED=221111802

node24.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.287
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.287
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:       1361544 kB
Buffers:         73172 kB
Cached:         485108 kB
SwapCached:          0 kB
Active:         233580 kB
Inactive:       394208 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1361544 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1764 kB
Writeback:           0 kB
Mapped:          80940 kB
Slab:            51804 kB
Committed_AS:   589260 kB
PageTables:       1904 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= 66412 MiB
End job on node24 at 2009-07-16 00:13:45