From: Markus Volk <f_l_k@t-online.de>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [oe-core][PATCHv2] glib: update 2.74.6 -> 2.76.0
Date: Wed, 15 Mar 2023 16:06:57 +0100 [thread overview]
Message-ID: <LZHKRR.FOHLRDXQDV053@t-online.de> (raw)
In-Reply-To: <CANNYZj-k2EG4giH=zhXQywFhnVnpuaFtc4ngHgn8SV3w2kQhrw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1011 bytes --]
Am Mi, 15. Mär 2023 um 08:27:33 +0100 schrieb Alexander Kanavin
<alex.kanavin@gmail.com>:
> Guesswork is a fast track to frustration.
True :D But thats what always happens to me if I dont know enough and
can't find a way to reproduce.
Thanks to your hint on core-image-ptest-glib-2.0 I was able to
reproduce the issue. Running the test from /var/volatile/tmp didn't
solve the issue. But compared to core-image-ptest-glib-2.0 where /tmp
links to /var/tmp the tmpdir is handled by systemd tmp.mount in my
image and thus is not a symbolic link.
According to systemd ducumentation /var/tmp and /tmp are not the same
and are handled differently
<https://systemd.io/TEMPORARY_DIRECTORIES/>
Still I have no idea how this should be fixed or if the failed test
could maybe ignored but I was able to pass the tests in
core-image-ptest-glib-2.0 by removing the /tmp symlink and adding this
line to fstab:
tmpfs /tmp tmpfs defaults 0 0
After a reboot the tests completed successful
[-- Attachment #2: Type: text/html, Size: 1258 bytes --]
next prev parent reply other threads:[~2023-03-15 15:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 7:09 [oe-core][PATCHv2] glib: update 2.74.6 -> 2.76.0 Markus Volk
2023-03-15 7:27 ` Alexander Kanavin
2023-03-15 15:06 ` Markus Volk [this message]
2023-03-15 15:51 ` Alexander Kanavin
2023-03-15 17:21 ` Markus Volk
2023-03-15 17:46 ` Alexander Kanavin
2023-03-15 18:04 ` Markus Volk
2023-03-16 8:11 ` Alexander Kanavin
2023-03-17 5:58 ` Markus Volk
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=LZHKRR.FOHLRDXQDV053@t-online.de \
--to=f_l_k@t-online.de \
--cc=alex.kanavin@gmail.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.