Trace number 247471

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? (exit code) 0.402938 0.418303

General information on the benchmark

Namerandom/rand-8-20-5/
rand-8-20-5-18-800-9_ext.xml
MD5SUM2edb97a8e449f03344d9a881313e99a5
Bench CategoryN-ARY-EXT (n-ary constraints in extension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark62.1805
SatisfiableYES
(Un)Satisfiability was proved
Number of variables20
Number of constraints18
Maximum constraint arity8
Maximum domain size5
Number of constraints which are defined in extension18
Number of constraints which are defined in intension0
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
0.01	c 	relations...
0.41		Unexpected exception :
0.41		last tuple is incomplete !

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/node6/watcher-247471-1168392765 -o ROOT/results/node6/solver-247471-1168392765 -C 1800 -M 900 /tmp/evaluation/247471-1168392765/mistral/bin/solver /tmp/evaluation/247471-1168392765/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.12 1.07 1.07 2/78 26470
/proc/meminfo: memFree=1585712/2055924 swapFree=4165672/4192956
[pid=26469] ppid=26467 vsize=6792 CPUtime=0
/proc/26469/stat : 26469 (solver) R 26467 26469 25370 0 -1 4194304 420 0 0 0 0 0 0 0 18 0 1 0 187672049 6955008 399 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 2152244 0 0 4096 0 0 0 0 17 1 0 0
/proc/26469/statm: 1698 400 363 92 0 30 0

[startup+0.102782 s]
/proc/loadavg: 1.12 1.07 1.07 2/78 26470
/proc/meminfo: memFree=1585712/2055924 swapFree=4165672/4192956
[pid=26469] ppid=26467 vsize=12532 CPUtime=0.09
/proc/26469/stat : 26469 (solver) R 26467 26469 25370 0 -1 4194304 3147 0 0 0 8 1 0 0 18 0 1 0 187672049 12832768 2179 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 4159427426 0 0 4096 0 0 0 0 17 1 0 0
/proc/26469/statm: 3133 2179 693 92 0 1477 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 12532

Child status: 1
Real time (s): 0.418303
CPU time (s): 0.402938
CPU user time (s): 0.385941
CPU system time (s): 0.016997
CPU usage (%): 96.3268
Max. virtual memory (cumulated for all children) (KiB): 12532

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.385941
system time used= 0.016997
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 3188
page faults= 2
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 15
involuntary context switches= 17

runsolver used 0.001999 s user time and 0.006998 s system time

The end

Launcher Data (download as text)

Begin job on node6 on Wed Jan 10 01:32:46 UTC 2007


IDJOB= 247471
IDBENCH= 11129
FILE ID= node6/247471-1168392765

PBS_JOBID= 3522777

Free space on /tmp= 66529 MiB

BENCH NAME= HOME/pub/bench/CPAI06/random/rand-8-20-5/rand-8-20-5-18-800-9_ext.xml
COMMAND LINE= /tmp/evaluation/247471-1168392765/mistral/bin/solver /tmp/evaluation/247471-1168392765/unknown.xml -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node6/watcher-247471-1168392765 -o ROOT/results/node6/solver-247471-1168392765 -C 1800 -M 900  /tmp/evaluation/247471-1168392765/mistral/bin/solver /tmp/evaluation/247471-1168392765/unknown.xml -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  2edb97a8e449f03344d9a881313e99a5

RANDOM SEED= 579280903

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:      2055924 kB
MemFree:       1586256 kB
Buffers:         47948 kB
Cached:         329080 kB
SwapCached:       2888 kB
Active:         224368 kB
Inactive:       184908 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055924 kB
LowFree:       1586256 kB
SwapTotal:     4192956 kB
SwapFree:      4165672 kB
Dirty:           25012 kB
Writeback:           0 kB
Mapped:          41536 kB
Slab:            45788 kB
Committed_AS:  6348900 kB
PageTables:       1976 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= 66529 MiB



End job on node6 on Wed Jan 10 01:32:47 UTC 2007