Coming from #1378058-5: Calling field_attach_load corrupts the field cache on user logout

Certain tests need to verify diverse actions being executed in more than one user session.

We have a session system, we can use it, and SimpleTest is sufficiently prepared already to make our lives easier.

CommentFileSizeAuthor
#9 drupal8.simpletest-multisession.8.patch7.54 KBbdragon
#7 drupal8.simpletest-multisession.7.patch7.37 KBsun
#5 drupal8.simpletest-multisession.5.patch7.44 KBsun
#3 drupal8.simpletest-multisession.3.patch7.42 KBsun
#1 drupal8.simpletest-multisession.1.patch3.57 KBsun
drupal8.simpletest-multisession.0.patch3.46 KBsun

Comments

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
StatusFileSize
new drupal8.simpletest-multisession.1.patch3.57 KB

Minor clean-ups.

Status: Needs review » Needs work

The last submitted patch, drupal8.simpletest-multisession.1.patch, failed testing.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Status: Needs work » Needs review
Issue tags: +Testing system
StatusFileSize
new drupal8.simpletest-multisession.3.patch7.42 KB

Re-rolled against HEAD and completely refactored after functional testing with Conflict module: https://drupal.org/sandbox/bdragon/1599370

Status: Needs review » Needs work

The last submitted patch, drupal8.simpletest-multisession.3.patch, failed testing.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Status: Needs work » Needs review
StatusFileSize
new drupal8.simpletest-multisession.5.patch7.44 KB

Ah-ha. Minimal tweak required.

Status: Needs review » Needs work

The last submitted patch, drupal8.simpletest-multisession.5.patch, failed testing.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Status: Needs work » Needs review
StatusFileSize
new drupal8.simpletest-multisession.7.patch7.37 KB

One more tweak.

Status: Needs review » Needs work

The last submitted patch, drupal8.simpletest-multisession.7.patch, failed testing.

bdragon’s picture

bdragon commented
Status: Needs work » Needs review
StatusFileSize
new drupal8.simpletest-multisession.8.patch7.54 KB

Rerolled.

The last submitted patch, drupal8.simpletest-multisession.8.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.

dawehner’s picture

dawehner
Primary language German
commented
Issue summary: View changes
Status: Needs work » Fixed

Mink has the necessary abstractions we need for this usecase. Given that this issue is not longer needed.

Status: Fixed » Closed (fixed)

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