Trace number 1127158

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
toulbar2 2008-06-27OPTIMUM 0.010998 0.017252

General information on the benchmark

Namemaxcsp/pedigree/
normalized-connell_ext.xml
MD5SUMbae97c5d5334d51ddebe0c72aebbf7b6
Bench CategoryN-ARY-EXT (n-ary constraints in extension)
Best result obtained on this benchmarkMOPT
Best Number of falsified constraints1
Best CPU time to get the best result obtained on this benchmark0.029995
Satisfiable
(Un)Satisfiability was proved
Number of variables13
Number of constraints15
Maximum constraint arity3
Maximum domain size6
Number of constraints which are defined in extension15
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.00/0.01	o 1
0.00/0.01	s OPTIMUM FOUND
0.00/0.01	v 3 1 3 1 1 3 3 1 1 3 1 0 -1

Verifier Data (download as text)

OK	1	14
1 unsatisfied constraints, 14 satisfied constraints

Watcher Data (download as text)

runsolver version 3.2.5 (c) roussel@cril.univ-artois.fr

command line: /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1127158-1216188104/watcher-1127158-1216188104 -o /tmp/evaluation-result-1127158-1216188104/solver-1127158-1216188104 -C 3600 -W 4000 -M 900 --output-limit 1,15 HOME/solver.sh HOME/instance-1127158-1216188104.xml 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 3600 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 3630 seconds
Enforcing wall clock limit (soft limit, will send SIGTERM then SIGKILL): 4000 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
Solver output will be limited to a maximum of 15728640 bytes. The first 1048576 bytes and the last 14680064 bytes will be preserved
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 2.17 2.16 2.09 4/73 2616
/proc/meminfo: memFree=1592912/2055920 swapFree=4192812/4192956
[pid=2616] ppid=2614 vsize=5356 CPUtime=0
/proc/2616/stat : 2616 (solver.sh) S 2614 2616 994 0 -1 4194304 280 0 0 0 0 0 0 0 20 0 1 0 75513772 5484544 231 996147200 4194304 4889804 548682068832 18446744073709551615 233632752452 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/2616/statm: 1339 231 192 169 0 50 0
[pid=2617] ppid=2616 vsize=192 CPUtime=0
/proc/2617/stat : 2617 (rm) R 2616 2616 994 0 -1 4194304 44 0 0 0 0 0 0 0 22 0 1 0 75513772 196608 29 996147200 4194304 4227748 548682069056 18446744073709551615 233630126112 0 0 4096 0 0 0 0 17 1 0 0
/proc/2617/statm: 48 29 23 8 0 3 0

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

Child status: 0
Real time (s): 0.017252
CPU time (s): 0.010998
CPU user time (s): 0.005999
CPU system time (s): 0.004999
CPU usage (%): 63.749
Max. virtual memory (cumulated for all children) (KiB): 0

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

runsolver used 0.003999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node3 at 2008-07-16 08:01:44
IDJOB=1127158
IDBENCH=66134
IDSOLVER=371
FILE ID=node3/1127158-1216188104
PBS_JOBID= 7905832
Free space on /tmp= 66432 MiB

SOLVER NAME= toulbar2 2008-06-27
BENCH NAME= CPAI08/maxcsp/pedigree/normalized-connell_ext.xml
COMMAND LINE= HOME/solver.sh BENCHNAME 
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1127158-1216188104/watcher-1127158-1216188104 -o /tmp/evaluation-result-1127158-1216188104/solver-1127158-1216188104 -C 3600 -W 4000 -M 900 --output-limit 1,15  HOME/solver.sh HOME/instance-1127158-1216188104.xml 

TIME LIMIT= 3600 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= bae97c5d5334d51ddebe0c72aebbf7b6
RANDOM SEED=597087299

node3.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.238
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.238
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:       1593392 kB
Buffers:          3328 kB
Cached:          55560 kB
SwapCached:          0 kB
Active:         400240 kB
Inactive:        12016 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1593392 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            9588 kB
Writeback:           0 kB
Mapped:         364692 kB
Slab:            34848 kB
Committed_AS:   631452 kB
PageTables:       2580 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= 66424 MiB
End job on node3 at 2008-07-16 08:01:44