Trace number 209985

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 1UNSAT 0.878865 0.910207

General information on the benchmark

NameschurrLemma/
lemma-24-3.xml
MD5SUM2d89d082bab320d272974b2d2c3ae9ce
Bench CategoryN-ARY-INT (n-ary constraints in intension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.32495
SatisfiableNO
(Un)Satisfiability was provedNO
Number of variables24
Number of constraints132
Maximum constraint arity3
Maximum domain size3
Number of constraints which are defined in extension0
Number of constraints which are defined in intension132
Global constraints used (with number of constraints)

Solver Data (download as text)

0.03	c --- Preproc Stats ---
0.69	c start processing
0.69	c start relation processing
0.69	c start cnf exporting
0.83	c parsing time : 0.527
0.83	c preprocessing time : 0.668
0.83	
0.83	c Nary constraints - conflicts : 132 supports : 0
0.83	c Binary constraints - conflicts : 0 supports :0
0.83	c max arity constraint : 3
0.83	c Max Tuples generated 27
0.83	c relations : 1
0.83	c relations BDD: 0
0.83	c vars : 73 - clauses :  492
0.83	
0.85	 
0.85	c --- Minisat Stats ---
0.85	 
0.90	c restarts              : 8
0.90	c conflicts             : 4372           (79504 /sec)
0.90	c decisions             : 5256           (1.46 % random) (95579 /sec)
0.90	c propagations          : 84250          (1532069 /sec)
0.90	c conflict literals     : 37568          (11.58 % deleted)
0.90	c Memory used           : 1.73 MB
0.90	c CPU time              : 0.054991 s
0.90	
0.90	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/node40/watcher-209985-1168195405 -o ROOT/results/node40/solver-209985-1168195405 -C 1800 -M 900 /tmp/evaluation/209985-1168195405/galac.sh /tmp/evaluation/209985-1168195405/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: 2.07 2.02 2.00 5/73 27869
/proc/meminfo: memFree=1681480/2055920 swapFree=4192812/4192956
[pid=27868] ppid=27866 vsize=5184 CPUtime=0
/proc/27868/stat : 27868 (galac.sh) R 27866 27868 27598 0 -1 4194304 99 0 0 0 0 0 0 0 20 0 1 0 167939814 5308416 71 18446744073709551615 4194304 4520092 548682069344 18446744073709551615 4320528 0 0 4096 0 0 0 0 17 1 0 0
/proc/27868/statm: 1296 71 54 79 0 106 0

[startup+0.104222 s]
/proc/loadavg: 2.07 2.02 2.00 5/73 27869
/proc/meminfo: memFree=1681480/2055920 swapFree=4192812/4192956
[pid=27868] ppid=27866 vsize=47564 CPUtime=0.01
/proc/27868/stat : 27868 (galac.sh) S 27866 27868 27598 0 -1 4194304 762 1704 0 0 0 0 0 1 18 0 1 0 167939814 48705536 363 18446744073709551615 4194304 4520092 548682069344 18446744073709551615 264519215962 0 2 4096 73728 18446744071563181037 0 0 17 1 0 0
/proc/27868/statm: 11891 363 245 79 0 218 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 47564

[startup+0.512274 s]
/proc/loadavg: 2.07 2.02 2.00 5/73 27869
/proc/meminfo: memFree=1681480/2055920 swapFree=4192812/4192956
[pid=27868] ppid=27866 vsize=47564 CPUtime=0.01
/proc/27868/stat : 27868 (galac.sh) S 27866 27868 27598 0 -1 4194304 762 1704 0 0 0 0 0 1 18 0 1 0 167939814 48705536 363 18446744073709551615 4194304 4520092 548682069344 18446744073709551615 264519215962 0 2 4096 73728 18446744071563181037 0 0 17 1 0 0
/proc/27868/statm: 11891 363 245 79 0 218 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 47564

Child status: 0
Real time (s): 0.910207
CPU time (s): 0.878865
CPU user time (s): 0.777881
CPU system time (s): 0.100984
CPU usage (%): 96.5566
Max. virtual memory (cumulated for all children) (KiB): 47564

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.777881
system time used= 0.100984
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 14648
page faults= 1
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 851
involuntary context switches= 818

runsolver used 0.003999 s user time and 0.004999 s system time

The end

Launcher Data (download as text)

Begin job on node40 on Sun Jan  7 18:43:25 UTC 2007


IDJOB= 209985
IDBENCH= 4585
FILE ID= node40/209985-1168195405

PBS_JOBID= 3479457

Free space on /tmp= 66546 MiB

BENCH NAME= HOME/pub/bench/CPAI06/schurrLemma/lemma-24-3.xml
COMMAND LINE= /tmp/evaluation/209985-1168195405/galac.sh /tmp/evaluation/209985-1168195405/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node40/watcher-209985-1168195405 -o ROOT/results/node40/solver-209985-1168195405 -C 1800 -M 900  /tmp/evaluation/209985-1168195405/galac.sh /tmp/evaluation/209985-1168195405/unknown.xml

META MD5SUM SOLVER= d8bf20eb49fe33822f00bab08f33d7fc
MD5SUM BENCH=  2d89d082bab320d272974b2d2c3ae9ce

RANDOM SEED= 877644116

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.239
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.239
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:       1681960 kB
Buffers:         22172 kB
Cached:         216440 kB
SwapCached:          0 kB
Active:         179004 kB
Inactive:       141360 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1681960 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            3028 kB
Writeback:           0 kB
Mapped:          95360 kB
Slab:            38888 kB
Committed_AS:  3532024 kB
PageTables:       1976 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= 66546 MiB



End job on node40 on Sun Jan  7 18:43:26 UTC 2007