Trace number 201964

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 2007-01-08UNSAT 0.183972 0.18868

General information on the benchmark

Namecomposed/composed-25-1-80/
composed-25-1-80-2_ext.xml
MD5SUMab1eefca7324098cbdabf6af7190d8e1
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 benchmark0.027995
SatisfiableNO
(Un)Satisfiability was provedNO
Number of variables33
Number of constraints302
Maximum constraint arity2
Maximum domain size10
Number of constraints which are defined in extension302
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 

UNSAT

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/node11/watcher-201964-1168701776 -o ROOT/results/node11/solver-201964-1168701776 -C 1800 -M 900 /tmp/evaluation/201964-1168701776/solver /tmp/evaluation/201964-1168701776/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.55 1.52 0.92 5/87 2831
/proc/meminfo: memFree=1576328/2055920 swapFree=4171812/4192956
[pid=2830] ppid=2828 vsize=5352 CPUtime=0
/proc/2830/stat : 2830 (solver) R 2828 2830 32479 0 -1 4194304 313 190 0 0 0 0 0 0 19 0 1 0 218572858 5480448 241 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 262910044831 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/2830/statm: 1338 241 202 169 0 49 0
[pid=2834] ppid=2830 vsize=0 CPUtime=0
/proc/2834/stat : 2834 (solver) R 2830 2830 32479 0 -1 4194368 21 0 0 0 0 0 0 0 19 0 1 0 218572859 0 0 18446744073709551615 0 0 0 18446744073709551615 262910045479 0 0 4096 0 0 0 0 17 1 0 0
/proc/2834/statm: 0 0 0 0 0 0 0

[startup+0.107707 s]
/proc/loadavg: 1.55 1.52 0.92 5/87 2831
/proc/meminfo: memFree=1576328/2055920 swapFree=4171812/4192956
[pid=2830] ppid=2828 vsize=5352 CPUtime=0.03
/proc/2830/stat : 2830 (solver) S 2828 2830 32479 0 -1 4194304 376 2239 0 0 0 0 1 2 19 0 1 0 218572858 5480448 242 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 262910042948 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/2830/statm: 1338 242 203 169 0 49 0
Current children cumulated CPU time (s) 0.03
Current children cumulated vsize (KiB) 5352

Child status: 0
Real time (s): 0.18868
CPU time (s): 0.183972
CPU user time (s): 0.124981
CPU system time (s): 0.058991
CPU usage (%): 97.5047
Max. virtual memory (cumulated for all children) (KiB): 5352

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.124981
system time used= 0.058991
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 3482
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= 77
involuntary context switches= 23

runsolver used 0.005999 s user time and 0.004999 s system time

The end

Launcher Data (download as text)

Begin job on node11 on Sat Jan 13 15:22:58 UTC 2007


IDJOB= 201964
IDBENCH= 3794
IDSOLVER= 83
FILE ID= node11/201964-1168701776

PBS_JOBID= 3547031

Free space on /tmp= 66552 MiB

SOLVER NAME= buggy_2_5 2007-01-08
BENCH NAME= HOME/pub/bench/CPAI06/composed/composed-25-1-80/composed-25-1-80-2_ext.xml
COMMAND LINE= /tmp/evaluation/201964-1168701776/solver /tmp/evaluation/201964-1168701776/unknown 1800
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node11/watcher-201964-1168701776 -o ROOT/results/node11/solver-201964-1168701776 -C 1800 -M 900  /tmp/evaluation/201964-1168701776/solver /tmp/evaluation/201964-1168701776/unknown 1800

META MD5SUM SOLVER= 6c84d9851726bfff2e2bc2bb5530c705
MD5SUM BENCH=  ab1eefca7324098cbdabf6af7190d8e1

RANDOM SEED= 109301634

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.261
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.261
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:       1576936 kB
Buffers:         10216 kB
Cached:         149008 kB
SwapCached:       2684 kB
Active:         329832 kB
Inactive:        88344 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1576936 kB
SwapTotal:     4192956 kB
SwapFree:      4171812 kB
Dirty:           11824 kB
Writeback:           0 kB
Mapped:         277232 kB
Slab:            45056 kB
Committed_AS:  7338876 kB
PageTables:       2816 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= 66552 MiB



End job on node11 on Sat Jan 13 15:22:59 UTC 2007