Trace number 1035347

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 2008-06-27SAT 0.102983 0.110844

General information on the benchmark

Namecsp/QWH-10/
normalized-qwh-10-57-2_ext.xml
MD5SUMc4dd165d12437f388ac205c7999d9d58
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.021995
Satisfiable
(Un)Satisfiability was proved
Number of variables100
Number of constraints756
Maximum constraint arity2
Maximum domain size10
Number of constraints which are defined in extension756
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.00/0.02	c bpsolver version 6.27.2008
0.00/0.02	c converting(HOME/instance-1035347-1214951601)
0.04/0.09	c Converted in 27 ms
0.04/0.09	c solving(HOME/instance-1035347-1214951601,1800000)
0.08/0.10	c (ffc_inout)
0.08/0.10	s SATISFIABLE
0.08/0.10	v 3 7 4 6 1 5 8 9 0 2 2 5 8 3 6 7 9 0 4 1 6 1 0 5 7 9 4 8 2 3 0 4 6 2 9 1 3 7 8 5 9 0 5 8 2 4 7 1 3 6 1 9 2 4 0 3 6 5 7 8 4 3 1 0 8 6 5 2 9 7 8 6 7 1 4 2 0 3 5 9 7 8 3 9 5 0 2 6 1 4 5 2 9 7 3 8 1 4 6 0 
0.08/0.10	
0.08/0.11	c Time=8 ms
0.08/0.11

Verifier Data (download as text)

OK

Watcher Data (download as text)

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

command line: /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1035347-1214951601/watcher-1035347-1214951601 -o /tmp/evaluation-result-1035347-1214951601/solver-1035347-1214951601 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/solver HOME/instance-1035347-1214951601 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): 2200 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
Solver output will be limited to a maximum of 15728640 bytes. The first 1048576 bytes and the last 14680064 bytes will be preserved
Current StackSize limit: 10240 KiB


[startup+0 s]
/proc/loadavg: 2.19 2.12 1.82 4/73 30776
/proc/meminfo: memFree=1278752/2055920 swapFree=4180240/4192956
[pid=30776] ppid=30774 vsize=18572 CPUtime=0
/proc/30776/stat : 30776 (runsolver) R 30774 30776 29493 0 -1 4194368 15 0 0 0 0 0 0 0 20 0 1 0 1974132116 19017728 292 996147200 4194304 4296836 548682068496 18446744073709551615 240577473831 0 0 4096 24578 0 0 0 17 1 0 0
/proc/30776/statm: 4643 292 257 25 0 2626 0

[startup+0.060407 s]
/proc/loadavg: 2.19 2.12 1.82 4/73 30776
/proc/meminfo: memFree=1278752/2055920 swapFree=4180240/4192956
[pid=30776] ppid=30774 vsize=56080 CPUtime=0.04
/proc/30776/stat : 30776 (bprolog) R 30774 30776 29493 0 -1 4194304 1102 0 0 0 2 2 0 0 20 0 1 0 1974132116 57425920 815 996147200 134512640 134990860 4294956112 18446744073709551615 134773268 0 0 4096 2 0 0 0 17 1 0 0
/proc/30776/statm: 14020 815 176 116 0 13531 0
Current children cumulated CPU time (s) 0.04
Current children cumulated vsize (KiB) 56080

[startup+0.10141 s]
/proc/loadavg: 2.19 2.12 1.82 4/73 30776
/proc/meminfo: memFree=1278752/2055920 swapFree=4180240/4192956
[pid=30776] ppid=30774 vsize=56076 CPUtime=0.08
/proc/30776/stat : 30776 (bprolog) R 30774 30776 29493 0 -1 4194304 1133 0 0 0 4 4 0 0 20 0 1 0 1974132116 57421824 844 996147200 134512640 134990860 4294956112 18446744073709551615 134774072 0 0 4096 2 0 0 0 17 1 0 0
/proc/30776/statm: 14019 844 178 116 0 13530 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 56076

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

Child status: 0
Real time (s): 0.110844
CPU time (s): 0.102983
CPU user time (s): 0.052991
CPU system time (s): 0.049992
CPU usage (%): 92.908
Max. virtual memory (cumulated for all children) (KiB): 56080

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.052991
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= 1191
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= 131

runsolver used 0.002999 second user time and 0.007998 second system time

The end

Launcher Data (download as text)

Begin job on node50 at 2008-07-02 00:33:21
IDJOB=1035347
IDBENCH=53392
IDSOLVER=347
FILE ID=node50/1035347-1214951601
PBS_JOBID= 7870234
Free space on /tmp= 66544 MiB

SOLVER NAME= bpsolver 2008-06-27
BENCH NAME= CPAI08/csp/QWH-10/normalized-qwh-10-57-2_ext.xml
COMMAND LINE= HOME/solver BENCHNAMENOEXT TIMEOUT
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1035347-1214951601/watcher-1035347-1214951601 -o /tmp/evaluation-result-1035347-1214951601/solver-1035347-1214951601 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/solver HOME/instance-1035347-1214951601 1800

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= c4dd165d12437f388ac205c7999d9d58
RANDOM SEED=747714140

node50.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.261
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.261
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:       1279232 kB
Buffers:         48012 kB
Cached:         508644 kB
SwapCached:       6724 kB
Active:         303948 kB
Inactive:       394156 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1279232 kB
SwapTotal:     4192956 kB
SwapFree:      4180240 kB
Dirty:            1876 kB
Writeback:           0 kB
Mapped:         147976 kB
Slab:            63644 kB
Committed_AS:  3862532 kB
PageTables:       2104 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= 66544 MiB
End job on node50 at 2008-07-02 00:33:22