Just for testing patches.

CommentFileSizeAuthor
#15 testing3-2476407-119.patch12.75 KBhussainweb
#13 testing2-2476407-119.patch12.88 KBhussainweb
#12 testing2-2476407-119.patch11.24 KBhussainweb
#9 testing-2476407-119.patch12.86 KBhussainweb
#8 testing4-2476407-108.patch11.43 KBhussainweb
#5 test-2580147-5.patch801 byteshussainweb
#3 testing2-2476407-108.patch10.67 KBhussainweb
#2 testing-2476407-108.patch9.86 KBhussainweb

Comments

hussainweb created an issue. See original summary.

hussainweb’s picture

hussainweb
Primary language English
commented
Status: Active » Needs review
StatusFileSize
new testing-2476407-108.patch9.86 KB

Testing for #2476407-114: Use CacheableResponseInterface to determine which responses should be cached

hussainweb’s picture

hussainweb
Primary language English
commented
StatusFileSize
new testing2-2476407-108.patch10.67 KB

Testing a variation of the patch in #2.

hussainweb’s picture

hussainweb
Primary language English
commented
Priority: Normal » Minor
hussainweb’s picture

hussainweb
Primary language English
commented
StatusFileSize
new test-2580147-5.patch801 bytes

Adding a test for public files to check if there was a pre-existing problem in image download tests. Related to #2476407: Use CacheableResponseInterface to determine which responses should be cached.

The last submitted patch, 2: testing-2476407-108.patch, failed testing.

The last submitted patch, 2: testing-2476407-108.patch, failed testing.

hussainweb’s picture

hussainweb
Primary language English
commented
StatusFileSize
new testing4-2476407-108.patch11.43 KB

Combining patch in #5 with #2476407-108: Use CacheableResponseInterface to determine which responses should be cached

hussainweb’s picture

hussainweb
Primary language English
commented
StatusFileSize
new testing-2476407-119.patch12.86 KB

Adding another test to the patch in #2476407-119: Use CacheableResponseInterface to determine which responses should be cached

Status: Needs review » Needs work

The last submitted patch, 9: testing-2476407-119.patch, failed testing.

The last submitted patch, 9: testing-2476407-119.patch, failed testing.

hussainweb’s picture

hussainweb
Primary language English
commented
Status: Needs work » Needs review
StatusFileSize
new testing2-2476407-119.patch11.24 KB

Okay, let's see if we can fix the error.

hussainweb’s picture

hussainweb
Primary language English
commented
StatusFileSize
new testing2-2476407-119.patch12.88 KB

Wrong patch! Here's the correct one. This is the patch in #9 with a possible fix.

Status: Needs review » Needs work

The last submitted patch, 13: testing2-2476407-119.patch, failed testing.

hussainweb’s picture

hussainweb
Primary language English
commented
Status: Needs work » Needs review
StatusFileSize
new testing3-2476407-119.patch12.75 KB

Final fixes.

The last submitted patch, 13: testing2-2476407-119.patch, failed testing.

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

dpi’s picture

dpi
Location Perth, Australia
commented
Status: Needs review » Closed (won't fix)