Trace number 195246

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
VALCSP 3.0SAT 0.163974 0.177314

DiagnosticValue
CHECKS1129660
NODES606

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.17	s SATISFIABLE
0.17	v 72 310 128 366 366 128 296 58 114 352 100 338 114 352 16 254 128 366 16 254 338 100 86 324 72 310 30 268 310 72 30 268 394 156 58 296 72 310 268 30 16 254 310 72 30 268 282 44 268 30 72 310 380 142 58 296 30 268 310 72 352 114 44 282 86 324 30 268 16 254 142 380 58 296 366 128 268 30 114 352 324 86 44 282 58 296 142 380 394 156 282 44 30 268 254 16 282 44 30 268 296 58 338 100 44 282 366 128 100 338 324 86 296 58 16 254 156 394 142 380 310 72 30 268 58 296 30 268 142 380 72 310 30 268 380 142 30 268 72 310 268 30 338 100 44 282 86 324 366 128 16 254 254 16 142 380 338 100 58 296 296 58 380 142 254 16 30 268 114 352 114 352 296 58 44 282 268 30 142 380 86 324 44 282 30 268 100 338 142 380 324 86 394 156 352 114 16 254 310 72 86 324 338 100 254 16 268 30 324 86 338 100 142 380 254 16 366 128 282 44 366 128 268 30 114 352 380 142 254 16 254 16 128 366 128 366 282 44 16 254 268 30 310 72 58 296 380 142 86 324 324 86 268 30 142 380 352 114 380 142 128 366 142 380 142 380 86 324 44 282 282 44 86 324 86 324 268 30 338 100 282 44 282 44 142 380 16 254 72 310 380 142 142 380 114 352 142 380 380 142 352 114 16 254 44 282 72 310 380 142 142 380 142 380 44 282 142 380 338 100 128 366 156 394 58 296 296 58 282 44 352 114 156 394 16 254 30 268 380 142 268 30 324 86 156 394 310 72 142 380 142 380 72 310 128 366 16 254 338 100 338 100 394 156 44 282 282 44 296 58 72 310 156 394 254 16 72 310 30 268 296 58 268 30 100 338 338 100 324 86 44 282 296 58 338 100 16 254 72 310 
0.17	d CHECKS 1.12966e+06
0.17	d NODES 606
0.17

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/node41/watcher-195246-1168112433 -o ROOT/results/node41/solver-195246-1168112433 -C 1800 -M 900 /tmp/evaluation/195246-1168112433/VALCSP /tmp/evaluation/195246-1168112433/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: 1.57 1.86 1.88 5/82 17249
/proc/meminfo: memFree=1521096/2055920 swapFree=4192812/4192956
[pid=17248] ppid=17246 vsize=18540 CPUtime=0
/proc/17248/stat : 17248 (runsolver) R 17246 17248 16814 0 -1 4194368 16 0 0 0 0 0 0 0 18 0 1 0 159642576 18984960 279 18446744073709551615 4194304 4267372 548682069088 18446744073709551615 238390144295 0 0 4096 24578 0 0 0 17 1 0 0
/proc/17248/statm: 4635 279 244 17 0 2626 0

[startup+0.10382 s]
/proc/loadavg: 1.57 1.86 1.88 5/82 17249
/proc/meminfo: memFree=1521096/2055920 swapFree=4192812/4192956
[pid=17248] ppid=17246 vsize=7144 CPUtime=0.08
/proc/17248/stat : 17248 (VALCSP) R 17246 17248 16814 0 -1 4194304 1515 0 0 0 8 0 0 0 18 0 1 0 159642576 7315456 1493 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134530978 0 0 4096 0 0 0 0 17 0 0 0
/proc/17248/statm: 1786 1493 64 8 0 1458 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 7144

Child status: 0
Real time (s): 0.177314
CPU time (s): 0.163974
CPU user time (s): 0.151976
CPU system time (s): 0.011998
CPU usage (%): 92.4766
Max. virtual memory (cumulated for all children) (KiB): 7144

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

runsolver used 0.002999 s user time and 0.003999 s system time

The end

Launcher Data (download as text)

Begin job on node41 on Sat Jan  6 19:40:33 UTC 2007


IDJOB= 195246
IDBENCH= 3257
FILE ID= node41/195246-1168112433

PBS_JOBID= 3477370

Free space on /tmp= 66327 MiB

BENCH NAME= HOME/pub/bench/CPAI06/rlfap/rlfapGraphsMod/graph2-f24.xml
COMMAND LINE= /tmp/evaluation/195246-1168112433/VALCSP /tmp/evaluation/195246-1168112433/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node41/watcher-195246-1168112433 -o ROOT/results/node41/solver-195246-1168112433 -C 1800 -M 900  /tmp/evaluation/195246-1168112433/VALCSP /tmp/evaluation/195246-1168112433/unknown.xml

META MD5SUM SOLVER= 6fc756be3a7e45a17a81a19ce431bc48
MD5SUM BENCH=  b71c9e7325e6d9265cae682ae68d2699

RANDOM SEED= 127937725

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:       1521576 kB
Buffers:         23888 kB
Cached:         364732 kB
SwapCached:          0 kB
Active:         136132 kB
Inactive:       326900 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1521576 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:          207000 kB
Writeback:           0 kB
Mapped:          91216 kB
Slab:            56492 kB
Committed_AS:  2940580 kB
PageTables:       2056 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= 66305 MiB



End job on node41 on Sat Jan  6 19:40:35 UTC 2007