This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/gerrit-log@lists.osmocom.org/.
Neels Hofmeyr gerrit-no-reply at lists.osmocom.orgPatch Set 1: Code-Review-2 > - A: scenario is just a filter for a given type of object. It > doesn't apply for each object in particular as in a list, but just > a list of attributes to require for a given type of object. We need distinct attributes for each instance of an object. With A, e.g., I can only have one BTS item, so I can't select "one sysmo, one trx, please". > - B: Scenario is a real object-to-object specific match. That > means, if you have a suite.conf with 2 BTS, then you need to pass a > scenario which is written in a way to explicitly set attribute for > 2 BTS. Yes, that is the plan. The idea is to have a scenario "first_bts_is_sysmo_and_second_is_trx.conf' and be able to reverse that too. This is only possible with a list of dicts. Could be seen as a disadvantage to need distinct configs for multi-BTS cases, but that was the plan from the start (it's a feature). -- To view, visit https://gerrit.osmocom.org/3907 To unsubscribe, visit https://gerrit.osmocom.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I25eb639c7e3cf3b4c67a205422808bffbdd791e6 Gerrit-PatchSet: 1 Gerrit-Project: osmo-gsm-tester Gerrit-Branch: master Gerrit-Owner: Pau Espin Pedrol <pespin at sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: Neels Hofmeyr <nhofmeyr at sysmocom.de> Gerrit-Reviewer: Pau Espin Pedrol <pespin at sysmocom.de> Gerrit-HasComments: No