* [U-Boot] Different build result for board "tbs2910" in gitlab-ci and azure
@ 2019-11-02 13:02 Bin Meng
2019-11-02 13:05 ` Tom Rini
2019-11-02 15:26 ` Igor Opaniuk
0 siblings, 2 replies; 6+ messages in thread
From: Bin Meng @ 2019-11-02 13:02 UTC (permalink / raw)
To: u-boot
Hi Tom,
When I build Simon's patches (the one I applied to u-boot-x86 today),
I noticed that the build results for board "tbs2910" in gitlab-ci and
azure are different.
On gitlab-ci [1], the build fails with error message:
arm: + tbs2910
+u-boot.imx exceeds file size limit:
+ limit: 0x5fc00 bytes
+ actual: 0x60c00 bytes
+ excess: 0x1000 bytes
+make[1]: *** [u-boot.imx] Error 1
+make[1]: *** Deleting file 'u-boot.imx'
+make: *** [sub-make] Error 2
125 331 1 /701 0:17:40 : tbs2910
On azure [2] job "Build the World imx6", the build succeeds:
arm: w+ tbs2910
+===================== WARNING ======================
+This board does not use CONFIG_DM_VIDEO Please update
+the board to use CONFIG_DM_VIDEO before the v2019.07 release.
+Failure to update by the deadline may result in board removal.
+See doc/driver-model/MIGRATION.txt for more info.
+====================================================
+CONFIG_OF_EMBED is enabled. This option should only
+be used for debugging purposes. Please use
+CONFIG_OF_SEPARATE for boards in mainline.
+See doc/README.fdt-control for more info.
6 24 0 /55 0:07:44 : tbs2910
I am not sure what might be the problem. Do you know what could be the cause?
[1] https://gitlab.denx.de/u-boot/custodians/u-boot-x86/-/jobs/26524
[2] https://dev.azure.com/bmeng/GitHub/_build/results?buildId=135
Regards,
Bin
^ permalink raw reply [flat|nested] 6+ messages in thread
* [U-Boot] Different build result for board "tbs2910" in gitlab-ci and azure
2019-11-02 13:02 [U-Boot] Different build result for board "tbs2910" in gitlab-ci and azure Bin Meng
@ 2019-11-02 13:05 ` Tom Rini
2019-11-02 13:17 ` Bin Meng
2019-11-02 15:26 ` Igor Opaniuk
1 sibling, 1 reply; 6+ messages in thread
From: Tom Rini @ 2019-11-02 13:05 UTC (permalink / raw)
To: u-boot
On Sat, Nov 02, 2019 at 09:02:36PM +0800, Bin Meng wrote:
> Hi Tom,
>
> When I build Simon's patches (the one I applied to u-boot-x86 today),
> I noticed that the build results for board "tbs2910" in gitlab-ci and
> azure are different.
>
> On gitlab-ci [1], the build fails with error message:
>
> arm: + tbs2910
> +u-boot.imx exceeds file size limit:
> + limit: 0x5fc00 bytes
> + actual: 0x60c00 bytes
> + excess: 0x1000 bytes
> +make[1]: *** [u-boot.imx] Error 1
> +make[1]: *** Deleting file 'u-boot.imx'
> +make: *** [sub-make] Error 2
>
> 125 331 1 /701 0:17:40 : tbs2910
>
> On azure [2] job "Build the World imx6", the build succeeds:
>
> arm: w+ tbs2910
> +===================== WARNING ======================
> +This board does not use CONFIG_DM_VIDEO Please update
> +the board to use CONFIG_DM_VIDEO before the v2019.07 release.
> +Failure to update by the deadline may result in board removal.
> +See doc/driver-model/MIGRATION.txt for more info.
> +====================================================
> +CONFIG_OF_EMBED is enabled. This option should only
> +be used for debugging purposes. Please use
> +CONFIG_OF_SEPARATE for boards in mainline.
> +See doc/README.fdt-control for more info.
>
> 6 24 0 /55 0:07:44 : tbs2910
>
> I am not sure what might be the problem. Do you know what could be the cause?
>
> [1] https://gitlab.denx.de/u-boot/custodians/u-boot-x86/-/jobs/26524
> [2] https://dev.azure.com/bmeng/GitHub/_build/results?buildId=135
I just noticed that as well. I suspect the answer is hard-coded source
paths in the binary and it's short enough on GitLab-CI
(/build/u-boot/u-boot) and Azure (/u/u-boot/u-boot/ ?) but not Travis.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20191102/8ceb0321/attachment.sig>
^ permalink raw reply [flat|nested] 6+ messages in thread
* [U-Boot] Different build result for board "tbs2910" in gitlab-ci and azure
2019-11-02 13:05 ` Tom Rini
@ 2019-11-02 13:17 ` Bin Meng
2019-11-02 14:08 ` Tom Rini
0 siblings, 1 reply; 6+ messages in thread
From: Bin Meng @ 2019-11-02 13:17 UTC (permalink / raw)
To: u-boot
Hi Tom,
On Sat, Nov 2, 2019 at 9:05 PM Tom Rini <trini@konsulko.com> wrote:
>
> On Sat, Nov 02, 2019 at 09:02:36PM +0800, Bin Meng wrote:
> > Hi Tom,
> >
> > When I build Simon's patches (the one I applied to u-boot-x86 today),
> > I noticed that the build results for board "tbs2910" in gitlab-ci and
> > azure are different.
> >
> > On gitlab-ci [1], the build fails with error message:
> >
> > arm: + tbs2910
> > +u-boot.imx exceeds file size limit:
> > + limit: 0x5fc00 bytes
> > + actual: 0x60c00 bytes
> > + excess: 0x1000 bytes
> > +make[1]: *** [u-boot.imx] Error 1
> > +make[1]: *** Deleting file 'u-boot.imx'
> > +make: *** [sub-make] Error 2
> >
> > 125 331 1 /701 0:17:40 : tbs2910
> >
> > On azure [2] job "Build the World imx6", the build succeeds:
> >
> > arm: w+ tbs2910
> > +===================== WARNING ======================
> > +This board does not use CONFIG_DM_VIDEO Please update
> > +the board to use CONFIG_DM_VIDEO before the v2019.07 release.
> > +Failure to update by the deadline may result in board removal.
> > +See doc/driver-model/MIGRATION.txt for more info.
> > +====================================================
> > +CONFIG_OF_EMBED is enabled. This option should only
> > +be used for debugging purposes. Please use
> > +CONFIG_OF_SEPARATE for boards in mainline.
> > +See doc/README.fdt-control for more info.
> >
> > 6 24 0 /55 0:07:44 : tbs2910
> >
> > I am not sure what might be the problem. Do you know what could be the cause?
> >
> > [1] https://gitlab.denx.de/u-boot/custodians/u-boot-x86/-/jobs/26524
> > [2] https://dev.azure.com/bmeng/GitHub/_build/results?buildId=135
>
> I just noticed that as well. I suspect the answer is hard-coded source
> paths in the binary and it's short enough on GitLab-CI
> (/build/u-boot/u-boot) and Azure (/u/u-boot/u-boot/ ?) but not Travis.
So right now both gitlab-ci and travis fails with this board. Azure is
using /u as the working directory (short enough).
Regards,
Bin
^ permalink raw reply [flat|nested] 6+ messages in thread
* [U-Boot] Different build result for board "tbs2910" in gitlab-ci and azure
2019-11-02 13:17 ` Bin Meng
@ 2019-11-02 14:08 ` Tom Rini
0 siblings, 0 replies; 6+ messages in thread
From: Tom Rini @ 2019-11-02 14:08 UTC (permalink / raw)
To: u-boot
On Sat, Nov 02, 2019 at 09:17:32PM +0800, Bin Meng wrote:
> Hi Tom,
>
> On Sat, Nov 2, 2019 at 9:05 PM Tom Rini <trini@konsulko.com> wrote:
> >
> > On Sat, Nov 02, 2019 at 09:02:36PM +0800, Bin Meng wrote:
> > > Hi Tom,
> > >
> > > When I build Simon's patches (the one I applied to u-boot-x86 today),
> > > I noticed that the build results for board "tbs2910" in gitlab-ci and
> > > azure are different.
> > >
> > > On gitlab-ci [1], the build fails with error message:
> > >
> > > arm: + tbs2910
> > > +u-boot.imx exceeds file size limit:
> > > + limit: 0x5fc00 bytes
> > > + actual: 0x60c00 bytes
> > > + excess: 0x1000 bytes
> > > +make[1]: *** [u-boot.imx] Error 1
> > > +make[1]: *** Deleting file 'u-boot.imx'
> > > +make: *** [sub-make] Error 2
> > >
> > > 125 331 1 /701 0:17:40 : tbs2910
> > >
> > > On azure [2] job "Build the World imx6", the build succeeds:
> > >
> > > arm: w+ tbs2910
> > > +===================== WARNING ======================
> > > +This board does not use CONFIG_DM_VIDEO Please update
> > > +the board to use CONFIG_DM_VIDEO before the v2019.07 release.
> > > +Failure to update by the deadline may result in board removal.
> > > +See doc/driver-model/MIGRATION.txt for more info.
> > > +====================================================
> > > +CONFIG_OF_EMBED is enabled. This option should only
> > > +be used for debugging purposes. Please use
> > > +CONFIG_OF_SEPARATE for boards in mainline.
> > > +See doc/README.fdt-control for more info.
> > >
> > > 6 24 0 /55 0:07:44 : tbs2910
> > >
> > > I am not sure what might be the problem. Do you know what could be the cause?
> > >
> > > [1] https://gitlab.denx.de/u-boot/custodians/u-boot-x86/-/jobs/26524
> > > [2] https://dev.azure.com/bmeng/GitHub/_build/results?buildId=135
> >
> > I just noticed that as well. I suspect the answer is hard-coded source
> > paths in the binary and it's short enough on GitLab-CI
> > (/build/u-boot/u-boot) and Azure (/u/u-boot/u-boot/ ?) but not Travis.
>
> So right now both gitlab-ci and travis fails with this board. Azure is
> using /u as the working directory (short enough).
GitLab is close? https://gitlab.denx.de/u-boot/u-boot/pipelines/1191
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20191102/61e9219d/attachment.sig>
^ permalink raw reply [flat|nested] 6+ messages in thread
* [U-Boot] Different build result for board "tbs2910" in gitlab-ci and azure
2019-11-02 13:02 [U-Boot] Different build result for board "tbs2910" in gitlab-ci and azure Bin Meng
2019-11-02 13:05 ` Tom Rini
@ 2019-11-02 15:26 ` Igor Opaniuk
2019-11-02 23:07 ` Bin Meng
1 sibling, 1 reply; 6+ messages in thread
From: Igor Opaniuk @ 2019-11-02 15:26 UTC (permalink / raw)
To: u-boot
Hi Bin,
On Sat, Nov 2, 2019 at 3:03 PM Bin Meng <bmeng.cn@gmail.com> wrote:
>
> Hi Tom,
>
> When I build Simon's patches (the one I applied to u-boot-x86 today),
> I noticed that the build results for board "tbs2910" in gitlab-ci and
> azure are different.
>
> On gitlab-ci [1], the build fails with error message:
>
> arm: + tbs2910
> +u-boot.imx exceeds file size limit:
> + limit: 0x5fc00 bytes
> + actual: 0x60c00 bytes
> + excess: 0x1000 bytes
> +make[1]: *** [u-boot.imx] Error 1
> +make[1]: *** Deleting file 'u-boot.imx'
> +make: *** [sub-make] Error 2
>
> 125 331 1 /701 0:17:40 : tbs2910
>
> On azure [2] job "Build the World imx6", the build succeeds:
>
> arm: w+ tbs2910
> +===================== WARNING ======================
> +This board does not use CONFIG_DM_VIDEO Please update
> +the board to use CONFIG_DM_VIDEO before the v2019.07 release.
> +Failure to update by the deadline may result in board removal.
> +See doc/driver-model/MIGRATION.txt for more info.
> +====================================================
> +CONFIG_OF_EMBED is enabled. This option should only
> +be used for debugging purposes. Please use
> +CONFIG_OF_SEPARATE for boards in mainline.
> +See doc/README.fdt-control for more info.
>
> 6 24 0 /55 0:07:44 : tbs2910
>
> I am not sure what might be the problem. Do you know what could be the cause?
>
> [1] https://gitlab.denx.de/u-boot/custodians/u-boot-x86/-/jobs/26524
> [2] https://dev.azure.com/bmeng/GitHub/_build/results?buildId=135
>
> Regards,
> Bin
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> https://lists.denx.de/listinfo/u-boot
That is toolchain version specific issue(there was a discussion about
this board [1]).
On Azure gcc-9.1.0-2 is used
In gitlab-ci - gcc-7.3.0.
[1] https://patchwork.ozlabs.org/patch/1180025/
--
Best regards - Freundliche Grüsse - Meilleures salutations
Igor Opaniuk
mailto: igor.opaniuk at gmail.com
skype: igor.opanyuk
+380 (93) 836 40 67
http://ua.linkedin.com/in/iopaniuk
^ permalink raw reply [flat|nested] 6+ messages in thread
* [U-Boot] Different build result for board "tbs2910" in gitlab-ci and azure
2019-11-02 15:26 ` Igor Opaniuk
@ 2019-11-02 23:07 ` Bin Meng
0 siblings, 0 replies; 6+ messages in thread
From: Bin Meng @ 2019-11-02 23:07 UTC (permalink / raw)
To: u-boot
Hi Igor,
On Sat, Nov 2, 2019 at 11:26 PM Igor Opaniuk <igor.opaniuk@gmail.com> wrote:
>
> Hi Bin,
>
> On Sat, Nov 2, 2019 at 3:03 PM Bin Meng <bmeng.cn@gmail.com> wrote:
> >
> > Hi Tom,
> >
> > When I build Simon's patches (the one I applied to u-boot-x86 today),
> > I noticed that the build results for board "tbs2910" in gitlab-ci and
> > azure are different.
> >
> > On gitlab-ci [1], the build fails with error message:
> >
> > arm: + tbs2910
> > +u-boot.imx exceeds file size limit:
> > + limit: 0x5fc00 bytes
> > + actual: 0x60c00 bytes
> > + excess: 0x1000 bytes
> > +make[1]: *** [u-boot.imx] Error 1
> > +make[1]: *** Deleting file 'u-boot.imx'
> > +make: *** [sub-make] Error 2
> >
> > 125 331 1 /701 0:17:40 : tbs2910
> >
> > On azure [2] job "Build the World imx6", the build succeeds:
> >
> > arm: w+ tbs2910
> > +===================== WARNING ======================
> > +This board does not use CONFIG_DM_VIDEO Please update
> > +the board to use CONFIG_DM_VIDEO before the v2019.07 release.
> > +Failure to update by the deadline may result in board removal.
> > +See doc/driver-model/MIGRATION.txt for more info.
> > +====================================================
> > +CONFIG_OF_EMBED is enabled. This option should only
> > +be used for debugging purposes. Please use
> > +CONFIG_OF_SEPARATE for boards in mainline.
> > +See doc/README.fdt-control for more info.
> >
> > 6 24 0 /55 0:07:44 : tbs2910
> >
> > I am not sure what might be the problem. Do you know what could be the cause?
> >
> > [1] https://gitlab.denx.de/u-boot/custodians/u-boot-x86/-/jobs/26524
> > [2] https://dev.azure.com/bmeng/GitHub/_build/results?buildId=135
> >
> > Regards,
> > Bin
> > _______________________________________________
> > U-Boot mailing list
> > U-Boot at lists.denx.de
> > https://lists.denx.de/listinfo/u-boot
>
> That is toolchain version specific issue(there was a discussion about
> this board [1]).
>
Thanks for checking.
> On Azure gcc-9.1.0-2 is used
> In gitlab-ci - gcc-7.3.0.
>
But I don't understand why this is caused by GCC version. Azure is
using the same CI runner docker image used by gitlab-ci so compiler
version should be the same.
> [1] https://patchwork.ozlabs.org/patch/1180025/
>
Regards,
Bin
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2019-11-02 23:07 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-11-02 13:02 [U-Boot] Different build result for board "tbs2910" in gitlab-ci and azure Bin Meng
2019-11-02 13:05 ` Tom Rini
2019-11-02 13:17 ` Bin Meng
2019-11-02 14:08 ` Tom Rini
2019-11-02 15:26 ` Igor Opaniuk
2019-11-02 23:07 ` Bin Meng
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.