[MAGNOLIA-4135] m_main-trunk-forked-test fail now and then because of test-failure in m-m-cache Created: 21/Mar/12  Updated: 09/May/23  Resolved: 21/Mar/12

Status: Closed
Project: Magnolia
Component/s: cache
Affects Version/s: 4.4.6, 4.5.1
Fix Version/s: 4.4.7, 4.5.2

Type: Bug Priority: Major
Reporter: Daniel Lipp Assignee: Daniel Lipp
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLCACHE-294 Expand options for browser cache cont... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

e.g. Error Message:

Unexpected method call setHeader("Cache-Control", "max-age=1799, public"): setHeader("Pragma", ""): expected: 1, actual: 1 setHeader("Cache-Control", "max-age=1800, public"): expected: 1, actual: 0

-> we expected a call of setHeader("Cache-Control", "max-age=1800, public") but actually got a call with max-age=1799

full details: http://hudson.magnolia-cms.com/view/X/job/magnolia_main-trunk-forked-tests/1126/


Generated at Mon Feb 12 03:53:00 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.