Trace number 287174

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
rjw-solver 2006-12-09? (problem) 0.038994 0.133706

General information on the benchmark

Namelard/
lard-89-89.xml
MD5SUM75d66e9edb073d20e5e74659e34b5dc8
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 benchmark22.1156
SatisfiableYES
(Un)Satisfiability was proved
Number of variables89
Number of constraints3916
Maximum constraint arity2
Maximum domain size90
Number of constraints which are defined in extension3916
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.13	error: unbound variable - ARR-ORIG-DOMAINS
0.13	> c 
c 
c 
c conversion script
c 
c

Verifier Data (download as text)

ERROR: Unexpected answer ! (SAT/UNSAT expected)
Got answer:

Watcher Data (download as text)

runsolver version 3.1.3 (c) roussel@cril.univ-artois.fr

command line: runsolver --timestamp -w ROOT/results/node60/watcher-287174-1170112348 -o ROOT/results/node60/solver-287174-1170112348 -C 1800 -M 900 /tmp/evaluation/287174-1170112348/solve /tmp/evaluation/287174-1170112348/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: 2.00 1.97 1.91 3/73 25973
/proc/meminfo: memFree=1453840/2055920 swapFree=4184188/4192956
[pid=25972] ppid=25970 vsize=5352 CPUtime=0
/proc/25972/stat : 25972 (solve) R 25970 25972 25284 0 -1 4194304 283 174 0 0 0 0 0 0 18 0 1 0 31252404 5480448 229 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 271894243999 0 65538 4100 65536 0 0 0 17 1 0 0
/proc/25972/statm: 1338 229 192 169 0 49 0
[pid=25975] ppid=25972 vsize=5352 CPUtime=0
/proc/25975/stat : 25975 (solve) R 25972 25972 25284 0 -1 4194368 16 0 0 0 0 0 0 0 18 0 1 0 31252404 5480448 229 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 271894089762 0 0 4100 65536 0 0 0 17 1 0 0
/proc/25975/statm: 1338 229 192 169 0 49 0

[startup+0.102499 s]
/proc/loadavg: 2.00 1.97 1.91 3/73 25973
/proc/meminfo: memFree=1453840/2055920 swapFree=4184188/4192956
[pid=25972] ppid=25970 vsize=5352 CPUtime=0
/proc/25972/stat : 25972 (solve) S 25970 25972 25284 0 -1 4194304 315 174 0 0 0 0 0 0 18 0 1 0 31252404 5480448 229 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 271894242116 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/25972/statm: 1338 229 192 169 0 49 0
[pid=25975] ppid=25972 vsize=3372 CPUtime=0
/proc/25975/stat : 25975 (xlisp) R 25972 25972 25284 0 -1 4194304 282 0 7 0 0 0 0 0 18 0 1 0 31252404 3452928 253 18446744073709551615 134512640 135322396 4294956848 18446744073709551615 134812500 0 0 4096 130 0 0 0 17 0 0 0
/proc/25975/statm: 843 253 186 197 0 83 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 8724

Child status: 0
Real time (s): 0.133706
CPU time (s): 0.038994
CPU user time (s): 0.025996
CPU system time (s): 0.012998
CPU usage (%): 29.164
Max. virtual memory (cumulated for all children) (KiB): 8724

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.025996
system time used= 0.012998
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 1097
page faults= 9
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 65
involuntary context switches= 17

runsolver used 0.001999 s user time and 0.006998 s system time

The end

Launcher Data (download as text)

Begin job on node60 on Mon Jan 29 23:12:31 UTC 2007


IDJOB= 287174
IDBENCH= 19807
IDSOLVER= 66
FILE ID= node60/287174-1170112348

PBS_JOBID= 3689966

Free space on /tmp= 66405 MiB

SOLVER NAME= rjw-solver 2006-12-09
BENCH NAME= HOME/pub/bench/CPAI06/lard/lard-89-89.xml
COMMAND LINE= /tmp/evaluation/287174-1170112348/solve /tmp/evaluation/287174-1170112348/unknown 1800
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node60/convwatcher-287174-1170112348 -o ROOT/results/node60/conversion-287174-1170112348 -C 600 -M 900 /tmp/evaluation/287174-1170112348/conversion /tmp/evaluation/287174-1170112348/unknown
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node60/watcher-287174-1170112348 -o ROOT/results/node60/solver-287174-1170112348 -C 1800 -M 900  /tmp/evaluation/287174-1170112348/solve /tmp/evaluation/287174-1170112348/unknown 1800

META MD5SUM SOLVER= 91bbaf997669a18b91ccd2f734d8d9ca
MD5SUM BENCH=  75d66e9edb073d20e5e74659e34b5dc8

RANDOM SEED= 988166647

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.283
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.283
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:       1455216 kB
Buffers:         32328 kB
Cached:         366848 kB
SwapCached:       1548 kB
Active:         436484 kB
Inactive:       120312 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1455216 kB
SwapTotal:     4192956 kB
SwapFree:      4184188 kB
Dirty:              16 kB
Writeback:           0 kB
Mapped:         165368 kB
Slab:            28804 kB
Committed_AS:   711120 kB
PageTables:       2352 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= 66405 MiB



End job on node60 on Mon Jan 29 23:22:36 UTC 2007