Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 843431 - dev-vcs/mercurial-5.8.1 fails tests on stable ppc
Summary: dev-vcs/mercurial-5.8.1 fails tests on stable ppc
Status: CONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal with 1 vote (vote)
Assignee: Cédric Krier
URL: https://bz.mercurial-scm.org/show_bug...
Whiteboard:
Keywords:
Depends on:
Blocks: 811543 918865
  Show dependency tree
 
Reported: 2022-05-09 13:50 UTC by Agostino Sarubbo
Modified: 2024-02-20 08:16 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
build.log (build.log,352.03 KB, text/plain)
2022-05-09 13:50 UTC, Agostino Sarubbo
Details
build.log (ppc, 6.4.4) (mercurial-6.4.4:20230803-224400.log,592.29 KB, text/plain)
2023-08-04 10:40 UTC, ernsteiswuerfel
Details
build.log (ppc, 6.5) (mercurial-6.5:20230804-104209.log,608.61 KB, text/plain)
2023-08-05 11:35 UTC, ernsteiswuerfel
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Agostino Sarubbo gentoo-dev 2022-05-09 13:50:07 UTC
https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/

Issue: dev-vcs/mercurial-5.8.1 fails tests on stable ppc.
Discovered on: ppc (internal ref: ppc_at)
Comment 1 Agostino Sarubbo gentoo-dev 2022-05-09 13:50:08 UTC
Created attachment 777779 [details]
build.log

build log and emerge --info
Comment 2 ernsteiswuerfel archtester 2023-08-04 10:40:42 UTC
Created attachment 867013 [details]
build.log (ppc, 6.4.4)

More test failures compared to 5.8.1 but no regression (less tests in 5.8.1).

[...]
Failed test-debugcommands.t: output changed
Failed test-dirstate-read-race.t#dirstate-v1#pre-all-read: output changed
Failed test-dirstate-read-race.t#dirstate-v1#pre-some-read: output changed
Failed test-dirstate-read-race.t#dirstate-v2-append#pre-all-read: output changed
Failed test-dirstate-read-race.t#dirstate-v2-append#pre-some-read: output changed
Failed test-dirstate-read-race.t#dirstate-v2-rewrite#pre-all-read: output changed
Failed test-dirstate-read-race.t#dirstate-v2-rewrite#pre-some-read: output changed
Failed test-dirstate-status-write-race.t#dirstate-v1: output changed
Failed test-dirstate-status-write-race.t#dirstate-v2-append: output changed
Failed test-dirstate-status-write-race.t#dirstate-v2-rewrite: output changed
Failed test-remotefilelog-gc.t: output changed
# Ran 925 tests, 49 skipped, 11 failed.
python hash seed: 3320138338
 * ERROR: dev-vcs/mercurial-6.4.4::gentoo failed (test phase):
 *   Tests fail with python3.11
Comment 3 ernsteiswuerfel archtester 2023-08-05 11:35:36 UTC
Created attachment 867143 [details]
build.log (ppc, 6.5)

Failed test-clone-stream.t#stream-bundle2-v3: output changed
Failed test-debugcommands.t: output changed
Failed test-dirstate-read-race.t#dirstate-v1#pre-all-read: output changed
Failed test-dirstate-read-race.t#dirstate-v1#pre-some-read: output changed
Failed test-dirstate-read-race.t#dirstate-v2-append#pre-all-read: output changed
Failed test-dirstate-read-race.t#dirstate-v2-append#pre-some-read: output changed
Failed test-dirstate-read-race.t#dirstate-v2-rewrite#pre-all-read: output changed
Failed test-dirstate-read-race.t#dirstate-v2-rewrite#pre-some-read: output changed
Failed test-dirstate-status-write-race.t#dirstate-v1: output changed
Failed test-dirstate-status-write-race.t#dirstate-v2-append: output changed
Failed test-dirstate-status-write-race.t#dirstate-v2-rewrite: output changed
Failed test-lock-badness.t: output changed
# Ran 934 tests, 50 skipped, 12 failed.
python hash seed: 2313753079
 * ERROR: dev-vcs/mercurial-6.5::gentoo failed (test phase):
 *   Tests fail with python3.11
Comment 4 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2024-02-20 05:34:47 UTC
Those look like timeouts to me...
Comment 5 Sam James archtester Gentoo Infrastructure gentoo-dev Security 2024-02-20 05:36:56 UTC
(In reply to Sam James from comment #4)
> Those look like timeouts to me...

Looks like we could try setting HGTEST_TIMEOUT?
Comment 6 Cédric Krier gentoo-dev 2024-02-20 08:16:15 UTC
(In reply to Sam James from comment #5)
> (In reply to Sam James from comment #4)
> > Those look like timeouts to me...
> 
> Looks like we could try setting HGTEST_TIMEOUT?

OK but to which value? I guess it depends on the speed of the testing machine.