854405 – app-accessibility/espeak-ng-1.51 fails tests

Bug 854405 - app-accessibility/espeak-ng-1.51 fails tests

Summary: app-accessibility/espeak-ng-1.51 fails tests

Status:	UNCONFIRMED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	All Linux

Importance:	Normal normal with 1 vote (vote)
Assignee:	William Hubbs

URL:
Whiteboard:
Keywords:	TESTFAILURE

Depends on:
Blocks:

Reported:	2022-06-26 16:38 UTC by Jonathan Lovelace
Modified:	2024-04-11 01:28 UTC (History)
CC List:	2 users (show)

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

Attachments
app-accessibility:espeak-ng-1.51:20220625-185909.log (app-accessibility:espeak-ng-1.51:20220625-185909.log,216.89 KB, text/x-log) 2022-06-26 16:38 UTC, Jonathan Lovelace	Details
emerge-info.txt (emerge-info.txt,8.40 KB, text/plain) 2022-06-26 16:38 UTC, Jonathan Lovelace	Details
build.log (ppc, 1.51) (espeak-ng-1.51:20230801-200610.log,220.71 KB, text/plain) 2023-08-01 20:20 UTC, ernsteiswuerfel	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Jonathan Lovelace 2022-06-26 16:38:16 UTC

Created attachment 787772 [details]
app-accessibility:espeak-ng-1.51:20220625-185909.log

=app-accessibility/espeak-ng-1.51 fails its test phase for me. If I'm reading the build log correctly, and concurrency from MAKEOPTS="-j3" hasn't confused things, it looks like it's in the test tests/dictionary.test, in the specific test case "testing en $u and $u+". Version 1.50-r3 passed its tests when it was last built, earlier this month.

Comment 1 Jonathan Lovelace 2022-06-26 16:38:36 UTC

Created attachment 787775 [details]
emerge-info.txt

Comment 2 ernsteiswuerfel archtester

2023-08-01 20:20:16 UTC

Created attachment 866822 [details]
build.log (ppc, 1.51)

Same on ppc.

Comment 3 Sam James archtester

2024-03-01 06:43:35 UTC

I had a comment written out about how this might be parallelism again, as it hit this package before, but it turns out that must have been another a11y package...

Anyway: there's a lot of test fixes in git but no release, they seem to have been planning one since December. :(