Trace number 205468

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
buggy_2_5_s 2007-01-08SAT 0.05699 0.068251

General information on the benchmark

Namehanoi/
hanoi-3_ext.xml
MD5SUM61eab57f9f916e4d1d75ade140564103
Bench Category2-ARY-EXT (binary constraints in extension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.002998
SatisfiableYES
(Un)Satisfiability was provedYES
Number of variables6
Number of constraints5
Maximum constraint arity2
Maximum domain size27
Number of constraints which are defined in extension5
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

c 
c 
c 
c solution file
c 
c 

SAT
2 5 4 22 21 24

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/node2/watcher-205468-1168701800 -o ROOT/results/node2/solver-205468-1168701800 -C 1800 -M 900 /tmp/evaluation/205468-1168701800/solver2 /tmp/evaluation/205468-1168701800/unknown 1800 

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.15 1.34 0.84 3/87 10833
/proc/meminfo: memFree=1563792/2055920 swapFree=4180552/4192956
[pid=10832] ppid=10830 vsize=780 CPUtime=0
/proc/10832/stat : 10832 (solver2) R 10830 10832 9427 0 -1 4194304 18 0 0 0 0 0 0 0 20 0 1 0 218575835 798720 3 18446744073709551615 0 0 548682070043 18446744073709551615 206381313319 0 0 4096 0 0 0 0 17 1 0 0
/proc/10832/statm: 195 3 0 0 0 6 0

Child status: 0
Real time (s): 0.068251
CPU time (s): 0.05699
CPU user time (s): 0.029995
CPU system time (s): 0.026995
CPU usage (%): 83.5006
Max. virtual memory (cumulated for all children) (KiB): 0

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.029995
system time used= 0.026995
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 3213
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= 73
involuntary context switches= 19

runsolver used 0.001999 s user time and 0.004999 s system time

The end

Launcher Data (download as text)

Begin job on node2 on Sat Jan 13 15:23:21 UTC 2007


IDJOB= 205468
IDBENCH= 4132
IDSOLVER= 82
FILE ID= node2/205468-1168701800

PBS_JOBID= 3547034

Free space on /tmp= 66553 MiB

SOLVER NAME= buggy_2_5_s 2007-01-08
BENCH NAME= HOME/pub/bench/CPAI06/hanoi/hanoi-3_ext.xml
COMMAND LINE= /tmp/evaluation/205468-1168701800/solver2 /tmp/evaluation/205468-1168701800/unknown 1800
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node2/watcher-205468-1168701800 -o ROOT/results/node2/solver-205468-1168701800 -C 1800 -M 900  /tmp/evaluation/205468-1168701800/solver2 /tmp/evaluation/205468-1168701800/unknown 1800

META MD5SUM SOLVER= 2182e29fee250f6e45b9a85a6429fa3a
MD5SUM BENCH=  61eab57f9f916e4d1d75ade140564103

RANDOM SEED= 925476644

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.259
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	: 5931.00
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.259
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:       1564272 kB
Buffers:         17196 kB
Cached:         147904 kB
SwapCached:        548 kB
Active:         332152 kB
Inactive:        98888 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1564272 kB
SwapTotal:     4192956 kB
SwapFree:      4180552 kB
Dirty:           10628 kB
Writeback:           0 kB
Mapped:         278308 kB
Slab:            44896 kB
Committed_AS:  6342180 kB
PageTables:       2820 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= 66553 MiB



End job on node2 on Sat Jan 13 15:23:23 UTC 2007