[LNT] Fix profile assigning to tests

[kpdev42]

Summary

report.json may contain the following content:

“Tests”: [
{“Data”: [ 123 ], “Name”: “nts.SomeTest.test:subTest1.exec”},
{“Data”: [ 456 ], “Name”: “nts.SomeTest.test:subTest2.exec”},
{“Data”: [ “base64_encoded_profile_data” ], “Name”: “nts.SomeTest.profile”}
]

This report.json contains 2 tests (execution_time) and 1 profile data which must be assigned to both tests.
Currently LNT creates 3 tests. First 2 tests do not have a profile data. 3rd test does not have any metric, but has the profile data.

This patch implements the correct processing such reports.

OS Laboratory. Huawei Russian Research Institute. Saint-Petersburg

[kpdev42]

Ping

[thopre]

lnt/server/db/testsuitedb.py

1045

If a profile is determined by having the name ends in .profile I'd prefer to check that explicitely (i.e. test_data['name'].endswith('profie'))

1078

And mirror it here, perhaps introduce a "is_profile" lambda.

[slydiman]

lnt/server/db/testsuitedb.py

1045

It will not work because __init__.py (line 593) removes '.profile' from the name during preprocessing.

[thopre]

lnt/server/db/testsuitedb.py

1045

One more reason to rewrite this test.

[kpdev42]

Address review commentaries. Thank you

[slydiman]

lnt/server/db/testsuitedb.py

1045

What test do you mean? This code works just fine.

You suggested

If a profile is determined by having the name ends in .profile I'd prefer to check that explicitely (i.e. test_data['name'].endswith('profie'))

But it will not work because lnt/testing/__init__.py (line 593) converts JSON data v1 to v2:

{“Data”: [ “base64_encoded_profile_data” ], “Name”: “nts.SomeTest.profile”}

to

{“profile”: [ “base64_encoded_profile_data” ], “name”: “nts.SomeTest”}

[thopre]

lnt/server/db/testsuitedb.py

1045

Ah my bad, hadn't realized it gets transformed to a dictionary with a "profile" key. I thought it was looking for "profile" in one of the value. LGTM then.