vimPlugins: update on 2024-09-11#341146
Conversation
fb40f73 to
a8e1e52
Compare
|
Result of 6 packages marked as broken and skipped:
1 package failed to build:
443 packages built:
|
PerchunPak
left a comment
There was a problem hiding this comment.
Nice, I just was going to create an update. Could you please implement what I wrote in #337299?
|
Thank you for rolling this update. |
|
Better to just manually revert its update. I don't think luaPackages update is too far away |
Yes, this is what I meant but poorly phrased. |
Didn't realize that's why it was held back, sure I'll undo that bump. |
|
Result of 6 packages marked as broken and skipped:
444 packages built:
|
|
Result of 6 packages marked as broken and skipped:
1 package failed to build:
442 packages built:
|
I'm seeing similar issue with neotest on aar64-darwin, i think with tests. Running the nixpkgs-review again one more time just to validate it's not transient errors. |
|
Nevermind, it was sqlite errors. Result of 6 packages marked as broken and skipped:
5 packages failed to build:
439 packages built:
Hash mismatch on treesitter sql grammar on darwin somehow... |
|
Result of 6 packages marked as broken and skipped:
4 packages failed to build:
439 packages built:
|
|
Result of 6 packages marked as broken and skipped:
443 packages built:
|
|
Could you post logs for |
|
Found why tests in neotest fail nixpkgs/pkgs/development/lua-modules/overrides.nix Lines 547 to 549 in e6b04a8 Edit: neotest fails on aarch64-linux, not darwin... |
Want me to gate it on aarch64, too? |
|
Not sure yet, will dig deeper and then make a decision |
|
Extremely strange, this patch fixes it for me diff --git a/pkgs/development/lua-modules/overrides.nix b/pkgs/development/lua-modules/overrides.nix
index 358560cfc771..a22d590ebb5e 100644
--- a/pkgs/development/lua-modules/overrides.nix
+++ b/pkgs/development/lua-modules/overrides.nix
@@ -560,7 +560,7 @@ in
export LUA_PATH="./lua/?.lua;./lua/?/init.lua;$LUA_PATH"
nvim --headless -i NONE \
--cmd "set rtp+=${vimPlugins.plenary-nvim}" \
- -c "PlenaryBustedDirectory tests/ {}"
+ -c "PlenaryBustedDirectory tests/ {sequential = true}"
runHook postCheck
'';Could you try it on darwin (don't forget to comment out |
Yep, builds fine on darwin (built on aarch64 and x86). So probably a classic case of not fully isolated test cases. Did you wanna add that commit so you get credit for the fix? Might actually resolve the sqlite issue I had locally, too... |
|
So the sqlite change fixed the one package. But, the others still fail during the tests. Result of 6 packages marked as broken and skipped:
3 packages failed to build:
440 packages built:
|
PerchunPak
left a comment
There was a problem hiding this comment.
LGTM!
Will post x86_64-linux and aarch64-linux nixpkgs-review runs soon
|
Looks like plenary.nvim has some regressions. Anyway, I will look at it more closely tomorrow and will try to report to upstream. For now, just revert the update for plenary.nvim. Also, @teto, is there any particular reason why plenary.nvim is not used from |
In the update script, there was a bug where some deprecations in `deprecated.json` were not deleted from the index file. And everything the script did was updating deprecation dates. This commit properly updates deprecated plugins and modifies dates to actual ones.
|
Result of 6 packages marked as broken and skipped:
425 packages built:
|
|
Result of 6 packages marked as broken and skipped:
4 packages failed to build:
421 packages built:
|
|
|
|
Thanks, that makes me feel better... |
|
Thanks for handling this @khaneliman ! |
You mean, build multiple versions in parallel? Shouldn't nix sandbox fix this? It doesn't fail on master https://hydra.nixos.org/jobset/nixpkgs/trunk#tabs-jobs |
Yes, building them sequentially works fine.
It should. The darwin sandbox does not always behave the same as the linux one. I was able to build |

Description of changes
Things done
nix.conf? (See Nix manual)sandbox = relaxedsandbox = truenix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/)Add a 👍 reaction to pull requests you find important.