svn commit: r50435 - head/en_US.ISO8859-1/htdocs/news/status

Sun Jul 2 21:49:31 UTC 2017

Author: bjk
Date: Sun Jul  2 21:49:30 2017
New Revision: 50435
URL: https://svnweb.freebsd.org/changeset/doc/50435

Log:
  Add 2017Q2 entry on ports on non-x86 from linimon

Modified:
  head/en_US.ISO8859-1/htdocs/news/status/report-2017-04-2017-06.xml

Modified: head/en_US.ISO8859-1/htdocs/news/status/report-2017-04-2017-06.xml
==============================================================================

--- head/en_US.ISO8859-1/htdocs/news/status/report-2017-04-2017-06.xml	Sun Jul  2 21:31:53 2017	(r50434)
+++ head/en_US.ISO8859-1/htdocs/news/status/report-2017-04-2017-06.xml	Sun Jul  2 21:49:30 2017	(r50435)
@@ -488,4 +488,61 @@
 	accurate representations.</p>
     </body>
   </project>
+
+  <project cat='ports'>
+    <title>Updating Port Metadata for non-x86 Architectures</title>
+
+    <contact>
+      <person>
+	<name>
+	  <given>Mark</given>
+	  <common>Linimon</common>
+	</name>
+	<email>linimon at FreeBSD.org</email>
+      </person>
+    </contact>
+
+    <links>
+      <url href="http://thunderx1.nyi.FreeBSD.org/jail.html?mastername=110arm64-default">aarch64 Poudriere Machine</url>
+      <url href="http://beefy8.nyi.FreeBSD.org/jail.html?mastername=head-armv6-default">armv6 Poudriere Machine</url>
+    </links>
+
+    <body>
+      <p>I have been analyzing the error logs from ports builds for
+	all non-x86 architectures, including both the logs published
+	on the package build cluster and also other builds of
+	powerpc64 and sparc64.</p>
+
+      <p>From this analysis, I have marked almost all the failing
+	ports as either <tt>BROKEN</tt> or
+	<tt>NOT_FOR</tt>/<tt>ONLY_FOR</tt>, as appropriate.</p>
+
+      <p>The intent of this work is not to make life harder for
+	anyone, but rather, in fact, the opposite.  With these
+	definitions in place, it is possible to scan the poudriere
+	bulk build output (the "Ignored ports" portion, in
+	particular) and see quickly what ports are failing to build
+	and why.  Previously, finding the exact reason why a build
+	failed needed some research (<tt>portsmon</tt> only models
+	failure messages on amd64).  Additionally, it is extremely
+	difficult to work through several hundred logs that simply say
+	"failed to compile", "failed to link", and
+	so forth.</p>
+
+      <p>This is part of an effort to identify where we need further
+	work to bring sufficient Ports Collection support to, e.g.,
+	armv6 and aarch64 to bring them closer to true Tier-1
+	status.</p>
+
+      <p>To further facilitate locating patterns in the Poudriere
+	output, I have begun reworking some existing
+	<tt>BROKEN</tt>/<tt>NOT_FOR</tt>/<tt>ONLY_FOR</tt> messages so
+	that they will sort more easily.  This includes sorting the
+	order of the <tt>ARCH</tt> definitions.</p>
+
+      <p>Many people have been doing great work on fixing the
+	individual ports.  I hope that my work makes their jobs
+	somewhat easier.</p>
+    </body>
+  </project>
 </report>
