Trace number 204740

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-04UNSAT 6.76797 6.7798

General information on the benchmark

Namefapp/fapp16-20/fapp17/
fapp17-0300-3.xml
MD5SUM9ae1df0cce98a242997f01d96e447136
Bench Category2-ARY-INT (binary constraints in intension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark1.65675
SatisfiableNO
(Un)Satisfiability was provedNO
Number of variables300
Number of constraints3865
Maximum constraint arity2
Maximum domain size302
Number of constraints which are defined in extension0
Number of constraints which are defined in intension3865
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.02
0.03	c 	variables............. 0.02
0.04	c 	predicates............    0
0.04	c 	constraints........... 0.26
0.30	c Allocating memory
0.30	c 
0.30	c time limit = -1
0.30	c heuristic = dom/wdeg
0.30	c restart policy = Geometric increment
0.30	c restart base = 199
0.30	c restart factor = 1.33
0.30	c 
0.30	c Solving
0.30	c
6.77	s UNSATISFIABLE
6.77	d        UNSAT       112 BTS       6.5 s

Verifier Data (download as text)

No possible verification on an UNSAT instance

Watcher Data (download as text)

runsolver version 3.1.3 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node14/watcher-204740-1168166738 -o ROOT/results/node14/solver-204740-1168166738 -C 1800 -M 900 /tmp/evaluation/204740-1168166738/tramontane/bin/solver /tmp/evaluation/204740-1168166738/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.88 2.03 1.99 5/97 25399
/proc/meminfo: memFree=1310736/2055920 swapFree=4182236/4192956
[pid=25398] ppid=25396 vsize=6792 CPUtime=0
/proc/25398/stat : 25398 (solver) R 25396 25398 25154 0 -1 4194304 424 0 0 0 0 0 0 0 18 0 1 0 165068996 6955008 403 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 6896504 0 0 4096 0 0 0 0 17 0 0 0
/proc/25398/statm: 1698 403 364 92 0 30 0

[startup+0.103702 s]
/proc/loadavg: 1.88 2.03 1.99 5/97 25399
/proc/meminfo: memFree=1310736/2055920 swapFree=4182236/4192956
[pid=25398] ppid=25396 vsize=20080 CPUtime=0.09
/proc/25398/stat : 25398 (solver) R 25396 25398 25154 0 -1 4194304 2096 0 0 0 9 0 0 0 18 0 1 0 165068996 20561920 2064 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 4156461053 0 0 4096 0 0 0 0 17 0 0 0
/proc/25398/statm: 5020 2064 708 92 0 3364 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 20080

[startup+0.511739 s]
/proc/loadavg: 1.88 2.03 1.99 5/97 25399
/proc/meminfo: memFree=1310736/2055920 swapFree=4182236/4192956
[pid=25398] ppid=25396 vsize=22192 CPUtime=0.5
/proc/25398/stat : 25398 (solver) R 25396 25398 25154 0 -1 4194304 2655 0 0 0 49 1 0 0 22 0 1 0 165068996 22724608 2623 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 134710313 0 0 4096 0 0 0 0 17 0 0 0
/proc/25398/statm: 5548 2623 719 92 0 3892 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 22192

[startup+1.33282 s]
/proc/loadavg: 1.88 2.03 1.99 3/97 25399
/proc/meminfo: memFree=1297872/2055920 swapFree=4182236/4192956
[pid=25398] ppid=25396 vsize=22192 CPUtime=1.32
/proc/25398/stat : 25398 (solver) R 25396 25398 25154 0 -1 4194304 2655 0 0 0 131 1 0 0 25 0 1 0 165068996 22724608 2623 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 134812994 0 0 4096 0 0 0 0 17 0 0 0
/proc/25398/statm: 5548 2623 719 92 0 3892 0
Current children cumulated CPU time (s) 1.32
Current children cumulated vsize (KiB) 22192

[startup+2.97498 s]
/proc/loadavg: 1.88 2.03 1.99 3/97 25399
/proc/meminfo: memFree=1287504/2055920 swapFree=4182236/4192956
[pid=25398] ppid=25396 vsize=22192 CPUtime=2.97
/proc/25398/stat : 25398 (solver) R 25396 25398 25154 0 -1 4194304 2655 0 0 0 296 1 0 0 25 0 1 0 165068996 22724608 2623 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 134711287 0 0 4096 0 0 0 0 17 0 0 0
/proc/25398/statm: 5548 2623 719 92 0 3892 0
Current children cumulated CPU time (s) 2.97
Current children cumulated vsize (KiB) 22192

[startup+6.25829 s]
/proc/loadavg: 1.89 2.02 1.99 3/97 25399
/proc/meminfo: memFree=1276240/2055920 swapFree=4182236/4192956
[pid=25398] ppid=25396 vsize=22192 CPUtime=6.24
/proc/25398/stat : 25398 (solver) R 25396 25398 25154 0 -1 4194304 2655 0 0 0 623 1 0 0 25 0 1 0 165068996 22724608 2623 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 134722064 0 0 4096 0 0 0 0 17 0 0 0
/proc/25398/statm: 5548 2623 719 92 0 3892 0
Current children cumulated CPU time (s) 6.24
Current children cumulated vsize (KiB) 22192

Child status: 0
Real time (s): 6.7798
CPU time (s): 6.76797
CPU user time (s): 6.75297
CPU system time (s): 0.014997
CPU usage (%): 99.8255
Max. virtual memory (cumulated for all children) (KiB): 22192

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

runsolver used 0.011998 s user time and 0.025996 s system time

The end

Launcher Data (download as text)

Begin job on node14 on Sun Jan  7 10:45:39 UTC 2007


IDJOB= 204740
IDBENCH= 4051
FILE ID= node14/204740-1168166738

PBS_JOBID= 3478691

Free space on /tmp= 66340 MiB

BENCH NAME= HOME/pub/bench/CPAI06/fapp/fapp16-20/fapp17/fapp17-0300-3.xml
COMMAND LINE= /tmp/evaluation/204740-1168166738/tramontane/bin/solver /tmp/evaluation/204740-1168166738/unknown.xml -res geom -f 3 -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node14/watcher-204740-1168166738 -o ROOT/results/node14/solver-204740-1168166738 -C 1800 -M 900  /tmp/evaluation/204740-1168166738/tramontane/bin/solver /tmp/evaluation/204740-1168166738/unknown.xml -res geom -f 3 -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  9ae1df0cce98a242997f01d96e447136

RANDOM SEED= 914005135

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.227
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.227
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:       1321776 kB
Buffers:         26732 kB
Cached:         135916 kB
SwapCached:       4156 kB
Active:         557164 kB
Inactive:       108240 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1321776 kB
SwapTotal:     4192956 kB
SwapFree:      4182236 kB
Dirty:            3828 kB
Writeback:           0 kB
Mapped:         522156 kB
Slab:            52664 kB
Committed_AS:  5898408 kB
PageTables:       3116 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= 66340 MiB



End job on node14 on Sun Jan  7 10:45:48 UTC 2007