Trace number 2082307

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.038993 0.044129

DiagnosticValue
ASSIGNMENTS1

General information on the benchmark

Namecsp/langford2/
normalized-langford-2-15.xml
MD5SUMb3b5e0407ff63c54b23fa4bc60010aed
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.020996
Satisfiable
(Un)Satisfiability was proved
Number of variables30
Number of constraints450
Maximum constraint arity2
Maximum domain size30
Number of constraints which are defined in extension0
Number of constraints which are defined in intension450
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 1515633941
0.00/0.04	c Constructing HOME/instance-2082307-1247720889.xml 
0.00/0.04	c deduced all_different(V1,V2,V3,V4,V5,V6,V7,V8,V9,V10,V11,V12,V13,V14,V15,V16,V17,V18,V19,V20,V21,V22,V23,V24,V25,V26,V27,V28,V29,V0)
0.00/0.04	c  with 451 constraints
0.00/0.04	c Solving 1 backtracks
0.00/0.04	s SATISFIABLE
0.00/0.04	c V0=26, V1=22, V2=7, V3=24, V4=21, V5=3, V6=12, V7=6, V8=4, V9=8, V10=1, V11=5, V12=9, V13=2, V14=0, V15=28, V16=25, V17=11, V18=29, V19=27, V20=10, V21=20, V22=15, V23=14, V24=19, V25=13, V26=18, V27=23, V28=17, V29=16, 
0.00/0.04	v 26 22 7 24 21 3 12 6 4 8 1 5 9 2 0 28 25 11 29 27 10 20 15 14 19 13 18 23 17 16 
0.00/0.04	d ASSIGNMENTS 1

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-2082307-1247720889/watcher-2082307-1247720889 -o /tmp/evaluation-result-2082307-1247720889/solver-2082307-1247720889 -C 1800 -W 2000 -M 900 HOME/pcssolve -s 1515633941 HOME/instance-2082307-1247720889.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.98 2.01 2.00 4/82 19965
/proc/meminfo: memFree=1568208/2055920 swapFree=4192812/4192956
[pid=19965] ppid=19963 vsize=5356 CPUtime=0
/proc/19965/stat : 19965 (pcssolve) R 19963 19965 17507 0 -1 4194304 265 0 0 0 0 0 0 0 20 0 1 0 59151660 5484544 233 996147200 4194304 4889804 548682068800 18446744073709551615 4318827 0 0 4100 65536 0 0 0 17 1 0 0
/proc/19965/statm: 1339 233 194 169 0 50 0

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

Child status: 0
Real time (s): 0.044129
CPU time (s): 0.038993
CPU user time (s): 0.030995
CPU system time (s): 0.007998
CPU usage (%): 88.3613
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.030995
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= 1708
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= 10

runsolver used 0.000999 second user time and 0.008998 second system time

The end

Launcher Data 

Begin job on node67 at 2009-07-16 07:08:09
IDJOB=2082307
IDBENCH=57567
IDSOLVER=733
FILE ID=node67/2082307-1247720889
PBS_JOBID= 9521463
Free space on /tmp= 66332 MiB

SOLVER NAME= pcs 0.2
BENCH NAME= CPAI08/csp/langford2/normalized-langford-2-15.xml
COMMAND LINE= HOME/pcssolve -s RANDOMSEED BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2082307-1247720889/watcher-2082307-1247720889 -o /tmp/evaluation-result-2082307-1247720889/solver-2082307-1247720889 -C 1800 -W 2000 -M 900  HOME/pcssolve -s 1515633941 HOME/instance-2082307-1247720889.xml

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

MD5SUM BENCH= b3b5e0407ff63c54b23fa4bc60010aed
RANDOM SEED=1515633941

node67.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.239
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.239
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:       1568688 kB
Buffers:         74744 kB
Cached:         265256 kB
SwapCached:          0 kB
Active:         147680 kB
Inactive:       265364 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1568688 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1840 kB
Writeback:           0 kB
Mapped:          93488 kB
Slab:            59048 kB
Committed_AS:   565492 kB
PageTables:       2008 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= 66332 MiB
End job on node67 at 2009-07-16 07:08:09