-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Dockerfile: use bats-core #2336
Conversation
CI failure is unrelated (it's a flaky C/R test which is actually fixed by #2332) |
rebased to re-kick ci |
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.
LGTM, thanks!
OK, CI failures caused by github being (partially) down. Restarted. |
OK we're again hitting a test case bug fixed by #2332 :( |
The bats testing framework we use for integration test is not maintained since 2015 and was superceded by bats-core [1]. More to say, we were using an unreleased version and relying on some features of it (unfortunately I don't remember now what are those features exactly). As Debian still packages very old version of bats from the old repo, so let's Use recent bats-core from the new, supposedly better maintained, github repo. [1] sstephenson/bats#269 Signed-off-by: Kir Kolyshkin <[email protected]>
rebased to fix ci |
@cyphar @AkihiroSuda ptal |
this is a replacement for #2307, see some initial discussion in there
The bats testing framework we use for integration test is not maintained
since 2015 and was superceded by bats-core [1]. More to say, we were
using an unreleased version and relying on some features of it
(unfortunately I don't remember now what are those features exactly).
As Debian still packages very old version of bats from the old repo,
so let's Use recent bats-core from the new, supposedly better maintained,
github repo.
[1] sstephenson/bats#269