Arch Linux User Repository

If you're having issues with failing tests.. easy workaround is just skipping the tests in general. Just edit your PKGBUILD and comment out line 82: ninja -C build check, or remove it completely with the surrounding IF

Tested on 2 Systems, Build fails with failed unittests:

QWARN : TestEditorLineInfo::discardCompleteAddedContent() This plugin does not support propagateSizeHints()
QWARN : TestEditorLineInfo::discardCompleteAddedContent() This plugin does not support propagateSizeHints()
QWARN : TestEditorLineInfo::discardCompleteAddedContent() This plugin does not support propagateSizeHints()
QWARN : TestEditorLineInfo::discardCompleteAddedContent() QProcess: Destroyed while process ("/tmp/trizen-danny/gittyup/src/build/test/indexer") is still running.
PASS : TestEditorLineInfo::discardCompleteAddedContent()
PASS : TestEditorLineInfo::cleanupTestCase()
Totals: 14 passed, 7 failed, 0 skipped, 0 blacklisted, 9482ms
* Finished testing of TestEditorLineInfo *

  Start 15: CommitAuthorCommitter

15/23 Test #15: CommitAuthorCommitter ............ Passed 0.59 sec
Start 16: rebase
16/23 Test #16: rebase ........................... Passed 4.42 sec
Start 17: TreeView
17/23 Test #17: TreeView ......................... Passed 2.61 sec
Start 18: Submodule
18/23 Test #18: Submodule ........................ Passed 2.45 sec
Start 19: referencelist
19/23 Test #19: referencelist .................... Passed 0.91 sec
Start 20: amend
20/23 Test #20: amend ............................ Passed 0.91 sec
Start 21: SshConfig
21/23 Test #21: SshConfig ........................ Passed 0.16 sec
Start 22: fileContextMenu
22/23 Test #22: fileContextMenu .................. Passed 2.71 sec
Start 23: Setting
23/23 Test #23: Setting .......................... Passed 0.14 sec

96% tests passed, 1 tests failed out of 23

Label Time Summary:
NO_WIN32_OFFSCREEN = 5.11 sec*proc (4 tests)

Total Test time (real) = 40.23 sec

The following tests FAILED:
14 - EditorLineInfos (Failed)
Errors while running CTest
FAILED: test/CMakeFiles/check /tmp/trizen-danny/gittyup/src/build/test/CMakeFiles/check
cd /tmp/trizen-danny/gittyup/src/build/test && /usr/bin/ctest --force-new-ctest-process --output-on-failure --timeout 300
ninja: build stopped: subcommand failed.
==> FEHLER: Ein Fehler geschah in check().
Breche ab...
:: Unable to build gittyup - makepkg exited with code: 4
=>> Try again? [y/N]:

@teras: As I've mentioned in the comments before, try my PKGBUILD.

I have the same problem with @denzil

Still two errors.

FAIL!  : TestIndex::stageDirectory() Compared values are not the same
   Actual   (unstagedModel->rowCount()): 2
   Expected (1)                        : 1
   Loc: [/home/teras/.cache/paru/clone/gittyup/src/Gittyup/test/index.cpp(157)]

FAIL!  : TestTreeView::restoreStagedFileAfterCommit() Compared values are not the same
   Actual   (unstagedModel->data(file_txt).toString()): "folder/subfolder/file.txt"
   Expected (QString("file.txt"))                     : "file.txt"
   Loc: [/home/teras/.cache/paru/clone/gittyup/src/Gittyup/test/TreeView.cpp(59)]

The funny thing is, I installed it two days ago for the first time (version 1.2.0). Now it updates to 1.2.1 and the error appears. Could it be, that what it "finds' is the older build version?

I actually tried uninstalling and reinstalling , even removing the cache, but the only result was not to have gittyup any more installed on my system :(

For me it's building normally.

TIP: If you want to get rid of the "recent files" that comes with the installation open the file nano ~/.config/gittyup.github.com/Gittyup.conf and delete what is in "recent"...

[General]
recent=
[...]

.

I still have to use yochananmarqos's PKGBUILD file to have a successfull build, without the 2 test errors.

@alerque I got the same error, in fact I have 2 tests failed. You can see entire output here https://pastebin.com/fh29e9rV I checked, I don't have git-lfs package installed.

@SoftExpert That does not sound right at all. This does not require git-lfs to build, and indeed I've been building it in chroots without it installed. I only have it marked as an optional dependency. I doubt your system is missing anything because makepkg would warn you about not having any of the necessary dependencies, what I suspect is happening is you have something more than specified here that was causing an incorrectly configured build. It would be nice to know what that is but I don't see any clues yet (again partly because your log doesn't show the actual error).

@alerque: I was missing git-lfs package; once I installed it, the package built correctly. Thank you !

@SoftExpert My tests building this in a clean chroot build environment pass the checks. Are you building on a host system with possibly other packages installed that it finds instead of the vendored submodules? Try building in a chroot with only the declared dependencies.

Your output doesn't show the part of the tests that actually failed, so I can't suggest much.

Also you can install the prebuilt package from my Arch user repository.