Trace number 2092016

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
Conquer 2009-07-10UNSAT 0.785879 0.987337

General information on the benchmark

Namecsp/composed-75-1-80/
normalized-composed-75-1-80-7_ext.xml
MD5SUMe845c92db2276515253f094cda6f8ed2
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.047991
Satisfiable
(Un)Satisfiability was proved
Number of variables83
Number of constraints702
Maximum constraint arity2
Maximum domain size10
Number of constraints which are defined in extension702
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data 

0.03/0.98	s UNSATISFIABLE

Verifier Data 

No possible verification on an UNSAT instance

Watcher Data 

runsolver version 3.2.9 (svn:492) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2092016-1247396953/watcher-2092016-1247396953 -o /tmp/evaluation-result-2092016-1247396953/solver-2092016-1247396953 -C 1800 -W 2000 -M 900 HOME/solver -benchname HOME/instance-2092016-1247396953.xml -dir HOME -tmpdir HOME 

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.95 2.04 2.06 3/70 1236
/proc/meminfo: memFree=1807912/2055912 swapFree=4192812/4192956
[pid=1236] ppid=1234 vsize=5356 CPUtime=0
/proc/1236/stat : 1236 (solver) S 1234 1236 362 0 -1 4194304 314 142 0 0 0 0 0 0 18 0 1 0 26759866 5484544 241 996147200 4194304 4889804 548682068704 18446744073709551615 255372878660 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/1236/statm: 1339 241 200 169 0 50 0
[pid=1238] ppid=1236 vsize=184 CPUtime=0
/proc/1238/stat : 1238 (ld-linux.so.2) R 1236 1236 362 0 -1 4194304 44 0 0 0 0 0 0 0 20 0 1 0 26759866 188416 29 996147200 1448431616 1448550632 4294956128 18446744073709551615 1448524651 0 0 4096 0 0 0 0 17 1 0 0
/proc/1238/statm: 46 29 23 29 0 3 0

[startup+0.092804 s]
/proc/loadavg: 1.95 2.04 2.06 3/70 1236
/proc/meminfo: memFree=1807912/2055912 swapFree=4192812/4192956
[pid=1236] ppid=1234 vsize=5356 CPUtime=0.03
/proc/1236/stat : 1236 (solver) S 1234 1236 362 0 -1 4194304 361 337 0 0 0 0 1 2 16 0 1 0 26759866 5484544 242 996147200 4194304 4889804 548682068704 18446744073709551615 255372878660 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/1236/statm: 1339 242 201 169 0 50 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 5356

[startup+0.101804 s]
/proc/loadavg: 1.95 2.04 2.06 3/70 1236
/proc/meminfo: memFree=1807912/2055912 swapFree=4192812/4192956
[pid=1236] ppid=1234 vsize=5356 CPUtime=0.03
/proc/1236/stat : 1236 (solver) S 1234 1236 362 0 -1 4194304 361 337 0 0 0 0 1 2 16 0 1 0 26759866 5484544 242 996147200 4194304 4889804 548682068704 18446744073709551615 255372878660 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/1236/statm: 1339 242 201 169 0 50 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 5356

[startup+0.301827 s]
/proc/loadavg: 1.95 2.04 2.06 3/70 1236
/proc/meminfo: memFree=1807912/2055912 swapFree=4192812/4192956
[pid=1236] ppid=1234 vsize=5356 CPUtime=0.03
/proc/1236/stat : 1236 (solver) S 1234 1236 362 0 -1 4194304 361 337 0 0 0 0 1 2 16 0 1 0 26759866 5484544 242 996147200 4194304 4889804 548682068704 18446744073709551615 255372878660 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/1236/statm: 1339 242 201 169 0 50 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 5356

[startup+0.701867 s]
/proc/loadavg: 1.95 2.04 2.06 3/70 1236
/proc/meminfo: memFree=1807912/2055912 swapFree=4192812/4192956
[pid=1236] ppid=1234 vsize=5356 CPUtime=0.03
/proc/1236/stat : 1236 (solver) S 1234 1236 362 0 -1 4194304 361 337 0 0 0 0 1 2 16 0 1 0 26759866 5484544 242 996147200 4194304 4889804 548682068704 18446744073709551615 255372878660 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/1236/statm: 1339 242 201 169 0 50 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 5356

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

[startup+0.90189 s]
/proc/loadavg: 1.95 2.04 2.06 3/70 1236
/proc/meminfo: memFree=1807912/2055912 swapFree=4192812/4192956
[pid=1236] ppid=1234 vsize=5356 CPUtime=0.03
/proc/1236/stat : 1236 (solver) S 1234 1236 362 0 -1 4194304 361 337 0 0 0 0 1 2 16 0 1 0 26759866 5484544 242 996147200 4194304 4889804 548682068704 18446744073709551615 255372878660 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/1236/statm: 1339 242 201 169 0 50 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 5356

Child status: 0
Real time (s): 0.987337
CPU time (s): 0.785879
CPU user time (s): 0.738887
CPU system time (s): 0.046992
CPU usage (%): 79.5958
Max. virtual memory (cumulated for all children) (KiB): 5356

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

runsolver used 0.002999 second user time and 0.009998 second system time

The end

Launcher Data 

Begin job on node78 at 2009-07-12 13:09:13
IDJOB=2092016
IDBENCH=60234
IDSOLVER=740
FILE ID=node78/2092016-1247396953
PBS_JOBID= 9507363
Free space on /tmp= 126812 MiB

SOLVER NAME= Conquer 2009-06-04
BENCH NAME= CPAI08/csp/composed-75-1-80/normalized-composed-75-1-80-7_ext.xml
COMMAND LINE= HOME/solver -benchname BENCHNAME -dir DIR -tmpdir TMPDIR
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2092016-1247396953/watcher-2092016-1247396953 -o /tmp/evaluation-result-2092016-1247396953/solver-2092016-1247396953 -C 1800 -W 2000 -M 900  HOME/solver -benchname HOME/instance-2092016-1247396953.xml -dir HOME -tmpdir HOME

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

MD5SUM BENCH= e845c92db2276515253f094cda6f8ed2
RANDOM SEED=2132453105

node78.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.232
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.232
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:      2055912 kB
MemFree:       1808592 kB
Buffers:         36332 kB
Cached:         142032 kB
SwapCached:          0 kB
Active:         133924 kB
Inactive:        60824 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055912 kB
LowFree:       1808592 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:           21200 kB
Writeback:           0 kB
Mapped:          26220 kB
Slab:            37860 kB
Committed_AS:   198104 kB
PageTables:       1672 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264960 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 126792 MiB
End job on node78 at 2009-07-12 13:09:14