Trace number 2082373

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.028995 0.034273

DiagnosticValue
ASSIGNMENTS21

General information on the benchmark

Namecsp/langford2/
normalized-langford-2-5.xml
MD5SUM42a251b4e5e78e8baab98daca83f50dd
Bench Category2-ARY-INT (binary constraints in intension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.006998
Satisfiable
(Un)Satisfiability was proved
Number of variables10
Number of constraints50
Maximum constraint arity2
Maximum domain size10
Number of constraints which are defined in extension0
Number of constraints which are defined in intension50
Global constraints used (with number of constraints)

Solver Data 

0.00/0.01	c has operations which may create big domains
0.00/0.01	c big-domain mode
0.00/0.02	c Seed is 1039790156
0.00/0.02	c Constructing HOME/instance-2082373-1247720995.xml 
0.00/0.02	c deduced all_different(V1,V2,V3,V4,V5,V6,V7,V8,V9,V0)
0.00/0.02	c  with 51 constraints
0.00/0.02	c Solving 21 backtracks 1 restarts
0.00/0.03	s UNSATISFIABLE
0.00/0.03	d ASSIGNMENTS 21

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-2082373-1247720995/watcher-2082373-1247720995 -o /tmp/evaluation-result-2082373-1247720995/solver-2082373-1247720995 -C 1800 -W 2000 -M 900 HOME/pcssolve -s 1039790156 HOME/instance-2082373-1247720995.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.00 2.00 2.00 4/81 13481
/proc/meminfo: memFree=1496168/2055920 swapFree=4192812/4192956
[pid=13481] ppid=13479 vsize=5356 CPUtime=0
/proc/13481/stat : 13481 (pcssolve) R 13479 13481 12010 0 -1 4194304 290 0 0 0 0 0 0 0 21 0 1 0 59166545 5484544 241 996147200 4194304 4889804 548682068800 18446744073709551615 262910044831 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/13481/statm: 1339 241 200 169 0 50 0
[pid=13482] ppid=13481 vsize=3676 CPUtime=0
/proc/13482/stat : 13482 (fgrep) R 13481 13481 12010 0 -1 4194304 125 0 0 0 0 0 0 0 22 0 1 0 59166546 3764224 92 996147200 4194304 4274172 548682068976 18446744073709551615 262909918176 0 0 4096 0 0 0 0 17 1 0 0
/proc/13482/statm: 919 92 74 19 0 43 0
[pid=13483] ppid=13481 vsize=5356 CPUtime=0
/proc/13483/stat : 13483 (pcssolve) R 13481 13481 12010 0 -1 4194368 0 0 0 0 0 0 0 0 21 0 1 0 59166546 5484544 241 996147200 4194304 4889804 548682068800 18446744073709551615 262910044831 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/13483/statm: 1339 241 200 169 0 50 0

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

Child status: 0
Real time (s): 0.034273
CPU time (s): 0.028995
CPU user time (s): 0.016997
CPU system time (s): 0.011998
CPU usage (%): 84.6
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.016997
system time used= 0.011998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1660
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 node11 at 2009-07-16 07:09:55
IDJOB=2082373
IDBENCH=57579
IDSOLVER=733
FILE ID=node11/2082373-1247720995
PBS_JOBID= 9521466
Free space on /tmp= 66420 MiB

SOLVER NAME= pcs 0.2
BENCH NAME= CPAI08/csp/langford2/normalized-langford-2-5.xml
COMMAND LINE= HOME/pcssolve -s RANDOMSEED BENCHNAME
RUNSOLVER COMMAND LINE= BIN/runsolver --timestamp -w /tmp/evaluation-result-2082373-1247720995/watcher-2082373-1247720995 -o /tmp/evaluation-result-2082373-1247720995/solver-2082373-1247720995 -C 1800 -W 2000 -M 900  HOME/pcssolve -s 1039790156 HOME/instance-2082373-1247720995.xml

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

MD5SUM BENCH= 42a251b4e5e78e8baab98daca83f50dd
RANDOM SEED=1039790156

node11.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.274
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.274
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:       1496648 kB
Buffers:         69240 kB
Cached:         306460 kB
SwapCached:          0 kB
Active:         183976 kB
Inactive:       305632 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1496648 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            1972 kB
Writeback:           0 kB
Mapped:         134340 kB
Slab:            54540 kB
Committed_AS:   653016 kB
PageTables:       2132 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= 66416 MiB
End job on node11 at 2009-07-16 07:09:55