| Summary: | Incremental build in Docker fails with Invalid cross-device link error | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Meta-yocto | Reporter: | Devendra Tewari <devendra.tewari> | ||||||
| Component: | meta-yocto | Assignee: | Devendra Tewari <devendra.tewari> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | Medium | CC: | devendra.tewari, poky.bs.watcher, poky.watcher, randy.macleod | ||||||
| Version: | unspecified | ||||||||
| Target Milestone: | 3.4 | ||||||||
| Hardware: | x86 | ||||||||
| OS: | Multiple | ||||||||
| Whiteboard: | |||||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||||
| Verified: | Documentation change: | Don't know | |||||||
| Attachments: |
|
||||||||
|
Description
Devendra Tewari
2021-03-11 18:24:32 UTC
Created attachment 4776 [details]
Use shutil.move instead of os.rename
The rename is faster but we could trap the error and fall-back to the move if the host/filesystem has an error. Can you send a patch? According to documentation, shutil.move falls back to os.rename when source and destination are on the same filesystem, but trapping error with os.rename and trying shutil.move looks safer. I'll attach a patch. Created attachment 4777 [details]
Use shutil.move when os.rename fails
Thanks Devendra, Are you able to send he patch to the oe-core email list, like this: git send-email -M -1 --to="openembedded-core@lists.openembedded.org" See: https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded#Sending_using_git-send-email Thanks, Randy. I've submitted the patch via git send-email. Hello Devendra, I didn't see the email. Did I miss it? Did it get merged? ../Randy Sorry, looks like I didn't have an smtp server setup and the mail didn't go out. Sent it out again, and confirmed it got sent at https://lists.openembedded.org/g/openembedded-core/topic/patch_use_shutil_move_when/81698791. Patches have been integrated. |