Re: mysqlIndexerTest.test_unicode fails for me

Hi Ralf:

In message <[email protected]>,
Ralf Schlatterbeck writes:
>The test in test_indexer.py:
>mysqlIndexerTest.test_unicode
>
>fails in my debian buster installation. It was broken before on the
>previous debian version, too. The test passes in Travis.
>
>Any idea what the problem might be? Do I have to install some additional
>mysql software for the indexer to work? Or configure something somewhere
>to allow utf-8 for the indexer?
>
>Not that I care too much about mysql but it's annoying having a failing
>test.

I am way out of my depth here. However, my only thought is that the
index database/table isn't being created with CHARACTER SET utf8. Does
the systems's my.cnf (or your user's my.cnf) have some other character
set or collation?

That's all I can come up with as Travis is ok with it, so it must be
something in your environment, or something broken in that release of
python. I don't know exactly what release of 3.7 Travis is using. That
said, we may be missing something in the roundup code that can fix
this issue.

Can you get anymore info about how it's failing? What is being
returned by the call to find? Empty list? Mangled data? Maybe add:

  import pdb; pdb.set_trace()

in the test and run python3 -m pytest and poke around the test in the
debugger.

Sorry I don't have any better ideas.

--
				-- rouilj
John Rouillard
===========================================================================
My employers don't acknowledge my existence much less my opinions.