Trace number 207727

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.27365 2.30881

General information on the benchmark

Namefapp/test01-04/test01/
test01-0150-8.xml
MD5SUMc3f7208494f1f464cbff75e34a96bcfc
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.867867
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.13	c 
0.13	c Parsing xml file
0.13	c 	domains............... 0.03
0.13	c 	variables.............    0
0.13	c 	predicates............    0
0.13	c 	constraints........... 0.11
0.15	c Allocating memory
0.15	c 
0.15	c time limit = -1
0.15	c heuristic = dom/wdeg
0.15	c restart policy = Geometric increment
0.15	c restart base = 99
0.15	c restart factor = 1.33
0.15	c 
0.15	c Solving
0.15	c
2.30	s SATISFIABLE
2.30	v -2640 -2720 -2476 -2284 -2504 -2636 -2192 -2472 -2700 -2676 2560 -2632 -2228 -2596 -2160 -2396 -2552 -2628 2136 -2680 -2668 -2700 -2452 -2656 2272 2304 2484 -2356 2660 -2568 -2208 -2624 -2636 -2656 -2600 -2544 2232 -2240 -2544 -2232 2120 -2528 -2660 2192 2160 2200 -2400 -2188 2636 -2464 -2700 -2412 2644 2596 -2380 2680 -2700 -2228 -2420 -2176 -2488 -2688 2688 -2340 -2688 2584 -2312 -2700 -2120 2244 -2664 -2660 -2696 -2648 -2660 -2360 2444 2220 -2624 2168 2312 -2636 -2272 -2260 -2504 -2644 -2268 -2520 -2584 2536 -2648 -2584 -2660 -2608 -2496 2592 2512 -2188 -2484 2272 2320 -2660 2604 -2652 2440 -2700 2436 -2380 -2628 -2592 2700 -2300 -2524 -2700 -2180 -2624 2400 -2684 -2660 -2312 2120 2552 2660 -2644 -2260 -2560 2192 -2696 -2668 -2688 -2644 -2232 -2160 -2660 2148 -2612 -2256 -2700 -2648 -2396 2216 -2264 -2432 -2684 -2140 2436 -2648 -2440 -2604 -2676
2.30	d          SAT         0 BTS       2.1 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/node18/watcher-207727-1168183021 -o ROOT/results/node18/solver-207727-1168183021 -C 1800 -M 900 /tmp/evaluation/207727-1168183021/tramontane/bin/solver /tmp/evaluation/207727-1168183021/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.92 1.99 2.06 5/94 29591
/proc/meminfo: memFree=1103376/2055920 swapFree=4192812/4192956
[pid=29590] ppid=29588 vsize=18540 CPUtime=0
/proc/29590/stat : 29590 (runsolver) R 29588 29590 27759 0 -1 4194368 16 0 0 0 0 0 0 0 20 0 1 0 166697030 18984960 279 18446744073709551615 4194304 4267372 548682068992 18446744073709551615 227848809767 0 0 4096 24578 0 0 0 17 1 0 0
/proc/29590/statm: 4635 279 244 17 0 2626 0

[startup+0.109185 s]
/proc/loadavg: 1.92 1.99 2.06 5/94 29591
/proc/meminfo: memFree=1103376/2055920 swapFree=4192812/4192956
[pid=29590] ppid=29588 vsize=13748 CPUtime=0.09
/proc/29590/stat : 29590 (solver) R 29588 29590 27759 0 -1 4194304 1497 0 0 0 9 0 0 0 18 0 1 0 166697030 14077952 1465 18446744073709551615 134512640 134893233 4294956640 18446744073709551615 7997031 0 0 4096 0 0 0 0 17 1 0 0
/proc/29590/statm: 3437 1465 708 92 0 1781 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 13748

[startup+0.521214 s]
/proc/loadavg: 1.92 1.99 2.06 5/94 29591
/proc/meminfo: memFree=1103376/2055920 swapFree=4192812/4192956
[pid=29590] ppid=29588 vsize=14276 CPUtime=0.5
/proc/29590/stat : 29590 (solver) R 29588 29590 27759 0 -1 4194304 1646 0 0 0 50 0 0 0 21 0 1 0 166697030 14618624 1614 18446744073709551615 134512640 134893233 4294956640 18446744073709551615 134722064 0 0 4096 0 0 0 0 17 1 0 0
/proc/29590/statm: 3569 1614 719 92 0 1913 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 14276

[startup+1.3463 s]
/proc/loadavg: 1.93 1.99 2.06 3/94 29591
/proc/meminfo: memFree=1097040/2055920 swapFree=4192812/4192956
[pid=29590] ppid=29588 vsize=14276 CPUtime=1.31
/proc/29590/stat : 29590 (solver) R 29588 29590 27759 0 -1 4194304 1646 0 0 0 131 0 0 0 25 0 1 0 166697030 14618624 1614 18446744073709551615 134512640 134893233 4294956640 18446744073709551615 134710345 0 0 4096 0 0 0 0 17 1 0 0
/proc/29590/statm: 3569 1614 719 92 0 1913 0
Current children cumulated CPU time (s) 1.31
Current children cumulated vsize (KiB) 14276

Child status: 0
Real time (s): 2.30881
CPU time (s): 2.27365
CPU user time (s): 2.26766
CPU system time (s): 0.005999
CPU usage (%): 98.4772
Max. virtual memory (cumulated for all children) (KiB): 14276

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 2.26765
system time used= 0.005999
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= 13
involuntary context switches= 112

runsolver used 0.004999 s user time and 0.016997 s system time

The end

Launcher Data (download as text)

Begin job on node18 on Sun Jan  7 15:17:03 UTC 2007


IDJOB= 207727
IDBENCH= 4308
FILE ID= node18/207727-1168183021

PBS_JOBID= 3478869

Free space on /tmp= 66284 MiB

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

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  c3f7208494f1f464cbff75e34a96bcfc

RANDOM SEED= 106187152

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.231
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.231
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:       1104944 kB
Buffers:         33336 kB
Cached:         192356 kB
SwapCached:          0 kB
Active:         742920 kB
Inactive:       148144 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1104944 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            3248 kB
Writeback:           0 kB
Mapped:         693256 kB
Slab:            43536 kB
Committed_AS:  5357032 kB
PageTables:       3356 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= 66284 MiB



End job on node18 on Sun Jan  7 15:17:07 UTC 2007