Trace number 237302

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-04SAT 0.414936 0.423417

General information on the benchmark

Nameos-gp/
gp10-04-1077.xml
MD5SUM9e1073cf0543b531d5d4e0d0fba8e4b2
Bench Category2-ARY-INT (binary constraints in intension)
Best result obtained on this benchmarkSAT
Best CPU time to get the best result obtained on this benchmark0.297953
SatisfiableYES
(Un)Satisfiability was proved
Number of variables101
Number of constraints1000
Maximum constraint arity2
Maximum domain size1078
Number of constraints which are defined in extension0
Number of constraints which are defined in intension1000
Global constraints used (with number of constraints)

Solver Data (download as text)

0.20	c 
0.20	c Parsing xml file
0.20	c 	domains...............    0
0.20	c 	variables.............    0
0.20	c 	predicates............    0
0.20	c 	constraints........... 0.06
0.20	c Allocating memory
0.20	c 
0.20	c time limit = -1
0.20	c heuristic = dom/wdeg
0.20	c restart policy = No restart
0.20	c 
0.20	c Solving
0.20	c
0.40	s SATISFIABLE
0.40	v 1077 1066 0 86 623 25 1059 1060 565 23 1075 1064 3 602 1070 873 280 1049 1073 0 862 240 718 891 6 1075 638 1073 1074 780 1 707 706 0 1059 81 1055 1070 666 646 665 1073 705 594 538 1072 602 0 706 54 666 1075 792 593 1 0 1074 511 9 621 688 1060 1074 1055 280 631 0 1054 623 538 872 705 490 81 1076 23 718 86 0 9 994 1055 780 1049 0 1 1073 840 1072 665 6 1 240 565 1075 872 1076 593 511 891 0
0.40	d          SAT      1653 BTS      0.25 s

Verifier Data (download as text)

OK

Watcher Data (download as text)

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

command line: runsolver --timestamp -w ROOT/results/node24/watcher-237302-1168347351 -o ROOT/results/node24/solver-237302-1168347351 -C 1800 -M 900 /tmp/evaluation/237302-1168347351/mistral/bin/solver /tmp/evaluation/237302-1168347351/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.91 1.95 1.92 5/93 1626
/proc/meminfo: memFree=1687208/2055920 swapFree=4192800/4192956
[pid=1625] ppid=1623 vsize=18540 CPUtime=0
/proc/1625/stat : 1625 (runsolver) R 1623 1625 805 0 -1 4194368 16 0 0 0 0 0 0 0 20 0 1 0 183130415 18984960 279 18446744073709551615 4194304 4267372 548682069056 18446744073709551615 237788261671 0 0 4096 24578 0 0 0 17 1 0 0
/proc/1625/statm: 4635 279 244 17 0 2626 0

[startup+0.107874 s]
/proc/loadavg: 1.91 1.95 1.92 5/93 1626
/proc/meminfo: memFree=1687208/2055920 swapFree=4192800/4192956
[pid=1625] ppid=1623 vsize=14060 CPUtime=0.09
/proc/1625/stat : 1625 (solver) R 1623 1625 805 0 -1 4194304 2604 0 0 0 9 0 0 0 18 0 1 0 183130415 14397440 2572 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 3040891 0 0 4096 0 0 0 0 17 1 0 0
/proc/1625/statm: 3515 2572 715 92 0 1859 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 14060

Child status: 0
Real time (s): 0.423417
CPU time (s): 0.414936
CPU user time (s): 0.382941
CPU system time (s): 0.031995
CPU usage (%): 97.997
Max. virtual memory (cumulated for all children) (KiB): 23496

getrusage(RUSAGE_CHILDREN,...) data:
user time used= 0.382941
system time used= 0.031995
maximum resident set size= 0
integral shared memory size= 0
integral unshared data size= 0
integral unshared stack size= 0
page reclaims= 4990
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= 31

runsolver used 0.004999 s user time and 0.004999 s system time

The end

Launcher Data (download as text)

Begin job on node24 on Tue Jan  9 12:55:51 UTC 2007


IDJOB= 237302
IDBENCH= 6912
FILE ID= node24/237302-1168347351

PBS_JOBID= 3503543

Free space on /tmp= 66473 MiB

BENCH NAME= HOME/pub/bench/CPAI06/os-gp/gp10-04-1077.xml
COMMAND LINE= /tmp/evaluation/237302-1168347351/mistral/bin/solver /tmp/evaluation/237302-1168347351/unknown.xml -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node24/watcher-237302-1168347351 -o ROOT/results/node24/solver-237302-1168347351 -C 1800 -M 900  /tmp/evaluation/237302-1168347351/mistral/bin/solver /tmp/evaluation/237302-1168347351/unknown.xml -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  9e1073cf0543b531d5d4e0d0fba8e4b2

RANDOM SEED= 843969039

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:       1687688 kB
Buffers:         26840 kB
Cached:          98552 kB
SwapCached:          0 kB
Active:         263372 kB
Inactive:        51384 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1687688 kB
SwapTotal:     4192956 kB
SwapFree:      4192800 kB
Dirty:            3172 kB
Writeback:           0 kB
Mapped:         216092 kB
Slab:            37836 kB
Committed_AS:  4802048 kB
PageTables:       2652 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= 66473 MiB



End job on node24 on Tue Jan  9 12:55:52 UTC 2007