Trace number 287333

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
Diarmuid-rndi 2006-12-21? (problem) 0.039993 0.170518

General information on the benchmark

Namelard/
lard-88-88.xml
MD5SUMc30789c20fabc1aa3a4853b54ec1164c
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 benchmark21.1418
SatisfiableYES
(Un)Satisfiability was proved
Number of variables88
Number of constraints3828
Maximum constraint arity2
Maximum domain size89
Number of constraints which are defined in extension3828
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

0.16	error: unbound variable - ARR-ORIG-DOMAINS
0.16	> 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/node34/watcher-287333-1170113157 -o ROOT/results/node34/solver-287333-1170113157 -C 1800 -M 900 /tmp/evaluation/287333-1170113157/solver 

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: 0.81 1.61 2.60 4/68 27906
/proc/meminfo: memFree=1822448/2055920 swapFree=4192812/4192956
[pid=27905] ppid=27903 vsize=5352 CPUtime=0
/proc/27905/stat : 27905 (solver) S 27903 27905 27039 0 -1 4194304 280 0 0 0 0 0 0 0 18 0 1 0 5142495 5480448 229 18446744073709551615 4194304 4889804 548682069408 18446744073709551615 254195327812 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/27905/statm: 1338 229 192 169 0 49 0
[pid=27907] ppid=27905 vsize=5352 CPUtime=0
/proc/27907/stat : 27907 (solver) D 27905 27905 27039 0 -1 4194368 18 0 0 0 0 0 0 0 18 0 1 0 5142495 5480448 229 18446744073709551615 4194304 4889804 548682069408 18446744073709551615 254195330343 0 0 4096 0 18446744071563608240 0 0 17 1 0 0
/proc/27907/statm: 1338 229 192 169 0 49 0

[startup+0.105536 s]
/proc/loadavg: 0.81 1.61 2.60 4/68 27906
/proc/meminfo: memFree=1822448/2055920 swapFree=4192812/4192956
[pid=27905] ppid=27903 vsize=5352 CPUtime=0
/proc/27905/stat : 27905 (solver) S 27903 27905 27039 0 -1 4194304 314 174 0 0 0 0 0 0 16 0 1 0 5142495 5480448 229 18446744073709551615 4194304 4889804 548682069408 18446744073709551615 254195327812 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/27905/statm: 1338 229 192 169 0 49 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 5352

Child status: 0
Real time (s): 0.170518
CPU time (s): 0.039993
CPU user time (s): 0.026995
CPU system time (s): 0.012998
CPU usage (%): 23.4538
Max. virtual memory (cumulated for all children) (KiB): 5352

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.026995
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= 1088
page faults= 13
swaps= 0
block input operations= 0
block output operations= 0
messages sent= 0
messages received= 0
signals received= 0
voluntary context switches= 70
involuntary context switches= 9

runsolver used 0.001999 s user time and 0.005999 s system time

The end

Launcher Data (download as text)

Begin job on node34 on Mon Jan 29 23:26:01 UTC 2007


IDJOB= 287333
IDBENCH= 19814
IDSOLVER= 63
FILE ID= node34/287333-1170113157

PBS_JOBID= 3690212

Free space on /tmp= 50749 MiB

SOLVER NAME= Diarmuid-rndi 2006-12-21
BENCH NAME= HOME/pub/bench/CPAI06/lard/lard-88-88.xml
COMMAND LINE= /tmp/evaluation/287333-1170113157/solver
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node34/convwatcher-287333-1170113157 -o ROOT/results/node34/conversion-287333-1170113157 -C 600 -M 900 /tmp/evaluation/287333-1170113157/conversion /tmp/evaluation/287333-1170113157/unknown
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node34/watcher-287333-1170113157 -o ROOT/results/node34/solver-287333-1170113157 -C 1800 -M 900  /tmp/evaluation/287333-1170113157/solver

META MD5SUM SOLVER= b57068d1450403a75f014042200261c5
MD5SUM BENCH=  c30789c20fabc1aa3a4853b54ec1164c

RANDOM SEED= 755991947

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.234
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.234
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:       1822736 kB
Buffers:         21144 kB
Cached:         144164 kB
SwapCached:          0 kB
Active:          46544 kB
Inactive:       139300 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1822736 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:              28 kB
Writeback:           0 kB
Mapped:          30712 kB
Slab:            32936 kB
Committed_AS:   378188 kB
PageTables:       1596 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= 66483 MiB



End job on node34 on Mon Jan 29 23:36:48 UTC 2007