Report created on Wed Mar 29 20:53:48 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
audio/bristol pierrejacques.mimifir@gmail.com new_compiler_error    
cad/freecad tj+freebsd_ports@a13.fr new_compiler_error    
databases/xapian-core10 ports@FreeBSD.org ???
new_compiler_error
   
devel/cheritrace-devel theraven@FreeBSD.org new_compiler_error    
devel/include-what-you-use koobs@FreeBSD.org new_compiler_error    
devel/libepoll-shim x11@FreeBSD.org new_compiler_error    
devel/libgrading jonathan@FreeBSD.org missing_header
new_compiler_error
   
devel/linenoise-ng lx@FreeBSD.org new_compiler_error    
devel/pure-stllib lichray@gmail.com new_compiler_error    
devel/spdlog vanilla@FreeBSD.org new_compiler_error    
emulators/simh bob@eager.cx linker_error
new_compiler_error
   
ftp/curlpp sunpoet@FreeBSD.org new_compiler_error    
games/bunnysay ben.lavery@hashbang0.com new_compiler_error    
graphics/hugin grog@FreeBSD.org new_compiler_error    
graphics/libboard thierry@FreeBSD.org new_compiler_error    
graphics/opencolorio FreeBSD@Shaneware.biz new_compiler_error    
lang/dmd2 cy@FreeBSD.org coredump
linker_error
new_compiler_error
   
lang/newlisp olgeni@FreeBSD.org new_compiler_error    
lang/newlisp-devel olgeni@FreeBSD.org new_compiler_error    
lang/squirrel ports@FreeBSD.org ???
new_compiler_error
   
net/nethogs anastasios@mageirias.com new_compiler_error    
net/ns3 koue@chaosophia.net ???
new_compiler_error
   
net/openvswitch kevlo@FreeBSD.org new_compiler_error    
net/yami4 prog@msobczak.com new_compiler_error    
security/honggfuzz sbz@FreeBSD.org new_compiler_error    
security/revealrk pi@FreeBSD.org clang
new_compiler_error
   
security/sha1collisiondetection jharris@widomaker.com clang_werror
new_compiler_error
   
sysutils/asmon bofh@FreeBSD.org clang
new_compiler_error
   
sysutils/atop samm@os2.kiev.ua clang
new_compiler_error
   
sysutils/lnav tom@hur.st new_compiler_error    
sysutils/muse freebsd@spatula.net clang
new_compiler_error
   
sysutils/p5-BSD-Sysctl david@landgren.net new_compiler_error    
sysutils/wmmemfree ports@FreeBSD.org clang
new_compiler_error
   
textproc/ansifilter ports@FreeBSD.org new_compiler_error    
textproc/htdig ports@FreeBSD.org new_compiler_error    
textproc/opengrm-ngram demon@FreeBSD.org new_compiler_error    
www/py-libsass yuri@rawbw.com new_compiler_error    
ports shown: 37   ports with build errors: 37 ports with outstanding PRs: 0  
ports with either build errors or PRs: 37

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.