Trace number 215737

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.9354 3.9435

General information on the benchmark

NamepseudoSeries/mps/
mps-mitre.xml
MD5SUMe83d0bee8574e551da497bc065f26910
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 benchmark30.4264
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables10724
Number of constraints2045
Maximum constraint arity98
Maximum domain size2
Number of constraints which are defined in extension0
Number of constraints which are defined in intension2045
Global constraints used (with number of constraints)

Solver Data (download as text)

0.01	c 
0.01	c Parsing xml file
0.01	c 	domains...............    0
0.01	c 	variables............. 0.22
0.22	c 	predicates............ 0.03
0.26	c 	constraints........... 1.13
1.38	c Allocating memory
1.38	c 
1.38	c time limit = -1
1.38	c heuristic = dom/wdeg
1.38	c restart policy = No restart
1.38	c 
1.38	c Solving
1.38	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/node50/watcher-215737-1168235836 -o ROOT/results/node50/solver-215737-1168235836 -C 1800 -M 900 /tmp/evaluation/215737-1168235836/mistral/bin/solver /tmp/evaluation/215737-1168235836/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: 0.78 0.95 0.98 3/65 23110
/proc/meminfo: memFree=1836600/2055920 swapFree=4191892/4192956
[pid=23109] ppid=23107 vsize=6792 CPUtime=0
/proc/23109/stat : 23109 (solver) R 23107 23109 22308 0 -1 4194304 400 0 0 0 0 0 0 0 18 0 1 0 171982172 6955008 380 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 7887736 0 0 4096 0 0 0 0 17 1 0 0
/proc/23109/statm: 1698 380 356 92 0 30 0

[startup+0.106531 s]
/proc/loadavg: 0.78 0.95 0.98 3/65 23110
/proc/meminfo: memFree=1836600/2055920 swapFree=4191892/4192956
[pid=23109] ppid=23107 vsize=8120 CPUtime=0.1
/proc/23109/stat : 23109 (solver) R 23107 23109 22308 0 -1 4194304 1078 0 0 0 10 0 0 0 18 0 1 0 171982172 8314880 1046 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 8353403 0 0 4096 0 0 0 0 17 1 0 0
/proc/23109/statm: 2030 1046 688 92 0 374 0
Current children cumulated CPU time (s) 0.1
Current children cumulated vsize (KiB) 8120

[startup+0.514599 s]
/proc/loadavg: 0.78 0.95 0.98 3/65 23110
/proc/meminfo: memFree=1836600/2055920 swapFree=4191892/4192956
[pid=23109] ppid=23107 vsize=11728 CPUtime=0.5
/proc/23109/stat : 23109 (solver) R 23107 23109 22308 0 -1 4194304 2015 0 0 0 50 0 0 0 21 0 1 0 171982172 12009472 1983 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 8353403 0 0 4096 0 0 0 0 17 1 0 0
/proc/23109/statm: 2932 1983 713 92 0 1276 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 11728

[startup+1.33474 s]
/proc/loadavg: 0.78 0.95 0.98 2/65 23110
/proc/meminfo: memFree=1819128/2055920 swapFree=4191892/4192956
[pid=23109] ppid=23107 vsize=29332 CPUtime=1.32
/proc/23109/stat : 23109 (solver) R 23107 23109 22308 0 -1 4194304 6469 0 0 0 130 2 0 0 25 0 1 0 171982172 30035968 6362 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 8353403 0 0 4096 0 0 0 0 17 1 0 0
/proc/23109/statm: 7333 6362 713 92 0 5677 0
Current children cumulated CPU time (s) 1.32
Current children cumulated vsize (KiB) 29332

[startup+2.97102 s]
/proc/loadavg: 0.78 0.95 0.98 2/65 23110
/proc/meminfo: memFree=1594680/2055920 swapFree=4191892/4192956
[pid=23109] ppid=23107 vsize=576668 CPUtime=2.96
/proc/23109/stat : 23109 (solver) R 23107 23109 22308 0 -1 4194304 142472 0 0 0 243 53 0 0 25 0 1 0 171982172 590508032 142365 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 8353403 0 0 4096 0 0 0 0 17 0 0 0
/proc/23109/statm: 144167 142365 718 92 0 142511 0
Current children cumulated CPU time (s) 2.96
Current children cumulated vsize (KiB) 576668



Maximum VSize exceeded: sending SIGTERM then SIGKILL

[startup+3.79415 s]
/proc/loadavg: 0.80 0.95 0.98 2/65 23110
/proc/meminfo: memFree=907640/2055920 swapFree=4191892/4192956
[pid=23109] ppid=23107 vsize=938064 CPUtime=3.78
/proc/23109/stat : 23109 (solver) R 23107 23109 22308 0 -1 4194304 232836 0 0 0 287 91 0 0 25 0 1 0 171982172 960577536 232729 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 8353403 0 0 4096 0 0 0 0 17 1 0 0
/proc/23109/statm: 234516 232731 718 92 0 232860 0
Current children cumulated CPU time (s) 3.78
Current children cumulated vsize (KiB) 938064

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

Child ended because it received signal 15 (SIGTERM)
Real time (s): 3.9435
CPU time (s): 3.9354
CPU user time (s): 2.87956
CPU system time (s): 1.05584
CPU usage (%): 99.7947
Max. virtual memory (cumulated for all children) (KiB): 938064

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

runsolver used 0.008998 s user time and 0.013997 s system time

The end

Launcher Data (download as text)

Begin job on node50 on Mon Jan  8 05:57:16 UTC 2007


IDJOB= 215737
IDBENCH= 5024
FILE ID= node50/215737-1168235836

PBS_JOBID= 3481436

Free space on /tmp= 66559 MiB

BENCH NAME= HOME/pub/bench/CPAI06/pseudoSeries/mps/mps-mitre.xml
COMMAND LINE= /tmp/evaluation/215737-1168235836/mistral/bin/solver /tmp/evaluation/215737-1168235836/unknown.xml -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node50/watcher-215737-1168235836 -o ROOT/results/node50/solver-215737-1168235836 -C 1800 -M 900  /tmp/evaluation/215737-1168235836/mistral/bin/solver /tmp/evaluation/215737-1168235836/unknown.xml -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  e83d0bee8574e551da497bc065f26910

RANDOM SEED= 91801091

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.263
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.263
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:       1837080 kB
Buffers:         32848 kB
Cached:         120712 kB
SwapCached:        392 kB
Active:          94136 kB
Inactive:        74256 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1837080 kB
SwapTotal:     4192956 kB
SwapFree:      4191892 kB
Dirty:            4436 kB
Writeback:           0 kB
Mapped:          23652 kB
Slab:            36484 kB
Committed_AS:  4146876 kB
PageTables:       1460 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= 66559 MiB



End job on node50 on Mon Jan  8 05:57:20 UTC 2007