- Boost-users - lists.preview.boost.org

Boost ASIO write: Socket operation on non-socket
by Sharma, Nishant 11 Jan '18

11 Jan '18

Hi, I cannot post the complete program, but when I do asio::write , I get the error: write: Socket operation on non-socket Now, just before that I check if the socket is opened or not and it indeed is opened. io_service is also running.. I just need some pointers and possible cause for this so that I can debug and take his further... My use model is I call asio::write which is synchronous and for reading I use async_read which first reads the header data and then calls asio::read to read the actual data. Best Regards, Nishant Sharma

2 1

Google Summer of Code 2018
by David Bellot 10 Jan '18

10 Jan '18

Dear Boost community, once again this year, we will apply to be a mentoring organization for the Google Summer of Code 2018. Our organization has been quite succesful for the last decade and this year we hope to be selected again. As part of filling in our application for 2018, we must supply to Google a list of potential GSoC mentors and potential GSoC projects for summer 2018 in order to be approved as an organisation this year. Therefore a lengthy page of awesome project ideas at https://svn.boost.org/trac/boost/wiki/SoC2018 before *January 23rd* would be an enormous help to getting us approved again this year and bringing to Boost another Google funding (worth dozens of thousands of dollars on average). If you think yourself able to mentor a student doing some work on Boost this summer, *please* consider adding a description of the proposed work item and your name to the list. If you want to have a better chance receiving funding for your project ideas, it is better to find good students early and that is best done by getting project ideas floated *early*. If you want to know more about mentoring a Google Summer of Code funded student work before you nominate yourself, please feel free to ask on the main Boost developers mailing list boost(a)lists.boost.org or via gsoc-admin(a)boost.org. Thank you in advance for your time. Finally, I would like to thank Niall Douglas, our previous Boost admnistrator for GSoC, who did an awesome work during many years and helped the Boost community grow thanks to all the funding we received years after years from Google. Best regards, David

1 0

1.66 changes in layout suffix seems to break cmake finder
by Stephan Menzel 09 Jan '18

09 Jan '18

Hello, I am currently trying to upgrade my projects to 1.66 and I am puzzled by a change in bjam's 'laout' parameter. I am building boost for MSVC14 (x64). Normally I use the following command line: > bjam.exe --layout=versioned variant=release address-model=64 link=static,shared runtime-link=shared threading=multi stage to achieve the build flags and setup that I need. Up until 1.65 this yielded libs named like: libboost_atomic-vc140-mt-1_65.lib This is what appears to be the most flexible for my use case and I always discover them using the 'normal' CMake finders like this: set(BOOST_ROOT ${WHERE_MY_THIRD_PARTY_STUFF_IS}/boost-1.66.0 CACHE PATH "set root of boost install") set(BOOST_INCLUDEDIR ${BOOST_ROOT}/include CACHE PATH "set boost includes") set(BOOST_LIBRARYDIR ${BOOST_ROOT}/lib CACHE PATH "set boost library dir") set(Boost_ADDITIONAL_VERSIONS "1.66.0") find_package(Boost REQUIRED COMPONENTS ...) Now over the years the meaning of the --layout parameter and its defaults have occasionally changed by I always managed to get something like this. But now, with 1.66 the filenames are changed to that: libboost_atomic-vc140-mt-x64-1_66.lib With this, CMake won't find the libs anymore. I have tried all different variantions of --layout I know (system, tagged, versioned) but I cannot get the old naming scheme back. I could rename the files manually but I am a bit afraid that this might break some linker (autolink) magick and also it doesn't seem right. Trying with several CMake finder options also got me nowhere. Using layout system is not desired as I like to quickly distinguish between versions on sight. So my question is: Is there a way to get >=1.66 to build with the filename scheme it had until now? Or is there a change to the CMake finders that will fix this? Thanks for any suggestions... Stephan

3 7

[filesystem] VS2005 compiler warnings
by Klebsch, Mario 09 Jan '18

09 Jan '18

Hi, I am using boost library 1.63.0 in an old project, which still uses VS2005. I get some compiler warnings from boost::filesystem: boost\libs\filesystem\src\unique_path.cpp(114) : warning C4267: 'argument' : conversion from 'size_t' to 'DWORD', possible loss of data boost\libs\filesystem\src\windows_file_codecvt.cpp(43) : warning C4244: 'argument' : conversion from '__w64 int' to 'int', possible loss of data boost\libs\filesystem\src\windows_file_codecvt.cpp(43) : warning C4244: 'argument' : conversion from '__w64 int' to 'int', possible loss of data boost\libs\filesystem\src\windows_file_codecvt.cpp(63) : warning C4244: 'argument' : conversion from '__w64 int' to 'int', possible loss of data boost\libs\filesystem\src\windows_file_codecvt.cpp(63) : warning C4244: 'argument' : conversion from '__w64 int' to 'int', possible loss of data boost\boost\filesystem\string_file.hpp(27) : warning C4267: 'argument' : conversion from 'size_t' to 'std::streamsize', possible loss of data boost\boost\filesystem\string_file.hpp(38) : warning C4267: 'argument' : conversion from 'size_t' to 'std::streamsize', possible loss of data I am new on boost-users, so I don't yet know, whether patches for compiler warnings are welcome, but I would like to propose some changes: For the warning in unique_path.cpp(114),I think it is safe to static_cast len to DWORD: > BOOL gen_ok = ::CryptGenRandom(handle, static_cast <DWORD>(len), static_cast<unsigned char*>(buf)); For the two lines in windows_file_codecvt.cpp, I also think that a static_cast is ok: windows_file_codecvt.cpp(42) > if ((count = ::MultiByteToWideChar(codepage, MB_PRECOMPOSED, from, windows_file_codecvt.cpp(43) > static_cast<int>(from_end - from), to, static_cast<int>(to_end - to))) == 0) windows_file_codecvt.cpp(62) > if ((count = ::WideCharToMultiByte(codepage, WC_NO_BEST_FIT_CHARS, from, windows_file_codecvt.cpp(63) > static_cast<int>(from_end - from), to, static_cast<int>(to_end - to), 0, 0)) == 0) The last two warnings are in generic parts, and changes would affect not only windows. Unfortunately, I have no good idea, on how to fix or avoid these warnings. 73, Mario -- Mario Klebsch Actia I+ME GmbH Mario.klebsch(a)ime-actia.de<mailto:Mario.klebsch@ime-actia.de> Dresdenstrasse 17/18 Fon: +49 531 38 701 716 38124 Braunschweig Fax: +49 531 38 701 88 Germany

1 0

[Boost.Asio] defer, dispatch and post differences?
by Daniel Bergström 08 Jan '18

08 Jan '18

The free functions *defer*, *dispatch* and *post* all have the exact same set of overloads and description in the library's reference (version 1.66.0). I also couldn't find anything on the subject in the *Overview* section of the library's documentation. Is the differences between them clearly described somewhere else, that I've missed, or could someone explain it? Thank you, Daniel

5 14

Boost asio reuse address
by Sharma, Nishant 07 Jan '18

07 Jan '18

Hi, Just wanted to know if setting the following option on acceptor should be ever done or not.. When should this be used.. acceptor_.set_option(boost::asio::ip::tcp::acceptor::reuse_address(true)); The reason I am asking this is because I have a server application which crashed but the socket did not close. So, the next time, I was bringing up the server, I get the error : Error occured! Error code = system:98. Message: bind: Address already in use But, even giving the option above, it is not working fine. I referred to the URL : https://stackoverflow.com/questions/34596638/boost-asio-so-reuseport to figure out the steps in which acceptor should be created from this link. Best Regards, Nishant Sharma

2 1

Building boost fails with VS2017 (v15.5.2)
by Christian Henning 06 Jan '18

06 Jan '18

This is rather strange. I have downloaded boost 1.66 and can build Boost.Build engine. But building the libs fails. The full output is here: https://pastebin.com/raw/mRriQDvq Here is what I'm seeing: ********************************************************************** ** Visual Studio 2017 Developer Command Prompt v15.5.2 ** Copyright (c) 2017 Microsoft Corporation ********************************************************************** [vcvarsall.bat] Environment initialized for: 'x64' C:\Users\chhenning\source>d: D:\>cd boost D:\boost>.\bootstrap.bat Building Boost.Build engine Bootstrapping is done. To build, run: .\b2 To adjust configuration, edit 'project-config.jam'. Further information: - Command line help: .\b2 --help - Getting started guide: http://boost.org/more/getting_started/windows.html - Boost.Build documentation: http://www.boost.org/build/doc/html/index.html D:\boost>b2 -j8 --toolset=msvc variant=release link=static runtime-link=shared address-model=64 define=_CRT_NONSTDC_NO_DEPRECATE define=_CRT_SECURE_NO_DEPRECATE define=_SCL_SECURE_NO_DEPRECATE define=_SECURE_SCL=0 define=_HAS_ITERATOR_DEBUGGING=0 define=BOOST_REGEX_MATCH_EXTRA stage Performing configuration checks - 32-bit : no (cached) - 64-bit : no (cached) - arm : no (cached) - mips1 : no (cached) - power : no (cached) - sparc : no (cached) - x86 : no (cached) - combined : no (cached) - symlinks supported : no (cached) - junctions supported : yes (cached) - hardlinks supported : yes (cached) error: No best alternative for libs/context/build/asm_sources next alternative: required properties: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>clang not matched next alternative: required properties: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>qcc not matched next alternative: required properties: <abi>aapcs <address-model>32 <architecture>arm <binary-format>mach-o <threading>multi <toolset>clang not matched next alternative: required properties: <abi>aapcs <address-model>32 <architecture>arm <binary-format>mach-o <threading>multi <toolset>darwin not matched next alternative: required properties: <abi>aapcs <address-model>32 <architecture>arm <binary-format>pe <threading>multi <toolset>msvc not matched next alternative: required properties: <abi>aapcs <address-model>64 <architecture>arm <binary-format>elf <threading>multi <toolset>clang not matched next alternative: required properties: <abi>aapcs <address-model>64 <architecture>arm <binary-format>elf <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>aapcs <address-model>64 <architecture>arm <binary-format>mach-o <threading>multi <toolset>clang not matched next alternative: required properties: <abi>aapcs <address-model>64 <architecture>arm <binary-format>mach-o <threading>multi <toolset>darwin not matched next alternative: required properties: <abi>o32 <address-model>32 <architecture>mips1 <binary-format>elf <threading>multi <toolset>clang not matched next alternative: required properties: <abi>o32 <address-model>32 <architecture>mips1 <binary-format>elf <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>power <binary-format>elf <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>power <binary-format>elf <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>power <binary-format>mach-o <threading>multi <toolset>darwin not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>power <binary-format>xcoff <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>power <binary-format>xcoff <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>power <binary-format>elf <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>power <binary-format>elf <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>power <binary-format>mach-o <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>power <binary-format>mach-o <threading>multi <toolset>darwin not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>power <binary-format>xcoff <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>power <binary-format>xcoff <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>sysv <address-model>32_64 <architecture>power <binary-format>mach-o <threading>multi not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>x86 <binary-format>elf <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>x86 <binary-format>elf <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>x86 <binary-format>elf <threading>multi <toolset>intel not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>x86 <binary-format>mach-o <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>x86 <binary-format>mach-o <threading>multi <toolset>darwin not matched next alternative: required properties: <abi>ms <address-model>32 <architecture>x86 <binary-format>pe <threading>multi <toolset>clang not matched next alternative: required properties: <abi>ms <address-model>32 <architecture>x86 <binary-format>pe <threading>multi <toolset>clang-win not matched next alternative: required properties: <abi>ms <address-model>32 <architecture>x86 <binary-format>pe <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>ms <address-model>32 <architecture>x86 <binary-format>pe <threading>multi <toolset>intel not matched next alternative: required properties: <abi>ms <address-model>32 <architecture>x86 <binary-format>pe <threading>multi <toolset>msvc not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>x86 <binary-format>elf <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>x86 <binary-format>elf <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>x86 <binary-format>elf <threading>multi <toolset>intel not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>x86 <binary-format>mach-o <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>x86 <binary-format>mach-o <threading>multi <toolset>darwin not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>x86 <binary-format>mach-o <threading>multi <toolset>intel not matched next alternative: required properties: <abi>ms <address-model>64 <architecture>x86 <binary-format>pe <threading>multi <toolset>clang not matched next alternative: required properties: <abi>ms <address-model>64 <architecture>x86 <binary-format>pe <threading>multi <toolset>clang-win not matched next alternative: required properties: <abi>ms <address-model>64 <architecture>x86 <binary-format>pe <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>ms <address-model>64 <architecture>x86 <binary-format>pe <threading>multi <toolset>intel not matched next alternative: required properties: <abi>ms <address-model>64 <architecture>x86 <binary-format>pe <threading>multi <toolset>msvc not matched next alternative: required properties: <abi>x32 <address-model>64 <architecture>x86 <binary-format>elf <threading>multi <toolset>clang not matched next alternative: required properties: <abi>x32 <address-model>64 <architecture>x86 <binary-format>elf <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>x32 <address-model>64 <architecture>x86 <binary-format>elf <threading>multi <toolset>intel not matched next alternative: required properties: <abi>sysv <address-model>32_64 <architecture>x86 <binary-format>mach-o <threading>multi not matched next alternative: required properties: <abi>sysv <architecture>combined <binary-format>mach-o <threading>multi not matched - C++11 mutex : no (cached) - Boost.Config Feature Check: cxx11_auto_declarations : no (cached) - Boost.Config Feature Check: cxx11_constexpr : no (cached) - Boost.Config Feature Check: cxx11_defaulted_functions : no (cached) - Boost.Config Feature Check: cxx11_final : no (cached) - Boost.Config Feature Check: cxx11_hdr_mutex : no (cached) - Boost.Config Feature Check: cxx11_hdr_regex : no (cached) - Boost.Config Feature Check: cxx11_hdr_tuple : no (cached) - Boost.Config Feature Check: cxx11_lambdas : no (cached) - Boost.Config Feature Check: cxx11_noexcept : no (cached) - Boost.Config Feature Check: cxx11_nullptr : no (cached) - Boost.Config Feature Check: cxx11_rvalue_references : no (cached) - Boost.Config Feature Check: cxx11_template_aliases : no (cached) - Boost.Config Feature Check: cxx11_thread_local : no (cached) - Boost.Config Feature Check: cxx11_variadic_templates : no (cached) - has_icu builds : no (cached) warning: Graph library does not contain MPI-based parallel components. note: to enable them, add "using mpi ;" to your user-config.jam - zlib : no (cached) - bzip2 : no (cached) - lzma : no (cached) - iconv (libc) : no (cached) - iconv (separate) : no (cached) - icu : no (cached) - icu (lib64) : no (cached) - native-atomic-int32-supported : no (cached) - message-compiler : yes (cached) - native-syslog-supported : no (cached) - pthread-supports-robust-mutexes : no (cached) - compiler-supports-visibility : no (cached) - x86 : no (cached) - arm : no (cached) - mips1 : no (cached) - power : no (cached) - sparc : no (cached) - gcc visibility : no (cached) - long double support : no (cached) warning: skipping optional Message Passing Interface (MPI) library. note: to enable MPI support, add "using mpi ;" to user-config.jam. note: to suppress this message, pass "--without-mpi" to bjam. note: otherwise, you can safely ignore this message. - libbacktrace builds : no (cached) - addr2line builds : no (cached) - WinDbg builds : no (cached) - WinDbgCached builds : no (cached) Component configuration: - atomic : building - chrono : building - container : building - context : building - coroutine : building - date_time : building - exception : building - fiber : building - filesystem : building - graph : building - graph_parallel : building - iostreams : building - locale : building - log : building - math : building - mpi : building - program_options : building - python : building - random : building - regex : building - serialization : building - signals : building - stacktrace : building - system : building - test : building - thread : building - timer : building - type_erasure : building - wave : building ...patience... ...patience... ...patience... ...patience... ...patience... ...patience... ...found 16860 targets... ...updating 401 targets... compile-c-c++ bin.v2\libs\atomic\build\msvc-14.1\release\address-model-64\link-static\threadapi-win32\threading-multi\lockpool.obj 'cl' is not recognized as an internal or external command, operable program or batch file. call "C:\Users\CHHENN~1\AppData\Local\Temp\b2_msvc_14.1_vcvarsx86_amd64_.cmd" >nul cl /Zm800 -nologo @"bin.v2\libs\atomic\build\msvc-14.1\release\address-model-64\link-static\threadapi-win32\threading-multi\lockpool.obj.rsp" ...failed compile-c-c++ bin.v2\libs\atomic\build\msvc-14.1\release\address-model-64\link-static\threadapi-win32\threading-multi\lockpool.obj... ...skipped <pbin.v2\libs\atomic\build\msvc-14.1\release\address-model-64\link-static\threadapi-win32\threading-multi>libboost_atomic-vc141-mt-1_66.lib for lack of <pbin.v2\libs\atomic\build\msvc-14.1\release\address-model-64\link-static\threadapi-win32\threading-multi>lockpool.obj... ...skipped <pstage\lib>libboost_atomic-vc141-mt-1_66.lib for lack of <pbin.v2\libs\atomic\build\msvc-14.1\release\address-model-64\link-static\threadapi-win32\threading-multi>libboost_atomic-vc141-mt-1_66.lib... compile-c-c++ bin.v2\libs\system\build\msvc-14.1\release\address-model-64\link-static\threadapi-win32\threading-multi\error_code.obj 'cl' is not recognized as an internal or external command, operable program or batch file. call "C:\Users\CHHENN~1\AppData\Local\Temp\b2_msvc_14.1_vcvarsx86_amd64_.cmd" >nul cl /Zm800 -nologo @"bin.v2\libs\system\build\msvc-14.1\release\address-model-64\link-static\threadapi-win32\threading-multi\error_code.obj.rsp" ...failed compile-c-c++ bin.v2\libs\system\build\msvc-14.1\release\address-model-64\link-static\threadapi-win32\threading-multi\error_code.obj... ...skipped <pbin.v2\libs\system\build\msvc-14.1\release\address-model-64\link-static\threadapi-win32\threading-multi>libboost_system-vc141-mt-1_66.lib for lack of <pbin.v2\libs\system\build\msvc-14.1\release\address-model-64\link-static\threadapi-win32\threading-multi>error_code.obj... ...skipped <pstage\lib>libboost_system-vc141-mt-1_66.lib for lack of <pbin.v2\libs\system\build\msvc-14.1\release\address-model-64\link-static\threadapi-win32\threading-multi>libboost_system-vc141-mt-1_66.lib... compile-c-c++ bin.v2\libs\chrono\build\msvc-14.1\release\address-model-64\link-static\threadapi-win32\threading-multi\chrono.obj 'cl' is not recognized as an internal or external command, operable program or batch file. [snip] Anyone any idea what is going on? Thanks, Christian

3 5

[process] Couple of issues
by Sebastian Messerschmidt 02 Jan '18

02 Jan '18

Hi, I'm using boost 1.64 on Windows7 with VisualStudio 2015 64bit. While testing boost.process I've encountered some issues that I'm not able to resolve: 1. Passing of multiple parameters: Consider this minimal example: <code> void test_sync() { try { bp::ipstream is; bp::child c(bp::search_path("ping"), "127.0.0.1 -t", bp::std_out > is); std::string line; while (c.running() && std::getline(is, line) && !line.empty()) { std::cerr << line << std::endl; } c.wait(); } catch (const std::exception& e) { std::cerr << "Error in execution: " << e.what(); } } </code> This doesn't correctly execute "ping 127.0.0.1 -t", instead it will act like "ping 127.0.0.1". I could not find an up2date example on how to pass parameters correctly. Any ideas? 2. No output on std::cout It seems that some applications don't output to std::cout/clog/cerr but somehow via printing to console directly (my guess as it is colored output on windows) In those instances, redirection fails. Can anyone think of a way to still monitor the output of the spawned child? Cheers Sebastian

2 3

Boost.Test: floating point comparison using absolute diference
by Georgios Sermaidis 30 Dec '17

30 Dec '17

Hi all, I am trying to find a way to make the boost unit test framework use an absolute difference for floating point comparison instead of the relative difference. I searched the documentation to try to find a suitable decorator but couldn’t find anything. Any help is much appreciated! #define BOOST_TEST_MODULE example #include <boost/test/included/unit_test.hpp> // boost::unit_test::tolerance uses relative difference and hence this test will pass; // is there anything I can use here to indicate absolute difference? BOOST_AUTO_TEST_CASE(my_test, * boost::unit_test::tolerance(0.1) ) { BOOST_TEST(10.1 == 10.3); }

2 4

Boost Unit Test: How to run only the enabled tests of a test suite?
by Maarten Anonymous 28 Dec '17

28 Dec '17

Hey, I'm looking for a way to only run the enabled unit tests of a tests suite. I have the following test suite: #define BOOST_TEST_MODULE decorator_predicate#include <boost/test/included/unit_test.hpp>namespace utf = boost::unit_test; BOOST_AUTO_TEST_SUITE(test_suite_1) BOOST_AUTO_TEST_CASE(bare_test){ BOOST_TEST(true);} BOOST_AUTO_TEST_CASE(enabled_test, * utf::enabled()){ BOOST_TEST(true);} BOOST_AUTO_TEST_CASE(disabled_test, * utf::disabled()){ BOOST_TEST(false);} BOOST_AUTO_TEST_SUITE_END() BOOST_AUTO_TEST_SUITE(test_suite_2) BOOST_AUTO_TEST_CASE(bare_test){ BOOST_TEST(true);} BOOST_AUTO_TEST_CASE(enabled_test, * utf::enabled()){ BOOST_TEST(true);} BOOST_AUTO_TEST_CASE(disabled_test, * utf::disabled()){ BOOST_TEST(false);} BOOST_AUTO_TEST_SUITE_END() Compilation and running: # Compile the test g++ predicate.cpp -o predicate # List all tests./predicate --list_content test_suite_1* bare_test* enabled_test* disabled_test test_suite_2* bare_test* enabled_test* disabled_test # Run the tests that are enabled by default./predicateRunning 4 test cases... *** No errors detected # Here, I would like to only run the enabled tests of test_suite_1.# Instead, all tests are run. Including the disabled../predicate -t test_suite_1Running 3 test cases... predicate.cpp(21): error: in "test_suite_1/disabled_test": check false has failed *** 1 failure is detected in the test module "decorator_predicate" How can I only run the enabled tests of tst_suite1? Only bare_test and enabled_test should be run. Thanks!

2 1