12:15:25 **************************************** ERROR IN YANG FILE /home/jenkins/src/main/yang/standard/ietf/RFC/ietf-te-topology-state.yang ****************************************12:15:25 11:11:20.799 [main] WARN org.opendaylight.yangtools.yang.parser.stmt.reactor.BuildGlobalContext - Unexpected error processing source SourceIdentifier [ietf-network-topology-state@2018-02-26]. Please file an issue with this model attached.

Okay, so the key factor here is that the leaf is guarded by if-feature and yang-model-validator is running with empty features.

This means the leaf should not be built, so the original has flags -88 == 0b10101000 which in turn decodes to:
HAVE_IGNORE_IF_FEATURE | HAVE_SUPPORTED_BY_FEATURES | ALL_INDEPENDENT.

So far this seems to involve undeclared case statements, which do not seem to realize they are no supported. This needs a bit of thought, as here we have an inverted parent->child causality: the child needs to be supported for the parent to be supported.

The reproducer is a bit involved:

module foo {
  namespace foo;
  prefix foo;

  feature foo;

  container foo;

  augment /foo {
    container bar {
      choice baz {
        mandatory true;

        leaf one {
          type string;
        }

        leaf two {
          if-feature foo;
          type string;
        }
      }
    }
  }
}

The problem seems to be the combination of augment, choice, implicit case and if-feature'd leaf. ietf-ip.yang triggers this as well, hence high priority.

Also, the error path occurs under container foo, hence I think the crux of the issue is InferredStatementContext not consulting original's either isSupportedByFeatures(), or more likely isSupportedToBuildEffective().