Hi Holger
Since I wrote my last e-mail in this thread, we developed some more
stuff for osmo-gsm-tester which may be interesting for this topic.
I recently introduced some code to be able to run TTCN3 tests using real
HW and a motorola c213 phone running osmocom-bb, since we originally
only
> On 10. Jan 2018, at 09:49, Pau Espin Pedrol wrote:
Hey Pau,
> I never used virtbts but I think it should be quite easy adding support for
> it in osmo-gsm-tester. The only big issue I can think of is that we need to
> find a way to differentiate between virtbs and other bts since they us
> On 7. Feb 2018, at 09:31, Holger Freyther wrote:
>
Hey,
> Knowing what I know now I would have gone for Go. It is made for the kind of
> concurrency where python seems unusable. I hesitated to build my own event
> loop but will build something that looks like our C apps in python (single
>
> On 4. Feb 2018, at 22:35, Holger Freyther wrote:
Hi,
> * SIGCHLD arrives
> * Something will be written into one end of a socketpair[1]
> * In the python code on wait(2) will be called on every registered process
> (https://github.com/python/cpython/blob/3.6/Lib/asyncio/unix_events.py#L819)
> On 29. Jan 2018, at 21:52, Holger Freyther wrote:
>
Hey,
I wish I had better news. Instead of an end to end test I realize that picking
"asyncio" was a grave mistake. Besides the lack AF_UNIX SOCK_DGRAM support, the
process support is dangerous and doesn't scale. Today I stumbled into SIG
> On 29. Jan 2018, at 10:50, Harald Welte wrote:
>
> Hi Holger,
>
> thanks for your status update. Looking forward to the related code.
hehe. It is just a couple of hundred lines so far. It should bring us far
enough. Will continue with it in a few minutes. For simplicity I am not
segmenting
Hi Holger,
thanks for your status update. Looking forward to the related code.
--
- Harald Weltehttp://laforge.gnumonks.org/
"Privacy in residential applications is a desirable marketing option."
> On 21. Jan 2018, at 20:16, Holger Freyther wrote:
>
Hey!
some more progress. I had to learn a bit about asyncio and in the end will
be forced to use a stream socket[1] and will end up using the IPA and add
a reservation for JSON events. I will probably push my unfinished code to
gerrit but i
> On 10. Jan 2018, at 23:39, Harald Welte wrote:
>
Hi!
> If you reuse osmo-gsm-tester code for templates or the like, then it should
> probably go there. If not, OsmocomBB seems like the more logical place.
> Would be great if in that case it is some kind of python library/module
> and a sma
Hi Holger,
On Wed, Jan 10, 2018 at 10:52:59PM +, Holger Freyther wrote:
> okay. That reduces some degrees of the freedom. Where to put it? Into the
> OsmocomBB sources? Osmo GSM tester even if it might not share much code?
If you reuse osmo-gsm-tester code for templates or the like, then it
> On 10. Jan 2018, at 11:55, Harald Welte wrote:
>
> Hi Holger,
> Sure, I understand. However, it is definitely a part that we're very
> much looking forward to have :)
me too... I dislike not having made progress here.
> One might also think of a more structured format to return the data,
Hi Holger,
On Wed, Jan 10, 2018 at 12:24:47AM +, Holger Freyther wrote:
> the lua binding code was added to be able to automate OpenBSC tests.
> In theory we should be able to do this for SMS and UpdateLocation
> (call handling with MNCC exposing is left as a todo) but in practice
> we miss a
Hi Holger,
I never used virtbts but I think it should be quite easy adding support
for it in osmo-gsm-tester. The only big issue I can think of is that we
need to find a way to differentiate between virtbs and other bts since
they use a different communication medium and then that means that t
Hi Holger,
I never used virtbts but I think it should be quite easy adding support
for it in osmo-gsm-tester. The only big issue I can think of is that we
need to find a way to differentiate between virtbs and other bts since
they use a different communication medium and then that means that t
14 matches
Mail list logo
