Trace number 217105

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.893863 0.954715

General information on the benchmark

Namecomposed/composed-25-1-40/
composed-25-1-40-5_ext.xml
MD5SUMf949c768ad43ca425c1184f86c1aaa53
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.024995
SatisfiableNO
(Un)Satisfiability was provedNO
Number of variables33
Number of constraints262
Maximum constraint arity2
Maximum domain size10
Number of constraints which are defined in extension262
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.78	c start processing
0.78	c start relation processing
0.79	c start cnf exporting
0.84	c parsing time : 0.622
0.84	c preprocessing time : 0.68
0.84	
0.84	c Nary constraints - conflicts : 0 supports : 0
0.84	c Binary constraints - conflicts : 240 supports :22
0.84	c max arity constraint : 2
0.84	c Max Tuples generated 0
0.84	c relations : 262
0.84	c relations BDD: 0
0.84	c vars : 331 - clauses :  5149
0.84	
0.87	c Start Sat4J solver
0.87	
0.89	s UNSATISFIABLE
0.89	c {propagations=298, learnedliterals=1, changedreason=0, reduceddb=0, starts=1, learnedbinaryclauses=2, learnedclauses=7, reducedliterals=14, learnedternaryclauses=1, conflicts=9, serialVersionUID=1, inspects=2214, rootSimplifications=0, decisions=9}

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/node52/watcher-217105-1168434390 -o ROOT/results/node52/solver-217105-1168434390 -C 1800 -M 900 /tmp/evaluation/217105-1168434390/galacJ.sh /tmp/evaluation/217105-1168434390/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.86 1.88 1.50 5/81 28680
/proc/meminfo: memFree=1098552/2055920 swapFree=4192812/4192956
[pid=28679] ppid=28677 vsize=8560 CPUtime=0
/proc/28679/stat : 28679 (galacJ.sh) R 28677 28679 28044 0 -1 4194304 308 0 0 0 0 0 0 0 20 0 1 0 191837461 8765440 253 18446744073709551615 4194304 4520092 548682069328 18446744073709551615 273653942159 0 0 4096 8192 0 0 0 17 1 0 0
/proc/28679/statm: 2140 253 197 79 0 133 0

[startup+0.10547 s]
/proc/loadavg: 1.86 1.88 1.50 5/81 28680
/proc/meminfo: memFree=1098552/2055920 swapFree=4192812/4192956
[pid=28679] ppid=28677 vsize=47552 CPUtime=0.01
/proc/28679/stat : 28679 (galacJ.sh) S 28677 28679 28044 0 -1 4194304 796 1728 0 0 0 0 0 1 24 0 1 0 191837461 48693248 362 18446744073709551615 4194304 4520092 548682069328 18446744073709551615 273653361498 0 2 4096 73728 18446744071563181037 0 0 17 1 0 0
/proc/28679/statm: 11888 362 245 79 0 217 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 47552

[startup+0.517497 s]
/proc/loadavg: 1.86 1.88 1.50 5/81 28680
/proc/meminfo: memFree=1098552/2055920 swapFree=4192812/4192956
[pid=28679] ppid=28677 vsize=47552 CPUtime=0.01
/proc/28679/stat : 28679 (galacJ.sh) S 28677 28679 28044 0 -1 4194304 796 1728 0 0 0 0 0 1 24 0 1 0 191837461 48693248 362 18446744073709551615 4194304 4520092 548682069328 18446744073709551615 273653361498 0 2 4096 73728 18446744071563181037 0 0 17 1 0 0
/proc/28679/statm: 11888 362 245 79 0 217 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 47552

Child status: 0
Real time (s): 0.954715
CPU time (s): 0.893863
CPU user time (s): 0.798878
CPU system time (s): 0.094985
CPU usage (%): 93.6262
Max. virtual memory (cumulated for all children) (KiB): 47552

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.798878
system time used= 0.094985
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 12751
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= 905
involuntary context switches= 883

runsolver used 0.001999 s user time and 0.005999 s system time

The end

Launcher Data (download as text)

Begin job on node52 on Wed Jan 10 13:06:30 UTC 2007


IDJOB= 217105
IDBENCH= 5118
FILE ID= node52/217105-1168434390

PBS_JOBID= 3523938

Free space on /tmp= 66555 MiB

BENCH NAME= HOME/pub/bench/CPAI06/composed/composed-25-1-40/composed-25-1-40-5_ext.xml
COMMAND LINE= /tmp/evaluation/217105-1168434390/galacJ.sh /tmp/evaluation/217105-1168434390/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node52/watcher-217105-1168434390 -o ROOT/results/node52/solver-217105-1168434390 -C 1800 -M 900  /tmp/evaluation/217105-1168434390/galacJ.sh /tmp/evaluation/217105-1168434390/unknown.xml

META MD5SUM SOLVER= ffd78bd56f274e94bd0d0faf76d262cb
MD5SUM BENCH=  f949c768ad43ca425c1184f86c1aaa53

RANDOM SEED= 79760220

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:       1099160 kB
Buffers:         34564 kB
Cached:         146044 kB
SwapCached:          0 kB
Active:         788660 kB
Inactive:       105268 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1099160 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            3588 kB
Writeback:           0 kB
Mapped:         732296 kB
Slab:            46620 kB
Committed_AS:  5367660 kB
PageTables:       3324 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= 66555 MiB



End job on node52 on Wed Jan 10 13:06:31 UTC 2007