Created attachment 3966 [details] This log has all build attempts described on the steps. DESCRIPTION: When building a simple core-image-minimal you are able to download all artifacts on the build summary but if you latter on add a package, change bitbake variables to generate ipk or deb packages, all but the license manifest artifacts are NOT downloadable. STEPS TO REPRODUCE: 1. Start Toaster. 2. Click on new project button. 3. Enter a project name, select a release and click on create project. 4. Build an image recipe (ex: core-image-minimal) and wait until build finish. 5. Click on the built recipe. 6. From other artifacts tab click on a link to download at this point they are downloadable. 7. Go to the bitbake variables under the configuration tab and add openssh. then build core-image-minimal 8. Once build is done, Go to the bitbake variables under configuration tab and change the PACKAGE_CLASSES value to package_ipk and package_deb. 9. Build once again. 10. Added a layer meta-kernel created by me and added so that I could produce a failure and built once again. Of course it failed 11. At this point the core-image-minimal recipes that were successful we cannot download the artifacts. EXPECTED OUTCOME: On each recipe successfully built you can download the artifacts if you go to the build summary. ACTUAL OUTCOME: The following message appears: The build artifact you are trying to download does not exist. Back to previous page NOTE: I have attached all the build logs from the steps 4, 7, 9, 10 in that order separated by --------
I cannot yet replicate the error, even with the broken layer received from Libby. Possible Workaround: I will mention that I have observed in the past that if you build a target (like a file system) that produces certain artifacts, and then re-build with a differed target (like for eSDKs), the last build does not present a cumulative list of valid artifacts, and that you usually have to go back to the previous build to get those respective target links. That may be related here, where even though the last target failed you can still go back to previous build to get those working artifact links. I am moving this to YP-2.5 since we are at the end of M4, but I will see about pulling this into 2.4.1.
Bulk move from 4.99 or 0.00 to 5.99