Trace number 268984

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, and are wall clock time (not CPU 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
VALCSP 3.1SAT 26.8759 26.9426

DiagnosticValue
CHECKS1548700000
NODES46484

General information on the benchmark

Nametightness/tightness0.8/
rand-2-40-80-103-800-37_ext.xml
MD5SUM4f1efc87014a8b5ba672ff295cc5cd98
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark1.2818
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables40
Number of constraints103
Maximum constraint arity2
Maximum domain size80
Number of constraints which are defined in extension103
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

26.93	s SATISFIABLE
26.93	v 12 9 15 32 66 26 53 69 75 59 9 63 23 61 49 52 38 29 52 31 73 42 69 13 13 16 57 55 6 0 35 9 24 50 64 45 15 44 14 64 
26.93	d CHECKS 1.5487e+09
26.93	d NODES 46484

Verifier Data (download as text)

OK

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node34/watcher-268984-1168980092 -o ROOT/results/node34/solver-268984-1168980092 -C 1800 -M 900 /tmp/evaluation/268984-1168980092/VALCSP /tmp/evaluation/268984-1168980092/unknown.xml 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 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

/proc/loadavg: 0.73 0.91 0.86 2/68 2010
/proc/meminfo: memFree=1743712/2055920 swapFree=4192812/4192956
[pid=2009] ppid=2007 vsize=188 CPUtime=0
/proc/2009/stat : 2009 (VALCSP) D 2007 2009 1857 0 -1 4194304 44 0 0 0 0 0 0 0 18 0 1 0 246404586 192512 29 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 7721764 0 0 4096 0 18446744071563608240 0 0 17 1 0 0
/proc/2009/statm: 47 29 24 8 0 2 0

[startup+0.102185 s]
/proc/loadavg: 0.73 0.91 0.86 2/68 2010
/proc/meminfo: memFree=1743712/2055920 swapFree=4192812/4192956
[pid=2009] ppid=2007 vsize=1732 CPUtime=0.08
/proc/2009/stat : 2009 (VALCSP) R 2007 2009 1857 0 -1 4194304 168 0 0 0 8 0 0 0 18 0 1 0 246404586 1773568 146 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 8180822 0 0 4096 0 0 0 0 17 1 0 0
/proc/2009/statm: 433 146 64 8 0 105 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 1732

[startup+0.510215 s]
/proc/loadavg: 0.73 0.91 0.86 2/68 2010
/proc/meminfo: memFree=1743712/2055920 swapFree=4192812/4192956
[pid=2009] ppid=2007 vsize=2656 CPUtime=0.49
/proc/2009/stat : 2009 (VALCSP) R 2007 2009 1857 0 -1 4194304 406 0 0 0 49 0 0 0 20 0 1 0 246404586 2719744 384 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 8182990 0 0 4096 0 0 0 0 17 1 0 0
/proc/2009/statm: 664 384 64 8 0 336 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 2656

[startup+1.33028 s]
/proc/loadavg: 0.75 0.91 0.87 2/68 2010
/proc/meminfo: memFree=1741024/2055920 swapFree=4192812/4192956
[pid=2009] ppid=2007 vsize=4504 CPUtime=1.3
/proc/2009/stat : 2009 (VALCSP) R 2007 2009 1857 0 -1 4194304 883 0 0 0 130 0 0 0 25 0 1 0 246404586 4612096 861 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 8183004 0 0 4096 0 0 0 0 17 1 0 0
/proc/2009/statm: 1126 861 64 8 0 798 0
Current children cumulated CPU time (s) 1.3
Current children cumulated vsize (KiB) 4504

[startup+2.96641 s]
/proc/loadavg: 0.75 0.91 0.87 2/68 2010
/proc/meminfo: memFree=1736736/2055920 swapFree=4192812/4192956
[pid=2009] ppid=2007 vsize=8332 CPUtime=2.93
/proc/2009/stat : 2009 (VALCSP) R 2007 2009 1857 0 -1 4194304 1835 0 0 0 293 0 0 0 25 0 1 0 246404586 8531968 1813 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 134524988 0 0 4096 0 0 0 0 17 1 0 0
/proc/2009/statm: 2083 1813 66 8 0 1755 0
Current children cumulated CPU time (s) 2.93
Current children cumulated vsize (KiB) 8332

[startup+6.24668 s]
/proc/loadavg: 0.77 0.91 0.87 2/68 2010
/proc/meminfo: memFree=1736736/2055920 swapFree=4192812/4192956
[pid=2009] ppid=2007 vsize=8332 CPUtime=6.21
/proc/2009/stat : 2009 (VALCSP) R 2007 2009 1857 0 -1 4194304 1835 0 0 0 621 0 0 0 25 0 1 0 246404586 8531968 1813 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 134524976 0 0 4096 0 0 0 0 17 1 0 0
/proc/2009/statm: 2083 1813 66 8 0 1755 0
Current children cumulated CPU time (s) 6.21
Current children cumulated vsize (KiB) 8332

[startup+12.6972 s]
/proc/loadavg: 0.79 0.91 0.87 2/68 2013
/proc/meminfo: memFree=1736544/2055920 swapFree=4192812/4192956
[pid=2009] ppid=2007 vsize=8332 CPUtime=12.66
/proc/2009/stat : 2009 (VALCSP) R 2007 2009 1857 0 -1 4194304 1835 0 0 0 1266 0 0 0 25 0 1 0 246404586 8531968 1813 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 134524900 0 0 4096 0 0 0 0 17 1 0 0
/proc/2009/statm: 2083 1813 66 8 0 1755 0
Current children cumulated CPU time (s) 12.66
Current children cumulated vsize (KiB) 8332

[startup+25.5022 s]
/proc/loadavg: 0.82 0.91 0.87 3/73 2036
/proc/meminfo: memFree=1727336/2055920 swapFree=4192812/4192956
[pid=2009] ppid=2007 vsize=8332 CPUtime=25.44
/proc/2009/stat : 2009 (VALCSP) R 2007 2009 1857 0 -1 4194304 1835 0 0 0 2543 1 0 0 25 0 1 0 246404586 8531968 1813 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 134524979 0 0 4096 0 0 0 0 17 0 0 0
/proc/2009/statm: 2083 1813 66 8 0 1755 0
Current children cumulated CPU time (s) 25.44
Current children cumulated vsize (KiB) 8332

Child status: 0
Real time (s): 26.9426
CPU time (s): 26.8759
CPU user time (s): 26.8609
CPU system time (s): 0.014997
CPU usage (%): 99.7524
Max. virtual memory (cumulated for all children) (KiB): 8332

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 26.8609
system time used= 0.014997
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1865
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= 11
involuntary context switches= 190

runsolver used 0.029995 s user time and 0.069989 s system time

The end

Launcher Data (download as text)

Begin job on node34 on Tue Jan 16 20:41:39 UTC 2007


IDJOB= 268984
IDBENCH= 5774
IDSOLVER= 90
FILE ID= node34/268984-1168980092

PBS_JOBID= 3566263

Free space on /tmp= 66564 MiB

SOLVER NAME= VALCSP 3.1
BENCH NAME= HOME/pub/bench/CPAI06/tightness/tightness0.8/rand-2-40-80-103-800-37_ext.xml
COMMAND LINE= /tmp/evaluation/268984-1168980092/VALCSP /tmp/evaluation/268984-1168980092/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node34/watcher-268984-1168980092 -o ROOT/results/node34/solver-268984-1168980092 -C 1800 -M 900  /tmp/evaluation/268984-1168980092/VALCSP /tmp/evaluation/268984-1168980092/unknown.xml

META MD5SUM SOLVER= d4fc2c4e0b0392ee9c79e754aa39e238
MD5SUM BENCH=  4f1efc87014a8b5ba672ff295cc5cd98

RANDOM SEED= 855683857

TIME LIMIT= 1800 seconds

MEMORY LIMIT= 900 MiB


/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.227
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.227
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:       1744320 kB
Buffers:         29912 kB
Cached:         183472 kB
SwapCached:          0 kB
Active:          37980 kB
Inactive:       195624 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1744320 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:             876 kB
Writeback:           0 kB
Mapped:          30412 kB
Slab:            63748 kB
Committed_AS:  4092404 kB
PageTables:       1596 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= 66563 MiB



End job on node34 on Tue Jan 16 20:42:21 UTC 2007