Trace number 241912

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.3UNSAT 0.025995 0.029879

General information on the benchmark

Namedimacs/pret/
pret-60-60_ext.xml
MD5SUMb2b762c34be059b37506a29c09fcdb74
Bench CategoryN-ARY-EXT (n-ary constraints in extension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.025995
SatisfiableNO
(Un)Satisfiability was proved
Number of variables60
Number of constraints40
Maximum constraint arity3
Maximum domain size2
Number of constraints which are defined in extension40
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 instanciating clauses for relation R0 (supports) and variables V35 V34 V33 
0.01	c instanciating clauses for relation R0 (supports) and variables V38 V37 V36 
0.01	c instanciating clauses for relation R0 (supports) and variables V39 V36 V15 
0.01	c instanciating clauses for relation R0 (supports) and variables V41 V40 V14 
0.01	c instanciating clauses for relation R0 (supports) and variables V42 V40 V13 
0.01	c instanciating clauses for relation R0 (supports) and variables V43 V17 V9 
0.01	c instanciating clauses for relation R0 (supports) and variables V43 V16 V12 
0.01	c instanciating clauses for relation R0 (supports) and variables V45 V44 V5 
0.01	c instanciating clauses for relation R0 (supports) and variables V44 V21 V4 
0.01	c instanciating clauses for relation R0 (supports) and variables V47 V46 V20 
0.01	c instanciating clauses for relation R0 (supports) and variables V46 V45 V19 
0.01	c instanciating clauses for relation R0 (supports) and variables V48 V23 V0 
0.01	c instanciating clauses for relation R0 (supports) and variables V48 V22 V18 
0.01	c instanciating clauses for relation R0 (supports) and variables V50 V49 V8 
0.01	c instanciating clauses for relation R0 (supports) and variables V49 V27 V7 
0.01	c instanciating clauses for relation R0 (supports) and variables V51 V41 V26 
0.01	c instanciating clauses for relation R0 (supports) and variables V51 V50 V25 
0.01	c instanciating clauses for relation R0 (supports) and variables V52 V29 V3 
0.01	c instanciating clauses for relation R0 (supports) and variables V52 V28 V24 
0.01	c instanciating clauses for relation R0 (supports) and variables V54 V53 V11 
0.01	c instanciating clauses for relation R0 (supports) and variables V53 V33 V10 
0.01	c instanciating clauses for relation R0 (supports) and variables V55 V47 V32 
0.01	c instanciating clauses for relation R0 (supports) and variables V55 V54 V31 
0.01	c instanciating clauses for relation R0 (supports) and variables V56 V35 V6 
0.01	c instanciating clauses for relation R0 (supports) and variables V56 V34 V30 
0.01	c instanciating clauses for relation R0 (supports) and variables V58 V57 V2 
0.01	c instanciating clauses for relation R0 (supports) and variables V57 V39 V1 
0.01	c instanciating clauses for relation R0 (supports) and variables V59 V42 V38 
0.01	c instanciating clauses for relation R0 (supports) and variables V59 V58 V37 
0.01	c instanciating clauses for relation R1 (supports) and variables V2 V1 V0 
0.01	c instanciating clauses for relation R1 (supports) and variables V5 V4 V3 
0.01	c instanciating clauses for relation R1 (supports) and variables V8 V7 V6 
0.01	c instanciating clauses for relation R1 (supports) and variables V11 V10 V9 
0.01	c instanciating clauses for relation R1 (supports) and variables V14 V13 V12 
0.01	c instanciating clauses for relation R1 (supports) and variables V17 V16 V15 
0.01	c instanciating clauses for relation R1 (supports) and variables V20 V19 V18 
0.01	c instanciating clauses for relation R1 (supports) and variables V23 V22 V21 
0.01	c instanciating clauses for relation R1 (supports) and variables V26 V25 V24 
0.01	c instanciating clauses for relation R1 (supports) and variables V29 V28 V27 
0.01	c instanciating clauses for relation R1 (supports) and variables V32 V31 V30 
0.01	c ...done
0.01	c #SATvar=282 #SATclauses=1360 #CSPpredicates=0
0.02	c SAT problem is solved
0.02	restarts              : 3
0.02	conflicts             : 358            (17051 /sec)
0.02	decisions             : 706            (1.56 % random) (33625 /sec)
0.02	propagations          : 17547          (835731 /sec)
0.02	conflict literals     : 3300           (5.31 % deleted)
0.02	Memory used           : 6.76 MB
0.02	CPU time              : 0.020996 s
0.02	
0.02	s UNSATISFIABLE

Verifier Data (download as text)

No possible verification on an UNSAT instance

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node23/watcher-241912-1168093321 -o ROOT/results/node23/solver-241912-1168093321 -C 1800 -M 900 /tmp/evaluation/241912-1168093321/CSPtoSAT+minisat /tmp/evaluation/241912-1168093321/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.01 0.38 0.80 4/81 25476
/proc/meminfo: memFree=1448848/2055920 swapFree=4192812/4192956
[pid=25475] ppid=25473 vsize=6696 CPUtime=0
/proc/25475/stat : 25475 (CSPtoSAT+minisa) R 25473 25475 25133 0 -1 4194304 424 0 0 0 0 0 0 0 18 0 1 0 157726906 6856704 403 18446744073709551615 134512640 134728504 4294956704 18446744073709551615 2464632 0 0 4096 0 0 0 0 17 1 0 0
/proc/25475/statm: 1674 403 365 52 0 30 0

Child status: 0
Real time (s): 0.029879
CPU time (s): 0.025995
CPU user time (s): 0.020996
CPU system time (s): 0.004999
CPU usage (%): 87.0009
Max. virtual memory (cumulated for all children) (KiB): 0

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

runsolver used 0.001999 s user time and 0.006998 s system time

The end

Launcher Data (download as text)

Begin job on node23 on Sat Jan  6 14:22:05 UTC 2007


IDJOB= 241912
IDBENCH= 7353
FILE ID= node23/241912-1168093321

PBS_JOBID= 3476666

Free space on /tmp= 66549 MiB

BENCH NAME= HOME/pub/bench/CPAI06/dimacs/pret/pret-60-60_ext.xml
COMMAND LINE= /tmp/evaluation/241912-1168093321/CSPtoSAT+minisat /tmp/evaluation/241912-1168093321/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node23/watcher-241912-1168093321 -o ROOT/results/node23/solver-241912-1168093321 -C 1800 -M 900  /tmp/evaluation/241912-1168093321/CSPtoSAT+minisat /tmp/evaluation/241912-1168093321/unknown.xml

META MD5SUM SOLVER= 0ab327eaa5be249b47b2f4b19927f0b0
MD5SUM BENCH=  b2b762c34be059b37506a29c09fcdb74

RANDOM SEED= 319620136

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.265
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.265
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:       1449264 kB
Buffers:         47240 kB
Cached:         422368 kB
SwapCached:          0 kB
Active:         169132 kB
Inactive:       361016 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1449264 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            3220 kB
Writeback:           0 kB
Mapped:          79484 kB
Slab:            61568 kB
Committed_AS:  3018368 kB
PageTables:       2124 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= 66549 MiB



End job on node23 on Sat Jan  6 14:22:05 UTC 2007