devs/cproof
1
2
Fork 1
Code Issues 43 Pull Requests 6 Actions Packages Projects 1 Releases Wiki Activity

WIP: Fix cmocka 2.0 compatibility #69

Closed
jabber.developer2 wants to merge 1 commits from fix/cmocka-2.0-compatibility into master
pull from: fix/cmocka-2.0-compatibility
merge into: devs:master
Conversation 1 Commits 1 Files Changed 1 +17
jabber.developer2 commented 2026-01-16 13:44:54 +00:00
Collaborator
Copy Link

Description:

Problem

cmocka 2.0 (released December 2025) deprecated several APIs used by profanity unit tests:

  • will_return() → use will_return_int(), will_return_ptr()
  • check_expected() → use check_expected_int(), check_expected_ptr()
  • mock_type() → use mock_int(), mock_ptr_type()

This breaks CI builds on rolling-release distros:

  • Debian testing (cmocka 2.0.1)
  • openSUSE Tumbleweed (cmocka 2.0.2)

Solution

Add CMOCKA_DISABLE_DEPRECATION_WARNINGS define in prof_cmocka.h before including <cmocka.h>. This suppresses deprecation warnings and allows deprecated APIs to work correctly in cmocka 2.0.

This is the recommended approach by cmocka maintainers for projects that need to support both cmocka 1.x and 2.x.

Changes

  • prof_cmocka.h: Add #define CMOCKA_DISABLE_DEPRECATION_WARNINGS 1 before cmocka include

Testing

  • ✅ Tested with cmocka 1.1.x (Debian bookworm, Fedora, Arch, Ubuntu)
  • ✅ Tested with cmocka 2.0.x (Debian testing)

Future work

Consider migrating to type-safe cmocka 2.0 APIs (will_return_int(), mock_int(), etc.) for better type checking. This would require ~300 changes across test files.

**Description:** ### Problem cmocka 2.0 (released December 2025) deprecated several APIs used by profanity unit tests: - `will_return()` → use `will_return_int()`, `will_return_ptr()` - `check_expected()` → use `check_expected_int()`, `check_expected_ptr()` - `mock_type()` → use `mock_int()`, `mock_ptr_type()` This breaks CI builds on rolling-release distros: - Debian testing (cmocka 2.0.1) - openSUSE Tumbleweed (cmocka 2.0.2) ### Solution Add `CMOCKA_DISABLE_DEPRECATION_WARNINGS` define in prof_cmocka.h before including `<cmocka.h>`. This suppresses deprecation warnings and allows deprecated APIs to work correctly in cmocka 2.0. This is the recommended approach by cmocka maintainers for projects that need to support both cmocka 1.x and 2.x. ### Changes - prof_cmocka.h: Add `#define CMOCKA_DISABLE_DEPRECATION_WARNINGS 1` before cmocka include ### Testing - ✅ Tested with cmocka 1.1.x (Debian bookworm, Fedora, Arch, Ubuntu) - ✅ Tested with cmocka 2.0.x (Debian testing) ### Future work Consider migrating to type-safe cmocka 2.0 APIs (`will_return_int()`, `mock_int()`, etc.) for better type checking. This would require ~300 changes across test files.
jabber.developer2 added 1 commit 2026-01-16 13:44:54 +00:00
feat: update compatibility header for cmocka 2.0 deprecation handling
All checks were successful
CI Code / Check spelling (pull_request) Successful in 19s
Details
CI Code / Check coding style (pull_request) Successful in 34s
Details
CI Code / Linux (debian) (pull_request) Successful in 1h5m4s
Details
CI Code / Linux (ubuntu) (pull_request) Successful in 1h7m47s
Details
CI Code / Linux (arch) (pull_request) Successful in 1h8m8s
Details
aee32ecbf8
jabber.developer changed title from Fix cmocka 2.0 compatibility to WIP: Fix cmocka 2.0 compatibility 2026-01-17 16:37:59 +00:00
jabber.developer2 commented 2026-06-19 07:24:00 +00:00
Author
Collaborator
Copy Link

Not needed anymore

Not needed anymore
jabber.developer2 deleted branch fix/cmocka-2.0-compatibility 2026-06-19 07:24:15 +00:00
Some checks are pending
CI Code / Check spelling (pull_request) Successful in 19s
Required
Details
CI Code / Check coding style (pull_request) Successful in 34s
Required
Details
CI Code / Linux (debian) (pull_request) Successful in 1h5m4s
Required
Details
CI Code / Linux (ubuntu) (pull_request) Successful in 1h7m47s
Required
Details
CI Code / Linux (arch) (pull_request) Successful in 1h8m8s
Required
Details
CI Code / Code Coverage (pull_request)
Required

Pull request closed

This pull request cannot be reopened because the branch was deleted.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
Kind/Bug
Something is not working
Kind/Documentation
Documentation changes
Kind/Enhancement
Improve existing functionality
Kind/Feature
New functionality
Kind/Security
This is security issue
Kind/Testing
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
admin jabber.developer jabber.developer2
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: devs/cproof#69
No description provided.
Delete Branch "fix/cmocka-2.0-compatibility"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?