Trace number 1040131

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
bpsolver 2008-06-27SAT 0.407937 0.415003

General information on the benchmark

Namecsp/rcpsp/
normalized-rcpsp25-38.xml
MD5SUM5cbdc43a2892001654fb931964b42687
Bench CategoryGLOBAL (global constraints)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.037993
Satisfiable
(Un)Satisfiability was proved
Number of variables25
Number of constraints48
Maximum constraint arity25
Maximum domain size23
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 (download as text)

0.00/0.02	c bpsolver version 6.27.2008
0.00/0.02	c converting(HOME/instance-1040131-1214997474)
0.00/0.03	c Converted in 6 ms
0.00/0.03	c solving(HOME/instance-1040131-1214997474,1800000)
0.38/0.41	c (ff_inout)
0.38/0.41	s SATISFIABLE
0.38/0.41	v 0 0 4 4 0 6 6 3 17 3 19 2 7 8 12 12 9 11 7 17 14 14 14 20 22 
0.38/0.41	
0.38/0.41	c Time=373 ms
0.38/0.41

Verifier Data (download as text)

OK

Watcher Data (download as text)

runsolver version 3.2.5 (c) roussel@cril.univ-artois.fr

command line: /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1040131-1214997474/watcher-1040131-1214997474 -o /tmp/evaluation-result-1040131-1214997474/solver-1040131-1214997474 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/solver HOME/instance-1040131-1214997474 1800 

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): 2200 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
Solver output will be limited to a maximum of 15728640 bytes. The first 1048576 bytes and the last 14680064 bytes will be preserved
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 2.04 1.50 0.68 4/73 6920
/proc/meminfo: memFree=1912768/2055920 swapFree=4180652/4192956
[pid=6920] ppid=6918 vsize=4780 CPUtime=0
/proc/6920/stat : 6920 (bprolog) R 6918 6920 4674 0 -1 4194304 623 0 0 0 0 0 0 0 20 0 1 0 1978720416 4894720 341 996147200 134512640 134990860 4294956112 18446744073709551615 134530848 0 0 4096 0 0 0 0 17 1 0 0
/proc/6920/statm: 1195 341 72 116 0 706 0

[startup+0.095636 s]
/proc/loadavg: 2.04 1.50 0.68 4/73 6920
/proc/meminfo: memFree=1912768/2055920 swapFree=4180652/4192956
[pid=6920] ppid=6918 vsize=66316 CPUtime=0.07
/proc/6920/stat : 6920 (bprolog) R 6918 6920 4674 0 -1 4194304 1258 0 0 0 7 0 0 0 21 0 2 0 1978720416 67907584 968 996147200 134512640 134990860 4294956112 18446744073709551615 134911937 0 0 4096 2 18446744073709551615 0 0 17 1 0 0
/proc/6920/statm: 16579 968 208 116 0 16090 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 66316

[startup+0.101636 s]
/proc/loadavg: 2.04 1.50 0.68 4/73 6920
/proc/meminfo: memFree=1912768/2055920 swapFree=4180652/4192956
[pid=6920] ppid=6918 vsize=66316 CPUtime=0.08
/proc/6920/stat : 6920 (bprolog) R 6918 6920 4674 0 -1 4194304 1258 0 0 0 8 0 0 0 21 0 2 0 1978720416 67907584 968 996147200 134512640 134990860 4294956112 18446744073709551615 134607366 0 0 4096 2 18446744073709551615 0 0 17 1 0 0
/proc/6920/statm: 16579 968 208 116 0 16090 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 66316

[startup+0.301653 s]
/proc/loadavg: 2.04 1.50 0.68 4/73 6920
/proc/meminfo: memFree=1912768/2055920 swapFree=4180652/4192956
[pid=6920] ppid=6918 vsize=66316 CPUtime=0.28
/proc/6920/stat : 6920 (bprolog) R 6918 6920 4674 0 -1 4194304 1258 0 0 0 28 0 0 0 22 0 2 0 1978720416 67907584 968 996147200 134512640 134990860 4294956112 18446744073709551615 134593106 0 0 4096 2 18446744073709551615 0 0 17 1 0 0
/proc/6920/statm: 16579 968 208 116 0 16090 0
Current children cumulated CPU time (s) 0.28
Current children cumulated vsize (KiB) 66316

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

[startup+0.401662 s]
/proc/loadavg: 2.04 1.50 0.68 4/73 6920
/proc/meminfo: memFree=1912768/2055920 swapFree=4180652/4192956
[pid=6920] ppid=6918 vsize=66316 CPUtime=0.38
/proc/6920/stat : 6920 (bprolog) R 6918 6920 4674 0 -1 4194304 1258 0 0 0 38 0 0 0 23 0 2 0 1978720416 67907584 968 996147200 134512640 134990860 4294956112 18446744073709551615 134629968 0 0 4096 2 18446744073709551615 0 0 17 1 0 0
/proc/6920/statm: 16579 968 208 116 0 16090 0
Current children cumulated CPU time (s) 0.38
Current children cumulated vsize (KiB) 66316

Child status: 0
Real time (s): 0.415003
CPU time (s): 0.407937
CPU user time (s): 0.396939
CPU system time (s): 0.010998
CPU usage (%): 98.2974
Max. virtual memory (cumulated for all children) (KiB): 66316

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

runsolver used 0.004999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node41 at 2008-07-02 13:17:54
IDJOB=1040131
IDBENCH=53675
IDSOLVER=347
FILE ID=node41/1040131-1214997474
PBS_JOBID= 7870840
Free space on /tmp= 66196 MiB

SOLVER NAME= bpsolver 2008-06-27
BENCH NAME= CPAI08/csp/rcpsp/normalized-rcpsp25-38.xml
COMMAND LINE= HOME/solver BENCHNAMENOEXT TIMEOUT
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1040131-1214997474/watcher-1040131-1214997474 -o /tmp/evaluation-result-1040131-1214997474/solver-1040131-1214997474 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/solver HOME/instance-1040131-1214997474 1800

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= 5cbdc43a2892001654fb931964b42687
RANDOM SEED=113034747

node41.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.232
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.232
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:       1913248 kB
Buffers:          5448 kB
Cached:          60252 kB
SwapCached:       5972 kB
Active:          69956 kB
Inactive:        10428 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1913248 kB
SwapTotal:     4192956 kB
SwapFree:      4180652 kB
Dirty:            1836 kB
Writeback:           0 kB
Mapped:          21520 kB
Slab:            47624 kB
Committed_AS:  3455704 kB
PageTables:       1688 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= 66196 MiB
End job on node41 at 2008-07-02 13:17:55