In pytest based self tests, netsim is not run for DUT path when using --update_ref=2 option

I am not sure how widely this affects things but for some reason, the netsim processing is not done when running self_test.prm using pytest and the option --update_ref=2. Everything works fine if you first run --update_ref=1 version followed by --update_ref=0 version.

As an example, this does not work

pytest tests/codec_be_on_mr_nonselection/test_param_file.py --update_ref=2 --param_file scripts/config/custom_test.prm --dut_encoder_path=pathtobin/IVAS_cod --dut_decoder_path=pathtobin/IVAS_dec --ref_encoder_path=pathtobin/IVAS_cod_ref --ref_decoder_path=pathtobin/IVAS_dec_ref --html=report.html --self-contained-html

But this works

pytest tests/codec_be_on_mr_nonselection/test_param_file.py --update_ref=1 --param_file scripts/config/custom_test.prm --dut_encoder_path=pathtobin/IVAS_cod --dut_decoder_path=pathtobin/IVAS_dec --ref_encoder_path=pathtobin/IVAS_cod_ref --ref_decoder_path=pathtobin/IVAS_dec_ref --html=report.html --self-contained-html

pytest tests/codec_be_on_mr_nonselection/test_param_file.py --update_ref=0 --param_file scripts/config/custom_test.prm --dut_encoder_path=pathtobin/IVAS_cod --dut_decoder_path=pathtobin/IVAS_dec --ref_encoder_path=pathtobin/IVAS_cod_ref --ref_decoder_path=pathtobin/IVAS_dec_ref --html=report.html --self-contained-html

Probably not the most critical thing to fix but good to know that there is such issue. I can avert this by just doing the two-step approach.