Bug 717108 – =net-p2p/syncthing-1.3.4-r1: test failure on ppc64

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Agostino Sarubbo 2020-04-11 15:56:11 UTC]

This is an auto-filled bug because net-p2p/syncthing fails tests. Attached build log and emerge --info

[Comment 1 Agostino Sarubbo 2020-04-11 15:56:20 UTC]

Created attachment 632266 [details]
build.log.bz2

build log and emerge --info

[Comment 2 Marek Szuba (RETIRED) 2020-04-11 17:09:04 UTC]

Is this only on ppc64 (as per the build log) or on other arches as well? Does it happen every time?

[Comment 3 Agostino Sarubbo 2020-04-11 17:29:01 UTC]

Atm I don't know for the other arches. Yes it happens every time

[Comment 4 Marek Szuba (RETIRED) 2020-04-12 08:47:36 UTC]

I do not see any test failures on my amd64 test system and seeing as you have stabilised this ebuild on amd64 and arm, I assume you haven't observed any either and the problem *is* ppc64-specific. I'll follow this up with upstream.

[Comment 5 Agostino Sarubbo 2020-04-13 09:18:09 UTC]

(In reply to Marek Szuba from comment #4)
> I do not see any test failures on my amd64 test system and seeing as you
> have stabilised this ebuild on amd64 and arm, I assume you haven't observed
> any either and the problem *is* ppc64-specific. I'll follow this up with
> upstream.

That's right..

[Comment 6 Agostino Sarubbo 2020-04-13 09:18:09 UTC]

(In reply to Marek Szuba from comment #4)
> I do not see any test failures on my amd64 test system and seeing as you
> have stabilised this ebuild on amd64 and arm, I assume you haven't observed
> any either and the problem *is* ppc64-specific. I'll follow this up with
> upstream.

That's right..

[Comment 7 Marek Szuba (RETIRED) 2020-04-16 11:33:40 UTC]

Upstream has suggested the issue might lie with the time-out value being too low, could you try again with it increased from 10 to 20 seconds?

[Comment 8 Marek Szuba (RETIRED) 2020-04-16 11:34:26 UTC]

Created attachment 633232 [details, diff]
Changes the time-out value of TestIssue5063

[Comment 9 Larry the Git Cow 2020-04-17 17:58:07 UTC]

The bug has been closed via the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e3a69b9e068c2e919d14f4a848711919fe1ea7ed

commit e3a69b9e068c2e919d14f4a848711919fe1ea7ed
Author:     Marek Szuba <[e-mail]>
AuthorDate: 2020-04-17 17:50:19 +0000
Commit:     Marek Szuba <[e-mail]>
CommitDate: 2020-04-17 17:57:29 +0000

    net-p2p/syncthing: work around ppc64 test failure
    
    For some reason one of the Syncthing tests - TestIssue5063 - times out
    on our ppc64 buildhost, with 100% reproducibility. Upstream were not
    aware of the problem because apparently they have never run the test
    suite on such a system, that said their suggestion to adjust the
    time-out threshold appears to do the trick. Make it 20 s i.e. twice what
    it originally is, hopefully this will prevent the problem from
    resurfacing any time soon.
    
    Closes: https://bugs.gentoo.org/717108
    See-also: https://github.com/syncthing/syncthing/issues/6539
    Signed-off-by: Marek Szuba <[e-mail]>

 .../files/syncthing-1.3.4-TestIssue5063_timeout.patch  | 18 ++++++++++++++++++
 net-p2p/syncthing/syncthing-1.3.4-r1.ebuild            |  4 ++++
 net-p2p/syncthing/syncthing-1.4.2.ebuild               |  4 ++++
 3 files changed, 26 insertions(+)