Trace number 230574

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
CSP4J - Combo 2006-12-19SAT 0.790878 0.927886

DiagnosticValue
NODES64

General information on the benchmark

Namegeom/
geo50-20-d4-75-98_ext.xml
MD5SUMe5ab1747cde861323d93f50120d77a34
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.117981
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables50
Number of constraints377
Maximum constraint arity2
Maximum domain size20
Number of constraints which are defined in extension377
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.87	v 15 15 5 4 14 2 7 7 14 11 7 13 6 1 8 6 12 6 17 5 1 14 11 15 12 5 11 4 15 8 2 5 11 11 5 3 18 12 19 5 16 4 19 5 12 9 5 1 1 4 
0.87	s SATISFIABLE
0.87	d NODES 64

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/node60/watcher-230574-1168316846 -o ROOT/results/node60/solver-230574-1168316846 -C 1800 -M 900 /tmp/evaluation/230574-1168316846/cspfj.sh -solver Combo -competition /tmp/evaluation/230574-1168316846/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.50 1.73 1.88 3/85 12368
/proc/meminfo: memFree=1370984/2055920 swapFree=4192812/4192956
[pid=12367] ppid=12365 vsize=5352 CPUtime=0
/proc/12367/stat : 12367 (cspfj.sh) D 12365 12367 11956 0 -1 4194304 295 128 0 0 0 0 0 0 18 0 1 0 180082746 5480448 240 18446744073709551615 4194304 4889804 548682069280 18446744073709551615 271894411877 0 2147483391 4100 65536 18446744072099781622 0 0 17 1 0 0
/proc/12367/statm: 1338 240 201 169 0 49 0

[startup+0.102509 s]
/proc/loadavg: 1.50 1.73 1.88 3/85 12368
/proc/meminfo: memFree=1370984/2055920 swapFree=4192812/4192956
[pid=12367] ppid=12365 vsize=5352 CPUtime=0
/proc/12367/stat : 12367 (cspfj.sh) S 12365 12367 11956 0 -1 4194304 315 128 0 0 0 0 0 0 18 0 1 0 180082746 5480448 240 18446744073709551615 4194304 4889804 548682069280 18446744073709551615 271894242116 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/12367/statm: 1338 240 201 169 0 49 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 5352

[startup+0.510548 s]
/proc/loadavg: 1.50 1.73 1.88 3/85 12368
/proc/meminfo: memFree=1370984/2055920 swapFree=4192812/4192956
[pid=12367] ppid=12365 vsize=5352 CPUtime=0
/proc/12367/stat : 12367 (cspfj.sh) S 12365 12367 11956 0 -1 4194304 315 128 0 0 0 0 0 0 18 0 1 0 180082746 5480448 240 18446744073709551615 4194304 4889804 548682069280 18446744073709551615 271894242116 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/12367/statm: 1338 240 201 169 0 49 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 5352

Child status: 0
Real time (s): 0.927886
CPU time (s): 0.790878
CPU user time (s): 0.730888
CPU system time (s): 0.05999
CPU usage (%): 85.2344
Max. virtual memory (cumulated for all children) (KiB): 5352

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.730888
system time used= 0.05999
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 4966
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= 1183
involuntary context switches= 1095

runsolver used 0.004999 s user time and 0.004999 s system time

The end

Launcher Data (download as text)

Begin job on node60 on Tue Jan  9 04:27:27 UTC 2007


IDJOB= 230574
IDBENCH= 6421
FILE ID= node60/230574-1168316846

PBS_JOBID= 3502503

Free space on /tmp= 66562 MiB

BENCH NAME= HOME/pub/bench/CPAI06/geom/geo50-20-d4-75-98_ext.xml
COMMAND LINE= /tmp/evaluation/230574-1168316846/cspfj.sh -solver Combo -competition /tmp/evaluation/230574-1168316846/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node60/watcher-230574-1168316846 -o ROOT/results/node60/solver-230574-1168316846 -C 1800 -M 900  /tmp/evaluation/230574-1168316846/cspfj.sh -solver Combo -competition /tmp/evaluation/230574-1168316846/unknown.xml

META MD5SUM SOLVER= ae5901f6cce23734dab709fa25e92adb
MD5SUM BENCH=  e5ab1747cde861323d93f50120d77a34

RANDOM SEED= 664841633

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.236
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.236
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:       1371592 kB
Buffers:         73012 kB
Cached:         442156 kB
SwapCached:          0 kB
Active:         315664 kB
Inactive:       307384 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1371592 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:             540 kB
Writeback:           0 kB
Mapped:         128048 kB
Slab:            46432 kB
Committed_AS:  5132988 kB
PageTables:       2068 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= 66562 MiB



End job on node60 on Tue Jan  9 04:27:30 UTC 2007