diff options
author | dundargoc <33953936+dundargoc@users.noreply.github.com> | 2022-11-04 13:26:12 +0100 |
---|---|---|
committer | GitHub <noreply@github.com> | 2022-11-04 13:26:12 +0100 |
commit | 0aba1761714661b8576d4676c61c319e76bfac1b (patch) | |
tree | a948bd938c40f606f5c125e09e4c37aa847aa95e /test/functional/vimscript/eval_spec.lua | |
parent | dce3fc3e9a455426a45db072f28604b1bc63680a (diff) | |
download | rneovim-0aba1761714661b8576d4676c61c319e76bfac1b.tar.gz rneovim-0aba1761714661b8576d4676c61c319e76bfac1b.tar.bz2 rneovim-0aba1761714661b8576d4676c61c319e76bfac1b.zip |
ci: skip tests if build fails (#20908)
It's currently difficult to pinpoint the cause of a failure since all
tests are run even if the build steps fail. But since the build failed
the test will almost always fail as well as it's dependent on a
successful build, leading to many steps being marked as a failure even
though the real problem was the build step. Even worse, the default
behavior of GitHub Actions is to only automatically show the last failed
step, which is misleading if the build process fails since it'll show
the logs of the failing test step.
An easy solution would be to abort all subsequent steps if any steps
fail. This isn't optimal however, as we want all lint and test failures
to show on a single run instead of prematurely aborting on a single test
step.
We can solve both problems by dividing each job into two phases: the
build/installation phase and the test/lint phase, with a checkmark step
in between. The strategy is simple: if any step before the checkmark
step fails (the build phase), then abort all following steps. If any
step after the checkmark fails (the test phase), then show that test as
failed but continue running all tests.
Diffstat (limited to 'test/functional/vimscript/eval_spec.lua')
0 files changed, 0 insertions, 0 deletions