+1 to Nico's comment. A simple ninja to build or ninja check to build + unit tests is sufficient.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Nov 27 2019
Nov 26 2019
Nov 25 2019
I already did this prior to you red'ing the diff.
- Use assert_debug_log instead of time.sleep
- Refactor to prevent needing to jump around the code just to read and understand everything.
- Add MSG_CMPCTBLOCK to messages.py
- Improve perf from ~25 seconds to ~6 seconds
Fix extension
Removed change to stackexchange link
Change type
Rebase
Nov 23 2019
Nov 22 2019
Address feedback
- Added some basic unit tests
- int -> size_t
- Funny how forcing yourself to write some tests reveals subtle design flaws. Moved ParseKeyValue() out of ArgsManager because it doesn't actually belong in that class. I still kept the implementations close to make backporting easier.
Rebase + rename build option
In D4496#108676, @deadalnix wrote:Considering there are still many backports to do in there, I don't think this is very wise to go there.
Rebase
Added error message + minor refactor
Nov 21 2019
The build plan is ambiguous, so I trust you did both make and ninja
Nov 20 2019
Removed envp
Bail instead of resetting local commits.
Also fixed some bugs.
Fixed shellcheck warning
Fix origin/${BRANCH} -> ${REMOTE}/${BRANCH} so that any remote and branch name combination can work.
Use ForceSetArg() instead of ParseParameters()
In D4474#108521, @deadalnix wrote:What about using this: https://www.boost.org/doc/libs/1_71_0/libs/test/doc/html/boost_test/runtime_config/custom_command_line_arguments.html ?
You can then setup gArgs as you want it to in BasicTestingSetup.
A release has gone out, but the fix wasn't included. I'm urging them to give us an actual ETA, because we need to land this soon.
Added all boost runtime params to the whitelist