This is a minor 'test' release to verify an issue with the heartbeat ------------------ RELEASE NOTES ------------------ https://github.com/mozilla-services/loop-server/releases COMPARISONS https://github.com/mozilla-services/loop-server/compare/0.15.3...0.15.4 https://github.com/mozilla-services/loop-server/compare/0.15.4...0.15.5 https://github.com/mozilla-services/loop-server/compare/0.15.5...0.15.6 TAGS https://github.com/mozilla-services/loop-server/releases/tag/0.15.6 https://github.com/mozilla-services/loop-server/commit/819c382696311de123f3f077c074ea62db5eba7b
This has been pushed to stage.
Assignee: nobody → bobm
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
Cool, we need to do a quick verification (loadtest) here but nothing has really changed since the last tag so we should be okay.
No longer blocks: 1125788
Hi Tarek, the loadstool is back up again (thank you!), but for some reason every test is dying after 5-10 seconds even though I've restarted circus on all hosts several times. Is there something I can check on this?
It looks like the test itself eats memory too fast. Maybe there's something to tweak there.
thanks, Tarek, good catch. Do you want me to file a bug to address this or do you guys have it?
Please file a bug and cc alexis When this happens you can simply terminate the broken loads aws agents box. Aws will automatically start new nodes for you.
You need to log in before you can comment on or make changes to this bug.