-
Notifications
You must be signed in to change notification settings - Fork 44
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 with AUR package 1.3.0-1 #161
Comments
Note: This build error is as of right now reproducible. It happened 5 out of 5 times in a row. |
Strange, in my env I could not reproduce it at all so far. So far I could only fix the layout-related warnings. |
I have the following
|
I assume the first issue I have no idea about the second failing test. |
Oh joy! A partially different build error! By the way, I have used |
I confirm the issue after building everything using
|
I'm actually trying to assign a random port for the test instance of Syncthing to avoid running in conflicts with an already running one. This is done by starting Syncthing with
So Syncthing seems to write the different port even to its config file in your case. My test is only expecting the default port because I observed in my environment that Syncthing still writes the default port to the config file (despite the |
I believe this should be about equivalent to what aurutils does in chroot mode. It uses devtools under the hood with some extra dependency handling fixes on top. |
This warning might indicate that overriding
|
And this warning looks like we're hitting an internal problem of Qt (which I'm also not getting):
|
Now that I have built and upgraded using
So it seems the HOME/XDG thing might be a red herring for this particular problem. I'm building with distcc, but that shouldn't have any effect. I just verified that |
Note: |
Yes, looks like the HOME/XDG thing isn't relevant. Just for reference, a good run looks like this (on the latest commit fixing the layout issues):
So the |
I can now reproduce the exact problem by starting |
This might not be relevant (if the port thing you just posted caused both problems), but I had already written it when that post popped up: I have verified that I can reproduce the issues on two computers, a Thinkpad T480 with Intel Core i7-8550U and a desktop with AMD Ryzen 5600X. Turning off distcc didn't make a difference (only tested on the Ryzen desktop). Mind you, I use centralised configuration management, so the computers are very similarly configured. One thing worth trying might be running the unit test under valgrind or one of the various sanitisers that modern GCC/clang has? EDIT: Also @Keloran had a different error than me and @iyanmv did. So there is that too. |
Syncthing is behaving strange. When its default port is already used (e.g.
then the resulting config file contains the random port If I invoke the very same command but Syncthing's default port is not blocked I get So I believe we found a Syncthing bug here. You're nevertheless right that the error messages from you differ slightly and the warning from |
I've been adding a workaround. Can you test whether the latest commits I've pushed work for you? Before testing anything I'd recommend to stop any leftover Syncthing processes from previous test runs (but having your regular Syncthing running on 8384 should be fine). |
If it helps I get the same failed test, here my log of it.
It seems the fails are consistent, the one you already indentified related to the port and then the other one And here some info:
Let me know if you need more info, |
@th3bucch Looks like you haven't tried with the latest commit on Git. It would help to know whether that is working. |
I tried to build it using your -git PKGBUILD from your PKGBUILD repo, but it seems to need the -git version specifically of c++utilities etc too. I don't have time to mess around with all of that right now, but if you can point me to a PKGBUILD that will work with the current release versions of the dependencies I'll happily test that. |
The -git PKGBUILDs shouldn't take long to build and are co-installable with everything else. However, I'd just recommend to build it manually following the steps in the README. |
I ended up editing the -git PKGBUILD removing all the cmake parameters about git suffixes and removing -git from the .so dependencies. That builds correctly with makepkg and aur build (resulting in version 1434.860cf28-1). |
Ok, I'll patch the PKGBUILDs then. |
With the latest version, everything works for me. For my part, feel free to close the issue, or keep it open for tracking the different error that @Keloran was getting. |
I'm closing the issue because he's been creating another one anyways. |
Relevant components
The unit test fails when building the package from AUR. I'm not sure which component that corresponds to.
syncthingctl
)libsyncthing
)Environment and versions
syncthingtray
,qtutilities
andc++utilities
: 1.3.0-1, 6.10.0-1, 5.20.0-1Bug description
Unit test failure when building the latest AUR package. Only syncthingwidgets_run_wizard_tests fails:
Steps to reproduce
Note I have not tested if it breaks outside a chroot as well due to above mentioned pain with exact version dependencies.
Expected behavior
Build should succeed.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: