Trace number 207615

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 8.36573 8.44233

General information on the benchmark

Namefapp/test01-04/test01/
test01-0150-10.xml
MD5SUMca801d693e5f281aecf2d953ed79f03d
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.918859
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.20	c 
0.20	c Parsing xml file
0.20	c 	domains............... 0.02
0.20	c 	variables.............    0
0.20	c 	predicates............    0
0.20	c 	constraints...........  0.1
0.20	c Allocating memory
0.20	c 
0.20	c time limit = -1
0.20	c heuristic = dom/wdeg
0.20	c restart policy = Geometric increment
0.20	c restart base = 99
0.20	c restart factor = 1.33
0.20	c 
0.20	c Solving
0.20	c
8.43	s SATISFIABLE
8.43	v -2692 2320 2520 2300 2508 2192 2140 2424 2676 -2680 2172 -2620 2332 2680 2160 -2464 -2248 -2636 -2648 2652 2676 2656 -2448 2668 -2436 -2412 -2648 2424 -2660 -2612 2240 -2644 -2640 -2696 2628 2552 -2180 2240 2468 2320 2540 2576 2696 2360 -2328 2200 2520 2148 -2720 -2552 -2644 2488 -2700 -2232 -2344 2280 -2656 -2272 2384 2688 -2536 2640 2616 -2208 2648 2604 2476 -2700 2120 -2340 -2660 2660 -2656 -2656 2660 -2300 2484 -2400 -2700 -2200 -2528 2696 -2516 -2440 -2512 -2400 -2372 -2212 2628 2400 2680 -2592 2696 2572 2360 -2624 2208 -2232 2444 -2568 -2260 2636 2400 2680 -2480 2700 -2436 -2168 -2644 2580 2700 -2220 -2608 2252 2144 2588 -2148 2700 2292 2476 -2368 -2584 -2684 2660 2180 2668 -2292 2628 2684 2660 2440 2252 2500 2636 2188 2640 -2252 -2676 2688 2476 -2212 -2372 -2464 2660 2184 -2480 2700 -2188 -2440 2656
8.43	d          SAT       573 BTS       8.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/node30/watcher-207615-1168182514 -o ROOT/results/node30/solver-207615-1168182514 -C 1800 -M 900 /tmp/evaluation/207615-1168182514/tramontane/bin/solver /tmp/evaluation/207615-1168182514/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.98 1.81 1.76 3/94 3007
/proc/meminfo: memFree=1292112/2055920 swapFree=4191880/4192956
[pid=3006] ppid=3004 vsize=540 CPUtime=0
/proc/3006/stat : 3006 (solver) R 3004 3006 2360 0 -1 4194304 41 0 0 0 0 0 0 0 21 0 1 0 166645448 552960 26 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 7016747 0 0 4096 0 0 0 0 17 1 0 0
/proc/3006/statm: 135 26 21 92 0 18 0

[startup+0.102916 s]
/proc/loadavg: 1.98 1.81 1.76 3/94 3007
/proc/meminfo: memFree=1292112/2055920 swapFree=4191880/4192956
[pid=3006] ppid=3004 vsize=13748 CPUtime=0.08
/proc/3006/stat : 3006 (solver) R 3004 3006 2360 0 -1 4194304 1503 0 0 0 8 0 0 0 18 0 1 0 166645448 14077952 1471 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 7450404 0 0 4096 0 0 0 0 17 1 0 0
/proc/3006/statm: 3437 1471 708 92 0 1781 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 13748

[startup+0.510938 s]
/proc/loadavg: 1.98 1.81 1.76 3/94 3007
/proc/meminfo: memFree=1292112/2055920 swapFree=4191880/4192956
[pid=3006] ppid=3004 vsize=14276 CPUtime=0.49
/proc/3006/stat : 3006 (solver) R 3004 3006 2360 0 -1 4194304 1646 0 0 0 49 0 0 0 22 0 1 0 166645448 14618624 1614 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 134812848 0 0 4096 0 0 0 0 17 1 0 0
/proc/3006/statm: 3569 1614 719 92 0 1913 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 14276

[startup+1.33199 s]
/proc/loadavg: 1.98 1.81 1.76 3/94 3007
/proc/meminfo: memFree=1288464/2055920 swapFree=4191880/4192956
[pid=3006] ppid=3004 vsize=14276 CPUtime=1.3
/proc/3006/stat : 3006 (solver) R 3004 3006 2360 0 -1 4194304 1646 0 0 0 130 0 0 0 25 0 1 0 166645448 14618624 1614 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 134710305 0 0 4096 0 0 0 0 17 1 0 0
/proc/3006/statm: 3569 1614 719 92 0 1913 0
Current children cumulated CPU time (s) 1.3
Current children cumulated vsize (KiB) 14276

[startup+2.96909 s]
/proc/loadavg: 1.98 1.81 1.76 3/94 3007
/proc/meminfo: memFree=1288400/2055920 swapFree=4191880/4192956
[pid=3006] ppid=3004 vsize=14280 CPUtime=2.93
/proc/3006/stat : 3006 (solver) R 3004 3006 2360 0 -1 4194304 1647 0 0 0 292 1 0 0 25 0 1 0 166645448 14622720 1615 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 134709344 0 0 4096 0 0 0 0 17 1 0 0
/proc/3006/statm: 3570 1615 719 92 0 1914 0
Current children cumulated CPU time (s) 2.93
Current children cumulated vsize (KiB) 14280

[startup+6.2483 s]
/proc/loadavg: 1.98 1.81 1.76 3/94 3007
/proc/meminfo: memFree=1288400/2055920 swapFree=4191880/4192956
[pid=3006] ppid=3004 vsize=14280 CPUtime=6.18
/proc/3006/stat : 3006 (solver) R 3004 3006 2360 0 -1 4194304 1647 0 0 0 617 1 0 0 25 0 1 0 166645448 14622720 1615 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 134812960 0 0 4096 0 0 0 0 17 1 0 0
/proc/3006/statm: 3570 1615 719 92 0 1914 0
Current children cumulated CPU time (s) 6.18
Current children cumulated vsize (KiB) 14280

Child status: 0
Real time (s): 8.44233
CPU time (s): 8.36573
CPU user time (s): 8.34973
CPU system time (s): 0.015997
CPU usage (%): 99.0926
Max. virtual memory (cumulated for all children) (KiB): 14280

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 8.34973
system time used= 0.015997
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= 342

runsolver used 0.014997 s user time and 0.025996 s system time

The end

Launcher Data (download as text)

Begin job on node30 on Sun Jan  7 15:08:34 UTC 2007


IDJOB= 207615
IDBENCH= 4301
FILE ID= node30/207615-1168182514

PBS_JOBID= 3479172

Free space on /tmp= 66485 MiB

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

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  ca801d693e5f281aecf2d953ed79f03d

RANDOM SEED= 708629276

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.234
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.234
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:       1292592 kB
Buffers:         37928 kB
Cached:         201028 kB
SwapCached:        268 kB
Active:         550196 kB
Inactive:       142928 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1292592 kB
SwapTotal:     4192956 kB
SwapFree:      4191880 kB
Dirty:            3480 kB
Writeback:           0 kB
Mapped:         479792 kB
Slab:            54108 kB
Committed_AS:  4120916 kB
PageTables:       3080 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= 66485 MiB



End job on node30 on Sun Jan  7 15:08:44 UTC 2007