All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Rust test too long
Date: Thu, 21 Jun 2018 23:41:04 +0200	[thread overview]
Message-ID: <d2deab79-5ca8-4dc7-e0c6-2e0dafd70255@mind.be> (raw)
In-Reply-To: <20180618204438.7a481c7e@windsurf>



On 18-06-18 20:44, Thomas Petazzoni wrote:
> Hello,
> 
> On Mon, 18 Jun 2018 20:33:20 +0200, Eric Le Bihan wrote:
> 
>>> Is this expected that this test takes as much as 3 hours ? Is there
>>> something we can do to reduce this ?  
>>
>> What is the horsepower of the Gitlab instance?
> 
> I have no idea :-/
> 
>> When building rust from source, the longest part is building the LLVM
>> backend.
>>
>> On a 4-core i5-7500 CPU @ 3.40GHz, TestRust takes 60 minutes. But on a
>> 4-core i3-4010U CPU @ 1.70GHz, it does takes nearly 3 hours...
> 
> OK, so it is not crazy that the Gitlab instances are not able to build
> this. So, I'd say we need to:
> 
>  - In the short term, disable this test from the Gitlab testing. Do you
>    think you could look into this ?
> 
>  - In the mid/long term, have our own Gitlab instances, that have more
>    horsepower and no limit in the duration of jobs.

 I actually have spare cycles @work, but I'm lacking the time to set up a gitlab
runner instance. I'm also lacking in disk space but for the tests it should be fine.

 Regards,
 Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

      reply	other threads:[~2018-06-21 21:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-10 14:57 [Buildroot] Rust test too long Thomas Petazzoni
2018-06-18 18:33 ` Eric Le Bihan
2018-06-18 18:44   ` Thomas Petazzoni
2018-06-21 21:41     ` Arnout Vandecappelle [this message]

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=d2deab79-5ca8-4dc7-e0c6-2e0dafd70255@mind.be \
    --to=arnout@mind.be \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.