{"action":"opened","issue":{"url":"https://api.github.com/repos/gatling/gatling/issues/3608","repository_url":"https://api.github.com/repos/gatling/gatling","labels_url":"https://api.github.com/repos/gatling/gatling/issues/3608/labels{/name}","comments_url":"https://api.github.com/repos/gatling/gatling/issues/3608/comments","events_url":"https://api.github.com/repos/gatling/gatling/issues/3608/events","html_url":"https://github.com/gatling/gatling/issues/3608","id":381240429,"node_id":"MDU6SXNzdWUzODEyNDA0Mjk=","number":3608,"title":"Gatling hangs with negative active users and progress exceeding 100%","user":{"login":"nmutsanas","id":7649625,"node_id":"MDQ6VXNlcjc2NDk2MjU=","avatar_url":"https://avatars1.githubusercontent.com/u/7649625?v=4","gravatar_id":"","url":"https://api.github.com/users/nmutsanas","html_url":"https://github.com/nmutsanas","followers_url":"https://api.github.com/users/nmutsanas/followers","following_url":"https://api.github.com/users/nmutsanas/following{/other_user}","gists_url":"https://api.github.com/users/nmutsanas/gists{/gist_id}","starred_url":"https://api.github.com/users/nmutsanas/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nmutsanas/subscriptions","organizations_url":"https://api.github.com/users/nmutsanas/orgs","repos_url":"https://api.github.com/users/nmutsanas/repos","events_url":"https://api.github.com/users/nmutsanas/events{/privacy}","received_events_url":"https://api.github.com/users/nmutsanas/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-11-15T16:29:44Z","updated_at":"2018-11-15T16:29:44Z","closed_at":null,"author_association":"NONE","body":"Since migrating to gatling 3.0.0 yesterday we get invalid numbers in the progress console log: negative active users and overall progress that exceeds 100%. The loadtest seems to hang and needs to be aborted.\r\n\r\nSee log excerpt:\r\n`---- Foo -----------------------------------------------------------------------`\r\n`[###################################################################################]112%`\r\n`          waiting: 0      / active: -150   / done: 1350  `\r\n`================================================================================`\r\n\r\nA rerun of the loadtest exhibits the same problem with different numbers\r\n`---- Foo -----------------------------------------------------------------------`\r\n`[##########################################################################]101%`\r\n`          waiting: 0      / active: -13    / done: 1213  `\r\n`================================================================================`\r\n\r\n1200 users is what would be expected from the test setup\r\n\r\nThere is a second scenario that completed successfully in both runs\r\n\r\nIn both runs there are several warnings of the following form:\r\n`07:33:00.955 [WARN ] i.g.h.e.GatlingHttpListener - Request 'bar' failed for user 3291`\r\n`07:33:00.955 [WARN ] i.g.h.e.r.DefaultStatsProcessor - Request 'bar' failed for user 3291: i.g.h.c.i.RequestTimeoutException: Request timeout to xxxxx:1111 after 60000 ms\r\n`\r\nThe same nightly loadtest has been running without this issue on gatling 2.3 for a few weeks.\r\nThe same loadtests with fewer users have been ran successfully on gatling 3.0.0.\r\n\r\nThe next nightly is scheduled to run only the 'problematic' scenario. I will update this bug report if it behaves differently.\r\nAny hints on how to further narrow the problem down are appreciated."}}
{"actor":{"display_login":"nmutsanas"}}