Taking my own summary for example: http://portsmon.freebsd.org/portsconcordanceformaintainer.py?maintainer=marino%40FreeBSD.org It shows 3 build failures: - devel/matreshka - lang/gnatdroid-armv7 - www/aws www/aws ======= If you click on "cluster" link, you get 404 it tries to go to: http://beefy2.isc.freebsd.org/bulk/83amd64-default/latest/logs/errors/aws-3.1.0.0_2.log The current version of aws/aws is 3.2.0.0 since 17 may, there are no build failures per http://portsmon.freebsd.org/portoverview.py?category=www&portname=aws lang/gnatdroid-armv7 ==================== If you click on "cluster" link, you get 404 tried: http://beefy1.isc.freebsd.org/bulk/83i386-default/latest/logs/errors/gnatdroid-armv7-20140416.log if you click on "???" link, you get a log at http://beefy1.isc.freebsd.org/bulk/84i386-default/latest/logs/errors/gnatdroid-armv7-20140422_1.log The current version is 20140722 the log matches the only (stale) failure of http://portsmon.freebsd.org/portoverview.py?category=lang&portname=gnatdroid-armv7 so it's sort of ok... devel/matreshka =============== the "???" link is 404 as well, tried to go *old* http://beefy1.isc.freebsd.org/bulk/91i386-quarterly/latest/logs/errors/matreshka-0.6.0_3.log the "cluster" link is a real log, but it's even older: http://beefy1.isc.freebsd.org/bulk/93i386-RELENG_9_3/latest/logs/errors/matreshka-0.6.0_2.log The current version is 0.6.0_5 this is currently out of sync: http://portsmon.freebsd.org/portoverview.py?category=devel&portname=matreshka There are error logs and good packages showing for the same entries at the same time. The page has been like this for weeks. I thought i would document it with a bug report.
adding Mark to CC
CC bugmeister too
Related: http://portsmon.freebsd.org/portoverview.py?category=security&portname=wpa_supplicant Overall Status security/wpa_supplicant is no longer a valid port: (deleted per /usr/ports/MOVED) This port was restored a few days ago and the page shows 6 successful packages. It seems the whatever mechanism that determines "overall status" has no way to trigger when a change occurs.
we need to assign this PR to someone. Who is responsible for updating portmon?
any news here? These incorrect links are still showing so it looks like nothing has changed.
A partial fix has been committed. The problem is that the errorlog URLs were being encoded with the "default/" subdirectory. Although this is where they first appear, the URL must and shall be a full path to the individual build timestamp. This is necessary but insufficient. The problem is that as new builds are undertaken, an individual error may or may not go away. What we want is to show "the last time the port built correctly" and "the log from the last failure." If the port now builds correctly, the errorlog entry should be deleted. If the port has instead been marked BROKEN (or so on), the errorlog entry should _not_ be deleted. Right now the partial fix is that stale errorlogs are not deleted, but at least the URLs are correct. This is going to take more rework than I can do in the next few days. I need some non-interrupted time and so far this year that has been quite scarce. I'm sorry that it took this long just to assess the damage.
Data from EOL releases has now been deleted. More work is needed.
Unfortunately I have not worked on portsmon in several years. If someone wants to take it over, please contact me offline.