Trace number 237415

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 1.17882 1.19327

General information on the benchmark

Nameos-gp/
gp10-03-1081.xml
MD5SUM2024c7f683e3aa406b493242136d5569
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 benchmark1.17882
SatisfiableYES
(Un)Satisfiability was proved
Number of variables101
Number of constraints1000
Maximum constraint arity2
Maximum domain size1082
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.21	c 
0.21	c Parsing xml file
0.21	c 	domains...............    0
0.21	c 	variables.............    0
0.21	c 	predicates............    0
0.21	c 	constraints........... 0.06
0.21	c Allocating memory
0.21	c 
0.21	c time limit = -1
0.21	c heuristic = dom/wdeg
0.21	c restart policy = Geometric increment
0.21	c restart base = 666
0.21	c restart factor = 1.33
0.21	c 
0.21	c Solving
0.21	c
1.17	s SATISFIABLE
1.17	v 1081 869 1055 164 115 124 1062 91 326 0 901 908 800 31 0 1073 817 642 1071 1069 148 399 1054 1070 481 1055 0 110 1006 290 1069 607 1050 326 1065 1049 659 1071 182 817 0 659 1062 302 98 0 908 303 115 185 885 31 0 2 1072 185 1073 776 90 91 1071 0 862 1000 1067 1069 63 1072 860 578 1064 517 2 0 1006 1072 580 1080 885 1065 638 56 1000 607 1066 1048 578 0 1054 399 1049 481 517 1064 124 800 1077 90 0 1049 1048
1.17	d          SAT      8672 BTS         1 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/node50/watcher-237415-1168347995 -o ROOT/results/node50/solver-237415-1168347995 -C 1800 -M 900 /tmp/evaluation/237415-1168347995/tramontane/bin/solver /tmp/evaluation/237415-1168347995/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: 2.25 2.13 2.01 5/81 15199
/proc/meminfo: memFree=783544/2055920 swapFree=4191892/4192956
[pid=15198] ppid=15196 vsize=540 CPUtime=0
/proc/15198/stat : 15198 (solver) R 15196 15198 14954 0 -1 4194304 41 0 0 0 0 0 0 0 19 0 1 0 183198164 552960 26 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 7918372 0 2147483391 4096 0 0 0 0 17 1 0 0
/proc/15198/statm: 135 26 21 92 0 18 0

[startup+0.104623 s]
/proc/loadavg: 2.25 2.13 2.01 5/81 15199
/proc/meminfo: memFree=783544/2055920 swapFree=4191892/4192956
[pid=15198] ppid=15196 vsize=12340 CPUtime=0.09
/proc/15198/stat : 15198 (solver) R 15196 15198 14954 0 -1 4194304 2168 0 0 0 8 1 0 0 18 0 1 0 183198164 12636160 2136 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 8353403 0 0 4096 0 0 0 0 17 1 0 0
/proc/15198/statm: 3085 2136 717 92 0 1429 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 12340

[startup+0.514677 s]
/proc/loadavg: 2.25 2.13 2.01 5/81 15199
/proc/meminfo: memFree=783544/2055920 swapFree=4191892/4192956
[pid=15198] ppid=15196 vsize=23456 CPUtime=0.5
/proc/15198/stat : 15198 (solver) R 15196 15198 14954 0 -1 4194304 4972 0 0 0 47 3 0 0 22 0 1 0 183198164 24018944 4940 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 134792864 0 0 4096 0 0 0 0 17 1 0 0
/proc/15198/statm: 5864 4940 720 92 0 4208 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 23456

Child status: 0
Real time (s): 1.19327
CPU time (s): 1.17882
CPU user time (s): 1.13783
CPU system time (s): 0.040993
CPU usage (%): 98.7889
Max. virtual memory (cumulated for all children) (KiB): 23456

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 1.13783
system time used= 0.040993
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= 45

runsolver used 0.004999 s user time and 0.011998 s system time

The end

Launcher Data (download as text)

Begin job on node50 on Tue Jan  9 13:06:36 UTC 2007


IDJOB= 237415
IDBENCH= 6919
FILE ID= node50/237415-1168347995

PBS_JOBID= 3503634

Free space on /tmp= 66556 MiB

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

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  2024c7f683e3aa406b493242136d5569

RANDOM SEED= 195387971

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.263
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	: 5931.00
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.263
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:        784024 kB
Buffers:         76884 kB
Cached:         428640 kB
SwapCached:        396 kB
Active:         898444 kB
Inactive:       313528 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:        784024 kB
SwapTotal:     4192956 kB
SwapFree:      4191892 kB
Dirty:            3232 kB
Writeback:           0 kB
Mapped:         724236 kB
Slab:            43856 kB
Committed_AS:  5290692 kB
PageTables:       3296 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= 66556 MiB



End job on node50 on Tue Jan  9 13:06:37 UTC 2007