mlandauer / testing-not-creating-sqlite

Testing what happens when you don't create an sqlite database

Contributors mlandauer

Last run failed with status code 998.

Console output of last run

Injecting configuration and compiling... Injecting scraper and running... total 32 drwxr-xr-x 2 u22520 u22520 4096 Dec 4 04:03 bin -rw-r--r-- 1 u22520 u22520 379 Dec 4 04:03 Gemfile -rw-r--r-- 1 u22520 u22520 1065 Dec 4 04:03 Gemfile.lock -rw-r--r-- 1 u22520 u22520 63 Dec 4 04:03 Procfile -rw-r--r-- 1 u22520 u22520 128 Dec 4 06:14 README.md -rwxr-xr-x 1 u22520 u22520 953 Dec 4 06:14 scraper.rb -rw-r--r-- 1 u22520 u22520 0 Dec 4 06:14 time.output drwxr-xr-x 2 u22520 u22520 4096 Dec 4 04:04 tmp drwxr-xr-x 5 u22520 u22520 4096 Dec 4 04:03 vendor Scraper didn't create an SQLite database in your current working directory called data.sqlite. If you've just created your first scraper and not edited the code yet this is to be expected. To fix this make your scraper write to an SQLite database at data.sqlite. However, this could also be related to an intermittant problem which we're working hard to resolve: https://github.com/openaustralia/morph/issues/1064

Statistics

Total run time: less than 10 seconds

Total cpu time used: less than 5 seconds

Total disk space used: 22.2 KB

History

  • Manually ran revision b4e28e95 and failed .
  • Manually ran revision b4e28e95 and failed .
  • Created on morph.io