Trace number 2074222

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.118981 0.125947

DiagnosticValue
ASSIGNMENTS29

General information on the benchmark

Namecsp/jobShop-ewddr2/
normalized-ewddr2-10-by-5-3.xml
MD5SUM0c2cc22208dbe8b0d9892e512f71aad5
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.035994
Satisfiable
(Un)Satisfiability was proved
Number of variables50
Number of constraints265
Maximum constraint arity2
Maximum domain size152
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.08/0.12	c Seed is 106931653
0.08/0.12	c Constructing HOME/instance-2074222-1247712301.xml  with 1655 constraints
0.08/0.12	c Solving 29 backtracks 1 restarts
0.08/0.12	s SATISFIABLE
0.08/0.12	c V0=101, V1=110, V2=121, V3=132, V4=136, V5=37, V6=158, V7=164, V8=174, V9=178, V10=16, V11=24, V12=35, V13=79, V14=84, V15=30, V16=51, V17=62, V18=89, V19=93, V20=37, V21=47, V22=102, V23=118, V24=124, V25=33, V26=44, V27=50, V28=65, V29=112, V30=6, V31=17, V32=24, V33=64, V34=68, V35=118, V36=126, V37=134, V38=144, V39=151, V40=73, V41=83, V42=92, V43=161, V44=164, V45=64, V46=72, V47=75, V48=91, V49=102, 
0.08/0.12	v 101 110 121 132 136 37 158 164 174 178 16 24 35 79 84 30 51 62 89 93 37 47 102 118 124 33 44 50 65 112 6 17 24 64 68 118 126 134 144 151 73 83 92 161 164 64 72 75 91 102 
0.08/0.12	d ASSIGNMENTS 29

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-2074222-1247712301/watcher-2074222-1247712301 -o /tmp/evaluation-result-2074222-1247712301/solver-2074222-1247712301 -C 1800 -W 2000 -M 900 HOME/pcssolve -s 106931653 HOME/instance-2074222-1247712301.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.10 2.04 2.02 4/81 17693
/proc/meminfo: memFree=1544128/2055920 swapFree=4192812/4192956
[pid=17693] ppid=17691 vsize=18576 CPUtime=0
/proc/17693/stat : 17693 (runsolver) R 17691 17693 17399 0 -1 4194368 15 0 0 0 0 0 0 0 20 0 1 0 58292831 19021824 284 996147200 4194304 4302564 548682068496 18446744073709551615 271638392103 0 0 4096 24578 0 0 0 17 1 0 0
/proc/17693/statm: 4644 284 249 26 0 2626 0

[startup+0.0163919 s]
/proc/loadavg: 2.10 2.04 2.02 4/81 17693
/proc/meminfo: memFree=1544128/2055920 swapFree=4192812/4192956
[pid=17693] ppid=17691 vsize=0 CPUtime=0
/proc/17693/stat : 17693 (pcssolve) R 17691 17693 17399 0 -1 4194304 353 659 0 0 0 0 0 0 23 0 1 0 58292831 0 0 996147200 0 0 0 18446744073709551615 271638392103 0 0 4096 0 0 0 0 17 1 0 0
/proc/17693/statm: 0 0 0 0 0 0 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 0

[startup+0.101378 s]
/proc/loadavg: 2.10 2.04 2.02 4/81 17693
/proc/meminfo: memFree=1544128/2055920 swapFree=4192812/4192956
[pid=17693] ppid=17691 vsize=5952 CPUtime=0.08
/proc/17693/stat : 17693 (pcs.big) R 17691 17693 17399 0 -1 4194304 1203 659 0 0 8 0 0 0 18 0 1 0 58292831 6094848 781 996147200 134512640 135215973 4294956304 18446744073709551615 4158960269 0 0 4096 0 0 0 0 17 1 0 0
/proc/17693/statm: 1488 781 408 171 0 413 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 5952

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

Child status: 0
Real time (s): 0.125947
CPU time (s): 0.118981
CPU user time (s): 0.106983
CPU system time (s): 0.011998
CPU usage (%): 94.4691
Max. virtual memory (cumulated for all children) (KiB): 5952

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.106983
system time used= 0.011998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1871
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= 18
involuntary context switches= 13

runsolver used 0.003999 second user time and 0.003999 second system time

The end

Launcher Data 

Begin job on node67 at 2009-07-16 04:45:01
IDJOB=2074222
IDBENCH=56077
IDSOLVER=733
FILE ID=node67/2074222-1247712301
PBS_JOBID= 9521408
Free space on /tmp= 66332 MiB

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

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

MD5SUM BENCH= 0c2cc22208dbe8b0d9892e512f71aad5
RANDOM SEED=106931653

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:       1544608 kB
Buffers:         66924 kB
Cached:         259816 kB
SwapCached:          0 kB
Active:         178032 kB
Inactive:       259368 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1544608 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1840 kB
Writeback:           0 kB
Mapped:         130988 kB
Slab:            58768 kB
Committed_AS:   651092 kB
PageTables:       2072 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 04:45:01