[MacPorts] #64126: qt ports: Please use known_fail yes in ports that are known to fail

[MacPorts]

#64126: qt ports: Please use known_fail yes in ports that are known to fail
-------------------------+-------------------------------------------------
 Reporter:  ryandesign   |      Owner:  MarcusCalhoun-Lopez
     Type:  defect       |     Status:  assigned
 Priority:  High         |  Milestone:
Component:  ports        |    Version:  2.7.1
 Keywords:  monterey     |       Port:  phantomjs-qt qt5 qt55 qt56 qt57
                         |  qt58 qt59
-------------------------+-------------------------------------------------
 In [b910627a24dd483d5154676d41069654e70a8df0/macports-ports] a typo was
 corrected in a comment in the ports phantomjs-qt, qt5, qt55, qt56, qt57,
 qt58, qt59. I would not have expected this to trigger any builds, but
 [https://build.macports.org/builders/ports-12_arm64-watcher/builds/1950 it
 did trigger] 165 builds on the macOS 12 arm64 builder, all of which
 failed, taking 3 hours 43 minutes to do so. And our Apple Silicon build
 machine is very fast compared to our Intel build machines, so if the same
 failure affects Intel builds it would waste an even greater amount of
 build time.

 If you can fix the build failures (and there are other tickets about
 those) that's great, but until then ''please'' use `known_fail yes` within
 a portindex-sanctioned conditional (e.g. based on `os.platform`,
 `os.major`, and/or `os.arch`) so that the build system can spend its
 limited time on more fruitful endeavors.

 There are already some occurrences of `known_fail yes` in these ports so
 that just needs to be expanded. I don't know if it's a general failure on
 Monterey or only on Monterey on Apple Silicon. Other tickets may have more
 info on what conditional to use.

-- 
Ticket URL: <https://trac.macports.org/ticket/64126>
MacPorts <https://www.macports.org/>
Ports system for macOS