Re: how to handle 'internal' logs for failed builds

2024-04-04 Thread Ryan Schmidt
On Apr 4, 2024, at 17:29, Joshua Root wrote: > > Do that on a branch, make some change to the affected port as well, and push > to your fork and let CI run. That presumes it will fail in CI. If it succeeds in CI but fails on buildbot, suspect a case sensitivity issue.

Re: how to handle 'internal' logs for failed builds

2024-04-04 Thread Joshua Root
On 5/4/2024 01:39, Chris Jones wrote: So what is happening is the build internally packages its own versions of some externals, freetype being one of them, and its this that fails during configure for some reason. The problem is the contents of that log are, of course, not in the macports bui

Re: how to handle 'internal' logs for failed builds

2024-04-04 Thread Fred Wright
On Thu, 4 Apr 2024, Chris Jones wrote: [...] The problem is the contents of that log are, of course, not in the macports build log, so I cannot see what it is that is causing it, and as it works for me I cannot look locally myself. I've tried looking at my versions of the logs, and just gues

how to handle 'internal' logs for failed builds

2024-04-04 Thread Chris Jones
Hi, I recently pushed an update to the root6 port. It works fine for me but fails on all build bots, e.g. https://build.macports.org/builders/ports-12_arm64-builder/builds/17/steps/install-port/logs/stdio the only error is this './configure' '--prefix' '/opt/local/var/macports/build/