-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Keep last_build_profile
in sync with profile requested in manifest
#1049
Conversation
|
||
# Check implicit profile when build is indirect | ||
|
||
run_alr("run") # Causes a default build |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if alr run
should keep the last build profile.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, it's probably more intuitive that way. I'll add that change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But in a follow-up patch
I'm stuck trying to fix the errors in the testsuite. For starters, it seems to depend on the compiler version: I don't get those with Ubuntu's 20 compiler (9.x) but I do with 11.2. And then, when I run the test steps by hand, I don't get the exception either. I guess something in the test environment is having something to do, but event trying to set up it by hand in advance is not working. Glad for any ideas on what to try. |
13f240b
to
cecfce8
Compare
cecfce8
to
27692ef
Compare
So after some trial and error, the only "simple" solution I could find was to manually manage and trigger the finalization of the new |
Fixes #1040