Trace number 242216

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.031994 0.0330471

General information on the benchmark

Namedimacs/dubois/
dubois-25_ext.xml
MD5SUMc8d9181936a64a100d65217b65ed3de1
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.031994
SatisfiableNO
(Un)Satisfiability was proved
Number of variables75
Number of constraints50
Maximum constraint arity3
Maximum domain size2
Number of constraints which are defined in extension50
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 V48 V49 V0 
0.01	c instanciating clauses for relation R0 (supports) and variables V0 V50 V1 
0.01	c instanciating clauses for relation R0 (supports) and variables V1 V51 V2 
0.01	c instanciating clauses for relation R0 (supports) and variables V2 V52 V3 
0.01	c instanciating clauses for relation R0 (supports) and variables V3 V53 V4 
0.01	c instanciating clauses for relation R0 (supports) and variables V4 V54 V5 
0.01	c instanciating clauses for relation R0 (supports) and variables V5 V55 V6 
0.01	c instanciating clauses for relation R0 (supports) and variables V6 V56 V7 
0.01	c instanciating clauses for relation R0 (supports) and variables V7 V57 V8 
0.01	c instanciating clauses for relation R0 (supports) and variables V8 V58 V9 
0.01	c instanciating clauses for relation R0 (supports) and variables V9 V59 V10 
0.01	c instanciating clauses for relation R0 (supports) and variables V10 V60 V11 
0.01	c instanciating clauses for relation R0 (supports) and variables V11 V61 V12 
0.01	c instanciating clauses for relation R0 (supports) and variables V12 V62 V13 
0.01	c instanciating clauses for relation R0 (supports) and variables V13 V63 V14 
0.01	c instanciating clauses for relation R0 (supports) and variables V14 V64 V15 
0.01	c instanciating clauses for relation R0 (supports) and variables V15 V65 V16 
0.01	c instanciating clauses for relation R0 (supports) and variables V16 V66 V17 
0.01	c instanciating clauses for relation R0 (supports) and variables V17 V67 V18 
0.01	c instanciating clauses for relation R0 (supports) and variables V18 V68 V19 
0.01	c instanciating clauses for relation R0 (supports) and variables V19 V69 V20 
0.01	c instanciating clauses for relation R0 (supports) and variables V20 V70 V21 
0.01	c instanciating clauses for relation R0 (supports) and variables V21 V71 V22 
0.01	c instanciating clauses for relation R0 (supports) and variables V22 V72 V23 
0.01	c instanciating clauses for relation R0 (supports) and variables V23 V73 V74 
0.01	c instanciating clauses for relation R0 (supports) and variables V24 V73 V74 
0.01	c instanciating clauses for relation R0 (supports) and variables V25 V72 V24 
0.01	c instanciating clauses for relation R0 (supports) and variables V26 V71 V25 
0.01	c instanciating clauses for relation R0 (supports) and variables V27 V70 V26 
0.01	c instanciating clauses for relation R0 (supports) and variables V28 V69 V27 
0.01	c instanciating clauses for relation R0 (supports) and variables V29 V68 V28 
0.01	c instanciating clauses for relation R0 (supports) and variables V30 V67 V29 
0.01	c instanciating clauses for relation R0 (supports) and variables V31 V66 V30 
0.01	c instanciating clauses for relation R0 (supports) and variables V32 V65 V31 
0.01	c instanciating clauses for relation R0 (supports) and variables V33 V64 V32 
0.01	c instanciating clauses for relation R0 (supports) and variables V34 V63 V33 
0.01	c instanciating clauses for relation R0 (supports) and variables V35 V62 V34 
0.01	c instanciating clauses for relation R0 (supports) and variables V36 V61 V35 
0.01	c instanciating clauses for relation R0 (supports) and variables V37 V60 V36 
0.01	c instanciating clauses for relation R0 (supports) and variables V38 V59 V37 
0.01	c instanciating clauses for relation R0 (supports) and variables V39 V58 V38 
0.01	c instanciating clauses for relation R0 (supports) and variables V40 V57 V39 
0.01	c instanciating clauses for relation R0 (supports) and variables V41 V56 V40 
0.01	c instanciating clauses for relation R0 (supports) and variables V42 V55 V41 
0.01	c instanciating clauses for relation R0 (supports) and variables V43 V54 V42 
0.01	c instanciating clauses for relation R0 (supports) and variables V44 V53 V43 
0.01	c instanciating clauses for relation R0 (supports) and variables V45 V52 V44 
0.01	c instanciating clauses for relation R0 (supports) and variables V46 V51 V45 
0.01	c instanciating clauses for relation R0 (supports) and variables V47 V50 V46 
0.01	c instanciating clauses for relation R1 (supports) and variables V48 V49 V47 
0.01	c ...done
0.01	c #SATvar=352 #SATclauses=1700 #CSPpredicates=0
0.03	c SAT problem is solved
0.03	restarts              : 3
0.03	conflicts             : 463            (19295 /sec)
0.03	decisions             : 733            (1.64 % random) (30547 /sec)
0.03	propagations          : 24859          (1035964 /sec)
0.03	conflict literals     : 5784           (6.84 % deleted)
0.03	Memory used           : 6.77 MB
0.03	CPU time              : 0.023996 s
0.03	
0.03	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/node3/watcher-242216-1168701566 -o ROOT/results/node3/solver-242216-1168701566 -C 1800 -M 900 /tmp/evaluation/242216-1168701566/CSPtoSAT+minisat /tmp/evaluation/242216-1168701566/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: 1.00 1.72 0.84 4/82 16921
/proc/meminfo: memFree=1924600/2055920 swapFree=4191880/4192956
[pid=16920] ppid=16917 vsize=6696 CPUtime=0
/proc/16920/stat : 16920 (CSPtoSAT+minisa) R 16917 16920 16853 0 -1 4194304 414 0 0 0 0 0 0 0 18 0 1 0 218552440 6856704 393 18446744073709551615 134512640 134728504 4294956704 18446744073709551615 10894625 0 0 4096 0 0 0 0 17 1 0 0
/proc/16920/statm: 1674 402 364 52 0 30 0

Child status: 0
Real time (s): 0.0330471
CPU time (s): 0.031994
CPU user time (s): 0.023996
CPU system time (s): 0.007998
CPU usage (%): 96.8133
Max. virtual memory (cumulated for all children) (KiB): 0

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

runsolver used 0.002999 s user time and 0.003999 s system time

The end

Launcher Data (download as text)

Begin job on node3 on Sat Jan 13 15:19:27 UTC 2007


IDJOB= 242216
IDBENCH= 7375
IDSOLVER= 87
FILE ID= node3/242216-1168701566

PBS_JOBID= 3547003

Free space on /tmp= 66563 MiB

SOLVER NAME= CSPtoSAT+minisat 0.3
BENCH NAME= HOME/pub/bench/CPAI06/dimacs/dubois/dubois-25_ext.xml
COMMAND LINE= /tmp/evaluation/242216-1168701566/CSPtoSAT+minisat /tmp/evaluation/242216-1168701566/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node3/watcher-242216-1168701566 -o ROOT/results/node3/solver-242216-1168701566 -C 1800 -M 900  /tmp/evaluation/242216-1168701566/CSPtoSAT+minisat /tmp/evaluation/242216-1168701566/unknown.xml

META MD5SUM SOLVER= 0ab327eaa5be249b47b2f4b19927f0b0
MD5SUM BENCH=  c8d9181936a64a100d65217b65ed3de1

RANDOM SEED= 841660447

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.279
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.279
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:       1925216 kB
Buffers:          3112 kB
Cached:          30956 kB
SwapCached:        408 kB
Active:          84052 kB
Inactive:         6652 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1925216 kB
SwapTotal:     4192956 kB
SwapFree:      4191880 kB
Dirty:            1864 kB
Writeback:           0 kB
Mapped:          68060 kB
Slab:            25324 kB
Committed_AS:  6207112 kB
PageTables:       1900 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= 66562 MiB



End job on node3 on Sat Jan 13 15:19:30 UTC 2007