#1239 assigned defect

document why package dependencies not auto-satisfied on test-from-prefixdir and test-with-fake-pkg steps

Reported by: midnightmagic Owned by: zooko
Priority: major Milestone: undecided
Component: code Version: 1.8.0
Keywords: packaging buildbot build-helpers setuptools Cc:
Launchpad Bug:

Description (last modified by daira)

See the error message:

"Traceback (most recent call last):
  File "/home/tahoe/buildslave/tahoe/netbsd5-i386/build/src/../misc/build_helpers/run_trial.py", line 14, in <module>
    __import__(modulename)
  File "/home/tahoe/buildslave/tahoe/netbsd5-i386/build/src/allmydata/__init__.py", line 27, in <module>
    import nevow
ImportError: No module named nevow"

Here: http://tahoe-lafs.org/buildbot/builders/MM%20netbsd5%20i386%20warp/builds/108/steps/test-with-fake-pkg/logs/stdio

When Nevow is manually installed, this error happens: http://tahoe-lafs.org/buildbot/builders/MM%20netbsd5%20i386%20warp/builds/106/steps/test-from-prefixdir/logs/stdio

Change History (9)

comment:1 Changed at 2010-10-29T21:36:49Z by warner

  • Description modified (diff)

fixed formatting

comment:2 Changed at 2010-10-29T23:27:17Z by zooko

The "build" and "test" steps automatically resolve dependencies. The test-from-prefixdir and run-test-with-fake-pkg steps do not.

This is kind of a problem, but it is also potentially useful information to see how a build system without automatic dependency resolution (such as, potentially, Brian's unsuck branch?) would fare on our current buildslaves.

comment:3 Changed at 2010-10-29T23:27:48Z by zooko

  • Summary changed from Nevow package dependency not auto-satisfied to package dependencies not auto-satisfied on test-from-prefixdir and run-test-with-fake-pkg

comment:4 Changed at 2010-10-29T23:40:21Z by davidsarah

  • Component changed from unknown to code
  • Owner changed from nobody to somebody
  • Priority changed from minor to major
  • Summary changed from package dependencies not auto-satisfied on test-from-prefixdir and run-test-with-fake-pkg to package dependencies not auto-satisfied on test-from-egg, test-from-prefixdir and test-with-fake-pkg steps

This also applies to the test-from-egg step.

comment:5 Changed at 2010-10-29T23:44:28Z by davidsarah

  • Summary changed from package dependencies not auto-satisfied on test-from-egg, test-from-prefixdir and test-with-fake-pkg steps to package dependencies not auto-satisfied on test-from-prefixdir and test-with-fake-pkg steps

Oh, I'm mistaken. test-from-egg does auto-resolve dependencies (compare this test-from-egg and this test-from-prefixdir).

comment:6 Changed at 2010-12-01T20:05:59Z by davidsarah

  • Keywords packaging buildbot build-helpers setuptools added

comment:7 Changed at 2010-12-03T02:23:45Z by zooko

I don't think this is a bug. The test-from-prefixdir step is supposed to test what happens when there isn't automatic resolution of dependencies. How about if we change this ticket to "test-from-prefixdir is badly named and ill-documented so people don't realize that it is supposed to be testing the traditional no-automatic-dependencies install"? :-)

comment:8 Changed at 2011-01-14T23:42:51Z by zooko

  • Owner changed from somebody to zooko
  • Status changed from new to assigned
  • Summary changed from package dependencies not auto-satisfied on test-from-prefixdir and test-with-fake-pkg steps to document why package dependencies not auto-satisfied on test-from-prefixdir and test-with-fake-pkg steps

I'm assigning this to myself to organize and document the test-from-prefixdir step so that people like Brian understand what it is supposed to do.

comment:9 Changed at 2013-08-27T12:14:59Z by daira

  • Description modified (diff)

Maybe this ticket is invalid, if python setup.py install is actually supposed to install dependencies (#1494 and #2063).

Note: See TracTickets for help on using tickets.