Trace number 195542

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.743885 0.779137

General information on the benchmark

Namerlfap/rlfapGraphs/
graph6.xml
MD5SUMc50dbbefd6ab60c3d06d4df6d3eb879d
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.280957
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.07	c 
0.07	c Parsing xml file
0.07	c 	domains...............    0
0.07	c 	variables.............    0
0.07	c 	predicates............    0
0.07	c 	constraints........... 0.13
0.17	c Allocating memory
0.17	c 
0.17	c time limit = -1
0.17	c heuristic = dom/wdeg
0.17	c restart policy = No restart
0.17	c 
0.17	c Solving
0.17	c
0.60	s UNSATISFIABLE
0.60	d        UNSAT         1 BTS      0.07 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/node55/watcher-195542-1168113140 -o ROOT/results/node55/solver-195542-1168113140 -C 1800 -M 900 /tmp/evaluation/195542-1168113140/mistral/bin/solver /tmp/evaluation/195542-1168113140/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: 0.99 1.28 1.65 5/84 21904
/proc/meminfo: memFree=1848112/2055920 swapFree=4192812/4192956
[pid=21903] ppid=21901 vsize=18540 CPUtime=0
/proc/21903/stat : 21903 (runsolver) R 21901 21903 21615 0 -1 4194368 16 0 0 0 0 0 0 0 18 0 1 0 159712364 18984960 279 18446744073709551615 4194304 4267372 548682069056 18446744073709551615 248761609511 0 0 4096 24578 0 0 0 17 1 0 0
/proc/21903/statm: 4635 279 244 17 0 2626 0

[startup+0.102994 s]
/proc/loadavg: 0.99 1.28 1.65 5/84 21904
/proc/meminfo: memFree=1848112/2055920 swapFree=4192812/4192956
[pid=21903] ppid=21901 vsize=9688 CPUtime=0.06
/proc/21903/stat : 21903 (solver) R 21901 21903 21615 0 -1 4194304 1513 0 0 0 6 0 0 0 18 0 1 0 159712364 9920512 1481 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 4158769860 0 0 4096 0 0 0 0 17 0 0 0
/proc/21903/statm: 2422 1481 706 92 0 766 0
Current children cumulated CPU time (s) 0.06
Current children cumulated vsize (KiB) 9688

[startup+0.511041 s]
/proc/loadavg: 0.99 1.28 1.65 5/84 21904
/proc/meminfo: memFree=1848112/2055920 swapFree=4192812/4192956
[pid=21903] ppid=21901 vsize=68296 CPUtime=0.47
/proc/21903/stat : 21903 (solver) R 21901 21903 21615 0 -1 4194304 16147 0 0 0 41 6 0 0 21 0 1 0 159712364 69935104 16115 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 4156460742 0 0 4096 0 0 0 0 17 0 0 0
/proc/21903/statm: 17074 16115 715 92 0 15418 0
Current children cumulated CPU time (s) 0.47
Current children cumulated vsize (KiB) 68296

Child status: 0
Real time (s): 0.779137
CPU time (s): 0.743885
CPU user time (s): 0.664898
CPU system time (s): 0.078987
CPU usage (%): 95.4755
Max. virtual memory (cumulated for all children) (KiB): 72124

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.664898
system time used= 0.078987
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 17123
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= 13
involuntary context switches= 51

runsolver used 0.003999 s user time and 0.005999 s system time

The end

Launcher Data (download as text)

Begin job on node55 on Sat Jan  6 19:52:21 UTC 2007


IDJOB= 195542
IDBENCH= 3285
FILE ID= node55/195542-1168113140

PBS_JOBID= 3477393

Free space on /tmp= 66540 MiB

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

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  c50dbbefd6ab60c3d06d4df6d3eb879d

RANDOM SEED= 173749025

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	: 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.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:       1851216 kB
Buffers:         14576 kB
Cached:         106192 kB
SwapCached:          0 kB
Active:          97220 kB
Inactive:        54244 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1851216 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            6212 kB
Writeback:           0 kB
Mapped:          49688 kB
Slab:            38612 kB
Committed_AS:  3931708 kB
PageTables:       1796 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= 66540 MiB



End job on node55 on Sat Jan  6 19:52:22 UTC 2007