Trace number 283171

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 2007-01-21UNSAT 1.27081 1.2831

DiagnosticValue
CHECKS127225
NODES5

General information on the benchmark

Nameehi/ehi-85/
ehi-85-297-43_ext.xml
MD5SUMa34777e1c99afaa7639f38cb2fbceb0f
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.085986
SatisfiableNO
(Un)Satisfiability was provedNO
Number of variables297
Number of constraints4111
Maximum constraint arity2
Maximum domain size7
Number of constraints which are defined in extension4111
Number of constraints which are defined in intension0
Global constraints used (with number of constraints)

Solver Data (download as text)

1.28	s UNSATISFIABLE
1.28	d NODES 5
1.28	d CHECKS 127225
c 
c 
c 
c conversion script
c 
c

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/node66/watcher-283171-1169466743 -o ROOT/results/node66/solver-283171-1169466743 -C 1800 -M 900 /tmp/evaluation/283171-1169466743/solve /tmp/evaluation/283171-1169466743/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: 0.54 0.24 0.61 5/75 27903
/proc/meminfo: memFree=1808352/2055920 swapFree=4183744/4192956
[pid=27902] ppid=27900 vsize=5352 CPUtime=0
/proc/27902/stat : 27902 (solve) S 27900 27902 27501 0 -1 4194304 280 0 0 0 0 0 0 0 18 0 1 0 94173804 5480448 229 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 227607634756 0 65536 4100 65538 18446744071563356171 0 0 17 1 0 0
/proc/27902/statm: 1338 229 192 169 0 49 0
[pid=27904] ppid=27902 vsize=164 CPUtime=0
/proc/27904/stat : 27904 (cp) R 27902 27902 27501 0 -1 4194304 41 0 0 0 0 0 0 0 20 0 1 0 94173804 167936 23 18446744073709551615 4194304 4250668 548682069536 18446744073709551615 227605017993 0 0 4096 0 0 0 0 17 1 0 0
/proc/27904/statm: 41 23 17 13 0 3 0

[startup+0.102989 s]
/proc/loadavg: 0.54 0.24 0.61 5/75 27903
/proc/meminfo: memFree=1808352/2055920 swapFree=4183744/4192956
[pid=27902] ppid=27900 vsize=5352 CPUtime=0
/proc/27902/stat : 27902 (solve) S 27900 27902 27501 0 -1 4194304 315 174 0 0 0 0 0 0 16 0 1 0 94173804 5480448 229 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 227607634756 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/27902/statm: 1338 229 192 169 0 49 0
Current children cumulated CPU time (s) 0
Current children cumulated vsize (KiB) 5352

[startup+0.513043 s]
/proc/loadavg: 0.54 0.24 0.61 5/75 27903
/proc/meminfo: memFree=1808352/2055920 swapFree=4183744/4192956
[pid=27902] ppid=27900 vsize=5352 CPUtime=0
/proc/27902/stat : 27902 (solve) S 27900 27902 27501 0 -1 4194304 315 174 0 0 0 0 0 0 16 0 1 0 94173804 5480448 229 18446744073709551615 4194304 4889804 548682069328 18446744073709551615 227607634756 0 65536 4100 65538 18446744071563356171 0 0 17 0 0 0
/proc/27902/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): 1.2831
CPU time (s): 1.27081
CPU user time (s): 1.24881
CPU system time (s): 0.021996
CPU usage (%): 99.0417
Max. virtual memory (cumulated for all children) (KiB): 18292

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 1.24881
system time used= 0.021996
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 3055
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= 36
involuntary context switches= 35

runsolver used 0.005999 s user time and 0.007998 s system time

The end

Launcher Data (download as text)

Begin job on node66 on Mon Jan 22 11:52:25 UTC 2007


IDJOB= 283171
IDBENCH= 3198
IDSOLVER= 93
FILE ID= node66/283171-1169466743

PBS_JOBID= 3613801

Free space on /tmp= 66562 MiB

SOLVER NAME= rjw-solver 2007-01-21
BENCH NAME= HOME/pub/bench/CPAI06/ehi/ehi-85/ehi-85-297-43_ext.xml
COMMAND LINE= /tmp/evaluation/283171-1169466743/solve /tmp/evaluation/283171-1169466743/unknown 1800
CONVERSION COMMAND LINE= runsolver -w ROOT/results/node66/convwatcher-283171-1169466743 -o ROOT/results/node66/conversion-283171-1169466743 -C 600 -M 900 /tmp/evaluation/283171-1169466743/conversion /tmp/evaluation/283171-1169466743/unknown
CONVERSION RUNSOLVER STATUS CODE= 0
CONVERSION STATUS CODE= 0

RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node66/watcher-283171-1169466743 -o ROOT/results/node66/solver-283171-1169466743 -C 1800 -M 900  /tmp/evaluation/283171-1169466743/solve /tmp/evaluation/283171-1169466743/unknown 1800

META MD5SUM SOLVER= 4108942ff566d5523369442a8e3d06c4
MD5SUM BENCH=  a34777e1c99afaa7639f38cb2fbceb0f

RANDOM SEED= 52371605

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.230
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.230
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:       1808696 kB
Buffers:         14144 kB
Cached:         172740 kB
SwapCached:       4264 kB
Active:          85832 kB
Inactive:       124348 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1808696 kB
SwapTotal:     4192956 kB
SwapFree:      4183744 kB
Dirty:            3652 kB
Writeback:           0 kB
Mapped:          29456 kB
Slab:            22480 kB
Committed_AS:  1281280 kB
PageTables:       1752 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= 66561 MiB



End job on node66 on Mon Jan 22 11:52:51 UTC 2007