Trace number 2078853

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.361944 0.373253

DiagnosticValue
ASSIGNMENTS179

General information on the benchmark

Namecsp/nengfa/
normalized-radi.xml
MD5SUM721069b46612331b45c8be673b18e6c8
Bench CategoryN-ARY-INT (n-ary constraints in intension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.074988
Satisfiable
(Un)Satisfiability was proved
Number of variables86
Number of constraints141
Maximum constraint arity10
Maximum domain size71
Number of constraints which are defined in extension0
Number of constraints which are defined in intension141
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 1842614637
0.00/0.02	c Constructing HOME/instance-2078853-1247716560.xml  with 1144 constraints
0.00/0.04	c Solving 179 backtracks 4 restarts
0.28/0.37	s SATISFIABLE
0.28/0.37	c V0=0, V1=0, V2=0, V3=1, V4=1, V5=0, V6=1, V7=0, V8=1, V9=0, V10=1, V11=0, V12=1, V13=1, V14=1, V15=0, V16=0, V17=1, V18=0, V19=0, V20=0, V21=0, V22=0, V23=1, V24=0, V25=0, V26=0, V27=1, V28=0, V29=1, V30=0, V31=1, V32=1, V33=0, V34=1, V35=0, V36=0, V37=1, V38=0, V39=0, V40=1, V41=0, V42=0, V43=0, V44=1, V45=0, V46=0, V47=0, V48=0, V49=1, V50=1, V51=0, V52=0, V53=1, V54=1, V55=0, V56=0, V57=0, V58=1, V59=0, V60=1, V61=0, V62=0, V63=0, V64=1, V65=0, V66=0, V67=0, V68=1, V69=1, V70=1, V71=1, V72=0, V73=1, V74=0, V75=0, V76=0, V77=1, V78=0, V79=0, V80=7, V81=5, V82=5, V83=2, V84=1, V85=20, 
0.28/0.37	v 0 0 0 1 1 0 1 0 1 0 1 0 1 1 1 0 0 1 0 0 0 0 0 1 0 0 0 1 0 1 0 1 1 0 1 0 0 1 0 0 1 0 0 0 1 0 0 0 0 1 1 0 0 1 1 0 0 0 1 0 1 0 0 0 1 0 0 0 1 1 1 1 0 1 0 0 0 1 0 0 7 5 5 2 1 20 
0.28/0.37	d ASSIGNMENTS 179

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-2078853-1247716560/watcher-2078853-1247716560 -o /tmp/evaluation-result-2078853-1247716560/solver-2078853-1247716560 -C 1800 -W 2000 -M 900 HOME/pcssolve -s 1842614637 HOME/instance-2078853-1247716560.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.91 1.95 1.98 4/72 12351
/proc/meminfo: memFree=1288584/2055920 swapFree=4192812/4192956
[pid=12351] ppid=12349 vsize=5356 CPUtime=0
/proc/12351/stat : 12351 (pcssolve) R 12349 12351 12002 0 -1 4194304 290 0 0 0 0 0 0 0 21 0 1 0 58719819 5484544 241 996147200 4194304 4889804 548682068800 18446744073709551615 258939087519 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/12351/statm: 1339 241 200 169 0 50 0
[pid=12352] ppid=12351 vsize=3676 CPUtime=0
/proc/12352/stat : 12352 (fgrep) R 12351 12351 12002 0 -1 4194304 144 0 0 0 0 0 0 0 22 0 1 0 58719820 3764224 111 996147200 4194304 4274172 548682068976 18446744073709551615 258939256914 0 0 4096 0 0 0 0 17 1 0 0
/proc/12352/statm: 919 111 85 19 0 43 0
[pid=12353] ppid=12351 vsize=5356 CPUtime=0
/proc/12353/stat : 12353 (pcssolve) R 12351 12351 12002 0 -1 4194368 0 0 0 0 0 0 0 0 21 0 1 0 58719820 5484544 241 996147200 4194304 4889804 548682068800 18446744073709551615 258939087519 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/12353/statm: 1339 241 200 169 0 50 0

[startup+0.106725 s]
/proc/loadavg: 1.91 1.95 1.98 4/72 12351
/proc/meminfo: memFree=1288584/2055920 swapFree=4192812/4192956
[pid=12351] ppid=12349 vsize=5424 CPUtime=0.08
/proc/12351/stat : 12351 (pcs.big) R 12349 12351 12002 0 -1 4194304 1044 657 0 0 8 0 0 0 23 0 1 0 58719819 5554176 675 996147200 134512640 135215973 4294956304 18446744073709551615 134592807 0 0 4096 0 0 0 0 17 1 0 0
/proc/12351/statm: 1356 675 416 171 0 281 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 5424

[startup+0.202702 s]
/proc/loadavg: 1.91 1.95 1.98 4/72 12351
/proc/meminfo: memFree=1288584/2055920 swapFree=4192812/4192956
[pid=12351] ppid=12349 vsize=5552 CPUtime=0.18
/proc/12351/stat : 12351 (pcs.big) R 12349 12351 12002 0 -1 4194304 1078 657 0 0 18 0 0 0 24 0 1 0 58719819 5685248 709 996147200 134512640 135215973 4294956304 18446744073709551615 4158960136 0 0 4096 0 0 0 0 17 1 0 0
/proc/12351/statm: 1388 709 416 171 0 313 0
Current children cumulated CPU time (s) 0.18
Current children cumulated vsize (KiB) 5552

[startup+0.30272 s]
/proc/loadavg: 1.91 1.95 1.98 4/72 12351
/proc/meminfo: memFree=1288584/2055920 swapFree=4192812/4192956
[pid=12351] ppid=12349 vsize=5680 CPUtime=0.28
/proc/12351/stat : 12351 (pcs.big) R 12349 12351 12002 0 -1 4194304 1122 657 0 0 28 0 0 0 25 0 1 0 58719819 5816320 753 996147200 134512640 135215973 4294956304 18446744073709551615 134585409 0 0 4096 0 0 0 0 17 1 0 0
/proc/12351/statm: 1420 753 416 171 0 345 0
Current children cumulated CPU time (s) 0.28
Current children cumulated vsize (KiB) 5680

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

[startup+0.30272 s]
/proc/loadavg: 1.91 1.95 1.98 4/72 12351
/proc/meminfo: memFree=1288584/2055920 swapFree=4192812/4192956
[pid=12351] ppid=12349 vsize=5680 CPUtime=0.28
/proc/12351/stat : 12351 (pcs.big) R 12349 12351 12002 0 -1 4194304 1122 657 0 0 28 0 0 0 25 0 1 0 58719819 5816320 753 996147200 134512640 135215973 4294956304 18446744073709551615 134585409 0 0 4096 0 0 0 0 17 1 0 0
/proc/12351/statm: 1420 753 416 171 0 345 0
Current children cumulated CPU time (s) 0.28
Current children cumulated vsize (KiB) 5680

Child status: 0
Real time (s): 0.373253
CPU time (s): 0.361944
CPU user time (s): 0.348946
CPU system time (s): 0.012998
CPU usage (%): 96.9702
Max. virtual memory (cumulated for all children) (KiB): 5680

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.348946
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= 1811
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= 20

runsolver used 0.001999 second user time and 0.006998 second system time

The end

Launcher Data

Begin job on node45 at 2009-07-16 05:56:00
IDJOB=2078853
IDBENCH=56819
IDSOLVER=733
FILE ID=node45/2078853-1247716560
PBS_JOBID= 9521445
Free space on /tmp= 66380 MiB

SOLVER NAME= pcs 0.2
BENCH NAME= CPAI08/csp/nengfa/normalized-radi.xml
COMMAND LINE= HOME/pcssolve -s RANDOMSEED BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2078853-1247716560/watcher-2078853-1247716560 -o /tmp/evaluation-result-2078853-1247716560/solver-2078853-1247716560 -C 1800 -W 2000 -M 900  HOME/pcssolve -s 1842614637 HOME/instance-2078853-1247716560.xml

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

MD5SUM BENCH= 721069b46612331b45c8be673b18e6c8
RANDOM SEED=1842614637

node45.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.281
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.281
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:       1289064 kB
Buffers:         81512 kB
Cached:         571492 kB
SwapCached:          0 kB
Active:         121244 kB
Inactive:       554344 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1289064 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1800 kB
Writeback:           0 kB
Mapped:          34108 kB
Slab:            76680 kB
Committed_AS:   510328 kB
PageTables:       1712 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 node45 at 2009-07-16 05:56:01