| Summary: | [Autobuilder] No dtb file for mpc8315e-rdb in directory with 1.3 M2 RC1 | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] Kernel | Reporter: | Yi Zhao <yi.zhao> |
| Component: | linux-yocto | Assignee: | Beth Flanagan <elizabeth.flanagan> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | bruce.ashfield, elizabeth.flanagan, infras.ab.watcher, Infras.watcher, jiajun.xu, laurentiu.serban, liang.li2, msm-oss, sgw, yi.zhao |
| Version: | 1.3 | ||
| Target Milestone: | 1.3 M3 | ||
| Hardware: | mpc8315e-rdb | ||
| OS: | ppc | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Yi Zhao
2012-07-16 09:14:19 UTC
I'm pretty sure that this is not an autobuilder bug: The artifacts are published as such: cp -Rd *%s* %s/machines/qemu/%s Which means if the file existed, it would have been copied. May I know what's the problem here? I tried to build virtual/kernel with eb0cb7e8234f5d2e5623406e9660be91cf52f65, and following images can be generated successfully. $ ls -l tmp/deploy/images/ total 46376 -rw-r--r-- 1 b19537 b19537 43660746 Aug 7 05:06 modules-3.4.4-yocto-standard-r4.0-mpc8315e-rdb.tgz -rw-r--r-- 1 b19537 b19537 294 Aug 7 05:06 README_-_DO_NOT_DELETE_FILES_IN_THIS_DIRECTORY.txt lrwxrwxrwx 1 b19537 b19537 138 Aug 7 05:06 uImage -> uImage-3.4.4+git1+a8cf77018b0faa0d29f1483ff4e5a2034dc8edd5_1+47d3076aa7e2a640a1dab8d663529a784709f697-r4.0-mpc8315e-rdb-20120807092932.bin -rw-r--r-- 1 b19537 b19537 3778536 Aug 7 05:06 uImage-3.4.4+git1+a8cf77018b0faa0d29f1483ff4e5a2034dc8edd5_1+47d3076aa7e2a640a1dab8d663529a784709f697-r4.0-mpc8315e-rdb-20120807092932.bin -rw-r--r-- 1 b19537 b19537 21042 Aug 7 05:06 uImage-3.4.4+git1+a8cf77018b0faa0d29f1483ff4e5a2034dc8edd5_1+47d3076aa7e2a640a1dab8d663529a784709f697-r4.0-mpc8315erdb-20120807092932.dtb lrwxrwxrwx 1 b19537 b19537 138 Aug 7 05:06 uImage-mpc8315e-rdb.bin -> uImage-3.4.4+git1+a8cf77018b0faa0d29f1483ff4e5a2034dc8edd5_1+47d3076aa7e2a640a1dab8d663529a784709f697-r4.0-mpc8315e-rdb-20120807092932.bin lrwxrwxrwx 1 b19537 b19537 137 Aug 7 05:06 uImage-mpc8315erdb.dtb -> uImage-3.4.4+git1+a8cf77018b0faa0d29f1483ff4e5a2034dc8edd5_1+47d3076aa7e2a640a1dab8d663529a784709f697-r4.0-mpc8315erdb-20120807092932.dtb (In reply to comment #2) > May I know what's the problem here? > The problem is: our autobuilder will copy all artifacts to a publish directory when building complete. But now the dtb file doesn't copy. The root cause is the dtb file name is not correct. Please see the autobuilder log : http://autobuilder.yoctoproject.org:8010/builders/nightly-ppc/builds/516/steps/shell_50/logs/stdio The first line is: sh -c 'cp -Rd *mpc8315e-rdb* /srv/www/vhosts/autobuilder.yoctoproject.org/pub/nightly/20120807-1/machines/mpc8315e-rdb' It will copy all *mpc8315e-rdb* file to the directory. But the dtb file name is "uImage-mpc8315erdb.dtb", missing "-" between "mpc8315e" and "rdb". So it doesn't copy. Please modify the dtb file name like this : uImage-mpc8315e-rdb.dtb Thanks > I tried to build virtual/kernel with > eb0cb7e8234f5d2e5623406e9660be91cf52f65, and following images can be > generated successfully. > > $ ls -l tmp/deploy/images/ > total 46376 > -rw-r--r-- 1 b19537 b19537 43660746 Aug 7 05:06 > modules-3.4.4-yocto-standard-r4.0-mpc8315e-rdb.tgz > -rw-r--r-- 1 b19537 b19537 294 Aug 7 05:06 > README_-_DO_NOT_DELETE_FILES_IN_THIS_DIRECTORY.txt > lrwxrwxrwx 1 b19537 b19537 138 Aug 7 05:06 uImage -> > uImage-3.4. > 4+git1+a8cf77018b0faa0d29f1483ff4e5a2034dc8edd5_1+47d3076aa7e2a640a1dab8d6635 > 29a784709f697-r4.0-mpc8315e-rdb-20120807092932.bin > -rw-r--r-- 1 b19537 b19537 3778536 Aug 7 05:06 > uImage-3.4. > 4+git1+a8cf77018b0faa0d29f1483ff4e5a2034dc8edd5_1+47d3076aa7e2a640a1dab8d6635 > 29a784709f697-r4.0-mpc8315e-rdb-20120807092932.bin > -rw-r--r-- 1 b19537 b19537 21042 Aug 7 05:06 > uImage-3.4. > 4+git1+a8cf77018b0faa0d29f1483ff4e5a2034dc8edd5_1+47d3076aa7e2a640a1dab8d6635 > 29a784709f697-r4.0-mpc8315erdb-20120807092932.dtb > lrwxrwxrwx 1 b19537 b19537 138 Aug 7 05:06 uImage-mpc8315e-rdb.bin -> > uImage-3.4. > 4+git1+a8cf77018b0faa0d29f1483ff4e5a2034dc8edd5_1+47d3076aa7e2a640a1dab8d6635 > 29a784709f697-r4.0-mpc8315e-rdb-20120807092932.bin > lrwxrwxrwx 1 b19537 b19537 137 Aug 7 05:06 uImage-mpc8315erdb.dtb -> > uImage-3.4. > 4+git1+a8cf77018b0faa0d29f1483ff4e5a2034dc8edd5_1+47d3076aa7e2a640a1dab8d6635 > 29a784709f697-r4.0-mpc8315erdb-20120807092932.dtb Ok, relooking at this and have a fix pending for the AB. I don't like the fact that names are getting changed like this because it has the possibility of being a real nightmare to maintain from the AB. Just for the record the file name changed because it switched to basing the name off what's in the kernel tree - this should not change again... $ find arch/powerpc/boot/dts/ | grep mpc8315 arch/powerpc/boot/dts/mpc8315erdb.dts IMO, This makes a sense because now we can have many device tree's and the kernel names are usually appropriate to differentiate. Verified. |