Trace number 2075946

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. The first timestamp (if present) is estimated CPU time. The last timestamp is wall clock 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 1.545SAT 0.430933 0.437379

DiagnosticValue
ASSIGNMENTS80
CHECKS3342
NODES80

General information on the benchmark

Namecsp/modifiedRenault/
normalized-renault-mod-38_ext.xml
MD5SUM8d7d263222f8a3b1cbee67e9aeda3849
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 benchmark0.430933
Satisfiable
(Un)Satisfiability was proved
Number of variables111
Number of constraints154
Maximum constraint arity10
Maximum domain size42
Number of constraints which are defined in extension154
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data 

0.00/0.14	c mistral version 1.545
0.39/0.41	s SATISFIABLE
0.39/0.41	v 0 1 14 6 0 1 0 3 0 1 1 0 0 4 1 0 1 0 1 2 2 1 1 0 17 0 4 1 0 0 0 0 0 17 1 0 0 0 1 2 0 0 1 1 1 1 6 0 0 3 1 1 2 1 1 2 1 1 1 1 0 1 4 1 0 4 1 1 1 2 0 5 4 4 11 0 0 1 0 1 4 1 0 0 0 0 1 0 0 0 0 1 0 0 0 3 3 6 1 0 4 0 0 2 9 7 6 7 7 7 9
0.39/0.41	d CHECKS 3342
0.39/0.41	d ASSIGNMENTS 80
0.39/0.41	d NODES 80 BACKTRACKS 61 FAILURES 61 RUNTIME 0.04 TOTALTIME 0.41 NODES/s 2000 CHECKS/s 83550

Verifier Data 

OK

Watcher Data 

runsolver version 3.2.9 (svn:492) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2075946-1247362211/watcher-2075946-1247362211 -o /tmp/evaluation-result-2075946-1247362211/solver-2075946-1247362211 -C 1800 -W 2000 -M 900 /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve HOME/instance-2075946-1247362211.xml 

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


[startup+0 s]
/proc/loadavg: 2.00 2.03 2.00 4/80 19288
/proc/meminfo: memFree=1279088/2055920 swapFree=4192956/4192956
[pid=19288] ppid=19286 vsize=3436 CPUtime=0
/proc/19288/stat : 19288 (ld-linux.so.2) D 19286 19288 16916 0 -1 4194304 68 0 0 0 0 0 0 0 18 0 1 0 23288034 3518464 51 996147200 1448431616 1448550632 4294956208 18446744073709551615 1448525156 0 2147483391 4096 0 18446744072099781622 0 0 17 1 0 0
/proc/19288/statm: 1195 55 38 29 0 14 0

[startup+0.277684 s]
/proc/loadavg: 2.00 2.03 2.00 4/80 19288
/proc/meminfo: memFree=1279088/2055920 swapFree=4192956/4192956
[pid=19288] ppid=19286 vsize=10764 CPUtime=0.26
/proc/19288/stat : 19288 (ld-linux.so.2) R 19286 19288 16916 0 -1 4194304 1866 0 0 0 26 0 0 0 19 0 1 0 23288034 11022336 1845 996147200 1448431616 1448550632 4294956208 18446744073709551615 134671617 0 0 4096 0 0 0 0 17 1 0 0
/proc/19288/statm: 2691 1845 358 29 0 1506 0
Current children cumulated CPU time (s) 0.26
Current children cumulated vsize (KiB) 10764

[startup+0.301683 s]
/proc/loadavg: 2.00 2.03 2.00 4/80 19288
/proc/meminfo: memFree=1279088/2055920 swapFree=4192956/4192956
[pid=19288] ppid=19286 vsize=11160 CPUtime=0.28
/proc/19288/stat : 19288 (ld-linux.so.2) R 19286 19288 16916 0 -1 4194304 2001 0 0 0 28 0 0 0 19 0 1 0 23288034 11427840 1980 996147200 1448431616 1448550632 4294956208 18446744073709551615 134671431 0 0 4096 0 0 0 0 17 1 0 0
/proc/19288/statm: 2790 1980 358 29 0 1605 0
Current children cumulated CPU time (s) 0.28
Current children cumulated vsize (KiB) 11160

[startup+0.40171 s]
/proc/loadavg: 2.00 2.03 2.00 4/80 19288
/proc/meminfo: memFree=1279088/2055920 swapFree=4192956/4192956
[pid=19288] ppid=19286 vsize=18052 CPUtime=0.39
/proc/19288/stat : 19288 (ld-linux.so.2) R 19286 19288 16916 0 -1 4194304 3624 0 0 0 38 1 0 0 20 0 1 0 23288034 18485248 3603 996147200 1448431616 1448550632 4294956208 18446744073709551615 134850059 0 0 4096 0 0 0 0 17 1 0 0
/proc/19288/statm: 4513 3603 418 29 0 3328 0
Current children cumulated CPU time (s) 0.39
Current children cumulated vsize (KiB) 18052

Solver just ended. Dumping a history of the last processes samples

[startup+0.40171 s]
/proc/loadavg: 2.00 2.03 2.00 4/80 19288
/proc/meminfo: memFree=1279088/2055920 swapFree=4192956/4192956
[pid=19288] ppid=19286 vsize=18052 CPUtime=0.39
/proc/19288/stat : 19288 (ld-linux.so.2) R 19286 19288 16916 0 -1 4194304 3624 0 0 0 38 1 0 0 20 0 1 0 23288034 18485248 3603 996147200 1448431616 1448550632 4294956208 18446744073709551615 134850059 0 0 4096 0 0 0 0 17 1 0 0
/proc/19288/statm: 4513 3603 418 29 0 3328 0
Current children cumulated CPU time (s) 0.39
Current children cumulated vsize (KiB) 18052

Child status: 0
Real time (s): 0.437379
CPU time (s): 0.430933
CPU user time (s): 0.415936
CPU system time (s): 0.014997
CPU usage (%): 98.5262
Max. virtual memory (cumulated for all children) (KiB): 18052

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

runsolver used 0.002999 second user time and 0.005999 second system time

The end

Launcher Data 

Begin job on node14 at 2009-07-12 03:30:11
IDJOB=2075946
IDBENCH=56363
IDSOLVER=769
FILE ID=node14/2075946-1247362211
PBS_JOBID= 9506865
Free space on /tmp= 66488 MiB

SOLVER NAME= Mistral 1.545
BENCH NAME= CPAI08/csp/modifiedRenault/normalized-renault-mod-38_ext.xml
COMMAND LINE= /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2075946-1247362211/watcher-2075946-1247362211 -o /tmp/evaluation-result-2075946-1247362211/solver-2075946-1247362211 -C 1800 -W 2000 -M 900  /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve HOME/instance-2075946-1247362211.xml

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB
MAX NB THREAD= 0

MD5SUM BENCH= 8d7d263222f8a3b1cbee67e9aeda3849
RANDOM SEED=1788449636

node14.alineos.net Linux 2.6.9-22.EL.rootsmp #1 SMP Mon Oct 3 08:59:52 CEST 2005

/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.265
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.265
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:       1279568 kB
Buffers:         78904 kB
Cached:         529696 kB
SwapCached:          0 kB
Active:         221800 kB
Inactive:       499248 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1279568 kB
SwapTotal:     4192956 kB
SwapFree:      4192956 kB
Dirty:            4792 kB
Writeback:           0 kB
Mapped:         130240 kB
Slab:            40284 kB
Committed_AS:   920316 kB
PageTables:       2044 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= 66488 MiB
End job on node14 at 2009-07-12 03:30:11