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

Bluetooth: controller: legacy: Backport conformance test related changes #25314

Closed
cvinayak opened this issue May 14, 2020 · 5 comments
Closed
Assignees
Labels
bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug Stale
Milestone

Comments

@cvinayak
Copy link
Contributor

Describe the bug
During conformance testing of v2.2-branch, numerous implementation fixes related to conformance test changes and failures were undertaken. These fixes are missing in legacy controller in v1.14-branch.

To Reproduce
Re-run conformance testing using hci_uart application in v1.14-branch

Expected behavior
Bluetooth Controller in v1.14-branch shall meet the same level of quality as v2.2-branch for a said Bluetooth v5.1 qualified design listing.

Impact
showstopper

Screenshots or console output
NA

Environment (please complete the following information):

  • OS: Linux
  • Toolchain Zephyr SDK
  • Commit SHA or Version used: v1.14.2

Additional context
backport PR #23091

@cvinayak cvinayak added the bug The issue is a bug, or the PR is fixing a bug label May 14, 2020
@cvinayak cvinayak added this to the v1.14.3 milestone May 14, 2020
@MaureenHelm MaureenHelm added the priority: low Low impact/importance bug label Jun 16, 2020
@github-actions
Copy link

This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.

@github-actions github-actions bot added the Stale label Aug 16, 2020
@cvinayak
Copy link
Contributor Author

This issue corresponds to #23091

@github-actions github-actions bot removed the Stale label Aug 18, 2020
@MaureenHelm MaureenHelm added this to To do in Backports Aug 18, 2020
@carlescufi
Copy link
Member

@cvinayak does #23091 fix this issue?

@MaureenHelm MaureenHelm removed this from To do in Backports Sep 22, 2020
@cvinayak
Copy link
Contributor Author

@cvinayak does #23091 fix this issue?

@carlescufi Yes.

@github-actions
Copy link

This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug Stale
Projects
None yet
Development

No branches or pull requests

3 participants