Trace number 269722

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.75673 1.77994

DiagnosticValue
CHECKS52402100
NODES29457

General information on the benchmark

Namelangford/
langford-3-11-ext.xml
MD5SUMf047fc038009e372113925ae5ca60f88
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.69774
SatisfiableNO
(Un)Satisfiability was proved
Number of variables33
Number of constraints550
Maximum constraint arity2
Maximum domain size33
Number of constraints which are defined in extension550
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

1.77	s UNSATISFIABLE
1.77	d CHECKS 5.24021e+07
1.77	d NODES 29457

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/node5/watcher-269722-1168982792 -o ROOT/results/node5/solver-269722-1168982792 -C 1800 -M 900 /tmp/evaluation/269722-1168982792/VALCSP /tmp/evaluation/269722-1168982792/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.72 1.93 1.89 5/86 9591
/proc/meminfo: memFree=1375976/2055920 swapFree=4192812/4192956
[pid=9590] ppid=9588 vsize=1600 CPUtime=0
/proc/9590/stat : 9590 (VALCSP) R 9588 9590 9496 0 -1 4194304 148 0 0 0 0 0 0 0 20 0 1 0 226893699 1638400 126 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 8331936 0 0 4096 0 0 0 0 17 1 0 0
/proc/9590/statm: 400 126 64 8 0 72 0

[startup+0.107542 s]
/proc/loadavg: 1.72 1.93 1.89 5/86 9591
/proc/meminfo: memFree=1375976/2055920 swapFree=4192812/4192956
[pid=9590] ppid=9588 vsize=3844 CPUtime=0.09
/proc/9590/stat : 9590 (VALCSP) R 9588 9590 9496 0 -1 4194304 723 0 0 0 9 0 0 0 20 0 1 0 226893699 3936256 701 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134535272 0 0 4096 0 0 0 0 17 1 0 0
/proc/9590/statm: 961 701 64 8 0 633 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 3844

[startup+0.516586 s]
/proc/loadavg: 1.72 1.93 1.89 5/86 9591
/proc/meminfo: memFree=1375976/2055920 swapFree=4192812/4192956
[pid=9590] ppid=9588 vsize=4240 CPUtime=0.49
/proc/9590/stat : 9590 (VALCSP) R 9588 9590 9496 0 -1 4194304 816 0 0 0 49 0 0 0 24 0 1 0 226893699 4341760 794 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134521042 0 0 4096 0 0 0 0 17 1 0 0
/proc/9590/statm: 1060 794 66 8 0 732 0
Current children cumulated CPU time (s) 0.49
Current children cumulated vsize (KiB) 4240

[startup+1.34468 s]
/proc/loadavg: 1.72 1.93 1.89 3/86 9591
/proc/meminfo: memFree=1372968/2055920 swapFree=4192812/4192956
[pid=9590] ppid=9588 vsize=4240 CPUtime=1.32
/proc/9590/stat : 9590 (VALCSP) R 9588 9590 9496 0 -1 4194304 816 0 0 0 132 0 0 0 25 0 1 0 226893699 4341760 794 18446744073709551615 134512640 134547260 4294956720 18446744073709551615 134520756 0 0 4096 0 0 0 0 17 1 0 0
/proc/9590/statm: 1060 794 66 8 0 732 0
Current children cumulated CPU time (s) 1.32
Current children cumulated vsize (KiB) 4240

Child status: 0
Real time (s): 1.77994
CPU time (s): 1.75673
CPU user time (s): 1.74973
CPU system time (s): 0.006998
CPU usage (%): 98.6963
Max. virtual memory (cumulated for all children) (KiB): 4240

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

runsolver used 0.005999 s user time and 0.007998 s system time

The end

Launcher Data (download as text)

Begin job on node5 on Tue Jan 16 21:26:33 UTC 2007


IDJOB= 269722
IDBENCH= 11649
IDSOLVER= 90
FILE ID= node5/269722-1168982792

PBS_JOBID= 3566063

Free space on /tmp= 66564 MiB

SOLVER NAME= VALCSP 3.1
BENCH NAME= HOME/pub/bench/CPAI06/langford/langford-3-11-ext.xml
COMMAND LINE= /tmp/evaluation/269722-1168982792/VALCSP /tmp/evaluation/269722-1168982792/unknown.xml
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node5/watcher-269722-1168982792 -o ROOT/results/node5/solver-269722-1168982792 -C 1800 -M 900  /tmp/evaluation/269722-1168982792/VALCSP /tmp/evaluation/269722-1168982792/unknown.xml

META MD5SUM SOLVER= d4fc2c4e0b0392ee9c79e754aa39e238
MD5SUM BENCH=  f047fc038009e372113925ae5ca60f88

RANDOM SEED= 144097854

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.240
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.240
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:       1376392 kB
Buffers:         49572 kB
Cached:         459204 kB
SwapCached:          0 kB
Active:         246776 kB
Inactive:       357600 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1376392 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:             436 kB
Writeback:           0 kB
Mapped:         115400 kB
Slab:            59904 kB
Committed_AS:  6304940 kB
PageTables:       2212 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 node5 on Tue Jan 16 21:26:35 UTC 2007