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 2: > - Be able to run the latest trial manually. it's a bit cumersome to 'ls -1t | head -n 1' but we could also add a command line option to osmo-gsm-tester.py to do this automatically. > - If the list of trials is accessible via ssh, ftp or http, give > users who want to get the latest trial a unique reference/link. The problem is that with concurrent runs, there isn't really a concept of a latest trial. I would discourage scripts from launching a trial and then assuming that the latest trial dir is the one they should look at. Instead, there should be a safe way to know which trial run was launched... What other use case is there than wanting to run a fairly recent set of binaries manually? I get the intention and I would love to be able to just accept this, but the more I think about it the more I don't like the side effects it's introducing... For example, what if a manual run tries to point the latest symlink back at itself? and so on... we need to safeguard and work around it. If we just have no such symlink, all problems disappear, and we still have other easy ways to implement the use case for a 'latest' link, right? -- To view, visit https://gerrit.osmocom.org/2443 To unsubscribe, visit https://gerrit.osmocom.org/settings Gerrit-MessageType: comment Gerrit-Change-Id: I26ddf55110738bd1944ccbfe72e8410ff9811392 Gerrit-PatchSet: 2 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-Reviewer: neels <nhofmeyr at sysmocom.de> Gerrit-HasComments: No