Clarify test descriptions in test_suite_memory_buffer_alloc #310
No reviewers
Labels
No labels
api-spec
bug
CLA requested
CLA valid
compliance
DO NOT MERGE
duplicate
enhancement
feature branch
good first issue
HEADER FORMATTING ISSUE
help wanted
Information
invalid
Jira status: AWAITING REVIEW
Jira status: CLOSED
Jira status: DONE
Jira status: IN PROGRESS
Jira status: IN REVIEW
Jira status: OPEN
Jira status: REOPENED
Jira status: RESOLVED
mirrored
mirror internally
needs: backports
needs: ci
needs: design review
needs: preceding PR
needs: review
needs: work
notabug
open for community contribution
Product Backlog
question
ready for merge
security
stale
type: bug
type: enhancement
type: question
web pages
wontfix
writing
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-ARMmbed/mbed-crypto!310
Loading…
Reference in a new issue
No description provided.
Delete branch "memory_buffer_alloc-fatal-pass"
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?
One test case prints "FATAL: verification of first header failed". This is actually expected because the test case deliberately sets up a heap that can't have a valid first header. Clarify that in the test description and in the code. Fix #309.
I also removed some spurious dependencies on
MBEDTLS_MEMORY_DEBUGin that test suite. I'm not touching the test scripts: that's out of scope and memory_buffer_alloc is only minimally maintained so doesn't deserve extra testing.Should be backported to Mbed TLS LTS branches.
Passing CI run: https://jenkins-internal.mbed.com/job/mbed-crypto-pr/job/PR-310-merge/9/
Backports: https://github.com/ARMmbed/mbedtls/pull/2936 https://github.com/ARMmbed/mbedtls/pull/2937