Report created on Sun Jul 23 20:56:26 2017. back to main menu


Enter a new build error (partial match is ok) to get information about FreeBSD ports with that error:

Build error: 

For explanatory information and summary details, see the notes below.

portname maintainer build error logs Problem Reports Responsible
astro/opencpn ml@netfence.it clang    
audio/gnuspeechsa amdmi3@FreeBSD.org clang    
audio/ncmpcpp yamagi@yamagi.org clang    
audio/wildmidi liangtai.s16@gmail.com clang
compiler_error
   
benchmarks/nosqlbench vg@FreeBSD.org clang    
chinese/tin ports@FreeBSD.org clang    
databases/mongodb34-rocks numisemis@yahoo.com clang    
databases/percona56-server flo@FreeBSD.org clang
gcc4_error
   
databases/riak2 wg@FreeBSD.org clang
coredump
   
databases/timescaledb kbowling@FreeBSD.org clang    
devel/blame jhein@symmetricom.com ???
clang
   
devel/byacc sunpoet@FreeBSD.org clang    
devel/cvs-devel bdheeman@gmail.com clang
manpage
   
devel/grpc vanilla@FreeBSD.org clang    
devel/liblas12 rhurlin@gwdg.de clang
manpage
   
devel/libnfc romain@FreeBSD.org clang    
devel/plan9port ports@FreeBSD.org clang    
devel/py-pyinstaller python@FreeBSD.org clang    
devel/qtscriptgenerator syncer@gmail.com clang    
dns/dnscrypt-proxy freebsd@dns-lab.com clang    
editors/texworks hrs@FreeBSD.org clang    
emulators/gngeo acm@FreeBSD.org clang-bug    
games/widelands amdmi3@FreeBSD.org clang    
graphics/dia gnome@FreeBSD.org clang    
graphics/gsculpt ports@FreeBSD.org clang    
graphics/sdump sue@iwmt.org clang    
lang/lua53 gmesalazar@gmail.com clang    
lang/racket-minimal olgeni@FreeBSD.org ???
clang
   
mail/deforaos-mailer olivier@FreeBSD.org clang-bug    
mail/thunderbird gecko@FreeBSD.org clang    
net-mgmt/yaf dikshie@sfc.wide.ad.jp clang    
net/bnxt-kmod [I] shurd@FreeBSD.org clang    
news/tin johans@FreeBSD.org clang    
science/avogadro ports@FreeBSD.org clang    
security/opencryptoki hrs@FreeBSD.org clang    
sysutils/py-psutil121 swills@FreeBSD.org clang
new_compiler_error
   
www/firefox gecko@FreeBSD.org clang    
www/firefox-esr gecko@FreeBSD.org clang    
www/libxul gecko@FreeBSD.org clang    
www/mod_perl2 apache@FreeBSD.org clang-bug    
www/seamonkey gecko@FreeBSD.org clang    
x11-toolkits/mygui amdmi3@FreeBSD.org clang    
ports shown: 42   ports with build errors: 42 ports with outstanding PRs: 0  
ports with either build errors or PRs: 42

Notes:

Clicking on each column heading will cause the report to be redone sorted by that column. Clicking again will reverse the sort.

The portname column includes links to a more complete overview for that port.

The maintainer column includes links to a page showing the status of all ports for that maintainer.

The build error logs column represents the list of unique errors noticed in any build environment (if any). The errors are listed alphabetically. Each entry is a link to a particular errorlog. (In cases where the same error occurs in multiple build environments, the latest errorlog is used.)

The list of build errors that are detected, and a short description of each one, can be found here.

The PRs (if any) for the given port are listed numerically in the Problem Reports column. Thus, for each port, they should also be in order from earliest to latest.

Currently, no effort is made to correlate any individual build error with any individual PR. They are listed in adjacent columns only for your viewing convenience.

The underlying technology of this report relies on trying to extract information from the existing PR database entries. These entries are entered by human users using the send-pr command. As such, the quality of the entries varies greatly.

The fastest, and easiest, information is gleaned from a PR entry whose subject line contains the port category and port name, separated by a slash. However, if this algorithm only flagged those, it would miss nearly 50% of the ports PRs, not to mention all the 'framework' PRs.

So, as an extension, various heuristics are used to guess what it is the user really intended. See the code in prQueryUtils.py for the gory details. What's important to understand is this: there is no possible algorithm that will correctly identify all the ambiguous PRs without getting a few false identifications and still run in less than geological time. So, before you are tempted to file a PR on this algorithm itself, read the code to understand its design tradeoffs, and then consider instead filing followup PRs to the ambiguous PRs that would disambiguate them instead. Thanks -- the author.