Trace number 243146

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
galacJ beta 1SAT 0.964853 1.02357

General information on the benchmark

Namedimacs/aim-50/
aim-50-2-0-sat-4_ext.xml
MD5SUM21494f4758a42f305bdee38339469e3e
Bench CategoryN-ARY-EXT (n-ary constraints in extension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.016996
SatisfiableYES
(Un)Satisfiability was proved
Number of variables50
Number of constraints94
Maximum constraint arity3
Maximum domain size2
Number of constraints which are defined in extension94
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.03	rm: No match.
0.03	c --- Preproc Stats ---
0.03	c benchs : unknown.xml
0.50	c start processing
0.51	c start relation processing
0.51	c start cnf exporting
0.51	c parsing time : 0.346
0.51	c preprocessing time : 0.352
0.51	
0.51	c Nary constraints - conflicts : 93 supports : 0
0.51	c Binary constraints - conflicts : 1 supports :0
0.51	c max arity constraint : 3
0.51	c Max Tuples generated 0
0.51	c relations : 14
0.51	c relations BDD: 0
0.51	c vars : 51 - clauses :  100
0.51	
0.53	c Start Sat4J solver
0.53	
0.54	s SATISFIABLE
0.54	c {propagations=94, learnedliterals=0, changedreason=0, reduceddb=0, starts=1, learnedbinaryclauses=4, learnedclauses=9, reducedliterals=0, learnedternaryclauses=3, conflicts=9, serialVersionUID=1, inspects=207, rootSimplifications=0, decisions=21}
1.02	v  0 0 0 0 1 0 0 1 1 1 0 0 1 1 0 1 0 1 0 0 0 1 1 1 1 1 0 1 1 0 1 0 1 0 0 0 0 1 0 0 0 1 1 0 1 1 1 1 1 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/node10/watcher-243146-1168383814 -o ROOT/results/node10/solver-243146-1168383814 -C 1800 -M 900 /tmp/evaluation/243146-1168383814/galacJ.sh /tmp/evaluation/243146-1168383814/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.15 0.66 0.91 4/79 26426
/proc/meminfo: memFree=1831856/2055920 swapFree=4178216/4192956
[pid=26425] ppid=26422 vsize=5236 CPUtime=0
/proc/26425/stat : 26425 (galacJ.sh) R 26422 26425 25582 0 -1 4194304 142 0 0 0 0 0 0 0 20 0 1 0 186776862 5361664 110 18446744073709551615 4194304 4520092 548682069328 18446744073709551615 4444368 0 0 4096 0 0 0 0 17 1 0 0
/proc/26425/statm: 1309 110 82 79 0 113 0

[startup+0.103678 s]
/proc/loadavg: 0.15 0.66 0.91 4/79 26426
/proc/meminfo: memFree=1831856/2055920 swapFree=4178216/4192956
[pid=26425] ppid=26422 vsize=47572 CPUtime=0.01
/proc/26425/stat : 26425 (galacJ.sh) S 26422 26425 25582 0 -1 4194304 796 1728 0 0 0 0 0 1 17 0 1 0 186776862 48713728 362 18446744073709551615 4194304 4520092 548682069328 18446744073709551615 214919474010 0 2 4096 73728 18446744071563181037 0 0 17 1 0 0
/proc/26425/statm: 11893 362 245 79 0 217 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 47572

[startup+0.511738 s]
/proc/loadavg: 0.15 0.66 0.91 4/79 26426
/proc/meminfo: memFree=1831856/2055920 swapFree=4178216/4192956
[pid=26425] ppid=26422 vsize=47572 CPUtime=0.01
/proc/26425/stat : 26425 (galacJ.sh) S 26422 26425 25582 0 -1 4194304 796 1728 0 0 0 0 0 1 17 0 1 0 186776862 48713728 362 18446744073709551615 4194304 4520092 548682069328 18446744073709551615 214919474010 0 2 4096 73728 18446744071563181037 0 0 17 1 0 0
/proc/26425/statm: 11893 362 245 79 0 217 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 47572

Child status: 0
Real time (s): 1.02357
CPU time (s): 0.964853
CPU user time (s): 0.833873
CPU system time (s): 0.13098
CPU usage (%): 94.2639
Max. virtual memory (cumulated for all children) (KiB): 47572

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

runsolver used 0.001999 s user time and 0.006998 s system time

The end

Launcher Data (download as text)

Begin job on node10 on Tue Jan  9 23:03:37 UTC 2007


IDJOB= 243146
IDBENCH= 7446
FILE ID= node10/243146-1168383814

PBS_JOBID= 3522541

Free space on /tmp= 66560 MiB

BENCH NAME= HOME/pub/bench/CPAI06/dimacs/aim-50/aim-50-2-0-sat-4_ext.xml
COMMAND LINE= /tmp/evaluation/243146-1168383814/galacJ.sh /tmp/evaluation/243146-1168383814/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node10/watcher-243146-1168383814 -o ROOT/results/node10/solver-243146-1168383814 -C 1800 -M 900  /tmp/evaluation/243146-1168383814/galacJ.sh /tmp/evaluation/243146-1168383814/unknown.xml

META MD5SUM SOLVER= ffd78bd56f274e94bd0d0faf76d262cb
MD5SUM BENCH=  21494f4758a42f305bdee38339469e3e

RANDOM SEED= 971693013

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.232
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.232
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:       1832336 kB
Buffers:         24416 kB
Cached:         118152 kB
SwapCached:       1864 kB
Active:         117556 kB
Inactive:        53956 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1832336 kB
SwapTotal:     4192956 kB
SwapFree:      4178216 kB
Dirty:            3612 kB
Writeback:           0 kB
Mapped:          38720 kB
Slab:            37432 kB
Committed_AS:  5470660 kB
PageTables:       1864 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= 66560 MiB



End job on node10 on Tue Jan  9 23:03:39 UTC 2007