Hob has 3 main screens: 1) Image configuration 2) Selection of what to build 3) What to include in the images In stage 3, the image building process, when errors occur the image creation process is stopped, and the screen the user is pushed to is the 1st screen, forcing the user to completely start over from scratch and do the entirety of the build process again, hopefully after they have figured out and completely resolved the problem. ================ Expected result: ================ The expected interaction would be that Hob would do some sort of temporary state saving, including what packages have been selected for inclusion in the image, before attempting to build the image. Should there be errors, instead of kicking the user all the way back out to step 1, they should be brought back to the selection screen for step 3, along with the packages they had selected. This gives the user the ability to potentially remove the offending package from the image build, or gives the user the ability to resolve the image creation issue and proceed without having to completely restart. As an added advantage this and the state for step 2 (what packages to build) could conveniently be bundled allow for complete, reproducible builds, from within hob itself (not that this can't be done by building recipes and templates and such, but auto-building those from hob would make it slightly more user friendly)
Hello, Can you please add the following information: -host operating system -what environment did you use to run HOB? (poby build environment, build appliance) -poky version (or branch + commit) - if you used the build appliance, the version of poky relevant for it Note: you can also use the "Version" field.
Hello Corneliu, Thanks for helping out. Can you please try to reproduce this issue on current version of poky repository? Regards, Cristian
Please try to reproduce.
Andreea, please test this :)
Hello, There is nothing to test for this bug. The current implementation follows a design. Belen what do you think related to this approapch? Can you help me with this? Cristiana
I've attached the relevant designs from bug 2183 (see build-fail-flow.pdf). If the build fails, the 'edit image' button should bring you to the previous step (recipes screen or packages screen depending on when the failure occurs). The document says that recipes and packages selections should be remembered. This is exactly what is described in the "Expected results" section of this bug (as far as I can see). I believe the button label 'edit image' might have changed, but the behaviour should be exactly the same, and I am pretty sure it was behaving as designed when I verified bug 2183. If it's no longer working like this, we have a bug. I hope this helps. Belen (In reply to comment #5) > Hello, > > There is nothing to test for this bug. The current implementation follows a > design. Belen what do you think related to this approapch? Can you help me > with this? > > Cristiana
Created attachment 1103 [details] build-fail-flow.pdf
Andreea, can you please test it to see if it is working as designed? If it is working as design, I think we should close this bug. Thanks, Cristiana
Ok, I will test it :)
I have tested it and the current implementation follows the design described by Belen in the document attached (the recipes and packages selected are remembered when the build fails). Verified in master:d823759b4594143d522eae0b2a2498436a6dcb1e.
I set it to not a bug.
Verified.