After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 772208 - In Universal builds, post-build "shell" command goes to wrong place
In Universal builds, post-build "shell" command goes to wrong place
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: cerbero
git master
Other Linux
: Normal blocker
: 1.10.0
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2016-09-29 21:30 UTC by Olivier Crête
Modified: 2016-10-14 16:06 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Put the arch in the exception to run shell in the right place (5.05 KB, patch)
2016-09-29 21:31 UTC, Olivier Crête
committed Details | Review
Go to the right directory on failed Universal builds (2.40 KB, patch)
2016-09-29 21:31 UTC, Olivier Crête
rejected Details | Review

Description Olivier Crête 2016-09-29 21:30:02 UTC
If a universal build and one selects "0" to get a shell, it goes to the first recipe in the list instead of to the one that failed.

I'm attaching two possible patches to fix it, the first adds the architecture to the exception and bubbles it up that way. The second just sets the current arch on the Universal recipe so that getattr afterwards are redirected to it.. I'm not sure at all which one is better although I tend towrds the exception based one.
Comment 1 Olivier Crête 2016-09-29 21:31:17 UTC
Created attachment 336551 [details] [review]
Put the arch in the exception to run shell in the right place
Comment 2 Olivier Crête 2016-09-29 21:31:28 UTC
Created attachment 336552 [details] [review]
Go to the right directory on failed Universal builds

Instead of picking a random architecture, instead save
the failed one and use it.
Comment 3 Arun Raghavan 2016-09-30 07:02:41 UTC
I think embedding the arch in the exception is cleaner than mutable state on the recipe. Only reason to go with the latter is if we foresee needing the current_arch information in any other scenario.
Comment 4 Olivier Crête 2016-10-14 16:05:18 UTC
Review of attachment 336551 [details] [review]:

Merged as:

commit a0a134fdf6aadc7d527600b1edc4563b947f07eb
Author: Olivier Crête <olivier.crete@collabora.com>
Date:   Thu Sep 29 17:19:44 2016 -0400

    Go to the right directory on failed Universal builds
    
    Instead of picking a random architecture, instead save the failed on in
    the exception and use it to go to the right directory.
    
    https://bugzilla.gnome.org/show_bug.cgi?id=772208
Comment 5 Olivier Crête 2016-10-14 16:05:39 UTC
Review of attachment 336552 [details] [review]:

It's cleaner in an exception, so use the other one