Trace number 2075718

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.139977 0.14661

DiagnosticValue
ASSIGNMENTS39

General information on the benchmark

Namecsp/jobShop-enddr1/
normalized-enddr1-10-by-5-3.xml
MD5SUM7676ba89a6c27576d9a50d1678221d98
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.027995
Satisfiable
(Un)Satisfiability was proved
Number of variables50
Number of constraints265
Maximum constraint arity2
Maximum domain size126
Number of constraints which are defined in extension0
Number of constraints which are defined in intension265
Global constraints used (with number of constraints)

Solver Data 

0.00/0.01	c has big domains
0.00/0.01	c big-domain mode
0.10/0.14	c Seed is 1527607267
0.10/0.14	c Constructing HOME/instance-2075718-1247713849.xml  with 1655 constraints
0.10/0.14	c Solving 39 backtracks 1 restarts
0.10/0.14	s SATISFIABLE
0.10/0.14	c V0=12, V1=22, V2=30, V3=102, V4=112, V5=28, V6=35, V7=46, V8=127, V9=133, V10=73, V11=77, V12=140, V13=151, V14=158, V15=71, V16=78, V17=86, V18=101, V19=145, V20=73, V21=91, V22=108, V23=127, V24=137, V25=48, V26=56, V27=59, V28=108, V29=148, V30=66, V31=88, V32=98, V33=135, V34=141, V35=82, V36=112, V37=118, V38=131, V39=139, V40=60, V41=70, V42=73, V43=113, V44=116, V45=0, V46=5, V47=15, V48=115, V49=125, 
0.10/0.14	v 12 22 30 102 112 28 35 46 127 133 73 77 140 151 158 71 78 86 101 145 73 91 108 127 137 48 56 59 108 148 66 88 98 135 141 82 112 118 131 139 60 70 73 113 116 0 5 15 115 125 
0.10/0.14	d ASSIGNMENTS 39

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-2075718-1247713849/watcher-2075718-1247713849 -o /tmp/evaluation-result-2075718-1247713849/solver-2075718-1247713849 -C 1800 -W 2000 -M 900 HOME/pcssolve -s 1527607267 HOME/instance-2075718-1247713849.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.09 2.06 2.01 4/82 16867
/proc/meminfo: memFree=1106832/2055920 swapFree=4192812/4192956
[pid=16867] ppid=16865 vsize=5356 CPUtime=0
/proc/16867/stat : 16867 (pcssolve) R 16865 16867 15459 0 -1 4194304 266 0 0 0 0 0 0 0 20 0 1 0 58452182 5484544 234 996147200 4194304 4889804 548682068800 18446744073709551615 4365152 0 0 4100 65536 0 0 0 17 1 0 0
/proc/16867/statm: 1339 234 195 169 0 50 0

[startup+0.121391 s]
/proc/loadavg: 2.09 2.06 2.01 4/82 16867
/proc/meminfo: memFree=1106832/2055920 swapFree=4192812/4192956
[pid=16867] ppid=16865 vsize=5744 CPUtime=0.1
/proc/16867/stat : 16867 (pcs.big) R 16865 16867 15459 0 -1 4194304 1112 662 0 0 10 0 0 0 18 0 1 0 58452182 5881856 743 996147200 134512640 135215973 4294956304 18446744073709551615 134590262 0 0 4096 0 0 0 0 17 1 0 0
/proc/16867/statm: 1436 743 408 171 0 361 0
Current children cumulated CPU time (s) 0.1
Current children cumulated vsize (KiB) 5744

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

[startup+0.121391 s]
/proc/loadavg: 2.09 2.06 2.01 4/82 16867
/proc/meminfo: memFree=1106832/2055920 swapFree=4192812/4192956
[pid=16867] ppid=16865 vsize=5744 CPUtime=0.1
/proc/16867/stat : 16867 (pcs.big) R 16865 16867 15459 0 -1 4194304 1112 662 0 0 10 0 0 0 18 0 1 0 58452182 5881856 743 996147200 134512640 135215973 4294956304 18446744073709551615 134590262 0 0 4096 0 0 0 0 17 1 0 0
/proc/16867/statm: 1436 743 408 171 0 361 0
Current children cumulated CPU time (s) 0.1
Current children cumulated vsize (KiB) 5744

Child status: 0
Real time (s): 0.14661
CPU time (s): 0.139977
CPU user time (s): 0.131979
CPU system time (s): 0.007998
CPU usage (%): 95.4757
Max. virtual memory (cumulated for all children) (KiB): 5744

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.131979
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= 1876
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= 19
involuntary context switches= 12

runsolver used 0.001999 second user time and 0.009998 second system time

The end

Launcher Data 

Begin job on node17 at 2009-07-16 05:10:49
IDJOB=2075718
IDBENCH=56339
IDSOLVER=733
FILE ID=node17/2075718-1247713849
PBS_JOBID= 9521314
Free space on /tmp= 66348 MiB

SOLVER NAME= pcs 0.2
BENCH NAME= CPAI08/csp/jobShop-enddr1/normalized-enddr1-10-by-5-3.xml
COMMAND LINE= HOME/pcssolve -s RANDOMSEED BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2075718-1247713849/watcher-2075718-1247713849 -o /tmp/evaluation-result-2075718-1247713849/solver-2075718-1247713849 -C 1800 -W 2000 -M 900  HOME/pcssolve -s 1527607267 HOME/instance-2075718-1247713849.xml

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

MD5SUM BENCH= 7676ba89a6c27576d9a50d1678221d98
RANDOM SEED=1527607267

node17.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.213
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.213
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:       1107312 kB
Buffers:         93352 kB
Cached:         634520 kB
SwapCached:          0 kB
Active:         224636 kB
Inactive:       644168 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1107312 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1764 kB
Writeback:           0 kB
Mapped:         161300 kB
Slab:            64756 kB
Committed_AS:   703248 kB
PageTables:       2192 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= 66348 MiB
End job on node17 at 2009-07-16 05:10:50