NFD

At 20150803 conference call, Alex believes this feature is still useful for Vagrant runtime.

Eric says he cannot take this issue because he doesn't know Python enough.

Change 4368,9 test log:

/tmp/integ$ grep -v '#' repos.conf

PACKAGE_NDNCXX=gerrit:4381,5
PACKAGE_NFD=local:../NFD
PACKAGE_NDNTOOLS=branch:master
PACKAGE_NDNTRAFFIC=branch:master
PACKAGE_REPONG=branch:master

/tmp/integ$ git -C ../NFD log | head -1
commit 00d39fda3c24e48fc0fee5f0749bcf596f3876dc

Output snippet:

    template: INSTALLING ndn-cxx
    template: ******************
    template: Checking out from Gerrit: master
    template: Initialized empty Git repository in /home/vagrant/nfd_prepare/ndn-cxx/.git/
    template: From https://gerrit.named-data.net/ndn-cxx
    template:  * branch            master     -> FETCH_HEAD
    template: Note: checking out 'FETCH_HEAD'.
    template:
    template: You are in 'detached HEAD' state. You can look around, make experimental
    template: changes and commit them, and you can discard any commits you make in this
    template: state without impacting any branches by performing another checkout.
    template:
    template: If you want to create a new branch to retain commits you create, you may
    template: do so (now or later) by using -b with the checkout command again. Example:
    template:
    template:   git checkout -b new_branch_name
    template: HEAD is now at 7f01247... mgmt: encode/decode CS Information Dataset
[omitted]
    template: 'install' finished successfully (0.476s)
    template: CONFIGURING SECURITY ENVIRONMENT WITH ndnsec
    template: ********************************************
    template: OK: certificate with name [
    template: /tmp/nfd_integration_tests/KEY/%0E%AA%90%B3%B2%88_%8D/self/%FD%00%00%01%60o%E1%99w
    template: ]
    template: has been successfully installed
    template: INSTALLING NFD
    template: **************
    template: Checking out from Gerrit: master
    template: Initialized empty Git repository in /home/vagrant/nfd_prepare/NFD/.git/
    template: From https://gerrit.named-data.net/NFD
    template:  * branch            master     -> FETCH_HEAD
    template: Note: checking out 'FETCH_HEAD'.
    template:
    template: You are in 'detached HEAD' state. You can look around, make experimental
    template: changes and commit them, and you can discard any commits you make in this
    template: state without impacting any branches by performing another checkout.
    template:
    template: If you want to create a new branch to retain commits you create, you may
    template: do so (now or later) by using -b with the checkout command again. Example:
    template:
    template:   git checkout -b new_branch_name
    template:
    template: HEAD is now at 00d39fd... tests: improve LpReliability unit tests
[omitted]
    template: 'install' finished successfully (0.292s)
    template:

I've checked that repos.conf is copied to the template box, but ../NFD is not transferred properly. Neither PACKAGE_NDNCXX nor PACKAGE_NFD directive was effective.

The issue reported in note 11 should be fixed in the latest patchset.

Junxiao Shi wrote:

I am NOT using Vagrant. ./install_apps.py is one of several methods to run integration tests, as described in README.md.

In case you are wondering, verification is passing on Vagrant.

We still need some way to copy a local repository to a location accessible from the testing machines (VM or otherwise), which will vary by platform. I assume you're using Emulab to run the tests above? Perhaps you could write a script that does what run-vagrant-tests.sh does with any local repositories (creates a folder nfd_prepare in the integration_tests folder and then copies the provided local repository folders to that location).

We still need some way to copy a local repository to a location accessible from the testing machines (VM or otherwise), which will vary by platform.

In my test, the local repository is already available on the testing machine (node A).

I assume you're using Emulab to run the tests above?

No. It is a single machine, intending to run a single host test case such as test_ndnping.

The problem is: repos.conf claims to support “local:../NFD” syntax, but ./install_apps.py is looking for the repository in nfd_prepare. It is wrong to put the copying logic in Vagrant script, because Vagrant is not the only way to run tests. ./install_apps.py needs to looks at the directory specified in repos.conf.
When Vagrant is used, the Vagrant script can upload the local repository, and upload a modified version of repos.conf to point to its location on the template machine, or simply let ./install_apps.py check both locations.

Change 4368,17 test log:

$ cat repos.conf
PACKAGE_NDNCXX=gerrit:4381,5
PACKAGE_NFD=local:../NFD

$ git -C ../NFD log | head -7
commit 4738f15594d7a1c62f692f7fb2a372aabed9308e
Author: Eric Newberry <enewberry@cs.arizona.edu>
Date:   Mon Dec 18 13:10:32 2017 -0700

    tests: make CongestionMarkStrategy parameters human-readable

    Change-Id: I45448640b9125015a0ae2711f14fc3c1472603c3

Output snippet of ./run-vagrant-tests.sh:

    template: INSTALLING ndn-cxx
    template: ******************
    template: Checking out from Gerrit: refs/changes/81/4381/5
    template: Initialized empty Git repository in /home/vagrant/integration-tests/prepare/ndn-cxx/.git/
    template: From https://gerrit.named-data.net/ndn-cxx
    template:  * branch            refs/changes/81/4381/5 -> FETCH_HEAD

    template: INSTALLING NFD
    template: **************
    template: Using local copy of NFD
    template: ERROR: No local copy of package NFD could be found in prepare
    template: