Trace number 2059273

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.205968 0.213957

DiagnosticValue
ASSIGNMENTS2396

General information on the benchmark

Namecsp/coloring/
normalized-myciel-5g-4-ext.xml
MD5SUM174aee4ff53d2fa062227496e7b76689
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.042993
Satisfiable
(Un)Satisfiability was proved
Number of variables47
Number of constraints236
Maximum constraint arity2
Maximum domain size4
Number of constraints which are defined in extension236
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.18/0.21	c Seed is 2014198501
0.18/0.21	c Constructing HOME/instance-2059273-1247695112.xml  with 944 constraints
0.18/0.21	c Solving 2396 backtracks 10 restarts
0.18/0.21	s UNSATISFIABLE
0.18/0.21	d ASSIGNMENTS 2396

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-2059273-1247695112/watcher-2059273-1247695112 -o /tmp/evaluation-result-2059273-1247695112/solver-2059273-1247695112 -C 1800 -W 2000 -M 900 HOME/pcssolve -s 2014198501 HOME/instance-2059273-1247695112.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.04 1.90 1.21 4/73 13056
/proc/meminfo: memFree=815712/2055920 swapFree=4192812/4192956
[pid=13056] ppid=13054 vsize=5356 CPUtime=0
/proc/13056/stat : 13056 (pcssolve) R 13054 13056 12845 0 -1 4194304 290 0 0 0 0 0 0 0 21 0 1 0 56576983 5484544 241 996147200 4194304 4889804 548682068800 18446744073709551615 228774701727 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/13056/statm: 1339 241 200 169 0 50 0
[pid=13057] ppid=13056 vsize=0 CPUtime=0
/proc/13057/stat : 13057 (fgrep) Z 13056 13056 12845 0 -1 4194316 151 0 0 0 0 0 0 0 22 0 1 0 56576983 0 0 996147200 0 0 0 0 0 0 0 4096 0 18446744071563351923 0 0 17 1 0 0
/proc/13057/statm: 0 0 0 0 0 0 0

[startup+0.202506 s]
/proc/loadavg: 2.04 1.90 1.21 4/73 13056
/proc/meminfo: memFree=815712/2055920 swapFree=4192812/4192956
[pid=13056] ppid=13054 vsize=5060 CPUtime=0.18
/proc/13056/stat : 13056 (pcs.small) R 13054 13056 12845 0 -1 4194304 985 810 0 0 18 0 0 0 18 0 1 0 56576983 5181440 594 996147200 134512640 135095119 4294956304 18446744073709551615 134838118 0 0 4096 0 0 0 0 17 1 0 0
/proc/13056/statm: 1265 594 378 142 0 219 0
Current children cumulated CPU time (s) 0.18
Current children cumulated vsize (KiB) 5060

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

[startup+0.202506 s]
/proc/loadavg: 2.04 1.90 1.21 4/73 13056
/proc/meminfo: memFree=815712/2055920 swapFree=4192812/4192956
[pid=13056] ppid=13054 vsize=5060 CPUtime=0.18
/proc/13056/stat : 13056 (pcs.small) R 13054 13056 12845 0 -1 4194304 985 810 0 0 18 0 0 0 18 0 1 0 56576983 5181440 594 996147200 134512640 135095119 4294956304 18446744073709551615 134838118 0 0 4096 0 0 0 0 17 1 0 0
/proc/13056/statm: 1265 594 378 142 0 219 0
Current children cumulated CPU time (s) 0.18
Current children cumulated vsize (KiB) 5060

Child status: 0
Real time (s): 0.213957
CPU time (s): 0.205968
CPU user time (s): 0.19597
CPU system time (s): 0.009998
CPU usage (%): 96.2661
Max. virtual memory (cumulated for all children) (KiB): 5060

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.19597
system time used= 0.009998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1835
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= 21
involuntary context switches= 13

runsolver used 0.001999 second user time and 0.008998 second system time

The end

Launcher Data 

Begin job on node74 at 2009-07-15 23:58:32
IDJOB=2059273
IDBENCH=53567
IDSOLVER=733
FILE ID=node74/2059273-1247695112
PBS_JOBID= 9521169
Free space on /tmp= 103032 MiB

SOLVER NAME= pcs 0.2
BENCH NAME= CPAI08/csp/coloring/normalized-myciel-5g-4-ext.xml
COMMAND LINE= HOME/pcssolve -s RANDOMSEED BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2059273-1247695112/watcher-2059273-1247695112 -o /tmp/evaluation-result-2059273-1247695112/solver-2059273-1247695112 -C 1800 -W 2000 -M 900  HOME/pcssolve -s 2014198501 HOME/instance-2059273-1247695112.xml

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

MD5SUM BENCH= 174aee4ff53d2fa062227496e7b76689
RANDOM SEED=2014198501

node74.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.234
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.234
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:        816192 kB
Buffers:         59212 kB
Cached:        1007300 kB
SwapCached:          0 kB
Active:         172004 kB
Inactive:       992528 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        816192 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1768 kB
Writeback:           0 kB
Mapped:         109448 kB
Slab:            60296 kB
Committed_AS:   590676 kB
PageTables:       2000 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264960 kB
VmallocChunk: 536605679 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 103032 MiB
End job on node74 at 2009-07-15 23:58:32