Closed (fixed)
Project:
Flag
Version:
8.x-4.x-dev
Component:
Flag core
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
7 Sep 2015 at 20:43 UTC
Updated:
11 Oct 2015 at 20:44 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
joachim commentedComment #4
joshi.rohit100I think wrong core version.
Comment #5
joachim commentedHaha. Thanks!
Comment #8
rashid_786 commentedComment #10
giancarlosotelo commentedFails are not related.
See #2565501: Tests are not working because Dynamic page cache was committed in core.
Comment #12
joachim commentedDid either of you try it out? What should happen is without the patch, the saved flag doesn't have a 'weight' property (in the config table). With the patch, it does. (The weight is always 0 because there's no UI yet, but that comes later...)
Comment #13
socketwench commentedSo something in this patch is causing the test to stall. Looks like it happened to testbot, but also can confirm the behavior locally. It doesn't last more than a minute or two locally, but that may be why Testbot cancels out and never returns results.
Once the tests do complete, the weight is persisted to configuration.
Comment #15
socketwench commented15 hours later and still stuck. :-/
Comment #16
joachim commentedWell it passed again here, so I'm pretty sure it's a problem with your system somehow.
Comment #17
socketwench commentedYeah, it was my system. I was asking too much of it at the time and it stalled.
Comment #19
socketwench commentedAnd fixed. Thanks!