[Buildroot] [PATCH] configs/freescale_p1025twr: needs host-openssl for the Linux kernel build

[Buildroot] [PATCH] configs/freescale_p1025twr: needs host-openssl for the Linux kernel build

[Thomas Petazzoni]

Fixes:

  https://gitlab.com/buildroot.org/buildroot/-/jobs/59015355

Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
---
 configs/freescale_p1025twr_defconfig | 1 +
 1 file changed, 1 insertion(+)

diff --git a/configs/freescale_p1025twr_defconfig b/configs/freescale_p1025twr_defconfig
index f7cc50f093..13ec517fbd 100644
--- a/configs/freescale_p1025twr_defconfig
+++ b/configs/freescale_p1025twr_defconfig
@@ -12,6 +12,7 @@ BR2_LINUX_KERNEL_CUSTOM_VERSION_VALUE="4.15.7"
 BR2_LINUX_KERNEL_DEFCONFIG="mpc85xx_smp"
 BR2_LINUX_KERNEL_DTS_SUPPORT=y
 BR2_LINUX_KERNEL_INTREE_DTS_NAME="fsl/p1025twr"
+BR2_LINUX_KERNEL_NEEDS_HOST_OPENSSL=y
 
 # Filesystem
 BR2_TARGET_ROOTFS_CPIO=y
-- 
2.14.3

[Buildroot] [PATCH] configs/freescale_p1025twr: needs host-openssl for the Linux kernel build

[Peter Korsgaard]

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:

 > Fixes:
 >   https://gitlab.com/buildroot.org/buildroot/-/jobs/59015355

 > Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>

Committed, thanks.

-- 
Bye, Peter Korsgaard

[Buildroot] [PATCH] configs/freescale_p1025twr: needs host-openssl for the Linux kernel build

[Matthew Weber]

Thomas,

On Sat, Mar 24, 2018 at 9:26 AM, Thomas Petazzoni
<thomas.petazzoni@bootlin.com> wrote:
> Fixes:
>
>   https://gitlab.com/buildroot.org/buildroot/-/jobs/59015355
>

Sorry, I didn't realize this failed.  Is there an automated email on
this sort of failure?

Matt

[Buildroot] [PATCH] configs/freescale_p1025twr: needs host-openssl for the Linux kernel build

[Thomas Petazzoni]

Hello,

On Sat, 24 Mar 2018 20:15:33 -0500, Matthew Weber wrote:

> > Fixes:
> >
> >   https://gitlab.com/buildroot.org/buildroot/-/jobs/59015355
> 
> Sorry, I didn't realize this failed.  Is there an automated email on
> this sort of failure?

No, there isn't. Unfortunately, the Gitlab CI infra is not very
reliable, and a number of failures are not related to real problems in
Buildroot, but to Gitlab CI infrastructure problems.

Best regards,

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

[Buildroot] [PATCH] configs/freescale_p1025twr: needs host-openssl for the Linux kernel build

[Arnout Vandecappelle]

On 25-03-18 21:20, Thomas Petazzoni wrote:
> Hello,
> 
> On Sat, 24 Mar 2018 20:15:33 -0500, Matthew Weber wrote:
> 
>>> Fixes:
>>>
>>>   https://gitlab.com/buildroot.org/buildroot/-/jobs/59015355
>>
>> Sorry, I didn't realize this failed.  Is there an automated email on
>> this sort of failure?
> 
> No, there isn't. Unfortunately, the Gitlab CI infra is not very
> reliable, and a number of failures are not related to real problems in
> Buildroot, but to Gitlab CI infrastructure problems.

 Well, to be completely fair, it's not really the Gitlab CI infra which is
unreliable. Rather, it's the free runners that are unreliable. I expect that if
we would have a dedicated runner, we wouldn't see these problems. At least,
that's how it looks to me (I'm not really an expert though).

 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

[Buildroot] [PATCH] configs/freescale_p1025twr: needs host-openssl for the Linux kernel build

[Matthew Weber]

Arnout, Thomas,

On Mon, Mar 26, 2018 at 6:55 AM, Arnout Vandecappelle <arnout@mind.be> wrote:
>
>
> On 25-03-18 21:20, Thomas Petazzoni wrote:
>> Hello,
>>
>> On Sat, 24 Mar 2018 20:15:33 -0500, Matthew Weber wrote:
>>
>>>> Fixes:
>>>>
>>>>   https://gitlab.com/buildroot.org/buildroot/-/jobs/59015355
>>>
>>> Sorry, I didn't realize this failed.  Is there an automated email on
>>> this sort of failure?
>>
>> No, there isn't. Unfortunately, the Gitlab CI infra is not very
>> reliable, and a number of failures are not related to real problems in
>> Buildroot, but to Gitlab CI infrastructure problems.
>
>  Well, to be completely fair, it's not really the Gitlab CI infra which is
> unreliable. Rather, it's the free runners that are unreliable. I expect that if
> we would have a dedicated runner, we wouldn't see these problems. At least,
> that's how it looks to me (I'm not really an expert though).
>

Has anyone setup a Gitlab console/REST client?  We could build a
script on top of that which monitors the failed builds and does log
analysis (not sure what output our .gitlab-ci.yml is setup for
capturing).  Hopefully using that we could discard the bad jobs.  Then
we should be able to at least get the stage of failure from the API
too, which if each defconfig is a stage we could then map to
maintainer.  Similarly for the test cases....

If there isn't a console/REST client setup....
- Could we generate some test API keys for the Buildroot Gitlab instance?
- Do we have a spot we could run this script if someone was to develop it?


Matt