1905190 – biber FTBFS in Rawhide (F34): tests fail on different \field{sortinithash} values

Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1905190 - biber FTBFS in Rawhide (F34): tests fail on different \field{sortinithash} values

Summary: biber FTBFS in Rawhide (F34): tests fail on different \field{sortinithash} va...

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	Fedora
Classification:	Fedora
Component:	biber
Sub Component:
Version:	34
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	unspecified
Target Milestone:	---
Assignee:	Petr Pisar
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:
URL:
Whiteboard:
Duplicates (1):	1923441 (view as bug list)
Depends On:
Blocks:	F34FTBFS
TreeView+	depends on / blocked

Reported:	2020-12-07 17:03 UTC by Troy Dawson
Modified:	2021-05-27 01:04 UTC (History)
CC List:	7 users (show)
Fixed In Version:	biber-2.16-1.fc35 biber-2.14-6.fc34 biber-2.14-5.fc33
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2021-05-27 00:31:15 UTC
Type:	Bug
Embargoed:
Dependent Products:

Attachments	(Terms of Use)
biber scratch build log (311.96 KB, text/plain) 2020-12-07 17:03 UTC, Troy Dawson	no flags	Details
View All

Description Troy Dawson 2020-12-07 17:03:48 UTC

Created attachment 1737370 [details]
biber scratch build log

Description of problem:
biber fails to build in F34 Rawhide.

Version-Release number of selected component (if applicable):
biber-2.14-4

How reproducible:
100%

Steps to Reproduce:
1. fedpkg clone biber ; cd biber
2. fedpkg build --scratch


Actual results:
Failed build

Expected results:
Build should build correctly

Additional info:
It is failing because of the tests.  I do not know enough of the tests to give you a guess what the main cause it.  A build log has been attached.

This was discovered by Fedora ELN, but we are reporting it now so it can be fixed in advance of the Fedora F34 mass rebuild.

Comment 1 Petr Pisar 2021-02-01 17:15:28 UTC

From the build.log:

+ ./Build test verbose=1
#   Failed test 'Annotations - 1'
#   at t/annotations.t line 136.
# --- Got
# +++ Expected
# @@ -1,42 +1,42 @@
#  '    \\entry{ann1}{misc}{}
#        \\name{author}{3}{}{%
#          {{hash=89a9e5097e11e595700540379c9b3a6b}{%
#             family={Last1},
#             familyi={L\\bibinitperiod},
#             given={First1},
#             giveni={F\\bibinitperiod}}}%
#          {{hash=7475b6b7b3c24a2ac6bd4d146cdc74dc}{%
#             family={Last2},
#             familyi={L\\bibinitperiod},
#             given={First2},
#             giveni={F\\bibinitperiod}}}%
#          {{hash=fd3dffa06a5d1f89c512841df1ccf4d0}{%
#             family={Last3},
#             familyi={L\\bibinitperiod},
#             given={First3},
#             giveni={F\\bibinitperiod}}}%
#        }
#        \\list{language}{2}{%
#          {english}%
#          {french}%
#        }
#        \\strng{namehash}{90ae96c82de92e36949bc64254bbde0c}
#        \\strng{fullhash}{90ae96c82de92e36949bc64254bbde0c}
#        \\strng{bibnamehash}{90ae96c82de92e36949bc64254bbde0c}
#        \\strng{authorbibnamehash}{90ae96c82de92e36949bc64254bbde0c}
#        \\strng{authornamehash}{90ae96c82de92e36949bc64254bbde0c}
#        \\strng{authorfullhash}{90ae96c82de92e36949bc64254bbde0c}
#        \\field{extraname}{1}
#        \\field{sortinit}{L}
# -      \\field{sortinithash}{7c47d417cecb1f4bd38d1825c427a61a}
# +      \\field{sortinithash}{dad3efd0836470093a7b4a7bb756eb8c}
#        \\field{labelnamesource}{author}
#        \\field{labeltitlesource}{title}
#        \\field{title}{The Title}
#        \\annotation{field}{language}{default}{}{}{0}{ann4}
#        \\annotation{field}{title}{default}{}{}{0}{one, two}
#        \\annotation{item}{author}{default}{2}{}{0}{corresponding}
#        \\annotation{item}{language}{default}{1}{}{0}{ann1}
#        \\annotation{item}{language}{default}{2}{}{0}{ann2, ann3}
#        \\annotation{part}{author}{default}{1}{family}{0}{student}
#      \\endentry
#  '
[...]
Test Summary Report
-------------------
t/annotations.t         (Wstat: 512 Tests: 2 Failed: 2)
  Failed tests:  1-2
  Non-zero exit status: 2
t/basic-misc.t          (Wstat: 3584 Tests: 69 Failed: 14)
  Failed tests:  1, 5, 10, 13, 16-18, 44, 59-62, 68-69
  Non-zero exit status: 14
t/biblatexml.t          (Wstat: 512 Tests: 5 Failed: 2)
  Failed tests:  1, 5
  Non-zero exit status: 2
t/crossrefs.t           (Wstat: 6144 Tests: 37 Failed: 24)
  Failed tests:  1-6, 8-16, 18-19, 21-22, 32-36
  Non-zero exit status: 24
t/datalists.t           (Wstat: 512 Tests: 15 Failed: 2)
  Failed tests:  13-14
  Non-zero exit status: 2
t/dateformats.t         (Wstat: 4352 Tests: 53 Failed: 17)
  Failed tests:  20-22, 24, 26, 28, 31, 33-42
  Non-zero exit status: 17
t/encoding.t            (Wstat: 2304 Tests: 10 Failed: 9)
  Failed tests:  1-8, 10
  Non-zero exit status: 9
t/names.t               (Wstat: 7936 Tests: 73 Failed: 31)
  Failed tests:  35-61, 66-69
  Non-zero exit status: 31
t/options.t             (Wstat: 768 Tests: 9 Failed: 3)
  Failed tests:  7-9
  Non-zero exit status: 3
t/related-entries.t     (Wstat: 1280 Tests: 15 Failed: 5)
  Failed tests:  1-2, 10, 14-15
  Non-zero exit status: 5
t/set-dynamic.t         (Wstat: 1536 Tests: 7 Failed: 6)
  Failed tests:  2-7
  Non-zero exit status: 6
t/set-legacy.t          (Wstat: 256 Tests: 3 Failed: 1)
  Failed test:  1
  Non-zero exit status: 1
t/set-static.t          (Wstat: 1280 Tests: 5 Failed: 5)
  Failed tests:  1-5
  Non-zero exit status: 5
t/skips.t               (Wstat: 2048 Tests: 15 Failed: 8)
  Failed tests:  7, 9-15
  Non-zero exit status: 8
t/skipsg.t              (Wstat: 768 Tests: 3 Failed: 3)
  Failed tests:  1-3
  Non-zero exit status: 3
t/sort-complex.t        (Wstat: 1280 Tests: 9 Failed: 5)
  Failed tests:  2-6
  Non-zero exit status: 5
t/truncation.t          (Wstat: 2560 Tests: 12 Failed: 10)
  Failed tests:  1-10
  Non-zero exit status: 10
t/uniqueness-nameparts.t (Wstat: 3840 Tests: 36 Failed: 15)
  Failed tests:  1-8, 30-36
  Non-zero exit status: 15
t/xdata.t               (Wstat: 1024 Tests: 11 Failed: 4)
  Failed tests:  1-2, 5-6
  Non-zero exit status: 4
Files=52, Tests=1219, 179 wallclock secs ( 0.61 usr  0.20 sys + 168.74 cusr  7.77 csys = 177.32 CPU)

Comment 2 Petr Pisar 2021-02-01 17:15:54 UTC

*** Bug 1923441 has been marked as a duplicate of this bug. ***

Comment 3 Petr Pisar 2021-02-01 17:21:34 UTC

The very first failure is captured at <https://koschei.fedoraproject.org/build/9035013>. This failure is similar to an older bug #1674692. This time triggered by upgrading perl-Unicode-Collate from 1.27-457.fc33 to 1.28-1.fc34. Maybe a new biber-2.16 (bug #1869114) contains the fix.

Comment 4 Ben Cotton 2021-02-09 15:32:20 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle.
Changing version to 34.

Comment 5 Fedora Release Engineering 2021-02-14 04:22:17 UTC

Dear Maintainer,

your package has an open Fails To Build From Source bug for Fedora 34.
Action is required from you.

If you can fix your package to build, perform a build in koji, and either create
an update in bodhi, or close this bug without creating an update, if updating is
not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to
acknowledge this. If you have already fixed this issue, please close this Bugzilla report.

Following the policy for such packages [2], your package will be orphaned if
this bug remains in NEW state more than 8 weeks (not sooner than 2021-02-01).

A week before the mass branching of Fedora 35 according to the schedule [3],
any packages not successfully rebuilt at least on Fedora 33 will be
retired regardless of the status of this bug.

[1] https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
[2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
[3] https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html

Comment 6 Fedora Release Engineering 2021-03-07 04:22:13 UTC

Dear Maintainer,

your package has an open Fails To Build From Source bug for Fedora 34.
Action is required from you.

If you can fix your package to build, perform a build in koji, and either create
an update in bodhi, or close this bug without creating an update, if updating is
not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to
acknowledge this. If you have already fixed this issue, please close this Bugzilla report.

Following the policy for such packages [2], your package will be orphaned if
this bug remains in NEW state more than 8 weeks (not sooner than 2021-02-01).

A week before the mass branching of Fedora 35 according to the schedule [3],
any packages not successfully rebuilt at least on Fedora 33 will be
retired regardless of the status of this bug.

[1] https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
[2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
[3] https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html

Comment 7 Fedora Release Engineering 2021-03-28 04:22:06 UTC

Dear Maintainer,

your package has an open Fails To Build From Source bug for Fedora 34.
Action is required from you.

If you can fix your package to build, perform a build in koji, and either create
an update in bodhi, or close this bug without creating an update, if updating is
not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to
acknowledge this. If you have already fixed this issue, please close this Bugzilla report.

Following the policy for such packages [2], your package will be orphaned if
this bug remains in NEW state more than 8 weeks (not sooner than 2021-02-01).

A week before the mass branching of Fedora 35 according to the schedule [3],
any packages not successfully rebuilt at least on Fedora 33 will be
retired regardless of the status of this bug.

[1] https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
[2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
[3] https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html

Comment 8 Fedora Release Engineering 2021-04-18 04:22:05 UTC

Dear Maintainer,

your package has an open Fails To Build From Source bug for Fedora 34.
Action is required from you.

If you can fix your package to build, perform a build in koji, and either create
an update in bodhi, or close this bug without creating an update, if updating is
not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to
acknowledge this. If you have already fixed this issue, please close this Bugzilla report.

Following the policy for such packages [2], your package will be orphaned if
this bug remains in NEW state more than 8 weeks (not sooner than 2021-02-01).

A week before the mass branching of Fedora 35 according to the schedule [3],
any packages not successfully rebuilt at least on Fedora 33 will be
retired regardless of the status of this bug.

[1] https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
[2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
[3] https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html

Comment 9 Fedora Release Engineering 2021-05-09 04:22:05 UTC

Dear Maintainer,

your package has an open Fails To Build From Source bug for Fedora 34.
Action is required from you.

If you can fix your package to build, perform a build in koji, and either create
an update in bodhi, or close this bug without creating an update, if updating is
not appropriate [1]. If you are working on a fix, set the status to ASSIGNED to
acknowledge this. If you have already fixed this issue, please close this Bugzilla report.

Following the policy for such packages [2], your package will be orphaned if
this bug remains in NEW state more than 8 weeks (not sooner than 2021-02-01).

A week before the mass branching of Fedora 35 according to the schedule [3],
any packages not successfully rebuilt at least on Fedora 33 will be
retired regardless of the status of this bug.

[1] https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
[2] https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
[3] https://fedorapeople.org/groups/schedule/f-35/f-35-key-tasks.html

Comment 10 Fedora Update System 2021-05-18 12:39:07 UTC

FEDORA-2021-c82dc9bfab has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-c82dc9bfab

Comment 11 Fedora Update System 2021-05-18 12:40:08 UTC

FEDORA-2021-d5916963ae has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-d5916963ae

Comment 12 Fedora Update System 2021-05-19 02:20:14 UTC

FEDORA-2021-c82dc9bfab has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-c82dc9bfab`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-c82dc9bfab

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 13 Fedora Update System 2021-05-19 02:29:33 UTC

FEDORA-2021-d5916963ae has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-d5916963ae`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-d5916963ae

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 14 Fedora Update System 2021-05-27 00:31:15 UTC

FEDORA-2021-c82dc9bfab has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 15 Fedora Update System 2021-05-27 01:04:40 UTC

FEDORA-2021-d5916963ae has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.

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