Trace number 269674

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 0.549915 0.556197

DiagnosticValue
CHECKS7112660
NODES21008

General information on the benchmark

Nameqcp-qwh/QCP-15/
qcp-15-120-7_ext.xml
MD5SUMd3df06e25014e5ca721bd24b7eb5bf96
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 benchmark0.362944
SatisfiableYES
(Un)Satisfiability was proved
Number of variables225
Number of constraints3150
Maximum constraint arity2
Maximum domain size15
Number of constraints which are defined in extension3150
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.55	s SATISFIABLE
0.55	v 9 12 6 8 2 11 13 10 7 0 3 1 14 5 4 12 4 13 6 1 2 9 0 3 5 14 10 8 11 7 0 10 1 13 5 12 3 14 8 6 9 4 7 2 11 6 13 9 1 10 8 11 4 5 3 7 0 2 14 12 2 8 11 12 3 4 5 9 14 13 10 7 0 1 6 5 11 0 2 8 6 4 7 13 14 1 12 3 9 10 3 2 4 7 6 1 14 13 10 8 11 9 5 12 0 11 14 8 0 7 13 2 12 4 10 5 6 1 3 9 10 0 5 9 12 14 1 3 11 7 8 2 6 4 13 4 3 2 5 0 7 10 11 9 1 12 14 13 6 8 13 9 14 3 4 5 7 1 0 11 6 8 12 10 2 8 6 10 14 9 3 0 5 12 4 2 13 11 7 1 1 5 7 10 14 9 8 6 2 12 13 11 4 0 3 7 1 3 11 13 0 12 2 6 9 4 5 10 8 14 14 7 12 4 11 10 6 8 1 2 0 3 9 13 5 
0.55	d CHECKS 7.11266e+06
0.55	d NODES 21008

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/node9/watcher-269674-1168982492 -o ROOT/results/node9/solver-269674-1168982492 -C 1800 -M 900 /tmp/evaluation/269674-1168982492/VALCSP /tmp/evaluation/269674-1168982492/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: 1.96 1.97 1.81 5/86 27063
/proc/meminfo: memFree=929872/2055920 swapFree=4191880/4192956
[pid=27062] ppid=27060 vsize=18540 CPUtime=0
/proc/27062/stat : 27062 (runsolver) R 27060 27006 27006 0 -1 4194368 14 0 0 0 0 0 0 0 19 0 1 0 246644309 18984960 278 18446744073709551615 4194304 4267372 548682069072 18446744073709551615 215418992800 0 0 4096 24578 0 0 0 17 1 0 0
/proc/27062/statm: 4635 278 243 17 0 2626 0

[startup+0.108372 s]
/proc/loadavg: 1.96 1.97 1.81 5/86 27063
/proc/meminfo: memFree=929872/2055920 swapFree=4191880/4192956
[pid=27062] ppid=27060 vsize=5328 CPUtime=0.09
/proc/27062/stat : 27062 (VALCSP) R 27060 27062 27006 0 -1 4194304 1095 0 0 0 9 0 0 0 20 0 1 0 246644309 5455872 1073 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134524753 0 0 4096 0 0 0 0 17 1 0 0
/proc/27062/statm: 1332 1073 66 8 0 1004 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 5328

[startup+0.516409 s]
/proc/loadavg: 1.96 1.97 1.81 5/86 27063
/proc/meminfo: memFree=929872/2055920 swapFree=4191880/4192956
[pid=27062] ppid=27060 vsize=5328 CPUtime=0.5
/proc/27062/stat : 27062 (VALCSP) R 27060 27062 27006 0 -1 4194304 1095 0 0 0 50 0 0 0 24 0 1 0 246644309 5455872 1073 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134524947 0 0 4096 0 0 0 0 17 1 0 0
/proc/27062/statm: 1332 1073 66 8 0 1004 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 5328

Child status: 0
Real time (s): 0.556197
CPU time (s): 0.549915
CPU user time (s): 0.541917
CPU system time (s): 0.007998
CPU usage (%): 98.8706
Max. virtual memory (cumulated for all children) (KiB): 5328

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

runsolver used 0.003999 s user time and 0.005999 s system time

The end

Launcher Data (download as text)

Begin job on node9 on Tue Jan 16 21:21:32 UTC 2007


IDJOB= 269674
IDBENCH= 7097
IDSOLVER= 90
FILE ID= node9/269674-1168982492

PBS_JOBID= 3566059

Free space on /tmp= 66564 MiB

SOLVER NAME= VALCSP 3.1
BENCH NAME= HOME/pub/bench/CPAI06/qcp-qwh/QCP-15/qcp-15-120-7_ext.xml
COMMAND LINE= /tmp/evaluation/269674-1168982492/VALCSP /tmp/evaluation/269674-1168982492/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node9/watcher-269674-1168982492 -o ROOT/results/node9/solver-269674-1168982492 -C 1800 -M 900  /tmp/evaluation/269674-1168982492/VALCSP /tmp/evaluation/269674-1168982492/unknown.xml

META MD5SUM SOLVER= d4fc2c4e0b0392ee9c79e754aa39e238
MD5SUM BENCH=  d3df06e25014e5ca721bd24b7eb5bf96

RANDOM SEED= 110145367

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.231
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.231
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:        930288 kB
Buffers:         50240 kB
Cached:         176068 kB
SwapCached:        268 kB
Active:         847740 kB
Inactive:       195044 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        930288 kB
SwapTotal:     4192956 kB
SwapFree:      4191880 kB
Dirty:             512 kB
Writeback:           0 kB
Mapped:         828960 kB
Slab:            66176 kB
Committed_AS:  8173988 kB
PageTables:       3744 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= 66564 MiB



End job on node9 on Tue Jan 16 21:21:32 UTC 2007