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

merge with runctst #78

Closed
ghost opened this issue Aug 28, 2019 · 10 comments
Closed

merge with runctst #78

ghost opened this issue Aug 28, 2019 · 10 comments

Comments

@ghost
Copy link

ghost commented Aug 28, 2019

In the runc era, there is a testsuite called runctst that has been matured in testing on RHEL and occasionally Fedora, which depend only on skopeo and python3-psutils.

crun has its own tests which are similar which seems have less testing coverage than runctst. Do you think it make sense to merge runctst into the crun tests to have one single python file that could use for regression testing?

@rhatdan
Copy link
Member

rhatdan commented Aug 28, 2019

Yes I think that is a great idea.

@ghost
Copy link
Author

ghost commented Aug 28, 2019

OK. Moreover, I will be looking into rewriting all the tests in C by which crun is written. With a bit luck, it might end up getting ride of dependencies on skopeo and python3-psutils.

@giuseppe
Copy link
Member

@CAILCA yes thanks, that will be helpful. I've not added more tests as for Travis I am already using the oci-validation tests and the libpod tests.

Is there any reason why you'd like to drop these dependencies? I think it is fine to have them for the tests. Keeping the tests in Python is much nicer than handling JSON in C.

@ghost
Copy link
Author

ghost commented Aug 28, 2019

OK, stick with Python is probably fine then. The original thought was that since the purpose here is to test crun, so we don't need to spend time on dealing bugs in skopeo. For python3-psutils, it is not part of standard library and has to install separately, but no biggies.

@giuseppe
Copy link
Member

@CAILCA is there any work going on for this issue?

@ghost
Copy link
Author

ghost commented Sep 10, 2019

Unfortunately, no. I have been buried with something else at the moment.

@ghost ghost mentioned this issue Sep 18, 2019
@rhatdan
Copy link
Member

rhatdan commented Oct 1, 2019

Totally untested
ocitst.py

Basically change all references to 'runc' to oci and then set oci based on args[0] of the command or based on environment variable or default to runc.

@giuseppe
Copy link
Member

@CAILCA any movement here or can we close this issue?

@ghost
Copy link
Author

ghost commented Feb 13, 2020

I don't think I'll get to this now. Unless there is someone else to pick it up, feel free to close it.

@giuseppe
Copy link
Member

ok thanks, let's reopen if things change

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants