Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
configuration system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
31 Jan 2015 at 16:35 UTC
Updated:
17 Feb 2015 at 16:24 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
yched commentedpatch
Comment #2
yched commentedEasy RTBC ?
Comment #3
amateescu commentedVery easy :)
Comment #4
yched commented:-)
Along the same line : #2417839: Add code to ease debugging of ConfigImportAllTest fails
Comment #5
jibranThis comment needs update now.
Comment #6
yched commentedOops, indeed :-)
Just a comment fix, as the interdiff shows, so keeping at RTBC.
Comment #7
alexpottSo I'm ambivalent about this change. On one hand it means that modules laying around in your checkout don't influence test results and you run on the same code base as testbot - otoh - we've had this pattern with d7 and d8 for the module install/enable/uninstall/disable test. And if you get failures then it exposes bugs in those modules.
Comment #8
yched commentedA test should have a fixed scope as to what it tests ?
It's really weird that some test passes on the testbot and fails locally because of some stuff that happens to lie around on my disk outside the core/ folder ?
Comment #9
alexpottWell the scope in your codebase :) but I'm not that fussed and if it helps so that people won't moan about this test then yay. Committed 3207072 and pushed to 8.0.x. Thanks!