NFD

@Hila has some experience with integration tests.

I see both face_system.unix.listen and unix_socket in integration tests code, so I assume the failures are caused by both problems.

I'm looking into it and I see that 3 tests fail:

1. Interest loop test fails to connect to the forwarder, probably because it uses its own copy of nfd.conf.
   Another problem with this test is that it reports PASSED at the end rather than FAILED. I believe it should be fixed as well. I'm not sure if you want to open a new bug for it since it contains some structural changes to the code. I believe it would be better to solve it separately but it's your call.

2. local host test also fails to connect to the forwarder. I can see in the code that the script modifies unix_socket in client.conf. Here, the script correctly reports on its failure.

3. NDN hub discovery fails because it tries to create Non-canonical face.

I don't know how often you choose to run the integration tests, but I think it should be automated to run once a week or two. I can help building such an automation if you agree it's necessary. If automation is not possible due to the required resources, then maybe we can mark potential tasks/bugs as 'regression required' on redmine and then manually run the tests as part of the code-review process. I think it would be helpful to do it on a major commit such as a new feature or an infrastructure change.