Hey,

We want to put #318975: Remove confirmation page after installation into core, can we remove this in the testbot?

Regards,

Bojhan

Comments

jthorson’s picture

Status: Active » Postponed
sun’s picture

Category: Feature request » Task
Issue summary: View changes
Status: Postponed » Needs review
StatusFileSize
new576 bytes

I may be mistaken, but I've the impression that we have consensus on #318975: Remove confirmation page after installation in the meantime.

sun’s picture

Could we move forward here?

I've the impression that people do not want to RTBC the core patch, because it contains a temporary hack for PIFR :-/

Bojhan’s picture

Status: Needs review » Reviewed & tested by the community

We will see what the comitter says.

jthorson’s picture

Revisiting this, I would still like to assert *something*, as I've seen bots fail and return a white screen at this point in the past. That said, we should definitely put this on the Szeged agenda, and my Drupal vacation ends in the morning. ;)

sun’s picture

Once #1808220: Remove run-tests.sh dependency on existing/installed parent site is fully deployed to PIFR/testbots, tests for D8 won't go through this manual installation code in PIFR in the first place.

For D8, we have proper tests for the interactive installer in Drupal core already — PIFR does not need to confirm anything manually beyond those tests.

For previous versions, this check could still be useful. → Instead of removing the line, let's wrap it in a version condition < 8.x?

jthorson’s picture

Yup ... I can support that.

moshe weitzman’s picture

FYI, this "hidden" code shows up for all Drush installs so it would be nice to remove it.

jthorson’s picture

Remove the code ... this assertion no longer exists, now that the bots are all using the 6.x-3.x branch. It was removed when the testbot was converted over to use drush si for installs.

Not marking as 'fixed' quite yet, because I don't want this to fall off the radar, given that there are also issues to remove the drush dependency on testbot.

jthorson’s picture

Status: Reviewed & tested by the community » Postponed
tstoeckler’s picture

Per #2274167-241: [ignore] Patch testing issue it seems the code in core is no longer needed. Is it safe now to remove it?

jthorson’s picture

As per #9, it should now be safe to remove it ... a quick scan through the file referenced in the patch on this issue (which I haven't done recently) could be done to confirm I wasn't imagining things when I wrote that. :)

tstoeckler’s picture

So I checked and 6.x-3.x no longer contains any such assertion (here's the relevant file: http://cgit.drupalcode.org/project_issue_file_review/tree/review/drupal/... ; I also did a full grep on the PIFR codebase and the corresponding string is nowhere to be found)

So I'm assuming that means this can be closed?!

tstoeckler’s picture

Status: Postponed » Fixed

The Drupal core issue got in (see related issues), so closing this now.

Status: Fixed » Closed (fixed)

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