#1786490: Add caching to the state system

The fight is on ;)

(Don't worry, just running that single test class. That previously passed, though)

CommentFileSizeAuthor
#21 2395143-57.patch16.91 KBberdir
#21 2395143-57.patch16.91 KBberdir
#21 2395143-57.patch16.91 KBberdir
#21 2395143-57.patch16.91 KBberdir
#21 2395143-57.patch16.91 KBberdir
#21 2395143-57.patch16.91 KBberdir
#21 2395143-57.patch16.91 KBberdir
#21 2395143-57.patch16.91 KBberdir
#21 2395143-57.patch16.91 KBberdir
#21 2395143-57.patch16.91 KBberdir
#21 2395143-57.patch16.91 KBberdir
#13 2395143-53.patch16.04 KBberdir
#13 2395143-53.patch16.04 KBberdir
#13 2395143-53.patch16.04 KBberdir
#13 2395143-53.patch16.04 KBberdir
#13 2395143-53.patch16.04 KBberdir
#13 2395143-53.patch16.04 KBberdir
#13 2395143-53.patch16.04 KBberdir
#13 2395143-53.patch16.04 KBberdir
#11 entity-get-system-path-2082049-11-interdiff.txt5.28 KBberdir
#11 entity-get-system-path-2082049-11.patch90.66 KBberdir
#9 entity-get-system-path-2082049-9-interdiff.txt16.42 KBberdir
#9 entity-get-system-path-2082049-9.patch88.64 KBberdir
#2 fakepatch.patch0 bytesberdir
#2 fakepatch.patch0 bytesberdir
#2 fakepatch.patch0 bytesberdir
#2 fakepatch.patch0 bytesberdir
#2 fakepatch.patch0 bytesberdir
#2 fakepatch.patch0 bytesberdir
#2 fakepatch.patch0 bytesberdir
#2 fakepatch.patch0 bytesberdir
#2 fakepatch.patch0 bytesberdir
#2 fakepatch.patch0 bytesberdir
#2 2190643-40.patch13.1 KBberdir
#2 2190643-40.patch13.1 KBberdir
#2 2190643-40.patch13.1 KBberdir
#2 2190643-40.patch13.1 KBberdir
#2 2190643-40.patch13.1 KBberdir
#2 2190643-40.patch13.1 KBberdir
#2 2190643-40.patch13.1 KBberdir
#2 2190643-40.patch13.1 KBberdir
#2 2190643-40.patch13.1 KBberdir
#2 2190643-40.patch13.1 KBberdir
come-on.patch12.27 KBberdir
come-on.patch12.27 KBberdir
come-on.patch12.27 KBberdir
come-on.patch12.27 KBberdir
come-on.patch12.27 KBberdir
come-on.patch12.27 KBberdir
come-on.patch12.27 KBberdir
come-on.patch12.27 KBberdir
come-on.patch12.27 KBberdir
come-on.patch12.27 KBberdir

Comments

berdir’s picture

Status: Active » Needs review

Well. 1 - 0 for DownloadTest. Setting to needs review would help.

berdir’s picture

Title: Ignore me: Berdir vs. DownloadTest » Ignore me: Berdir vs. Simpletest
Issue summary: View changes
StatusFileSize
new13.1 KB
new13.1 KB
new13.1 KB
new13.1 KB
new13.1 KB
new13.1 KB
new13.1 KB
new13.1 KB
new13.1 KB
new13.1 KB
new0 bytes
new0 bytes
new0 bytes
new0 bytes
new0 bytes
new0 bytes
new0 bytes
new0 bytes
new0 bytes
new0 bytes

Trying to figure out if #2190643: Serializing the container is a very very bad idea, let's prevent it? is helping with the testbot stability. Uploading 10x an empty patche and 10x the latest patch from there to see if we have any random failures.

Looks like queue on testbot is fairly low right now.

The last submitted patch, 2: 2190643-40.patch, failed testing.

The last submitted patch, 2: 2190643-40.patch, failed testing.

The last submitted patch, 2: fakepatch.patch, failed testing.

The last submitted patch, 2: fakepatch.patch, failed testing.

Status: Needs review » Needs work

The last submitted patch, 2: fakepatch.patch, failed testing.

The last submitted patch, 2: fakepatch.patch, failed testing.

berdir’s picture

Status: Needs work » Needs review
StatusFileSize
new88.64 KB
new16.42 KB

Go bot.

Status: Needs review » Needs work

The last submitted patch, 9: entity-get-system-path-2082049-9.patch, failed testing.

berdir’s picture

Status: Needs work » Needs review
StatusFileSize
new90.66 KB
new5.28 KB

Weird, I would have expected many more test fails, e.g. the page cache tag tests.

berdir’s picture

Oh. Those tests work because they absolute URL's.

berdir’s picture

StatusFileSize
new16.04 KB
new16.04 KB
new16.04 KB
new16.04 KB
new16.04 KB
new16.04 KB
new16.04 KB
new16.04 KB

Trying to find out how many randomly failing tests we have in #2395143: YAML parsing is very slow, cache it with FileCache.

The last submitted patch, 13: 2395143-53.patch, failed testing.

The last submitted patch, 13: 2395143-53.patch, failed testing.

The last submitted patch, 13: 2395143-53.patch, failed testing.

The last submitted patch, 13: 2395143-53.patch, failed testing.

The last submitted patch, 13: 2395143-53.patch, failed testing.

The last submitted patch, 13: 2395143-53.patch, failed testing.

The last submitted patch, 13: 2395143-53.patch, failed testing.

berdir’s picture

StatusFileSize
new16.91 KB
new16.91 KB
new16.91 KB
new16.91 KB
new16.91 KB
new16.91 KB
new16.91 KB
new16.91 KB
new16.91 KB
new16.91 KB
new16.91 KB

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.

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

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

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

berdir’s picture

Status: Needs review » Closed (outdated)

> alexpott: given Simpletest is no longer in core looks like you won!

I suppose so.