Trace number 216915

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 1UNSAT 0.886864 0.929105

General information on the benchmark

Namecomposed/composed-25-1-25/
composed-25-1-25-4_ext.xml
MD5SUM9f7d8dbbe1d24a7f253b985620679f04
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.023995
SatisfiableNO
(Un)Satisfiability was provedNO
Number of variables33
Number of constraints247
Maximum constraint arity2
Maximum domain size10
Number of constraints which are defined in extension247
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.05	rm: No match.
0.05	c --- Preproc Stats ---
0.05	c benchs : unknown.xml
0.81	c start processing
0.81	c start relation processing
0.81	c start cnf exporting
0.86	c parsing time : 0.615
0.86	c preprocessing time : 0.675
0.86	
0.86	c Nary constraints - conflicts : 0 supports : 0
0.87	c Binary constraints - conflicts : 225 supports :22
0.87	c max arity constraint : 2
0.87	c Max Tuples generated 0
0.87	c relations : 247
0.87	c relations BDD: 0
0.87	c vars : 331 - clauses :  5082
0.87	
0.89	c Start Sat4J solver
0.89	
0.91	s UNSATISFIABLE
0.92	c {propagations=280, learnedliterals=1, changedreason=0, reduceddb=0, starts=1, learnedbinaryclauses=1, learnedclauses=6, reducedliterals=3, learnedternaryclauses=1, conflicts=8, serialVersionUID=1, inspects=2106, rootSimplifications=0, decisions=8}

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/node5/watcher-216915-1168244162 -o ROOT/results/node5/solver-216915-1168244162 -C 1800 -M 900 /tmp/evaluation/216915-1168244162/galacJ.sh /tmp/evaluation/216915-1168244162/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.19 1.69 1.88 3/94 30810
/proc/meminfo: memFree=1327600/2055920 swapFree=4192812/4192956
[pid=30809] ppid=30807 vsize=6348 CPUtime=0
/proc/30809/stat : 30809 (galacJ.sh) R 30807 30809 30431 0 -1 4194304 261 0 0 0 0 0 0 0 20 0 1 0 153030752 6500352 216 18446744073709551615 4194304 4520092 548682069328 18446744073709551615 226913359211 0 0 4096 8192 0 0 0 17 1 0 0
/proc/30809/statm: 1587 216 165 79 0 123 0

[startup+0.10448 s]
/proc/loadavg: 1.19 1.69 1.88 3/94 30810
/proc/meminfo: memFree=1327600/2055920 swapFree=4192812/4192956
[pid=30809] ppid=30807 vsize=47556 CPUtime=0.01
/proc/30809/stat : 30809 (galacJ.sh) S 30807 30809 30431 0 -1 4194304 797 1728 0 0 0 0 0 1 22 0 1 0 153030752 48697344 362 18446744073709551615 4194304 4520092 548682069328 18446744073709551615 226913086298 0 2 4096 73728 18446744071563181037 0 0 17 1 0 0
/proc/30809/statm: 11889 362 245 79 0 217 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 47556

[startup+0.512525 s]
/proc/loadavg: 1.19 1.69 1.88 3/94 30810
/proc/meminfo: memFree=1327600/2055920 swapFree=4192812/4192956
[pid=30809] ppid=30807 vsize=47556 CPUtime=0.01
/proc/30809/stat : 30809 (galacJ.sh) S 30807 30809 30431 0 -1 4194304 797 1728 0 0 0 0 0 1 22 0 1 0 153030752 48697344 362 18446744073709551615 4194304 4520092 548682069328 18446744073709551615 226913086298 0 2 4096 73728 18446744071563181037 0 0 17 1 0 0
/proc/30809/statm: 11889 362 245 79 0 217 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 47556

Child status: 0
Real time (s): 0.929105
CPU time (s): 0.886864
CPU user time (s): 0.790879
CPU system time (s): 0.095985
CPU usage (%): 95.4536
Max. virtual memory (cumulated for all children) (KiB): 47556

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

runsolver used 0.005999 s user time and 0.004999 s system time

The end

Launcher Data (download as text)

Begin job on node5 on Mon Jan  8 08:16:03 UTC 2007


IDJOB= 216915
IDBENCH= 5108
FILE ID= node5/216915-1168244162

PBS_JOBID= 3481587

Free space on /tmp= 66352 MiB

BENCH NAME= HOME/pub/bench/CPAI06/composed/composed-25-1-25/composed-25-1-25-4_ext.xml
COMMAND LINE= /tmp/evaluation/216915-1168244162/galacJ.sh /tmp/evaluation/216915-1168244162/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node5/watcher-216915-1168244162 -o ROOT/results/node5/solver-216915-1168244162 -C 1800 -M 900  /tmp/evaluation/216915-1168244162/galacJ.sh /tmp/evaluation/216915-1168244162/unknown.xml

META MD5SUM SOLVER= ffd78bd56f274e94bd0d0faf76d262cb
MD5SUM BENCH=  9f7d8dbbe1d24a7f253b985620679f04

RANDOM SEED= 571872718

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.240
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.240
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:       1328208 kB
Buffers:         61428 kB
Cached:         508752 kB
SwapCached:          0 kB
Active:         255044 kB
Inactive:       409468 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1328208 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            3648 kB
Writeback:           0 kB
Mapped:         122084 kB
Slab:            47800 kB
Committed_AS:  4731736 kB
PageTables:       2364 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= 66352 MiB



End job on node5 on Mon Jan  8 08:16:04 UTC 2007