Trace number 2066091

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.104983 0.113833

General information on the benchmark

Namecsp/pseudo/par/
normalized-par-8-5-c.xml
MD5SUM9698abad9c93eea5d80e7b5d03e642fa
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.025995
Satisfiable
(Un)Satisfiability was proved
Number of variables150
Number of constraints373
Maximum constraint arity3
Maximum domain size2
Number of constraints which are defined in extension0
Number of constraints which are defined in intension373
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-2066091-1247341184)
0.01/0.09	c Converted in 27 ms
0.08/0.10	c solving(HOME/instance-2066091-1247341184,1800000)
0.08/0.10	c solving(HOME/instance-2066091-1247341184,1800000)
0.08/0.10	c (ffc_inout)
0.08/0.10	s SATISFIABLE
0.08/0.10	v 1 0 1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 0 1 1 0 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 1 0 1 0 1 0 0 1 1 0 1 0 0 1 1 0 1 0 0 1 0 1 0 1 1 0 1 0 0 1 1 0 1 0 0 1 1 0 1 0 1 0 1 0 1 0 1 0 0 1 0 1 1 0 0 1 0 1 1 0 0 1 0 1 0 1 1 0 1 0 
0.08/0.11	
0.08/0.11	c Time=11 ms Backtracks=9
0.08/0.11

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-2066091-1247341184/watcher-2066091-1247341184 -o /tmp/evaluation-result-2066091-1247341184/solver-2066091-1247341184 -C 1800 -W 2000 -M 900 HOME/solver HOME/instance-2066091-1247341184 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: 1.84 1.93 2.02 4/72 15585
/proc/meminfo: memFree=1895368/2055920 swapFree=4192812/4192956
[pid=15585] ppid=15583 vsize=18576 CPUtime=0
/proc/15585/stat : 15585 (runsolver) R 15583 15585 14440 0 -1 4194368 15 0 0 0 0 0 0 0 20 0 1 0 21185444 19021824 284 996147200 4194304 4302564 548682068528 18446744073709551615 262910045479 0 0 4096 24578 0 0 0 17 1 0 0
/proc/15585/statm: 4644 284 249 26 0 2626 0

[startup+0.029194 s]
/proc/loadavg: 1.84 1.93 2.02 4/72 15585
/proc/meminfo: memFree=1895368/2055920 swapFree=4192812/4192956
[pid=15585] ppid=15583 vsize=62208 CPUtime=0.01
/proc/15585/stat : 15585 (bprolog) R 15583 15585 14440 0 -1 4194304 1094 0 0 0 1 0 0 0 20 0 1 0 21185444 63700992 807 996147200 134512640 135105188 4294956096 18446744073709551615 134602196 0 0 4096 2 0 0 0 17 1 0 0
/proc/15585/statm: 15552 807 174 144 0 15036 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 62208

[startup+0.101203 s]
/proc/loadavg: 1.84 1.93 2.02 4/72 15585
/proc/meminfo: memFree=1895368/2055920 swapFree=4192812/4192956
[pid=15585] ppid=15583 vsize=62204 CPUtime=0.08
/proc/15585/stat : 15585 (bprolog) R 15583 15585 14440 0 -1 4194304 1159 0 0 0 4 4 0 0 20 0 1 0 21185444 63696896 870 996147200 134512640 135105188 4294956096 18446744073709551615 134566444 0 0 4096 2 0 0 0 17 1 0 0
/proc/15585/statm: 15551 870 180 144 0 15035 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 62204

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

Child status: 0
Real time (s): 0.113833
CPU time (s): 0.104983
CPU user time (s): 0.054991
CPU system time (s): 0.049992
CPU usage (%): 92.2254
Max. virtual memory (cumulated for all children) (KiB): 62208

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.054991
system time used= 0.049992
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1240
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= 183

runsolver used 0.003999 second user time and 0.008998 second system time

The end

Launcher Data 

Begin job on node11 at 2009-07-11 21:39:44
IDJOB=2066091
IDBENCH=54469
IDSOLVER=770
FILE ID=node11/2066091-1247341184
PBS_JOBID= 9506748
Free space on /tmp= 66444 MiB

SOLVER NAME= bpsolver 09
BENCH NAME= CPAI08/csp/pseudo/par/normalized-par-8-5-c.xml
COMMAND LINE= HOME/solver BENCHNAMENOEXT TIMEOUT
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2066091-1247341184/watcher-2066091-1247341184 -o /tmp/evaluation-result-2066091-1247341184/solver-2066091-1247341184 -C 1800 -W 2000 -M 900  HOME/solver HOME/instance-2066091-1247341184 1800

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

MD5SUM BENCH= 9698abad9c93eea5d80e7b5d03e642fa
RANDOM SEED=1676748185

node11.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.274
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.274
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:       1895848 kB
Buffers:         11868 kB
Cached:          77008 kB
SwapCached:          0 kB
Active:          82048 kB
Inactive:        26380 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1895848 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1512 kB
Writeback:           0 kB
Mapped:          31132 kB
Slab:            37040 kB
Committed_AS:   136148 kB
PageTables:       1808 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= 66444 MiB
End job on node11 at 2009-07-11 21:39:45