[pota-quantization-value-test] Set right mode

[mhs4670go]

This commit fixes the bug where the mode was not set properly.

Related: #12526
ONE-DCO-1.0-Signed-off-by: seongwoo [email protected]

[mhs4670go]

@Seunghui98

pota-quantization-value-test test will be passed after this PR.

[Seunghui98]

@mhs4670go
Q) Why is it related to setting mode and solving this bug? :)

[mhs4670go]

@mhs4670go Q) Why is it related to setting mode and solving this bug? :)

One of the tests that failed is pota-quantization-value-test.

The following tests FAILED:
         64 - pota_quantization_test_with_config (Failed)
         76 - circle-interpreter-test (Failed)
Errors while running CTest

[mhs4670go]

@Seunghui98 I've said the detail in the offline since it's a bit complicated to be explained by comments. But let me try as much as possible.

pota-quantization-value-test tests the values from outputs of each quantization steps. The test names each steps as "mode". And, I've written a script that does testing according to given mode.

ONE/compiler/pota-quantization-value-test/compare_tensors_all.py

Lines 36 to 53 in 7dea6ca

	modes_to_expected_folder = {
	'fake_quantization': 'fake_quantization',
	'mixed_fake_quantization': 'fake_quantization',
	'record_minmax': 'record_minmax',
	'parallel_record_minmax': 'record_minmax',
	'quantization': 'quantization',
	'mixed_quantization': 'quantization',
	'weights_only_quantization': 'wo_quantization'
	}
	modes_to_input_h5_suffix = {
	'fake_quantization': 'fake_quantized.circle.h5',
	'mixed_fake_quantization': 'fake_quantized.mixed.circle.h5',
	'record_minmax': 'minmax_recorded.circle.h5',
	'parallel_record_minmax': 'parallel_minmax_recorded.circle.h5',
	'quantization': 'quantized.circle.h5',
	'mixed_quantization': 'quantized.mixed.circle.h5',
	'weights_only_quantization': 'wo_quantized.circle.h5'
	}

But, I mistakenly gave a wrong mode for some tests. Even though the test failed at first, the second run passed because the required output artifacts are generated from other test which is the one that I've mistakenly given.

For example, this is the right test order.

./test.py --mode mixed_record_minmax
./test.py --mode mixed_quantization # it depends on the artifacts from `mixed_record_minmax`

./test.py --mode record_minmax
./test.py --mode quantization # it depends on the artifacts from `record_minmax`

But, I mistakenly wrote tests like below.

./test.py --mode mixed_record_minmax
./test.py --mode quantization # WRONG!!

./test.py --mode record_minmax
./test.py --mode quantization

Above second line failed because the quantization mode test depends on the artifacts of record_minmax not mixed_record_minmax.

But, second run passed because record_minmax mode test has run at the first run so there are outputs in the test artifact directory.

---

So, I fixed the wrong mode.

I think this is because it is important to remove previously generated test artifacts before running the testing.

[Seunghui98]

@mhs4670go

Thank you for letting me know. :)

[Seunghui98]

LGTM :)

[jinevening]

LGTM