groonga-query-log 1.3.4 → 1.3.5

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (27) hide show
  1. checksums.yaml +4 -4
  2. data/doc/text/news.md +12 -0
  3. data/lib/groonga-query-log/command/check-crash.rb +2 -0
  4. data/lib/groonga-query-log/statistic.rb +4 -2
  5. data/lib/groonga-query-log/version.rb +1 -1
  6. metadata +30 -72
  7. data/test/fixtures/run-regression-test/db.new/db +0 -0
  8. data/test/fixtures/run-regression-test/db.new/db.0000000 +0 -0
  9. data/test/fixtures/run-regression-test/db.new/db.0000100 +0 -0
  10. data/test/fixtures/run-regression-test/db.new/db.0000101 +0 -0
  11. data/test/fixtures/run-regression-test/db.new/db.0000102 +0 -0
  12. data/test/fixtures/run-regression-test/db.new/db.0000103 +0 -0
  13. data/test/fixtures/run-regression-test/db.new/db.0000103.c +0 -0
  14. data/test/fixtures/run-regression-test/db.new/db.001 +0 -0
  15. data/test/fixtures/run-regression-test/db.new/db.conf +0 -0
  16. data/test/fixtures/run-regression-test/db.new/groonga.log +0 -165
  17. data/test/fixtures/run-regression-test/db.old/db +0 -0
  18. data/test/fixtures/run-regression-test/db.old/db.0000000 +0 -0
  19. data/test/fixtures/run-regression-test/db.old/db.0000100 +0 -0
  20. data/test/fixtures/run-regression-test/db.old/db.0000101 +0 -0
  21. data/test/fixtures/run-regression-test/db.old/db.0000102 +0 -0
  22. data/test/fixtures/run-regression-test/db.old/db.0000103 +0 -0
  23. data/test/fixtures/run-regression-test/db.old/db.0000103.c +0 -0
  24. data/test/fixtures/run-regression-test/db.old/db.001 +0 -0
  25. data/test/fixtures/run-regression-test/db.old/db.conf +0 -0
  26. data/test/fixtures/run-regression-test/db.old/groonga.log +0 -79
  27. data/test/fixtures/run-regression-test/results/query.log +0 -0
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: e09cac93999ccbd46a1521afa9ccae705d47795575d275d086a1cc15e16ed8f1
4
- data.tar.gz: e39350cad4042ef656afc00e133db5913664e50ff9102ac7e11afb26a1fc7143
3
+ metadata.gz: 0e173b6fc3d59ec776e703b53cf127d0ff9daaf8cf5ff7a81c25b8f2534ecc3f
4
+ data.tar.gz: 773d85f3aa8490f3b7a53c908788a3f912901829d1901c60e40500a5485edfaf
5
5
  SHA512:
6
- metadata.gz: d06425f98da9e4d9402211298bf9b7e9baceb1735b37fb37fc0e634f8a71dae7c31bbd576682177650d72affaee9e0dbac953e0e0de26a000a121b4d15791684
7
- data.tar.gz: 4a88d239858bd5e61ef0261c566039207cb95f36e2fad05ef0f847a967935765ee54128afe326c6a0e2989d071f2feb5f267f99e5136e4d15cee6b70dcab02f4
6
+ metadata.gz: e410a6e79714ba52241f25a0a792235e2c72fed744fe8b548f407bc58892f3380b331c86c276b343e232b686cac480c6ae9c5052582c0936bfe8021d9aa81378
7
+ data.tar.gz: 3af0903f15525d691d2afa7002e9b949f6d0a83e1ae115190a5260af537f99543ac8edadfc2f563ef33f2840e195d8ce3eb854d5ef5160b780f051347f454c10
data/doc/text/news.md CHANGED
@@ -1,5 +1,17 @@
1
1
  # News
2
2
 
3
+ ## 1.3.5: 2018-08-30
4
+
5
+ ### Improvements
6
+
7
+ * `groonga-query-log-check-crash`:
8
+
9
+ * Added support for no `grn_init` case.
10
+
11
+ * `groonga-query-log-analyze`:
12
+
13
+ * Improved `range_filter` and `logical_range_filter` support.
14
+
3
15
  ## 1.3.4: 2018-08-22
4
16
 
5
17
  ### Improvements
data/lib/groonga-query-log/command/check-crash.rb CHANGED
@@ -275,6 +275,8 @@ module GroongaQueryLog
275
275
  @running_processes[entry.pid] = process
276
276
  when /\Agrn_fin \((\d+)\)\z/
277
277
  n_leaks = $1.to_i
278
+ @running_processes[entry.pid] ||=
279
+ GroongaProcess.new(entry.pid, Time.at(0), path)
278
280
  process = @running_processes[entry.pid]
279
281
  process.n_leaks = n_leaks
280
282
  process.last_time = entry.timestamp
data/lib/groonga-query-log/statistic.rb CHANGED
@@ -164,9 +164,11 @@ module GroongaQueryLog
164
164
  label = operation[:name]
165
165
  case label
166
166
  when "filter"
167
- if command.query and context[:query_used].nil?
167
+ query = nil
168
+ query = command.query if command.respond_to?(:query)
169
+ if query and context[:query_used].nil?
168
170
  context[:query_used] = true
169
- "query: #{command.query}"
171
+ "query: #{query}"
170
172
  else
171
173
  index = context[:filter_index]
172
174
  context[:filter_index] += 1
data/lib/groonga-query-log/version.rb CHANGED
@@ -15,5 +15,5 @@
15
15
  # Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
16
16
 
17
17
  module GroongaQueryLog
18
- VERSION = "1.3.4"
18
+ VERSION = "1.3.5"
19
19
  end
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: groonga-query-log
3
3
  version: !ruby/object:Gem::Version
4
- version: 1.3.4
4
+ version: 1.3.5
5
5
  platform: ruby
6
6
  authors:
7
7
  - Kouhei Sutou
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2018-08-22 00:00:00.000000000 Z
11
+ date: 2018-08-30 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: groonga-command-parser
@@ -168,17 +168,17 @@ description: ''
168
168
  email:
169
169
  - kou@clear-code.com
170
170
  executables:
171
- - groonga-query-log-replay
171
+ - groonga-query-log-check-crash
172
172
  - groonga-query-log-format-regression-test-logs
173
- - groonga-query-log-show-running-queries
174
- - groonga-query-log-detect-memory-leak
175
173
  - groonga-query-log-verify-server
174
+ - groonga-query-log-extract
175
+ - groonga-query-log-analyze-load
176
176
  - groonga-query-log-run-regression-test
177
- - groonga-query-log-check-crash
178
177
  - groonga-query-log-check-command-version-compatibility
178
+ - groonga-query-log-replay
179
+ - groonga-query-log-show-running-queries
180
+ - groonga-query-log-detect-memory-leak
179
181
  - groonga-query-log-analyze
180
- - groonga-query-log-analyze-load
181
- - groonga-query-log-extract
182
182
  extensions: []
183
183
  extra_rdoc_files: []
184
184
  files:
@@ -261,29 +261,8 @@ files:
261
261
  - test/fixtures/reporter/json-stream.expected
262
262
  - test/fixtures/reporter/json.expected
263
263
  - test/fixtures/run-regression-test/data/data.grn
264
- - test/fixtures/run-regression-test/db.new/db
265
- - test/fixtures/run-regression-test/db.new/db.0000000
266
- - test/fixtures/run-regression-test/db.new/db.0000100
267
- - test/fixtures/run-regression-test/db.new/db.0000101
268
- - test/fixtures/run-regression-test/db.new/db.0000102
269
- - test/fixtures/run-regression-test/db.new/db.0000103
270
- - test/fixtures/run-regression-test/db.new/db.0000103.c
271
- - test/fixtures/run-regression-test/db.new/db.001
272
- - test/fixtures/run-regression-test/db.new/db.conf
273
- - test/fixtures/run-regression-test/db.new/groonga.log
274
- - test/fixtures/run-regression-test/db.old/db
275
- - test/fixtures/run-regression-test/db.old/db.0000000
276
- - test/fixtures/run-regression-test/db.old/db.0000100
277
- - test/fixtures/run-regression-test/db.old/db.0000101
278
- - test/fixtures/run-regression-test/db.old/db.0000102
279
- - test/fixtures/run-regression-test/db.old/db.0000103
280
- - test/fixtures/run-regression-test/db.old/db.0000103.c
281
- - test/fixtures/run-regression-test/db.old/db.001
282
- - test/fixtures/run-regression-test/db.old/db.conf
283
- - test/fixtures/run-regression-test/db.old/groonga.log
284
264
  - test/fixtures/run-regression-test/indexes/indexes.grn
285
265
  - test/fixtures/run-regression-test/query-logs/query.log
286
- - test/fixtures/run-regression-test/results/query.log
287
266
  - test/fixtures/run-regression-test/schema/schema.grn
288
267
  - test/fixtures/target-commands.expected
289
268
  - test/fixtures/target-tables.expected
@@ -321,54 +300,33 @@ summary: Groonga-query-log is a collection of library and tools to process [Groo
321
300
  as a library. You can analyze your Groonga's queries and test with your Groonga's
322
301
  query log by using groonga-query-log as a tool.
323
302
  test_files:
324
- - test/fixtures/multi.expected
325
- - test/fixtures/target-tables.expected
326
- - test/fixtures/target-commands.expected
327
- - test/fixtures/n_entries.expected
328
- - test/fixtures/query.log
303
+ - test/test-parser.rb
304
+ - test/test-response-comparer.rb
305
+ - test/command/test-analyzer.rb
306
+ - test/command/test-extract.rb
307
+ - test/command/test-format-regression-test-logs.rb
329
308
  - test/fixtures/other-query.log
330
- - test/fixtures/order/-start-time.expected
331
- - test/fixtures/order/elapsed.expected
332
- - test/fixtures/order/-elapsed.expected
333
- - test/fixtures/order/start-time.expected
334
- - test/fixtures/regression-test-logs/url-format.log
335
- - test/fixtures/regression-test-logs/command-format.log
336
- - test/fixtures/reporter/json.expected
309
+ - test/fixtures/target-commands.expected
337
310
  - test/fixtures/reporter/console.expected
338
311
  - test/fixtures/reporter/html.expected
339
312
  - test/fixtures/reporter/json-stream.expected
340
- - test/fixtures/run-regression-test/db.old/db.0000100
341
- - test/fixtures/run-regression-test/db.old/db.0000103
342
- - test/fixtures/run-regression-test/db.old/db.0000103.c
343
- - test/fixtures/run-regression-test/db.old/db.0000101
344
- - test/fixtures/run-regression-test/db.old/db
345
- - test/fixtures/run-regression-test/db.old/db.0000000
346
- - test/fixtures/run-regression-test/db.old/db.001
347
- - test/fixtures/run-regression-test/db.old/db.conf
348
- - test/fixtures/run-regression-test/db.old/db.0000102
349
- - test/fixtures/run-regression-test/db.old/groonga.log
350
- - test/fixtures/run-regression-test/query-logs/query.log
313
+ - test/fixtures/reporter/json.expected
314
+ - test/fixtures/target-tables.expected
315
+ - test/fixtures/query.log
316
+ - test/fixtures/multi.expected
317
+ - test/fixtures/no-report-summary.expected
318
+ - test/fixtures/run-regression-test/indexes/indexes.grn
351
319
  - test/fixtures/run-regression-test/schema/schema.grn
352
320
  - test/fixtures/run-regression-test/data/data.grn
353
- - test/fixtures/run-regression-test/indexes/indexes.grn
354
- - test/fixtures/run-regression-test/db.new/db.0000100
355
- - test/fixtures/run-regression-test/db.new/db.0000103
356
- - test/fixtures/run-regression-test/db.new/db.0000103.c
357
- - test/fixtures/run-regression-test/db.new/db.0000101
358
- - test/fixtures/run-regression-test/db.new/db
359
- - test/fixtures/run-regression-test/db.new/db.0000000
360
- - test/fixtures/run-regression-test/db.new/db.001
361
- - test/fixtures/run-regression-test/db.new/db.conf
362
- - test/fixtures/run-regression-test/db.new/db.0000102
363
- - test/fixtures/run-regression-test/db.new/groonga.log
364
- - test/fixtures/run-regression-test/results/query.log
365
- - test/fixtures/no-report-summary.expected
321
+ - test/fixtures/run-regression-test/query-logs/query.log
322
+ - test/fixtures/regression-test-logs/url-format.log
323
+ - test/fixtures/regression-test-logs/command-format.log
324
+ - test/fixtures/n_entries.expected
325
+ - test/fixtures/order/-start-time.expected
326
+ - test/fixtures/order/elapsed.expected
327
+ - test/fixtures/order/start-time.expected
328
+ - test/fixtures/order/-elapsed.expected
366
329
  - test/helper.rb
367
- - test/command/test-analyzer.rb
368
- - test/command/test-format-regression-test-logs.rb
369
- - test/command/test-extract.rb
370
- - test/test-replayer.rb
371
- - test/test-incompatibility-detector.rb
372
330
  - test/run-test.rb
373
- - test/test-parser.rb
374
- - test/test-response-comparer.rb
331
+ - test/test-incompatibility-detector.rb
332
+ - test/test-replayer.rb
data/test/fixtures/run-regression-test/db.new/groonga.log DELETED
@@ -1,165 +0,0 @@
1
- 2017-04-24 11:06:45.783903|n| grn_init: <7.0.1-105-gf940037>
2
- 2017-04-24 11:06:45.783995|n| vm.overcommit_memory kernel parameter should be 1: <0>: See INFO level log to resolve this
3
- 2017-04-24 11:06:45.785696|n| DDL:256:table_create Entries
4
- 2017-04-24 11:06:45.832240|n| spec:256:update:Entries:48(table:hash_key):0
5
- 2017-04-24 11:06:45.832566|n| DDL:257:column_create Entries description
6
- 2017-04-24 11:06:45.882379|n| spec:257:update:Entries.description:65(column:var_size):15(Text)
7
- 2017-04-24 11:06:45.902188|n| grn_fin (0)
8
- 2017-04-24 11:06:45.911851|n| grn_init: <7.0.1-105-gf940037>
9
- 2017-04-24 11:06:45.911981|n| vm.overcommit_memory kernel parameter should be 1: <0>: See INFO level log to resolve this
10
- 2017-04-24 11:06:45.927281|n| grn_fin (0)
11
- 2017-04-24 11:06:45.938921|n| grn_init: <7.0.1-105-gf940037>
12
- 2017-04-24 11:06:45.939085|n| vm.overcommit_memory kernel parameter should be 1: <0>: See INFO level log to resolve this
13
- 2017-04-24 11:06:45.943080|n| DDL:258:table_create Bigram
14
- 2017-04-24 11:06:45.990956|n| spec:258:update:Bigram:49(table:pat_key):0
15
- 2017-04-24 11:06:45.991456|n| DDL:259:column_create Bigram Entries_description
16
- 2017-04-24 11:06:46.084367|n| spec:259:update:Bigram.Entries_description:72(column:index):256(Entries)
17
- 2017-04-24 11:06:46.099864|n| DDL:259:set_source Bigram.Entries_description Entries.description
18
- 2017-04-24 11:06:46.099925|n| spec:257:update:Entries.description:65(column:var_size):15(Text)
19
- 2017-04-24 11:06:46.104701|n| spec:259:update:Bigram.Entries_description:72(column:index):256(Entries)
20
- 2017-04-24 11:06:46.113406|n| grn_fin (0)
21
- 2017-04-24 11:06:46.117714|n| grn_init: <7.0.1-105-gf940037>
22
- 2017-04-24 11:06:46.117765|n| vm.overcommit_memory kernel parameter should be 1: <0>: See INFO level log to resolve this
23
- 2017-04-24 11:06:46.117899|n| RLIMIT_NOFILE(4096,4096)
24
- 2017-04-24 11:06:47.117263|n| thread start (0/1)
25
- 2017-04-24 11:06:47.495184|n| thread end (0/0)
26
- 2017-04-24 11:06:47.498054|n| grn_fin (0)
27
- 2017-04-24 11:07:45.262160|n| grn_init: <7.0.1-105-gf940037>
28
- 2017-04-24 11:07:45.262192|n| vm.overcommit_memory kernel parameter should be 1: <0>: See INFO level log to resolve this
29
- 2017-04-24 11:07:45.262282|n| RLIMIT_NOFILE(4096,4096)
30
- 2017-04-24 11:07:46.261844|n| thread start (0/1)
31
- 2017-04-24 11:07:46.580606|n| thread end (0/0)
32
- 2017-04-24 11:07:46.583733|n| grn_fin (0)
33
- 2017-04-24 11:07:46.586691|n| grn_init: <7.0.1-105-gf940037>
34
- 2017-04-24 11:07:46.586724|n| vm.overcommit_memory kernel parameter should be 1: <0>: See INFO level log to resolve this
35
- 2017-04-24 11:07:46.586809|n| RLIMIT_NOFILE(4096,4096)
36
- 2017-04-24 11:07:47.585962|n| thread start (0/1)
37
- 2017-04-24 11:07:48.028639|n| thread end (0/0)
38
- 2017-04-24 11:07:48.030048|n| grn_fin (0)
39
- 2017-04-24 11:07:48.034362|n| grn_init: <7.0.1-105-gf940037>
40
- 2017-04-24 11:07:48.034410|n| vm.overcommit_memory kernel parameter should be 1: <0>: See INFO level log to resolve this
41
- 2017-04-24 11:07:48.034549|n| RLIMIT_NOFILE(4096,4096)
42
- 2017-04-24 11:07:49.032453|n| thread start (0/1)
43
- 2017-04-24 11:07:49.195891|n| thread end (0/0)
44
- 2017-04-24 11:07:49.196755|n| grn_fin (0)
45
- 2017-04-24 11:10:47.018307|n| grn_init: <7.0.1-105-gf940037>
46
- 2017-04-24 11:10:47.018349|n| vm.overcommit_memory kernel parameter should be 1: <0>: See INFO level log to resolve this
47
- 2017-04-24 11:10:47.018437|n| RLIMIT_NOFILE(4096,4096)
48
- 2017-04-24 11:10:48.017869|n| thread start (0/1)
49
- 2017-04-24 11:10:48.313167|n| thread end (0/0)
50
- 2017-04-24 11:10:48.314042|n| grn_fin (0)
51
- 2017-04-24 11:10:48.316882|n| grn_init: <7.0.1-105-gf940037>
52
- 2017-04-24 11:10:48.316926|n| vm.overcommit_memory kernel parameter should be 1: <0>: See INFO level log to resolve this
53
- 2017-04-24 11:10:48.317007|n| RLIMIT_NOFILE(4096,4096)
54
- 2017-04-24 11:10:49.315935|n| thread start (0/1)
55
- 2017-04-24 11:10:49.698905|n| thread end (0/0)
56
- 2017-04-24 11:10:49.700064|n| grn_fin (0)
57
- 2017-04-24 11:10:49.705284|n| grn_init: <7.0.1-105-gf940037>
58
- 2017-04-24 11:10:49.705412|n| vm.overcommit_memory kernel parameter should be 1: <0>: See INFO level log to resolve this
59
- 2017-04-24 11:10:49.705578|n| RLIMIT_NOFILE(4096,4096)
60
- 2017-04-24 11:10:50.702205|n| thread start (0/1)
61
- 2017-04-24 11:10:50.858002|n| thread end (0/0)
62
- 2017-04-24 11:10:50.858862|n| grn_fin (0)
63
- 2017-04-24 11:11:12.606175|n| grn_init: <7.0.1-105-gf940037>
64
- 2017-04-24 11:11:12.606214|n| vm.overcommit_memory kernel parameter should be 1: <0>: See INFO level log to resolve this
65
- 2017-04-24 11:11:12.606307|n| RLIMIT_NOFILE(4096,4096)
66
- 2017-04-24 11:11:13.605834|n| thread start (0/1)
67
- 2017-04-24 11:11:13.842406|n| thread end (0/0)
68
- 2017-04-24 11:11:13.843288|n| grn_fin (0)
69
- 2017-04-24 11:11:13.846133|n| grn_init: <7.0.1-105-gf940037>
70
- 2017-04-24 11:11:13.846164|n| vm.overcommit_memory kernel parameter should be 1: <0>: See INFO level log to resolve this
71
- 2017-04-24 11:11:13.846254|n| RLIMIT_NOFILE(4096,4096)
72
- 2017-04-24 11:11:14.845410|n| thread start (0/1)
73
- 2017-04-24 11:11:15.127688|n| thread end (0/0)
74
- 2017-04-24 11:11:15.128568|n| grn_fin (0)
75
- 2017-04-24 11:11:15.131325|n| grn_init: <7.0.1-105-gf940037>
76
- 2017-04-24 11:11:15.131357|n| vm.overcommit_memory kernel parameter should be 1: <0>: See INFO level log to resolve this
77
- 2017-04-24 11:11:15.131440|n| RLIMIT_NOFILE(4096,4096)
78
- 2017-04-24 11:11:16.130617|n| thread start (0/1)
79
- 2017-04-24 11:11:42.306188|n| grn_init: <7.0.1-105-gf940037>
80
- 2017-04-24 11:11:42.306219|n| vm.overcommit_memory kernel parameter should be 1: <0>: See INFO level log to resolve this
81
- 2017-04-24 11:11:42.306306|n| RLIMIT_NOFILE(4096,4096)
82
- 2017-04-24 11:11:43.308553|n| thread start (0/1)
83
- 2017-04-24 11:11:43.580788|n| thread end (0/0)
84
- 2017-04-24 11:11:43.581685|n| grn_fin (0)
85
- 2017-04-24 11:11:43.584541|n| grn_init: <7.0.1-105-gf940037>
86
- 2017-04-24 11:11:43.584576|n| vm.overcommit_memory kernel parameter should be 1: <0>: See INFO level log to resolve this
87
- 2017-04-24 11:11:43.584662|n| RLIMIT_NOFILE(4096,4096)
88
- 2017-04-24 11:11:44.583985|n| thread start (0/1)
89
- 2017-04-24 11:11:44.874262|n| thread end (0/0)
90
- 2017-04-24 11:11:44.875167|n| grn_fin (0)
91
- 2017-04-24 11:11:44.877971|n| grn_init: <7.0.1-105-gf940037>
92
- 2017-04-24 11:11:44.878014|n| vm.overcommit_memory kernel parameter should be 1: <0>: See INFO level log to resolve this
93
- 2017-04-24 11:11:44.878098|n| RLIMIT_NOFILE(4096,4096)
94
- 2017-04-24 11:11:45.877207|n| thread start (0/1)
95
- 2017-04-24 11:11:46.066477|n| thread end (0/0)
96
- 2017-04-24 11:11:46.067611|n| grn_fin (0)
97
- 2017-04-24 11:12:06.890149|n| grn_init: <7.0.1-105-gf940037>
98
- 2017-04-24 11:12:06.890181|n| vm.overcommit_memory kernel parameter should be 1: <0>: See INFO level log to resolve this
99
- 2017-04-24 11:12:06.890263|n| RLIMIT_NOFILE(4096,4096)
100
- 2017-04-24 11:12:07.889979|n| thread start (0/1)
101
- 2017-04-24 11:12:08.166979|n| thread end (0/0)
102
- 2017-04-24 11:12:08.167884|n| grn_fin (0)
103
- 2017-04-24 11:12:08.170752|n| grn_init: <7.0.1-105-gf940037>
104
- 2017-04-24 11:12:08.170794|n| vm.overcommit_memory kernel parameter should be 1: <0>: See INFO level log to resolve this
105
- 2017-04-24 11:12:08.170877|n| RLIMIT_NOFILE(4096,4096)
106
- 2017-04-24 11:12:09.170034|n| thread start (0/1)
107
- 2017-04-24 11:12:09.466889|n| thread end (0/0)
108
- 2017-04-24 11:12:09.467813|n| grn_fin (0)
109
- 2017-04-24 11:12:09.470729|n| grn_init: <7.0.1-105-gf940037>
110
- 2017-04-24 11:12:09.470761|n| vm.overcommit_memory kernel parameter should be 1: <0>: See INFO level log to resolve this
111
- 2017-04-24 11:12:09.470845|n| RLIMIT_NOFILE(4096,4096)
112
- 2017-04-24 11:12:10.469841|n| thread start (0/1)
113
- 2017-04-24 11:12:10.568799|n| thread end (0/0)
114
- 2017-04-24 11:12:10.569881|n| grn_fin (0)
115
- 2017-04-24 11:12:21.466214|n| grn_init: <7.0.1-105-gf940037>
116
- 2017-04-24 11:12:21.466249|n| vm.overcommit_memory kernel parameter should be 1: <0>: See INFO level log to resolve this
117
- 2017-04-24 11:12:21.466332|n| RLIMIT_NOFILE(4096,4096)
118
- 2017-04-24 11:12:22.466174|n| thread start (0/1)
119
- 2017-04-24 11:12:22.724694|n| thread end (0/0)
120
- 2017-04-24 11:12:22.725556|n| grn_fin (0)
121
- 2017-04-24 11:12:22.728489|n| grn_init: <7.0.1-105-gf940037>
122
- 2017-04-24 11:12:22.728520|n| vm.overcommit_memory kernel parameter should be 1: <0>: See INFO level log to resolve this
123
- 2017-04-24 11:12:22.728608|n| RLIMIT_NOFILE(4096,4096)
124
- 2017-04-24 11:12:23.727545|n| thread start (0/1)
125
- 2017-04-24 11:12:23.997429|n| thread end (0/0)
126
- 2017-04-24 11:12:23.998293|n| grn_fin (0)
127
- 2017-04-24 11:12:24.001106|n| grn_init: <7.0.1-105-gf940037>
128
- 2017-04-24 11:12:24.001138|n| vm.overcommit_memory kernel parameter should be 1: <0>: See INFO level log to resolve this
129
- 2017-04-24 11:12:24.001219|n| RLIMIT_NOFILE(4096,4096)
130
- 2017-04-24 11:12:25.000343|n| thread start (0/1)
131
- 2017-04-24 11:12:25.201017|n| thread end (0/0)
132
- 2017-04-24 11:12:25.202162|n| grn_fin (0)
133
- 2017-04-24 11:19:59.316027|n| grn_init: <7.0.1-105-gf940037>
134
- 2017-04-24 11:19:59.316064|n| vm.overcommit_memory kernel parameter should be 1: <0>: See INFO level log to resolve this
135
- 2017-04-24 11:19:59.316148|n| RLIMIT_NOFILE(4096,4096)
136
- 2017-04-24 11:20:00.315342|n| thread start (0/1)
137
- 2017-04-24 11:20:00.543339|n| thread end (0/0)
138
- 2017-04-24 11:20:00.544322|n| grn_fin (0)
139
- 2017-04-24 11:20:00.547319|n| grn_init: <7.0.1-105-gf940037>
140
- 2017-04-24 11:20:00.547355|n| vm.overcommit_memory kernel parameter should be 1: <0>: See INFO level log to resolve this
141
- 2017-04-24 11:20:00.547440|n| RLIMIT_NOFILE(4096,4096)
142
- 2017-04-24 11:20:01.545653|n| thread start (0/1)
143
- 2017-04-24 11:20:01.731747|n| thread end (0/0)
144
- 2017-04-24 11:20:01.732644|n| grn_fin (0)
145
- 2017-04-24 11:20:01.735519|n| grn_init: <7.0.1-105-gf940037>
146
- 2017-04-24 11:20:01.735558|n| vm.overcommit_memory kernel parameter should be 1: <0>: See INFO level log to resolve this
147
- 2017-04-24 11:20:01.735643|n| RLIMIT_NOFILE(4096,4096)
148
- 2017-04-24 11:20:02.734551|n| thread start (0/1)
149
- 2017-04-24 11:20:02.951152|n| thread end (0/0)
150
- 2017-04-24 11:20:02.952691|n| grn_fin (0)
151
- 2017-04-24 11:20:09.446073|n| grn_init: <7.0.1-105-gf940037>
152
- 2017-04-24 11:20:09.446115|n| vm.overcommit_memory kernel parameter should be 1: <0>: See INFO level log to resolve this
153
- 2017-04-24 11:20:09.446201|n| RLIMIT_NOFILE(4096,4096)
154
- 2017-04-24 11:20:10.448377|n| thread start (0/1)
155
- 2017-04-24 11:20:10.789136|n| thread end (0/0)
156
- 2017-04-24 11:20:10.792153|n| grn_fin (0)
157
- 2017-04-24 13:01:10.344434|e| system call error: Interrupted system call: epoll_wait
158
- 2017-04-24 13:01:10.344720|e| /tmp/local/lib/libgroonga.so.0(grn_com_event_poll+0x600) [0x7fe1890695cf]
159
- 2017-04-24 13:01:10.344749|e| /tmp/local/bin/groonga(+0x8db6) [0x564c572ecdb6]
160
- 2017-04-24 13:01:10.344763|e| /tmp/local/bin/groonga(+0x9e7c) [0x564c572ede7c]
161
- 2017-04-24 13:01:10.344776|e| /tmp/local/bin/groonga(+0xa035) [0x564c572ee035]
162
- 2017-04-24 13:01:10.344788|e| /tmp/local/bin/groonga(+0x132b7) [0x564c572f72b7]
163
- 2017-04-24 13:01:10.344800|e| /tmp/local/bin/groonga(+0x18088) [0x564c572fc088]
164
- 2017-04-24 13:01:10.344813|e| /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0x7fe1872bf2b1]
165
- 2017-04-24 13:01:10.344825|e| /tmp/local/bin/groonga(+0x4e2a) [0x564c572e8e2a]
data/test/fixtures/run-regression-test/db.old/groonga.log DELETED
@@ -1,79 +0,0 @@
1
- 2017-04-24 11:06:44.872561|n| grn_init: <7.0.1-105-gf940037>
2
- 2017-04-24 11:06:44.872642|n| vm.overcommit_memory kernel parameter should be 1: <0>: See INFO level log to resolve this
3
- 2017-04-24 11:06:44.873832|n| DDL:256:table_create Entries
4
- 2017-04-24 11:06:44.929837|n| spec:256:update:Entries:48(table:hash_key):0
5
- 2017-04-24 11:06:44.930157|n| DDL:257:column_create Entries description
6
- 2017-04-24 11:06:44.979980|n| spec:257:update:Entries.description:65(column:var_size):15(Text)
7
- 2017-04-24 11:06:45.005342|n| grn_fin (0)
8
- 2017-04-24 11:06:45.013826|n| grn_init: <7.0.1-105-gf940037>
9
- 2017-04-24 11:06:45.013966|n| vm.overcommit_memory kernel parameter should be 1: <0>: See INFO level log to resolve this
10
- 2017-04-24 11:06:45.030106|n| grn_fin (0)
11
- 2017-04-24 11:06:45.038715|n| grn_init: <7.0.1-105-gf940037>
12
- 2017-04-24 11:06:45.038857|n| vm.overcommit_memory kernel parameter should be 1: <0>: See INFO level log to resolve this
13
- 2017-04-24 11:06:45.042555|n| DDL:258:table_create Bigram
14
- 2017-04-24 11:06:45.088700|n| spec:258:update:Bigram:49(table:pat_key):0
15
- 2017-04-24 11:06:45.089198|n| DDL:259:column_create Bigram Entries_description
16
- 2017-04-24 11:06:45.189880|n| spec:259:update:Bigram.Entries_description:72(column:index):256(Entries)
17
- 2017-04-24 11:06:45.210684|n| DDL:259:set_source Bigram.Entries_description Entries.description
18
- 2017-04-24 11:06:45.210758|n| spec:257:update:Entries.description:65(column:var_size):15(Text)
19
- 2017-04-24 11:06:45.215438|n| spec:259:update:Bigram.Entries_description:72(column:index):256(Entries)
20
- 2017-04-24 11:06:45.223494|n| grn_fin (0)
21
- 2017-04-24 11:06:46.117605|n| grn_init: <7.0.1-105-gf940037>
22
- 2017-04-24 11:06:46.117680|n| vm.overcommit_memory kernel parameter should be 1: <0>: See INFO level log to resolve this
23
- 2017-04-24 11:06:46.117807|n| RLIMIT_NOFILE(4096,4096)
24
- 2017-04-24 11:06:47.117914|n| thread start (0/1)
25
- 2017-04-24 11:06:47.495106|n| thread end (0/0)
26
- 2017-04-24 11:06:47.498049|n| grn_fin (0)
27
- 2017-04-24 11:07:45.260497|n| grn_init: <7.0.1-105-gf940037>
28
- 2017-04-24 11:07:45.260555|n| vm.overcommit_memory kernel parameter should be 1: <0>: See INFO level log to resolve this
29
- 2017-04-24 11:07:45.260635|n| RLIMIT_NOFILE(4096,4096)
30
- 2017-04-24 11:07:46.262231|n| thread start (0/1)
31
- 2017-04-24 11:07:49.196124|n| thread end (0/0)
32
- 2017-04-24 11:07:49.199045|n| grn_fin (0)
33
- 2017-04-24 11:10:47.015640|n| grn_init: <7.0.1-105-gf940037>
34
- 2017-04-24 11:10:47.015723|n| vm.overcommit_memory kernel parameter should be 1: <0>: See INFO level log to resolve this
35
- 2017-04-24 11:10:47.015811|n| RLIMIT_NOFILE(4096,4096)
36
- 2017-04-24 11:10:48.018144|n| thread start (0/1)
37
- 2017-04-24 11:10:50.858117|n| thread end (0/0)
38
- 2017-04-24 11:10:50.861057|n| grn_fin (0)
39
- 2017-04-24 11:11:12.604406|n| grn_init: <7.0.1-105-gf940037>
40
- 2017-04-24 11:11:12.604464|n| vm.overcommit_memory kernel parameter should be 1: <0>: See INFO level log to resolve this
41
- 2017-04-24 11:11:12.604542|n| RLIMIT_NOFILE(4096,4096)
42
- 2017-04-24 11:11:13.606243|n| thread start (0/1)
43
- 2017-04-24 11:11:42.304545|n| grn_init: <7.0.1-105-gf940037>
44
- 2017-04-24 11:11:42.304594|n| vm.overcommit_memory kernel parameter should be 1: <0>: See INFO level log to resolve this
45
- 2017-04-24 11:11:42.304674|n| RLIMIT_NOFILE(4096,4096)
46
- 2017-04-24 11:11:43.305717|n| thread start (0/1)
47
- 2017-04-24 11:11:46.066584|n| thread end (0/0)
48
- 2017-04-24 11:11:46.070501|n| grn_fin (0)
49
- 2017-04-24 11:12:06.886810|n| grn_init: <7.0.1-105-gf940037>
50
- 2017-04-24 11:12:06.886857|n| vm.overcommit_memory kernel parameter should be 1: <0>: See INFO level log to resolve this
51
- 2017-04-24 11:12:06.886933|n| RLIMIT_NOFILE(4096,4096)
52
- 2017-04-24 11:12:06.888501|n| thread start (0/1)
53
- 2017-04-24 11:12:10.568618|n| thread end (0/0)
54
- 2017-04-24 11:12:10.571785|n| grn_fin (0)
55
- 2017-04-24 11:12:21.462928|n| grn_init: <7.0.1-105-gf940037>
56
- 2017-04-24 11:12:21.462974|n| vm.overcommit_memory kernel parameter should be 1: <0>: See INFO level log to resolve this
57
- 2017-04-24 11:12:21.463054|n| RLIMIT_NOFILE(4096,4096)
58
- 2017-04-24 11:12:21.467367|n| thread start (0/1)
59
- 2017-04-24 11:12:25.201154|n| thread end (0/0)
60
- 2017-04-24 11:12:25.205066|n| grn_fin (0)
61
- 2017-04-24 11:19:59.312302|n| grn_init: <7.0.1-105-gf940037>
62
- 2017-04-24 11:19:59.312348|n| vm.overcommit_memory kernel parameter should be 1: <0>: See INFO level log to resolve this
63
- 2017-04-24 11:19:59.312424|n| RLIMIT_NOFILE(4096,4096)
64
- 2017-04-24 11:19:59.314172|n| thread start (0/1)
65
- 2017-04-24 11:20:02.950972|n| thread end (0/0)
66
- 2017-04-24 11:20:02.956336|n| grn_fin (0)
67
- 2017-04-24 11:20:09.443167|n| grn_init: <7.0.1-105-gf940037>
68
- 2017-04-24 11:20:09.443214|n| vm.overcommit_memory kernel parameter should be 1: <0>: See INFO level log to resolve this
69
- 2017-04-24 11:20:09.443297|n| RLIMIT_NOFILE(4096,4096)
70
- 2017-04-24 11:20:10.445853|n| thread start (0/1)
71
- 2017-04-24 11:20:10.789276|n| thread end (0/0)
72
- 2017-04-24 11:20:10.792230|n| grn_fin (0)
73
- 2017-04-24 13:01:10.343392|e| system call error: Interrupted system call: epoll_wait
74
- 2017-04-24 13:01:10.343699|e| /tmp/local/lib/libgroonga.so.0(grn_com_event_poll+0x600) [0x7f8575c9c5cf]
75
- 2017-04-24 13:01:10.343722|e| groonga(+0xc58b) [0x56012441658b]
76
- 2017-04-24 13:01:10.343737|e| groonga(+0xde2e) [0x560124417e2e]
77
- 2017-04-24 13:01:10.343748|e| groonga(+0x54e0) [0x56012440f4e0]
78
- 2017-04-24 13:01:10.343759|e| /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1) [0x7f857478d2b1]
79
- 2017-04-24 13:01:10.343771|e| groonga(+0x5e6a) [0x56012440fe6a]
data/test/fixtures/run-regression-test/results/query.log DELETED
File without changes