Trace number 272955

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
CSP4J - MAC 2007-01-16SAT 0.792879 0.822107

DiagnosticValue
CHECKS687
NODES100

General information on the benchmark

Nameprimes/primes-10/
primes-10-40-2-1.xml
MD5SUM234e674269a89c373d7af686e7590efb
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.022996
SatisfiableYES
(Un)Satisfiability was proved
Number of variables100
Number of constraints40
Maximum constraint arity3
Maximum domain size28
Number of constraints which are defined in extension0
Number of constraints which are defined in intension40
Global constraints used (with number of constraints)

Solver Data (download as text)

0.80	v 7 17 19 19 7 13 17 5 29 3 2 2 2 29 2 2 2 19 5 11 2 23 2 2 5 2 2 7 19 13 29 5 5 23 2 2 7 17 3 2 29 18 3 17 17 2 23 2 2 2 7 2 2 2 2 7 5 2 17 3 13 2 2 2 29 2 2 2 7 19 11 17 2 13 11 2 2 2 2 16 2 23 26 2 23 11 2 2 13 2 5 2 29 2 29 2 17 29 11 29 
0.80	s SATISFIABLE
0.80	c 0.02 s
0.80	d NODES 100
0.80	d CHECKS 687

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/node72/watcher-272955-1169176119 -o ROOT/results/node72/solver-272955-1169176119 -C 1800 -M 900 /tmp/evaluation/272955-1169176119/cspfj.sh -competition /tmp/evaluation/272955-1169176119/unknown.xml 

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.16 2.23 2.03 5/94 27063
/proc/meminfo: memFree=1384296/2055920 swapFree=4191880/4192956
[pid=27062] ppid=27060 vsize=5352 CPUtime=0
/proc/27062/stat : 27062 (cspfj.sh) S 27060 27062 25985 0 -1 4194304 271 0 0 0 0 0 0 0 20 0 1 0 266020806 5480448 229 18446744073709551615 4194304 4889804 548682069312 18446744073709551615 234517750596 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/27062/statm: 1338 229 192 169 0 49 0
[pid=27064] ppid=27062 vsize=0 CPUtime=0
/proc/27064/stat : 27064 (dirname) R 27062 27062 25985 0 -1 4194308 128 0 0 0 0 0 0 0 21 0 1 0 266020806 0 0 18446744073709551615 0 0 0 0 0 0 0 4096 0 0 0 0 17 1 0 0
/proc/27064/statm: 0 0 0 0 0 0 0

[startup+0.106717 s]
/proc/loadavg: 2.16 2.23 2.03 5/94 27063
/proc/meminfo: memFree=1384296/2055920 swapFree=4191880/4192956
[pid=27062] ppid=27060 vsize=5352 CPUtime=0
/proc/27062/stat : 27062 (cspfj.sh) S 27060 27062 25985 0 -1 4194304 315 128 0 0 0 0 0 0 18 0 1 0 266020806 5480448 240 18446744073709551615 4194304 4889804 548682069312 18446744073709551615 234517750596 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/27062/statm: 1338 240 201 169 0 49 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 5352

[startup+0.518752 s]
/proc/loadavg: 2.16 2.23 2.03 5/94 27063
/proc/meminfo: memFree=1384296/2055920 swapFree=4191880/4192956
[pid=27062] ppid=27060 vsize=5352 CPUtime=0
/proc/27062/stat : 27062 (cspfj.sh) S 27060 27062 25985 0 -1 4194304 315 128 0 0 0 0 0 0 18 0 1 0 266020806 5480448 240 18446744073709551615 4194304 4889804 548682069312 18446744073709551615 234517750596 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/27062/statm: 1338 240 201 169 0 49 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 5352

Child status: 0
Real time (s): 0.822107
CPU time (s): 0.792879
CPU user time (s): 0.742887
CPU system time (s): 0.049992
CPU usage (%): 96.4448
Max. virtual memory (cumulated for all children) (KiB): 5352

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.742887
system time used= 0.049992
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 4705
page faults= 1
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 771
involuntary context switches= 698

runsolver used 0.002999 s user time and 0.007998 s system time

The end

Launcher Data (download as text)

Begin job on node72 on Fri Jan 19 03:08:40 UTC 2007


IDJOB= 272955
IDBENCH= 11663
IDSOLVER= 91
FILE ID= node72/272955-1169176119

PBS_JOBID= 3584169

Free space on /tmp= 66564 MiB

SOLVER NAME= CSP4J - MAC 2007-01-16
BENCH NAME= HOME/pub/bench/CPAI06/primes/primes-10/primes-10-40-2-1.xml
COMMAND LINE= /tmp/evaluation/272955-1169176119/cspfj.sh  -competition /tmp/evaluation/272955-1169176119/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node72/watcher-272955-1169176119 -o ROOT/results/node72/solver-272955-1169176119 -C 1800 -M 900  /tmp/evaluation/272955-1169176119/cspfj.sh  -competition /tmp/evaluation/272955-1169176119/unknown.xml

META MD5SUM SOLVER= 1cf1b9d4821c2ee5eee0dc0e02656faa
MD5SUM BENCH=  234e674269a89c373d7af686e7590efb

RANDOM SEED= 194267949

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.223
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.223
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:       1384712 kB
Buffers:         55900 kB
Cached:         461108 kB
SwapCached:        268 kB
Active:         276616 kB
Inactive:       314936 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1384712 kB
SwapTotal:     4192956 kB
SwapFree:      4191880 kB
Dirty:             332 kB
Writeback:           0 kB
Mapped:          99456 kB
Slab:            64232 kB
Committed_AS:  4534552 kB
PageTables:       2404 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= 66564 MiB



End job on node72 on Fri Jan 19 03:08:41 UTC 2007