You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With Gramps 5.2.4, there is a failing unit test. I have confirmed it fails regardless of Python version and all other combinations (Ubuntu versions, etc.) I have tried have not made it work.
The test test_get_reports_report_localized_content generates a textual ancestor report with a non-English locale and checks whether the result is actually in the requested locale. It is not.
Note that all other tests related to localizations pass, it is something specific to reports.
I can't find anything recent, but the translation "Ahnentafel für" was changed to "Ahnentafel Bericht für" about 3 years ago. I can't find the string in the error message.
With Gramps 5.2.4, there is a failing unit test. I have confirmed it fails regardless of Python version and all other combinations (Ubuntu versions, etc.) I have tried have not made it work.
The test
test_get_reports_report_localized_content
generates a textual ancestor report with a non-English locale and checks whether the result is actually in the requested locale. It is not.Note that all other tests related to localizations pass, it is something specific to reports.
Under the hood, the language is set here
https://github.com/gramps-project/gramps-web-api/blob/master/gramps_webapi/api/report.py#L331
essentially by calling the
set_locale
method of the base report class.@Nick-Hall, @cdhorn, do you have any clue why this would suddenly fail?
The text was updated successfully, but these errors were encountered: