{"action":"closed","issue":{"url":"https://api.github.com/repos/d11wtq/dockerpty-restored-2/issues/20","labels_url":"https://api.github.com/repos/d11wtq/dockerpty-restored-2/issues/20/labels{/name}","comments_url":"https://api.github.com/repos/d11wtq/dockerpty-restored-2/issues/20/comments","events_url":"https://api.github.com/repos/d11wtq/dockerpty-restored-2/issues/20/events","html_url":"https://github.com/d11wtq/dockerpty-restored-2/issues/20","id":107831900,"number":20,"title":"Feature Failure in dockerpty-0.2.4","user":{"login":"d11wtq","id":37948,"avatar_url":"https://avatars.githubusercontent.com/u/37948?v=3","gravatar_id":"","url":"https://api.github.com/users/d11wtq","html_url":"https://github.com/d11wtq","followers_url":"https://api.github.com/users/d11wtq/followers","following_url":"https://api.github.com/users/d11wtq/following{/other_user}","gists_url":"https://api.github.com/users/d11wtq/gists{/gist_id}","starred_url":"https://api.github.com/users/d11wtq/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/d11wtq/subscriptions","organizations_url":"https://api.github.com/users/d11wtq/orgs","repos_url":"https://api.github.com/users/d11wtq/repos","events_url":"https://api.github.com/users/d11wtq/events{/privacy}","received_events_url":"https://api.github.com/users/d11wtq/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-09-23T00:53:41Z","updated_at":"2015-09-23T00:53:43Z","closed_at":"2015-09-23T00:53:43Z","body":"#20 Issue by __alunduil__, created on: 2014-10-26T15:38:43Z\n\nI'm packaging up dockerpty for Gentoo. While running the tests that include docker, I came across only one failure.  I'm having a hard time determining if the failure was caused by the system or something in the code and am petitioning here for a few pointers as to what causes of this particular failure might be:\r\n\r\n```\r\n  Scenario: Resizing the PTY frenetically                # features/interactive_terminal.feature:101\r\n    Given I am using a TTY with dimensions 20 x 70       # features/steps/step_definitions.py:36\r\n    And I run \"/bin/sh\" in a docker container with a PTY # features/steps/step_definitions.py:42\r\n    When I start dockerpty                               # features/steps/step_definitions.py:74\r\n    And I resize the terminal to 30 x 100                # features/steps/step_definitions.py:102\r\n    And I resize the terminal to 30 x 101                # features/steps/step_definitions.py:102\r\n    And I resize the terminal to 30 x 98                 # features/steps/step_definitions.py:102\r\n    And I resize the terminal to 28 x 98                 # features/steps/step_definitions.py:102\r\n    And I resize the terminal to 28 x 105                # features/steps/step_definitions.py:102\r\n    And I wait 3 seconds                                 # features/steps/step_definitions.py:135\r\n    And I type \"stty size\"                               # features/steps/step_definitions.py:113\r\n    And I press ENTER                                    # features/steps/step_definitions.py:118\r\n    Then I will see the output                           # features/steps/step_definitions.py:141\r\n      \"\"\"\r\n      / # stty size\r\n      28 105\r\n      / #\r\n      \"\"\"\r\n      Assertion Failed: Expected ['/ # stty size', '30 100', '/ #'] to equal [u'/ # stty size', u'28 105', u'/ #']\r\n```\r\n\r\nMy first thoughts are that the system was not performing as expected and the three second delay is not enough to consistently make this test pass.  I just want to get some confirmation that this hypothesis is reasonable and I will be doing a follow up test if necessary with a longer sleep.  The entire build log is here, https://bpaste.net/show/fbb5749bac95, if needed.\r\n\r\nSince everything else passes, I assume I can conclude that the packaging is correct and the environment is properly configured but I would also like someone else's confirmation.\r\n\r\nAny guidance is appreciated and thanks in advance."}}