Regression in --build behaviour
See original GitHub issueHello,
I’ve noticed a small regression with the new version 0.20.
Before we used to be able to do this: conan test_package --build=outdated --build=Boost .
It meant “rebuild any outdated package and rebuild Boost anyway”.
Today I can only specify --build=outdated
(or missing
) if it’s the only --build
argument.
Else outdated
is interpreted as the name of a package.
Issue Analytics
- State:
- Created 7 years ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
Child regression: What it is and how you can support your little ...
Regression can vary, but in general, it is acting in a younger or needier way. You may see more temper tantrums, difficulty with...
Read more >Build the 'Right' Regression Suite Using Behavior Driven ...
I did a webinar for uTest on how to “Identify the 'right' regression suite using Behavior Driven Testing (BDT)”. The video from the...
Read more >Regression testing with 'behave' - Webinterpret Tech
Regression testing plays a crucial role in software development, especially when an application is based on microservices which are constantly ...
Read more >Why understanding Regression Defects benefits your Release ...
Understand key practices that can be deployed to prevent regression defects and benefit your release cycle.
Read more >What is Regression Testing? Definition, Tools, Method, and ...
Regression test can be performed on a new build when there is a significant change in the original functionality that too even in...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It seems I did another stupid mistake, sorry. Will probably release a minor tomorrow, I will try to add a fix for this.
Yeah, sorry, but the thing is that the --build behavior for special values like “missing” is not intended to be chained with package names patterns. Even if it wouldn’t fail, it won’t work as expected, so changing that would also be breaking behavior, so we are trapped anyway. If you check the PR, you will see that it is not small, so it will introduce risks of breaking other things, more time is needed to stabilize it.