{"action":"created","issue":{"url":"https://api.github.com/repos/g-truc/glm/issues/396","labels_url":"https://api.github.com/repos/g-truc/glm/issues/396/labels{/name}","comments_url":"https://api.github.com/repos/g-truc/glm/issues/396/comments","events_url":"https://api.github.com/repos/g-truc/glm/issues/396/events","html_url":"https://github.com/g-truc/glm/issues/396","id":105102970,"number":396,"title":"Reduce the time it takes to run the tests","user":{"login":"muep","id":47061,"avatar_url":"https://avatars.githubusercontent.com/u/47061?v=3","gravatar_id":"","url":"https://api.github.com/users/muep","html_url":"https://github.com/muep","followers_url":"https://api.github.com/users/muep/followers","following_url":"https://api.github.com/users/muep/following{/other_user}","gists_url":"https://api.github.com/users/muep/gists{/gist_id}","starred_url":"https://api.github.com/users/muep/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/muep/subscriptions","organizations_url":"https://api.github.com/users/muep/orgs","repos_url":"https://api.github.com/users/muep/repos","events_url":"https://api.github.com/users/muep/events{/privacy}","received_events_url":"https://api.github.com/users/muep/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-09-06T16:36:15Z","updated_at":"2015-09-06T18:09:26Z","closed_at":null,"body":"Some tests in the glm test suite seem to be a bit wasteful in their use of CPU time.\r\n\r\nFor example, gtx_fast_trigonometry.cpp seems to go through the trouble of testing functions with every possible float value between -glm::pi() and glm::pi(). On my midrange-ish desktop, running that test in release mode takes more than 3 minutes.\r\n\r\n I am fairly sure that testing e.g. just one percent of those possible values would give a quite accurate view on how fast those functions are.\r\n\r\nFortunately, most of the tests in the test suite produce useful results in a fraction of a second here. Making the CPU intensive ones run e.g. within ten seconds on usual hardware would make it way less cumbersome to run the whole suite."},"comment":{"url":"https://api.github.com/repos/g-truc/glm/issues/comments/138104754","html_url":"https://github.com/g-truc/glm/issues/396#issuecomment-138104754","issue_url":"https://api.github.com/repos/g-truc/glm/issues/396","id":138104754,"user":{"login":"muep","id":47061,"avatar_url":"https://avatars.githubusercontent.com/u/47061?v=3","gravatar_id":"","url":"https://api.github.com/users/muep","html_url":"https://github.com/muep","followers_url":"https://api.github.com/users/muep/followers","following_url":"https://api.github.com/users/muep/following{/other_user}","gists_url":"https://api.github.com/users/muep/gists{/gist_id}","starred_url":"https://api.github.com/users/muep/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/muep/subscriptions","organizations_url":"https://api.github.com/users/muep/orgs","repos_url":"https://api.github.com/users/muep/repos","events_url":"https://api.github.com/users/muep/events{/privacy}","received_events_url":"https://api.github.com/users/muep/received_events","type":"User","site_admin":false},"created_at":"2015-09-06T18:09:26Z","updated_at":"2015-09-06T18:09:26Z","body":"I would want to verify that GLM versions shipped in Fedora at least pass their test suite on all supported architectures, on both clang and gcc and with at least minimal build flags and -std=c++11 and -std=c++14 . It takes a long time to do this verification if a single test run on a midrange computer takes over 6 minutes.\r\n\r\nEspecially for ARM machines, having highly CPU intensive tests is inconvenient. The 6 minutes could easily become something like 60 minutes.\r\n\r\nI would not mind that much if the CPU time was used for something that is clearly necessary and useful. But I am currently not convinced that testing all of the possible float values is an useful thing to test routinely."}}