Trace number 247722

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, and are wall clock time (not CPU 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
CSPtoSAT+minisat 0.3SAT 0.017997 0.018552

General information on the benchmark

Namelangford/
langford-2-4-ext.xml
MD5SUM25c174e83f0c6bcbedb708ae90485196
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.001998
SatisfiableYES
(Un)Satisfiability was proved
Number of variables8
Number of constraints32
Maximum constraint arity2
Maximum domain size8
Number of constraints which are defined in extension32
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.01	c This is CSPtoSAT+minisat version 0.3
0.01	c (c) 2006 roussel@cril.univ-artois.fr
0.01	
0.01	c This solver internally uses a modified version of MiniSat2 version 061112
0.01	c MiniSat -- Copyright (c) 2003-2006, Niklas Een, Niklas Sorensson
0.01	
0.01	c parsing...
0.01	c preparing clauses for relation R0
0.01	c preparing clauses for relation R1
0.01	c preparing clauses for relation R2
0.01	c preparing clauses for relation R3
0.01	c preparing clauses for relation R4
0.01	c instanciating clauses for relation R0 (supports) and variables V5 V1 
0.01	c instanciating clauses for relation R1 (supports) and variables V7 V3 
0.01	c instanciating clauses for relation R2 (supports) and variables V6 V2 
0.01	c instanciating clauses for relation R3 (conflicts) and variables V0 V1 
0.01	c instanciating clauses for relation R3 (conflicts) and variables V0 V2 
0.01	c instanciating clauses for relation R3 (conflicts) and variables V0 V3 
0.01	c instanciating clauses for relation R3 (conflicts) and variables V0 V4 
0.01	c instanciating clauses for relation R3 (conflicts) and variables V0 V5 
0.01	c instanciating clauses for relation R3 (conflicts) and variables V0 V6 
0.01	c instanciating clauses for relation R3 (conflicts) and variables V0 V7 
0.01	c instanciating clauses for relation R3 (conflicts) and variables V1 V2 
0.01	c instanciating clauses for relation R3 (conflicts) and variables V1 V3 
0.01	c instanciating clauses for relation R3 (conflicts) and variables V1 V4 
0.01	c instanciating clauses for relation R3 (conflicts) and variables V1 V5 
0.01	c instanciating clauses for relation R3 (conflicts) and variables V1 V6 
0.01	c instanciating clauses for relation R3 (conflicts) and variables V1 V7 
0.01	c instanciating clauses for relation R3 (conflicts) and variables V2 V3 
0.01	c instanciating clauses for relation R3 (conflicts) and variables V2 V4 
0.01	c instanciating clauses for relation R3 (conflicts) and variables V2 V5 
0.01	c instanciating clauses for relation R3 (conflicts) and variables V2 V6 
0.01	c instanciating clauses for relation R3 (conflicts) and variables V2 V7 
0.01	c instanciating clauses for relation R3 (conflicts) and variables V3 V4 
0.01	c instanciating clauses for relation R3 (conflicts) and variables V3 V5 
0.01	c instanciating clauses for relation R3 (conflicts) and variables V3 V6 
0.01	c instanciating clauses for relation R3 (conflicts) and variables V3 V7 
0.01	c instanciating clauses for relation R3 (conflicts) and variables V4 V5 
0.01	c instanciating clauses for relation R3 (conflicts) and variables V4 V6 
0.01	c instanciating clauses for relation R3 (conflicts) and variables V4 V7 
0.01	c instanciating clauses for relation R3 (conflicts) and variables V5 V6 
0.01	c instanciating clauses for relation R3 (conflicts) and variables V5 V7 
0.01	c instanciating clauses for relation R3 (conflicts) and variables V6 V7 
0.01	c instanciating clauses for relation R4 (supports) and variables V4 V0 
0.01	c ...done
0.01	c #SATvar=206 #SATclauses=675 #CSPpredicates=0
0.01	Verified 675 original clauses.
0.01	c SAT problem is solved
0.01	restarts              : 1
0.01	conflicts             : 4              (333 /sec)
0.01	decisions             : 7              (0.00 % random) (583 /sec)
0.01	propagations          : 619            (51592 /sec)
0.01	conflict literals     : 7              (0.00 % deleted)
0.01	Memory used           : 6.64 MB
0.01	CPU time              : 0.011998 s
0.01	c all predicates checked
0.01	
0.01	s SATISFIABLE
0.01	v 1 4 2 0 3 7 6 5 
0.01

Verifier Data (download as text)

OK

Watcher Data (download as text)

runsolver version 3.1.3 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node4/watcher-247722-1168093727 -o ROOT/results/node4/solver-247722-1168093727 -C 1800 -M 900 /tmp/evaluation/247722-1168093727/CSPtoSAT+minisat /tmp/evaluation/247722-1168093727/unknown.xml 

Enforcing CPUTime limit (soft limit, will send SIGTERM then SIGKILL): 1800 seconds
Enforcing CPUTime limit (hard limit, will send SIGXCPU): 1830 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

/proc/loadavg: 0.76 1.07 1.59 5/86 16779
/proc/meminfo: memFree=1904440/2055920 swapFree=4182144/4192956
[pid=16778] ppid=16776 vsize=6696 CPUtime=0
/proc/16778/stat : 16778 (CSPtoSAT+minisa) R 16776 16778 16624 0 -1 4194304 403 0 0 0 0 0 0 0 18 0 1 0 157768766 6856704 383 18446744073709551615 134512640 134728504 4294956704 18446744073709551615 10553201 0 0 4096 0 0 0 0 17 1 0 0
/proc/16778/statm: 1674 383 358 52 0 30 0

Child status: 0
Real time (s): 0.018552
CPU time (s): 0.017997
CPU user time (s): 0.011998
CPU system time (s): 0.005999
CPU usage (%): 97.0085
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.011998
system time used= 0.005999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 855
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= 14
involuntary context switches= 61

runsolver used 0.003999 s user time and 0.004999 s system time

The end

Launcher Data (download as text)

Begin job on node4 on Sat Jan  6 14:28:50 UTC 2007


IDJOB= 247722
IDBENCH= 11651
FILE ID= node4/247722-1168093727

PBS_JOBID= 3476434

Free space on /tmp= 66307 MiB

BENCH NAME= HOME/pub/bench/CPAI06/langford/langford-2-4-ext.xml
COMMAND LINE= /tmp/evaluation/247722-1168093727/CSPtoSAT+minisat /tmp/evaluation/247722-1168093727/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node4/watcher-247722-1168093727 -o ROOT/results/node4/solver-247722-1168093727 -C 1800 -M 900  /tmp/evaluation/247722-1168093727/CSPtoSAT+minisat /tmp/evaluation/247722-1168093727/unknown.xml

META MD5SUM SOLVER= 0ab327eaa5be249b47b2f4b19927f0b0
MD5SUM BENCH=  25c174e83f0c6bcbedb708ae90485196

RANDOM SEED= 48849472

TIME LIMIT= 1800 seconds

MEMORY LIMIT= 900 MiB


/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.223
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.223
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:       1904984 kB
Buffers:          8032 kB
Cached:          33988 kB
SwapCached:       2520 kB
Active:          82204 kB
Inactive:        15748 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1904984 kB
SwapTotal:     4192956 kB
SwapFree:      4182144 kB
Dirty:            1568 kB
Writeback:           0 kB
Mapped:          67824 kB
Slab:            37612 kB
Committed_AS:  3861144 kB
PageTables:       2384 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= 66307 MiB



End job on node4 on Sat Jan  6 14:28:55 UTC 2007