Trace number 248139

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
BPrologCSPSolver70a 2006-12-13SAT 0.031994 0.0345021

General information on the benchmark

Nameprimes/primes-30/
primes-30-80-2-7.xml
MD5SUM07e25463948b7cfaec32b3dc58c5304a
Bench CategoryN-ARY-INT (n-ary constraints in intension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.031994
SatisfiableYES
(Un)Satisfiability was proved
Number of variables100
Number of constraints80
Maximum constraint arity9
Maximum domain size112
Number of constraints which are defined in extension0
Number of constraints which are defined in intension80
Global constraints used (with number of constraints)

Solver Data (download as text)

0.03	
0.03	Time: 15
0.03	
c 
c 
c 
c solution file
c 
c 

SAT
43 59 107 101 89 101 59 41 29 3 5 19 73 71 89 59 2 17 83 59 37 23 107 29 5 73 5 43 19 101 113 41 41 67 113 107 43 59 3 83 29 7 79 113 47 19 23 47 13 2 89 59 3 73 103 7 5 73 59 3 53 53 47 107 103 13 59 29 43 61 97 53 41 53 47 107 47 47 7 73 19 67 17 23 23 97 7 37 47 71 41 2 103 67 71 83 59 17 97 113 
c 
c 
c 
c conversion script
c 
c 

converting(/tmp/evaluation/248139-1168719455/unknown)

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/node76/watcher-248139-1168719455 -o ROOT/results/node76/solver-248139-1168719455 -C 1800 -M 900 /tmp/evaluation/248139-1168719455/Complete/Ordinary/solver /tmp/evaluation/248139-1168719455/unknown 1800 

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: 0.61 0.90 0.98 5/75 11410
/proc/meminfo: memFree=1675592/2055888 swapFree=4095388/4096564
[pid=11409] ppid=11407 vsize=53476 CPUtime=0
/proc/11409/stat : 11409 (bprolog) R 11407 11409 11272 0 -1 4194304 514 0 0 0 0 0 0 0 18 0 1 0 220343369 54759424 235 18446744073709551615 134512640 134884608 4294956576 18446744073709551615 134535461 0 0 4096 2 0 0 0 17 0 0 0
/proc/11409/statm: 13369 235 124 90 0 12906 0

Child status: 0
Real time (s): 0.0345021
CPU time (s): 0.031994
CPU user time (s): 0.024996
CPU system time (s): 0.006998
CPU usage (%): 92.7306
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.024996
system time used= 0.006998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 852
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= 8
involuntary context switches= 2

runsolver used 0.002999 s user time and 0.004999 s system time

The end

Launcher Data (download as text)

Begin job on node76 on Sat Jan 13 20:17:36 UTC 2007


IDJOB= 248139
IDBENCH= 11684
IDSOLVER= 64
FILE ID= node76/248139-1168719455

PBS_JOBID= 3547678

Free space on /tmp= 66650 MiB

SOLVER NAME= BPrologCSPSolver70a 2006-12-13
BENCH NAME= HOME/pub/bench/CPAI06/primes/primes-30/primes-30-80-2-7.xml
COMMAND LINE= /tmp/evaluation/248139-1168719455/Complete/Ordinary/solver /tmp/evaluation/248139-1168719455/unknown 1800
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node76/convwatcher-248139-1168719455 -o ROOT/results/node76/conversion-248139-1168719455 -C 600 -M 900 /tmp/evaluation/248139-1168719455/Complete/Ordinary/conversion /tmp/evaluation/248139-1168719455/unknown
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node76/watcher-248139-1168719455 -o ROOT/results/node76/solver-248139-1168719455 -C 1800 -M 900  /tmp/evaluation/248139-1168719455/Complete/Ordinary/solver /tmp/evaluation/248139-1168719455/unknown 1800

META MD5SUM SOLVER= b53ab06f245aa5e62684a7a0a4388ade
MD5SUM BENCH=  07e25463948b7cfaec32b3dc58c5304a

RANDOM SEED= 452997676

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.254
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	: 6006.17
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.254
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	: 5999.42
clflush size	: 64
cache_alignment	: 128
address sizes	: 36 bits physical, 48 bits virtual
power management:


/proc/meminfo:
MemTotal:      2055888 kB
MemFree:       1676336 kB
Buffers:         32092 kB
Cached:         273088 kB
SwapCached:        276 kB
Active:          76188 kB
Inactive:       248860 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055888 kB
LowFree:       1676336 kB
SwapTotal:     4096564 kB
SwapFree:      4095388 kB
Dirty:            2284 kB
Writeback:           0 kB
Mapped:          29136 kB
Slab:            40432 kB
Committed_AS:  7501504 kB
PageTables:       1712 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264388 kB
VmallocChunk: 536606243 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

Free space on /tmp at the end= 66650 MiB



End job on node76 on Sat Jan 13 20:17:45 UTC 2007