Trace number 2086081

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-restart 0.3.2SAT 0.119981 0.117993

DiagnosticValue
ASSIGNMENTS30

General information on the benchmark

Namecsp/jobShop-e0ddr2/
normalized-e0ddr2-10-by-5-8.xml
MD5SUMda9db23f5ede02b3ff6c2a743d786917
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.040993
Satisfiable
(Un)Satisfiability was proved
Number of variables50
Number of constraints265
Maximum constraint arity2
Maximum domain size132
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.00/0.02	c Seed is 244618370
0.00/0.02	c Constructing HOME/instance-2086081-1247726714.xml  with 1655 constraints
0.08/0.11	c Solving 30 backtracks 1 restarts
0.08/0.11	s SATISFIABLE
0.08/0.11	c V0=28, V1=39, V2=46, V3=58, V4=156, V5=35, V6=101, V7=110, V8=120, V9=123, V10=73, V11=90, V12=101, V13=127, V14=135, V15=0, V16=11, V17=19, V18=55, V19=73, V20=63, V21=79, V22=127, V23=137, V24=146, V25=30, V26=52, V27=59, V28=79, V29=84, V30=1, V31=4, V32=10, V33=43, V34=51, V35=58, V36=69, V37=73, V38=84, V39=93, V40=12, V41=22, V42=32, V43=51, V44=63, V45=1, V46=41, V47=86, V48=96, V49=107, 
0.08/0.11	v 28 39 46 58 156 35 101 110 120 123 73 90 101 127 135 0 11 19 55 73 63 79 127 137 146 30 52 59 79 84 1 4 10 43 51 58 69 73 84 93 12 22 32 51 63 1 41 86 96 107 
0.08/0.11	d ASSIGNMENTS 30

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-2086081-1247726714/watcher-2086081-1247726714 -o /tmp/evaluation-result-2086081-1247726714/solver-2086081-1247726714 -C 1800 -W 2000 -M 900 HOME/pcssolve -s 244618370 HOME/instance-2086081-1247726714.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.24 2.29 2.12 4/82 15154
/proc/meminfo: memFree=1359904/2055920 swapFree=4192812/4192956
[pid=15154] ppid=15152 vsize=5360 CPUtime=0
/proc/15154/stat : 15154 (pcssolve) R 15152 15154 15086 0 -1 4194304 353 661 0 0 0 0 0 0 16 0 1 0 59736740 5488640 244 996147200 4194304 4889804 548682068800 18446744073709551615 4459254 0 0 4100 65536 0 0 0 17 1 0 0
/proc/15154/statm: 1340 244 202 169 0 51 0

[startup+0.0924041 s]
/proc/loadavg: 2.24 2.29 2.12 4/82 15154
/proc/meminfo: memFree=1359904/2055920 swapFree=4192812/4192956
[pid=15154] ppid=15152 vsize=5956 CPUtime=0.07
/proc/15154/stat : 15154 (pcs.big) R 15152 15154 15086 0 -1 4194304 1208 661 0 0 7 0 0 0 19 0 1 0 59736740 6098944 786 996147200 134512640 135215973 4294956304 18446744073709551615 134533266 0 0 4096 0 0 0 0 17 0 0 0
/proc/15154/statm: 1489 786 408 171 0 414 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 5956

[startup+0.102447 s]
/proc/loadavg: 2.24 2.29 2.12 4/82 15154
/proc/meminfo: memFree=1359904/2055920 swapFree=4192812/4192956
[pid=15154] ppid=15152 vsize=5956 CPUtime=0.08
/proc/15154/stat : 15154 (pcs.big) R 15152 15154 15086 0 -1 4194304 1210 661 0 0 8 0 0 0 19 0 1 0 59736740 6098944 788 996147200 134512640 135215973 4294956304 18446744073709551615 134609891 0 0 4096 0 0 0 0 17 0 0 0
/proc/15154/statm: 1489 788 408 171 0 414 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 5956

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

Child status: 0
Real time (s): 0.117993
CPU time (s): 0.119981
CPU user time (s): 0.106983
CPU system time (s): 0.012998
CPU usage (%): 101.685
Max. virtual memory (cumulated for all children) (KiB): 5956

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.106983
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= 1889
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= 17
involuntary context switches= 7

runsolver used 0.002999 second user time and 0.004999 second system time

The end

Launcher Data 

Begin job on node85 at 2009-07-16 08:45:14
IDJOB=2086081
IDBENCH=58560
IDSOLVER=734
FILE ID=node85/2086081-1247726714
PBS_JOBID= 9521614
Free space on /tmp= 126540 MiB

SOLVER NAME= pcs-restart 0.2.restart
BENCH NAME= CPAI08/csp/jobShop-e0ddr2/normalized-e0ddr2-10-by-5-8.xml
COMMAND LINE= HOME/pcssolve -s RANDOMSEED BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2086081-1247726714/watcher-2086081-1247726714 -o /tmp/evaluation-result-2086081-1247726714/solver-2086081-1247726714 -C 1800 -W 2000 -M 900  HOME/pcssolve -s 244618370 HOME/instance-2086081-1247726714.xml

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

MD5SUM BENCH= da9db23f5ede02b3ff6c2a743d786917
RANDOM SEED=244618370

node85.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.220
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.220
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:       1360320 kB
Buffers:         91056 kB
Cached:         457296 kB
SwapCached:          0 kB
Active:         276308 kB
Inactive:       345552 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1360320 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1940 kB
Writeback:           0 kB
Mapped:          93780 kB
Slab:            58824 kB
Committed_AS:   548208 kB
PageTables:       1944 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= 126536 MiB
End job on node85 at 2009-07-16 08:45:14