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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3533 bytes
Desc: not available
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20190323/15369e08/attachment.bin>