groonga-query-log 1.5.0 → 1.5.1

Sign up to get free protection for your applications and to get access to all the features.
Files changed (33) hide show
  1. checksums.yaml +4 -4
  2. data/doc/text/news.md +15 -0
  3. data/lib/groonga-query-log/command-line.rb +2 -1
  4. data/lib/groonga-query-log/command/check-performance-regression.rb +9 -8
  5. data/lib/groonga-query-log/command/run-regression-test.rb +4 -3
  6. data/lib/groonga-query-log/response-comparer.rb +5 -2
  7. data/lib/groonga-query-log/version.rb +1 -1
  8. data/test/#test-response-comparer.rb# +14750 -0
  9. data/test/command/test-run-regression-test.rb +37 -2
  10. data/test/fixtures/{regression-test-logs/results/url-format.log → run-regression-test/mail-notifier/failure.log} +0 -0
  11. data/test/fixtures/run-regression-test/{results/query.log → mail-notifier/success.log} +0 -0
  12. data/test/test-response-comparer.rb +30 -0
  13. metadata +45 -84
  14. data/test/fixtures/run-regression-test/db.new/db +0 -0
  15. data/test/fixtures/run-regression-test/db.new/db.0000000 +0 -0
  16. data/test/fixtures/run-regression-test/db.new/db.0000100 +0 -0
  17. data/test/fixtures/run-regression-test/db.new/db.0000101 +0 -0
  18. data/test/fixtures/run-regression-test/db.new/db.0000102 +0 -0
  19. data/test/fixtures/run-regression-test/db.new/db.0000103 +0 -0
  20. data/test/fixtures/run-regression-test/db.new/db.0000103.c +0 -0
  21. data/test/fixtures/run-regression-test/db.new/db.001 +0 -0
  22. data/test/fixtures/run-regression-test/db.new/db.conf +0 -0
  23. data/test/fixtures/run-regression-test/db.new/groonga.log +0 -165
  24. data/test/fixtures/run-regression-test/db.old/db +0 -0
  25. data/test/fixtures/run-regression-test/db.old/db.0000000 +0 -0
  26. data/test/fixtures/run-regression-test/db.old/db.0000100 +0 -0
  27. data/test/fixtures/run-regression-test/db.old/db.0000101 +0 -0
  28. data/test/fixtures/run-regression-test/db.old/db.0000102 +0 -0
  29. data/test/fixtures/run-regression-test/db.old/db.0000103 +0 -0
  30. data/test/fixtures/run-regression-test/db.old/db.0000103.c +0 -0
  31. data/test/fixtures/run-regression-test/db.old/db.001 +0 -0
  32. data/test/fixtures/run-regression-test/db.old/db.conf +0 -0
  33. data/test/fixtures/run-regression-test/db.old/groonga.log +0 -79
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]