Project

General

Profile

Actions

Bug #3119

closed

TC_crcx_illegal_double_lco fails

Added by laforge about 6 years ago. Updated almost 6 years ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
-
Target version:
-
Start date:
03/28/2018
Due date:
% Done:

100%

Spec Reference:

Description

Th test case MGCP_Tests.TC_crcx_illegal_double_lco of the osmo-mgw test suite fails. It has always failed, we unfortunately didn't execute it automatically from jenkins until today so this sort-of slipped through the cracks.

Actions #1

Updated by laforge almost 6 years ago

  • Assignee changed from 4368 to dexter
  • Priority changed from Normal to Low
Actions #2

Updated by dexter almost 6 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 90

osmo-mgw now checks for the multiple appearance of LCO, TC_crcx_illegal_double_lco now passes.

See also:
https://gerrit.osmocom.org/#/c/osmo-mgw/+/9472 protocol: do not change LCO, when no LCO are present
https://gerrit.osmocom.org/#/c/osmo-mgw/+/9473 mgcp_lco: get rid of struct member "string"
https://gerrit.osmocom.org/#/c/osmo-mgw/+/9474 protocol: reject illegal multiple lco options

(I still have to update the expected results in the testsuite)

Actions #3

Updated by dexter almost 6 years ago

I have updated the patch, it now does a couple more checks. Also we should expect TC_crcx_illegal_double_lco to pass when the patches are merged:

https://gerrit.osmocom.org/#/c/osmo-ttcn3-hacks/+/9478 MGCP_Test: expect TC_crcx_illegal_double_lco to pass

Actions #4

Updated by dexter almost 6 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 90 to 100

The TTCN3 test now passes in jenkins. I think this is resolved now.

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)