Trace number 195239

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.645901 0.648723

General information on the benchmark

Namerlfap/rlfapGraphsMod/
graph2-f24.xml
MD5SUMb71c9e7325e6d9265cae682ae68d2699
Bench Category2-ARY-INT (binary constraints in intension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.52092
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables400
Number of constraints2245
Maximum constraint arity2
Maximum domain size22
Number of constraints which are defined in extension0
Number of constraints which are defined in intension2245
Global constraints used (with number of constraints)

Solver Data (download as text)

0.64	
0.64	Time: 577
0.64	
c 
c 
c 
c solution file
c 
c 

SAT
16 254 114 352 268 30 86 324 16 254 296 58 30 268 16 254 44 282 44 282 366 128 58 296 268 30 58 296 296 58 296 58 156 394 310 72 142 380 296 58 352 114 254 16 72 310 338 100 310 72 282 44 380 142 282 44 282 44 100 338 86 324 30 268 268 30 72 310 16 254 142 380 254 16 254 16 254 16 268 30 72 310 30 268 268 30 30 268 394 156 100 338 366 128 296 58 16 254 30 268 296 58 156 394 86 324 128 366 16 254 30 268 352 114 72 310 128 366 142 380 30 268 352 114 296 58 30 268 142 380 16 254 86 324 380 142 86 324 380 142 86 324 338 100 268 30 282 44 394 156 100 338 254 16 142 380 338 100 338 100 58 296 380 142 114 352 72 310 352 114 100 338 30 268 16 254 296 58 142 380 310 72 72 310 282 44 282 44 142 380 86 324 394 156 58 296 254 16 254 16 394 156 44 282 254 16 338 100 338 100 296 58 142 380 156 394 254 16 310 72 324 86 58 296 16 254 380 142 310 72 338 100 324 86 310 72 268 30 114 352 44 282 72 310 58 296 142 380 86 324 268 30 30 268 142 380 86 324 380 142 142 380 142 380 142 380 86 324 72 310 58 296 268 30 100 338 44 282 100 338 30 268 296 58 142 380 254 16 44 282 380 142 380 142 114 352 142 380 142 380 324 86 324 86 72 310 338 100 380 142 142 380 142 380 58 296 142 380 282 44 254 16 394 156 254 16 352 114 30 268 366 128 128 366 296 58 30 268 380 142 30 268 16 254 30 268 338 100 142 380 142 380 254 16 394 156 254 16 30 268 254 16 324 86 310 72 338 100 310 72 254 16 366 128 324 86 324 86 366 128 268 30 100 338 324 86 44 282 254 16 352 114 254 16 30 268 310 72 366 128 
c 
c 
c 
c conversion script
c 
c 

converting(/tmp/evaluation/195239-1168112419/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/node1/watcher-195239-1168112419 -o ROOT/results/node1/solver-195239-1168112419 -C 1800 -M 900 /tmp/evaluation/195239-1168112419/Complete/Ordinary/solver /tmp/evaluation/195239-1168112419/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.85 1.97 1.99 5/94 30336
/proc/meminfo: memFree=1238640/2055920 swapFree=4165584/4192956
[pid=30335] ppid=30333 vsize=53472 CPUtime=0
/proc/30335/stat : 30335 (bprolog) R 30333 30335 30090 0 -1 4194304 484 0 0 0 0 0 0 0 18 0 1 0 159638023 54755328 203 18446744073709551615 134512640 134884608 4294956576 18446744073709551615 134550268 0 0 4096 2 0 0 0 17 1 0 0
/proc/30335/statm: 13368 204 123 90 0 12906 0

[startup+0.103949 s]
/proc/loadavg: 1.85 1.97 1.99 5/94 30336
/proc/meminfo: memFree=1238640/2055920 swapFree=4165584/4192956
[pid=30335] ppid=30333 vsize=61772 CPUtime=0.09
/proc/30335/stat : 30335 (bprolog) R 30333 30335 30090 0 -1 4194304 1417 0 0 0 9 0 0 0 18 0 1 0 159638023 63254528 1132 18446744073709551615 134512640 134884608 4294956576 18446744073709551615 134589209 0 0 4096 2 0 0 0 17 1 0 0
/proc/30335/statm: 15443 1132 173 90 0 14981 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 61772

[startup+0.511997 s]
/proc/loadavg: 1.85 1.97 1.99 5/94 30336
/proc/meminfo: memFree=1238640/2055920 swapFree=4165584/4192956
[pid=30335] ppid=30333 vsize=79828 CPUtime=0.5
/proc/30335/stat : 30335 (bprolog) R 30333 30335 30090 0 -1 4194304 6900 0 0 0 48 2 0 0 22 0 2 0 159638023 81743872 4661 18446744073709551615 134512640 134884608 4294956576 18446744073709551615 134618374 0 0 4096 2 18446744073709551615 0 0 17 1 0 0
/proc/30335/statm: 19957 4661 177 90 0 19495 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 79828

Child status: 0
Real time (s): 0.648723
CPU time (s): 0.645901
CPU user time (s): 0.59091
CPU system time (s): 0.054991
CPU usage (%): 99.565
Max. virtual memory (cumulated for all children) (KiB): 95452

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

runsolver used 0.002999 s user time and 0.006998 s system time

The end

Launcher Data (download as text)

Begin job on node1 on Sat Jan  6 19:40:20 UTC 2007


IDJOB= 195239
IDBENCH= 3257
FILE ID= node1/195239-1168112419

PBS_JOBID= 3477093

Free space on /tmp= 66303 MiB

BENCH NAME= HOME/pub/bench/CPAI06/rlfap/rlfapGraphsMod/graph2-f24.xml
COMMAND LINE= /tmp/evaluation/195239-1168112419/Complete/Ordinary/solver /tmp/evaluation/195239-1168112419/unknown 1800
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node1/convwatcher-195239-1168112419 -o ROOT/results/node1/conversion-195239-1168112419 -C 600 -M 900 /tmp/evaluation/195239-1168112419/Complete/Ordinary/conversion /tmp/evaluation/195239-1168112419/unknown
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node1/watcher-195239-1168112419 -o ROOT/results/node1/solver-195239-1168112419 -C 1800 -M 900  /tmp/evaluation/195239-1168112419/Complete/Ordinary/solver /tmp/evaluation/195239-1168112419/unknown 1800

META MD5SUM SOLVER= b53ab06f245aa5e62684a7a0a4388ade
MD5SUM BENCH=  b71c9e7325e6d9265cae682ae68d2699

RANDOM SEED= 731660093

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.234
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.234
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:       1239184 kB
Buffers:         68500 kB
Cached:         599744 kB
SwapCached:       3664 kB
Active:         218508 kB
Inactive:       501816 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1239184 kB
SwapTotal:     4192956 kB
SwapFree:      4165584 kB
Dirty:            1692 kB
Writeback:           0 kB
Mapped:          69476 kB
Slab:            80928 kB
Committed_AS:  4414992 kB
PageTables:       2444 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= 66303 MiB



End job on node1 on Sat Jan  6 19:40:24 UTC 2007