Trace number 2075741

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.072988 0.0775271

DiagnosticValue
ASSIGNMENTS4

General information on the benchmark

Namecsp/jobShop-enddr1/
normalized-enddr1-10-by-5-9.xml
MD5SUMbbe49493e0d927785701c1e07cd803b2
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.028995
Satisfiable
(Un)Satisfiability was proved
Number of variables50
Number of constraints265
Maximum constraint arity2
Maximum domain size131
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.05/0.07	c Seed is 1642949549
0.05/0.07	c Constructing HOME/instance-2075741-1247713871.xml  with 1655 constraints
0.05/0.07	c Solving 4 backtracks
0.05/0.07	s SATISFIABLE
0.05/0.07	c V0=19, V1=116, V2=119, V3=129, V4=136, V5=0, V6=9, V7=15, V8=24, V9=33, V10=109, V11=113, V12=129, V13=138, V14=147, V15=3, V16=129, V17=138, V18=153, V19=156, V20=7, V21=90, V22=101, V23=116, V24=120, V25=0, V26=9, V27=24, V28=74, V29=101, V30=33, V31=50, V32=53, V33=67, V34=74, V35=16, V36=56, V37=79, V38=87, V39=105, V40=0, V41=13, V42=36, V43=46, V44=50, V45=0, V46=25, V47=67, V48=79, V49=136, 
0.05/0.07	v 19 116 119 129 136 0 9 15 24 33 109 113 129 138 147 3 129 138 153 156 7 90 101 116 120 0 9 24 74 101 33 50 53 67 74 16 56 79 87 105 0 13 36 46 50 0 25 67 79 136 
0.05/0.07	d ASSIGNMENTS 4

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-2075741-1247713871/watcher-2075741-1247713871 -o /tmp/evaluation-result-2075741-1247713871/solver-2075741-1247713871 -C 1800 -W 2000 -M 900 HOME/pcssolve -s 1642949549 HOME/instance-2075741-1247713871.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.07 2.13 2.07 4/82 10696
/proc/meminfo: memFree=874908/2055920 swapFree=4192812/4192956
[pid=10696] ppid=10694 vsize=18576 CPUtime=0
/proc/10696/stat : 10696 (runsolver) R 10694 10696 8667 0 -1 4194368 15 0 0 0 0 0 0 0 20 0 1 0 58454209 19021824 284 996147200 4194304 4302564 548682068496 18446744073709551615 215418989863 0 0 4096 24578 0 0 0 17 1 0 0
/proc/10696/statm: 4644 284 249 26 0 2626 0

[startup+0.0692449 s]
/proc/loadavg: 2.07 2.13 2.07 4/82 10696
/proc/meminfo: memFree=874908/2055920 swapFree=4192812/4192956
[pid=10696] ppid=10694 vsize=5744 CPUtime=0.05
/proc/10696/stat : 10696 (pcs.big) R 10694 10696 8667 0 -1 4194304 1120 659 0 0 5 0 0 0 18 0 1 0 58454209 5881856 751 996147200 134512640 135215973 4294956304 18446744073709551615 4158960128 0 0 4096 0 0 0 0 17 1 0 0
/proc/10696/statm: 1436 751 408 171 0 361 0
Current children cumulated CPU time (s) 0.05
Current children cumulated vsize (KiB) 5744

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

[startup+0.0692449 s]
/proc/loadavg: 2.07 2.13 2.07 4/82 10696
/proc/meminfo: memFree=874908/2055920 swapFree=4192812/4192956
[pid=10696] ppid=10694 vsize=5744 CPUtime=0.05
/proc/10696/stat : 10696 (pcs.big) R 10694 10696 8667 0 -1 4194304 1120 659 0 0 5 0 0 0 18 0 1 0 58454209 5881856 751 996147200 134512640 135215973 4294956304 18446744073709551615 4158960128 0 0 4096 0 0 0 0 17 1 0 0
/proc/10696/statm: 1436 751 408 171 0 361 0
Current children cumulated CPU time (s) 0.05
Current children cumulated vsize (KiB) 5744

Child status: 0
Real time (s): 0.0775271
CPU time (s): 0.072988
CPU user time (s): 0.058991
CPU system time (s): 0.013997
CPU usage (%): 94.1451
Max. virtual memory (cumulated for all children) (KiB): 5744

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.058991
system time used= 0.013997
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1854
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= 9

runsolver used 0.002999 second user time and 0.005999 second system time

The end

Launcher Data 

Begin job on node9 at 2009-07-16 05:11:11
IDJOB=2075741
IDBENCH=56341
IDSOLVER=734
FILE ID=node9/2075741-1247713871
PBS_JOBID= 9521367
Free space on /tmp= 66376 MiB

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

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

MD5SUM BENCH= bbe49493e0d927785701c1e07cd803b2
RANDOM SEED=1642949549

node9.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.216
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.216
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:        875388 kB
Buffers:         69592 kB
Cached:         272652 kB
SwapCached:          0 kB
Active:         838704 kB
Inactive:       270872 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        875388 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1776 kB
Writeback:           0 kB
Mapped:         787744 kB
Slab:            54728 kB
Committed_AS:  1299508 kB
PageTables:       3292 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= 66376 MiB
End job on node9 at 2009-07-16 05:11:11