public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] travis: rework NXP layerscape jobs
Date: Thu, 21 Nov 2019 07:24:26 +0100	[thread overview]
Message-ID: <12cd7fbd-da41-5fe2-d06c-a319f2dbb08f@denx.de> (raw)
In-Reply-To: <CAEUhbmXpm-fumpbRhjoYphumEMkJbbpo_ycsZ6t6-njs-6eDrQ@mail.gmail.com>

Hello Bin,

Am 21.11.2019 um 06:51 schrieb Bin Meng:
> Hi Heiko,
> 
> On Thu, Nov 21, 2019 at 1:48 PM Heiko Schocher <hs@denx.de> wrote:
>>
>> remove from NXP arm32 all layerscape boards and
>> build them instead in already existing layerscape
>> jobs (which now not only build aarch64 boards)
>>
>> Signed-off-by: Heiko Schocher <hs@denx.de>
>> ---
>> travis build:
>> https://travis-ci.org/hsdenx/u-boot-test/builds/614396275?utm_medium=notification&utm_source=email
>>
>> Changes in v2:
>> - collect in the layerscape jobs not only aarch64 based
>>    boards as Tom suggested.
>> - change subject, old was
>>    "travis: split NXP ARM32 job"
>>
>>   .travis.yml | 28 ++++++++++++++--------------
>>   1 file changed, 14 insertions(+), 14 deletions(-)
>>
>> diff --git a/.travis.yml b/.travis.yml
>> index f6aec96770..d5f34f96cc 100644
>> --- a/.travis.yml
>> +++ b/.travis.yml
>> @@ -183,27 +183,27 @@ matrix:
>>       - name: "buildman ARM bcm"
>>         env:
>>           - BUILDMAN="bcm -x mips"
>> -    - name: "buildman NXP ARM32"
>> +    - name: "buildman NXP ARM32 (catch-all)"
>>         env:
>> -        - BUILDMAN="freescale -x powerpc,m68k,aarch64"
>> -    - name: "buildman NXP AArch64 LS101x"
>> +        - BUILDMAN="freescale -x powerpc,m68k,aarch64,ls101,ls102,ls104,ls108,ls20,lx216"
>> +    - name: "buildman NXP LS101x"
>>         env:
>> -        - BUILDMAN="freescale&aarch64&ls101"
>> -    - name: "buildman NXP AArch64 LS102x"
>> +        - BUILDMAN="freescale&ls101"
>> +    - name: "buildman NXP LS102x"
>>         env:
>> -        - BUILDMAN="freescale&aarch64&ls102"
>> -    - name: "buildman NXP AArch64 LS104x"
>> +        - BUILDMAN="freescale&ls102"
>> +    - name: "buildman NXP LS104x"
>>         env:
>> -        - BUILDMAN="freescale&aarch64&ls104"
>> -    - name: "buildman NXP AArch64 LS108x"
>> +        - BUILDMAN="freescale&ls104"
>> +    - name: "buildman NXP LS108x"
>>         env:
>> -        - BUILDMAN="freescale&aarch64&ls108"
>> -    - name: "buildman NXP AArch64 LS20xx"
>> +        - BUILDMAN="freescale&ls108"
>> +    - name: "buildman NXP LS20xx"
>>         env:
>> -        - BUILDMAN="freescale&aarch64&ls20"
>> -    - name: "buildman NXP AArch64 LX216x"
>> +        - BUILDMAN="freescale&ls20"
>> +    - name: "buildman NXP LX216x"
>>         env:
>> -        - BUILDMAN="freescale&aarch64&lx216"
>> +        - BUILDMAN="freescale&lx216"
>>       - name: "buildman i.MX6 tqc"
>>         env:
>>           - BUILDMAN="mx6&tqc"
> 
> Will you do the same for Azure? Or does this only apply to Travis?

The patch is only for travis, as travis has a job timeout of 50 minutes,
and this job took to long for me...

The question is, does have Azure also such a job timeout?

Do we want to have the Azure jobs in sync with travis jobs?

bye,
Heiko
-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-52   Fax: +49-8142-66989-80   Email: hs at denx.de

  reply	other threads:[~2019-11-21  6:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-21  5:47 [U-Boot] [PATCH v2] travis: rework NXP layerscape jobs Heiko Schocher
2019-11-21  5:51 ` Bin Meng
2019-11-21  6:24   ` Heiko Schocher [this message]
2019-11-21 12:58     ` Tom Rini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=12cd7fbd-da41-5fe2-d06c-a319f2dbb08f@denx.de \
    --to=hs@denx.de \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox