Trace number 216775

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 0.266959 0.280257

General information on the benchmark

Namerlfap/rlfapScensMod/
scen2-f24.xml
MD5SUM5c81ef8039e928ad204d17c019cf929c
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.252961
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables200
Number of constraints1235
Maximum constraint arity2
Maximum domain size22
Number of constraints which are defined in extension0
Number of constraints which are defined in intension1235
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.07
0.11	c Allocating memory
0.11	c 
0.11	c time limit = -1
0.11	c heuristic = dom/wdeg
0.11	c restart policy = Geometric increment
0.11	c restart base = 133
0.11	c restart factor = 1.33
0.11	c 
0.11	c Solving
0.11	c
0.22	s SATISFIABLE
0.22	v 114 352 114 352 268 30 254 16 268 30 324 86 254 16 254 16 352 114 156 394 156 394 296 58 142 380 282 44 338 100 254 16 394 156 254 16 324 86 254 16 254 16 338 100 338 100 254 16 100 338 100 338 44 282 86 324 16 254 352 114 86 324 156 394 16 254 366 128 16 254 352 114 352 114 366 128 114 352 30 268 58 296 44 282 268 30 268 30 58 296 44 282 100 338 58 296 268 30 72 310 324 86 72 310 44 282 254 16 16 254 30 268 114 352 282 44 100 338 142 380 352 114 268 30 44 282 380 142 142 380 282 44 268 30 366 128 100 338 44 282 30 268 44 282 366 128 156 394 30 268 254 16 16 254 366 128 16 254 254 16 338 100 268 30 86 324 156 394 44 282 366 128 268 30 114 352 44 282 16 254 58 296 86 324 268 30 100 338 30 268 100 338 30 268 142 380 282 44 30 268
0.22	d          SAT        25 BTS      0.03 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/node56/watcher-216775-1168243966 -o ROOT/results/node56/solver-216775-1168243966 -C 1800 -M 900 /tmp/evaluation/216775-1168243966/tramontane/bin/solver /tmp/evaluation/216775-1168243966/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: 0.63 0.88 0.96 5/81 26717
/proc/meminfo: memFree=1842576/2055920 swapFree=4184772/4192956
[pid=26716] ppid=26714 vsize=18540 CPUtime=0
/proc/26716/stat : 26716 (runsolver) R 26714 26716 25837 0 -1 4194368 16 0 0 0 0 0 0 0 18 0 1 0 172794864 18984960 279 18446744073709551615 4194304 4267372 548682068992 18446744073709551615 253307186471 0 0 4096 24578 0 0 0 17 1 0 0
/proc/26716/statm: 4635 279 244 17 0 2626 0

[startup+0.10353 s]
/proc/loadavg: 0.63 0.88 0.96 5/81 26717
/proc/meminfo: memFree=1842576/2055920 swapFree=4184772/4192956
[pid=26716] ppid=26714 vsize=9952 CPUtime=0.09
/proc/26716/stat : 26716 (solver) R 26714 26716 25837 0 -1 4194304 1594 0 0 0 9 0 0 0 18 0 1 0 172794864 10190848 1562 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 10461696 0 0 4096 0 0 0 0 17 0 0 0
/proc/26716/statm: 2488 1562 716 92 0 832 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 9952

Child status: 0
Real time (s): 0.280257
CPU time (s): 0.266959
CPU user time (s): 0.242963
CPU system time (s): 0.023996
CPU usage (%): 95.2551
Max. virtual memory (cumulated for all children) (KiB): 25792

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

runsolver used 0.000999 s user time and 0.006998 s system time

The end

Launcher Data (download as text)

Begin job on node56 on Mon Jan  8 08:12:47 UTC 2007


IDJOB= 216775
IDBENCH= 5100
FILE ID= node56/216775-1168243966

PBS_JOBID= 3481800

Free space on /tmp= 66555 MiB

BENCH NAME= HOME/pub/bench/CPAI06/rlfap/rlfapScensMod/scen2-f24.xml
COMMAND LINE= /tmp/evaluation/216775-1168243966/tramontane/bin/solver /tmp/evaluation/216775-1168243966/unknown.xml -res geom -f 3 -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node56/watcher-216775-1168243966 -o ROOT/results/node56/solver-216775-1168243966 -C 1800 -M 900  /tmp/evaluation/216775-1168243966/tramontane/bin/solver /tmp/evaluation/216775-1168243966/unknown.xml -res geom -f 3 -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  5c81ef8039e928ad204d17c019cf929c

RANDOM SEED= 766549551

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.232
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.232
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:       1843056 kB
Buffers:          8640 kB
Cached:          68736 kB
SwapCached:       2048 kB
Active:         138508 kB
Inactive:        23344 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1843056 kB
SwapTotal:     4192956 kB
SwapFree:      4184772 kB
Dirty:            7616 kB
Writeback:           0 kB
Mapped:         100300 kB
Slab:            36108 kB
Committed_AS:  4281296 kB
PageTables:       2112 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= 66555 MiB



End job on node56 on Mon Jan  8 08:12:48 UTC 2007