Hi Thibaut, for testing MPI I add the following line into the script:
export OMPI_MCA_orte_rsh_agent=/bin/false Usually it works [1--3]. [1] http://anonscm.debian.org/cgit/debian-science/packages/esys-particle.git/tree/debian/tests/build1#n7 [2] https://anonscm.debian.org/cgit/debian-science/packages/liggghts.git/tree/debian/tests/heat [3] https://anonscm.debian.org/cgit/debian-science/packages/liggghts.git/tree/debian/tests/packing Best regards Anton Anton 2015-05-23 10:41 GMT+02:00 Thibaut Paumard <[email protected]>: > Hi, > > I'm working on autopkgtest support in one of my packages, gyoto. > > The upcoming upstream release (preview available on our alioth git repo) > features MPI parallelisation, and I want to test this feature. > > In my experience, running MPI code requires network access. Failing > that, openmpi hangs the machine. For instance, when debugging in the > subway, I have to connect to my cell-phone by wifi else the computer > will freeze during the test suite! > > I'm wondering whether putting "Restrictions: isolation-container" in the > test stanza is sufficient to ensure openmpi will behave properly? > > Also akin, is there a way to test the code during build, since it is > forbidden to access the network at that time? > > Kind regards, Thibaut. > > > -- > To UNSUBSCRIBE, email to [email protected] > with a subject of "unsubscribe". Trouble? Contact [email protected] > Archive: https://lists.debian.org/[email protected] > -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/CALF6qJmD0JBuA2XE0X7Z4k=4z83f-a7aa8b0rrbubd3fjyj...@mail.gmail.com
