public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Claudius Heine <claudius.heine.ext@siemens.com>
To: Jan Kiszka <jan.kiszka@siemens.com>,
	"Maxim Yu. Osipov" <mosipov@ilbers.de>
Cc: Claudius Heine <ch@denx.de>, isar-users <isar-users@googlegroups.com>
Subject: Re: Project isar_claudius_ilbers_fast_ci on isar-build.org
Date: Thu, 25 Apr 2019 12:24:37 +0200	[thread overview]
Message-ID: <9563e12a-8b2b-805e-f0a1-ebbf8d82f265@siemens.com> (raw)
In-Reply-To: <c852bf20-284a-4b4c-9e3f-34c986fe3a3c@siemens.com>

Hi Jan,

On 25/04/2019 12.19, Jan Kiszka wrote:
> On 25.04.19 11:50, Maxim Yu. Osipov wrote:
>> Hi Claudius,
>>
>> I've created and configured the project Project 
>> isar_claudius_ilbers_fast_ci to launch "fast" CI.
>>
>> I've started the test build in this project (it clones your branch 
>> ch/ilbers-ci from https://github.com/cmhe/isar)and it immediately 
>> reproduced the error I reported before:
>>
>> http://isar-build.org:8080/job/isar_claudius_ilbers_fast_ci/1/console
>>
>> Any problems with access,
>> please let me know.
> 
> In fact, it didn't even need that complication in the first place: The 
> issue is also reproducible in our gitlab-ci environment.
> 
> Claudius, you have access to it, and you can look into the logs what 
> went wrong or push new versions there. It just takes a few minutes to 
> get results as the failure is early.
> 
> Once we understood this issue, it would also be good to understand why 
> Claudius earlier run on the jenkins CI didn't reveal it. But one after 
> the other.

Well probably because "fast" enabled cross-compilation.

Now I enabled cross-compilation for rpi-stretch locally and now I cannot 
build next there, but it builds apparently on isar-build...

I would really love to be able to reproduce exactly that issue locally...

Claudius

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de

  reply	other threads:[~2019-04-25 10:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-25  9:50 Maxim Yu. Osipov
2019-04-25 10:19 ` Jan Kiszka
2019-04-25 10:24   ` Claudius Heine [this message]
2019-04-25 10:30     ` Jan Kiszka
2019-04-25 10:54       ` Baurzhan Ismagulov
2019-04-25 10:58         ` Jan Kiszka
2019-04-25 11:04           ` Baurzhan Ismagulov

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=9563e12a-8b2b-805e-f0a1-ebbf8d82f265@siemens.com \
    --to=claudius.heine.ext@siemens.com \
    --cc=ch@denx.de \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.com \
    --cc=mosipov@ilbers.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