Trace number 229280

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.753885 0.755722

General information on the benchmark

Nametightness/tightness0.35/
rand-2-40-16-250-350-39_ext.xml
MD5SUMfbd78a7b57afd433723f2e31085dcad0
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 benchmark0.309952
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables40
Number of constraints250
Maximum constraint arity2
Maximum domain size16
Number of constraints which are defined in extension250
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.75	
0.75	Time: 730
0.75	
c 
c 
c 
c solution file
c 
c 

SAT
1 10 13 12 7 3 2 6 2 13 0 2 8 0 9 6 12 12 14 5 1 5 4 0 1 14 5 10 13 3 13 13 15 1 8 14 5 11 10 12 
c 
c 
c 
c conversion script
c 
c 

converting(/tmp/evaluation/229280-1168305547/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/node6/watcher-229280-1168305547 -o ROOT/results/node6/solver-229280-1168305547 -C 1800 -M 900 /tmp/evaluation/229280-1168305547/Complete/Ordinary/solver /tmp/evaluation/229280-1168305547/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: 1.14 1.57 1.54 4/78 17376
/proc/meminfo: memFree=1496744/2055924 swapFree=4165672/4192956
[pid=17375] ppid=17373 vsize=53472 CPUtime=0
/proc/17375/stat : 17375 (bprolog) R 17373 17375 15963 0 -1 4194304 479 0 0 0 0 0 0 0 18 0 1 0 178950296 54755328 198 18446744073709551615 134512640 134884608 4294956576 18446744073709551615 4294960144 0 0 4096 2 0 0 0 17 1 0 0
/proc/17375/statm: 13368 199 123 90 0 12906 0

[startup+0.102817 s]
/proc/loadavg: 1.14 1.57 1.54 4/78 17376
/proc/meminfo: memFree=1496744/2055924 swapFree=4165672/4192956
[pid=17375] ppid=17373 vsize=53824 CPUtime=0.09
/proc/17375/stat : 17375 (bprolog) R 17373 17375 15963 0 -1 4194304 1263 0 0 0 9 0 0 0 18 0 1 0 178950296 55115776 979 18446744073709551615 134512640 134884608 4294956576 18446744073709551615 134601535 0 0 4096 2 0 0 0 17 1 0 0
/proc/17375/statm: 13456 979 158 90 0 12994 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 53824

[startup+0.510864 s]
/proc/loadavg: 1.14 1.57 1.54 4/78 17376
/proc/meminfo: memFree=1496744/2055924 swapFree=4165672/4192956
[pid=17375] ppid=17373 vsize=64064 CPUtime=0.5
/proc/17375/stat : 17375 (bprolog) R 17373 17375 15963 0 -1 4194304 2279 0 0 0 50 0 0 0 22 0 2 0 178950296 65601536 1994 18446744073709551615 134512640 134884608 4294956576 18446744073709551615 134552092 0 0 4096 2 18446744073709551615 0 0 17 1 0 0
/proc/17375/statm: 16016 1994 169 90 0 15554 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 64064

Child status: 0
Real time (s): 0.755722
CPU time (s): 0.753885
CPU user time (s): 0.742887
CPU system time (s): 0.010998
CPU usage (%): 99.7569
Max. virtual memory (cumulated for all children) (KiB): 64064

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

runsolver used 0.002999 s user time and 0.005999 s system time

The end

Launcher Data (download as text)

Begin job on node6 on Tue Jan  9 01:19:08 UTC 2007


IDJOB= 229280
IDBENCH= 6291
FILE ID= node6/229280-1168305547

PBS_JOBID= 3502271

Free space on /tmp= 66552 MiB

BENCH NAME= HOME/pub/bench/CPAI06/tightness/tightness0.35/rand-2-40-16-250-350-39_ext.xml
COMMAND LINE= /tmp/evaluation/229280-1168305547/Complete/Ordinary/solver /tmp/evaluation/229280-1168305547/unknown 1800
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node6/convwatcher-229280-1168305547 -o ROOT/results/node6/conversion-229280-1168305547 -C 600 -M 900 /tmp/evaluation/229280-1168305547/Complete/Ordinary/conversion /tmp/evaluation/229280-1168305547/unknown
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node6/watcher-229280-1168305547 -o ROOT/results/node6/solver-229280-1168305547 -C 1800 -M 900  /tmp/evaluation/229280-1168305547/Complete/Ordinary/solver /tmp/evaluation/229280-1168305547/unknown 1800

META MD5SUM SOLVER= b53ab06f245aa5e62684a7a0a4388ade
MD5SUM BENCH=  fbd78a7b57afd433723f2e31085dcad0

RANDOM SEED= 940744231

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.240
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.240
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:      2055924 kB
MemFree:       1497224 kB
Buffers:         87040 kB
Cached:         378196 kB
SwapCached:       2944 kB
Active:         283412 kB
Inactive:       214100 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055924 kB
LowFree:       1497224 kB
SwapTotal:     4192956 kB
SwapFree:      4165672 kB
Dirty:            1412 kB
Writeback:           0 kB
Mapped:          41480 kB
Slab:            46604 kB
Committed_AS:  5577692 kB
PageTables:       1976 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= 66552 MiB



End job on node6 on Tue Jan  9 01:19:09 UTC 2007