{"action":"opened","issue":{"url":"https://api.github.com/repos/mypyc/mypyc/issues/486","repository_url":"https://api.github.com/repos/mypyc/mypyc","labels_url":"https://api.github.com/repos/mypyc/mypyc/issues/486/labels{/name}","comments_url":"https://api.github.com/repos/mypyc/mypyc/issues/486/comments","events_url":"https://api.github.com/repos/mypyc/mypyc/issues/486/events","html_url":"https://github.com/mypyc/mypyc/issues/486","id":370372511,"node_id":"MDU6SXNzdWUzNzAzNzI1MTE=","number":486,"title":"More sophisticated test system for testing IR generation","user":{"login":"msullivan","id":340349,"node_id":"MDQ6VXNlcjM0MDM0OQ==","avatar_url":"https://avatars2.githubusercontent.com/u/340349?v=4","gravatar_id":"","url":"https://api.github.com/users/msullivan","html_url":"https://github.com/msullivan","followers_url":"https://api.github.com/users/msullivan/followers","following_url":"https://api.github.com/users/msullivan/following{/other_user}","gists_url":"https://api.github.com/users/msullivan/gists{/gist_id}","starred_url":"https://api.github.com/users/msullivan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/msullivan/subscriptions","organizations_url":"https://api.github.com/users/msullivan/orgs","repos_url":"https://api.github.com/users/msullivan/repos","events_url":"https://api.github.com/users/msullivan/events{/privacy}","received_events_url":"https://api.github.com/users/msullivan/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-10-15T22:45:59Z","updated_at":"2018-10-15T22:45:59Z","closed_at":null,"author_association":"COLLABORATOR","body":"Currently we just directly assert the IR output matches the test case, which has a bunch of problems:\r\n\r\n1. Any given test usually only cares about certain salient features of the output, so there is a lot of extra noise unrelated to what we are testing.\r\n2. The salient features are often not made clear, so it sometimes we can miss important changes when updating tests.\r\n3. Some changes induce a lot of test churn in tests that are unrelated to the core thing being changed.\r\n\r\nIt would be good to have some sort of system that allows specifying *what* we care about in the IR, and looking for just that. \r\n\r\nIt's probably worth looking into how clang/LLVM test IR generation and whether they have an approach we can adapt."}}
{"actor":{"display_login":"msullivan"}}