Trace number 237286

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.828873 0.836655

General information on the benchmark

Nameos-gp/
gp10-09-1112.xml
MD5SUM06eaa40bf809ba3f654c85e42e55e982
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.369943
SatisfiableYES
(Un)Satisfiability was proved
Number of variables101
Number of constraints1000
Maximum constraint arity2
Maximum domain size1113
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.01	c 
0.01	c Parsing xml file
0.01	c 	domains...............    0
0.01	c 	variables.............    0
0.01	c 	predicates............    0
0.01	c 	constraints........... 0.06
0.07	c Allocating memory
0.07	c 
0.07	c time limit = -1
0.07	c heuristic = dom/wdeg
0.07	c restart policy = No restart
0.07	c 
0.07	c Solving
0.07	c
0.81	s SATISFIABLE
0.81	v 1112 431 1068 0 532 1090 426 1102 1109 1105 330 1105 735 1079 176 402 41 1101 1108 7 5 688 5 624 1068 735 687 501 506 755 0 8 1090 581 1 918 6 502 624 0 431 506 3 627 72 0 7 1097 162 4 88 0 1028 1106 402 6 1 581 1105 1104 1096 782 712 1105 2 1110 466 116 88 1 9 1 0 1110 71 1097 151 1096 13 6 437 689 1079 1078 116 782 0 5 918 246 176 6 533 330 13 5 712 0 9 41 8
0.81	d          SAT      5462 BTS      0.68 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/node40/watcher-237286-1168347304 -o ROOT/results/node40/solver-237286-1168347304 -C 1800 -M 900 /tmp/evaluation/237286-1168347304/mistral/bin/solver /tmp/evaluation/237286-1168347304/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: 2.01 2.03 1.95 4/81 32049
/proc/meminfo: memFree=1514824/2055920 swapFree=4192812/4192956
[pid=32048] ppid=32046 vsize=6792 CPUtime=0
/proc/32048/stat : 32048 (solver) R 32046 32048 31804 0 -1 4194304 425 0 0 0 0 0 0 0 18 0 1 0 183129806 6955008 404 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 6880120 0 0 4096 0 0 0 0 17 0 0 0
/proc/32048/statm: 1698 405 366 92 0 30 0

[startup+0.104615 s]
/proc/loadavg: 2.01 2.03 1.95 4/81 32049
/proc/meminfo: memFree=1514824/2055920 swapFree=4192812/4192956
[pid=32048] ppid=32046 vsize=16440 CPUtime=0.09
/proc/32048/stat : 32048 (solver) R 32046 32048 31804 0 -1 4194304 3203 0 0 0 8 1 0 0 18 0 1 0 183129806 16834560 3171 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 7345787 0 0 4096 0 0 0 0 17 0 0 0
/proc/32048/statm: 4110 3174 715 92 0 2454 0
Current children cumulated CPU time (s) 0.09
Current children cumulated vsize (KiB) 16440

[startup+0.512667 s]
/proc/loadavg: 2.01 2.03 1.95 4/81 32049
/proc/meminfo: memFree=1514824/2055920 swapFree=4192812/4192956
[pid=32048] ppid=32046 vsize=23456 CPUtime=0.5
/proc/32048/stat : 32048 (solver) R 32046 32048 31804 0 -1 4194304 4970 0 0 0 48 2 0 0 22 0 1 0 183129806 24018944 4938 18446744073709551615 134512640 134893201 4294956688 18446744073709551615 134792865 0 0 4096 0 0 0 0 17 0 0 0
/proc/32048/statm: 5864 4938 718 92 0 4208 0
Current children cumulated CPU time (s) 0.5
Current children cumulated vsize (KiB) 23456

Child status: 0
Real time (s): 0.836655
CPU time (s): 0.828873
CPU user time (s): 0.801878
CPU system time (s): 0.026995
CPU usage (%): 99.0699
Max. virtual memory (cumulated for all children) (KiB): 23496

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

runsolver used 0.003999 s user time and 0.005999 s system time

The end

Launcher Data (download as text)

Begin job on node40 on Tue Jan  9 12:55:05 UTC 2007


IDJOB= 237286
IDBENCH= 6911
FILE ID= node40/237286-1168347304

PBS_JOBID= 3503615

Free space on /tmp= 66551 MiB

BENCH NAME= HOME/pub/bench/CPAI06/os-gp/gp10-09-1112.xml
COMMAND LINE= /tmp/evaluation/237286-1168347304/mistral/bin/solver /tmp/evaluation/237286-1168347304/unknown.xml -v 1
RUNSOLVER COMMAND LINE= runsolver  --timestamp  -w ROOT/results/node40/watcher-237286-1168347304 -o ROOT/results/node40/solver-237286-1168347304 -C 1800 -M 900  /tmp/evaluation/237286-1168347304/mistral/bin/solver /tmp/evaluation/237286-1168347304/unknown.xml -v 1

META MD5SUM SOLVER= cb80ed4ac975bdc0101f830a5b1b8f77
MD5SUM BENCH=  06eaa40bf809ba3f654c85e42e55e982

RANDOM SEED= 621796164

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.239
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.239
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:       1515240 kB
Buffers:         19584 kB
Cached:          90508 kB
SwapCached:          0 kB
Active:         445576 kB
Inactive:        38712 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2055920 kB
LowFree:       1515240 kB
SwapTotal:     4192956 kB
SwapFree:      4192812 kB
Dirty:            3260 kB
Writeback:           0 kB
Mapped:         392240 kB
Slab:            40976 kB
Committed_AS:  4436008 kB
PageTables:       2548 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= 66551 MiB



End job on node40 on Tue Jan  9 12:55:06 UTC 2007