Hello Yoann,

> Where does this FileNotFoundError happen in scarthgap?
> os.symlink() has no problem creating a symlink to a non existing file and I 
> don't see
> where we would open bootlog (we do open bootlog in wrynose/master though). Are
> you sure we need this fix on scarthgap? Or maybe we need something else?

You are right, thanks for catching that.

In scarthgap this does not fail in os.symlink() itself: it creates a
dangling symlink when the base bootlog is missing. The FileNotFoundError
then happens later in our CI pipeline when collecting/copying the oeqa
log artifacts.

So, the issue is narrower than the v2 commit message says: the patch
avoids creating a misleading dangling bootlog symlink in the result log
directory. If that still sounds acceptable for scarthgap, I can send a
v3 with the commit message updated accordingly and without implying that
testimage itself raises FileNotFoundError.

Regards,
Peter

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#245760): 
https://lists.openembedded.org/g/openembedded-core/message/245760
Mute This Topic: https://lists.openembedded.org/mt/121133618/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to