Re: fake azure pipeline failures

[Zero King]

On Sat, Mar 23, 2019 at 12:30:36PM -0500, Ryan Schmidt wrote:



On Mar 23, 2019, at 04:45, Christopher Jones wrote:


Also, it makes no sense the travis builds timeout - The build should not take 
anything close to 50mins - and again these builds seem to offer no explanation  
in any log I can find as to why they timeout, i.e. what’s exactly where they 
doing at the time they stopped ?


I agree. I do not know why more detailed logs are not being uploaded from 
Travis for these builds.


Our CI bot (build runner) receives complete messages from a Go channel,
so it doesn't support streaming. However unless the runner is aware of
when the build would time out (even just approximately), the best way to
provide more insight before the build gets killed (because of timeout)
is to stream the output to the Travis log, which would require some code
refactoring. I did add the empty *-start messages to indicate roughly
what the bot is doing.

BTW, in Azure Pipelines, if a build stage times out its log would become
unavailable (e.g. [1]). We can workaround this by making the runner exit
before the build times out. But of course it would be best for Microsoft
to fix this bug.

[1] https://dev.azure.com/macports/macports-ports/_build/results?buildId=601


P.S: Remember to use lists.macports.org list addresses, not the older ones. 
Although the old addresses forward to the new ones, some users cannot see those 
forwards due to the way their email providers' servers are configured.



--
Zero


smime.p7s
Description: S/MIME cryptographic signature

Re: fake azure pipeline failures

[Ryan Schmidt]

On Mar 23, 2019, at 04:45, Christopher Jones wrote:

> Also, it makes no sense the travis builds timeout - The build should not take 
> anything close to 50mins - and again these builds seem to offer no 
> explanation  in any log I can find as to why they timeout, i.e. what’s 
> exactly where they doing at the time they stopped ?

I agree. I do not know why more detailed logs are not being uploaded from 
Travis for these builds.

P.S: Remember to use lists.macports.org list addresses, not the older ones. 
Although the old addresses forward to the new ones, some users cannot see those 
forwards due to the way their email providers' servers are configured.

Re: fake azure pipeline failures

[Joshua Root]

On 2019-3-23 21:12 , Christopher Jones wrote:
> Hi,
> 
>>>
>>>
>>
>> You have to click through a couple things in Azure, but it does have a
>> log available: 
> 
> Thanks ! 
> 
> Could you briefly explain the steps to get there ? Honestly, I was
> clicking around for quite a while and failed to find my way to that log ?

1. Click Details by the Azure check in the PR.
2. Click "View more details on Azure Pipelines" at the bottom of the page.
3. Click "Build Job" in the left pane under Logs.
4. Click the failed step in the right pane, which is "Run port tests" in
this case.
5. Scroll down to the failure, where there will be a link to the paste
service which you have to cmd-click to follow for some reason.

- Josh

Re: fake azure pipeline failures

[Christopher Jones]

Hi,

>> 
>> 
> 
> You have to click through a couple things in Azure, but it does have a
> log available:  >

Thanks ! 

Could you briefly explain the steps to get there ? Honestly, I was clicking 
around for quite a while and failed to find my way to that log ?

> 
> Relevant section:
> 
> DEBUG: system: mkfontscale /opt/local/share/fonts/OTF
> sh: mkfontscale: command not found
> Command failed: mkfontscale /opt/local/share/fonts/OTF
> Exit code: 127
> Error: Failed to activate font-misc-ethiopic: command execution failed
> 
> It only has mkfontscale in depends_build but apparently uses it after
> build time.

Hmm thanks. This port was last updated in

https://github.com/macports/macports-ports/commit/0b0b1c6a303ab8f3bfebf1fdfdda2015a5336851
 


which did indeed change the deps w.r.t. mkfonstscale etc. Looks like something 
slipped through the cracks there.

cheers Chris

> 
> - Josh



smime.p7s
Description: S/MIME cryptographic signature

Re: fake azure pipeline failures

[Joshua Root]

On 2019-3-23 20:45 , Christopher Jones wrote:
> Hi,
> 
> Can anyone caste any light on why the checks in
> 
> https://github.com/macports/macports-ports/pull/3873
> 
> are failing ?
> 
> I am pretty certain, as I discuss in the comments, that the port update
> in question builds fine across the board, so the failures are in some
> sense fake, but I also cannot, and would like to, explain why they are
> happening. The azure pipeline failure just says
> 
> Installing dependency (158 of 170) 'font-misc-ethiopic' with variants ''
> (requesting '') ... [FAIL]
> 
> 
> but offers no explanation as to why, and I can install the above just
> fine myself, from both binary tarball and from source. So why does the
> check fail to install it ?
> 
> Also, it makes no sense the travis builds timeout - The build should not
> take anything close to 50mins - and again these builds seem to offer no
> explanation  in any log I can find as to why they timeout, i.e. what’s
> exactly where they doing at the time they stopped ?
> 
> Its great to have these checks, but not if its not possible to find out
> *why* they fail sometimes… ;)

You have to click through a couple things in Azure, but it does have a
log available: 

Relevant section:

DEBUG: system: mkfontscale /opt/local/share/fonts/OTF
sh: mkfontscale: command not found
Command failed: mkfontscale /opt/local/share/fonts/OTF
Exit code: 127
Error: Failed to activate font-misc-ethiopic: command execution failed

It only has mkfontscale in depends_build but apparently uses it after
build time.

- Josh