failed: UASSERT

[Kilarin]

I use Xubuntu 14.04
I have ppa:minetestdevs/daily-builds in my repositories.
I just updated minetest to the most recent daily build this morning and now I can't start minetest at all!

Your phone or window isn't wide enough to display the code box. If it's a phone, try rotating it to landscape mode.

Code: Select all

~$ minetest
19:53:38: ERROR[main]: Test (lowercase("Foo bAR") == "foo bar") failed: UASSERT
19:53:38: ERROR[main]: Test (is_yes("YeS") == true) failed: UASSERT
19:53:38: ERROR[main]: Test (is_yes("0") == false) failed: UASSERT
19:53:38: ERROR[main]: run_tests(): 1 / 13 tests failed.
19:53:38: ERROR[main]: run_tests() aborting.
Aborted (core dumped)
~$

Any idea what this is trying to tell me?

I reverted to minetest_201410281016-0~3029~ubuntu14.04.1 and it seems to work fine.

[GauVeldt]

For whatever reason the unit tests aren't sane and are failing for whatever reasons (whether the tests themselves are broken or what is being tested is broken remains to be seen).

try minetest executable adding the command line argument:
--disable-unittests

EDIT: glad I wasn't the only one getting this snag. I only discovered this command line argument after I majorly hardcoded (editing EVERY compile flag setting line to add -g and setting CMAKE_STRIP to touch.exe instead) the cmake files so I'd have debug symbols and stuff in release mode (the reason I needed to ensure I had symbols: https://forum.minetest.net/viewtopic.php?f=3&t=10487) but not run the unit tests.

[Zeno]

I did that :( It is fixed now

(The unit tests were failing correctly, the change I made was a simple one that forgot a single '+' character... ooops)

[GauVeldt]

I did that :( It is fixed now

(The unit tests were failing correctly, the change I made was a simple one that forgot a single '+' character... ooops)

I've had these failing on a straight build from unmodified sources so I don't quite trust all the tests yet. MT has had enough stable releases along its multi-year dev history that I would not expect simple stuff like testing path manipulation to be failing unit testing (would have been one of the first things fixed :)

[Zeno]

The only unit test that I know will fail incorrectly is if IPv6 is disabled or not available... perhaps there are others?

https://github.com/minetest/minetest/pull/1776

[Kilarin]

Just updated to tonights dev version, and it starts up just fine.
That's the risk of running the dev version... :D

[philipbenr]

If you are using Linux, there is a nice auto update script that I have written. It takes minetest that you have used the git clone way of downloading for, enters that folder and updates minetest engine (minetest_game and all the other mods that you used git clone for (I'm pretty sure) ), and compiles it. It is in this post:
viewtopic.php?f=42&t=3837&start=25#p149113

Have fun!