Flaky test `cache_test`

[silverwind]

--- FAIL: TestTest (0.00s)
    cache_test.go:46: 
        	Error Trace:	/home/runner/work/gitea/gitea/modules/cache/cache_test.go:46
        	Error:      	"189.488µs" is not less than "100µs"
        	Test:       	TestTest
2024/11/27 04:45:56 ...les/cache/context.go:135:GetContextData() [W] cache context is expired, is highly likely to be misused for long-life tasks: &{map[system_setting:map[my_config1:1]] {{0 0} 0 0 {{} 0} {{} 0}} {13963910789408841798 6417129 0x1092460} false}
FAIL

https://github.com/go-gitea/gitea/actions/runs/12043787826/job/33579745667?pr=32649

[wxiaoguang]

I still insist my point: it's not quite right to test cache by this approach.

#31265 (comment)

[TheFox0x7]

This also impacts self-tests when using redis/memcache where the base delay is larger than the threshold and always triggers the slow warning

It would be better to make it informative instead of a warning or to make the threshold larger as it only works correctly in memory/twoqueue.
This could be also included in /metrics as histogram.

@6543 Pinging since you're the author of this - Is there any reason as to why 0.1 milliseconds?

[wxiaoguang]

It believe it could be removed or changed.