Trace number 224765

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.0UNSAT 2.80557 2.83279

DiagnosticValue
CHECKS63798200
NODES1034

General information on the benchmark

Nametightness/tightness0.8/
rand-2-40-80-103-800-35_ext.xml
MD5SUM62fdf3dcfed7f5799c512f31618b4411
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark1.9827
SatisfiableNO
(Un)Satisfiability was provedNO
Number of variables40
Number of constraints103
Maximum constraint arity2
Maximum domain size80
Number of constraints which are defined in extension103
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

2.83	s UNSATISFIABLE
2.83	d CHECKS 6.37982e+07
2.83	d NODES 1034
2.83

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/node4/watcher-224765-1168269776 -o ROOT/results/node4/solver-224765-1168269776 -C 1800 -M 900 /tmp/evaluation/224765-1168269776/VALCSP /tmp/evaluation/224765-1168269776/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.24 2.39 2.30 5/94 29142
/proc/meminfo: memFree=1077160/2055920 swapFree=4182144/4192956
[pid=29141] ppid=29139 vsize=1468 CPUtime=0
/proc/29141/stat : 29141 (VALCSP) R 29139 29141 28644 0 -1 4194304 124 0 0 0 0 0 0 0 20 0 1 0 175373167 1503232 102 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 11027989 0 0 4096 0 0 0 0 17 1 0 0
/proc/29141/statm: 367 102 62 8 0 39 0

[startup+0.105329 s]
/proc/loadavg: 2.24 2.39 2.30 5/94 29142
/proc/meminfo: memFree=1077160/2055920 swapFree=4182144/4192956
[pid=29141] ppid=29139 vsize=1732 CPUtime=0.09
/proc/29141/stat : 29141 (VALCSP) R 29139 29141 28644 0 -1 4194304 176 0 0 0 9 0 0 0 20 0 1 0 175373167 1773568 154 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 11048071 0 0 4096 0 0 0 0 17 1 0 0
/proc/29141/statm: 433 154 62 8 0 105 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 1732

[startup+0.513367 s]
/proc/loadavg: 2.24 2.39 2.30 5/94 29142
/proc/meminfo: memFree=1077160/2055920 swapFree=4182144/4192956
[pid=29141] ppid=29139 vsize=2656 CPUtime=0.5
/proc/29141/stat : 29141 (VALCSP) R 29139 29141 28644 0 -1 4194304 413 0 0 0 50 0 0 0 24 0 1 0 175373167 2719744 391 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 11048012 0 0 4096 0 0 0 0 17 1 0 0
/proc/29141/statm: 664 391 62 8 0 336 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 2656

[startup+1.33445 s]
/proc/loadavg: 2.30 2.40 2.30 4/94 29142
/proc/meminfo: memFree=1074408/2055920 swapFree=4182144/4192956
[pid=29141] ppid=29139 vsize=4512 CPUtime=1.31
/proc/29141/stat : 29141 (VALCSP) R 29139 29141 28644 0 -1 4194304 880 0 0 0 131 0 0 0 25 0 1 0 175373167 4620288 858 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 11048097 0 0 4096 0 0 0 0 17 1 0 0
/proc/29141/statm: 1128 858 62 8 0 800 0
Current children cumulated CPU time (s) 1.31
Current children cumulated vsize (KiB) 4512

Child status: 0
Real time (s): 2.83279
CPU time (s): 2.80557
CPU user time (s): 2.78957
CPU system time (s): 0.015997
CPU usage (%): 99.0393
Max. virtual memory (cumulated for all children) (KiB): 8340

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

runsolver used 0.005999 s user time and 0.011998 s system time

The end

Launcher Data (download as text)

Begin job on node4 on Mon Jan  8 15:22:56 UTC 2007


IDJOB= 224765
IDBENCH= 5791
FILE ID= node4/224765-1168269776

PBS_JOBID= 3482979

Free space on /tmp= 66309 MiB

BENCH NAME= HOME/pub/bench/CPAI06/tightness/tightness0.8/rand-2-40-80-103-800-35_ext.xml
COMMAND LINE= /tmp/evaluation/224765-1168269776/VALCSP /tmp/evaluation/224765-1168269776/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node4/watcher-224765-1168269776 -o ROOT/results/node4/solver-224765-1168269776 -C 1800 -M 900  /tmp/evaluation/224765-1168269776/VALCSP /tmp/evaluation/224765-1168269776/unknown.xml

META MD5SUM SOLVER= 6fc756be3a7e45a17a81a19ce431bc48
MD5SUM BENCH=  62fdf3dcfed7f5799c512f31618b4411

RANDOM SEED= 750905937

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.223
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.223
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:       1077640 kB
Buffers:         62220 kB
Cached:         216408 kB
SwapCached:       2552 kB
Active:         804624 kB
Inactive:       116112 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1077640 kB
SwapTotal:     4192956 kB
SwapFree:      4182144 kB
Dirty:            1004 kB
Writeback:           0 kB
Mapped:         658176 kB
Slab:            40916 kB
Committed_AS:  5679496 kB
PageTables:       3640 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= 66309 MiB



End job on node4 on Mon Jan  8 15:22:59 UTC 2007