{"action":"closed","issue":{"url":"https://api.github.com/repos/catchorg/Catch2/issues/1120","repository_url":"https://api.github.com/repos/catchorg/Catch2","labels_url":"https://api.github.com/repos/catchorg/Catch2/issues/1120/labels{/name}","comments_url":"https://api.github.com/repos/catchorg/Catch2/issues/1120/comments","events_url":"https://api.github.com/repos/catchorg/Catch2/issues/1120/events","html_url":"https://github.com/catchorg/Catch2/issues/1120","id":278864629,"number":1120,"title":"Stdout capturing is wonky","user":{"login":"ibell","id":1859947,"avatar_url":"https://avatars2.githubusercontent.com/u/1859947?v=4","gravatar_id":"","url":"https://api.github.com/users/ibell","html_url":"https://github.com/ibell","followers_url":"https://api.github.com/users/ibell/followers","following_url":"https://api.github.com/users/ibell/following{/other_user}","gists_url":"https://api.github.com/users/ibell/gists{/gist_id}","starred_url":"https://api.github.com/users/ibell/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ibell/subscriptions","organizations_url":"https://api.github.com/users/ibell/orgs","repos_url":"https://api.github.com/users/ibell/repos","events_url":"https://api.github.com/users/ibell/events{/privacy}","received_events_url":"https://api.github.com/users/ibell/received_events","type":"User","site_admin":false},"labels":[{"id":513090088,"url":"https://api.github.com/repos/catchorg/Catch2/labels/Query","name":"Query","color":"1d76db","default":false},{"id":513090349,"url":"https://api.github.com/repos/catchorg/Catch2/labels/Resolved%20-%20pending%20review","name":"Resolved - pending review","color":"5319e7","default":false}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":7,"created_at":"2017-12-04T04:05:14Z","updated_at":"2018-02-08T14:35:51Z","closed_at":"2018-02-08T14:35:51Z","author_association":"NONE","body":"## Description\r\n\r\nThe capturing of stdout seems to not be working properly for me.  On linux, all stdout seems to be swallowed and none of it makes it to the console.  On the other hand, when I run the below example in wandbox, none of the stdout gets captured at all, and all of it makes it to the console.  What gives?\r\n\r\nI swear this worked correctly in Catch 1.x\r\n\r\nIs there a compilation flag I need to modify to get the Catch 1.x behavior where passing tests capture and swallow the stdout, and failing tests print out the captured stdout as part of the failure message?\r\n\r\n### Steps to reproduce\r\n``` c++\r\n#define CATCH_CONFIG_MAIN  // This tells Catch to provide a main() - only do this in one cpp file\r\n#include \"catch.hpp\"\r\n\r\nTEST_CASE(\"Check string capturing\", \"[capturing]\")\r\n{\r\n    SECTION(\"Captured?\", \"[capture]\"){\r\n        std::cout << \"should capture\\n\";\r\n        CHECK(1==0);\r\n    }\r\n    SECTION(\"Captured?22\", \"[capture]\"){\r\n        std::cout << \"should not capture\\n\";\r\n        CHECK(0==0);\r\n    }\r\n}\r\n```\r\n\r\nyields\r\n```\r\nshould capture\r\n\r\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\r\nprog.exe is a Catch v2.0.1 host application.\r\nRun with -? for options\r\n\r\n-------------------------------------------------------------------------------\r\nCheck string capturing\r\n  Captured?\r\n-------------------------------------------------------------------------------\r\nprog.cc:7\r\n...............................................................................\r\n\r\nprog.cc:9: FAILED:\r\n  CHECK( 1==0 )\r\nwith expansion:\r\n  1 == 0\r\n\r\nshould not capture\r\n===============================================================================\r\ntest cases: 1 | 1 failed\r\nassertions: 2 | 1 passed | 1 failed\r\n```\r\n"}}
{"actor":{"display_login":"horenmar"}}