Follow-up to #2764687: IpAddressBlockingTest is failing on DrupalCI

Problem/Motivation

Drupal\Tests\ban\Functional\IpAddressBlockingTest is failing consistently on DrupalCI PHP 7 test runs on 8.1.x and 8.2.x for all database types. For example https://www.drupal.org/pift-ci-job/368089.

PHP 7 version on DrupalCI is 7.0.10-dev. I've run this locally on PHP 7.0.6 and it passes. Running DrupalCI locally still results in failure. This suggests that this might be due to a change in PHP.

Proposed resolution

Replace 192.168.1.1 with 1.2.3.3.

Remaining tasks

- Replace 192.168.1.1 with 1.2.3.3 in statistics.test as well

User interface changes

API changes

Data model changes

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

stefan.r created an issue. See original summary.

stefan.r’s picture

Status: Patch (to be ported) » Needs review
FileSize
991 bytes
Fabianx’s picture

Title: IpAddressBlockingTest is failing on DrupalCI » [D7] IpAddressBlockingTest is failing on DrupalCI
Priority: Major » Critical
Status: Needs review » Needs work
Issue tags: +Novice

Need to fix https://api.drupal.org/api/drupal/modules!statistics!statistics.test/fun... as well, by changing 192.168.1.1 to 1.2.3.3.

Fabianx’s picture

Title: [D7] IpAddressBlockingTest is failing on DrupalCI » [D7] IpAddressBlockingTest is failing on DrupalCI for PHP 7
Issue summary: View changes
GoZ’s picture

Status: Needs work » Needs review
FileSize
2.22 KB
Fabianx’s picture

Status: Needs review » Reviewed & tested by the community
Issue tags: -Novice +Pending Drupal 7 commit

Thank you for your contribution!

Marking for commit, gave me and stefan credit as we re-investigated the issue, then re-found the D8 issue (which took some time).

  • Fabianx committed 29473bd on 7.x
    Issue #2784561 by stefan.r, GoZ, Fabianx: [D7] IpAddressBlockingTest is...
Fabianx’s picture

Status: Reviewed & tested by the community » Fixed
Issue tags: -Pending Drupal 7 commit

Committed and pushed to 7.x! Thanks!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.