All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Volk <f_l_k@t-online.de>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: Markus Volk <f_l_k@t-online.de>,
	Kai Kang <kai.kang@eng.windriver.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v2] adwaita-icon-theme: 43 -> 45.0
Date: Thu, 21 Sep 2023 17:51:14 +0200	[thread overview]
Message-ID: <EPEC1S.ET9N9UD2HEU43@t-online.de> (raw)
In-Reply-To: <CANNYZj-JBgC0NQGcjhV_h-EETBp0i59AhvpGVc8fHyxvU3bbxg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3761 bytes --]

On Thu, Sep 21 2023 at 05:36:13 PM +02:00:00, Alexander Kanavin 
<alex.kanavin@gmail.com> wrote:
> How did you trace it? That doesn't make sense given what the test
> does, and the task where diverge begins.

First I ran
oe-selftest -r 
sstatetests.SStateHashSameSigs2.test_sstate_allarch_samesigs
2023-09-21 17:43:06,946 - oe-selftest - INFO - 
----------------------------------------------------------------------
2023-09-21 17:43:06,946 - oe-selftest - INFO - Ran 1 test in 68.893s
2023-09-21 17:43:06,946 - oe-selftest - INFO - FAILED
2023-09-21 17:43:06,946 - oe-selftest - INFO -  (failures=1)
2023-09-21 17:43:11,370 - oe-selftest - INFO - RESULTS:
2023-09-21 17:43:11,370 - oe-selftest - INFO - RESULTS - 
sstatetests.SStateHashSameSigs2.test_sstate_allarch_samesigs: FAILED 
(66.80s)
2023-09-21 17:43:11,380 - oe-selftest - INFO - SUMMARY:
2023-09-21 17:43:11,380 - oe-selftest - INFO - oe-selftest () - Ran 1 
test in 68.896s
2023-09-21 17:43:11,380 - oe-selftest - INFO - oe-selftest - FAIL - 
Required tests failed (successes=0, skipped=0, failures=1, errors=0)

to verify that I can reproduce the issue.

Then I looked at the code and couldn't find any suspicious activity in 
meson so I thought it may be an internal problem.
 I removed all non-essential stuff from the recipe

SUMMARY = "GTK+ icon theme"
DESCRIPTION = "The Adwaita icon theme is the default icon theme of the 
GNOME desktop \
This package package contains an icon theme for Gtk+ 3 applications."
HOMEPAGE = "<https://gitlab.gnome.org/GNOME/adwaita-icon-theme>"
BUGTRACKER = 
"<https://gitlab.gnome.org/GNOME/adwaita-icon-theme/issues>"
SECTION = "x11/gnome"

LICENSE = "LGPL-3.0-only | CC-BY-SA-3.0"
LIC_FILES_CHKSUM = "file://COPYING;md5=c84cac88e46fc07647ea07e6c24eeb7c 
<file://copying;md5=c84cac88e46fc07647ea07e6c24eeb7c/> \
                    
file://COPYING_CCBYSA3;md5=96143d33de3a79321b1006c4e8ed07e7 
<file://copying_ccbysa3;md5=96143d33de3a79321b1006c4e8ed07e7/> \
                    
file://COPYING_LGPL;md5=e6a600fd5e1d9cbde2d983680233ad02 
<file://copying_lgpl;md5=e6a600fd5e1d9cbde2d983680233ad02/>"

GNOMEBASEBUILDCLASS = "meson"
GTKIC_VERSION = "4"
inherit  gnomebase pkgconfig gtk-icon-cache allarch

SRC_URI[archive.sha256sum] = 
"2442bfb06f4e6cc95bf6e2682fdff98fa5eddc688751b9d6215c623cb4e42ff1"
FILES:${PN}-doc = "${datadir}/licenses"
BBCLASSEXTEND = "native nativesdk"

but still the test failed. In the next step I excluded inherit allarch 
and the test succeeded

Looking at allarch.bbclass, this was the most suspicious part to me and 
first thing I tried was commenting out
#addhandler allarch_package_arch_handler

2023-09-21 17:08:57,046 - oe-selftest - INFO - Adding: "include 
selftest.inc" in /home/flk/poky/build-core-st/conf/local.conf
2023-09-21 17:08:57,046 - oe-selftest - INFO - Adding: "include 
bblayers.inc" in bblayers.conf
2023-09-21 17:08:57,046 - oe-selftest - INFO - 
test_sstate_allarch_samesigs 
(sstatetests.SStateHashSameSigs2.test_sstate_allarch_samesigs)
2023-09-21 17:10:02,922 - oe-selftest - INFO -  ... ok
2023-09-21 17:10:02,955 - oe-selftest - INFO - 
----------------------------------------------------------------------
2023-09-21 17:10:02,955 - oe-selftest - INFO - Ran 1 test in 68.008s
2023-09-21 17:10:02,955 - oe-selftest - INFO - OK
2023-09-21 17:10:07,700 - oe-selftest - INFO - RESULTS:
2023-09-21 17:10:07,700 - oe-selftest - INFO - RESULTS - 
sstatetests.SStateHashSameSigs2.test_sstate_allarch_samesigs: PASSED 
(65.88s)
2023-09-21 17:10:07,713 - oe-selftest - INFO - SUMMARY:
2023-09-21 17:10:07,713 - oe-selftest - INFO - oe-selftest () - Ran 1 
test in 68.008s
2023-09-21 17:10:07,713 - oe-selftest - INFO - oe-selftest - OK - All 
required tests passed (successes=1, skipped=0, failures=0, errors=0)


[-- Attachment #2: Type: text/html, Size: 4801 bytes --]

  reply	other threads:[~2023-09-21 15:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-21  6:47 [PATCH v2] adwaita-icon-theme: 43 -> 45.0 kai.kang
2023-09-21  7:06 ` Alexander Kanavin
2023-09-21  8:16   ` Kai
2023-09-21  8:34     ` [OE-core] " Markus Volk
2023-09-21  8:40       ` Alexander Kanavin
2023-09-21  9:45         ` Markus Volk
2023-09-21  9:51           ` Alexander Kanavin
2023-09-21 11:37             ` Markus Volk
2023-09-21 15:16             ` Markus Volk
2023-09-21 15:36               ` Alexander Kanavin
2023-09-21 15:51                 ` Markus Volk [this message]
2023-09-21 17:36                   ` Alexander Kanavin
2023-09-21 20:24                     ` Markus Volk
2023-09-21 20:35                       ` Alexander Kanavin
2023-09-22  3:23                         ` Markus Volk
2023-09-22  4:02                           ` Kai

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=EPEC1S.ET9N9UD2HEU43@t-online.de \
    --to=f_l_k@t-online.de \
    --cc=alex.kanavin@gmail.com \
    --cc=kai.kang@eng.windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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.