| Age | Commit message (Collapse) | Author | Files |
|---|
|
|
|
Specifically, functions that are run in the context of the test runner
are put in module `test/testutil.lua` while the functions that are run
in the context of the test session are put in
`test/functional/testnvim.lua`.
Closes https://github.com/neovim/neovim/issues/27004.
|
|
|
|
Work on https://github.com/neovim/neovim/issues/27004.
|
|
|
|
|
|
The removes the previous restriction that nvim_buf_set_extmark()
could not be used to highlight arbitrary multi-line regions
The problem can be summarized as follows: let's assume an extmark with a
hl_group is placed covering the region (5,0) to (50,0) Now, consider
what happens if nvim needs to redraw a window covering the lines 20-30.
It needs to be able to ask the marktree what extmarks cover this region,
even if they don't begin or end here.
Therefore the marktree needs to be augmented with the information covers
a point, not just what marks begin or end there. To do this, we augment
each node with a field "intersect" which is a set the ids of the
marks which overlap this node, but only if it is not part of the set of
any parent. This ensures the number of nodes that need to be explicitly
marked grows only logarithmically with the total number of explicitly
nodes (and thus the number of of overlapping marks).
Thus we can quickly iterate all marks which overlaps any query position
by looking up what leaf node contains that position. Then we only need
to consider all "start" marks within that leaf node, and the "intersect"
set of that node and all its parents.
Now, and the major source of complexity is that the tree restructuring
operations (to ensure that each node has T-1 <= size <= 2*T-1) also need
to update these sets. If a full inner node is split in two, one of the
new parents might start to completely overlap some ranges and its ids
will need to be moved from its children's sets to its own set.
Similarly, if two undersized nodes gets joined into one, it might no
longer completely overlap some ranges, and now the children which do
needs to have the have the ids in its set instead. And then there are
the pivots! Yes the pivot operations when a child gets moved from one
parent to another.
|
|
Follow-up to #24195.
|
|
Co-authored-by: Gustavo Sampaio <gbritosampaio@gmail.com>
Co-authored-by: C.D. MacEachern <craig.daniel.maceachern@gmail.com>
Co-authored-by: Sean Dewar <seandewar@users.noreply.github.com>
Co-authored-by: Tomas Nemec <nemi@skaut.cz>
|
|
Extend the capabilities of is_os to detect more platforms such as
freebsd and openbsd. Also remove `iswin()` helper function as it can be
replaced by `is_os("win")`.
|
|
helpers.source() was a hack to work around the lack of anonymous
:source. Its "create tempfile" behavior is not a required part of most
tests that use it.
Some tests still need the old "create tempfile" behavior either because
they test SID behavior, or because of missing nvim_exec features: #16071
|
|
|
|
Memory compression could complicate the measurements.
|
|
Problem: The wininfo list may contain stale entries.
Solution: When closing a window remove any other entry where the window
pointer is NULL.
https://github.com/vim/vim/commit/4882d983397057ea91c584c5a54aaccf15016d18
|
|
Problem: Memory usage test often fails on FreeBSD.
Solution: Increase multiplier for upper limit.
https://github.com/vim/vim/commit/6bce5856b5fc4d4eb8f75298382251ecda659ac3
|
|
This test can fail on any of the Windows builds
because Github Actions does not provide enough stability
and enough memory for all runners..
Check test requirements before running any test cases
to avoid duplicate checks.
|
|
The commit summary maybe does not make sense, but calling a function
that does not wait on anything `wait()` makes even less sense.
|
|
Problem: Memory test still fails on Cirrus CI.
Solution: Allow for a tiny bit more tolerance in the upper limit.
https://github.com/vim/vim/commit/bb062c1588c324a1ce4cf01fd5e0780e83aaabe4
Check memory usage after Neovim sourced the Vimscript files.
https://github.com/neovim/neovim/pull/12679
N/A patches for version.c:
vim-patch:8.2.0062: memory test is flaky on FreeBSD
Problem: Memory test is flaky on FreeBSD.
Solution: Add a short sleep before getting the first size.
https://github.com/vim/vim/commit/e7538ae997b3983d0c91a886a74ebacedd752164
vim-patch:8.2.0071: memory test often fails on Cirrus CI
Problem: Memory test often fails on Cirrus CI.
Solution: Allow for more tolerance in the upper limit. Remove sleep.
https://github.com/vim/vim/commit/1832d12aea30f1533f3c461d9e1530d10f66b162
|
|
Problem: Memory usage test is a bit too flaky.
Solution: Adjust the tolerances a bit. (Christian Brabandt)
https://github.com/vim/vim/commit/5d508dd39e810d446f29dfd4f4e745b802875001
|
|
Problem: Memory usage test may still fail on some systems.
Solution: Use 98% of the lower limit. (Christian Brabandt)
https://github.com/vim/vim/commit/3a731ee0c2dd34792c1b21fc4c699a84129f1b86
|
|
Problem: Memory usage test may still fail on some systems.
Solution: Increase tolerance from 3% to 20%.
https://github.com/vim/vim/commit/6b6f7aae4a3329d685e512699287605540257b40
|
|
Problem: Memory usage test may still fail on some systems. (Elimar
Riesebieter)
Solution: Increase tolerance from 1% to 3%.
https://github.com/vim/vim/commit/ba64ba093520e85d6bed2595960edb693bdb4c51
|
|
Problem: Memory usage test may still fail.
Solution: Drop the unused min value. (Christian Brabandt)
https://github.com/vim/vim/commit/f7e47af7760fe054cb645dac9a1e96b23c85804d
|
|
Problem: Memory usage test sometimes fails.
Solution: Use 80% of before.last as the lower limit. (Christian Brabandt)
https://github.com/vim/vim/commit/08cda65ddfbb4bce8cef43726a0c00817fc47327
|
|
Problem: Using closure may consume a lot of memory.
Solution: unreference items that are no longer needed. Add a test. (Ozaki
Kiichi, closes vim/vim#3961)
https://github.com/vim/vim/commit/209b8e3e3bf7a4a3d102134124120f6c7f57d560
|
