Trace number 268005

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.1SAT 0.492924 0.500746

DiagnosticValue
CHECKS2025060
NODES400

General information on the benchmark

Namerlfap/rlfapGraphs/
graph2.xml
MD5SUM047e2db4d84b7d874b43ae4e45dd9fec
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.830873
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables400
Number of constraints2245
Maximum constraint arity2
Maximum domain size44
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.49	s SATISFIABLE
0.49	v 254 16 128 366 254 16 296 58 114 352 72 310 324 86 16 254 44 282 338 100 338 100 156 394 44 282 352 114 296 58 58 296 394 156 310 72 72 310 338 100 16 254 310 72 30 268 254 16 30 268 128 366 380 142 58 296 30 268 324 86 100 338 30 268 324 86 414 652 44 282 142 380 58 296 366 128 72 310 324 86 254 16 324 86 58 296 72 310 394 156 282 44 30 268 86 324 86 324 30 268 296 58 16 254 156 394 58 296 30 268 324 86 310 72 16 254 128 366 142 380 268 30 394 156 58 296 128 366 142 380 16 254 254 16 380 142 428 666 352 114 428 666 268 30 86 324 86 324 366 128 16 254 16 254 142 380 86 324 16 254 680 442 380 142 114 352 30 268 114 352 86 324 338 100 296 58 268 30 142 380 30 268 470 708 428 666 44 282 142 380 282 44 86 324 296 58 16 254 310 72 86 324 296 58 428 666 268 30 100 338 86 324 142 380 254 16 72 310 268 30 366 128 44 282 86 324 380 142 128 366 254 16 128 366 114 352 282 44 58 296 414 652 30 268 86 324 380 142 428 666 254 16 86 324 142 380 310 72 380 142 254 16 142 380 142 380 296 58 44 282 296 58 72 310 86 324 268 30 498 736 428 666 324 86 142 380 310 72 86 324 380 142 380 142 352 114 380 142 380 142 414 652 16 254 30 268 414 652 380 142 142 380 142 380 44 282 142 380 338 100 128 366 30 268 414 652 58 296 310 72 268 30 44 282 114 352 30 268 380 142 268 30 310 72 310 72 30 268 142 380 142 380 100 338 114 352 310 72 324 86 666 428 324 86 456 694 414 652 366 128 414 652 128 366 254 16 30 268 394 156 296 58 114 352 30 268 324 86 128 366 310 72 114 352 366 128 16 254 72 310 
0.49	d CHECKS 2.02506e+06
0.49	d NODES 400

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/node33/watcher-268005-1168977863 -o ROOT/results/node33/solver-268005-1168977863 -C 1800 -M 900 /tmp/evaluation/268005-1168977863/VALCSP /tmp/evaluation/268005-1168977863/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


[startup+0.105847 s]
/proc/loadavg: 0.37 0.09 0.03 5/73 19834
/proc/meminfo: memFree=1369360/2055920 swapFree=4192224/4192956
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 0
/proc/loadavg: 0.37 0.09 0.03 5/73 19834
/proc/meminfo: memFree=1369360/2055920 swapFree=4192224/4192956
[pid=19833] ppid=19831 vsize=6880 CPUtime=0.09
/proc/19833/stat : 19833 (VALCSP) R 19831 19833 19472 0 -1 4194304 1463 0 0 0 9 0 0 0 20 0 1 0 246180765 7045120 1441 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 134528604 0 0 4096 0 0 0 0 17 1 0 0
/proc/19833/statm: 1720 1441 64 8 0 1392 0

Child status: 0
Real time (s): 0.500746
CPU time (s): 0.492924
CPU user time (s): 0.470928
CPU system time (s): 0.021996
CPU usage (%): 98.438
Max. virtual memory (cumulated for all children) (KiB): 16820

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

runsolver used 0.001999 s user time and 0.006998 s system time

The end

Launcher Data (download as text)

Begin job on node33 on Tue Jan 16 20:04:29 UTC 2007


IDJOB= 268005
IDBENCH= 3290
IDSOLVER= 90
FILE ID= node33/268005-1168977863

PBS_JOBID= 3566177

Free space on /tmp= 66564 MiB

SOLVER NAME= VALCSP 3.1
BENCH NAME= HOME/pub/bench/CPAI06/rlfap/rlfapGraphs/graph2.xml
COMMAND LINE= /tmp/evaluation/268005-1168977863/VALCSP /tmp/evaluation/268005-1168977863/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node33/watcher-268005-1168977863 -o ROOT/results/node33/solver-268005-1168977863 -C 1800 -M 900  /tmp/evaluation/268005-1168977863/VALCSP /tmp/evaluation/268005-1168977863/unknown.xml

META MD5SUM SOLVER= d4fc2c4e0b0392ee9c79e754aa39e238
MD5SUM BENCH=  047e2db4d84b7d874b43ae4e45dd9fec

RANDOM SEED= 358653685

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.281
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.281
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:       1370736 kB
Buffers:         49520 kB
Cached:         535284 kB
SwapCached:        268 kB
Active:         112436 kB
Inactive:       496300 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1370736 kB
SwapTotal:     4192956 kB
SwapFree:      4192224 kB
Dirty:             924 kB
Writeback:           0 kB
Mapped:          34432 kB
Slab:            61996 kB
Committed_AS:  4246252 kB
PageTables:       1728 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 node33 on Tue Jan 16 20:04:35 UTC 2007