OSX build test failure
- From:
- Thijs Koerselman
- Date:
- 2010-12-27 @ 14:19
Hi, I was just trying out mongrel2 for the first time, on OSX and I get the
following error during build.
sh ./tests/runtests.sh
Running unit tests:
tests/bstr_tests PASS
tests/cache_tests PASS
tests/config_tests PASS
tests/connection_tests PASS
tests/db_tests PASS
tests/dict_tests PASS
ERROR in test tests/dir_tests:
----
RUNNING: ./tests/dir_tests
FAILED: Failed to resolve file that should be there.
I had a look at test_dir.c and it looks like the error comes from:
char *test_Dir_resolve_file()
{
Dir *test = Dir_create("tests/", "sample.html", "test/plain");
mu_assert(test != NULL, "Failed to make test dir.");
FileRecord *rec = Dir_resolve_file(test, bfromcstr("/"),
bfromcstr("/sample.json"));
mu_assert(rec != NULL, "Failed to resolve file that should be there.");
I don't understand, because the sample.json file seems to be there in the
same directory.
Any idea?
Re: [mongrel2] OSX build test failure
- From:
- Zed A. Shaw
- Date:
- 2010-12-27 @ 17:55
On Mon, Dec 27, 2010 at 03:19:03PM +0100, Thijs Koerselman wrote:
> Hi, I was just trying out mongrel2 for the first time, on OSX and I get the
> following error during build.
>
>
> I don't understand, because the sample.json file seems to be there in the
> same directory.
Hmm, odd, why would it find one and not the other? Take a look in
tests/test.log and see what error it printed. You can also run that
test manually and use strace on it to see what it does.
What version of OSX is this? I can't imagine it's a recent change that
could cause this to fail suddenly, but you never know.
--
Zed A. Shaw
http://zedshaw.com/
Re: [mongrel2] OSX build test failure
- From:
- Thijs Koerselman
- Date:
- 2010-12-29 @ 23:56
On 12/27/10 6:55 PM, "Zed A. Shaw" <zedshaw@zedshaw.com> wrote:
>
>Hmm, odd, why would it find one and not the other? Take a look in
>tests/test.log and see what error it printed. You can also run that
>test manually and use strace on it to see what it does.
>
>What version of OSX is this? I can't imagine it's a recent change that
>could cause this to fail suddenly, but you never know.
If I run only the dir_test file, the log reports:
[INFO] (src/dir.c:188) MAX limits.dir_send_buffer=16384,
limits.dir_max_path=256
[ERROR] (tests/dir_tests.c:29: errno: None) Failed to resolve file that
should be there.
I'm using OS 10.6.5
What would be the way to skip tests during build?
Thijs