Trace number 2085662

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
pcs 0.3.2SAT 0.026995 0.0290659

DiagnosticValue
ASSIGNMENTS0

General information on the benchmark

Namecsp/graphColoring/insertion/full-insertion/
normalized-3-fullins-3-6.xml
MD5SUM6a42458055f9f919e0ad825af2236ae8
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.016996
Satisfiable
(Un)Satisfiability was proved
Number of variables80
Number of constraints346
Maximum constraint arity2
Maximum domain size6
Number of constraints which are defined in extension0
Number of constraints which are defined in intension346
Global constraints used (with number of constraints)

Solver Data 

0.00/0.01	c small-domain mode
0.00/0.02	c Seed is 1310630551
0.00/0.02	c Constructing HOME/instance-2085662-1247726268.xml  with 346 constraints
0.00/0.02	c Solving 0 backtracks
0.00/0.02	s SATISFIABLE
0.00/0.02	c V0=2, V1=3, V2=0, V3=0, V4=3, V5=3, V6=2, V7=2, V8=0, V9=0, V10=2, V11=5, V12=0, V13=4, V14=3, V15=1, V16=1, V17=1, V18=1, V19=1, V20=1, V21=1, V22=1, V23=1, V24=1, V25=1, V26=1, V27=1, V28=1, V29=1, V30=0, V31=0, V32=0, V33=0, V34=0, V35=0, V36=0, V37=0, V38=0, V39=0, V40=0, V41=0, V42=0, V43=0, V44=0, V45=1, V46=1, V47=1, V48=1, V49=1, V50=1, V51=1, V52=1, V53=1, V54=1, V55=1, V56=1, V57=1, V58=1, V59=1, V60=0, V61=0, V62=0, V63=0, V64=0, V65=0, V66=0, V67=0, V68=0, V69=0, V70=0, V71=0, V72=0, V73=0, V74=0, V75=3, V76=2, V77=4, V78=0, V79=1, 
0.00/0.02	v 2 3 0 0 3 3 2 2 0 0 2 5 0 4 3 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3 2 4 0 1 
0.00/0.02	d ASSIGNMENTS 0

Verifier Data 

OK

Watcher Data 

runsolver version 3.2.9 (svn:492) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2085662-1247726268/watcher-2085662-1247726268 -o /tmp/evaluation-result-2085662-1247726268/solver-2085662-1247726268 -C 1800 -W 2000 -M 900 HOME/pcssolve -s 1310630551 HOME/instance-2085662-1247726268.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): 2000 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


[startup+0 s]
/proc/loadavg: 1.92 1.97 1.99 4/82 14978
/proc/meminfo: memFree=1634992/2055920 swapFree=4192812/4192956
[pid=14978] ppid=14976 vsize=5356 CPUtime=0
/proc/14978/stat : 14978 (pcssolve) S 14976 14978 14707 0 -1 4194304 305 0 0 0 0 0 0 0 18 0 1 0 59692194 5484544 242 996147200 4194304 4889804 548682068800 18446744073709551615 243665527620 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/14978/statm: 1339 242 201 169 0 50 0
[pid=14979] ppid=14978 vsize=5356 CPUtime=0
/proc/14979/stat : 14979 (pcssolve) R 14978 14978 14707 0 -1 4194368 22 0 0 0 0 0 0 0 18 0 1 0 59692194 5484544 243 996147200 4194304 4889804 548682068800 18446744073709551615 243665530151 0 0 4096 0 0 0 0 17 1 0 0
/proc/14979/statm: 1339 243 202 169 0 50 0
[pid=14980] ppid=14978 vsize=3676 CPUtime=0
/proc/14980/stat : 14980 (grep) S 14978 14978 14707 0 -1 4194304 154 0 0 0 0 0 0 0 18 0 1 0 59692194 3764224 121 996147200 4194304 4274172 548682069040 18446744073709551615 243665698898 0 0 4096 0 18446744071563648864 0 0 17 0 0 0
/proc/14980/statm: 919 121 99 19 0 43 0

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

Child status: 0
Real time (s): 0.0290659
CPU time (s): 0.026995
CPU user time (s): 0.018997
CPU system time (s): 0.007998
CPU usage (%): 92.8752
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.018997
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= 1664
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= 22
involuntary context switches= 6

runsolver used 0.002999 second user time and 0.005999 second system time

The end

Launcher Data 

Begin job on node84 at 2009-07-16 08:37:48
IDJOB=2085662
IDBENCH=58476
IDSOLVER=733
FILE ID=node84/2085662-1247726268
PBS_JOBID= 9521598
Free space on /tmp= 66184 MiB

SOLVER NAME= pcs 0.2
BENCH NAME= CPAI08/csp/graphColoring/insertion/full-insertion/normalized-3-fullins-3-6.xml
COMMAND LINE= HOME/pcssolve -s RANDOMSEED BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2085662-1247726268/watcher-2085662-1247726268 -o /tmp/evaluation-result-2085662-1247726268/solver-2085662-1247726268 -C 1800 -W 2000 -M 900  HOME/pcssolve -s 1310630551 HOME/instance-2085662-1247726268.xml

TIME LIMIT= 1800 seconds
MEMORY LIMIT= 900 MiB
MAX NB THREAD= 0

MD5SUM BENCH= 6a42458055f9f919e0ad825af2236ae8
RANDOM SEED=1310630551

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.259
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.259
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:       1635472 kB
Buffers:         75060 kB
Cached:         214824 kB
SwapCached:          0 kB
Active:         125544 kB
Inactive:       206544 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1635472 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            3728 kB
Writeback:           0 kB
Mapped:          62592 kB
Slab:            73628 kB
Committed_AS:   540928 kB
PageTables:       1856 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= 66180 MiB
End job on node84 at 2009-07-16 08:37:48