Trace number 209069

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 1.39079 1.43607

General information on the benchmark

Namefapp/fapp01-05/fapp01/
fapp01-0200-10.xml
MD5SUM77e758121f45352fcd7f4ff036be2f28
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 benchmark1.36879
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables200
Number of constraints2053
Maximum constraint arity2
Maximum domain size190
Number of constraints which are defined in extension0
Number of constraints which are defined in intension2053
Global constraints used (with number of constraints)

Solver Data (download as text)

0.11	c 
0.11	c Parsing xml file
0.11	c 	domains...............    0
0.11	c 	variables.............    0
0.11	c 	predicates............    0
0.11	c 	constraints........... 0.14
0.18	c Allocating memory
0.18	c 
0.18	c time limit = -1
0.18	c heuristic = dom/wdeg
0.18	c restart policy = Geometric increment
0.18	c restart base = 133
0.18	c restart factor = 1.33
0.18	c 
0.18	c Solving
0.18	c
1.42	s SATISFIABLE
1.42	v -2600 -2424 2656 -2304 2372 -2512 -2420 -2492 -2428 -2296 -2336 2560 2468 2376 -2532 2592 2620 -2492 -2300 -2652 -2640 -2540 2288 -2552 -2400 -2568 2560 -2648 2596 2336 -2600 -2472 -2340 -2424 -2500 -2532 -2640 2572 -2440 -2324 2480 -2340 -2480 2468 -2368 -2584 -2516 2632 -2528 -2320 -2496 -2656 -2460 -2488 -2320 2332 2416 2488 -2492 2360 -2512 2400 -2464 -2548 2528 -2492 -2468 -2536 -2612 -2416 -2580 -2448 -2600 -2492 -2368 2640 2376 -2600 -2600 2280 2400 2280 2280 2448 -2528 2584 -2564 2360 2284 -2640 2364 -2480 -2532 -2492 -2504 2520 -2532 -2512 -2488 -2616 2440 2600 -2560 -2548 -2552 -2512 2280 -2524 -2448 -2596 -2500 2320 -2456 -2300 2384 -2552 -2424 -2596 2496 -2656 -2464 2508 2520 -2372 -2348 -2340 -2448 2380 2396 -2488 -2588 2640 -2460 -2408 -2308 -2508 -2640 -2408 -2620 2584 -2300 -2656 2508 -2328 2460 2472 2340 -2328 -2452 -2356 2592 2520 -2612 -2420 2332 -2408 -2580 2424 -2520 -2624 -2456 -2292 -2556 -2376 2556 -2628 2532 -2420 -2636 2400 2392 -2616 -2404 -2464 -2336 2432 -2512 -2456 2392 -2420 -2624 -2440 -2616 -2332 -2368 -2608 2552 2320 2344 -2380 -2460 -2352 -2556 2600 2544 -2616 -2416 2464 -2328 -2508
1.42	d          SAT         0 BTS       1.2 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/node26/watcher-209069-1168191464 -o ROOT/results/node26/solver-209069-1168191464 -C 1800 -M 900 /tmp/evaluation/209069-1168191464/tramontane/bin/solver /tmp/evaluation/209069-1168191464/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: 2.68 2.77 2.44 5/94 25256
/proc/meminfo: memFree=926872/2055920 swapFree=4192812/4192956
[pid=25255] ppid=25253 vsize=540 CPUtime=0
/proc/25255/stat : 25255 (solver) R 25253 25255 24765 0 -1 4194304 41 0 0 0 0 0 0 0 20 0 1 0 167540774 552960 26 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 12591908 0 2147483391 4096 0 0 0 0 17 1 0 0
/proc/25255/statm: 135 26 21 92 0 18 0

[startup+0.1036 s]
/proc/loadavg: 2.68 2.77 2.44 5/94 25256
/proc/meminfo: memFree=926872/2055920 swapFree=4192812/4192956
[pid=25255] ppid=25253 vsize=15724 CPUtime=0.08
/proc/25255/stat : 25255 (solver) R 25253 25255 24765 0 -1 4194304 1588 0 0 0 8 0 0 0 20 0 1 0 167540774 16101376 1556 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 134575848 0 0 4096 0 0 0 0 17 1 0 0
/proc/25255/statm: 3931 1556 706 92 0 2275 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 15724

[startup+0.511636 s]
/proc/loadavg: 2.68 2.77 2.44 5/94 25256
/proc/meminfo: memFree=926872/2055920 swapFree=4192812/4192956
[pid=25255] ppid=25253 vsize=16516 CPUtime=0.49
/proc/25255/stat : 25255 (solver) R 25253 25255 24765 0 -1 4194304 1819 0 0 0 49 0 0 0 25 0 1 0 167540774 16912384 1787 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 134722065 0 0 4096 0 0 0 0 17 1 0 0
/proc/25255/statm: 4129 1787 719 92 0 2473 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 16516

[startup+1.33271 s]
/proc/loadavg: 2.68 2.77 2.44 4/94 25256
/proc/meminfo: memFree=922392/2055920 swapFree=4192812/4192956
[pid=25255] ppid=25253 vsize=16516 CPUtime=1.27
/proc/25255/stat : 25255 (solver) R 25253 25255 24765 0 -1 4194304 1819 0 0 0 127 0 0 0 25 0 1 0 167540774 16912384 1787 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 134722065 0 0 4096 0 0 0 0 17 1 0 0
/proc/25255/statm: 4129 1787 719 92 0 2473 0
Current children cumulated CPU time (s) 1.27
Current children cumulated vsize (KiB) 16516

Child status: 0
Real time (s): 1.43607
CPU time (s): 1.39079
CPU user time (s): 1.37979
CPU system time (s): 0.010998
CPU usage (%): 96.8467
Max. virtual memory (cumulated for all children) (KiB): 16516

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 1.37979
system time used= 0.010998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1828
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= 13
involuntary context switches= 83

runsolver used 0.002999 s user time and 0.010998 s system time

The end

Launcher Data (download as text)

Begin job on node26 on Sun Jan  7 17:37:45 UTC 2007


IDJOB= 209069
IDBENCH= 4493
FILE ID= node26/209069-1168191464

PBS_JOBID= 3479263

Free space on /tmp= 66528 MiB

BENCH NAME= HOME/pub/bench/CPAI06/fapp/fapp01-05/fapp01/fapp01-0200-10.xml
COMMAND LINE= /tmp/evaluation/209069-1168191464/tramontane/bin/solver /tmp/evaluation/209069-1168191464/unknown.xml -res geom -f 3 -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node26/watcher-209069-1168191464 -o ROOT/results/node26/solver-209069-1168191464 -C 1800 -M 900  /tmp/evaluation/209069-1168191464/tramontane/bin/solver /tmp/evaluation/209069-1168191464/unknown.xml -res geom -f 3 -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  77e758121f45352fcd7f4ff036be2f28

RANDOM SEED= 949675656

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:        927288 kB
Buffers:         51824 kB
Cached:         348016 kB
SwapCached:          0 kB
Active:         763568 kB
Inactive:       301580 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        927288 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            3352 kB
Writeback:           0 kB
Mapped:         690848 kB
Slab:            47016 kB
Committed_AS:  3894928 kB
PageTables:       3508 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= 66528 MiB



End job on node26 on Sun Jan  7 17:37:47 UTC 2007