Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Add FreeBSD Jail execution environment support #224
Add FreeBSD Jail execution environment support #224
Changes from all commits
a4737b1
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(picking the first instance)
The syntax version should be bumped for an interface change/addition like this.
This allows the engine to treat function in a backwards compatible manner with the older Kyuafiles by not dealing with the execenv related syntax.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for opening this topic. I was thinking about this, but I decided not to make a move and postpone its discussion due to lack of strong opinions on my side. In terms of "syntax" term it's not changed, only extra metadata can be defined (if we think about metadata as a free set of key-value), but, probably, the project's philosophy/design means any change should bump the version -- this is where long term maintainer's opinion is expected. Also, I've found no direct support of versioning in the code, i.e. older Kyua binary simply stops a Kyuafile processing and errors about "unknown property". Conversely, if Kyuafile's
syntax
is set to3
then Kyua errors about the whole file even if only a single test needs newer metadata likeexecenv
, and other tests in the suite are still fine and could be run by the previous version of Kyua. It's kind of nothing to pick among these scenarios, and probably additional logic should be implemented. For instance, the first thing that comes to my mind is to skip/fail a test with unknown metadata to keep other tests of the same suite still working. But to make it work like this we should follow the design which means that the syntax is not changed and its version still is2
.I guess we could discuss and conclude here on the desired direction for the project but implement it as a separate PR if it requires extra changes. What do you think?