Trace number 211492

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-04? (MO) 3.9124 3.94124

General information on the benchmark

NamepseudoSeries/mpsReduced/
mps-red-timtab1.xml
MD5SUM32c91da81888477cfae68f23dd35133c
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 variables3763
Number of constraints624
Maximum constraint arity138
Maximum domain size2
Number of constraints which are defined in extension0
Number of constraints which are defined in intension624
Global constraints used (with number of constraints)

Solver Data (download as text)

0.20	c 
0.20	c Parsing xml file
0.20	c 	domains...............    0
0.20	c 	variables............. 0.08
0.20	c 	predicates............ 1.02
1.11	c 	constraints........... 0.68
1.79	c Allocating memory
1.79	c 
1.79	c time limit = -1
1.79	c heuristic = dom/wdeg
1.79	c restart policy = No restart
1.79	c 
1.79	c Solving
1.79	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/node5/watcher-211492-1168209423 -o ROOT/results/node5/solver-211492-1168209423 -C 1800 -M 900 /tmp/evaluation/211492-1168209423/mistral/bin/solver /tmp/evaluation/211492-1168209423/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: 2.01 2.00 1.84 3/89 20189
/proc/meminfo: memFree=1368856/2055920 swapFree=4192812/4192956
[pid=20188] ppid=20186 vsize=18540 CPUtime=0
/proc/20188/stat : 20188 (runsolver) R 20186 20188 19755 0 -1 4194368 16 0 0 0 0 0 0 0 20 0 1 0 149556794 18984960 279 18446744073709551615 4194304 4267372 548682069040 18446744073709551615 226913479975 0 0 4096 24578 0 0 0 17 1 0 0
/proc/20188/statm: 4635 279 244 17 0 2626 0

[startup+0.103248 s]
/proc/loadavg: 2.01 2.00 1.84 3/89 20189
/proc/meminfo: memFree=1368856/2055920 swapFree=4192812/4192956
[pid=20188] ppid=20186 vsize=7844 CPUtime=0.09
/proc/20188/stat : 20188 (solver) R 20186 20188 19755 0 -1 4194304 1045 0 0 0 9 0 0 0 18 0 1 0 149556794 8032256 1013 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 4159433742 0 0 4096 0 0 0 0 17 1 0 0
/proc/20188/statm: 1961 1013 698 92 0 305 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 7844

[startup+0.511277 s]
/proc/loadavg: 2.01 2.00 1.84 3/89 20189
/proc/meminfo: memFree=1368856/2055920 swapFree=4192812/4192956
[pid=20188] ppid=20186 vsize=8936 CPUtime=0.5
/proc/20188/stat : 20188 (solver) R 20186 20188 19755 0 -1 4194304 1322 0 0 0 50 0 0 0 22 0 1 0 149556794 9150464 1290 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 8326652 0 0 4096 0 0 0 0 17 1 0 0
/proc/20188/statm: 2234 1290 698 92 0 578 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 8936

[startup+1.33237 s]
/proc/loadavg: 2.01 2.00 1.84 3/86 20189
/proc/meminfo: memFree=1365592/2055920 swapFree=4192812/4192956
[pid=20188] ppid=20186 vsize=13700 CPUtime=1.31
/proc/20188/stat : 20188 (solver) R 20186 20188 19755 0 -1 4194304 2503 0 0 0 131 0 0 0 25 0 1 0 149556794 14028800 2471 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 8382737 0 0 4096 0 0 0 0 17 1 0 0
/proc/20188/statm: 3425 2471 712 92 0 1769 0
Current children cumulated CPU time (s) 1.31
Current children cumulated vsize (KiB) 13700

[startup+2.96957 s]
/proc/loadavg: 2.01 2.00 1.84 3/86 20189
/proc/meminfo: memFree=1159320/2055920 swapFree=4192812/4192956
[pid=20188] ppid=20186 vsize=560412 CPUtime=2.94
/proc/20188/stat : 20188 (solver) R 20186 20188 19755 0 -1 4194304 135265 0 0 0 238 56 0 0 25 0 1 0 149556794 573861888 135233 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 9185809 0 0 4096 0 0 0 0 17 1 0 0
/proc/20188/statm: 140103 135233 718 92 0 138447 0
Current children cumulated CPU time (s) 2.94
Current children cumulated vsize (KiB) 560412



Maximum VSize exceeded: sending SIGTERM then SIGKILL

[startup+3.79066 s]
/proc/loadavg: 2.01 2.00 1.84 3/86 20189
/proc/meminfo: memFree=434392/2055920 swapFree=4192812/4192956
[pid=20188] ppid=20186 vsize=954960 CPUtime=3.76
/proc/20188/stat : 20188 (solver) R 20186 20188 19755 0 -1 4194304 233900 0 0 0 281 95 0 0 25 0 1 0 149556794 977879040 233868 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134789281 0 0 4096 0 0 0 0 17 1 0 0
/proc/20188/statm: 238740 233868 718 92 0 237084 0
Current children cumulated CPU time (s) 3.76
Current children cumulated vsize (KiB) 954960

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

Child ended because it received signal 15 (SIGTERM)
Real time (s): 3.94124
CPU time (s): 3.9124
CPU user time (s): 2.81257
CPU system time (s): 1.09983
CPU usage (%): 99.2683
Max. virtual memory (cumulated for all children) (KiB): 954960

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 2.81257
system time used= 1.09983
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 233900
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= 156

runsolver used 0.010998 s user time and 0.017997 s system time

The end

Launcher Data (download as text)

Begin job on node5 on Sun Jan  7 22:37:04 UTC 2007


IDJOB= 211492
IDBENCH= 4698
FILE ID= node5/211492-1168209423

PBS_JOBID= 3480581

Free space on /tmp= 66343 MiB

BENCH NAME= HOME/pub/bench/CPAI06/pseudoSeries/mpsReduced/mps-red-timtab1.xml
COMMAND LINE= /tmp/evaluation/211492-1168209423/mistral/bin/solver /tmp/evaluation/211492-1168209423/unknown.xml -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node5/watcher-211492-1168209423 -o ROOT/results/node5/solver-211492-1168209423 -C 1800 -M 900  /tmp/evaluation/211492-1168209423/mistral/bin/solver /tmp/evaluation/211492-1168209423/unknown.xml -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  32c91da81888477cfae68f23dd35133c

RANDOM SEED= 965361803

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.240
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.240
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:       1369336 kB
Buffers:         56588 kB
Cached:         425260 kB
SwapCached:          0 kB
Active:         268292 kB
Inactive:       355344 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1369336 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            3968 kB
Writeback:           0 kB
Mapped:         162088 kB
Slab:            47488 kB
Committed_AS:  3998560 kB
PageTables:       2400 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= 66343 MiB



End job on node5 on Sun Jan  7 22:37:08 UTC 2007