File: skip-test-that-depends-on-server.patch

package info (click to toggle)
ruby-mysql2 0.5.7-1
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 1,116 kB
  • sloc: ansic: 3,534; ruby: 3,447; sh: 297; makefile: 3
file content (29 lines) | stat: -rw-r--r-- 1,024 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
From: Antonio Terceiro <terceiro@debian.org>
Date: Thu, 30 Nov 2023 07:21:08 -0500
Subject: skip test that depends on the server implementation

Origin: vendor
Forwarded: no
Last-Update: 2023-11-30

With mariadb 10.5, the server doesn't seem to create a new entry in
prepared_statements_instances, at least not for "SELECT 1". In any case,
having a test that depends on the server side implementation does not look
like a good idea.
---
 spec/mysql2/statement_spec.rb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/spec/mysql2/statement_spec.rb b/spec/mysql2/statement_spec.rb
index 5e99f32..5ff6915 100644
--- a/spec/mysql2/statement_spec.rb
+++ b/spec/mysql2/statement_spec.rb
@@ -20,7 +20,7 @@ RSpec.describe Mysql2::Statement do
     end
   end
 
-  it "should create a statement" do
+  xit "should create a statement" do
     statement = nil
     expect { statement = @client.prepare 'SELECT 1' }.to change(&method(:stmt_count)).by(1)
     expect(statement).to be_an_instance_of(Mysql2::Statement)