aboutsummaryrefslogtreecommitdiffstats
path: root/tools/test.rb
diff options
context:
space:
mode:
authorRyuta Kamizono <kamipo@gmail.com>2019-05-22 01:23:58 +0900
committerRyuta Kamizono <kamipo@gmail.com>2019-05-22 01:23:58 +0900
commit3453c5d4c0b54fc2a117a09ff4d5964110f5fbe8 (patch)
tree3d65a3958d6dad7bfad421f592de2f0650c21ed8 /tools/test.rb
parent36f6327b75820e19b0018c1e7afd4b30d1218002 (diff)
downloadrails-3453c5d4c0b54fc2a117a09ff4d5964110f5fbe8.tar.gz
rails-3453c5d4c0b54fc2a117a09ff4d5964110f5fbe8.tar.bz2
rails-3453c5d4c0b54fc2a117a09ff4d5964110f5fbe8.zip
Give up filling schema cache before `assert_no_queries`
This reverts commit a1ee4a9ff9d4a3cb255365310ead0dc7b739c6be. Even if a1ee4a9 is applied, CI is still flakiness. https://buildkite.com/rails/rails/builds/61252#2c090afa-aa84-4a2b-8b81-9f09219222c6/994-1005 https://buildkite.com/rails/rails/builds/61252#2e55bf83-1bde-44a2-a4f1-b5c3f6820fb4/929-938 Failing tests by whether schema cache is filled or not, it actually means that whether SCHEMA SQLs are executed or not is not target for the tests. So I've reverted commit a1ee4a9 which filling schema cache before `assert_no_queries`, and replace `assert_no_queries` to `assert_queries(0)`.
Diffstat (limited to 'tools/test.rb')
0 files changed, 0 insertions, 0 deletions