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
[Arch] Broken installation (FAIL: test_local_snapshot_is_successful) #1421
Comments
Dear matypist, Can you please specify the installation source. There are different Arch/AUR packages of git available. |
Regex does look for
The real output was:
Seems to be something with display manager. This is @aryoda 's area of topic. My this wayland issue be relevant? Can you tell us more about your setup, display manager, etc? |
|
|
UPDATE: fixed itself after a pacman update of all installed packages, completed the installation successfully |
Still fails for me. Can you assist me in finding the cause please? build output
|
I can see an unexpected WARNING in the unit test:
I will try to find out the reason and the solution... This unit test failure is not critical but to improve our diagnostics it would be helpful to install BiT anyhow by disabling the PKGBUILD check (or @buhtz I think we should try to filter out such Qt5 warnings from the CLI unit tests. They are caused by the Qt5-based systray icon plugin I guess (the CLI should not have any dependency on Qt5 - I am currently fixing this in my upcoming systray icon fix - as soon as I find the time to finish this ;-) |
@topas-rec Could you please provide me with the output of
Edit: I guess to install successfully you could set this env var first: |
Thanks for your help. Sure.
|
I tried the install with
I just looked at the error closer and realized there are two errors. One is This should be solvable by installing qt5-wayland package (from here). Did that and it shortend the error message to this:
It seems the arch repo has to add qt5-wayland to the dependencies, right? |
So do I understand it right: Even after installing
Yes, I'd say so, even though I think there may be discussions then that wayland dependencies are only required when wayland is really used as display manager - not only X11 and not when installing only BiT CLI (since this could lead to a full desktop environment installation on a headless system just because of this dependency). I think this is a thing the package maintainer has to decide). (Hopefully) all dependencies are documented here (and qt5wayland is mentioned there already): https://github.com/bit-team/backintime/blob/dev/CONTRIBUTING.md#build--install Shall I contact the package maintainer by dropping a comment here or do you want to take over the lead? |
I'm not into all wayland/x11 details. If you still think it might be an acceptable solution than I would filter that messages out. But I'm not sure which messages are the problem here. |
OK, I am trying to diagnose and solve this.
No need for you to do anything. I am still not sure (without the warning we couldn't have found the missing dependency). I am still analyzing the issue but the systray icon plugin is my main suspect ATM (if an old installation of BiT exists) - and this a problem of test isolation (unit tests should not trigger installed plugins which may interfere then)... |
I added a comment.
The test still fails, but I think it is because of Installing qt5-wayland just removed this part of the message:
The following full message remains:
Since the tests fail I think filtering out these messages is not enough. Something is going wrong. |
@topas-rec I have created a new issue for the remaining part of of the failing unit test since this issue is already closed (and to avoid mixing similar symptoms with different reasons in one single issue): #1429 |
OS: Arch Linux x86_64
Kernel: 6.1.22-1-lts
DE: Plasma 5.27.4
CPU: AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx (8) @ 2.100GHz
Python: 3.10.10
Tried installing through Octopi / yay but got the following error:
The text was updated successfully, but these errors were encountered: