D6 CCK tests fail on d.o. even though they work locally

This is pure speculation, and without actually looking into the problem with any detail, but the comments in the test indicate that the tests require the 'Schema' module to be installed ... but unless it is listed as a dependency in the .info file, the testbot will not download and install the schema module when running the branch test.

You may be able to confirm this theory by disabling the Schema module in your local install and attempting to run the tests again, comparing the results with those returned by the testbot.

Actually, *remove* schema, not disable. If it's not available to the tests, that will be the same situation as on the testbot.

Alternately, commit adding schema module as a dependency of one of the modules.

I definitely see "Undefined index: Schema" on http://qa.drupal.org/pifr/test/52378 when it tries to enable modules. That's going to be the (first) problem.

Your tests require schema... There's no way the testbot can know to check out schema if you don't tell it somehow. Dependencies are inferred from the dependencies listed in info files.

Make schema a dependency of a mock module (a module used only by the tests) and everything will suddenly work out.

Adding a module to setUp() will enable it... If it exists on the system. Otherwise it will result in an error (exactly what you're getting). If you rm schema from your local install you'll get the same result.

But as you know, one cannot enable a module that does not already exist on the drupal site. That is the problem we're having here.

setUp() tells *simpletest* to enable a module in the version of the system that it has created.

dependencies[] tells Drupal whether a module can be enabled successfully or not.

In addition, the Project Dependency module searches all the dependencies listed in dependencies[] to find what ought to be actually checked out when testing a given project. Then the testbot uses that information to check out the necessary dependencies.

Hope that makes some sense.

Thanks as always for *all* your incredible work in all these incredible places.

Karen,

There is an open issue in the PIFR queue (or PIFT, I forget which) about enabling 'soft' dependencies on the testbot, which I believe may address this particular situation ... But for now, the testbot only supports hard dependencies as listed in the .info file. Not ideal, but better than what we had before project_dependency. :)

The 'soft dependencies' issue I was referring to got moved to Project Dependency, located at #698932: "test_dependencies" for dependencies / integration tests.

Sorry, I should have mentioned that the dependencies get calculated when the new dev release gets rolled. And as of now, schema is calculated as a dependency of 6.x-2.x:

drush pdsd cck 6.x-2.x-dev
Array
(
    [701568] => Array
        (
            [uri] => schema
            [version] => 6.x-1.7-rc1
            [tag] => 6.x-1.7-rc1
        )

)

So just to make this clear, if we change info files and commit. Do a test right afterwards it will not have the needed dependencies until a new dev is rolled? Any way to enforce this change?

@Nick_vh you do understand correctly. I'm going to update the FAQ on the project page. As you have found out, I can use Jenkins to rebuild, but I don't know of a way for an unprivileged user to do it at this point. A feature request in project_dependency would be welcome. It sure makes sense to me.

So rfay ... we basically need to duplicate the same commit hook that's used in pift, and have it call project_dependency_[something], correct? Which project_dependency function is the one that performs the rebuild?

Where are we at with this?

Still having problems with tests failing on d.o, but passing locally.
http://qa.drupal.org/pifr/test/56483

Looks to me like jquery_ui is not being properly enabled.

jthorson implied this might be because jquery_ui is not explicitly defined as a dependancy in date module... (see #973924: jquery_ui dependency not in .info file for why that is)

@arlinsandbulte, please open new issues for new specific problems (this is a new one, right)

If you need jquery_ui, and it's not somewhere in the dependency chain, it will not be loaded by the test.

A workaround for this is to create a "mock module" in a test subdirectory (or perhaps you already have one) and make it have a dependency on jquery _ui.

DOH! I thought this was about the CCK *DATE* module!
Sorry for the noise.