| Commit message (Collapse) | Author | Age |
| ... | |
| |
|
|
| |
This will make it possible to see what needs to be fixed without having
uncrustify installed locally.
|
| | |
|
| |
|
|
|
|
|
| |
This lint job will ensure that the C codebase is properly formatted at
all times. This helps eliminate most of clint.py.
To save CI time, it's faster to manually compile uncrustify and cache
the binary instead of using homebrew (the apt-get package is too old).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Unnecessary CI builds increase the change of spurious failures, which are costly
noise. Of course, we should fix all legitimate bugs, but we also cannot
micro-manage every platform, so there needs to be a clear motivation for the CI
builds that we maintain.
Reasons against maintaining a mingw CI job:
1. The windows mingw build is slow.
2. Failures:
- https://github.com/neovim/neovim/issues/18494
- https://github.com/neovim/neovim/issues/18495
3. The mingw artifact is 10x bigger than the windows MSVC artifact:
https://github.com/neovim/neovim/issues/10560
4. Our releases publish the MSVC (not mingw) artifact for Windows users:
https://github.com/neovim/neovim/releases
5. Non-MSVCRT has limitations documented by libuv: http://docs.libuv.org/en/v1.x/process.html
> On Windows file descriptors greater than 2 are available to the child process only if the child processes uses the MSVCRT runtime.
Closes https://github.com/neovim/neovim/issues/18551
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
previous: https://github.com/neovim/neovim/pull/14123
CI tests were disabled on drafts #18566 to manage the
large number of incoming jobs. While this did help, it had the drawback
of making the purpose of the ready-for-review a bit fuzzier. It went
from a clear "my PR is ready" signal to maintainers to somewhere between
"my PR is ready but I need the tests to confirm" to "please don't merge
yet, I just need to see the test results". Worse is that the specific
case of wanting to see the test results but not wanting it merged is
that this needs to be actively conveyed to the maintainers with a [DNM]
or a comment to not merge the PR yet. All of this causes weird
workarounds and noises which I believe isn't necessary.
The reason why I don't think this workaround is needed anymore is that
our CI now aborts a job if a new job from the same pull requests is
created, which makes the "10 simultaneous jobs per PR" situations that
triggered this not possible.
|
| |
|
|
| |
gperf was removed in 36613b888bae7df764a26a28ca1627a2c0c2edeb
yay!
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Also remove perl from brew install to prevent a warning that states it's
already installed.
|
| | |
|
| | |
|
| | |
|
| |\
| |
| | |
ci: remove failing windows CI tests
|
| | |
| |
| |
| |
| |
| |
| |
| | |
The VS 2019 CMake generator no longer has different generator types for
different architectures. Now, the architecture is specified via CMake's
`-A` switch. However, this requires we also propagate
`${CMAKE_GENERATOR_PLATFORM}` to the bundled deps, so they build for the
same architecture as Nvim.
|
| | | |
|
| |\ \
| | |
| | | |
Use system dependencies for lint CI
|
| | | |
| | |
| | |
| | |
| | |
| | | |
“make clint-full” bypasses the normal mechanisms used to communicate
build flags in the CI jobs, so explicitly build nvim before running the
lint jobs.
|
| | |/ |
|
| |/ |
|
| |\
| |
| | |
ci: run each test suite in a separate github step
|
| | |
| |
| |
| |
| | |
This should help combat some of the lagginess when looking at the CI
logs in the browser.
|
| |/ |
|
| | |
|
| |
|
|
| |
This reverts commit a91a5c1880dcb7718aed4e19ff2757be0948e7d5.
|
| |
|
|
|
|
|
| |
Co-authored-by: Sean Dewar <seandewar@users.noreply.github.com>
Co-authored-by: Gregory Anders <greg@gpanders.com>
Co-authored-by: Sebastian Volland <seb@baunz.net>
Co-authored-by: Lewis Russell <lewis6991@gmail.com>
Co-authored-by: zeertzjq <zeertzjq@outlook.com>
|
| | |
|
| | |
|
| |\
| |
| | |
ci: run lint only on master branch
|
| | |
| |
| |
| |
| | |
The list of known lint issues is only updated for the master branch, so
other branches report lots of false positive issues.
|
| |\ \
| |/
|/| |
ci: bump clang version to 13 in asan and tsan
|
| | | |
|
| |/ |
|
| |
|
|
| |
[skip ci]
|
| |
|
|
|
|
| |
Packages are automatically upgraded on install. This will avoid
upgrading unrelated packages, cutting the macos job time to about a
half.
|
| | |
|
| |
|
|
|
|
|
|
| |
Now that we have various GH actions creating branches in the main repo,
using the generic '**' pattern for the CI workflow is just wasting CI
time and leading to more queued jobs.
[skip ci]
|
| | |
|
| |
|
|
|
|
| |
* build(cmake): update cmake min version to 3.10
* ci: test cmake minimum required version
* build(cmake): remove some legacy includes
* Since version 3.5 cmake_parse_arguments is implemented natively.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
By default, the pull_request target only runs for the "opened",
"synchronize", and "reopened" events.
Since we've disabled GHA CI for "draft" PRs, the "ready_for_review"
event also needs to be included so CI is automatically run when leaving
draft status.
|
| | |
|
| |
|
|
|
|
|
| |
(#15115)" (#15141)
This reverts commit 5377b2b00aea1a0bde1b81452e6198dabe5b9796.
(Fix no longer needed.)
|
| |
|
|
|
|
|
|
|
| |
macOS CI was failing because:
- brew upgrade fails because,
- mongodb-community cant upgrade because,
- some symlinks are owned by ... mongodb-community...
We don't use mogodb, so we can just remove it wholesale.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|