Trace number 191776

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 1.03984 1.24885

General information on the benchmark

Namecomposed/composed-75-1-25/
composed-75-1-25-4_ext.xml
MD5SUMd80236f9faf8071996b01e9c0e255964
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.05699
SatisfiableNO
(Un)Satisfiability was provedNO
Number of variables83
Number of constraints647
Maximum constraint arity2
Maximum domain size10
Number of constraints which are defined in extension647
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.17	rm: No match.
0.17	c --- Preproc Stats ---
0.17	c benchs : unknown.xml
1.07	c start processing
1.07	c start relation processing
1.08	c start cnf exporting
1.14	c parsing time : 0.764
1.14	c preprocessing time : 0.833
1.14	
1.14	c Nary constraints - conflicts : 0 supports : 0
1.14	c Binary constraints - conflicts : 625 supports :22
1.14	c max arity constraint : 2
1.14	c Max Tuples generated 0
1.14	c relations : 647
1.14	c relations BDD: 0
1.14	c vars : 831 - clauses :  13378
1.14	
1.17	c Start Sat4J solver
1.17	
1.20	s UNSATISFIABLE
1.20	c {propagations=178, learnedliterals=1, changedreason=0, reduceddb=0, starts=1, learnedbinaryclauses=2, learnedclauses=7, reducedliterals=9, learnedternaryclauses=1, conflicts=9, serialVersionUID=1, inspects=1714, rootSimplifications=0, decisions=14}

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-191776-1168096162 -o ROOT/results/node52/solver-191776-1168096162 -C 1800 -M 900 /tmp/evaluation/191776-1168096162/galacJ.sh /tmp/evaluation/191776-1168096162/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.13 0.96 1.50 4/68 362
/proc/meminfo: memFree=1427448/2055920 swapFree=4192812/4192956
[pid=361] ppid=359 vsize=5180 CPUtime=0
/proc/361/stat : 361 (galacJ.sh) D 359 361 32688 0 -1 4194304 80 0 0 0 0 0 0 0 18 0 1 0 158015448 5304320 53 18446744073709551615 4194304 4520092 548682069328 18446744073709551615 4456064 0 0 4096 0 18446744071563479169 0 0 17 1 0 0
/proc/361/statm: 1295 53 37 79 0 105 0

[startup+0.106378 s]
/proc/loadavg: 0.13 0.96 1.50 4/68 362
/proc/meminfo: memFree=1427448/2055920 swapFree=4192812/4192956
[pid=361] ppid=359 vsize=8784 CPUtime=0.01
/proc/361/stat : 361 (galacJ.sh) D 359 361 32688 0 -1 4194304 616 1485 3 0 0 0 0 1 16 0 1 0 158015448 8994816 320 18446744073709551615 4194304 4520092 548682069328 18446744073709551615 273653923922 0 2 4096 73728 18446744071563479169 0 0 17 0 0 0
/proc/361/statm: 2196 320 218 79 0 189 0
Current children cumulated CPU time (s) 0.01
Current children cumulated vsize (KiB) 8784

[startup+0.514408 s]
/proc/loadavg: 0.13 0.96 1.50 4/68 362
/proc/meminfo: memFree=1427448/2055920 swapFree=4192812/4192956
[pid=361] ppid=359 vsize=47552 CPUtime=0.02
/proc/361/stat : 361 (galacJ.sh) S 359 361 32688 0 -1 4194304 789 1728 6 0 0 1 0 1 18 0 1 0 158015448 48693248 362 18446744073709551615 4194304 4520092 548682069328 18446744073709551615 273653361498 0 2 4096 73728 18446744071563181037 0 0 17 0 0 0
/proc/361/statm: 11888 362 245 79 0 217 0
Current children cumulated CPU time (s) 0.02
Current children cumulated vsize (KiB) 47552

Child status: 0
Real time (s): 1.24885
CPU time (s): 1.03984
CPU user time (s): 0.927858
CPU system time (s): 0.111982
CPU usage (%): 83.2637
Max. virtual memory (cumulated for all children) (KiB): 910408

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.927858
system time used= 0.111982
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 14930
page faults= 9
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 834
involuntary context switches= 150

runsolver used 0.006998 s user time and 0.007998 s system time

The end

Launcher Data (download as text)

Begin job on node52 on Sat Jan  6 15:09:27 UTC 2007


IDJOB= 191776
IDBENCH= 3072
FILE ID= node52/191776-1168096162

PBS_JOBID= 3476741

Free space on /tmp= 66549 MiB

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

META MD5SUM SOLVER= ffd78bd56f274e94bd0d0faf76d262cb
MD5SUM BENCH=  d80236f9faf8071996b01e9c0e255964

RANDOM SEED= 439117993

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:       1426224 kB
Buffers:         41408 kB
Cached:         490012 kB
SwapCached:          0 kB
Active:          91352 kB
Inactive:       461660 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1426224 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            4404 kB
Writeback:           0 kB
Mapped:          32440 kB
Slab:            62136 kB
Committed_AS:  3208376 kB
PageTables:       1888 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= 66549 MiB



End job on node52 on Sat Jan  6 15:09:34 UTC 2007