Trace number 1053823

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
mddc-solv 2008-06-09SAT 0.104983 0.105001

DiagnosticValue
CHECKS26070

General information on the benchmark

Namecsp/aim-200/
normalized-aim-200-6-0-sat-2_ext.xml
MD5SUM6134633c83f48e046f576cefce3e531f
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.051991
Satisfiable
(Un)Satisfiability was proved
Number of variables200
Number of constraints1169
Maximum constraint arity3
Maximum domain size2
Number of constraints which are defined in extension1169
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.00/0.00	c loading... 0.07 secs
0.00/0.08	c smallest 4
0.00/0.08	c largest 5
0.00/0.08	c average 4.82609
0.00/0.08	
0.09/0.10	s SATISFIABLE
0.09/0.10	v 0 0 1 0 1 0 0 0 1 0 0 1 1 0 0 0 0 1 0 0 1 0 1 1 0 0 0 1 0 0 0 1 1 1 1 1 1 0 1 0 1 1 1 1 1 0 0 0 0 1 0 1 1 1 0 1 1 0 1 0 0 1 0 0 0 1 1 0 1 1 1 1 1 1 0 1 0 0 0 1 1 0 1 1 0 0 1 1 1 0 0 0 1 1 1 0 0 1 1 1 0 1 1 0 0 1 1 0 0 1 0 0 0 0 0 0 1 0 0 0 0 1 0 0 0 0 0 0 0 1 0 1 0 1 1 1 0 1 0 0 0 0 1 1 1 0 0 0 0 1 0 0 0 0 1 0 0 0 0 1 0 0 0 0 0 0 0 1 1 1 0 1 1 1 1 1 0 1 0 1 0 1 1 0 0 1 1 0 1 0 0 0 1 0 0 1 0 1 0 0
0.09/0.10	d CHECKS 26070
0.09/0.10	c FAILS 91
0.09/0.10	c RESTARTS 0

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-1053823-1215057680/watcher-1053823-1215057680 -o /tmp/evaluation-result-1053823-1215057680/solver-1053823-1215057680 -C 1800 -W 2200 -M 900 --output-limit 1,15 HOME/solver HOME/instance-1053823-1215057680.xml 

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.29 2.10 2.02 4/82 13799
/proc/meminfo: memFree=1748464/2055920 swapFree=4177412/4192956
[pid=13799] ppid=13797 vsize=8816 CPUtime=0
/proc/13799/stat : 13799 (solver) R 13797 13799 8924 0 -1 4194304 375 0 0 0 0 0 0 0 18 0 1 0 628688128 9027584 341 996147200 134512640 134773262 4294956256 18446744073709551615 4159705056 0 0 4096 0 0 0 0 17 0 0 0
/proc/13799/statm: 2204 348 301 63 0 1221 0

[startup+0.096005 s]
/proc/loadavg: 2.29 2.10 2.02 4/82 13799
/proc/meminfo: memFree=1748464/2055920 swapFree=4177412/4192956
[pid=13799] ppid=13797 vsize=4616 CPUtime=0.08
/proc/13799/stat : 13799 (solver) R 13797 13799 8924 0 -1 4194304 1602 0 0 0 8 0 0 0 18 0 1 0 628688128 4726784 539 996147200 134512640 134773262 4294956256 18446744073709551615 134526120 0 0 4096 0 0 0 0 17 0 0 0
/proc/13799/statm: 1154 539 363 63 0 171 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 4616

[startup+0.101002 s]
/proc/loadavg: 2.29 2.10 2.02 4/82 13799
/proc/meminfo: memFree=1748464/2055920 swapFree=4177412/4192956
[pid=13799] ppid=13797 vsize=4588 CPUtime=0.09
/proc/13799/stat : 13799 (solver) R 13797 13799 8924 0 -1 4194304 1602 0 0 0 9 0 0 0 18 0 1 0 628688128 4698112 539 996147200 134512640 134773262 4294956256 18446744073709551615 134526054 0 0 4096 0 0 0 0 17 0 0 0
/proc/13799/statm: 1147 539 363 63 0 164 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 4588

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

Child status: 0
Real time (s): 0.105001
CPU time (s): 0.104983
CPU user time (s): 0.095985
CPU system time (s): 0.008998
CPU usage (%): 99.9829
Max. virtual memory (cumulated for all children) (KiB): 4616

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

runsolver used 0.002999 second user time and 0.005999 second system time

The end

Launcher Data (download as text)

Begin job on node84 at 2008-07-03 06:01:20
IDJOB=1053823
IDBENCH=56113
IDSOLVER=311
FILE ID=node84/1053823-1215057680
PBS_JOBID= 7875010
Free space on /tmp= 66552 MiB

SOLVER NAME= mddc-solv 2008-06-09
BENCH NAME= CPAI08/csp/aim-200/normalized-aim-200-6-0-sat-2_ext.xml
COMMAND LINE= HOME/solver BENCHNAME 
RUNSOLVER COMMAND LINE= /home/evaluation/evaluation/pub/bin/runsolver --timestamp -w /tmp/evaluation-result-1053823-1215057680/watcher-1053823-1215057680 -o /tmp/evaluation-result-1053823-1215057680/solver-1053823-1215057680 -C 1800 -W 2200 -M 900 --output-limit 1,15  HOME/solver HOME/instance-1053823-1215057680.xml 

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB

MD5SUM BENCH= 6134633c83f48e046f576cefce3e531f
RANDOM SEED=678366127

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


/proc/meminfo:
MemTotal:      2055920 kB
MemFree:       1748880 kB
Buffers:         43808 kB
Cached:         168308 kB
SwapCached:       9700 kB
Active:         154164 kB
Inactive:        81272 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1748880 kB
SwapTotal:     4192956 kB
SwapFree:      4177412 kB
Dirty:             868 kB
Writeback:           0 kB
Mapped:          38240 kB
Slab:            56772 kB
Committed_AS:  1087892 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= 66552 MiB
End job on node84 at 2008-07-03 06:01:20