{"action":"created","issue":{"url":"https://api.github.com/repos/hitchtest/django-remindme-tests/issues/2","labels_url":"https://api.github.com/repos/hitchtest/django-remindme-tests/issues/2/labels{/name}","comments_url":"https://api.github.com/repos/hitchtest/django-remindme-tests/issues/2/comments","events_url":"https://api.github.com/repos/hitchtest/django-remindme-tests/issues/2/events","html_url":"https://github.com/hitchtest/django-remindme-tests/issues/2","id":97905745,"number":2,"title":"[Errno 2] No such file or directory: '/tmp/django-remindme/django-remindme-tests/.hitch/build/postgresql-9.3.9/postgresql-9.3.9/bin/postgres'","user":{"login":"EliotBerriot","id":1970915,"avatar_url":"https://avatars.githubusercontent.com/u/1970915?v=3","gravatar_id":"","url":"https://api.github.com/users/EliotBerriot","html_url":"https://github.com/EliotBerriot","followers_url":"https://api.github.com/users/EliotBerriot/followers","following_url":"https://api.github.com/users/EliotBerriot/following{/other_user}","gists_url":"https://api.github.com/users/EliotBerriot/gists{/gist_id}","starred_url":"https://api.github.com/users/EliotBerriot/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/EliotBerriot/subscriptions","organizations_url":"https://api.github.com/users/EliotBerriot/orgs","repos_url":"https://api.github.com/users/EliotBerriot/repos","events_url":"https://api.github.com/users/EliotBerriot/events{/privacy}","received_events_url":"https://api.github.com/users/EliotBerriot/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-07-29T10:16:30Z","updated_at":"2015-07-30T12:34:55Z","closed_at":"2015-07-29T11:16:43Z","body":"Sorry for opening a second issue, but it seemed distinct from the first one to me. When running `hitch test simple_reminder.test` for the first time, everything build correctly, until I get this : \r\n\r\n    builtins.FileNotFoundError\r\n\r\n    [Errno 2] No such file or directory: '/tmp/django-remindme/django-remindme-tests/.hitch/build/postgresql-9.3.9/postgresql-9.3.9/bin/postgres'\r\n        \r\nFull stack trace after PostgreSQL downloading : \r\n\r\n    100.0% [============================================================================== ]\r\n    patool: Extracting /tmp/django-remindme/django-remindme-tests/.hitch/downloads/postgresql-9.3.9.tar.gz ...\r\n    patool: running /bin/tar --extract -z --file /tmp/django-remindme/django-remindme-tests/.hitch/downloads/postgresql-9.3.9.tar.gz --directory /tmp/django-remindme/django-remindme-tests/.hitch/build/postgresql-9.3.9\r\n    patool: ... /tmp/django-remindme/django-remindme-tests/.hitch/downloads/postgresql-9.3.9.tar.gz extracted to `/tmp/django-remindme/django-remindme-tests/.hitch/build/postgresql-9.3.9'.\r\n    checking build system type... x86_64-unknown-linux-gnu\r\n    checking host system type... x86_64-unknown-linux-gnu\r\n    checking which template to use... linux\r\n    checking whether to build with 64-bit integer date/time support... yes\r\n    checking whether NLS is wanted... no\r\n    checking for default port number... 5432\r\n    checking for block size... 8kB\r\n    checking for segment size... 1GB\r\n    checking for WAL block size... 8kB\r\n    checking for WAL segment size... 16MB\r\n    checking for gcc... gcc\r\n    checking for C compiler default output file name... a.out\r\n    checking whether the C compiler works... yes\r\n    checking whether we are cross compiling... no\r\n    checking for suffix of executables... \r\n    checking for suffix of object files... o\r\n    checking whether we are using the GNU C compiler... yes\r\n    checking whether gcc accepts -g... yes\r\n    checking for gcc option to accept ISO C89... none needed\r\n    checking whether gcc supports -Wdeclaration-after-statement... yes\r\n    checking whether gcc supports -Wendif-labels... yes\r\n    checking whether gcc supports -Wmissing-format-attribute... yes\r\n    checking whether gcc supports -Wformat-security... yes\r\n    checking whether gcc supports -fno-strict-aliasing... yes\r\n    checking whether gcc supports -fwrapv... yes\r\n    checking whether gcc supports -fexcess-precision=standard... yes\r\n    checking whether gcc supports -funroll-loops... yes\r\n    checking whether gcc supports -ftree-vectorize... yes\r\n    checking whether gcc supports -Wunused-command-line-argument... no\r\n    checking whether the C compiler still works... yes\r\n    checking how to run the C preprocessor... gcc -E\r\n    checking allow thread-safe client libraries... yes\r\n    checking whether to build with Tcl... no\r\n    checking whether to build Perl modules... no\r\n    checking whether to build Python modules... no\r\n    checking whether to build with GSSAPI support... no\r\n    checking whether to build with Kerberos 5 support... no\r\n    checking whether to build with PAM support... no\r\n    checking whether to build with LDAP support... no\r\n    checking whether to build with Bonjour support... no\r\n    checking whether to build with OpenSSL support... no\r\n    checking whether to build with SELinux support... no\r\n    checking for grep that handles long lines and -e... /bin/grep\r\n    checking for egrep... /bin/grep -E\r\n    checking for ld used by GCC... /usr/bin/ld\r\n    checking if the linker (/usr/bin/ld) is GNU ld... yes\r\n    checking for ranlib... ranlib\r\n    checking for strip... strip\r\n    checking whether it is possible to strip libraries... yes\r\n    checking for ar... ar\r\n    checking for a BSD-compatible install... /usr/bin/install -c\r\n    checking for tar... /bin/tar\r\n    checking whether ln -s works... yes\r\n    checking for gawk... no\r\n    checking for mawk... mawk\r\n    checking for a thread-safe mkdir -p... /bin/mkdir -p\r\n    checking for bison... no\r\n    configure: WARNING:\r\n    *** Without Bison you will not be able to build PostgreSQL from Git nor\r\n    *** change any of the parser definition files.  You can obtain Bison from\r\n    *** a GNU mirror site.  (If you are using the official distribution of\r\n    *** PostgreSQL then you do not need to worry about this, because the Bison\r\n    *** output is pre-generated.)\r\n    checking for flex... no\r\n    configure: WARNING:\r\n    *** Without Flex you will not be able to build PostgreSQL from Git nor\r\n    *** change any of the scanner definition files.  You can obtain Flex from\r\n    *** a GNU mirror site.  (If you are using the official distribution of\r\n    *** PostgreSQL then you do not need to worry about this because the Flex\r\n    *** output is pre-generated.)\r\n    checking for perl... /usr/bin/perl\r\n    configure: using perl 5.18.2\r\n    checking for main in -lm... yes\r\n    checking for library containing setproctitle... no\r\n    checking for library containing dlopen... -ldl\r\n    checking for library containing socket... none required\r\n    checking for library containing shl_load... no\r\n    checking for library containing getopt_long... none required\r\n    checking for library containing crypt... -lcrypt\r\n    checking for library containing fdatasync... none required\r\n    checking for library containing gethostbyname_r... none required\r\n    checking for library containing shmget... none required\r\n    checking for library containing readline... no\r\n    configure: error: readline library not found\r\n    If you have readline already installed, see config.log for details on the\r\n    failure.  It is possible the compiler isn't looking in the proper directory.\r\n    Use --without-readline to disable readline support.\r\n    You need to run the 'configure' program first. See the file\r\n\r\nThere are two warnings about missing bison and flex library. So I installed them with `apt-get install bison flex` (I'm on Ubuntu 14.04), and relaunched the whole process, but it fails at the very same point. Then I also noticed the `readline` warning, but `libreadline6` is already installed on my machine, so I'm not sure what to do. \r\n\r\nAlso, after crashing, the process is left in the IPython shell, I think it would could be an improvement to return to the original user session / directory in case of error."},"comment":{"url":"https://api.github.com/repos/hitchtest/django-remindme-tests/issues/comments/126308175","html_url":"https://github.com/hitchtest/django-remindme-tests/issues/2#issuecomment-126308175","issue_url":"https://api.github.com/repos/hitchtest/django-remindme-tests/issues/2","id":126308175,"user":{"login":"EliotBerriot","id":1970915,"avatar_url":"https://avatars.githubusercontent.com/u/1970915?v=3","gravatar_id":"","url":"https://api.github.com/users/EliotBerriot","html_url":"https://github.com/EliotBerriot","followers_url":"https://api.github.com/users/EliotBerriot/followers","following_url":"https://api.github.com/users/EliotBerriot/following{/other_user}","gists_url":"https://api.github.com/users/EliotBerriot/gists{/gist_id}","starred_url":"https://api.github.com/users/EliotBerriot/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/EliotBerriot/subscriptions","organizations_url":"https://api.github.com/users/EliotBerriot/orgs","repos_url":"https://api.github.com/users/EliotBerriot/repos","events_url":"https://api.github.com/users/EliotBerriot/events{/privacy}","received_events_url":"https://api.github.com/users/EliotBerriot/received_events","type":"User","site_admin":false},"created_at":"2015-07-30T12:34:54Z","updated_at":"2015-07-30T12:34:54Z","body":"You're right, it's a feature, not a bug ;)"}}