-
Notifications
You must be signed in to change notification settings - Fork 11
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
Future roadmap and bugfixes #10
Labels
documentation
Improvements or additions to documentation
Comments
arunkoshy
added
good first issue
Good for newcomers
documentation
Improvements or additions to documentation
and removed
good first issue
Good for newcomers
labels
Feb 7, 2022
Opened PR #24 |
arunkoshy
changed the title
Port issues / discussions from old repo
Port & refactor documentation / issues / discussions from old repo
Mar 21, 2022
arunkoshy
changed the title
Port & refactor documentation / issues / discussions from old repo
Future roadmap and bugfixes
Mar 21, 2022
via @gregg-shick -- GUI , rough thoughts --
-- Acro code needed --
-- Other bugs --
|
-- security future integrations --
-- security work --
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Engineer:
Port & refactor documentation / issues / discussions from old repo:
-- build --
-- contest future work --
Update from discussions with OCP community
Question: will contest comply in future to the OCP spec which is currently under dev?
Answer(s):
contest has support for some stuff already - they're under the exec plugin:
https://github.com/linuxboot/contest/tree/main/plugins/teststeps/exec
The plugin was written to run external binaries of any sort, locally or remote thru ssh (see transport), and there's an ocp_output flag for it to look for that output on stdout; otherwise it just says started event , ended event
and result is based on exit code (still in the ocp_output=false case) with ocp_output=true, it looks for result in testRunEnd (or whatever the name of that message was), and creates additional events for stuff that happens inside the test (doesn't have measurements iirc) is it correct to assume that eventually contest will also comply
Summary: after OCP publish v1 of spec, maintainers will probably add the rest of the messages parsing
The text was updated successfully, but these errors were encountered: