-
-
Notifications
You must be signed in to change notification settings - Fork 14.8k
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
Build failure: neomutt #232074
Comments
Broken on Darwin x86-64 as well. |
neomutt | MacPorts seems to work — I can't tell whether they are running the tests, though, or not. Here are the failing tests. Test test_editor_backspace... [ FAILED ]
Case Common setup:
editor_backspace.c:86: Check editor_buffer_get_lastchar(es) == 2... failed
editor_backspace.c:87: Check editor_buffer_get_cursor(es) == 2... failed
Test test_editor_backward_char... [ FAILED ]
Case Common setup:
editor_backward_char.c:87: Check editor_buffer_get_cursor(es) == 2... failed
Test test_editor_delete_char... [ FAILED ]
Case Common setup:
editor_delete_char.c:88: Check editor_buffer_get_lastchar(es) == 2... failed
Test test_editor_forward_char... [ FAILED ]
Case Common setup:
editor_forward_char.c:88: Check editor_buffer_get_cursor(es) == 4... failed
Test test_editor_kill_eow... [ FAILED ]
Case Common setup:
editor_kill_eow.c:76: Check editor_buffer_get_lastchar(es) == 13... failed
Test test_editor_kill_word... [ FAILED ]
Case Common setup:
editor_kill_word.c:87: Check editor_buffer_get_lastchar(es) == 12... failed
editor_kill_word.c:88: Check editor_buffer_get_cursor(es) == 6... failed |
Looking at the latest comment on the already closed issue here: #233347 (comment) This issue could use some love. Neomutt is broken on MacOS and it looks like it's the derivation, not upstream. |
I can't install neomutt on MacOS with home-manager too
|
The failing tests were disabled upstream in neomutt/neomutt#3933 . I tried simply upgrading to HEAD with the following patch, and the
|
(@howarddo2208 That's a different bug which you should probably raise separately.) |
Unfortunately, the latest fix didn't work for my Intel Mac, some tests are failing for me. error.log I tested using with import <nixpkgs>
{
overlays = [
(_: prev: {
notmuch = prev.notmuch.override {
withEmacs = false;
};
})
];
};
mkShell {
# name = "";
buildInputs = [
(neomutt.override {
enableLua = true;
})
];
} |
Yes, the failure on |
Steps To Reproduce
Steps to reproduce the behavior:
nix run github:NixOS/nixpkgs/master#neomutt
on darwin aarch64Build log
see https://github.com/NixOS/nixpkgs/runs/13454777089
Additional context
Since #231638 neomutt is broken on darwin-aarch64. See the CI output: https://github.com/NixOS/nixpkgs/runs/13454777089
Tangent: is it normal that a failing CI build wasn't marked as a failed check, but rather just ignored?
Notify maintainers
Metadata
Please run
nix-shell -p nix-info --run "nix-info -m"
and paste the result.The text was updated successfully, but these errors were encountered: