Trace number 268629

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.1UNSAT 1.3068 1.31686

DiagnosticValue
CHECKS44457700
NODES2638

General information on the benchmark

Namerlfap/rlfapScensMod/
scen3-f11.xml
MD5SUM47d964f6bb88215eaa595d2ffc780e97
Bench Category2-ARY-INT (binary constraints in intension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark1.51377
SatisfiableNO
(Un)Satisfiability was provedNO
Number of variables400
Number of constraints2760
Maximum constraint arity2
Maximum domain size33
Number of constraints which are defined in extension0
Number of constraints which are defined in intension2760
Global constraints used (with number of constraints)

Solver Data (download as text)

1.31	s UNSATISFIABLE
1.31	d CHECKS 4.44577e+07
1.31	d NODES 2638

Verifier Data (download as text)

No possible verification on an UNSAT instance

Watcher Data (download as text)

runsolver version 3.1.3 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node70/watcher-268629-1168979662 -o ROOT/results/node70/solver-268629-1168979662 -C 1800 -M 900 /tmp/evaluation/268629-1168979662/VALCSP /tmp/evaluation/268629-1168979662/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: 2.01 1.99 1.65 5/73 11324
/proc/meminfo: memFree=1355600/2055920 swapFree=4192956/4192956
[pid=11323] ppid=11321 vsize=1996 CPUtime=0
/proc/11323/stat : 11323 (VALCSP) R 11321 11323 10780 0 -1 4194304 254 0 0 0 0 0 0 0 20 0 1 0 45463145 2043904 232 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 8849019 0 0 4096 0 0 0 0 17 1 0 0
/proc/11323/statm: 499 232 64 8 0 171 0

[startup+0.105105 s]
/proc/loadavg: 2.01 1.99 1.65 5/73 11324
/proc/meminfo: memFree=1355600/2055920 swapFree=4192956/4192956
[pid=11323] ppid=11321 vsize=6940 CPUtime=0.09
/proc/11323/stat : 11323 (VALCSP) R 11321 11323 10780 0 -1 4194304 1456 0 0 0 9 0 0 0 20 0 1 0 45463145 7106560 1434 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 134528694 0 0 4096 0 0 0 0 17 1 0 0
/proc/11323/statm: 1735 1434 64 8 0 1407 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 6940

[startup+0.513145 s]
/proc/loadavg: 2.01 1.99 1.65 5/73 11324
/proc/meminfo: memFree=1355600/2055920 swapFree=4192956/4192956
[pid=11323] ppid=11321 vsize=17180 CPUtime=0.5
/proc/11323/stat : 11323 (VALCSP) R 11321 11323 10780 0 -1 4194304 4040 0 0 0 49 1 0 0 23 0 1 0 45463145 17592320 4018 18446744073709551615 134512640 134547260 4294956736 18446744073709551615 134524815 0 0 4096 0 0 0 0 17 1 0 0
/proc/11323/statm: 4295 4018 66 8 0 3967 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 17180

Child status: 0
Real time (s): 1.31686
CPU time (s): 1.3068
CPU user time (s): 1.2898
CPU system time (s): 0.016997
CPU usage (%): 99.2364
Max. virtual memory (cumulated for all children) (KiB): 17180

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

runsolver used 0.002999 s user time and 0.010998 s system time

The end

Launcher Data (download as text)

Begin job on node70 on Tue Jan 16 20:34:22 UTC 2007


IDJOB= 268629
IDBENCH= 5088
IDSOLVER= 90
FILE ID= node70/268629-1168979662

PBS_JOBID= 3566121

Free space on /tmp= 66564 MiB

SOLVER NAME= VALCSP 3.1
BENCH NAME= HOME/pub/bench/CPAI06/rlfap/rlfapScensMod/scen3-f11.xml
COMMAND LINE= /tmp/evaluation/268629-1168979662/VALCSP /tmp/evaluation/268629-1168979662/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node70/watcher-268629-1168979662 -o ROOT/results/node70/solver-268629-1168979662 -C 1800 -M 900  /tmp/evaluation/268629-1168979662/VALCSP /tmp/evaluation/268629-1168979662/unknown.xml

META MD5SUM SOLVER= d4fc2c4e0b0392ee9c79e754aa39e238
MD5SUM BENCH=  47d964f6bb88215eaa595d2ffc780e97

RANDOM SEED= 857943124

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:       1356016 kB
Buffers:         45100 kB
Cached:         555136 kB
SwapCached:          0 kB
Active:         107052 kB
Inactive:       518728 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1356016 kB
SwapTotal:     4192956 kB
SwapFree:      4192956 kB
Dirty:             404 kB
Writeback:           0 kB
Mapped:          36532 kB
Slab:            59660 kB
Committed_AS:   436652 kB
PageTables:       1712 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 node70 on Tue Jan 16 20:34:24 UTC 2007