Kconfiglib.git/tests, branch v2.5.0Fork of https://github.com/zephyrproject-rtos/Kconfiglib.githttps://git.mcdonnell.dev/Kconfiglib.git/atom?h=v2.5.02018-01-20T04:19:42ZGet rid of _next_help_line()2018-01-20T04:19:42ZUlf Magnussonulfalizer@gmail.com2018-01-20T04:05:49Zurn:sha1:707204ac4a5539c9b4d4875d12fec340ba95c1a2
Speeds things up a bit further.
Rework the unget handling to save the ungotten line directly instead of
using a flag.
Add some help texts to tests/Klocation to make sure the line number is
updated properly for those.
Detect recursive 'source' and print backtrace2018-01-17T12:53:30ZUlf Magnussonulfalizer@gmail.com2018-01-17T11:56:13Zurn:sha1:7dc5b74229e83876307082712162d48e3124e10b
Easier to debug than a RecursionError.
Point out in the exception message that a common cause is environment
variables not being set correctly.
Don't write out 'option env' symbols to C header2018-01-05T20:38:57ZUlf Magnussonulfalizer@gmail.com2018-01-05T19:37:00Zurn:sha1:5d693b2e66451aedfd694ffde4dba7d4b74afa46
Oversight. SYMBOL_AUTO (env_var) being set indirectly clears
SYMBOL_WRITE (_write_to_conf) in sym_calc_value(). The .config case was
already fine due to an explicit env_var check.
Even non-visible env. symbols ended up in the header, due to
'option env' internally adding a default.
Disallow user values altogether on 'option env' symbols, even if
specified manually. This matches the C implementation. Add a warning
too.
Remove unused test files2017-11-12T10:07:09ZUlf Magnussonulfalizer@gmail.com2017-11-12T09:54:30Zurn:sha1:f74acbcf05512c01168652ad90d2665a04938a31
Some were for now-removed APIs, others tested things that are tested
differently now.
Spacing nit2017-11-08T10:18:21ZUlf Magnussonulfalizer@gmail.com2017-11-08T10:18:21Zurn:sha1:fe62569dd6a5f57c6c55b42ba58dce684ee436b5Add a release test script2017-11-08T10:14:57ZUlf Magnussonulfalizer@gmail.com2017-11-08T10:11:26Zurn:sha1:bac2790485ad61cf8f06de4017ff8c88f652eca8
Confirms that all the examples that aren't tested in the test suite at
least run. Easy to miss brokenness there. Output can be inspected
manually (it'll vary depending on the kernel version).
Fix defconfig_oldconfig.py, which hadn't been properly updated for the
new API.
Test Choice.assignable, fix for optional choices2017-11-03T05:43:12ZUlf Magnussonulfalizer@gmail.com2017-11-03T05:40:40Zurn:sha1:de2e7f766f247d4e8701dcca9fc921f1d0230463
Could never return 0 as a valid assignable value previously.
Add .assignable selftests for choice symbols2017-11-03T05:14:43ZUlf Magnussonulfalizer@gmail.com2017-11-03T05:13:23Zurn:sha1:d1ea825a1d9d8bfc9496926b6a800ad58581b09aTest .assignable for imply, find C menuconfig bug2017-11-03T04:27:17ZUlf Magnussonulfalizer@gmail.com2017-11-03T04:19:54Zurn:sha1:b74cd303f763fbdc1307830b6333354d65733ef8
A tristate implied to y can't be set to m. Other than that, imply
doesn't affect assignable values.
Fix some copy-paste type errors too.
In the C menuconfig, a tristate with m visibility implied to y gets
stuck if you change it with space. Look into that later. Test case:
config MODULES
def_bool y
option modules
config Y_IMPLIER
def_tristate y
imply Y_IMP_M_VIS_TRI
config Y_IMP_M_VIS_TRI
tristate "y-imp m-vis tri" if m
Add initial selftests for .assignable2017-11-03T02:24:56ZUlf Magnussonulfalizer@gmail.com2017-11-03T02:17:58Zurn:sha1:b59b618a0ce85632742ff92a5be2bab690a75e42
Comprehensive selftests are important here, because the
allno/yesconfig.py scripts only check the upper and lower bound, and
allnoconfig disables modules.
Found a bug for non-selected m-visible tristates, where n didn't show up
in sym.assignable. Everything matches menuconfig after fixing that.
Still need to test symbols in choices with different modes, imply, and
.assignable for choices.