Closed (fixed)
Project:
Drupal core
Version:
6.x-dev
Component:
taxonomy.module
Priority:
Normal
Category:
Bug report
Assigned:
Issue tags:
Reporter:
Created:
20 Feb 2010 at 20:51 UTC
Updated:
3 Jan 2014 at 01:08 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
dave reidPatch attached for review.
This is the test that was failing because of the data leaking inbetween test runs:
Comment #2
rfayI guess I have two questions about this:
1. If it's leaking between tests, is it just that the tests are trying to tell us there's a flaw in the code? We shouldn't have to modify code being tested to get it to pass tests....
2. This is actually an API change, although it won't break anything, of course. Does it seem likely you can convince the powers that be that it's important enough?
Is there another way to solve this problem? Is there a bug in the code that we have to ferret out?
Comment #3
dave reid1. Unfortunately is a bug in the code we'd only see when using tests. You could technically do the same thing in a standalone script that can use the Drupal APIs:
2. Well it's either we get this into D6 core, or we have to put anything like this into SimpleTests's core patch. It would be easier to fix it in core. But its not my decision to make.
Comment #4
andypost@Dave suppose you mean
This is really a core bug so let's wait Gabor's opinion
Comment #5
gábor hojtsyThanks, committed.
Comment #6
lfranck commentedAs we fetch objects one by one, using tid or vid, why do we need to flush all the cache on reset = TRUE, instead of flushing the related tid|vid cache like, for example :
Comment #7
dave reidThe point is to clear the *entire* cache, not just for the individual term. This works exactly the same as other similar static caching functions in core:
So I don't think it's appropriate for a follow-up.