Trace number 287279

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 19.63 19.8409

General information on the benchmark

Namelard/
lard-84-84.xml
MD5SUM0e84f8bfe18587ad81ed5970294179c4
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark19.4001
SatisfiableYES
(Un)Satisfiability was proved
Number of variables84
Number of constraints3486
Maximum constraint arity2
Maximum domain size85
Number of constraints which are defined in extension3486
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.07	c 
0.07	c Parsing xml file
0.07	c 	domains...............    0
0.08	c 	variables.............    0
0.09	c 	relations.............   18
18.17	c 	constraints........... 1.23
19.40	c Allocating memory
19.63	c 
19.63	c time limit = -1
19.63	c heuristic = dom/wdeg
19.63	c restart policy = Geometric increment
19.63	c restart base = 55
19.63	c restart factor = 1.33
19.63	c 
19.63	c Solving
19.63	c
19.74	s SATISFIABLE
19.74	v 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
19.74	d          SAT         0 BTS      0.06 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/node5/watcher-287279-1170112852 -o ROOT/results/node5/solver-287279-1170112852 -C 1800 -M 900 /tmp/evaluation/287279-1170112852/tramontane/bin/solver /tmp/evaluation/287279-1170112852/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.06 2.23 2.48 3/86 30259
/proc/meminfo: memFree=1372440/2055920 swapFree=4192812/4192956
[pid=30258] ppid=30256 vsize=4504 CPUtime=0
/proc/30258/stat : 30258 (solver) D 30256 30258 28981 0 -1 4194304 42 0 0 0 0 0 0 0 18 0 1 0 31240196 4612096 27 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 7898119 0 0 4096 0 18446744071563479169 0 0 17 0 0 0
/proc/30258/statm: 1126 27 21 92 0 19 0

[startup+0.108459 s]
/proc/loadavg: 2.06 2.23 2.48 3/86 30259
/proc/meminfo: memFree=1372440/2055920 swapFree=4192812/4192956
[pid=30258] ppid=30256 vsize=7864 CPUtime=0.03
/proc/30258/stat : 30258 (solver) R 30256 30258 28981 0 -1 4194304 980 0 19 0 2 1 0 0 18 0 1 0 31240196 8052736 967 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 8973966 0 0 4096 0 0 0 0 17 0 0 0
/proc/30258/statm: 1966 967 702 92 0 278 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 7864

[startup+0.519502 s]
/proc/loadavg: 2.06 2.23 2.48 3/86 30259
/proc/meminfo: memFree=1372440/2055920 swapFree=4192812/4192956
[pid=30258] ppid=30256 vsize=13368 CPUtime=0.44
/proc/30258/stat : 30258 (solver) R 30256 30258 28981 0 -1 4194304 2360 0 19 0 42 2 0 0 21 0 1 0 31240196 13688832 2347 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 8382791 0 0 4096 0 0 0 0 17 0 0 0
/proc/30258/statm: 3342 2347 702 92 0 1654 0
Current children cumulated CPU time (s) 0.44
Current children cumulated vsize (KiB) 13368

[startup+1.3446 s]
/proc/loadavg: 2.06 2.23 2.48 3/86 30259
/proc/meminfo: memFree=1343000/2055920 swapFree=4192812/4192956
[pid=30258] ppid=30256 vsize=23936 CPUtime=1.24
/proc/30258/stat : 30258 (solver) R 30256 30258 28981 0 -1 4194304 4999 0 19 0 120 4 0 0 25 0 1 0 31240196 24510464 4986 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 8382390 0 0 4096 0 0 0 0 17 0 0 0
/proc/30258/statm: 5984 4986 702 92 0 4296 0
Current children cumulated CPU time (s) 1.24
Current children cumulated vsize (KiB) 23936

[startup+2.98178 s]
/proc/loadavg: 2.14 2.24 2.48 3/86 30259
/proc/meminfo: memFree=1321816/2055920 swapFree=4192812/4192956
[pid=30258] ppid=30256 vsize=45600 CPUtime=2.87
/proc/30258/stat : 30258 (solver) R 30256 30258 28981 0 -1 4194304 10416 0 19 0 279 8 0 0 25 0 1 0 31240196 46694400 10403 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 0 0 0
/proc/30258/statm: 11400 10403 702 92 0 9712 0
Current children cumulated CPU time (s) 2.87
Current children cumulated vsize (KiB) 45600

[startup+6.26115 s]
/proc/loadavg: 2.14 2.24 2.48 4/86 30259
/proc/meminfo: memFree=1257304/2055920 swapFree=4192812/4192956
[pid=30258] ppid=30256 vsize=89204 CPUtime=6.12
/proc/30258/stat : 30258 (solver) R 30256 30258 28981 0 -1 4194304 21338 0 19 0 599 13 0 0 25 0 1 0 31240196 91344896 21325 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 8382482 0 0 4096 0 0 0 0 17 0 0 0
/proc/30258/statm: 22301 21325 702 92 0 20613 0
Current children cumulated CPU time (s) 6.12
Current children cumulated vsize (KiB) 89204

[startup+12.7249 s]
/proc/loadavg: 2.12 2.23 2.48 3/86 30259
/proc/meminfo: memFree=1131096/2055920 swapFree=4192812/4192956
[pid=30258] ppid=30256 vsize=175796 CPUtime=12.57
/proc/30258/stat : 30258 (solver) R 30256 30258 28981 0 -1 4194304 42973 0 19 0 1234 23 0 0 25 0 1 0 31240196 180015104 42960 18446744073709551615 134512640 134893233 4294956656 18446744073709551615 4156472285 0 0 4096 0 0 0 0 17 0 0 0
/proc/30258/statm: 43949 42960 702 92 0 42261 0
Current children cumulated CPU time (s) 12.57
Current children cumulated vsize (KiB) 175796

Child status: 0
Real time (s): 19.8409
CPU time (s): 19.63
CPU user time (s): 19.2701
CPU system time (s): 0.359945
CPU usage (%): 98.937
Max. virtual memory (cumulated for all children) (KiB): 251996

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 19.2701
system time used= 0.359945
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 62050
page faults= 19
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 39
involuntary context switches= 352

runsolver used 0.034994 s user time and 0.06199 s system time

The end

Launcher Data (download as text)

Begin job on node5 on Mon Jan 29 23:20:54 UTC 2007


IDJOB= 287279
IDBENCH= 19811
IDSOLVER= 85
FILE ID= node5/287279-1170112852

PBS_JOBID= 3689959

Free space on /tmp= 66403 MiB

SOLVER NAME= Tramontane 2006-12-04
BENCH NAME= HOME/pub/bench/CPAI06/lard/lard-84-84.xml
COMMAND LINE= /tmp/evaluation/287279-1170112852/tramontane/bin/solver /tmp/evaluation/287279-1170112852/unknown.xml -res geom -f 3 -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node5/watcher-287279-1170112852 -o ROOT/results/node5/solver-287279-1170112852 -C 1800 -M 900  /tmp/evaluation/287279-1170112852/tramontane/bin/solver /tmp/evaluation/287279-1170112852/unknown.xml -res geom -f 3 -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  0e84f8bfe18587ad81ed5970294179c4

RANDOM SEED= 454358616

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.224
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.224
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:       1372920 kB
Buffers:         29744 kB
Cached:         443264 kB
SwapCached:          0 kB
Active:         257448 kB
Inactive:       364844 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1372920 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:           71644 kB
Writeback:           0 kB
Mapped:         168816 kB
Slab:            45140 kB
Committed_AS:   660008 kB
PageTables:       2636 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= 66403 MiB



End job on node5 on Mon Jan 29 23:21:14 UTC 2007