Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Follow up from #2244513-203: Move the unmanaged file APIs to the file_system service (file.inc)
Running run-tests.sh with --browser gives you this:
Fatal error: Uncaught Error: Class 'FileSystemInterface' not found in /Users/paul/projects/drupal/core/scripts/run-tests.sh:1574 Stack trace: #0 /Users/paul/projects/drupal/core/scripts/run-tests.sh(173): simpletest_script_open_browser() #1 {main} thrown in /Users/paul/projects/drupal/core/scripts/run-tests.sh on line 1574
Needs a use Drupal\Core\File\FileSystemInterface; at the top.
Comment | File | Size | Author |
---|---|---|---|
#2 | 3037218-1.patch | 471 bytes | kim.pepper |
Comments
Comment #2
kim.pepperComment #3
dwwConfirmed the bug and the fix.
Not sure what a bot run is going to tell us, since clearly we don't have coverage for run-tests.sh --browser itself. ;)
Not sure how we could/should add tests for that.
RTBC.
Thanks!
-Derek
Comment #4
jibranWe can't test it until we fix #2624926: Refactor run-tests.sh for Console component..
Comment #5
jibranAnd #655178: Rename run-tests.sh to run-tests.php.
Comment #6
dwwSounds good. Thanks for the links. Now following. ;)
Cheers,
-Derek
Comment #7
Mile23There are ways to refactor to test for this. And I'll gladly do that work if someone sets this back to NW and says to. But it's basically one slice of #2624926: Refactor run-tests.sh for Console component. and probably too complex for this follow-up bugfix.
Comment #8
dww@Mile23 I vote we commit this as-is, and you spend your time (as desired) on the other linked issues. No sense slowing down an obvious fix for a fairly major bug in our testing world for refactoring that's been in the works for months/years.
Comment #9
alexpottCommitted 3f2ab9d and pushed to 8.7.x. Thanks!
Let's prioritise fixing this and testability can come later if necessary.
Comment #10
alexpottCrediting @dww for review and @Mile23 for finding the issue.