Trace number 242255

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.027994 0.0387531

General information on the benchmark

Namedimacs/dubois/
dubois-27_ext.xml
MD5SUMa0ae8c608b67bcc7ed6701414c2585cf
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.027994
SatisfiableNO
(Un)Satisfiability was proved
Number of variables81
Number of constraints54
Maximum constraint arity3
Maximum domain size2
Number of constraints which are defined in extension54
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.02	c preparing clauses for relation R0
0.02	c preparing clauses for relation R1
0.02	c instanciating clauses for relation R0 (supports) and variables V52 V53 V0 
0.02	c instanciating clauses for relation R0 (supports) and variables V0 V54 V1 
0.02	c instanciating clauses for relation R0 (supports) and variables V1 V55 V2 
0.02	c instanciating clauses for relation R0 (supports) and variables V2 V56 V3 
0.02	c instanciating clauses for relation R0 (supports) and variables V3 V57 V4 
0.02	c instanciating clauses for relation R0 (supports) and variables V4 V58 V5 
0.02	c instanciating clauses for relation R0 (supports) and variables V5 V59 V6 
0.02	c instanciating clauses for relation R0 (supports) and variables V6 V60 V7 
0.02	c instanciating clauses for relation R0 (supports) and variables V7 V61 V8 
0.02	c instanciating clauses for relation R0 (supports) and variables V8 V62 V9 
0.02	c instanciating clauses for relation R0 (supports) and variables V9 V63 V10 
0.02	c instanciating clauses for relation R0 (supports) and variables V10 V64 V11 
0.02	c instanciating clauses for relation R0 (supports) and variables V11 V65 V12 
0.02	c instanciating clauses for relation R0 (supports) and variables V12 V66 V13 
0.02	c instanciating clauses for relation R0 (supports) and variables V13 V67 V14 
0.02	c instanciating clauses for relation R0 (supports) and variables V14 V68 V15 
0.02	c instanciating clauses for relation R0 (supports) and variables V15 V69 V16 
0.02	c instanciating clauses for relation R0 (supports) and variables V16 V70 V17 
0.02	c instanciating clauses for relation R0 (supports) and variables V17 V71 V18 
0.02	c instanciating clauses for relation R0 (supports) and variables V18 V72 V19 
0.02	c instanciating clauses for relation R0 (supports) and variables V19 V73 V20 
0.02	c instanciating clauses for relation R0 (supports) and variables V20 V74 V21 
0.02	c instanciating clauses for relation R0 (supports) and variables V21 V75 V22 
0.02	c instanciating clauses for relation R0 (supports) and variables V22 V76 V23 
0.02	c instanciating clauses for relation R0 (supports) and variables V23 V77 V24 
0.02	c instanciating clauses for relation R0 (supports) and variables V24 V78 V25 
0.02	c instanciating clauses for relation R0 (supports) and variables V25 V79 V80 
0.02	c instanciating clauses for relation R0 (supports) and variables V26 V79 V80 
0.02	c instanciating clauses for relation R0 (supports) and variables V27 V78 V26 
0.02	c instanciating clauses for relation R0 (supports) and variables V28 V77 V27 
0.02	c instanciating clauses for relation R0 (supports) and variables V29 V76 V28 
0.02	c instanciating clauses for relation R0 (supports) and variables V30 V75 V29 
0.02	c instanciating clauses for relation R0 (supports) and variables V31 V74 V30 
0.02	c instanciating clauses for relation R0 (supports) and variables V32 V73 V31 
0.02	c instanciating clauses for relation R0 (supports) and variables V33 V72 V32 
0.02	c instanciating clauses for relation R0 (supports) and variables V34 V71 V33 
0.02	c instanciating clauses for relation R0 (supports) and variables V35 V70 V34 
0.02	c instanciating clauses for relation R0 (supports) and variables V36 V69 V35 
0.02	c instanciating clauses for relation R0 (supports) and variables V37 V68 V36 
0.02	c instanciating clauses for relation R0 (supports) and variables V38 V67 V37 
0.02	c instanciating clauses for relation R0 (supports) and variables V39 V66 V38 
0.02	c instanciating clauses for relation R0 (supports) and variables V40 V65 V39 
0.02	c instanciating clauses for relation R0 (supports) and variables V41 V64 V40 
0.02	c instanciating clauses for relation R0 (supports) and variables V42 V63 V41 
0.02	c instanciating clauses for relation R0 (supports) and variables V43 V62 V42 
0.02	c instanciating clauses for relation R0 (supports) and variables V44 V61 V43 
0.02	c instanciating clauses for relation R0 (supports) and variables V45 V60 V44 
0.02	c instanciating clauses for relation R0 (supports) and variables V46 V59 V45 
0.02	c instanciating clauses for relation R0 (supports) and variables V47 V58 V46 
0.02	c instanciating clauses for relation R0 (supports) and variables V48 V57 V47 
0.02	c instanciating clauses for relation R0 (supports) and variables V49 V56 V48 
0.02	c instanciating clauses for relation R0 (supports) and variables V50 V55 V49 
0.02	c instanciating clauses for relation R0 (supports) and variables V51 V54 V50 
0.02	c instanciating clauses for relation R1 (supports) and variables V52 V53 V51 
0.02	c ...done
0.02	c #SATvar=380 #SATclauses=1836 #CSPpredicates=0
0.03	c SAT problem is solved
0.03	restarts              : 3
0.03	conflicts             : 382            (18194 /sec)
0.03	decisions             : 675            (1.48 % random) (32149 /sec)
0.03	propagations          : 21316          (1015241 /sec)
0.03	conflict literals     : 5546           (4.94 % deleted)
0.03	Memory used           : 6.77 MB
0.03	CPU time              : 0.020996 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-242255-1168701568 -o ROOT/results/node3/solver-242255-1168701568 -C 1800 -M 900 /tmp/evaluation/242255-1168701568/CSPtoSAT+minisat /tmp/evaluation/242255-1168701568/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/83 16942
/proc/meminfo: memFree=1922800/2055920 swapFree=4191880/4192956
[pid=16940] ppid=16937 vsize=380 CPUtime=0
/proc/16940/stat : 16940 (CSPtoSAT+minisa) R 16937 16940 16513 0 -1 4194304 41 0 0 0 0 0 0 0 20 0 1 0 218552637 389120 26 18446744073709551615 134512640 134728504 4294956704 18446744073709551615 10880670 0 0 4096 0 0 0 0 17 1 0 0
/proc/16940/statm: 95 26 21 52 0 18 0

Child status: 0
Real time (s): 0.0387531
CPU time (s): 0.027994
CPU user time (s): 0.020996
CPU system time (s): 0.006998
CPU usage (%): 72.2368
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.020996
system time used= 0.006998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 885
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= 80

runsolver used 0.001999 s user time and 0.007998 s system time

The end

Launcher Data (download as text)

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


IDJOB= 242255
IDBENCH= 7378
IDSOLVER= 87
FILE ID= node3/242255-1168701568

PBS_JOBID= 3546995

Free space on /tmp= 66562 MiB

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

META MD5SUM SOLVER= 0ab327eaa5be249b47b2f4b19927f0b0
MD5SUM BENCH=  a0ae8c608b67bcc7ed6701414c2585cf

RANDOM SEED= 961099791

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:       1923680 kB
Buffers:          3116 kB
Cached:          32516 kB
SwapCached:        408 kB
Active:          85580 kB
Inactive:         6656 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1923680 kB
SwapTotal:     4192956 kB
SwapFree:      4191880 kB
Dirty:            3368 kB
Writeback:           0 kB
Mapped:          68060 kB
Slab:            25336 kB
Committed_AS:  6207128 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