Trace number 214372

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, and are wall clock time (not CPU 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
Mistral 2006-12-04SAT 3.77743 3.81033

General information on the benchmark

NamepseudoSeries/routing/
s4-4-3-8.xml
MD5SUM68fb44dcb60c35b63d5da7e4b563c586
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 benchmark1.55
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables432
Number of constraints1304
Maximum constraint arity18
Maximum domain size2
Number of constraints which are defined in extension0
Number of constraints which are defined in intension1304
Global constraints used (with number of constraints)

Solver Data (download as text)

0.10	c 
0.10	c Parsing xml file
0.10	c 	domains...............    0
0.10	c 	variables.............    0
0.10	c 	predicates............    0
0.10	c 	constraints...........  0.1
0.12	c Allocating memory
0.12	c 
0.12	c time limit = -1
0.12	c heuristic = dom/wdeg
0.12	c restart policy = No restart
0.12	c 
0.12	c Solving
0.12	c
3.80	s SATISFIABLE
3.80	v 0 0 0 0 0 1 0 0 0 1 1 1 0 0 1 0 0 0 0 1 1 0 0 1 0 0 0 0 0 0 1 1 0 0 0 0 1 0 0 0 1 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 1 1 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 1 0 0 0 0 0 0 0 1 0 0 0 1 0 0 0 1 1 0 0 0 1 1 0 0 1 0 1 0 1 0 0 0 0 1 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 0 0 0 0 0 1 1 0 0 1 1 0 0 0 1 0 1 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0
3.80	d          SAT     38213 BTS       3.6 s

Verifier Data (download as text)

OK

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node44/watcher-214372-1168230016 -o ROOT/results/node44/solver-214372-1168230016 -C 1800 -M 900 /tmp/evaluation/214372-1168230016/mistral/bin/solver /tmp/evaluation/214372-1168230016/unknown.xml -v 1 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 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

/proc/loadavg: 1.68 1.97 1.86 2/84 23415
/proc/meminfo: memFree=1662000/2055920 swapFree=4191892/4192956
[pid=23414] ppid=23412 vsize=540 CPUtime=0
/proc/23414/stat : 23414 (solver) R 23412 23414 22547 0 -1 4194304 41 0 0 0 0 0 0 0 19 0 1 0 171400718 552960 26 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 11281188 0 2147483391 4096 0 0 0 0 17 1 0 0
/proc/23414/statm: 135 26 21 92 0 18 0

[startup+0.10271 s]
/proc/loadavg: 1.68 1.97 1.86 2/84 23415
/proc/meminfo: memFree=1662000/2055920 swapFree=4191892/4192956
[pid=23414] ppid=23412 vsize=7576 CPUtime=0.09
/proc/23414/stat : 23414 (solver) R 23412 23414 22547 0 -1 4194304 964 0 0 0 9 0 0 0 19 0 1 0 171400718 7757824 932 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 4158553007 0 0 4096 0 0 0 0 17 1 0 0
/proc/23414/statm: 1894 932 701 92 0 238 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 7576

[startup+0.510746 s]
/proc/loadavg: 1.68 1.97 1.86 2/84 23415
/proc/meminfo: memFree=1662000/2055920 swapFree=4191892/4192956
[pid=23414] ppid=23412 vsize=8504 CPUtime=0.49
/proc/23414/stat : 23414 (solver) R 23412 23414 22547 0 -1 4194304 1214 0 0 0 49 0 0 0 23 0 1 0 171400718 8708096 1182 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134727329 0 0 4096 0 0 0 0 17 1 0 0
/proc/23414/statm: 2126 1182 721 92 0 470 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 8504

[startup+1.33183 s]
/proc/loadavg: 1.68 1.97 1.86 3/84 23415
/proc/meminfo: memFree=1652208/2055920 swapFree=4191892/4192956
[pid=23414] ppid=23412 vsize=8504 CPUtime=1.31
/proc/23414/stat : 23414 (solver) R 23412 23414 22547 0 -1 4194304 1214 0 0 0 131 0 0 0 25 0 1 0 171400718 8708096 1182 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134727371 0 0 4096 0 0 0 0 17 1 0 0
/proc/23414/statm: 2126 1182 721 92 0 470 0
Current children cumulated CPU time (s) 1.31
Current children cumulated vsize (KiB) 8504

[startup+2.969 s]
/proc/loadavg: 1.68 1.97 1.86 6/84 23415
/proc/meminfo: memFree=1645616/2055920 swapFree=4191892/4192956
[pid=23414] ppid=23412 vsize=8504 CPUtime=2.94
/proc/23414/stat : 23414 (solver) R 23412 23414 22547 0 -1 4194304 1214 0 0 0 294 0 0 0 25 0 1 0 171400718 8708096 1182 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134799251 0 0 4096 0 0 0 0 17 1 0 0
/proc/23414/statm: 2126 1182 721 92 0 470 0
Current children cumulated CPU time (s) 2.94
Current children cumulated vsize (KiB) 8504

Child status: 0
Real time (s): 3.81033
CPU time (s): 3.77743
CPU user time (s): 3.77243
CPU system time (s): 0.004999
CPU usage (%): 99.1365
Max. virtual memory (cumulated for all children) (KiB): 8512

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 3.77243
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= 1232
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= 13
involuntary context switches= 78

runsolver used 0.004999 s user time and 0.014997 s system time

The end

Launcher Data (download as text)

Begin job on node44 on Mon Jan  8 04:20:17 UTC 2007


IDJOB= 214372
IDBENCH= 4919
FILE ID= node44/214372-1168230016

PBS_JOBID= 3481355

Free space on /tmp= 66541 MiB

BENCH NAME= HOME/pub/bench/CPAI06/pseudoSeries/routing/s4-4-3-8.xml
COMMAND LINE= /tmp/evaluation/214372-1168230016/mistral/bin/solver /tmp/evaluation/214372-1168230016/unknown.xml -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node44/watcher-214372-1168230016 -o ROOT/results/node44/solver-214372-1168230016 -C 1800 -M 900  /tmp/evaluation/214372-1168230016/mistral/bin/solver /tmp/evaluation/214372-1168230016/unknown.xml -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  68fb44dcb60c35b63d5da7e4b563c586

RANDOM SEED= 520101848

TIME LIMIT= 1800 seconds

MEMORY LIMIT= 900 MiB


/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.213
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.213
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:       1662416 kB
Buffers:         24656 kB
Cached:         108728 kB
SwapCached:        304 kB
Active:         271212 kB
Inactive:        67072 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1662416 kB
SwapTotal:     4192956 kB
SwapFree:      4191892 kB
Dirty:            5804 kB
Writeback:           0 kB
Mapped:         224328 kB
Slab:            40152 kB
Committed_AS:  4317916 kB
PageTables:       2168 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= 66541 MiB



End job on node44 on Mon Jan  8 04:20:21 UTC 2007