Trace number 2089523

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.041993 0.0493741

DiagnosticValue
ASSIGNMENTS8

General information on the benchmark

Namecsp/composed-25-1-80/
normalized-composed-25-1-80-5_ext.xml
MD5SUM230b5499fe73c9f2e356f17cbcfd9ccc
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 variables33
Number of constraints302
Maximum constraint arity2
Maximum domain size10
Number of constraints which are defined in extension302
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 1044858518
0.00/0.02	c Constructing HOME/instance-2089523-1247730474.xml  with 2032 constraints
0.02/0.04	c Solving 8 backtracks
0.02/0.04	s UNSATISFIABLE
0.02/0.04	d ASSIGNMENTS 8

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-2089523-1247730474/watcher-2089523-1247730474 -o /tmp/evaluation-result-2089523-1247730474/solver-2089523-1247730474 -C 1800 -W 2000 -M 900 HOME/pcssolve -s 1044858518 HOME/instance-2089523-1247730474.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.02 2.00 4/81 13954
/proc/meminfo: memFree=1142928/2055920 swapFree=4192812/4192956
[pid=13954] ppid=13952 vsize=5356 CPUtime=0
/proc/13954/stat : 13954 (pcssolve) R 13952 13954 12500 0 -1 4194304 273 0 0 0 0 0 0 0 20 0 1 0 60111447 5484544 241 996147200 4194304 4889804 548682068800 18446744073709551615 266890439327 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/13954/statm: 1339 241 200 169 0 50 0
[pid=13955] ppid=13954 vsize=5356 CPUtime=0
/proc/13955/stat : 13955 (pcssolve) R 13954 13954 12500 0 -1 4194368 0 0 0 0 0 0 0 0 20 0 1 0 60111448 5484544 241 996147200 4194304 4889804 548682068800 18446744073709551615 266890439327 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/13955/statm: 1339 241 200 169 0 50 0

[startup+0.0395251 s]
/proc/loadavg: 2.07 2.02 2.00 4/81 13954
/proc/meminfo: memFree=1142928/2055920 swapFree=4192812/4192956
[pid=13954] ppid=13952 vsize=4640 CPUtime=0.02
/proc/13954/stat : 13954 (pcs.small) R 13952 13954 12500 0 -1 4194304 888 822 0 0 2 0 0 0 25 0 1 0 60111447 4751360 497 996147200 134512640 135095119 4294956304 18446744073709551615 134706684 0 0 4096 0 0 0 0 17 1 0 0
/proc/13954/statm: 1160 497 367 142 0 114 0
Current children cumulated CPU time (s) 0.02
Current children cumulated vsize (KiB) 4640

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

[startup+0.0395251 s]
/proc/loadavg: 2.07 2.02 2.00 4/81 13954
/proc/meminfo: memFree=1142928/2055920 swapFree=4192812/4192956
[pid=13954] ppid=13952 vsize=4640 CPUtime=0.02
/proc/13954/stat : 13954 (pcs.small) R 13952 13954 12500 0 -1 4194304 888 822 0 0 2 0 0 0 25 0 1 0 60111447 4751360 497 996147200 134512640 135095119 4294956304 18446744073709551615 134706684 0 0 4096 0 0 0 0 17 1 0 0
/proc/13954/statm: 1160 497 367 142 0 114 0
Current children cumulated CPU time (s) 0.02
Current children cumulated vsize (KiB) 4640

Child status: 0
Real time (s): 0.0493741
CPU time (s): 0.041993
CPU user time (s): 0.030995
CPU system time (s): 0.010998
CPU usage (%): 85.0506
Max. virtual memory (cumulated for all children) (KiB): 4640

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

runsolver used 0.003999 second user time and 0.004999 second system time

The end

Launcher Data 

Begin job on node38 at 2009-07-16 09:47:54
IDJOB=2089523
IDBENCH=59571
IDSOLVER=733
FILE ID=node38/2089523-1247730474
PBS_JOBID= 9521530
Free space on /tmp= 66224 MiB

SOLVER NAME= pcs 0.2
BENCH NAME= CPAI08/csp/composed-25-1-80/normalized-composed-25-1-80-5_ext.xml
COMMAND LINE= HOME/pcssolve -s RANDOMSEED BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2089523-1247730474/watcher-2089523-1247730474 -o /tmp/evaluation-result-2089523-1247730474/solver-2089523-1247730474 -C 1800 -W 2000 -M 900  HOME/pcssolve -s 1044858518 HOME/instance-2089523-1247730474.xml

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

MD5SUM BENCH= 230b5499fe73c9f2e356f17cbcfd9ccc
RANDOM SEED=1044858518

node38.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.229
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.229
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:       1143408 kB
Buffers:         95344 kB
Cached:         655512 kB
SwapCached:          0 kB
Active:         283956 kB
Inactive:       531020 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1143408 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            2160 kB
Writeback:           0 kB
Mapped:          84500 kB
Slab:            82544 kB
Committed_AS:   604784 kB
PageTables:       2020 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= 66224 MiB
End job on node38 at 2009-07-16 09:47:54