Trace number 201759

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.298953 0.306355

DiagnosticValue
CHECKS851390
NODES200

General information on the benchmark

Namerlfap/rlfapScens/
scen2.xml
MD5SUM6fd929da3fdebf81252e0d9d01639132
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.480926
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables200
Number of constraints1235
Maximum constraint arity2
Maximum domain size44
Number of constraints which are defined in extension0
Number of constraints which are defined in intension1235
Global constraints used (with number of constraints)

Solver Data (download as text)

0.30	s SATISFIABLE
0.30	v 394 156 394 156 30 268 254 16 86 324 114 352 254 16 16 254 324 86 414 652 414 652 268 30 100 338 30 268 30 268 16 254 16 254 254 16 324 86 254 16 254 16 338 100 338 100 254 16 394 156 394 156 44 282 86 324 16 254 352 114 428 666 366 128 352 114 414 652 16 254 484 722 484 722 380 142 114 352 30 268 44 282 58 296 100 338 30 268 58 296 44 282 100 338 352 114 268 30 16 254 16 254 142 380 44 282 100 338 16 254 30 268 352 114 282 44 366 128 58 296 352 114 268 30 30 268 310 72 30 268 282 44 268 30 428 666 86 324 30 268 44 282 44 282 366 128 156 394 30 268 16 254 16 254 142 380 16 254 254 16 338 100 268 30 86 324 414 652 30 268 128 366 100 338 100 338 366 128 16 254 338 100 86 324 268 30 100 338 30 268 100 338 30 268 100 338 128 366 30 268 
0.30	d CHECKS 851390
0.30	d NODES 200
0.30

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/node39/watcher-201759-1168149632 -o ROOT/results/node39/solver-201759-1168149632 -C 1800 -M 900 /tmp/evaluation/201759-1168149632/VALCSP /tmp/evaluation/201759-1168149632/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.92 1.98 1.93 5/74 11985
/proc/meminfo: memFree=1384008/2055920 swapFree=4187312/4192956
[pid=11984] ppid=11982 vsize=2128 CPUtime=0
/proc/11984/stat : 11984 (VALCSP) R 11982 11984 11320 0 -1 4194304 264 0 0 0 0 0 0 0 20 0 1 0 163362905 2179072 242 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 11527770 0 0 4096 0 0 0 0 17 1 0 0
/proc/11984/statm: 532 242 62 8 0 204 0

[startup+0.105667 s]
/proc/loadavg: 1.92 1.98 1.93 5/74 11985
/proc/meminfo: memFree=1384008/2055920 swapFree=4187312/4192956
[pid=11984] ppid=11982 vsize=5428 CPUtime=0.09
/proc/11984/stat : 11984 (VALCSP) R 11982 11984 11320 0 -1 4194304 1088 0 0 0 9 0 0 0 20 0 1 0 163362905 5558272 1066 18446744073709551615 134512640 134548440 4294956736 18446744073709551615 134530537 0 0 4096 0 0 0 0 17 1 0 0
/proc/11984/statm: 1357 1066 64 8 0 1029 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 5428

Child status: 0
Real time (s): 0.306355
CPU time (s): 0.298953
CPU user time (s): 0.284956
CPU system time (s): 0.013997
CPU usage (%): 97.5839
Max. virtual memory (cumulated for all children) (KiB): 8860

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

runsolver used 0.003999 s user time and 0.004999 s system time

The end

Launcher Data (download as text)

Begin job on node39 on Sun Jan  7 06:00:33 UTC 2007


IDJOB= 201759
IDBENCH= 3782
FILE ID= node39/201759-1168149632

PBS_JOBID= 3478144

Free space on /tmp= 66548 MiB

BENCH NAME= HOME/pub/bench/CPAI06/rlfap/rlfapScens/scen2.xml
COMMAND LINE= /tmp/evaluation/201759-1168149632/VALCSP /tmp/evaluation/201759-1168149632/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node39/watcher-201759-1168149632 -o ROOT/results/node39/solver-201759-1168149632 -C 1800 -M 900  /tmp/evaluation/201759-1168149632/VALCSP /tmp/evaluation/201759-1168149632/unknown.xml

META MD5SUM SOLVER= 6fc756be3a7e45a17a81a19ce431bc48
MD5SUM BENCH=  6fd929da3fdebf81252e0d9d01639132

RANDOM SEED= 340244439

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.236
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.236
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:       1384424 kB
Buffers:         34584 kB
Cached:         444492 kB
SwapCached:       1548 kB
Active:         280120 kB
Inactive:       332252 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1384424 kB
SwapTotal:     4192956 kB
SwapFree:      4187312 kB
Dirty:             296 kB
Writeback:           0 kB
Mapped:         141636 kB
Slab:            44396 kB
Committed_AS:  3477628 kB
PageTables:       2016 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= 66548 MiB



End job on node39 on Sun Jan  7 06:00:33 UTC 2007