Skip to content

Ignore Uninteresting test warnings during test teardown#26161

Open
zvecr wants to merge 1 commit intoqmk:developfrom
zvecr:test_uninteresting_warnings
Open

Ignore Uninteresting test warnings during test teardown#26161
zvecr wants to merge 1 commit intoqmk:developfrom
zvecr:test_uninteresting_warnings

Conversation

@zvecr
Copy link
Copy Markdown
Member

@zvecr zvecr commented Apr 18, 2026

Description

Tests currently output the following warning:

GMOCK WARNING:
Uninteresting mock function call - returning directly.
    Function call: send_keyboard_mock(@0x55fc66e71950 report:   empty
)
NOTE: You can safely ignore the above warning unless this call should not happen.  Do not suppress it by blindly adding an EXPECT_CALL() if you don't mean to enforce the call.  See https://github.com/google/googletest/blob/master/docs/gmock_cook_book.md#knowing-when-to-expect for details.

Types of Changes

  • Core
  • Bugfix
  • New feature
  • Enhancement/optimization
  • Keyboard (addition or update)
  • Keymap/layout (addition or update)
  • Documentation

Issues Fixed or Closed by This PR

Checklist

  • My code follows the code style of this project: C, Python
  • I have read the PR Checklist document and have made the appropriate changes.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • I have tested the changes and verified that they work and don't break anything (as well as I can manage).

@github-actions github-actions Bot added the core label Apr 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant