Trace number 2063740

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.334948 0.347055

DiagnosticValue
ASSIGNMENTS61

General information on the benchmark

Namecsp/radar-9-28-4-2/
normalized-radar-9-28-4-2-17.xml
MD5SUM19b87120d9b5d562811d3a9be967d4f1
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.108982
Satisfiable
(Un)Satisfiability was proved
Number of variables168
Number of constraints81
Maximum constraint arity22
Maximum domain size5
Number of constraints which are defined in extension0
Number of constraints which are defined in intension81
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 1384393635
0.00/0.02	c Constructing HOME/instance-2063740-1247696073.xml  with 4079 constraints
0.07/0.10	c Solving 61 backtracks 2 restarts
0.27/0.34	s SATISFIABLE
0.27/0.34	c V0=4, V1=0, V2=0, V3=1, V4=0, V5=4, V6=4, V7=3, V8=0, V9=2, V10=2, V11=4, V12=4, V13=3, V14=0, V15=2, V16=4, V17=4, V18=0, V19=4, V20=1, V21=0, V22=4, V23=2, V24=4, V25=2, V26=0, V27=2, V28=3, V29=3, V30=0, V31=4, V32=1, V33=3, V34=0, V35=1, V36=4, V37=4, V38=4, V39=1, V40=4, V41=3, V42=1, V43=4, V44=2, V45=0, V46=2, V47=0, V48=4, V49=0, V50=4, V51=4, V52=0, V53=1, V54=4, V55=1, V56=1, V57=1, V58=4, V59=4, V60=3, V61=4, V62=0, V63=1, V64=1, V65=1, V66=2, V67=0, V68=0, V69=3, V70=0, V71=0, V72=0, V73=0, V74=0, V75=0, V76=1, V77=0, V78=1, V79=3, V80=0, V81=0, V82=1, V83=2, V84=3, V85=0, V86=1, V87=0, V88=4, V89=2, V90=1, V91=0, V92=1, V93=0, V94=4, V95=0, V96=3, V97=4, V98=1, V99=4, V100=0, V101=0, V102=0, V103=2, V104=0, V105=0, V106=4, V107=0, V108=2, V109=1, V110=2, V111=4, V112=4, V113=4, V114=0, V115=3, V116=0, V117=1, V118=0, V119=1, V120=2, V121=0, V122=4, V123=0, V124=1, V125=0, V126=4, V127=4, V128=4, V129=4, V130=0, V131=1, V132=0, V133=0, V134=4, V135=4, V136=0, V137=0, V138=0, V139=0, V140=1, V141=1, V142=0, V143=1, V144=0, V145=4, V146=4, V147=0, V148=1, V149=1, V150=1, V151=3, V152=0, V153=4, V154=3, V155=3, V156=0, V157=3, V158=4, V159=4, V160=1, V161=2, V162=4, V163=4, V164=4, V165=4, V166=0, V167=2, 
0.27/0.34	v 4 0 0 1 0 4 4 3 0 2 2 4 4 3 0 2 4 4 0 4 1 0 4 2 4 2 0 2 3 3 0 4 1 3 0 1 4 4 4 1 4 3 1 4 2 0 2 0 4 0 4 4 0 1 4 1 1 1 4 4 3 4 0 1 1 1 2 0 0 3 0 0 0 0 0 0 1 0 1 3 0 0 1 2 3 0 1 0 4 2 1 0 1 0 4 0 3 4 1 4 0 0 0 2 0 0 4 0 2 1 2 4 4 4 0 3 0 1 0 1 2 0 4 0 1 0 4 4 4 4 0 1 0 0 4 4 0 0 0 0 1 1 0 1 0 4 4 0 1 1 1 3 0 4 3 3 0 3 4 4 1 2 4 4 4 4 0 2 
0.27/0.34	d ASSIGNMENTS 61

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-2063740-1247696073/watcher-2063740-1247696073 -o /tmp/evaluation-result-2063740-1247696073/solver-2063740-1247696073 -C 1800 -W 2000 -M 900 HOME/pcssolve -s 1384393635 HOME/instance-2063740-1247696073.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.92 1.95 1.68 4/72 7935
/proc/meminfo: memFree=1284696/2055920 swapFree=4192812/4192956
[pid=7935] ppid=7933 vsize=5356 CPUtime=0
/proc/7935/stat : 7935 (pcssolve) R 7933 7935 7397 0 -1 4194304 273 0 0 0 0 0 0 0 20 0 1 0 56670174 5484544 241 996147200 4194304 4889804 548682068800 18446744073709551615 227607636639 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/7935/statm: 1339 241 200 169 0 50 0
[pid=7936] ppid=7935 vsize=5356 CPUtime=0
/proc/7936/stat : 7936 (pcssolve) R 7935 7935 7397 0 -1 4194368 0 0 0 0 0 0 0 0 20 0 1 0 56670175 5484544 241 996147200 4194304 4889804 548682068800 18446744073709551615 227607636639 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/7936/statm: 1339 241 200 169 0 50 0

[startup+0.0887251 s]
/proc/loadavg: 1.92 1.95 1.68 4/72 7935
/proc/meminfo: memFree=1284696/2055920 swapFree=4192812/4192956
[pid=7935] ppid=7933 vsize=5968 CPUtime=0.06
/proc/7935/stat : 7935 (pcs.big) R 7933 7935 7397 0 -1 4194304 1148 826 0 0 6 0 0 0 24 0 1 0 56670174 6111232 757 996147200 134512640 135215973 4294956304 18446744073709551615 4159729128 0 0 4096 0 0 0 0 17 1 0 0
/proc/7935/statm: 1492 757 387 171 0 417 0
Current children cumulated CPU time (s) 0.06
Current children cumulated vsize (KiB) 5968

[startup+0.101723 s]
/proc/loadavg: 1.92 1.95 1.68 4/72 7935
/proc/meminfo: memFree=1284696/2055920 swapFree=4192812/4192956
[pid=7935] ppid=7933 vsize=6428 CPUtime=0.07
/proc/7935/stat : 7935 (pcs.big) R 7933 7935 7397 0 -1 4194304 1234 826 0 0 7 0 0 0 24 0 1 0 56670174 6582272 843 996147200 134512640 135215973 4294956304 18446744073709551615 134532979 0 0 4096 0 0 0 0 17 1 0 0
/proc/7935/statm: 1607 843 387 171 0 532 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 6428

[startup+0.301752 s]
/proc/loadavg: 1.92 1.95 1.68 4/72 7935
/proc/meminfo: memFree=1284696/2055920 swapFree=4192812/4192956
[pid=7935] ppid=7933 vsize=7924 CPUtime=0.27
/proc/7935/stat : 7935 (pcs.big) R 7933 7935 7397 0 -1 4194304 1786 826 0 0 27 0 0 0 25 0 1 0 56670174 8114176 1227 996147200 134512640 135215973 4294956304 18446744073709551615 4158844876 0 0 4096 0 0 0 0 17 1 0 0
/proc/7935/statm: 1981 1227 408 171 0 906 0
Current children cumulated CPU time (s) 0.27
Current children cumulated vsize (KiB) 7924

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

Child status: 0
Real time (s): 0.347055
CPU time (s): 0.334948
CPU user time (s): 0.317951
CPU system time (s): 0.016997
CPU usage (%): 96.5115
Max. virtual memory (cumulated for all children) (KiB): 7924

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

runsolver used 0.004999 second user time and 0.005999 second system time

The end

Launcher Data 

Begin job on node66 at 2009-07-16 00:14:33
IDJOB=2063740
IDBENCH=54078
IDSOLVER=734
FILE ID=node66/2063740-1247696073
PBS_JOBID= 9521182
Free space on /tmp= 66256 MiB

SOLVER NAME= pcs-restart 0.2.restart
BENCH NAME= CPAI08/csp/radar-9-28-4-2/normalized-radar-9-28-4-2-17.xml
COMMAND LINE= HOME/pcssolve -s RANDOMSEED BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2063740-1247696073/watcher-2063740-1247696073 -o /tmp/evaluation-result-2063740-1247696073/solver-2063740-1247696073 -C 1800 -W 2000 -M 900  HOME/pcssolve -s 1384393635 HOME/instance-2063740-1247696073.xml

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

MD5SUM BENCH= 19b87120d9b5d562811d3a9be967d4f1
RANDOM SEED=1384393635

node66.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.214
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.214
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:       1285176 kB
Buffers:         72284 kB
Cached:         499936 kB
SwapCached:          0 kB
Active:         302224 kB
Inactive:       386080 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1285176 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1792 kB
Writeback:           0 kB
Mapped:         127528 kB
Slab:            67756 kB
Committed_AS:   573920 kB
PageTables:       1920 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= 66256 MiB
End job on node66 at 2009-07-16 00:14:34