Trace number 216614

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
Mistral 2006-12-04SAT 0.151976 0.160343

General information on the benchmark

Namerlfap/rlfapScensMod/
scen6-w1.xml
MD5SUMe4761551e00079c0c6c5437557356554
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.148977
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables200
Number of constraints319
Maximum constraint arity2
Maximum domain size44
Number of constraints which are defined in extension0
Number of constraints which are defined in intension319
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.02
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 = No restart
0.11	c 
0.11	c Solving
0.11	c
0.12	s SATISFIABLE
0.12	v 16 254 428 666 16 254 16 254 254 16 16 254 414 652 100 338 324 86 16 254 114 352 750 512 30 268 16 254 254 16 708 470 254 16 722 484 652 414 16 254 498 736 442 680 254 16 30 268 254 16 254 16 254 16 16 254 414 652 764 526 414 652 30 268 254 16 16 254 414 652 792 554 16 254 254 16 750 512 282 44 268 30 428 666 16 254 30 268 470 708 268 30 30 268 540 778 694 456 268 30 310 72 254 16 498 736 254 16 414 652 254 16 268 30 512 750 30 268 268 30 268 30 540 778 30 268 268 30 428 666 86 324 512 750 324 86 30 268 428 666 428 666 30 268 442 680 30 268 254 16 16 254 296 58 16 254 694 456 512 750 652 414 722 484 778 540 254 16 30 268 764 526 694 456 666 428 16 254 16 254 86 324 428 666 736 498 30 268 30 268 666 428 30 268 428 666 100 338 30 268
0.12	d          SAT         0 BTS      0.02 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/node20/watcher-216614-1168243590 -o ROOT/results/node20/solver-216614-1168243590 -C 1800 -M 900 /tmp/evaluation/216614-1168243590/mistral/bin/solver /tmp/evaluation/216614-1168243590/unknown.xml -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.18 1.03 1.22 5/87 19706
/proc/meminfo: memFree=1839232/2055920 swapFree=4170192/4192956
[pid=19705] ppid=19703 vsize=540 CPUtime=0
/proc/19705/stat : 19705 (solver) R 19703 19705 19162 0 -1 4194304 41 0 0 0 0 0 0 0 19 0 1 0 172753590 552960 26 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 7619364 0 2147483391 4096 0 0 0 0 17 1 0 0
/proc/19705/statm: 135 26 21 92 0 18 0

[startup+0.103426 s]
/proc/loadavg: 1.18 1.03 1.22 5/87 19706
/proc/meminfo: memFree=1839232/2055920 swapFree=4170192/4192956
[pid=19705] ppid=19703 vsize=18004 CPUtime=0.09
/proc/19705/stat : 19705 (solver) R 19703 19705 19162 0 -1 4194304 3594 0 0 0 8 1 0 0 19 0 1 0 172753590 18436096 3562 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134710278 0 0 4096 0 0 0 0 17 1 0 0
/proc/19705/statm: 4501 3562 716 92 0 2845 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 18004

Child status: 0
Real time (s): 0.160343
CPU time (s): 0.151976
CPU user time (s): 0.134979
CPU system time (s): 0.016997
CPU usage (%): 94.7819
Max. virtual memory (cumulated for all children) (KiB): 18004

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

runsolver used 0.001999 s user time and 0.008998 s system time

The end

Launcher Data (download as text)

Begin job on node20 on Mon Jan  8 08:06:30 UTC 2007


IDJOB= 216614
IDBENCH= 5090
FILE ID= node20/216614-1168243590

PBS_JOBID= 3481785

Free space on /tmp= 66554 MiB

BENCH NAME= HOME/pub/bench/CPAI06/rlfap/rlfapScensMod/scen6-w1.xml
COMMAND LINE= /tmp/evaluation/216614-1168243590/mistral/bin/solver /tmp/evaluation/216614-1168243590/unknown.xml -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node20/watcher-216614-1168243590 -o ROOT/results/node20/solver-216614-1168243590 -C 1800 -M 900  /tmp/evaluation/216614-1168243590/mistral/bin/solver /tmp/evaluation/216614-1168243590/unknown.xml -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  e4761551e00079c0c6c5437557356554

RANDOM SEED= 970417709

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.216
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.216
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:       1839712 kB
Buffers:         30292 kB
Cached:          99764 kB
SwapCached:       3428 kB
Active:         103960 kB
Inactive:        58680 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1839712 kB
SwapTotal:     4192956 kB
SwapFree:      4170192 kB
Dirty:            4172 kB
Writeback:           0 kB
Mapped:          48520 kB
Slab:            38268 kB
Committed_AS:  3627636 kB
PageTables:       2352 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 node20 on Mon Jan  8 08:06:31 UTC 2007