Using all-Apple Thunderbolt hardware to kill my MacBook

Re:Using all-Apple Thunderbolt hardware to kill my MacBook by AnonC on Saturday October 17, 2020 @12:50PM (#24811253)

Apple's penchant for silence or not responding shows in bug reports too. Most of the time there are no responses or changes in the status to any issues filed. Apple uses an internal tracking system for itself and an external system for anyone outside Apple, and hardly any information flows back from the internal system.

[ Parent | on HN ]

Re:Using all-Apple Thunderbolt hardware to kill my MacBook by RyJones on Saturday October 17, 2020 @12:56PM (#24811318)

Here is the specific issue that was breaking our CI system[0]. I don't have XCode set up anywhere to see if this is still broken.

[0]: https://gist.github.com/ryjones/3e9a851e92794d67b5e37197608a...

[ Parent | on HN ]

Re:Using all-Apple Thunderbolt hardware to kill my MacBook by saagarjha on Saturday October 17, 2020 @01:42PM (#24811675)

I am fairly sure this heuristic was implemented on purpose.

[ Parent | on HN ]

Re:Using all-Apple Thunderbolt hardware to kill my MacBook by RyJones on Saturday October 17, 2020 @01:49PM (#24811735)

Agreed; however, it ignores return value of the build step.

[ Parent | on HN ]

Re:Using all-Apple Thunderbolt hardware to kill my MacBook by saagarjha on Saturday October 17, 2020 @01:57PM (#24811812)

This logs as a warning, right? “Step produced errors even though tool exited successfully?”

[ Parent | on HN ]

Re:Using all-Apple Thunderbolt hardware to kill my MacBook by RyJones on Saturday October 17, 2020 @02:09PM (#24811892)

no, the build step was info, not warn. It is detected as an error, and stops CI

[ Parent | on HN ]