Trace number 2077817

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 09SAT 0.046991 0.0534629

General information on the benchmark

Namecsp/primes-15/
normalized-primes-15-20-2-7.xml
MD5SUMe2e5b8738391b6588798536d183cefce
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 benchmark0.012997
Satisfiable
(Un)Satisfiability was proved
Number of variables100
Number of constraints20
Maximum constraint arity9
Maximum domain size46
Number of constraints which are defined in extension0
Number of constraints which are defined in intension20
Global constraints used (with number of constraints)

Solver Data 

0.00/0.02	c bpsolver version 6.29.2009
0.00/0.02	c converting(HOME/instance-2077817-1247365872)
0.03/0.04	c Converted in 11 ms
0.03/0.04	c solving(HOME/instance-2077817-1247365872,1800000)
0.03/0.04	c solving(HOME/instance-2077817-1247365872,1800000)
0.03/0.04	c (ffc_inout)
0.03/0.04	s SATISFIABLE
0.03/0.04	v 45 2 4 16 23 26 5 13 47 46 46 47 46 2 45 2 2 2 2 2 47 11 2 16 46 44 2 15 44 47 41 2 4 47 8 9 46 2 2 2 2 2 2 35 46 2 22 47 2 2 28 2 2 2 46 2 45 2 2 47 3 22 2 47 23 24 2 42 2 2 2 2 47 2 40 47 2 2 2 4 2 4 7 47 45 23 47 19 26 2 21 2 9 2 12 2 2 7 2 46 
0.03/0.05	
0.03/0.05	c Time=4 ms Backtracks=13
0.03/0.05

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-2077817-1247365872/watcher-2077817-1247365872 -o /tmp/evaluation-result-2077817-1247365872/solver-2077817-1247365872 -C 1800 -W 2000 -M 900 HOME/solver HOME/instance-2077817-1247365872 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): 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.48 2.99 2.88 4/80 25345
/proc/meminfo: memFree=1650352/2055924 swapFree=4192812/4192956
[pid=25345] ppid=25343 vsize=18576 CPUtime=0
/proc/25345/stat : 25345 (runsolver) R 25343 25345 21966 0 -1 4194368 15 0 0 0 0 0 0 0 24 0 1 0 23654585 19021824 284 996147200 4194304 4302564 548682068528 18446744073709551615 268582841639 0 0 4096 24578 0 0 0 17 1 0 0
/proc/25345/statm: 4644 284 249 26 0 2626 0

[startup+0.0432369 s]
/proc/loadavg: 2.48 2.99 2.88 4/80 25345
/proc/meminfo: memFree=1650352/2055924 swapFree=4192812/4192956
[pid=25345] ppid=25343 vsize=62208 CPUtime=0.03
/proc/25345/stat : 25345 (bprolog) R 25343 25345 21966 0 -1 4194304 1114 0 0 0 2 1 0 0 24 0 1 0 23654585 63700992 827 996147200 134512640 135105188 4294956096 18446744073709551615 4294960144 0 0 4096 2 0 0 0 17 1 0 0
/proc/25345/statm: 15552 827 177 144 0 15036 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 62208

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

[startup+0.0432369 s]
/proc/loadavg: 2.48 2.99 2.88 4/80 25345
/proc/meminfo: memFree=1650352/2055924 swapFree=4192812/4192956
[pid=25345] ppid=25343 vsize=62208 CPUtime=0.03
/proc/25345/stat : 25345 (bprolog) R 25343 25345 21966 0 -1 4194304 1114 0 0 0 2 1 0 0 24 0 1 0 23654585 63700992 827 996147200 134512640 135105188 4294956096 18446744073709551615 4294960144 0 0 4096 2 0 0 0 17 1 0 0
/proc/25345/statm: 15552 827 177 144 0 15036 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 62208

Child status: 0
Real time (s): 0.0534629
CPU time (s): 0.046991
CPU user time (s): 0.032994
CPU system time (s): 0.013997
CPU usage (%): 87.8945
Max. virtual memory (cumulated for all children) (KiB): 62208

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

runsolver used 0.001999 second user time and 0.008998 second system time

The end

Launcher Data 

Begin job on node6 at 2009-07-12 04:31:12
IDJOB=2077817
IDBENCH=56668
IDSOLVER=770
FILE ID=node6/2077817-1247365872
PBS_JOBID= 9507036
Free space on /tmp= 66400 MiB

SOLVER NAME= bpsolver 09
BENCH NAME= CPAI08/csp/primes-15/normalized-primes-15-20-2-7.xml
COMMAND LINE= HOME/solver BENCHNAMENOEXT TIMEOUT
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2077817-1247365872/watcher-2077817-1247365872 -o /tmp/evaluation-result-2077817-1247365872/solver-2077817-1247365872 -C 1800 -W 2000 -M 900  HOME/solver HOME/instance-2077817-1247365872 1800

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

MD5SUM BENCH= e2e5b8738391b6588798536d183cefce
RANDOM SEED=2014043601

node6.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.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	: 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.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:      2055924 kB
MemFree:       1650832 kB
Buffers:         41476 kB
Cached:         196048 kB
SwapCached:          0 kB
Active:         222456 kB
Inactive:       107716 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055924 kB
LowFree:       1650832 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1428 kB
Writeback:           0 kB
Mapped:         110460 kB
Slab:            59944 kB
Committed_AS:   915648 kB
PageTables:       2032 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= 66400 MiB
End job on node6 at 2009-07-12 04:31:12