Skip to content
This repository was archived by the owner on Jun 28, 2024. It is now read-only.

stability: fix fc name in hypervisor kill tests#1847

Merged
GabyCT merged 1 commit intokata-containers:masterfrom
bergwolf:fc-name
Jul 24, 2019
Merged

stability: fix fc name in hypervisor kill tests#1847
GabyCT merged 1 commit intokata-containers:masterfrom
bergwolf:fc-name

Conversation

@bergwolf
Copy link
Copy Markdown
Member

Instead of taking the full path name of the hypervisors, we need to
change to use only the name of the process because with jailer we have
different path shown there.

Fixes: #1846

bergwolf added a commit to bergwolf/kata-runtime that referenced this pull request Jul 23, 2019
Because the tests repo doesn't test fc, I have to use the runtime
repo ci to validate a tests PR for fc CI, for now.

Fixes: #999999
Depends-on: github.com/kata-containers/tests#1847
Signed-off-by: Peng Tao <bergwolf@hyper.sh>
Copy link
Copy Markdown
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
but I thought we'd already fixed this? @GabyCT @mcastelino

# Set the runtime if not set already
RUNTIME="${RUNTIME:-kata-runtime}"

HYPERVISOR_NAME=$(basename ${HYPERVISOR_PATH})
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

nit: you can use shell magic here like ${HYPERVISOR_PATH%/*} or similar ;-)

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Wow, that is real magic ;)

@bergwolf
Copy link
Copy Markdown
Member Author

Because tests repo doesn't validate fc in CI, I'm trying to test it in a runtime PR, see kata-containers/runtime#1905

@bergwolf
Copy link
Copy Markdown
Member Author

@grahamwhaley It's the same issue but in a different test case -- the one I just added to killing hypervisor process.

@bergwolf bergwolf force-pushed the fc-name branch 2 times, most recently from 97026ac to 6765b0d Compare July 23, 2019 12:21
@chavafg
Copy link
Copy Markdown
Contributor

chavafg commented Jul 23, 2019

/test

@chavafg
Copy link
Copy Markdown
Contributor

chavafg commented Jul 23, 2019

@GabyCT any idea of why fc job is not being triggered here?

@GabyCT
Copy link
Copy Markdown
Contributor

GabyCT commented Jul 23, 2019

/test

@GabyCT
Copy link
Copy Markdown
Contributor

GabyCT commented Jul 23, 2019

@chavafg I can see that now is being triggered

@chavafg
Copy link
Copy Markdown
Contributor

chavafg commented Jul 23, 2019

thanks @GabyCT, I see it now 😄

@GabyCT
Copy link
Copy Markdown
Contributor

GabyCT commented Jul 23, 2019

/test-fc

@GabyCT
Copy link
Copy Markdown
Contributor

GabyCT commented Jul 23, 2019

@bergwolf , if you want to launch the fc CI only you can use /test-fc to run only that job or '/test` and will run all the CI

@bergwolf
Copy link
Copy Markdown
Member Author

/test

@bergwolf bergwolf force-pushed the fc-name branch 2 times, most recently from e84573c to d0d6e81 Compare July 24, 2019 03:19
@bergwolf
Copy link
Copy Markdown
Member Author

/test

@bergwolf
Copy link
Copy Markdown
Member Author

/test-fc

Instead of taking the full path name of the hypervisors, we need to
change to use only the name of the process because with jailer we have
different path shown there.

Fixes: kata-containers#1848
Signed-off-by: Peng Tao <bergwolf@hyper.sh>
@bergwolf
Copy link
Copy Markdown
Member Author

/test

@GabyCT GabyCT merged commit fa89483 into kata-containers:master Jul 24, 2019
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.

firecracker is not tested here

5 participants