Trace number 211532

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
Tramontane 2006-12-04? (MO) 4.29235 4.33925

General information on the benchmark

NamepseudoSeries/mpsReduced/
mps-red-modglob.xml
MD5SUMdf7e571fc89355355c80c513189d5bf2
Bench CategoryN-ARY-INT (n-ary constraints in intension)
Best result obtained on this benchmark
Best CPU time to get the best result obtained on this benchmark
Satisfiable
(Un)Satisfiability was proved
Number of variables9818
Number of constraints386
Maximum constraint arity270
Maximum domain size2
Number of constraints which are defined in extension0
Number of constraints which are defined in intension386
Global constraints used (with number of constraints)

Solver Data (download as text)

0.21	c 
0.21	c Parsing xml file
0.21	c 	domains...............    0
0.21	c 	variables.............  0.2
0.22	c 	predicates............ 0.54
0.76	c 	constraints........... 2.08
2.85	c Allocating memory
2.85	c 
2.85	c time limit = -1
2.85	c heuristic = dom/wdeg
2.85	c restart policy = Geometric increment
2.85	c restart base = 6545
2.85	c restart factor = 1.33
2.85	c 
2.85	c Solving
2.85	c

Verifier Data (download as text)

ERROR: Unexpected answer ! (SAT/UNSAT expected)
Got answer:

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node2/watcher-211532-1168209746 -o ROOT/results/node2/solver-211532-1168209746 -C 1800 -M 900 /tmp/evaluation/211532-1168209746/tramontane/bin/solver /tmp/evaluation/211532-1168209746/unknown.xml -res geom -f 3 -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: 2.16 1.86 1.43 5/86 17534
/proc/meminfo: memFree=1784416/2055920 swapFree=4191880/4192956
[pid=17533] ppid=17531 vsize=18540 CPUtime=0
/proc/17533/stat : 17533 (runsolver) R 17531 17533 16954 0 -1 4194368 16 0 0 0 0 0 0 0 20 0 1 0 169370327 18984960 279 18446744073709551615 4194304 4267372 548682068992 18446744073709551615 206381313319 0 0 4096 24578 0 0 0 17 1 0 0
/proc/17533/statm: 4635 279 244 17 0 2626 0

[startup+0.108047 s]
/proc/loadavg: 2.16 1.86 1.43 5/86 17534
/proc/meminfo: memFree=1784416/2055920 swapFree=4191880/4192956
[pid=17533] ppid=17531 vsize=8112 CPUtime=0.09
/proc/17533/stat : 17533 (solver) R 17531 17533 16954 0 -1 4194304 1087 0 0 0 9 0 0 0 18 0 1 0 169370327 8306688 1055 18446744073709551615 134512640 134893233 4294956640 18446744073709551615 134575795 0 0 4096 0 0 0 0 17 1 0 0
/proc/17533/statm: 2028 1055 692 92 0 372 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 8112

[startup+0.516121 s]
/proc/loadavg: 2.16 1.86 1.43 5/86 17534
/proc/meminfo: memFree=1784416/2055920 swapFree=4191880/4192956
[pid=17533] ppid=17531 vsize=10716 CPUtime=0.49
/proc/17533/stat : 17533 (solver) R 17531 17533 16954 0 -1 4194304 1771 0 0 0 49 0 0 0 22 0 1 0 169370327 10973184 1739 18446744073709551615 134512640 134893233 4294956640 18446744073709551615 11002844 0 0 4096 0 0 0 0 17 1 0 0
/proc/17533/statm: 2679 1739 703 92 0 1023 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 10716

[startup+1.33727 s]
/proc/loadavg: 2.16 1.86 1.43 3/86 17534
/proc/meminfo: memFree=1779360/2055920 swapFree=4191880/4192956
[pid=17533] ppid=17531 vsize=11644 CPUtime=1.3
/proc/17533/stat : 17533 (solver) R 17531 17533 16954 0 -1 4194304 1993 0 0 0 130 0 0 0 25 0 1 0 169370327 11923456 1961 18446744073709551615 134512640 134893233 4294956640 18446744073709551615 10969175 0 0 4096 0 0 0 0 17 1 0 0
/proc/17533/statm: 2911 1961 713 92 0 1255 0
Current children cumulated CPU time (s) 1.3
Current children cumulated vsize (KiB) 11644

[startup+2.97658 s]
/proc/loadavg: 2.16 1.86 1.43 3/86 17534
/proc/meminfo: memFree=1778720/2055920 swapFree=4191880/4192956
[pid=17533] ppid=17531 vsize=168960 CPUtime=2.94
/proc/17533/stat : 17533 (solver) R 17531 17533 16954 0 -1 4194304 25044 0 0 0 284 10 0 0 25 0 1 0 169370327 173015040 25012 18446744073709551615 134512640 134893233 4294956640 18446744073709551615 10970747 0 0 4096 0 0 0 0 17 1 0 0
/proc/17533/statm: 42240 25012 719 92 0 40584 0
Current children cumulated CPU time (s) 2.94
Current children cumulated vsize (KiB) 168960



Maximum VSize exceeded: sending SIGTERM then SIGKILL

[startup+4.20581 s]
/proc/loadavg: 2.14 1.87 1.43 3/86 17534
/proc/meminfo: memFree=982048/2055920 swapFree=4191880/4192956
[pid=17533] ppid=17531 vsize=967400 CPUtime=4.15
/proc/17533/stat : 17533 (solver) R 17531 17533 16954 0 -1 4194304 200858 0 0 0 331 84 0 0 25 0 1 0 169370327 990617600 200826 18446744073709551615 134512640 134893233 4294956640 18446744073709551615 10976975 0 0 4096 0 0 0 0 17 1 0 0
/proc/17533/statm: 241850 200826 720 92 0 240194 0
Current children cumulated CPU time (s) 4.15
Current children cumulated vsize (KiB) 967400

Sending SIGTERM to process tree (bottom up)
Sleeping 2 seconds

Child ended because it received signal 15 (SIGTERM)
Real time (s): 4.33925
CPU time (s): 4.29235
CPU user time (s): 3.3195
CPU system time (s): 0.972852
CPU usage (%): 98.9192
Max. virtual memory (cumulated for all children) (KiB): 967400

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

runsolver used 0.006998 s user time and 0.022996 s system time

The end

Launcher Data (download as text)

Begin job on node2 on Sun Jan  7 22:42:27 UTC 2007


IDJOB= 211532
IDBENCH= 4701
FILE ID= node2/211532-1168209746

PBS_JOBID= 3480602

Free space on /tmp= 66328 MiB

BENCH NAME= HOME/pub/bench/CPAI06/pseudoSeries/mpsReduced/mps-red-modglob.xml
COMMAND LINE= /tmp/evaluation/211532-1168209746/tramontane/bin/solver /tmp/evaluation/211532-1168209746/unknown.xml -res geom -f 3 -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node2/watcher-211532-1168209746 -o ROOT/results/node2/solver-211532-1168209746 -C 1800 -M 900  /tmp/evaluation/211532-1168209746/tramontane/bin/solver /tmp/evaluation/211532-1168209746/unknown.xml -res geom -f 3 -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  df7e571fc89355355c80c513189d5bf2

RANDOM SEED= 617329124

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.259
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	: 5931.00
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.259
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:       1784896 kB
Buffers:         14140 kB
Cached:          83312 kB
SwapCached:        264 kB
Active:         176608 kB
Inactive:        41060 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1784896 kB
SwapTotal:     4192956 kB
SwapFree:      4191880 kB
Dirty:            4236 kB
Writeback:           0 kB
Mapped:         141992 kB
Slab:            37996 kB
Committed_AS:  4167200 kB
PageTables:       2460 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= 66328 MiB



End job on node2 on Sun Jan  7 22:42:31 UTC 2007