-
Notifications
You must be signed in to change notification settings - Fork 0
[PW_SID:951852] [v2] obex: Send response to client for Abort request #2773
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
base: workflow
Are you sure you want to change the base?
Conversation
This patch adds workflow files for ci:
[sync.yml]
- runs every 30 mins.
- sync repo with upstream repo and rebase workflow branch to tip of
master.
- creates PR after reading patches from patchwork.kernel.org
[ci.yml]
- Tests the following checks:
- checkpatch
- gitlint
- make
- make check
[code_scan.yml]
- Static code checker: Coverity and Clang
- Coverity: Submit the result to the coverity website
- Clang Code Scan: Send email with result file to the internal team
To simplify the history, new change will amend to this patch without
creating new patch.
Incase of ongoing transfer, If the client sends Abort request, Server is not sending any response back. Ideally it should send OK or Success reponse code for the abort command. This is required in PTS testing for passing below testcases - 1) OPP/SR/OPH/BV-27-I To verify that a server can respond to an ABORT from the client during an OBEX operation. 2)FTP/SR/OTR/BV-02-C To verify that the pushed file is aborted normally. 3)PBAP/PSE/PDF/BV-06-I Verify that the PCE can abort a Phone Book object download from the PSE. 4)PBAP/PSE/PBF/BV-03-I Verify that the PCE can abort a vCard-listing object download from the PSE.
|
CheckPatch |
|
GitLint |
|
BuildEll |
|
BluezMake |
|
MakeCheck |
|
MakeDistcheck |
|
CheckValgrind |
|
CheckSmatch |
|
bluezmakeextell |
|
IncrementalBuild |
|
ScanBuild |
df874a4 to
b5c1fe6
Compare
Incase of ongoing transfer, If the client sends Abort request, Server is not
sending any response back.
Ideally it should send OK or Success reponse code for the abort command.
This is required in PTS testing for passing below testcases -
To verify that a server can respond to an ABORT from the client during an OBEX operation.
2)FTP/SR/OTR/BV-02-C
To verify that the pushed file is aborted normally.
3)PBAP/PSE/PDF/BV-06-I
Verify that the PCE can abort a Phone Book object download from the PSE.
4)PBAP/PSE/PBF/BV-03-I
Verify that the PCE can abort a vCard-listing object download from the PSE.
obexd/src/obex.c | 2 ++
1 file changed, 2 insertions(+)