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
terminator: 1.92 -> 2.1.0 #100472
terminator: 1.92 -> 2.1.0 #100472
Conversation
I don't have time to investigate this now, sorry. (Did you try reproducing under nix-shell?) |
I did try under nix-shell, yes, but I ran into a bunch of different errors - presumably related to not applying For clarity: I've been using the actual executable as a terminal and that is working fine so far, it's purely a test issue. I will take another look later, but any input from other reviewers is welcome. |
Managed to get the same error inside a nix-shell, using a standalone clone of the upstream repo at v2.0.1:
Not sure where to go from here though... |
dc9ba88
to
f8020eb
Compare
11f4c8c
to
694c576
Compare
694c576
to
c5089cd
Compare
c5089cd
to
397a02d
Compare
397a02d
to
b315205
Compare
b315205
to
52ff7a7
Compare
52ff7a7
to
a0e2df2
Compare
@SuperSandro2000 I've been unable to find a way to get the tests to work, but I've been using the actual application as a daily driver since I opened the PR, so can this be merged or can someone take a look at what's wrong with the tests? |
Motivation for this change
A new version has been released.
Marked as a WIP for now because the tests are causing issues for me with a rather unhelpful error:
@bjornfor Could you maybe help out with this? The old
run_tests
file has been removed, and as far as I can see plain pytest should be the new way to run tests. It even dumps core if I runpytest --collect-only
.Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)