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

Run cirque test with GDB for backtrace #6946

Merged
merged 2 commits into from
May 21, 2021
Merged

Run cirque test with GDB for backtrace #6946

merged 2 commits into from
May 21, 2021

Conversation

yufengwangca
Copy link
Contributor

@yufengwangca yufengwangca commented May 18, 2021

Problem

Currently, Cirque is still disabled and we are running Cirque tests manually from our debug branch with GDB enabled. Enabling GDB for Cirque on master branch will help us run the regression check manually directly from master ToT with backtrace.

Change overview

Use GDB to run cirque test for IM and Echo for backtrace

Testing

How was this tested?

Cirque is still disabled, testing is done manually with the following steps:

Setting up cirque environment
git submodule update --init
./scripts/tests/cirque_tests.sh bootstrap

Run all tests
./scripts/tests/cirque_tests.sh run_all_tests

Currently, Cirque test always failed, confirmed backtrace stack is dumped when test failed.

@andy31415
Copy link
Contributor

Could you add a 'how did you test' section to the summary?

Copy link
Contributor

@woody-apple woody-apple left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Per the updated template, can you update the PR here?

#### Problem
What is being fixed?  Examples:
* Fix crash on startup
* Fixes #12345 12345 Frobnozzle is leaky (exactly like that, so GitHub will auto-close the issue).

#### Change overview
What's in this PR

#### Testing
How was this tested? (at least one bullet point required)
    • If unit tests were added, how do they cover this issue?
    • If unit tests existed, how were they fixed/modified to prevent this in future?
    • If integration tests were added, how do they verify this change?
    • If manually tested, what platforms controller and device platforms were manually tested, and how?
    • If no testing is required, why not?

@yufengwangca yufengwangca requested a review from woody-apple May 20, 2021 19:11
@yufengwangca
Copy link
Contributor Author

Per the updated template, can you update the PR here?

#### Problem
What is being fixed?  Examples:
* Fix crash on startup
* Fixes #12345 12345 Frobnozzle is leaky (exactly like that, so GitHub will auto-close the issue).

#### Change overview
What's in this PR

#### Testing
How was this tested? (at least one bullet point required)
    • If unit tests were added, how do they cover this issue?
    • If unit tests existed, how were they fixed/modified to prevent this in future?
    • If integration tests were added, how do they verify this change?
    • If manually tested, what platforms controller and device platforms were manually tested, and how?
    • If no testing is required, why not?

Done

@saurabhst saurabhst merged commit 58e35f9 into project-chip:master May 21, 2021
@yufengwangca yufengwangca deleted the pr/cirque/gdb branch May 21, 2021 16:29
nikita-s-wrk pushed a commit to nikita-s-wrk/connectedhomeip that referenced this pull request Sep 23, 2021
* Run cirque test with GDB for backtrace

* Add option to allow exit after processing options
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants