Trace number 2058602

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.2UNSAT 0.412936 0.419914

DiagnosticValue
ASSIGNMENTS5107

General information on the benchmark

Namecsp/BH-4-4/
normalized-BlackHole-4-4-e-0_ext.xml
MD5SUM78fd2e0579ed1e222d3ce17f5c52a213
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.019996
Satisfiable
(Un)Satisfiability was proved
Number of variables64
Number of constraints431
Maximum constraint arity2
Maximum domain size16
Number of constraints which are defined in extension431
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data

0.00/0.01	c small-domain mode
0.00/0.02	c Seed is 1447033153
0.00/0.02	c Constructing HOME/instance-2058602-1247694266.xml  with 2495 constraints
0.00/0.03	c Solving 5107 backtracks 12 restarts
0.37/0.41	s UNSATISFIABLE
0.37/0.41	d ASSIGNMENTS 5107

Verifier Data

No possible verification on an UNSAT instance

Watcher Data

runsolver version 3.2.9 (svn:492) (c) roussel@cril.univ-artois.fr

command line: BIN/runsolver --timestamp -w /tmp/evaluation-result-2058602-1247694266/watcher-2058602-1247694266 -o /tmp/evaluation-result-2058602-1247694266/solver-2058602-1247694266 -C 1800 -W 2000 -M 900 HOME/pcssolve -s 1447033153 HOME/instance-2058602-1247694266.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: 0.96 0.26 0.08 4/72 10657
/proc/meminfo: memFree=1184616/2055920 swapFree=4192812/4192956
[pid=10657] ppid=10655 vsize=5356 CPUtime=0
/proc/10657/stat : 10657 (pcssolve) R 10655 10657 10283 0 -1 4194304 273 0 0 0 0 0 0 0 23 0 1 0 56490762 5484544 241 996147200 4194304 4889804 548682068800 18446744073709551615 255539604127 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/10657/statm: 1339 241 200 169 0 50 0
[pid=10658] ppid=10657 vsize=5356 CPUtime=0
/proc/10658/stat : 10658 (pcssolve) R 10657 10657 10283 0 -1 4194368 0 0 0 0 0 0 0 0 23 0 1 0 56490762 5484544 241 996147200 4194304 4889804 548682068800 18446744073709551615 255539604127 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/10658/statm: 1339 241 200 169 0 50 0

[startup+0.100874 s]
/proc/loadavg: 0.96 0.26 0.08 4/72 10657
/proc/meminfo: memFree=1184616/2055920 swapFree=4192812/4192956
[pid=10657] ppid=10655 vsize=4928 CPUtime=0.07
/proc/10657/stat : 10657 (pcs.small) R 10655 10657 10283 0 -1 4194304 941 823 0 0 7 0 0 0 25 0 1 0 56490762 5046272 550 996147200 134512640 135095119 4294956304 18446744073709551615 134636926 0 0 4096 0 0 0 0 17 1 0 0
/proc/10657/statm: 1232 550 378 142 0 186 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 4928

[startup+0.201883 s]
/proc/loadavg: 0.96 0.26 0.08 4/72 10657
/proc/meminfo: memFree=1184616/2055920 swapFree=4192812/4192956
[pid=10657] ppid=10655 vsize=5320 CPUtime=0.17
/proc/10657/stat : 10657 (pcs.small) R 10655 10657 10283 0 -1 4194304 1055 823 0 0 17 0 0 0 25 0 1 0 56490762 5447680 631 996147200 134512640 135095119 4294956304 18446744073709551615 134589657 0 0 4096 0 0 0 0 17 1 0 0
/proc/10657/statm: 1330 631 378 142 0 284 0
Current children cumulated CPU time (s) 0.17
Current children cumulated vsize (KiB) 5320

[startup+0.301894 s]
/proc/loadavg: 0.96 0.26 0.08 4/72 10657
/proc/meminfo: memFree=1184616/2055920 swapFree=4192812/4192956
[pid=10657] ppid=10655 vsize=5580 CPUtime=0.27
/proc/10657/stat : 10657 (pcs.small) R 10655 10657 10283 0 -1 4194304 1138 823 0 0 27 0 0 0 25 0 1 0 56490762 5713920 681 996147200 134512640 135095119 4294956304 18446744073709551615 134643013 0 0 4096 0 0 0 0 17 1 0 0
/proc/10657/statm: 1395 681 378 142 0 349 0
Current children cumulated CPU time (s) 0.27
Current children cumulated vsize (KiB) 5580

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

[startup+0.401902 s]
/proc/loadavg: 0.96 0.26 0.08 4/72 10657
/proc/meminfo: memFree=1184616/2055920 swapFree=4192812/4192956
[pid=10657] ppid=10655 vsize=5712 CPUtime=0.37
/proc/10657/stat : 10657 (pcs.small) R 10655 10657 10283 0 -1 4194304 1182 823 0 0 37 0 0 0 25 0 1 0 56490762 5849088 725 996147200 134512640 135095119 4294956304 18446744073709551615 134637494 0 0 4096 0 0 0 0 17 1 0 0
/proc/10657/statm: 1428 725 378 142 0 382 0
Current children cumulated CPU time (s) 0.37
Current children cumulated vsize (KiB) 5712

Child status: 0
Real time (s): 0.419914
CPU time (s): 0.412936
CPU user time (s): 0.397939
CPU system time (s): 0.014997
CPU usage (%): 98.3382
Max. virtual memory (cumulated for all children) (KiB): 5712

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.397939
system time used= 0.014997
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 2014
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= 22
involuntary context switches= 20

runsolver used 0.004999 second user time and 0.005999 second system time

The end

Launcher Data

Begin job on node48 at 2009-07-15 23:44:26
IDJOB=2058602
IDBENCH=53506
IDSOLVER=733
FILE ID=node48/2058602-1247694266
PBS_JOBID= 9521217
Free space on /tmp= 66372 MiB

SOLVER NAME= pcs 0.2
BENCH NAME= CPAI08/csp/BH-4-4/normalized-BlackHole-4-4-e-0_ext.xml
COMMAND LINE= HOME/pcssolve -s RANDOMSEED BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2058602-1247694266/watcher-2058602-1247694266 -o /tmp/evaluation-result-2058602-1247694266/solver-2058602-1247694266 -C 1800 -W 2000 -M 900  HOME/pcssolve -s 1447033153 HOME/instance-2058602-1247694266.xml

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

MD5SUM BENCH= 78fd2e0579ed1e222d3ce17f5c52a213
RANDOM SEED=1447033153

node48.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.237
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.237
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:       1185096 kB
Buffers:         77552 kB
Cached:         668272 kB
SwapCached:          0 kB
Active:         208008 kB
Inactive:       579872 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1185096 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            3852 kB
Writeback:           0 kB
Mapped:          53552 kB
Slab:            68372 kB
Committed_AS:   588892 kB
PageTables:       1760 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= 66372 MiB
End job on node48 at 2009-07-15 23:44:27