Bug 220222 - devel/llvm40 poudriere build creates broken package on i386-10 (Lzma library error: No progress is possible)
Summary: devel/llvm40 poudriere build creates broken package on i386-10 (Lzma library ...
Status: Closed Not A Bug
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: i386 Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-23 07:37 UTC by Andriy Voskoboinyk
Modified: 2018-02-17 00:39 UTC (History)
2 users (show)

See Also:

Attachments
devel/llvm40 build log (101.65 KB, application/x-xz)
2017-06-23 07:37 UTC, Andriy Voskoboinyk 		no flags Details
graphics/mesa-libs build log with error message (12.43 KB, text/plain)
2017-06-23 07:38 UTC, Andriy Voskoboinyk 		no flags 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 Andriy Voskoboinyk freebsd_committer freebsd_triage 2017-06-23 07:37:10 UTC 
Created attachment 183731 [details]
devel/llvm40 build log

Host version: FreeBSD 12.0-CURRENT r319760
Jail version: FreeBSD 10.3-RELEASE (from ftp)

This was reproduced twice; the broken package was uploaded to freefall:/home/avos/broken_pkgs/llvm40-4.0.1.r1_5.txz (145 MB)
Comment 1 Andriy Voskoboinyk freebsd_committer freebsd_triage 2017-06-23 07:38:56 UTC 
Created attachment 183732 [details]
graphics/mesa-libs build log with error message
Comment 2 Mark Linimon freebsd_committer freebsd_triage 2017-06-23 14:24:34 UTC 
I can't make a guess as to the problem here but I'm going to guess it is in the build phase rather than the extract phase.  Assign but Cc: bdrewery@.
Comment 3 Brooks Davis freebsd_committer freebsd_triage 2017-06-23 17:37:28 UTC 
This looks like a pkg issue and nothing to do with llvm except perhaps that llvm is massive.
Comment 4 Brooks Davis freebsd_committer freebsd_triage 2017-10-15 18:51:18 UTC 
This is clearly a truncated file.  I have no idea why it might have happened.
Comment 5 Andriy Voskoboinyk freebsd_committer freebsd_triage 2017-11-07 00:28:49 UTC 
Looks like 'out of space' errors are ignored - this one was gone after turning 'tmpfs' option off.
Comment 6 Walter Schwarzenfeld 2018-01-31 18:27:57 UTC 
Seems solved. Could be closed.
Comment 7 Walter Schwarzenfeld 2018-02-17 00:39:07 UTC 
See comment11. Not a bug.