ConfigImportAllTest tries to enable all available modules.
When running the test locally, this also includes whatever contrib modules might be present on the site. Meaning, you don't run what the testbot runs.
The test should limit itself to core modules ?
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | interdiff.txt | 866 bytes | yched |
| #6 | 2417817-ConfigImportAllTest_core_only-6.patch | 1000 bytes | yched |
| #1 | 2417817-ConfigImportAllTest_core_only-1.patch | 805 bytes | yched |
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!