Trace number 237399

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.200969 0.210432

General information on the benchmark

Nameos-gp/
gp10-02-1097.xml
MD5SUM7da39230cb4e791d72b52232540de1a5
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.18597
SatisfiableYES
(Un)Satisfiability was proved
Number of variables101
Number of constraints1000
Maximum constraint arity2
Maximum domain size1098
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.18	s SATISFIABLE
0.18	v 1097 6 70 750 5 0 761 62 216 114 58 444 1092 1091 120 1093 412 1090 997 0 114 1082 1084 123 26 819 25 1081 750 890 1045 932 0 1084 1080 1091 488 1079 78 216 498 1086 412 1080 1043 978 410 78 0 1083 1028 1085 1028 1081 412 1086 26 2 840 839 916 1084 1081 0 1085 1079 502 880 814 504 123 58 1086 819 0 518 501 1068 1090 488 26 1083 85 1079 1089 1021 0 362 880 1080 25 1030 1007 761 839 3 518 1 1091 1051 0
0.18	d          SAT       243 BTS      0.05 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/node25/watcher-237399-1168347900 -o ROOT/results/node25/solver-237399-1168347900 -C 1800 -M 900 /tmp/evaluation/237399-1168347900/tramontane/bin/solver /tmp/evaluation/237399-1168347900/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.22 2.13 6/93 16409
/proc/meminfo: memFree=1754576/2055920 swapFree=4170236/4192956
[pid=16408] ppid=16406 vsize=540 CPUtime=0
/proc/16408/stat : 16408 (solver) R 16406 16408 16164 0 -1 4194304 41 0 0 0 0 0 0 0 19 0 1 0 183182477 552960 26 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 3765028 0 2147483391 4096 0 0 0 0 17 1 0 0
/proc/16408/statm: 135 26 21 92 0 18 0

[startup+0.105426 s]
/proc/loadavg: 2.25 2.22 2.13 6/93 16409
/proc/meminfo: memFree=1754576/2055920 swapFree=4170236/4192956
[pid=16408] ppid=16406 vsize=13532 CPUtime=0.09
/proc/16408/stat : 16408 (solver) R 16406 16408 16164 0 -1 4194304 2477 0 0 0 9 0 0 0 19 0 1 0 183182477 13856768 2445 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 4200059 0 0 4096 0 0 0 0 17 1 0 0
/proc/16408/statm: 3383 2445 717 92 0 1727 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 13532

Child status: 0
Real time (s): 0.210432
CPU time (s): 0.200969
CPU user time (s): 0.175973
CPU system time (s): 0.024996
CPU usage (%): 95.5031
Max. virtual memory (cumulated for all children) (KiB): 13532

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

runsolver used 0.003999 s user time and 0.006998 s system time

The end

Launcher Data (download as text)

Begin job on node25 on Tue Jan  9 13:05:01 UTC 2007


IDJOB= 237399
IDBENCH= 6918
FILE ID= node25/237399-1168347900

PBS_JOBID= 3503631

Free space on /tmp= 66560 MiB

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

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  7da39230cb4e791d72b52232540de1a5

RANDOM SEED= 575521699

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:       1755056 kB
Buffers:          9392 kB
Cached:          80816 kB
SwapCached:       1388 kB
Active:         209096 kB
Inactive:        39028 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1755056 kB
SwapTotal:     4192956 kB
SwapFree:      4170236 kB
Dirty:            3356 kB
Writeback:           0 kB
Mapped:         178152 kB
Slab:            37204 kB
Committed_AS:  4687400 kB
PageTables:       2604 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= 66560 MiB



End job on node25 on Tue Jan  9 13:05:01 UTC 2007