Starting with ETL unit testing

[TG-SAG]

Hi,
I'm currently trying to get more involved into the development of ETL.
First I cloned it to my linux machine which has g++ (GCC) 8.5.0 20210514 (Red Hat 8.5.0-10) and I got warnings that are errors and I could not compile. For example: -Wunused-variable.
How I generated the tests with run-tests.sh

 Running tests                        
 Configuration   : Initializer list test
 Compiler        : g++ (GCC) 8.5.0 20210514 (Red Hat 8.5.0-10)          
 Language        : C++17   
 Optimisation    : -O2               
 Sanitizer       : Off          
 Compiler select : gcc  
 ETL version     : 20.43.4       
 Git branch      : master  
 Processes       : 4

I then moved to a Github codespace which has the following configuration:

 Running tests                        
 Configuration   : STL
 Compiler        : g++ (Debian 12.2.0-14+deb12u1) 12.2.0          
 Language        : C++17   
 Optimisation    : -O2               
 Sanitizer       : Off          
 Compiler select : gcc  
 ETL version     : 20.43.4       
 Git branch      : master  
 Processes       : 4

But I also got compilation errors:

[ 52%] Building CXX object CMakeFiles/etl_tests.dir/test_fsm.cpp.o
In function ‘void UnitTest::ExecuteTest(T&, const TestDetails&, bool) [with T = {anonymous}::Suitetest_forward_list::SetupFixturetest_sort_emptyHelper]’:
cc1plus: error: potential null pointer dereference [-Werror=null-dereference]
cc1plus: error: potential null pointer dereference [-Werror=null-dereference]

• Is there a list of (GCC) compilers that can compile the ETL unit tests?
• There is a statistic on the https://github.com/ETLCPP/etl that compilations with different compilers and C++ standards are passing. Can I find out (or does anyone know) which compiler versions are used?
• At the end I want to have an development environment that will compile the unit tests.
• Perhaps there are some tips and tricks from other ETL developers on how they compile unit tests. I don't think that it makes sense to delete "-Werror" from the build because it's there for a reason.

[mike919192]

My development setup is:

• Ubuntu 24.04 LTS (I use a docker image and not as my primary OS, but shouldn't matter)
• gcc 13.3
• cmake version 3.28.3

After cloning, to build unit tests:

cmake -DBUILD_TESTS=ON -DETL_CXX_STANDARD=20 -B build .
cd build
make -j6
./test/etl_tests

[jwellbelove]

I compile the tests locally with :-

Windows 10
Ubuntu 22.04

VS2022 (Windows)
GCC 12.3.0 (Linux)
clang 15.0.7 (Linux)

cmake 4.1.1 (Windows)
cmake 3.22.1 (Linux)

The Github CI uses :-

Windows 10
Ubuntu 22.04

VS2022 (Windows)
GCC 11.4.0 (Linux)
clang 14.0.0 (Linux)

[jwellbelove]

The library is tested with and without STL support for C++11, 14, 17, 20, & 23, and tests C++03 compatible implementation alternatives.
There are syntax checks for C++03 (98), 11, 14, 17, 20, & 23.