Trace number 237271

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.305952 0.313734

General information on the benchmark

Nameos-gp/
gp10-10-1092.xml
MD5SUMc0094ff62451189fa8795b889ce9788b
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.305952
SatisfiableYES
(Un)Satisfiability was proved
Number of variables101
Number of constraints1000
Maximum constraint arity2
Maximum domain size1093
Number of constraints which are defined in extension0
Number of constraints which are defined in intension1000
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
0.20	c 	variables.............    0
0.20	c 	predicates............    0
0.20	c 	constraints........... 0.06
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 = 666
0.20	c restart factor = 1.33
0.20	c 
0.20	c Solving
0.20	c
0.29	s SATISFIABLE
0.29	v 1092 524 1063 273 518 709 359 0 380 1076 1089 709 684 1004 586 1091 1084 1007 1029 0 991 995 1057 982 28 1089 518 1082 0 976 981 1088 1060 1007 19 1087 189 986 28 965 289 1069 1068 1085 667 0 976 1075 1084 845 965 19 1088 372 0 1079 302 985 367 945 1004 1029 88 0 1085 1086 1082 1080 834 733 1079 503 1076 367 1090 1088 380 566 230 985 0 1057 733 1090 1089 1062 0 234 1085 586 230 302 0 88 845 1085 289 1086 512 834 273
0.29	d          SAT       770 BTS      0.15 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/node22/watcher-237271-1168347222 -o ROOT/results/node22/solver-237271-1168347222 -C 1800 -M 900 /tmp/evaluation/237271-1168347222/tramontane/bin/solver /tmp/evaluation/237271-1168347222/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.94 1.99 1.90 5/94 5141
/proc/meminfo: memFree=1813472/2055920 swapFree=4157544/4192956
[pid=5140] ppid=5138 vsize=540 CPUtime=0
/proc/5140/stat : 5140 (solver) R 5138 5140 4376 0 -1 4194304 41 0 0 0 0 0 0 0 19 0 1 0 183116644 552960 26 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 4678436 0 2147483391 4096 0 0 0 0 17 1 0 0
/proc/5140/statm: 135 26 21 92 0 18 0

[startup+0.102908 s]
/proc/loadavg: 1.94 1.99 1.90 5/94 5141
/proc/meminfo: memFree=1813472/2055920 swapFree=4157544/4192956
[pid=5140] ppid=5138 vsize=13664 CPUtime=0.09
/proc/5140/stat : 5140 (solver) R 5138 5140 4376 0 -1 4194304 2512 0 0 0 9 0 0 0 18 0 1 0 183116644 13991936 2480 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 5119717 0 0 4096 0 0 0 0 17 1 0 0
/proc/5140/statm: 3416 2480 717 92 0 1760 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 13664

Child status: 0
Real time (s): 0.313734
CPU time (s): 0.305952
CPU user time (s): 0.289955
CPU system time (s): 0.015997
CPU usage (%): 97.5195
Max. virtual memory (cumulated for all children) (KiB): 23496

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.289955
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= 4991
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= 19

runsolver used 0.001999 s user time and 0.005999 s system time

The end

Launcher Data (download as text)

Begin job on node22 on Tue Jan  9 12:53:42 UTC 2007


IDJOB= 237271
IDBENCH= 6910
FILE ID= node22/237271-1168347222

PBS_JOBID= 3503542

Free space on /tmp= 66558 MiB

BENCH NAME= HOME/pub/bench/CPAI06/os-gp/gp10-10-1092.xml
COMMAND LINE= /tmp/evaluation/237271-1168347222/tramontane/bin/solver /tmp/evaluation/237271-1168347222/unknown.xml -res geom -f 3 -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node22/watcher-237271-1168347222 -o ROOT/results/node22/solver-237271-1168347222 -C 1800 -M 900  /tmp/evaluation/237271-1168347222/tramontane/bin/solver /tmp/evaluation/237271-1168347222/unknown.xml -res geom -f 3 -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  c0094ff62451189fa8795b889ce9788b

RANDOM SEED= 461410446

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.279
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.279
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:       1813952 kB
Buffers:          9464 kB
Cached:          88520 kB
SwapCached:      11224 kB
Active:         151104 kB
Inactive:        36264 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1813952 kB
SwapTotal:     4192956 kB
SwapFree:      4157544 kB
Dirty:            3260 kB
Writeback:           0 kB
Mapped:         115872 kB
Slab:            39028 kB
Committed_AS:  4282904 kB
PageTables:       2460 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= 66558 MiB



End job on node22 on Tue Jan  9 12:53:42 UTC 2007