Trace number 207599

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 2.36264 2.37671

General information on the benchmark

Namefapp/test01-04/test01/
test01-0150-5.xml
MD5SUM46eec35b13530df24328b94610022319
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.78288
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables150
Number of constraints1460
Maximum constraint arity2
Maximum domain size302
Number of constraints which are defined in extension0
Number of constraints which are defined in intension1460
Global constraints used (with number of constraints)

Solver Data (download as text)

0.01	c 
0.01	c Parsing xml file
0.01	c 	domains............... 0.02
0.02	c 	variables.............    0
0.03	c 	predicates............    0
0.03	c 	constraints...........  0.1
0.13	c Allocating memory
0.13	c 
0.13	c time limit = -1
0.13	c heuristic = dom/wdeg
0.13	c restart policy = Geometric increment
0.13	c restart base = 99
0.13	c restart factor = 1.33
0.13	c 
0.13	c Solving
0.13	c
2.37	s SATISFIABLE
2.37	v 2620 -2720 2540 -2300 -2508 2536 -2160 2416 -2700 -2672 2548 -2612 -2228 -2600 2120 -2232 -2556 -2660 -2140 -2660 -2700 -2700 2408 -2700 -2148 -2228 -2584 -2192 2676 -2624 -2144 -2592 -2632 -2660 -2620 -2560 2200 -2264 2468 -2224 -2560 -2584 -2660 -2184 2120 2304 -2452 -2192 2640 2468 -2660 2448 2564 -2576 -2356 -2680 -2700 -2260 -2316 -2180 2544 -2628 -2688 -2388 -2700 2632 2188 -2700 2160 2260 -2612 -2660 2620 -2648 -2660 -2268 2412 2184 -2572 2184 -2420 -2660 2228 -2224 -2508 -2552 -2268 -2588 2644 2528 -2668 -2600 -2660 -2584 -2488 -2560 2516 -2220 2452 2380 2308 -2660 -2604 -2664 -2412 -2700 2468 -2348 -2628 2572 2636 2208 -2544 2448 2140 -2604 -2324 -2660 2488 2188 2160 2600 -2700 -2700 -2248 -2580 -2248 -2660 -2668 -2668 2644 -2208 2520 -2660 -2152 -2624 2172 -2700 2660 2428 -2132 -2268 2376 -2604 -2180 2500 -2628 2364 -2592 -2700
2.37	d          SAT         4 BTS       2.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/node4/watcher-207599-1168182473 -o ROOT/results/node4/solver-207599-1168182473 -C 1800 -M 900 /tmp/evaluation/207599-1168182473/tramontane/bin/solver /tmp/evaluation/207599-1168182473/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.90 2.01 1.99 5/94 19928
/proc/meminfo: memFree=1302192/2055920 swapFree=4182144/4192956
[pid=19927] ppid=19925 vsize=6792 CPUtime=0
/proc/19927/stat : 19927 (solver) R 19925 19927 19612 0 -1 4194304 433 0 0 0 0 0 0 0 18 0 1 0 166643050 6955008 412 18446744073709551615 134512640 134893233 4294956640 18446744073709551615 10558328 0 0 4096 0 0 0 0 17 0 0 0
/proc/19927/statm: 1698 412 373 92 0 30 0

[startup+0.108739 s]
/proc/loadavg: 1.90 2.01 1.99 5/94 19928
/proc/meminfo: memFree=1302192/2055920 swapFree=4182144/4192956
[pid=19927] ppid=19925 vsize=13880 CPUtime=0.09
/proc/19927/stat : 19927 (solver) R 19925 19927 19612 0 -1 4194304 1524 0 0 0 9 0 0 0 18 0 1 0 166643050 14213120 1492 18446744073709551615 134512640 134893233 4294956640 18446744073709551615 134560558 0 0 4096 0 0 0 0 17 0 0 0
/proc/19927/statm: 3470 1493 708 92 0 1814 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 13880

[startup+0.519774 s]
/proc/loadavg: 1.90 2.01 1.99 5/94 19928
/proc/meminfo: memFree=1302192/2055920 swapFree=4182144/4192956
[pid=19927] ppid=19925 vsize=14276 CPUtime=0.5
/proc/19927/stat : 19927 (solver) R 19925 19927 19612 0 -1 4194304 1646 0 0 0 50 0 0 0 22 0 1 0 166643050 14618624 1614 18446744073709551615 134512640 134893233 4294956640 18446744073709551615 134722065 0 0 4096 0 0 0 0 17 0 0 0
/proc/19927/statm: 3569 1614 719 92 0 1913 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 14276

[startup+1.34085 s]
/proc/loadavg: 1.90 2.01 1.99 3/94 19928
/proc/meminfo: memFree=1298544/2055920 swapFree=4182144/4192956
[pid=19927] ppid=19925 vsize=14276 CPUtime=1.32
/proc/19927/stat : 19927 (solver) R 19925 19927 19612 0 -1 4194304 1646 0 0 0 132 0 0 0 25 0 1 0 166643050 14618624 1614 18446744073709551615 134512640 134893233 4294956640 18446744073709551615 134712081 0 0 4096 0 0 0 0 17 0 0 0
/proc/19927/statm: 3569 1614 719 92 0 1913 0
Current children cumulated CPU time (s) 1.32
Current children cumulated vsize (KiB) 14276

Child status: 0
Real time (s): 2.37671
CPU time (s): 2.36264
CPU user time (s): 2.35264
CPU system time (s): 0.009998
CPU usage (%): 99.4078
Max. virtual memory (cumulated for all children) (KiB): 14280

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 2.35264
system time used= 0.009998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1655
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= 146

runsolver used 0.002999 s user time and 0.016997 s system time

The end

Launcher Data (download as text)

Begin job on node4 on Sun Jan  7 15:07:55 UTC 2007


IDJOB= 207599
IDBENCH= 4300
FILE ID= node4/207599-1168182473

PBS_JOBID= 3478921

Free space on /tmp= 66301 MiB

BENCH NAME= HOME/pub/bench/CPAI06/fapp/test01-04/test01/test01-0150-5.xml
COMMAND LINE= /tmp/evaluation/207599-1168182473/tramontane/bin/solver /tmp/evaluation/207599-1168182473/unknown.xml -res geom -f 3 -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node4/watcher-207599-1168182473 -o ROOT/results/node4/solver-207599-1168182473 -C 1800 -M 900  /tmp/evaluation/207599-1168182473/tramontane/bin/solver /tmp/evaluation/207599-1168182473/unknown.xml -res geom -f 3 -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  46eec35b13530df24328b94610022319

RANDOM SEED= 151966990

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.223
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.223
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:       1302672 kB
Buffers:         49640 kB
Cached:         255540 kB
SwapCached:       2520 kB
Active:         490976 kB
Inactive:       208032 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1302672 kB
SwapTotal:     4192956 kB
SwapFree:      4182144 kB
Dirty:            3428 kB
Writeback:           0 kB
Mapped:         412256 kB
Slab:            38160 kB
Committed_AS:  5057844 kB
PageTables:       3200 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= 66301 MiB



End job on node4 on Sun Jan  7 15:07:58 UTC 2007