Trace number 195606

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
Mistral 2006-12-04UNSAT 0.746885 0.755907

General information on the benchmark

Namerlfap/rlfapGraphs/
graph7.xml
MD5SUM6894350c4fec852e84b11a6ff9a12c54
Bench Category2-ARY-INT (binary constraints in intension)
Best result obtained on this benchmarkUNSAT
Best CPU time to get the best result obtained on this benchmark0.264959
SatisfiableNO
(Un)Satisfiability was provedNO
Number of variables400
Number of constraints2170
Maximum constraint arity2
Maximum domain size44
Number of constraints which are defined in extension0
Number of constraints which are defined in intension2170
Global constraints used (with number of constraints)

Solver Data (download as text)

0.21	c 
0.21	c Parsing xml file
0.21	c 	domains...............    0
0.21	c 	variables.............    0
0.21	c 	predicates............    0
0.21	c 	constraints........... 0.13
0.21	c Allocating memory
0.21	c 
0.21	c time limit = -1
0.21	c heuristic = dom/wdeg
0.21	c restart policy = No restart
0.21	c 
0.21	c Solving
0.21	c
0.58	s UNSATISFIABLE
0.58	d        UNSAT         1 BTS      0.02 s

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/node48/watcher-195606-1168113260 -o ROOT/results/node48/solver-195606-1168113260 -C 1800 -M 900 /tmp/evaluation/195606-1168113260/mistral/bin/solver /tmp/evaluation/195606-1168113260/unknown.xml -v 1 

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.18 1.70 1.83 6/73 9877
/proc/meminfo: memFree=1565872/2055920 swapFree=4192812/4192956
[pid=9876] ppid=9871 vsize=18540 CPUtime=0
/proc/9876/stat : 9876 (runsolver) R 9871 9876 9386 0 -1 4194368 16 0 0 0 0 0 0 0 18 0 1 0 159725093 18984960 279 18446744073709551615 4194304 4267372 548682069056 18446744073709551615 255539604775 0 0 4096 24578 0 0 0 17 1 0 0
/proc/9876/statm: 4635 279 244 17 0 2626 0

[startup+0.104073 s]
/proc/loadavg: 1.18 1.70 1.83 6/73 9877
/proc/meminfo: memFree=1565872/2055920 swapFree=4192812/4192956
[pid=9876] ppid=9871 vsize=9820 CPUtime=0.08
/proc/9876/stat : 9876 (solver) R 9871 9876 9386 0 -1 4194304 1536 0 0 0 8 0 0 0 18 0 1 0 159725093 10055680 1504 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 4156057746 0 0 4096 0 0 0 0 17 0 0 0
/proc/9876/statm: 2455 1504 706 92 0 799 0
Current children cumulated CPU time (s) 0.08
Current children cumulated vsize (KiB) 9820

[startup+0.512113 s]
/proc/loadavg: 1.18 1.70 1.83 6/73 9877
/proc/meminfo: memFree=1565872/2055920 swapFree=4192812/4192956
[pid=9876] ppid=9871 vsize=64872 CPUtime=0.5
/proc/9876/stat : 9876 (solver) R 9871 9876 9386 0 -1 4194304 15304 0 0 0 42 8 0 0 22 0 1 0 159725093 66428928 15272 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 3972865 0 0 4096 0 0 0 0 17 0 0 0
/proc/9876/statm: 16218 15272 715 92 0 14562 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 64872

Child status: 0
Real time (s): 0.755907
CPU time (s): 0.746885
CPU user time (s): 0.647901
CPU system time (s): 0.098984
CPU usage (%): 98.8065
Max. virtual memory (cumulated for all children) (KiB): 72000

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.647901
system time used= 0.098984
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 17093
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= 12
involuntary context switches= 25

runsolver used 0.001999 s user time and 0.006998 s system time

The end

Launcher Data (download as text)

Begin job on node48 on Sat Jan  6 19:54:23 UTC 2007


IDJOB= 195606
IDBENCH= 3289
FILE ID= node48/195606-1168113260

PBS_JOBID= 3477398

Free space on /tmp= 66555 MiB

BENCH NAME= HOME/pub/bench/CPAI06/rlfap/rlfapGraphs/graph7.xml
COMMAND LINE= /tmp/evaluation/195606-1168113260/mistral/bin/solver /tmp/evaluation/195606-1168113260/unknown.xml -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node48/watcher-195606-1168113260 -o ROOT/results/node48/solver-195606-1168113260 -C 1800 -M 900  /tmp/evaluation/195606-1168113260/mistral/bin/solver /tmp/evaluation/195606-1168113260/unknown.xml -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  6894350c4fec852e84b11a6ff9a12c54

RANDOM SEED= 921686345

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.218
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.218
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:       1567280 kB
Buffers:         41332 kB
Cached:         354360 kB
SwapCached:          0 kB
Active:         105688 kB
Inactive:       310080 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1567280 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            6800 kB
Writeback:           0 kB
Mapped:          30208 kB
Slab:            58476 kB
Committed_AS:  3255280 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= 66555 MiB



End job on node48 on Sat Jan  6 19:54:26 UTC 2007