Two of my modules had patches submitted by @crell recently and both of them add a new dependency to the modules in question:

I have not been able to reproduce the errors I am seeing reported by testbot on D.O. locally (or on simplytest.me) and neither has @crell. That said, I have noticed that even though all tests pass when run locally through the GUI, when I run them using Drush see failures (admin_user cannot login). These failures are different than those reported by testbot which fail on enabling modules during setup.

I've had issues in the past where adding a new dependency has caused testbot to become disgruntled and @rfay has had to reset something (not sure what) to get me up and running again. That was a while ago though.

Any thoughts?

Comments

bleen’s picture

bleen CreditAttribution: bleen commented
Issue summary: View changes
bleen’s picture

bleen CreditAttribution: bleen commented

nudge ... any help here would be greatly appreciated

Mixologic’s picture

Mixologic
He/Him/His
Primary language English
Location Portland, OR
CreditAttribution: Mixologic at Drupal Association commented
Status: Active » Closed (outdated)

Marking this outdated. On the old testbots, and currently in drupalci, dependencies are only calculated at packaging time, you cannot add one during patch time, so the only way to test something that adds a new dependency is to make a commit that adds the dependency, then test the patch. We're working on fixing that to not be broken like that.