Bug 1309731 - trojita: FTBFS in rawhide - tests fail on x86 because 32 bits (i386|i686)
Summary: trojita: FTBFS in rawhide - tests fail on x86 because 32 bits (i386|i686)
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: trojita
Version: rawhide
Hardware: i686
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Raphael Groner
QA Contact: Fedora Extras Quality Assurance
URL: https://apps.fedoraproject.org/kosche...
Whiteboard:
Depends On: 1307633
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-18 14:59 UTC by Raphael Groner
Modified: 2016-04-16 11:57 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-16 11:57:32 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
build.log (i386) (678.84 KB, text/plain)
2016-02-18 14:59 UTC, Raphael Groner
no flags Details
build.log (x86_64) (659.16 KB, text/plain)
2016-02-22 14:08 UTC, Raphael Groner
no flags Details

Description Raphael Groner 2016-02-18 14:59:47 UTC
Created attachment 1128253 [details]
build.log (i386)

Description of problem:
Package trojita fails to build from source in rawhide.

Version-Release number of selected component (if applicable):
0.6-1.fc24

Steps to Reproduce:
koji build --scratch f24 trojita-0.6-1.fc24.src.rpm

Additional info:
This package is tracked by Koschei. See:
https://apps.fedoraproject.org/koschei/package/trojita

See attached build.log, it contains warnings about missed charset "iso-8859-2", it seems to be gone on i386 only but available on x86_64. I strongly guess that's related to a false rebuild of libicu, libicu is used in QTextCodec (Qt5Core) and QTextCodec is used in the failing trojita tests.

Comment 1 Rex Dieter 2016-02-18 15:06:58 UTC
technically, the build succeeds, it's only the *%check* phase that fails

Comment 2 Raphael Groner 2016-02-22 14:06:59 UTC
Unfortunately, we see additionally on x86_64 other tests to fail, with a weird dbus error.

process 5553: arguments to dbus_connection_dispatch() were incorrect, assertion "connection != NULL" failed in file ../../dbus/dbus-connection.c line 4585.

The following tests FAILED:
	  3 - test_Html_formatting (OTHER_FAULT)
	  9 - test_Imap_MsgPartNetAccessManager (OTHER_FAULT)

Comment 3 Raphael Groner 2016-02-22 14:08:06 UTC
Created attachment 1129316 [details]
build.log (x86_64)

Comment 4 Raphael Groner 2016-02-22 14:10:52 UTC
(In reply to Rex Dieter from comment #1)
> technically, the build succeeds, it's only the *%check* phase that fails

Those tests are acceptance tests on a high level to simulate use cases. It's a bad idea to skip those, upstream confirms that we should keep all tests.

Comment 5 Jan Kurik 2016-02-24 15:34:13 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase

Comment 6 Raphael Groner 2016-02-24 19:02:40 UTC
x86_64 is fixed, but still the same error on i686

Comment 7 Raphael Groner 2016-02-24 19:03:15 UTC
Comment on attachment 1129316 [details]
build.log (x86_64)

fixed

Comment 8 Raphael Groner 2016-02-29 18:44:37 UTC
Disabled the tests on i386.
No good solution at all but it should fix nightlies for now.

Comment 9 Upstream Release Monitoring 2016-02-29 19:39:56 UTC
raphgro's trojita-0.6-2.fc25 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=738594

Comment 10 Upstream Release Monitoring 2016-03-08 17:01:07 UTC
rdieter's trojita-0.6-3.fc25 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=743051

Comment 11 Raphael Groner 2016-04-05 15:53:41 UTC
Fixed in F24.
http://koji.fedoraproject.org/koji/taskinfo?taskID=13566309

I'm aiting for a successful rebuild of icu in rawhide, to can fully validate the fix.

Comment 12 Upstream Release Monitoring 2016-04-16 11:45:40 UTC
raphgro's trojita-0.6-4.fc25 completed http://koji.fedoraproject.org/koji/buildinfo?buildID=751300


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