Trace number 1083689

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.231964 0.242894

General information on the benchmark

Namecsp/rlfapScensMod/
normalized-scen2-f24.xml
MD5SUM5a67895b6e4679565fdc3dec2d0f4ec1
Bench Category2-ARY-INT (binary constraints in intension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.090985
Satisfiable
(Un)Satisfiability was proved
Number of variables200
Number of constraints1235
Maximum constraint arity2
Maximum domain size22
Number of constraints which are defined in extension0
Number of constraints which are defined in intension1235
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-1083689-1215229255)
0.18/0.20	c Converted in 81 ms
0.18/0.20	c solving(HOME/instance-1083689-1215229255,1800000)
0.18/0.23	c (ffc_inout)
0.18/0.23	s SATISFIABLE
0.18/0.23	v 16 254 128 366 30 268 254 16 268 30 128 366 268 30 58 296 366 128 324 86 324 86 254 16 324 86 268 30 72 310 254 16 380 142 16 254 366 128 72 310 72 310 142 380 142 380 156 394 268 30 282 44 254 16 380 142 86 324 16 254 16 254 114 352 352 114 16 254 366 128 30 268 30 268 100 338 296 58 268 30 296 58 282 44 268 30 268 30 338 100 30 268 282 44 58 296 338 100 16 254 16 254 268 30 86 324 16 254 114 352 30 268 72 310 30 268 100 338 100 338 58 296 352 114 30 268 114 352 44 282 268 30 338 100 72 310 142 380 30 268 142 380 44 282 30 268 30 268 30 268 72 310 310 72 324 86 44 282 156 394 142 380 58 296 254 16 324 86 30 268 30 268 114 352 100 338 16 254 58 296 114 352 30 268 338 100 268 30 100 338 30 268 338 100 268 30 282 44 268 30 
0.18/0.24	
0.18/0.24	c Time=34 ms
0.18/0.24

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-1083689-1215229255/watcher-1083689-1215229255 -o /tmp/evaluation-result-1083689-1215229255/solver-1083689-1215229255 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/solver HOME/instance-1083689-1215229255 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.15 2.04 2.01 4/81 4821
/proc/meminfo: memFree=1175432/2055920 swapFree=4180808/4192956
[pid=4821] ppid=4819 vsize=18572 CPUtime=0
/proc/4821/stat : 4821 (runsolver) R 4819 4821 4223 0 -1 4194368 15 0 0 0 0 0 0 0 20 0 1 0 2001895301 19017728 292 996147200 4194304 4296836 548682068480 18446744073709551615 257203694887 0 0 4096 24578 0 0 0 17 1 0 0
/proc/4821/statm: 4643 292 257 25 0 2626 0

[startup+0.068229 s]
/proc/loadavg: 2.15 2.04 2.01 4/81 4821
/proc/meminfo: memFree=1175432/2055920 swapFree=4180808/4192956
[pid=4821] ppid=4819 vsize=56080 CPUtime=0.05
/proc/4821/stat : 4821 (bprolog) R 4819 4821 4223 0 -1 4194304 1116 0 0 0 3 2 0 0 20 0 1 0 2001895301 57425920 829 996147200 134512640 134990860 4294956096 18446744073709551615 134565774 0 0 4096 2 0 0 0 17 1 0 0
/proc/4821/statm: 14020 829 177 116 0 13531 0
Current children cumulated CPU time (s) 0.05
Current children cumulated vsize (KiB) 56080

[startup+0.101586 s]
/proc/loadavg: 2.15 2.04 2.01 4/81 4821
/proc/meminfo: memFree=1175432/2055920 swapFree=4180808/4192956
[pid=4821] ppid=4819 vsize=56080 CPUtime=0.08
/proc/4821/stat : 4821 (bprolog) R 4819 4821 4223 0 -1 4194304 1116 0 0 0 4 4 0 0 20 0 1 0 2001895301 57425920 829 996147200 134512640 134990860 4294956096 18446744073709551615 134598037 0 0 4096 2 0 0 0 17 1 0 0
/proc/4821/statm: 14020 829 177 116 0 13531 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 56080

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

[startup+0.2016 s]
/proc/loadavg: 2.15 2.04 2.01 4/81 4821
/proc/meminfo: memFree=1175432/2055920 swapFree=4180808/4192956
[pid=4821] ppid=4819 vsize=56080 CPUtime=0.18
/proc/4821/stat : 4821 (bprolog) R 4819 4821 4223 0 -1 4194304 1119 0 0 0 9 9 0 0 20 0 1 0 2001895301 57425920 832 996147200 134512640 134990860 4294956096 18446744073709551615 4294960144 0 0 4096 2 0 0 0 17 1 0 0
/proc/4821/statm: 14020 832 177 116 0 13531 0
Current children cumulated CPU time (s) 0.18
Current children cumulated vsize (KiB) 56080

Child status: 0
Real time (s): 0.242894
CPU time (s): 0.231964
CPU user time (s): 0.13098
CPU system time (s): 0.100984
CPU usage (%): 95.5001
Max. virtual memory (cumulated for all children) (KiB): 56080

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

runsolver used 0.004999 second user time and 0.008998 second system time

The end

Launcher Data (download as text)

Begin job on node65 at 2008-07-05 05:40:55
IDJOB=1083689
IDBENCH=57500
IDSOLVER=347
FILE ID=node65/1083689-1215229255
PBS_JOBID= 7881866
Free space on /tmp= 66492 MiB

SOLVER NAME= bpsolver 2008-06-27
BENCH NAME= CPAI08/csp/rlfapScensMod/normalized-scen2-f24.xml
COMMAND LINE= HOME/solver BENCHNAMENOEXT TIMEOUT
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1083689-1215229255/watcher-1083689-1215229255 -o /tmp/evaluation-result-1083689-1215229255/solver-1083689-1215229255 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/solver HOME/instance-1083689-1215229255 1800

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= 5a67895b6e4679565fdc3dec2d0f4ec1
RANDOM SEED=945663521

node65.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.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:       1175912 kB
Buffers:         15600 kB
Cached:         126456 kB
SwapCached:       5980 kB
Active:         768076 kB
Inactive:        57628 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1175912 kB
SwapTotal:     4192956 kB
SwapFree:      4180808 kB
Dirty:            2096 kB
Writeback:           0 kB
Mapped:         699808 kB
Slab:            38212 kB
Committed_AS:  4734424 kB
PageTables:       3216 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= 66492 MiB
End job on node65 at 2008-07-05 05:40:55