Skip to content
Sign in
Success

#595 (Jan 20, 2026, 5:43:00 PM)

Started 26 days ago
Took 19 min on build5-deb12build-ansible
Build Artifacts

Started by timer

This run spent:

  • 3 ms waiting;
  • 19 min build duration;
  • 19 min total from scheduled to completion.
Revision: 648954ff1ab94620833b484d8131d001c61faa78
Repository: https://gerrit.osmocom.org/osmo-ttcn3-hacks
  • origin/master
Tests (no failures)
    s1gw: add MME pool related REST definitions

    Change-Id: I76f1a5cf41331d021c08fbefdf78e34da4ac2121
    Related: osmo-s1gw.git Iad249aed99face9e35fd19e0596cf2364ade4c77
    Related: SYS#7052, SYS#7066
    Vadim Yanitskiy at
    bts: testenv: check ulimit -r in prepare=

    Don't respawning over and over again if osmo-bts-trx fails to start up
    because the user isn't allowed to set the rtpriority. Show instructions
    for fixing it instead.

    Change-Id: I7bc1414f95e4a54a40eb7c6f7b3d6c83ce3500c6
    Oliver Smith at
    testenv: less cluttered output for failed cmds

    The testenv.cmd.run() already prints the command to run at the start,
    prints the command output and blocks until the command is done.

    If the command fails, do not print the command again, and do not print a
    python stack trace. The reason for the failure is most likely in the
    output shown by the program itself (e.g. a prepare= script that failed).
    Make it easier for the user to spot this error by uncluttering the
    output.

    Change-Id: I508322b017e5ed9c21396384ef759a4c49c8d3da
    Oliver Smith at