Trace number 237303

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.297953 0.301625

General information on the benchmark

Nameos-gp/
gp10-04-1077.xml
MD5SUM9e1073cf0543b531d5d4e0d0fba8e4b2
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.297953
SatisfiableYES
(Un)Satisfiability was proved
Number of variables101
Number of constraints1000
Maximum constraint arity2
Maximum domain size1078
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.01	c 
0.01	c Parsing xml file
0.01	c 	domains...............    0
0.01	c 	variables.............    0
0.01	c 	predicates............    0
0.01	c 	constraints........... 0.06
0.07	c Allocating memory
0.07	c 
0.07	c time limit = -1
0.07	c heuristic = dom/wdeg
0.07	c restart policy = Geometric increment
0.07	c restart base = 666
0.07	c restart factor = 1.33
0.07	c 
0.07	c Solving
0.07	c
0.27	s SATISFIABLE
0.27	v 1077 1060 0 86 623 55 1059 54 565 1074 1075 1057 3 602 1070 872 280 1049 1072 0 862 239 718 890 5 1072 638 1073 1071 779 0 705 704 0 1059 81 1053 1056 1070 646 686 1066 1076 1061 538 54 602 0 686 55 664 1074 791 593 1076 0 1073 511 9 621 687 1053 1073 1060 280 631 0 1059 623 538 872 704 489 81 1075 23 718 86 0 9 994 1061 779 1055 0 1049 1056 840 1054 664 5 0 239 565 1074 1076 1075 593 511 890 840
0.27	d          SAT       681 BTS      0.14 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/node39/watcher-237303-1168347352 -o ROOT/results/node39/solver-237303-1168347352 -C 1800 -M 900 /tmp/evaluation/237303-1168347352/tramontane/bin/solver /tmp/evaluation/237303-1168347352/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.97 2.01 1.91 5/81 7453
/proc/meminfo: memFree=1750144/2055920 swapFree=4187312/4192956
[pid=7452] ppid=7450 vsize=6792 CPUtime=0
/proc/7452/stat : 7452 (solver) R 7450 7452 7137 0 -1 4194304 421 0 0 0 0 0 0 0 18 0 1 0 183134877 6955008 400 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 11062136 0 0 4096 0 0 0 0 17 1 0 0
/proc/7452/statm: 1698 400 363 92 0 30 0

[startup+0.106944 s]
/proc/loadavg: 1.97 2.01 1.91 5/81 7453
/proc/meminfo: memFree=1750144/2055920 swapFree=4187312/4192956
[pid=7452] ppid=7450 vsize=14588 CPUtime=0.1
/proc/7452/stat : 7452 (solver) R 7450 7452 7137 0 -1 4194304 2732 0 0 0 9 1 0 0 18 0 1 0 183134877 14938112 2700 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 11527803 0 0 4096 0 0 0 0 17 1 0 0
/proc/7452/statm: 3647 2704 717 92 0 1991 0
Current children cumulated CPU time (s) 0.1
Current children cumulated vsize (KiB) 14588

Child status: 0
Real time (s): 0.301625
CPU time (s): 0.297953
CPU user time (s): 0.270958
CPU system time (s): 0.026995
CPU usage (%): 98.7826
Max. virtual memory (cumulated for all children) (KiB): 23456

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.270958
system time used= 0.026995
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= 13
involuntary context switches= 62

runsolver used 0.001999 s user time and 0.007998 s system time

The end

Launcher Data (download as text)

Begin job on node39 on Tue Jan  9 12:55:53 UTC 2007


IDJOB= 237303
IDBENCH= 6912
FILE ID= node39/237303-1168347352

PBS_JOBID= 3503608

Free space on /tmp= 66553 MiB

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

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  9e1073cf0543b531d5d4e0d0fba8e4b2

RANDOM SEED= 738821182

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.236
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.236
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:       1750768 kB
Buffers:         25292 kB
Cached:         115420 kB
SwapCached:       1408 kB
Active:         180528 kB
Inactive:        71180 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1750768 kB
SwapTotal:     4192956 kB
SwapFree:      4187312 kB
Dirty:            3072 kB
Writeback:           0 kB
Mapped:         127140 kB
Slab:            38624 kB
Committed_AS:  4599360 kB
PageTables:       2060 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= 66553 MiB



End job on node39 on Tue Jan  9 12:55:53 UTC 2007