@Martchus the --nocheck did it for me. And sorry for not posting the full error. This is what I was getting... but I still don't see anything specific other than the second check failing due to a timeout.
test 2
Start 2: syncthingctl_run_tests
2: Test command: /tmp/syncthingtray/src/syncthingtray-0.8.1/cli/syncthingctl_tests "-p" "/tmp/syncthingtray/src/syncthingtray-0.8.1/cli/testfiles" "-w" "/tmp/syncthingtray/src/syncthingtray-0.8.1/cli/testworkingdir" "-a" "/tmp/syncthingtray/src/syncthingtray-0.8.1/cli/syncthingctl"
2: Test timeout computed to be: 10000000
2: Directories used to search for testfiles:
2: /tmp/syncthingtray/src/syncthingtray-0.8.1/cli/testfiles/
2: ./testfiles/
2:
2: Directory used to store working copies:
2: /tmp/syncthingtray/src/syncthingtray-0.8.1/cli/testworkingdir/
2:
2: Executing test cases ...
2: .
2: - Setup configuration for Syncthing tests ...
2:
2: - Launching Syncthing ...
2:
2: Waiting till Syncthing GUI becomes available ...- syncthingctl status --api-key syncthingtestinstance --url http://localhost:59251
2: Directories
2: - test2
2: Label Test dir 2
2: Path /tmp/some/path/2/
2: Status paused
2: Global 0 file(s), 0 dir(s), 0 bytes
2: Local 0 file(s), 0 dir(s), 0 bytes
2: Shared with Test dev 2
2: Type Send & Receive
2: Ignore permissions no
2: Auto-normalize yes
2: Rescan interval 365 d
2:
2: - test1
2: Path /tmp/some/path/1/
2: Status idle
2: Global 0 file(s), 0 dir(s), 0 bytes
2: Local 0 file(s), 0 dir(s), 0 bytes
2: Last scan time 2018-06-11 09:16:42
2: Shared with Test dev 2
2: Test dev 1
2: Type Send & Receive
2: Ignore permissions no
2: Auto-normalize yes
2: Rescan interval 2 h
2:
2: Devices
2: - Desktop-Arch
2: ID [removed]
2: Status own device
2: Addresses dynamic
2: Compression metadata
2:
2: - Test dev 1
2: ID [removed]
2: Status disconnected
2: Addresses dynamic
2: Compression metadata
2:
2: - Test dev 2
2: ID [removed]
2: Status paused
2: Addresses tcp://192.168.2.2:22000
2: Compression metadata
2:
2: expected status: Directories
2: - test2
2: Label Test dir 2
2: Path /tmp/some/path/2/
2: Status paused
2: Global 0 file\(s\), 0 dir\(s\), 0 bytes
2: Local 0 file\(s\), 0 dir\(s\), 0 bytes
2: Shared with Test dev 2
2: Type Send & Receive
2: Ignore permissions no
2: Auto-normalize yes
2: Rescan interval 365 d
2:
2: - test1
2: Path /tmp/some/path/1/
2: Status (idle|scanning)
2: Global 0 file\(s\), 0 dir\(s\), 0 bytes
2: Local 0 file\(s\), 0 dir\(s\), 0 bytes
2: Last scan time \d\d\d\d-\d\d-\d\d \d\d:\d\d:\d\d.*
2: Shared with Test dev 2
2: Test dev 1
2: Type Send & Receive
2: Ignore permissions no
2: Auto-normalize yes
2: Rescan interval 2 h
2:
2: Devices
2: - Test dev 1
2: ID [removed]
2: Status disconnected
2: Addresses dynamic
2: Compression metadata
2:
2: - Test dev 2
2: ID [removed]
2: Status paused
2: Addresses tcp://.*22000
2: Compression metadata
2:
2: - .*
2: ID \w\w\w\w\w\w\w-\w\w\w\w\w\w\w-\w\w\w\w\w\w\w-\w\w\w\w\w\w\w-\w\w\w\w\w\w\w-\w\w\w\w\w\w\w-\w\w\w\w\w\w\w-\w\w\w\w\w\w\w
2: Status own device
2: Addresses dynamic
2: Compression metadata
2:
2: F
2: - Waiting for Syncthing to terminate ...
2:
2: - Syncthing terminated with exit code 0.
2:
2: - Syncthing stdout during the testrun:
2: [monitor] 09:16:42 INFO: Signal 15 received; exiting
2:
2:
2:
2: !!!FAILURES!!!
2: Test Results:
2: Run: 1 Failures: 1 Errors: 0
2:
2:
2: 1) test: ApplicationTests::test (F) line: 120 /tmp/syncthingtray/src/syncthingtray-0.8.1/cli/tests/application.cpp
2: forced failure
2: - Actual status does not match expected status.
2:
2:
2/2 Test #2: syncthingctl_run_tests ...........***Failed 2.26 sec
Pinned Comments
Martchus commented on 2016-10-31 11:39
All my packages are managed at GitHub where you can also contribute directly: https://github.com/Martchus/PKGBUILDs There also exist a binary repository: https://martchus.no-ip.biz/repo/arch/ownstuff
Note that the tests of this package might fail despite there's nothing wrong (e. g. because Syncthing is just too slow and the test runs in a timeout). To ignore those false-positives, build the package with
makepkg --nocheckormakechrootpkg -- --nocheck. It makes still sense to report failures. But please include the actual error message and not just the last few lines.