Trace number 231481

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.840871 0.842523

General information on the benchmark

Namegeom/
geo50-20-d4-75-83_ext.xml
MD5SUMa85c59a6ccd57dea7071443931f0564e
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.197969
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables50
Number of constraints430
Maximum constraint arity2
Maximum domain size20
Number of constraints which are defined in extension430
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.83	
0.83	Time: 807
0.83	
c 
c 
c 
c solution file
c 
c 

SAT
19 9 1 15 5 1 1 12 7 7 7 19 9 20 1 3 20 10 17 11 1 5 6 4 1 19 1 1 13 3 18 13 5 6 14 3 2 1 1 12 11 18 10 7 6 18 15 1 7 4 
c 
c 
c 
c conversion script
c 
c 

converting(/tmp/evaluation/231481-1168318082/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/node72/watcher-231481-1168318082 -o ROOT/results/node72/solver-231481-1168318082 -C 1800 -M 900 /tmp/evaluation/231481-1168318082/Complete/Ordinary/solver /tmp/evaluation/231481-1168318082/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.72 0.98 1.35 4/78 22489
/proc/meminfo: memFree=1355944/2055920 swapFree=4191880/4192956
[pid=22488] ppid=22486 vsize=53472 CPUtime=0
/proc/22488/stat : 22488 (bprolog) R 22486 22488 22180 0 -1 4194304 478 0 0 0 0 0 0 0 18 0 1 0 180217726 54755328 197 18446744073709551615 134512640 134884608 4294956576 18446744073709551615 134531306 0 0 4096 2 0 0 0 17 1 0 0
/proc/22488/statm: 13368 198 123 90 0 12906 0

[startup+0.102676 s]
/proc/loadavg: 0.72 0.98 1.35 4/78 22489
/proc/meminfo: memFree=1355944/2055920 swapFree=4191880/4192956
[pid=22488] ppid=22486 vsize=53824 CPUtime=0.09
/proc/22488/stat : 22488 (bprolog) R 22486 22488 22180 0 -1 4194304 1588 0 0 0 9 0 0 0 18 0 1 0 180217726 55115776 1304 18446744073709551615 134512640 134884608 4294956576 18446744073709551615 134603132 0 0 4096 2 0 0 0 17 1 0 0
/proc/22488/statm: 13456 1304 158 90 0 12994 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 53824

[startup+0.510712 s]
/proc/loadavg: 0.72 0.98 1.35 4/78 22489
/proc/meminfo: memFree=1355944/2055920 swapFree=4191880/4192956
[pid=22488] ppid=22486 vsize=64064 CPUtime=0.5
/proc/22488/stat : 22488 (bprolog) R 22486 22488 22180 0 -1 4194304 3768 0 0 0 49 1 0 0 21 0 2 0 180217726 65601536 3483 18446744073709551615 134512640 134884608 4294956576 18446744073709551615 134711598 0 0 4096 2 18446744073709551615 0 0 17 1 0 0
/proc/22488/statm: 16016 3483 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.842523
CPU time (s): 0.840871
CPU user time (s): 0.822874
CPU system time (s): 0.017997
CPU usage (%): 99.8039
Max. virtual memory (cumulated for all children) (KiB): 64064

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

runsolver used 0.003999 s user time and 0.004999 s system time

The end

Launcher Data (download as text)

Begin job on node72 on Tue Jan  9 04:48:04 UTC 2007


IDJOB= 231481
IDBENCH= 6469
FILE ID= node72/231481-1168318082

PBS_JOBID= 3502451

Free space on /tmp= 66560 MiB

BENCH NAME= HOME/pub/bench/CPAI06/geom/geo50-20-d4-75-83_ext.xml
COMMAND LINE= /tmp/evaluation/231481-1168318082/Complete/Ordinary/solver /tmp/evaluation/231481-1168318082/unknown 1800
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node72/convwatcher-231481-1168318082 -o ROOT/results/node72/conversion-231481-1168318082 -C 600 -M 900 /tmp/evaluation/231481-1168318082/Complete/Ordinary/conversion /tmp/evaluation/231481-1168318082/unknown
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node72/watcher-231481-1168318082 -o ROOT/results/node72/solver-231481-1168318082 -C 1800 -M 900  /tmp/evaluation/231481-1168318082/Complete/Ordinary/solver /tmp/evaluation/231481-1168318082/unknown 1800

META MD5SUM SOLVER= b53ab06f245aa5e62684a7a0a4388ade
MD5SUM BENCH=  a85c59a6ccd57dea7071443931f0564e

RANDOM SEED= 444400938

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:       1356488 kB
Buffers:         57352 kB
Cached:         533368 kB
SwapCached:        268 kB
Active:         218972 kB
Inactive:       414828 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1356488 kB
SwapTotal:     4192956 kB
SwapFree:      4191880 kB
Dirty:            1860 kB
Writeback:           0 kB
Mapped:          60428 kB
Slab:            51080 kB
Committed_AS:  3530328 kB
PageTables:       1916 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= 66560 MiB



End job on node72 on Tue Jan  9 04:48:11 UTC 2007