Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mysql80: Mysql2::Client session_track fails on mysql >= 8.0.20 or 8.0.21? #1165

Closed
junaruga opened this issue Feb 12, 2021 · 5 comments
Closed

Comments

@junaruga
Copy link
Contributor

I like to open the ticket of this test failure on mysql80 case, coming from #1154 (comment) . Actually I see this issue happens on the current Travis too.

Failures:
  1) Mysql2::Client session_track returns multiple session track type values when available
     Failure/Error: expect(res).to eq(["________"])

       expected: ["________"]
            got: nil
     
       (compared using ==)
     # ./spec/mysql2/client_spec.rb:1053:in `block (3 levels) in <top (required)>'

Seeing the history of builds.

@junaruga
Copy link
Contributor Author

@junaruga junaruga changed the title mysql80: Mysql2::Client session_track fails on mysql 8.0.21? mysql80: Mysql2::Client session_track fails on mysql >= 8.0.20 or 8.0.21? Feb 12, 2021
@junaruga
Copy link
Contributor Author

junaruga commented Feb 27, 2021

You can see the reproducer of this issue on the following cases in GitHub Actions.

@sodabrew
Copy link
Collaborator

sodabrew commented Mar 2, 2021

Specifically this release note looks like the culprit:

The Performance Schema collected session-related statistics for errors that can occur only globally and not per session. This is no longer done, reducing memory overhead for error instrumentation. Additionally, rows for global errors are no longer included in error summaries reported per thread, account, user, or host. (Bug #30311574)

@junaruga
Copy link
Contributor Author

It seems it was fixed. See #1220 (comment) .

jeremyolliver pushed a commit to jeremyolliver/mysql2 that referenced this issue Nov 1, 2022
@Faq
Copy link

Faq commented Dec 17, 2022

As this is closed, noone updated those comments:

# Use ubuntu-18.04 instead of ubuntu-20.04 temporarily, due to a failing test on mysql 8.0.

sodabrew pushed a commit that referenced this issue Dec 28, 2022
As we fixed some of the issues, we can drop the allow-failure option in some
cases. #1165 was resolved by mysql2 0.5.4, while #1194 needs attention.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants