From: Tom Rini <trini@konsulko.com>
To: Safae Ouajih <souajih@baylibre.com>
Cc: sjg@chromium.org, u-boot@lists.denx.de, sean.anderson@seco.com,
r.stratiienko@gmail.com, mkorpershoek@baylibre.com,
glaroque@baylibre.com, khilman@baylibre.com
Subject: Re: [PATCH v3 18/19] test/py: android: extend abootimg test
Date: Mon, 6 Mar 2023 15:07:42 -0500 [thread overview]
Message-ID: <20230306200742.GD968799@bill-the-cat> (raw)
In-Reply-To: <fc19de68-ecbd-d8f9-2678-16402ff6d6b4@baylibre.com>
[-- Attachment #1: Type: text/plain, Size: 2906 bytes --]
On Mon, Mar 06, 2023 at 08:49:02PM +0100, Safae Ouajih wrote:
>
> On 27/02/2023 15:18, Tom Rini wrote:
> > On Mon, Feb 27, 2023 at 03:15:31PM +0100, Safae Ouajih wrote:
> > > On 07/02/2023 20:02, Tom Rini wrote:
> > > > On Mon, Feb 06, 2023 at 12:50:20AM +0100, Safae Ouajih wrote:
> > > >
> > > > > test_abootimg is extended to include the testing of boot images
> > > > > version 4. For this, boot.img and vendor_boot.img have been
> > > > > generated using mkbootimg tool with setting the header
> > > > > version to 4.
> > > > >
> > > > > This tests:
> > > > > - Getting the header version using abootimg
> > > > > - Extracting the load address of the dtb
> > > > > - Extracting the dtb start address in RAM
> > > > >
> > > > > Running test:
> > > > > $ ./test/py/test.py --bd sandbox --build -k test_abootimg
> > > > >
> > > > > Signed-off-by: Safae Ouajih <souajih@baylibre.com>
> > > > > Reviewed-by: Simon Glass <sjg@chromium.org>
> > > > > ---
> > > > > test/py/tests/test_android/test_abootimg.py | 136 ++++++++++++++++++--
> > > > > 1 file changed, 123 insertions(+), 13 deletions(-)
> > > > Alright, so I don't know where the failure starts, exactly. And to make
> > > > testing this easier, there's currently the
> > > > trini/u-boot-gitlab-ci-runner:jammy-20230126-07Feb2023 container you can
> > > > use to replicate my problem. The problem is that while this test passes
> > > > in CI, with GCC, with Clang it fails, consistently:
> > > > https://source.denx.de/u-boot/u-boot/-/jobs/572239#L284
> > > > and I'm not quite sure why. I hope that building sandbox with clang and
> > > > also just trying these features out interactively will fail too, and so
> > > > debugging this will be less of a problem.
> > > >
> > > Hello Tom,
> > >
> > > I have investigated this issue, clang has a strange behavior in:
> > >
> > > * abootimg_get_dtb_load_addr() : cmd/abootimg.c
> > > * android_image_get_dtb_by_index() : boot/image-android.c
> > >
> > > That is probably linked to some sort of optimization clang does.
> > >
> > > However, The fail is not reproducible using clang-15 and clang-16 and also
> > > not reproducible when turning off clang optimizations.
> > >
> > > I suggest using clang-15 to run the test or I can remove all optimizations
> > >
> > > on the related functions if clang-14 is used.
> > Thanks for investigating. I see that 15 is now considered stable, so
> > I'll update the next branch for that, then re-take this series.
> >
>
> Hello Tom,
>
> Thank you.
>
> I am a bit confused, do you mean that you will apply this series after
> clang-15 update?
Yes, and the series to move CI to clang-15 is currently stuck on some
pytest (real) failures that need to be resolved. But I would expect this
to all be resolved in time for this series here to be included in
v2023.07.
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2023-03-06 20:07 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-05 23:50 [PATCH v3 00/19] Support android boot image v3/v4 Safae Ouajih
2023-02-05 23:50 ` [PATCH v3 01/19] android: boot: rename andr_img_hdr -> andr_boot_img_hdr_v0 Safae Ouajih
2023-02-05 23:50 ` [PATCH v3 02/19] android: boot: support vendor boot image in abootimg Safae Ouajih
2023-02-05 23:50 ` [PATCH v3 03/19] android: boot: replace android_image_check_header Safae Ouajih
2023-02-05 23:50 ` [PATCH v3 04/19] android: boot: add boot image header v3 and v4 structures Safae Ouajih
2023-02-05 23:50 ` [PATCH v3 05/19] android: boot: kcomp: support andr_image_data Safae Ouajih
2023-02-05 23:50 ` [PATCH v3 06/19] android: boot: move to andr_image_data structure Safae Ouajih
2023-02-07 4:02 ` Simon Glass
2023-02-09 16:30 ` Safae Ouajih
2023-02-09 14:26 ` Mattijs Korpershoek
2023-02-09 16:49 ` Safae Ouajih
2023-02-05 23:50 ` [PATCH v3 07/19] android: boot: content print is not supported for v3, v4 header version Safae Ouajih
2023-02-05 23:50 ` [PATCH v3 08/19] android: boot: boot image header v3, v4 do not support recovery DTBO Safae Ouajih
2023-02-05 23:50 ` [PATCH v3 09/19] android: boot: add vendor boot image to prepare for v3, v4 support Safae Ouajih
2023-02-07 4:02 ` [PATCH v3 09/19] android: boot: add vendor boot image to prepare for v3,v4 support Simon Glass
2023-02-09 17:01 ` Safae Ouajih
2023-02-09 14:29 ` Mattijs Korpershoek
2023-02-09 14:30 ` Mattijs Korpershoek
2023-02-05 23:50 ` [PATCH v3 10/19] android: boot: update android_image_get_data to support v3, v4 Safae Ouajih
2023-02-09 14:32 ` [PATCH v3 10/19] android: boot: update android_image_get_data to support v3,v4 Mattijs Korpershoek
2023-02-05 23:50 ` [PATCH v3 11/19] android: boot: ramdisk: support vendor ramdisk Safae Ouajih
2023-02-09 14:35 ` Mattijs Korpershoek
2023-04-07 8:56 ` Roman Stratiienko
2023-04-07 13:16 ` Mattijs Korpershoek
2023-02-05 23:50 ` [PATCH v3 12/19] android: boot: support extra command line Safae Ouajih
2023-02-05 23:50 ` [PATCH v3 13/19] android: boot: update android_image_get_dtb_img_addr to support v3, v4 Safae Ouajih
2023-02-05 23:50 ` [PATCH v3 14/19] drivers: fastboot: zImage flashing is not supported for " Safae Ouajih
2023-02-09 14:38 ` [PATCH v3 14/19] drivers: fastboot: zImage flashing is not supported for v3,v4 Mattijs Korpershoek
2023-02-05 23:50 ` [PATCH v3 15/19] android: boot: support boot image header version 3 and 4 Safae Ouajih
2023-02-09 14:46 ` Mattijs Korpershoek
2023-02-05 23:50 ` [PATCH v3 16/19] android: boot: support bootconfig Safae Ouajih
2023-02-05 23:50 ` [PATCH v3 17/19] doc: android: add documentation for v3, v4 boot image header Safae Ouajih
2023-02-07 4:02 ` [PATCH v3 17/19] doc: android: add documentation for v3,v4 " Simon Glass
2023-02-08 8:54 ` Mattijs Korpershoek
2023-02-05 23:50 ` [PATCH v3 18/19] test/py: android: extend abootimg test Safae Ouajih
2023-02-07 19:02 ` Tom Rini
2023-02-09 16:52 ` Safae Ouajih
2023-02-27 14:15 ` Safae Ouajih
2023-02-27 14:18 ` Tom Rini
2023-03-06 19:49 ` Safae Ouajih
2023-03-06 20:07 ` Tom Rini [this message]
2023-02-05 23:50 ` [PATCH v3 19/19] Dockerfile: add mkbootimg tool Safae Ouajih
2023-02-09 14:08 ` [PATCH v3 00/19] Support android boot image v3/v4 Mattijs Korpershoek
2023-04-05 14:41 ` Tom Rini
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=20230306200742.GD968799@bill-the-cat \
--to=trini@konsulko.com \
--cc=glaroque@baylibre.com \
--cc=khilman@baylibre.com \
--cc=mkorpershoek@baylibre.com \
--cc=r.stratiienko@gmail.com \
--cc=sean.anderson@seco.com \
--cc=sjg@chromium.org \
--cc=souajih@baylibre.com \
--cc=u-boot@lists.denx.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 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.