Trace number 195671

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
Tramontane 2006-12-04SAT 0.414936 0.446263

General information on the benchmark

Namerlfap/rlfapGraphs/
graph1.xml
MD5SUM7d2754cc44d2423629dbe49c143cee41
Bench Category2-ARY-INT (binary constraints in intension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.405937
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables200
Number of constraints1134
Maximum constraint arity2
Maximum domain size44
Number of constraints which are defined in extension0
Number of constraints which are defined in intension1134
Global constraints used (with number of constraints)

Solver Data (download as text)

0.04	c 
0.04	c Parsing xml file
0.04	c 	domains...............    0
0.04	c 	variables.............    0
0.04	c 	predicates............    0
0.04	c 	constraints........... 0.06
0.11	c Allocating memory
0.11	c 
0.11	c time limit = -1
0.11	c heuristic = dom/wdeg
0.11	c restart policy = Geometric increment
0.11	c restart base = 133
0.11	c restart factor = 1.33
0.11	c 
0.11	c Solving
0.11	c
0.35	s SATISFIABLE
0.35	v 268 30 254 16 666 428 142 380 380 142 310 72 282 44 324 86 86 324 16 254 58 296 240 478 296 58 722 484 296 58 30 268 268 30 310 72 44 282 16 254 114 352 72 310 16 254 86 324 310 72 16 254 72 310 30 268 16 254 254 16 366 128 16 254 100 338 58 296 296 58 58 296 380 142 30 268 156 394 30 268 254 16 30 268 30 268 324 86 338 100 366 128 30 268 58 296 142 380 30 268 680 442 128 366 428 666 44 282 16 254 86 324 338 100 100 338 16 254 58 296 142 380 142 380 254 16 428 666 268 30 282 44 44 282 142 380 44 282 296 58 324 86 282 44 114 352 338 100 30 268 310 72 100 338 324 86 394 156 338 100 366 128 142 380 442 680 428 666 254 16 128 366 254 16 254 16 16 254 282 44 652 414 114 352 324 86 100 338 30 268 366 128 380 142 142 380 86 324 142 380
0.35	d          SAT         0 BTS      0.07 s

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/node51/watcher-195671-1168113352 -o ROOT/results/node51/solver-195671-1168113352 -C 1800 -M 900 /tmp/evaluation/195671-1168113352/tramontane/bin/solver /tmp/evaluation/195671-1168113352/unknown.xml -res geom -f 3 -v 1 

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.24 1.55 1.80 4/68 9744
/proc/meminfo: memFree=1552864/2055920 swapFree=4192812/4192956
[pid=9743] ppid=9741 vsize=540 CPUtime=0
/proc/9743/stat : 9743 (solver) D 9741 9743 8988 0 -1 4194304 41 0 0 0 0 0 0 0 18 0 1 0 159733809 552960 26 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 2618148 0 2147483391 4096 0 18446744072099781622 0 0 17 1 0 0
/proc/9743/statm: 135 26 21 92 0 18 0

[startup+0.104464 s]
/proc/loadavg: 1.24 1.55 1.80 4/68 9744
/proc/meminfo: memFree=1552864/2055920 swapFree=4192812/4192956
[pid=9743] ppid=9741 vsize=8500 CPUtime=0.07
/proc/9743/stat : 9743 (solver) R 9741 9743 8988 0 -1 4194304 1207 0 0 0 7 0 0 0 18 0 1 0 159733809 8704000 1175 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 4159297746 0 0 4096 0 0 0 0 17 0 0 0
/proc/9743/statm: 2125 1175 706 92 0 469 0
Current children cumulated CPU time (s) 0.07
Current children cumulated vsize (KiB) 8500

Child status: 0
Real time (s): 0.446263
CPU time (s): 0.414936
CPU user time (s): 0.371943
CPU system time (s): 0.042993
CPU usage (%): 92.9801
Max. virtual memory (cumulated for all children) (KiB): 39656

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.371943
system time used= 0.042993
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 9012
page faults= 0
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 12
involuntary context switches= 5

runsolver used 0.006998 s user time and 0.001999 s system time

The end

Launcher Data (download as text)

Begin job on node51 on Sat Jan  6 19:55:53 UTC 2007


IDJOB= 195671
IDBENCH= 3293
FILE ID= node51/195671-1168113352

PBS_JOBID= 3477403

Free space on /tmp= 66543 MiB

BENCH NAME= HOME/pub/bench/CPAI06/rlfap/rlfapGraphs/graph1.xml
COMMAND LINE= /tmp/evaluation/195671-1168113352/tramontane/bin/solver /tmp/evaluation/195671-1168113352/unknown.xml -res geom -f 3 -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node51/watcher-195671-1168113352 -o ROOT/results/node51/solver-195671-1168113352 -C 1800 -M 900  /tmp/evaluation/195671-1168113352/tramontane/bin/solver /tmp/evaluation/195671-1168113352/unknown.xml -res geom -f 3 -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  7d2754cc44d2423629dbe49c143cee41

RANDOM SEED= 715546204

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.277
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.277
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:       1552304 kB
Buffers:         40656 kB
Cached:         373872 kB
SwapCached:          0 kB
Active:          89128 kB
Inactive:       346508 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1552304 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            5940 kB
Writeback:           0 kB
Mapped:          34000 kB
Slab:            53624 kB
Committed_AS:  3193080 kB
PageTables:       1712 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= 66543 MiB



End job on node51 on Sat Jan  6 19:55:54 UTC 2007