On 04/21/2018 08:23 AM, Helmut Grohne wrote: > Control: severity 896234 normal > Control: severity 896242 normal > Control: severity 896272 normal > Control: severity 896306 normal > Control: severity 896307 normal > Control: severity 896328 normal > Control: severity 896378 normal > Control: severity 896396 normal > Control: severity 896429 normal > > I have lowered the severity of the relevant bugs (matching > "ImproperlyConfigured") to prevent issues with testing migration.
Instead, please *CLOSE* those bugs unless you've done proper testing. > I wonder whether we can draw anything useful from these bugs before > closing them. Unless you try to setup a working Django env before doing the import, I'm afraid you can't draw anything. > So yeah, for django this may make sense, but this behaviour is still > unfortunate from a qa pov. Feel free to raise this on a Django upstream message. I very much agree this isn't best. > After the dust has settled, I can follow up on d-devel with a summary > that suggests filtering this particular django exception. Again, instead you could setup a working Django environment and restart the tests. I'm not sure how hard that would be though. Cheers, Thomas Goirand (zigo)