Skip to content
This repository has been archived by the owner on May 12, 2021. It is now read-only.

create/run: Make bundle path default to cwd #836

Conversation

jodh-intel
Copy link
Contributor

The bundle path was documented as defaulting to the current directory
but was not being set to that value if not explicitly specified.

Fixes #821.

(cherry picked from commit 8831245)

Signed-off-by: James O. D. Hunt james.o.hunt@intel.com

Copy link
Contributor

@grahamwhaley grahamwhaley left a comment

Choose a reason for hiding this comment

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

lgtm

@devimc
Copy link

devimc commented Oct 18, 2018

/test

@codecov
Copy link

codecov bot commented Oct 18, 2018

Codecov Report

Merging #836 into stable-1.1 will decrease coverage by 0.02%.
The diff coverage is 66.66%.

@@              Coverage Diff               @@
##           stable-1.1     #836      +/-   ##
==============================================
- Coverage        65.2%   65.18%   -0.03%     
==============================================
  Files              80       80              
  Lines            8238     8244       +6     
==============================================
+ Hits             5372     5374       +2     
- Misses           2320     2322       +2     
- Partials          546      548       +2

@WeiZhang555
Copy link
Member

/test

@jodh-intel jodh-intel force-pushed the stable-1.1-fix-default-bundle-path branch 2 times, most recently from 5b7f143 to 746060f Compare October 24, 2018 16:43
@jodh-intel
Copy link
Contributor Author

/test

@jodh-intel
Copy link
Contributor Author

Blocked on kata-containers/tests#856.

@bergwolf
Copy link
Member

bergwolf commented Oct 29, 2018

LGTM.

Blocked on kata-containers/tests#856.

@jodh-intel the bloker PR has been merged but it is targeted at the master branch of tests repo. Do you mean we use the tests repo master branch to validate stable-1.1?

Approved with PullApprove

@jodh-intel
Copy link
Contributor Author

Hi @bergwolf - no, we need to merge the fix on #856 into the stable branches before the CI will work on these two stable PRs. But #856 depends on some other CI changes that haven't yet been ported into the stable branches. I'll try to resolve all this today...

@bergwolf
Copy link
Member

I see. Thanks @jodh-intel !

@sboeuf
Copy link

sboeuf commented Nov 5, 2018

@jodh-intel any progress on this?

@jodh-intel
Copy link
Contributor Author

¡mañana! Well, Monday maybe ;)

@grahamwhaley
Copy link
Contributor

I think #856 has merged - cannot tell if the other bits are fixed, but let's do a...
/test
why not.

The bundle path was documented as defaulting to the current directory
but was not being set to that value if not explicitly specified.

Fixes kata-containers#821.

(cherry picked from commit 8831245)

Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
@jodh-intel jodh-intel force-pushed the stable-1.1-fix-default-bundle-path branch from 746060f to 2061ad7 Compare November 22, 2018 14:48
@jodh-intel jodh-intel merged commit e59584e into kata-containers:stable-1.1 Nov 22, 2018
egernst pushed a commit to egernst/runtime that referenced this pull request Feb 9, 2021
Fix potential major:minor conflicts during device updates
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants