Trace number 213823

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
galac 1SAT 1.04584 1.21722

General information on the benchmark

NamepseudoSeries/
circuits/C17.xml
MD5SUM929d790516a575c2b1b19d5c2eb2a093
Bench CategoryN-ARY-INT (n-ary constraints in intension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.013997
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables15
Number of constraints20
Maximum constraint arity5
Maximum domain size2
Number of constraints which are defined in extension0
Number of constraints which are defined in intension20
Global constraints used (with number of constraints)

Solver Data (download as text)

0.04	c --- Preproc Stats ---
0.61	c start processing
0.61	c start relation processing
0.65	c start cnf exporting
0.69	c parsing time : 0.448
0.69	c preprocessing time : 0.529
0.69	
0.69	c Nary constraints - conflicts : 8 supports : 0
0.69	c Binary constraints - conflicts : 12 supports :0
0.69	c max arity constraint : 5
0.69	c Max Tuples generated 32
0.69	c relations : 6
0.69	c relations BDD: 2
0.69	c vars : 38 - clauses :  82
0.69	
0.74	 
0.74	c --- Minisat Stats ---
0.74	 
0.75	c restarts              : 1
0.75	c conflicts             : 0              (nan /sec)
0.75	c decisions             : 8              (0.00 % random) (inf /sec)
0.75	c propagations          : 37             (inf /sec)
0.75	c conflict literals     : 0              ( nan % deleted)
0.75	c Memory used           : 1.73 MB
0.75	c CPU time              : 0 s
0.75	
0.75	s SATISFIABLE
1.21	v 1 1 0 0 0 1 1 1 0 0 0 1 0 0 1

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/node72/watcher-213823-1168226301 -o ROOT/results/node72/solver-213823-1168226301 -C 1800 -M 900 /tmp/evaluation/213823-1168226301/galac.sh /tmp/evaluation/213823-1168226301/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.06 1.65 1.62 5/86 11291
/proc/meminfo: memFree=1373896/2055920 swapFree=4191880/4192956
[pid=11290] ppid=11288 vsize=652 CPUtime=0
/proc/11290/stat : 11290 (galac.sh) R 11288 11290 11160 0 -1 4194304 35 0 0 0 0 0 0 0 18 0 1 0 171039181 667648 19 18446744073709551615 4194304 4520092 548682069344 18446744073709551615 234515134025 0 0 4096 0 0 0 0 17 1 0 0
/proc/11290/statm: 163 19 12 79 0 53 0

[startup+0.108512 s]
/proc/loadavg: 1.06 1.65 1.62 5/86 11291
/proc/meminfo: memFree=1373896/2055920 swapFree=4191880/4192956
[pid=11290] ppid=11288 vsize=47560 CPUtime=0.01
/proc/11290/stat : 11290 (galac.sh) S 11288 11290 11160 0 -1 4194304 763 1704 0 0 0 0 0 1 21 0 1 0 171039181 48701440 365 18446744073709551615 4194304 4520092 548682069344 18446744073709551615 234517359450 0 2 4096 73728 18446744071563181037 0 0 17 0 0 0
/proc/11290/statm: 11890 365 247 79 0 218 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 47560

[startup+0.516548 s]
/proc/loadavg: 1.06 1.65 1.62 5/86 11291
/proc/meminfo: memFree=1373896/2055920 swapFree=4191880/4192956
[pid=11290] ppid=11288 vsize=47560 CPUtime=0.01
/proc/11290/stat : 11290 (galac.sh) S 11288 11290 11160 0 -1 4194304 763 1704 0 0 0 0 0 1 21 0 1 0 171039181 48701440 365 18446744073709551615 4194304 4520092 548682069344 18446744073709551615 234517359450 0 2 4096 73728 18446744071563181037 0 0 17 0 0 0
/proc/11290/statm: 11890 365 247 79 0 218 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 47560

Child status: 0
Real time (s): 1.21722
CPU time (s): 1.04584
CPU user time (s): 0.921859
CPU system time (s): 0.123981
CPU usage (%): 85.9202
Max. virtual memory (cumulated for all children) (KiB): 908688

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.921859
system time used= 0.123981
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 19785
page faults= 2
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 595
involuntary context switches= 476

runsolver used 0.005999 s user time and 0.009998 s system time

The end

Launcher Data (download as text)

Begin job on node72 on Mon Jan  8 03:18:24 UTC 2007


IDJOB= 213823
IDBENCH= 4877
FILE ID= node72/213823-1168226301

PBS_JOBID= 3481336

Free space on /tmp= 66556 MiB

BENCH NAME= HOME/pub/bench/CPAI06/pseudoSeries/circuits/C17.xml
COMMAND LINE= /tmp/evaluation/213823-1168226301/galac.sh /tmp/evaluation/213823-1168226301/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node72/watcher-213823-1168226301 -o ROOT/results/node72/solver-213823-1168226301 -C 1800 -M 900  /tmp/evaluation/213823-1168226301/galac.sh /tmp/evaluation/213823-1168226301/unknown.xml

META MD5SUM SOLVER= d8bf20eb49fe33822f00bab08f33d7fc
MD5SUM BENCH=  929d790516a575c2b1b19d5c2eb2a093

RANDOM SEED= 69017917

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:       1375696 kB
Buffers:         54252 kB
Cached:         505932 kB
SwapCached:        408 kB
Active:         125296 kB
Inactive:       482332 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1375696 kB
SwapTotal:     4192956 kB
SwapFree:      4191880 kB
Dirty:            5348 kB
Writeback:           0 kB
Mapped:          64672 kB
Slab:            57672 kB
Committed_AS:  3174220 kB
PageTables:       2112 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= 66556 MiB



End job on node72 on Mon Jan  8 03:18:26 UTC 2007