Trace number 2069350

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.84787 0.861598

DiagnosticValue
ASSIGNMENTS52

General information on the benchmark

Namecsp/pseudo/mps/
normalized-mps-pipex.xml
MD5SUM2a3b504a50b5a333cecc49785727f557
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.037993
Satisfiable
(Un)Satisfiability was proved
Number of variables48
Number of constraints41
Maximum constraint arity16
Maximum domain size2
Number of constraints which are defined in extension0
Number of constraints which are defined in intension41
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 190248080
0.00/0.02	c Constructing HOME/instance-2069350-1247708367.xml  with 432 constraints
0.00/0.02	c Solving 52 backtracks 2 restarts
0.77/0.86	s SATISFIABLE
0.77/0.86	c V0=0, V1=1, V2=0, V3=0, V4=1, V5=0, V6=0, V7=0, V8=0, V9=0, V10=0, V11=1, V12=0, V13=0, V14=0, V15=1, V16=0, V17=0, V18=1, V19=1, V20=0, V21=1, V22=1, V23=0, V24=0, V25=1, V26=0, V27=0, V28=0, V29=0, V30=0, V31=0, V32=1, V33=0, V34=0, V35=0, V36=0, V37=0, V38=0, V39=1, V40=1, V41=0, V42=1, V43=0, V44=1, V45=1, V46=1, V47=0, 
0.77/0.86	v 0 1 0 0 1 0 0 0 0 0 0 1 0 0 0 1 0 0 1 1 0 1 1 0 0 1 0 0 0 0 0 0 1 0 0 0 0 0 0 1 1 0 1 0 1 1 1 0 
0.77/0.86	d ASSIGNMENTS 52

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-2069350-1247708367/watcher-2069350-1247708367 -o /tmp/evaluation-result-2069350-1247708367/solver-2069350-1247708367 -C 1800 -W 2000 -M 900 HOME/pcssolve -s 190248080 HOME/instance-2069350-1247708367.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.98 1.99 4/72 10364
/proc/meminfo: memFree=724976/2055920 swapFree=4192812/4192956
[pid=10364] ppid=10362 vsize=18576 CPUtime=0
/proc/10364/stat : 10364 (runsolver) R 10362 10364 8500 0 -1 4194368 15 0 0 0 0 0 0 0 20 0 1 0 57900769 19021824 284 996147200 4194304 4302564 548682068496 18446744073709551615 266890439975 0 0 4096 24578 0 0 0 17 1 0 0
/proc/10364/statm: 4644 284 249 26 0 2626 0

[startup+0.0616761 s]
/proc/loadavg: 1.92 1.98 1.99 4/72 10364
/proc/meminfo: memFree=724976/2055920 swapFree=4192812/4192956
[pid=10364] ppid=10362 vsize=5080 CPUtime=0.04
/proc/10364/stat : 10364 (pcs.big) R 10362 10364 8500 0 -1 4194304 986 808 0 0 4 0 0 0 25 0 1 0 57900769 5201920 595 996147200 134512640 135215973 4294956304 18446744073709551615 134532714 0 0 4096 0 0 0 0 17 1 0 0
/proc/10364/statm: 1270 595 406 171 0 195 0
Current children cumulated CPU time (s) 0.04
Current children cumulated vsize (KiB) 5080

[startup+0.101683 s]
/proc/loadavg: 1.92 1.98 1.99 4/72 10364
/proc/meminfo: memFree=724976/2055920 swapFree=4192812/4192956
[pid=10364] ppid=10362 vsize=5812 CPUtime=0.08
/proc/10364/stat : 10364 (pcs.big) R 10362 10364 8500 0 -1 4194304 1159 808 0 0 8 0 0 0 25 0 1 0 57900769 5951488 768 996147200 134512640 135215973 4294956304 18446744073709551615 134600399 0 0 4096 0 0 0 0 17 1 0 0
/proc/10364/statm: 1453 768 406 171 0 378 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 5812

[startup+0.301705 s]
/proc/loadavg: 1.92 1.98 1.99 4/72 10364
/proc/meminfo: memFree=724976/2055920 swapFree=4192812/4192956
[pid=10364] ppid=10362 vsize=5940 CPUtime=0.28
/proc/10364/stat : 10364 (pcs.big) R 10362 10364 8500 0 -1 4194304 1199 808 0 0 28 0 0 0 25 0 1 0 57900769 6082560 808 996147200 134512640 135215973 4294956304 18446744073709551615 134600651 0 0 4096 0 0 0 0 17 1 0 0
/proc/10364/statm: 1485 808 409 171 0 410 0
Current children cumulated CPU time (s) 0.28
Current children cumulated vsize (KiB) 5940

[startup+0.701747 s]
/proc/loadavg: 1.92 1.98 1.99 4/72 10364
/proc/meminfo: memFree=724976/2055920 swapFree=4192812/4192956
[pid=10364] ppid=10362 vsize=6336 CPUtime=0.67
/proc/10364/stat : 10364 (pcs.big) R 10362 10364 8500 0 -1 4194304 1311 808 0 0 67 0 0 0 25 0 1 0 57900769 6488064 920 996147200 134512640 135215973 4294956304 18446744073709551615 134589807 0 0 4096 0 0 0 0 17 1 0 0
/proc/10364/statm: 1584 920 409 171 0 509 0
Current children cumulated CPU time (s) 0.67
Current children cumulated vsize (KiB) 6336

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

[startup+0.802762 s]
/proc/loadavg: 1.92 1.98 1.99 4/72 10364
/proc/meminfo: memFree=724976/2055920 swapFree=4192812/4192956
[pid=10364] ppid=10362 vsize=6336 CPUtime=0.77
/proc/10364/stat : 10364 (pcs.big) R 10362 10364 8500 0 -1 4194304 1327 808 0 0 77 0 0 0 25 0 1 0 57900769 6488064 936 996147200 134512640 135215973 4294956304 18446744073709551615 134600008 0 0 4096 0 0 0 0 17 1 0 0
/proc/10364/statm: 1584 936 409 171 0 509 0
Current children cumulated CPU time (s) 0.77
Current children cumulated vsize (KiB) 6336

Child status: 0
Real time (s): 0.861598
CPU time (s): 0.84787
CPU user time (s): 0.835872
CPU system time (s): 0.011998
CPU usage (%): 98.4067
Max. virtual memory (cumulated for all children) (KiB): 6336

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.835872
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= 2182
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= 33

runsolver used 0.004999 second user time and 0.006998 second system time

The end

Launcher Data 

Begin job on node38 at 2009-07-16 03:39:27
IDJOB=2069350
IDBENCH=55028
IDSOLVER=734
FILE ID=node38/2069350-1247708367
PBS_JOBID= 9521234
Free space on /tmp= 66228 MiB

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

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

MD5SUM BENCH= 2a3b504a50b5a333cecc49785727f557
RANDOM SEED=190248080

node38.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.229
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.229
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:        725456 kB
Buffers:         97988 kB
Cached:         803624 kB
SwapCached:          0 kB
Active:         686396 kB
Inactive:       542844 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        725456 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1860 kB
Writeback:           0 kB
Mapped:         339168 kB
Slab:            85704 kB
Committed_AS:   868872 kB
PageTables:       2664 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= 66224 MiB
End job on node38 at 2009-07-16 03:39:28