Trace number 237319

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.327949 0.335353

General information on the benchmark

Nameos-gp/
gp10-01-1093.xml
MD5SUM0da9d135f457ed0a2622be4bd1d9f01f
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.327949
SatisfiableYES
(Un)Satisfiability was proved
Number of variables101
Number of constraints1000
Maximum constraint arity2
Maximum domain size1094
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.10	c 
0.10	c Parsing xml file
0.10	c 	domains...............    0
0.10	c 	variables.............    0
0.10	c 	predicates............    0
0.10	c 	constraints........... 0.06
0.10	c Allocating memory
0.10	c 
0.10	c time limit = -1
0.10	c heuristic = dom/wdeg
0.10	c restart policy = Geometric increment
0.10	c restart base = 666
0.10	c restart factor = 1.33
0.10	c 
0.10	c Solving
0.10	c
0.31	s SATISFIABLE
0.31	v 1093 810 901 897 1076 1077 364 382 0 1078 1079 0 465 959 1077 480 458 1028 1030 1074 634 464 0 465 1024 1072 872 903 1073 585 959 465 464 607 1074 900 382 1 1072 1073 0 662 893 2 0 634 898 759 746 25 34 607 1076 585 609 1 0 974 1029 42 1028 712 480 1025 1022 42 1 971 810 34 2 1048 900 25 1018 872 460 901 971 0 1024 879 865 1 2 692 331 0 364 1052 1048 609 746 600 331 0 2 1033 692 862 1
0.31	d          SAT      1105 BTS      0.18 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/node12/watcher-237319-1168347453 -o ROOT/results/node12/solver-237319-1168347453 -C 1800 -M 900 /tmp/evaluation/237319-1168347453/tramontane/bin/solver /tmp/evaluation/237319-1168347453/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.96 2.00 2.00 5/94 7933
/proc/meminfo: memFree=1563128/2055920 swapFree=4160348/4192956
[pid=7932] ppid=7930 vsize=540 CPUtime=0
/proc/7932/stat : 7932 (solver) R 7930 7932 7688 0 -1 4194304 41 0 0 0 0 0 0 0 19 0 1 0 183140390 552960 26 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 9696036 0 2147483391 4096 0 0 0 0 17 1 0 0
/proc/7932/statm: 135 26 21 92 0 18 0

[startup+0.104342 s]
/proc/loadavg: 1.96 2.00 2.00 5/94 7933
/proc/meminfo: memFree=1563128/2055920 swapFree=4160348/4192956
[pid=7932] ppid=7930 vsize=14192 CPUtime=0.09
/proc/7932/stat : 7932 (solver) R 7930 7932 7688 0 -1 4194304 2634 0 0 0 8 1 0 0 19 0 1 0 183140390 14532608 2602 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 10131067 0 0 4096 0 0 0 0 17 1 0 0
/proc/7932/statm: 3548 2602 717 92 0 1892 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 14192

Child status: 0
Real time (s): 0.335353
CPU time (s): 0.327949
CPU user time (s): 0.294955
CPU system time (s): 0.032994
CPU usage (%): 97.7922
Max. virtual memory (cumulated for all children) (KiB): 23460

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.294955
system time used= 0.032994
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 4992
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.002999 s user time and 0.007998 s system time

The end

Launcher Data (download as text)

Begin job on node12 on Tue Jan  9 12:57:34 UTC 2007


IDJOB= 237319
IDBENCH= 6913
FILE ID= node12/237319-1168347453

PBS_JOBID= 3503618

Free space on /tmp= 66557 MiB

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

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  0da9d135f457ed0a2622be4bd1d9f01f

RANDOM SEED= 946367363

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.265
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.265
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:       1563608 kB
Buffers:         81488 kB
Cached:         266820 kB
SwapCached:       4816 kB
Active:         231912 kB
Inactive:       199552 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1563608 kB
SwapTotal:     4192956 kB
SwapFree:      4160348 kB
Dirty:            3288 kB
Writeback:           0 kB
Mapped:         101548 kB
Slab:            45648 kB
Committed_AS:  6143720 kB
PageTables:       2280 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= 66557 MiB



End job on node12 on Tue Jan  9 12:57:34 UTC 2007