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

test: fix TestRunWithoutCapability not take effect #2573

Merged
merged 1 commit into from
Dec 25, 2018
Merged

test: fix TestRunWithoutCapability not take effect #2573

merged 1 commit into from
Dec 25, 2018

Conversation

Ace-Tang
Copy link
Contributor

fix TestRunWithoutCapability not check error, test alway get pass
even the test is fail.

Signed-off-by: Ace-Tang aceapril@126.com

Ⅰ. Describe what this PR did

Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗?)

Ⅳ. Describe how to verify it

Ⅴ. Special notes for reviews

fix TestRunWithoutCapability not check error, test alway get pass
even the test is fail.

Signed-off-by: Ace-Tang <aceapril@126.com>
@codecov
Copy link

codecov bot commented Dec 19, 2018

Codecov Report

Merging #2573 into master will decrease coverage by 0.03%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #2573      +/-   ##
==========================================
- Coverage   69.16%   69.13%   -0.04%     
==========================================
  Files         278      278              
  Lines       18686    18686              
==========================================
- Hits        12925    12919       -6     
+ Misses       4290     4288       -2     
- Partials     1471     1479       +8
Flag Coverage Δ
#criv1alpha1test 31.26% <ø> (-0.15%) ⬇️
#criv1alpha2test 35.7% <ø> (+0.05%) ⬆️
#integrationtest 40.73% <ø> (ø) ⬆️
#nodee2etest 32.71% <ø> (-0.12%) ⬇️
#unittest 26.66% <ø> (ø) ⬆️
Impacted Files Coverage Δ
cri/v1alpha2/cri_wrapper.go 64.4% <0%> (-1.2%) ⬇️
cri/v1alpha1/cri.go 60.26% <0%> (-0.67%) ⬇️
cri/v1alpha2/cri.go 69.11% <0%> (-0.63%) ⬇️
cri/v1alpha2/cri_utils.go 89.64% <0%> (-0.29%) ⬇️
daemon/mgr/container.go 58.79% <0%> (-0.22%) ⬇️
daemon/logger/jsonfile/utils.go 73.17% <0%> (+1.62%) ⬆️
pkg/streams/utils.go 91.66% <0%> (+9.52%) ⬆️

@Ace-Tang
Copy link
Contributor Author

Bad reporter codecov/project

@ZYecho
Copy link
Contributor

ZYecho commented Dec 20, 2018

LGTM

@allencloud
Copy link
Collaborator

Do we need to make the lowercase of capability invalid when validating API request in daemon side? @Ace-Tang @ZYecho @fuweid

@Ace-Tang
Copy link
Contributor Author

But actually lowercase way is allowed , I just make full code format consistent

@allencloud allencloud merged commit ae86ab3 into AliyunContainerService:master Dec 25, 2018
@Ace-Tang Ace-Tang deleted the fix_test branch December 25, 2018 07:51
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.

5 participants