Trace number 207631

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.30865 2.32914

General information on the benchmark

Namefapp/test01-04/test01/
test01-0150-4.xml
MD5SUM608f318ddc1268ddf2e7f96ac3631c9f
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.801877
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.31	s SATISFIABLE
2.31	v 2620 -2720 2456 -2308 2412 -2636 2148 -2376 -2700 -2672 2544 2636 -2228 -2568 -2120 -2188 -2580 -2660 2120 -2660 -2700 -2700 2380 -2700 -2144 -2236 -2524 -2228 -2656 2596 2140 -2628 2632 -2660 -2612 -2560 2188 -2196 2452 -2204 2496 -2568 -2660 -2244 -2188 2236 -2440 2188 2608 -2472 -2660 -2420 2584 -2596 2296 -2680 -2700 -2240 -2336 -2160 -2528 -2628 2648 -2388 -2700 2588 -2184 -2700 2160 2268 -2660 -2660 2620 -2688 -2660 -2264 2360 -2172 2700 2180 -2420 -2660 2224 -2132 -2512 2392 -2268 -2584 2644 2500 -2668 -2520 -2660 -2556 -2460 -2556 2540 -2200 2400 2380 -2224 -2660 2596 -2660 2400 -2700 -2460 -2348 -2628 -2596 2616 -2264 2564 2336 -2140 -2604 2332 -2660 2296 -2184 2148 -2516 -2700 -2700 -2224 2572 -2256 -2660 -2668 -2664 2636 -2216 2456 -2660 -2148 -2620 -2176 -2700 2660 2420 2136 -2276 2416 2624 2180 2496 -2624 2372 2352 -2700
2.31	d          SAT         0 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/node58/watcher-207631-1168182564 -o ROOT/results/node58/solver-207631-1168182564 -C 1800 -M 900 /tmp/evaluation/207631-1168182564/tramontane/bin/solver /tmp/evaluation/207631-1168182564/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.29 1.07 1.03 4/70 26108
/proc/meminfo: memFree=1387464/2055920 swapFree=4192812/4192956
[pid=26107] ppid=26105 vsize=6792 CPUtime=0
/proc/26107/stat : 26107 (solver) R 26105 26107 25494 0 -1 4194304 432 0 0 0 0 0 0 0 18 0 1 0 166654426 6955008 411 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 4840312 0 0 4096 0 0 0 0 17 0 0 0
/proc/26107/statm: 1698 412 373 92 0 30 0

[startup+0.104413 s]
/proc/loadavg: 1.29 1.07 1.03 4/70 26108
/proc/meminfo: memFree=1387464/2055920 swapFree=4192812/4192956
[pid=26107] ppid=26105 vsize=13880 CPUtime=0.09
/proc/26107/stat : 26107 (solver) R 26105 26107 25494 0 -1 4194304 1522 0 0 0 9 0 0 0 19 0 1 0 166654426 14213120 1490 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 134572505 0 0 4096 0 0 0 0 17 0 0 0
/proc/26107/statm: 3470 1490 708 92 0 1814 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 13880

[startup+0.512443 s]
/proc/loadavg: 1.29 1.07 1.03 4/70 26108
/proc/meminfo: memFree=1387464/2055920 swapFree=4192812/4192956
[pid=26107] ppid=26105 vsize=14276 CPUtime=0.49
/proc/26107/stat : 26107 (solver) R 26105 26107 25494 0 -1 4194304 1646 0 0 0 49 0 0 0 22 0 1 0 166654426 14618624 1614 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 134710305 0 0 4096 0 0 0 0 17 1 0 0
/proc/26107/statm: 3569 1614 719 92 0 1913 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 14276

[startup+1.33251 s]
/proc/loadavg: 1.26 1.07 1.03 2/68 26111
/proc/meminfo: memFree=1387544/2055920 swapFree=4192812/4192956
[pid=26107] ppid=26105 vsize=14276 CPUtime=1.31
/proc/26107/stat : 26107 (solver) R 26105 26107 25494 0 -1 4194304 1646 0 0 0 131 0 0 0 25 0 1 0 166654426 14618624 1614 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 134722073 0 0 4096 0 0 0 0 17 0 0 0
/proc/26107/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.32914
CPU time (s): 2.30865
CPU user time (s): 2.29765
CPU system time (s): 0.010998
CPU usage (%): 99.1202
Max. virtual memory (cumulated for all children) (KiB): 14276

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 2.29765
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= 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= 11
involuntary context switches= 82

runsolver used 0.002999 s user time and 0.014997 s system time

The end

Launcher Data (download as text)

Begin job on node58 on Sun Jan  7 15:09:25 UTC 2007


IDJOB= 207631
IDBENCH= 4302
FILE ID= node58/207631-1168182564

PBS_JOBID= 3479185

Free space on /tmp= 66551 MiB

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

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  608f318ddc1268ddf2e7f96ac3631c9f

RANDOM SEED= 168444603

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:       1388256 kB
Buffers:         39200 kB
Cached:         540772 kB
SwapCached:          0 kB
Active:          90516 kB
Inactive:       509984 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1388256 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            6848 kB
Writeback:           0 kB
Mapped:          30772 kB
Slab:            52812 kB
Committed_AS:  2642568 kB
PageTables:       1672 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= 66554 MiB



End job on node58 on Sun Jan  7 15:09:27 UTC 2007