[Buildroot] Rust test too long

[Buildroot] Rust test too long

[Thomas Petazzoni]

Hello Eric,

The tests.package.test_rust.TestRust test case takes more than 3 hours
and Gitlab, and causes the overall test suite to always fail:

  https://gitlab.com/buildroot.org/buildroot/pipelines/23578303/failures

(This one also has a failure related to check-package caused by the
mender package, but I've fixed that)

Is this expected that this test takes as much as 3 hours ? Is there
something we can do to reduce this ?

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

[Buildroot] Rust test too long

[Eric Le Bihan]

Hi!

On 2018-06-10 16:57, Thomas Petazzoni wrote:
> Hello Eric,
>
> The tests.package.test_rust.TestRust test case takes more than 3 hours
> and Gitlab, and causes the overall test suite to always fail:
>
>   https://gitlab.com/buildroot.org/buildroot/pipelines/23578303/failures
>
> (This one also has a failure related to check-package caused by the
> mender package, but I've fixed that)
>
> 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?

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...

Regards.

--
ELB

[Buildroot] Rust test too long

[Thomas Petazzoni]

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.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

[Buildroot] Rust test too long

[Arnout Vandecappelle]

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