Trace number 2067776

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.038994 0.0438671

DiagnosticValue
ASSIGNMENTS12

General information on the benchmark

Namecsp/pseudo/aim/
normalized-aim-50-1-6-4.xml
MD5SUM92f4c4f4c04d9881c8d021484d7cab4c
Bench CategoryN-ARY-INT (n-ary constraints in intension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.014997
Satisfiable
(Un)Satisfiability was proved
Number of variables100
Number of constraints130
Maximum constraint arity3
Maximum domain size2
Number of constraints which are defined in extension0
Number of constraints which are defined in intension130
Global constraints used (with number of constraints)

Solver Data 

0.00/0.01	c has operations which may create big domains
0.00/0.01	c big-domain mode
0.00/0.04	c Seed is 957210983
0.00/0.04	c Constructing HOME/instance-2067776-1247705845.xml  with 440 constraints
0.00/0.04	c Solving 12 backtracks
0.00/0.04	s SATISFIABLE
0.00/0.04	c V0=0, V1=1, V2=1, V3=0, V4=0, V5=1, V6=0, V7=1, V8=0, V9=1, V10=1, V11=0, V12=0, V13=1, V14=0, V15=1, V16=0, V17=1, V18=1, V19=0, V20=1, V21=0, V22=0, V23=1, V24=0, V25=1, V26=1, V27=0, V28=1, V29=0, V30=1, V31=0, V32=0, V33=1, V34=1, V35=0, V36=1, V37=0, V38=1, V39=0, V40=0, V41=1, V42=1, V43=0, V44=1, V45=0, V46=1, V47=0, V48=1, V49=0, V50=0, V51=1, V52=0, V53=1, V54=0, V55=1, V56=0, V57=1, V58=0, V59=1, V60=0, V61=1, V62=1, V63=0, V64=0, V65=1, V66=0, V67=1, V68=1, V69=0, V70=1, V71=0, V72=0, V73=1, V74=0, V75=1, V76=1, V77=0, V78=1, V79=0, V80=0, V81=1, V82=1, V83=0, V84=1, V85=0, V86=1, V87=0, V88=0, V89=1, V90=1, V91=0, V92=1, V93=0, V94=0, V95=1, V96=0, V97=1, V98=1, V99=0, 
0.00/0.04	v 0 1 1 0 0 1 0 1 0 1 1 0 0 1 0 1 0 1 1 0 1 0 0 1 0 1 1 0 1 0 1 0 0 1 1 0 1 0 1 0 0 1 1 0 1 0 1 0 1 0 0 1 0 1 0 1 0 1 0 1 0 1 1 0 0 1 0 1 1 0 1 0 0 1 0 1 1 0 1 0 0 1 1 0 1 0 1 0 0 1 1 0 1 0 0 1 0 1 1 0 
0.00/0.04	d ASSIGNMENTS 12

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-2067776-1247705845/watcher-2067776-1247705845 -o /tmp/evaluation-result-2067776-1247705845/solver-2067776-1247705845 -C 1800 -W 2000 -M 900 HOME/pcssolve -s 957210983 HOME/instance-2067776-1247705845.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: 2.01 1.99 1.99 4/82 15191
/proc/meminfo: memFree=1004536/2055920 swapFree=4192812/4192956
[pid=15191] ppid=15189 vsize=18576 CPUtime=0
/proc/15191/stat : 15191 (runsolver) R 15189 15191 12845 0 -1 4194368 15 0 0 0 0 0 0 0 20 0 1 0 57650275 19021824 284 996147200 4194304 4302564 548682068496 18446744073709551615 228774702375 0 0 4096 24578 0 0 0 17 1 0 0
/proc/15191/statm: 4644 284 249 26 0 2626 0

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

Child status: 0
Real time (s): 0.0438671
CPU time (s): 0.038994
CPU user time (s): 0.025996
CPU system time (s): 0.012998
CPU usage (%): 88.8912
Max. virtual memory (cumulated for all children) (KiB): 0

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

runsolver used 0.000999 second user time and 0.007998 second system time

The end

Launcher Data 

Begin job on node74 at 2009-07-16 02:57:25
IDJOB=2067776
IDBENCH=54697
IDSOLVER=733
FILE ID=node74/2067776-1247705845
PBS_JOBID= 9521169
Free space on /tmp= 103032 MiB

SOLVER NAME= pcs 0.2
BENCH NAME= CPAI08/csp/pseudo/aim/normalized-aim-50-1-6-4.xml
COMMAND LINE= HOME/pcssolve -s RANDOMSEED BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2067776-1247705845/watcher-2067776-1247705845 -o /tmp/evaluation-result-2067776-1247705845/solver-2067776-1247705845 -C 1800 -W 2000 -M 900  HOME/pcssolve -s 957210983 HOME/instance-2067776-1247705845.xml

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

MD5SUM BENCH= 92f4c4f4c04d9881c8d021484d7cab4c
RANDOM SEED=957210983

node74.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.234
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.234
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:       1004952 kB
Buffers:         67924 kB
Cached:         836748 kB
SwapCached:          0 kB
Active:         115876 kB
Inactive:       858656 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1004952 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            2052 kB
Writeback:           0 kB
Mapped:          90316 kB
Slab:            61368 kB
Committed_AS:   575652 kB
PageTables:       2024 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264960 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 103032 MiB
End job on node74 at 2009-07-16 02:57:25