{"action":"created","issue":{"url":"https://api.github.com/repos/bazelbuild/bazel/issues/1293","repository_url":"https://api.github.com/repos/bazelbuild/bazel","labels_url":"https://api.github.com/repos/bazelbuild/bazel/issues/1293/labels{/name}","comments_url":"https://api.github.com/repos/bazelbuild/bazel/issues/1293/comments","events_url":"https://api.github.com/repos/bazelbuild/bazel/issues/1293/events","html_url":"https://github.com/bazelbuild/bazel/issues/1293","id":155792140,"number":1293,"title":"ill-advised glob pattern leads to geometric growth in 'bazel test' execution times.","user":{"login":"rpoyner-tri","id":17582368,"avatar_url":"https://avatars.githubusercontent.com/u/17582368?v=3","gravatar_id":"","url":"https://api.github.com/users/rpoyner-tri","html_url":"https://github.com/rpoyner-tri","followers_url":"https://api.github.com/users/rpoyner-tri/followers","following_url":"https://api.github.com/users/rpoyner-tri/following{/other_user}","gists_url":"https://api.github.com/users/rpoyner-tri/gists{/gist_id}","starred_url":"https://api.github.com/users/rpoyner-tri/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rpoyner-tri/subscriptions","organizations_url":"https://api.github.com/users/rpoyner-tri/orgs","repos_url":"https://api.github.com/users/rpoyner-tri/repos","events_url":"https://api.github.com/users/rpoyner-tri/events{/privacy}","received_events_url":"https://api.github.com/users/rpoyner-tri/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-05-19T17:29:46Z","updated_at":"2016-05-19T18:30:34Z","closed_at":null,"body":"See attached example project.\r\n\r\nUsing an ill-advised glob pattern to select data files (maybe any kind of files?) leads to some cumulative server or cache problem. The project continues to build, but execution times of 'bazel test //...' grow geometrically.\r\n\r\nI'm not looking for a fix to permit the bad glob pattern, necessarily. What I would like is for ill-advised cases like this to fail fast with a comprehensible error message. \r\n\r\n[bazelweird.zip](https://github.com/bazelbuild/bazel/files/273095/bazelweird.zip)\r\n"},"comment":{"url":"https://api.github.com/repos/bazelbuild/bazel/issues/comments/220412508","html_url":"https://github.com/bazelbuild/bazel/issues/1293#issuecomment-220412508","issue_url":"https://api.github.com/repos/bazelbuild/bazel/issues/1293","id":220412508,"user":{"login":"rpoyner-tri","id":17582368,"avatar_url":"https://avatars.githubusercontent.com/u/17582368?v=3","gravatar_id":"","url":"https://api.github.com/users/rpoyner-tri","html_url":"https://github.com/rpoyner-tri","followers_url":"https://api.github.com/users/rpoyner-tri/followers","following_url":"https://api.github.com/users/rpoyner-tri/following{/other_user}","gists_url":"https://api.github.com/users/rpoyner-tri/gists{/gist_id}","starred_url":"https://api.github.com/users/rpoyner-tri/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rpoyner-tri/subscriptions","organizations_url":"https://api.github.com/users/rpoyner-tri/orgs","repos_url":"https://api.github.com/users/rpoyner-tri/repos","events_url":"https://api.github.com/users/rpoyner-tri/events{/privacy}","received_events_url":"https://api.github.com/users/rpoyner-tri/received_events","type":"User","site_admin":false},"created_at":"2016-05-19T18:30:34Z","updated_at":"2016-05-19T18:30:34Z","body":"Right, here's a way to reproduce the problem, with (maybe redundant) timing measurements:\r\n`seq 100 | xargs -i time bazel test //...`\r\n\r\nIf you get beyond 12 or so iterations, you must have a very nice computer :) ."}}