Trace number 2060568

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.040993 0.116026

DiagnosticValue
ASSIGNMENTS57
CHECKS29363
NODES57

General information on the benchmark

Namecsp/rcpsp/
normalized-rcpsp25-33.xml
MD5SUM5307a8d0a7078c1d086e41be99977052
Bench CategoryAlldiff+Cumul+Elt+WSum (alldiff,cumulative,element,weightedsum)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.040993
Satisfiable
(Un)Satisfiability was proved
Number of variables25
Number of constraints48
Maximum constraint arity25
Maximum domain size17
Number of constraints which are defined in extension0
Number of constraints which are defined in intension45
Global constraints used (with number of constraints)cumulative(3)

Solver Data 

0.00/0.08	c mistral version 1.545
0.01/0.11	s SATISFIABLE
0.01/0.11	v 4 0 9 0 6 0 3 6 10 0 9 5 11 1 11 0 14 14 15 11 13 11 16 14 14
0.01/0.11	d CHECKS 29363
0.01/0.11	d ASSIGNMENTS 57
0.01/0.11	d NODES 57 BACKTRACKS 37 FAILURES 37 RUNTIME -4.1674e-19 TOTALTIME 0.01 NODES/s -1.36776e+20 CHECKS/s -7.04588e+22

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-2060568-1247325970/watcher-2060568-1247325970 -o /tmp/evaluation-result-2060568-1247325970/solver-2060568-1247325970 -C 1800 -W 2000 -M 900 /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve HOME/instance-2060568-1247325970.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: 1.31 1.81 1.91 3/84 13065
/proc/meminfo: memFree=1731096/2055920 swapFree=4192812/4192956
[pid=13065] ppid=13063 vsize=2224 CPUtime=0
/proc/13065/stat : 13065 (ld-linux.so.2) D 13063 13065 11608 0 -1 4194304 43 0 0 0 0 0 0 0 19 0 1 0 19663269 2277376 29 996147200 1448431616 1448550632 4294956208 18446744073709551615 1448531911 0 0 4096 0 18446744071563479169 0 0 17 0 0 0
/proc/13065/statm: 556 29 23 29 0 3 0

[startup+0.0711431 s]
/proc/loadavg: 1.31 1.81 1.91 3/84 13065
/proc/meminfo: memFree=1731096/2055920 swapFree=4192812/4192956
[pid=13065] ppid=13063 vsize=4804 CPUtime=0
/proc/13065/stat : 13065 (ld-linux.so.2) D 13063 13065 11608 0 -1 4194304 180 0 4 0 0 0 0 0 18 0 1 0 19663269 4919296 165 996147200 1448431616 1448550632 4294956208 18446744073709551615 1448479286 0 0 4096 0 18446744071563479169 0 0 17 0 0 0
/proc/13065/statm: 1201 165 140 29 0 16 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 4804

[startup+0.101148 s]
/proc/loadavg: 1.31 1.81 1.91 3/84 13065
/proc/meminfo: memFree=1731096/2055920 swapFree=4192812/4192956
[pid=13065] ppid=13063 vsize=5868 CPUtime=0.01
/proc/13065/stat : 13065 (ld-linux.so.2) R 13063 13065 11608 0 -1 4194304 693 0 10 0 0 1 0 0 18 0 1 0 19663269 6008832 683 996147200 1448431616 1448550632 4294956208 18446744073709551615 4157381179 0 0 4096 0 0 0 0 17 0 0 0
/proc/13065/statm: 1467 686 412 29 0 282 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 5868

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

Child status: 0
Real time (s): 0.116026
CPU time (s): 0.040993
CPU user time (s): 0.021996
CPU system time (s): 0.018997
CPU usage (%): 35.3309
Max. virtual memory (cumulated for all children) (KiB): 5868

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.021996
system time used= 0.018997
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 864
page faults= 11
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 51
involuntary context switches= 38

runsolver used 0.001999 second user time and 0.008998 second system time

The end

Launcher Data 

Begin job on node27 at 2009-07-11 17:26:10
IDJOB=2060568
IDBENCH=53689
IDSOLVER=769
FILE ID=node27/2060568-1247325970
PBS_JOBID= 9506574
Free space on /tmp= 66308 MiB

SOLVER NAME= Mistral 1.545
BENCH NAME= CPAI08/csp/rcpsp/normalized-rcpsp25-33.xml
COMMAND LINE= /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2060568-1247325970/watcher-2060568-1247325970 -o /tmp/evaluation-result-2060568-1247325970/solver-2060568-1247325970 -C 1800 -W 2000 -M 900  /home/evaluation/evaluation/libc32/lib/ld-linux.so.2 ./xsolve HOME/instance-2060568-1247325970.xml

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

MD5SUM BENCH= 5307a8d0a7078c1d086e41be99977052
RANDOM SEED=935613957

node27.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		: 2800.239
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	: 5521.40
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		: 2800.239
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:       1731456 kB
Buffers:          4496 kB
Cached:          50380 kB
SwapCached:          0 kB
Active:         255388 kB
Inactive:        19588 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1731456 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1468 kB
Writeback:           0 kB
Mapped:         235816 kB
Slab:            34300 kB
Committed_AS:   838360 kB
PageTables:       2136 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264948 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66308 MiB
End job on node27 at 2009-07-11 17:26:10