Trace number 229034

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.66659 2.66815

DiagnosticValue
CHECKS83050600
NODES18762

General information on the benchmark

Nametightness/tightness0.35/
rand-2-40-16-250-350-41_ext.xml
MD5SUM74df457be90ea7a152f59268da62bd6f
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 benchmark2.66659
SatisfiableNO
(Un)Satisfiability was provedNO
Number of variables40
Number of constraints250
Maximum constraint arity2
Maximum domain size16
Number of constraints which are defined in extension250
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

2.66	s UNSATISFIABLE
2.66	d CHECKS 8.30506e+07
2.66	d NODES 18762
2.66

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/node14/watcher-229034-1168303298 -o ROOT/results/node14/solver-229034-1168303298 -C 1800 -M 900 /tmp/evaluation/229034-1168303298/VALCSP /tmp/evaluation/229034-1168303298/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.01 1.02 1.12 4/78 9371
/proc/meminfo: memFree=1718392/2055920 swapFree=4163780/4192956
[pid=9370] ppid=9368 vsize=1468 CPUtime=0
/proc/9370/stat : 9370 (VALCSP) R 9368 9370 7370 0 -1 4194304 120 0 0 0 0 0 0 0 18 0 1 0 178724704 1503232 98 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 4294960144 0 0 4096 0 0 0 0 17 1 0 0
/proc/9370/statm: 367 98 62 8 0 39 0

[startup+0.104165 s]
/proc/loadavg: 1.01 1.02 1.12 4/78 9371
/proc/meminfo: memFree=1718392/2055920 swapFree=4163780/4192956
[pid=9370] ppid=9368 vsize=2656 CPUtime=0.1
/proc/9370/stat : 9370 (VALCSP) R 9368 9370 7370 0 -1 4194304 412 0 0 0 10 0 0 0 18 0 1 0 178724704 2719744 390 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134524623 0 0 4096 0 0 0 0 17 1 0 0
/proc/9370/statm: 664 390 65 8 0 336 0
Current children cumulated CPU time (s) 0.1
Current children cumulated vsize (KiB) 2656

[startup+0.514202 s]
/proc/loadavg: 1.01 1.02 1.12 4/78 9371
/proc/meminfo: memFree=1718392/2055920 swapFree=4163780/4192956
[pid=9370] ppid=9368 vsize=2656 CPUtime=0.51
/proc/9370/stat : 9370 (VALCSP) R 9368 9370 7370 0 -1 4194304 412 0 0 0 51 0 0 0 22 0 1 0 178724704 2719744 390 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134524776 0 0 4096 0 0 0 0 17 1 0 0
/proc/9370/statm: 664 390 65 8 0 336 0
Current children cumulated CPU time (s) 0.51
Current children cumulated vsize (KiB) 2656

[startup+1.33828 s]
/proc/loadavg: 1.01 1.02 1.12 2/78 9371
/proc/meminfo: memFree=1717048/2055920 swapFree=4163780/4192956
[pid=9370] ppid=9368 vsize=2656 CPUtime=1.33
/proc/9370/stat : 9370 (VALCSP) R 9368 9370 7370 0 -1 4194304 412 0 0 0 133 0 0 0 25 0 1 0 178724704 2719744 390 18446744073709551615 134512640 134548440 4294956720 18446744073709551615 134524853 0 0 4096 0 0 0 0 17 1 0 0
/proc/9370/statm: 664 390 65 8 0 336 0
Current children cumulated CPU time (s) 1.33
Current children cumulated vsize (KiB) 2656

Child status: 0
Real time (s): 2.66815
CPU time (s): 2.66659
CPU user time (s): 2.66459
CPU system time (s): 0.001999
CPU usage (%): 99.9418
Max. virtual memory (cumulated for all children) (KiB): 2656

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

runsolver used 0.005999 s user time and 0.008998 s system time

The end

Launcher Data (download as text)

Begin job on node14 on Tue Jan  9 00:41:38 UTC 2007


IDJOB= 229034
IDBENCH= 6268
FILE ID= node14/229034-1168303298

PBS_JOBID= 3502215

Free space on /tmp= 66346 MiB

BENCH NAME= HOME/pub/bench/CPAI06/tightness/tightness0.35/rand-2-40-16-250-350-41_ext.xml
COMMAND LINE= /tmp/evaluation/229034-1168303298/VALCSP /tmp/evaluation/229034-1168303298/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node14/watcher-229034-1168303298 -o ROOT/results/node14/solver-229034-1168303298 -C 1800 -M 900  /tmp/evaluation/229034-1168303298/VALCSP /tmp/evaluation/229034-1168303298/unknown.xml

META MD5SUM SOLVER= 6fc756be3a7e45a17a81a19ce431bc48
MD5SUM BENCH=  74df457be90ea7a152f59268da62bd6f

RANDOM SEED= 183443022

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.227
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.227
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:       1718808 kB
Buffers:         41836 kB
Cached:         226584 kB
SwapCached:       4056 kB
Active:         160732 kB
Inactive:       137700 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1718808 kB
SwapTotal:     4192956 kB
SwapFree:      4163780 kB
Dirty:             228 kB
Writeback:           0 kB
Mapped:          38540 kB
Slab:            24188 kB
Committed_AS:  5923736 kB
PageTables:       1804 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= 66346 MiB



End job on node14 on Tue Jan  9 00:41:40 UTC 2007