Project

General

Profile

Actions

Bug #5074

closed

Transport tests failing due to macOS AWDL interfaces

Added by Alexander Lane over 4 years ago. Updated 6 months ago.

Status:
Closed
Priority:
Low
Category:
Faces
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:

Description

On MacOS Mojave, unit tests are failing due to attempting to use Apple's internal P2P interfaces (AWDL) on the transport unit tests (see attached log). This generates significant false positives when checking for errors.


Files

output.txt (20.2 KB) output.txt Alexander Lane, 01/10/2020 01:33 PM

Related issues 1 (0 open1 closed)

Related to NFD - Bug #5096: TestMulticastEthernetTransport/NetifStateChange fails with interfaces that are not RUNNINGClosedEric Newberry

Actions
Actions #1

Updated by Davide Pesavento over 4 years ago

  • Subject changed from Unit tests failing due to MacOS AWDL interfaces to Transport tests failing due to macOS AWDL interfaces
  • Start date deleted (01/10/2020)
Actions #2

Updated by Eric Newberry about 4 years ago

This is happening on Catalina as well with Jenkins.

Actions #3

Updated by Eric Newberry about 4 years ago

  • Status changed from New to In Progress
  • Assignee set to Eric Newberry
  • Target version set to 22.02

(Removed previous comment. Was for a different issue.)

Actions #4

Updated by Eric Newberry about 4 years ago

  • Assignee deleted (Eric Newberry)
Actions #5

Updated by Davide Pesavento about 4 years ago

  • Status changed from In Progress to New
  • Target version deleted (22.02)
Actions #6

Updated by Davide Pesavento about 4 years ago

  • Related to Bug #5096: TestMulticastEthernetTransport/NetifStateChange fails with interfaces that are not RUNNING added
Actions #7

Updated by Davide Pesavento almost 4 years ago

  • Tags set to macOS, unit-tests
Actions #8

Updated by Davide Pesavento 6 months ago

  • Category changed from Unit Tests to Faces
  • Assignee set to Davide Pesavento
  • Priority changed from Normal to Low
  • Target version set to 24.next

I think it would make sense to blacklist these interfaces globally, not just in unit tests, given that they can't be used for anything in practice.

Actions #9

Updated by Davide Pesavento 6 months ago

  • Status changed from New to Code review
  • % Done changed from 0 to 100
Actions #10

Updated by Davide Pesavento 6 months ago

  • Status changed from Code review to Closed
Actions

Also available in: Atom PDF