Trace number 237383

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.348946 0.350335

General information on the benchmark

Nameos-gp/
gp10-08-1093.xml
MD5SUMf2d50c563873b0a18a3cc88920688123
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.348946
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.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.05
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.33	s SATISFIABLE
0.33	v 1093 1089 108 407 695 1084 0 1082 1083 1030 418 42 1085 565 1030 1058 1084 1057 71 783 1 975 1089 1 407 0 689 781 684 742 696 89 532 478 1079 1044 1077 1050 1057 0 63 478 0 418 1089 514 1074 1038 1037 1088 107 0 1082 1076 6 1037 920 1030 1 386 742 1090 1084 1082 1077 1 79 1029 689 1027 0 534 386 506 1082 55 1003 975 0 63 42 71 107 783 0 108 800 444 6 781 920 514 531 800 1076 444 696 0 565 1082 695
0.33	d          SAT      1243 BTS      0.21 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/node55/watcher-237383-1168347773 -o ROOT/results/node55/solver-237383-1168347773 -C 1800 -M 900 /tmp/evaluation/237383-1168347773/tramontane/bin/solver /tmp/evaluation/237383-1168347773/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.15 2.24 2.07 4/73 20842
/proc/meminfo: memFree=1571440/2055920 swapFree=4192192/4192956
[pid=20841] ppid=20839 vsize=6792 CPUtime=0
/proc/20841/stat : 20841 (solver) R 20839 20841 19310 0 -1 4194304 431 0 0 0 0 0 0 0 18 0 1 0 183175602 6955008 410 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 6818680 0 0 4096 0 0 0 0 17 0 0 0
/proc/20841/statm: 1698 411 372 92 0 30 0

[startup+0.104594 s]
/proc/loadavg: 2.15 2.24 2.07 4/73 20842
/proc/meminfo: memFree=1571440/2055920 swapFree=4192192/4192956
[pid=20841] ppid=20839 vsize=17104 CPUtime=0.1
/proc/20841/stat : 20841 (solver) R 20839 20841 19310 0 -1 4194304 3353 0 0 0 9 1 0 0 18 0 1 0 183175602 17514496 3321 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 7284293 0 0 4096 0 0 0 0 17 0 0 0
/proc/20841/statm: 4276 3323 717 92 0 2620 0
Current children cumulated CPU time (s) 0.1
Current children cumulated vsize (KiB) 17104

Child status: 0
Real time (s): 0.350335
CPU time (s): 0.348946
CPU user time (s): 0.32495
CPU system time (s): 0.023996
CPU usage (%): 99.6035
Max. virtual memory (cumulated for all children) (KiB): 23452

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.32495
system time used= 0.023996
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= 11
involuntary context switches= 64

runsolver used 0.003999 s user time and 0.003999 s system time

The end

Launcher Data (download as text)

Begin job on node55 on Tue Jan  9 13:02:53 UTC 2007


IDJOB= 237383
IDBENCH= 6917
FILE ID= node55/237383-1168347773

PBS_JOBID= 3503570

Free space on /tmp= 66561 MiB

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

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  f2d50c563873b0a18a3cc88920688123

RANDOM SEED= 424970823

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.218
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.218
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:       1571856 kB
Buffers:         26948 kB
Cached:         165904 kB
SwapCached:        268 kB
Active:         325728 kB
Inactive:       101916 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1571856 kB
SwapTotal:     4192956 kB
SwapFree:      4192192 kB
Dirty:            3372 kB
Writeback:           0 kB
Mapped:         244656 kB
Slab:            41648 kB
Committed_AS:  4331352 kB
PageTables:       2096 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= 66561 MiB



End job on node55 on Tue Jan  9 13:02:54 UTC 2007