Trace number 2062967

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.210967 0.217924

General information on the benchmark

Namecsp/jnhSat/
normalized-jnh07_ext.xml
MD5SUM621f9378e594bd91aed78f25bfee65f3
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.032994
Satisfiable
(Un)Satisfiability was proved
Number of variables100
Number of constraints848
Maximum constraint arity10
Maximum domain size2
Number of constraints which are defined in extension848
Number of constraints which are defined in intension0
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-2062967-1247329935)
0.00/0.15	c Converted in 46 ms
0.00/0.16	c solving(HOME/instance-2062967-1247329935,1800000)
0.00/0.16	c solving(HOME/instance-2062967-1247329935,1800000)
0.18/0.21	c (ffc_inout)
0.18/0.21	s SATISFIABLE
0.18/0.21	v 0 0 0 1 0 0 1 0 0 0 0 0 0 1 0 1 1 0 0 0 0 0 1 0 1 0 0 0 1 0 1 1 0 0 1 1 0 1 0 0 1 1 0 1 0 0 0 0 1 0 1 1 1 1 1 1 1 0 0 0 0 1 1 0 1 1 0 0 0 1 1 0 1 1 1 1 1 0 1 1 0 1 1 0 1 0 1 1 0 1 0 1 0 1 0 1 0 1 0 0 
0.18/0.21	
0.18/0.21	c Time=61 ms Backtracks=223
0.18/0.21

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-2062967-1247329935/watcher-2062967-1247329935 -o /tmp/evaluation-result-2062967-1247329935/solver-2062967-1247329935 -C 1800 -W 2000 -M 900 HOME/solver HOME/instance-2062967-1247329935 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.74 1.92 1.97 4/82 12995
/proc/meminfo: memFree=822736/2055920 swapFree=4192956/4192956
[pid=12995] ppid=12993 vsize=7000 CPUtime=0
/proc/12995/stat : 12995 (bprolog) R 12993 12995 10520 0 -1 4194304 665 0 0 0 0 0 0 0 20 0 1 0 20058760 7168000 383 996147200 134512640 135105188 4294956096 18446744073709551615 134530912 0 0 4096 0 0 0 0 17 0 0 0
/proc/12995/statm: 1750 383 72 144 0 1234 0

[startup+0.192585 s]
/proc/loadavg: 1.74 1.92 1.97 4/82 12995
/proc/meminfo: memFree=822736/2055920 swapFree=4192956/4192956
[pid=12995] ppid=12993 vsize=72444 CPUtime=0.18
/proc/12995/stat : 12995 (bprolog) R 12993 12995 10520 0 -1 4194304 1307 0 0 0 10 8 0 0 22 0 2 0 20058760 74182656 1017 996147200 134512640 135105188 4294956096 18446744073709551615 134629875 0 0 4096 2 18446744073709551615 0 0 17 0 0 0
/proc/12995/statm: 18111 1017 197 144 0 17595 0
Current children cumulated CPU time (s) 0.18
Current children cumulated vsize (KiB) 72444

[startup+0.201586 s]
/proc/loadavg: 1.74 1.92 1.97 4/82 12995
/proc/meminfo: memFree=822736/2055920 swapFree=4192956/4192956
[pid=12995] ppid=12993 vsize=72444 CPUtime=0.18
/proc/12995/stat : 12995 (bprolog) R 12993 12995 10520 0 -1 4194304 1307 0 0 0 10 8 0 0 22 0 2 0 20058760 74182656 1017 996147200 134512640 135105188 4294956096 18446744073709551615 134752800 0 0 4096 2 18446744073709551615 0 0 17 0 0 0
/proc/12995/statm: 18111 1017 197 144 0 17595 0
Current children cumulated CPU time (s) 0.18
Current children cumulated vsize (KiB) 72444

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

Child status: 0
Real time (s): 0.217924
CPU time (s): 0.210967
CPU user time (s): 0.121981
CPU system time (s): 0.088986
CPU usage (%): 96.8076
Max. virtual memory (cumulated for all children) (KiB): 72444

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

runsolver used 0.001999 second user time and 0.010998 second system time

The end

Launcher Data 

Begin job on node77 at 2009-07-11 18:32:15
IDJOB=2062967
IDBENCH=53947
IDSOLVER=770
FILE ID=node77/2062967-1247329935
PBS_JOBID= 9506479
Free space on /tmp= 66160 MiB

SOLVER NAME= bpsolver 09
BENCH NAME= CPAI08/csp/jnhSat/normalized-jnh07_ext.xml
COMMAND LINE= HOME/solver BENCHNAMENOEXT TIMEOUT
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2062967-1247329935/watcher-2062967-1247329935 -o /tmp/evaluation-result-2062967-1247329935/solver-2062967-1247329935 -C 1800 -W 2000 -M 900  HOME/solver HOME/instance-2062967-1247329935 1800

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

MD5SUM BENCH= 621f9378e594bd91aed78f25bfee65f3
RANDOM SEED=1974283994

node77.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.256
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.256
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	: 5996.54
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:        823216 kB
Buffers:         54056 kB
Cached:        1089908 kB
SwapCached:          0 kB
Active:         200020 kB
Inactive:       977436 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        823216 kB
SwapTotal:     4192956 kB
SwapFree:      4192956 kB
Dirty:            1680 kB
Writeback:           0 kB
Mapped:          52320 kB
Slab:            40436 kB
Committed_AS:   188264 kB
PageTables:       1852 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= 66160 MiB
End job on node77 at 2009-07-11 18:32:16