Common unit test problems - Revision history

Mudrd8mz: Text replacement - "`" to ""`


2021-07-14T13:03:08Z
Text replacement - "<code>" to "<syntaxhighlight lang="php">"

				
				
				
				
				
				← Older revision
				Revision as of 13:03, 14 July 2021
				
Line 5:
Line 5:
When I was running tests on oracle I was getting phpunit sefaulting.. --[[User:Dan Poltawski|Dan Poltawski]] 00:29, 16 May 2012 (WST) When I was running tests on oracle I was getting phpunit sefaulting.. --[[User:Dan Poltawski|Dan Poltawski]] 00:29, 16 May 2012 (WST)



'''Solution''' Set statement_cache_size in php.ini: <code>oci8.statement_cache_size = 0</syntaxhighlight>   '''Solution''' Set statement_cache_size in php.ini: <syntaxhighlight lang="php">oci8.statement_cache_size = 0</syntaxhighlight>  



(More info: [https://bugs.php.net/bug.php?id=49803 PHP Bug #49803]). (More info: [https://bugs.php.net/bug.php?id=49803 PHP Bug #49803]).
Line 24:
Line 24:
=== dml_testcase::test_unique_index_collation_trouble=== === dml_testcase::test_unique_index_collation_trouble===



<code>Unique index is accent insensitive, this may cause problems for non-ascii languages. This is usually caused by accent insensitive default collation.</syntaxhighlight> <syntaxhighlight lang="php">Unique index is accent insensitive, this may cause problems for non-ascii languages. This is usually caused by accent insensitive default collation.</syntaxhighlight>



'''Solution''' Use the utf8mb4_bin collation on your database for unit tests on MySQL/MariaDB '''Solution''' Use the utf8mb4_bin collation on your database for unit tests on MySQL/MariaDB
Line 30:
Line 30:
=== dml_testcase::test_sql_binary_equal === === dml_testcase::test_sql_binary_equal ===



<code>SQL operator "=" is expected to be case sensitive Failed asserting that 1 matches expected 2.</syntaxhighlight> <syntaxhighlight lang="php">SQL operator "=" is expected to be case sensitive Failed asserting that 1 matches expected 2.</syntaxhighlight>



'''Solution''' Use the utf8mb4_bin collation on your database for unit tests on MySQL/MariaDB '''Solution''' Use the utf8mb4_bin collation on your database for unit tests on MySQL/MariaDB
Line 36:
Line 36:
=== grading_manager_testcase::test_tokenize=== === grading_manager_testcase::test_tokenize===



<code>A test using UTF-8 characters has failed. Consider updating PHP and PHP's PCRE or INTL extensions (MDL-30494) Failed asserting that false is true.</syntaxhighlight> <syntaxhighlight lang="php">A test using UTF-8 characters has failed. Consider updating PHP and PHP's PCRE or INTL extensions (MDL-30494) Failed asserting that false is true.</syntaxhighlight>



'''Solution''' Use the utf8mb4_bin collation on your database for unit tests on MySQL/MariaDB '''Solution''' Use the utf8mb4_bin collation on your database for unit tests on MySQL/MariaDB
Line 42:
Line 42:
=== moodlesimplepie_testcase::test_getfeed === === moodlesimplepie_testcase::test_getfeed ===



<code>Failed to load the sample RSS file. Please check your proxy settings in Moodle. %s</syntaxhighlight> <syntaxhighlight lang="php">Failed to load the sample RSS file. Please check your proxy settings in Moodle. %s</syntaxhighlight>



'''Solution''' Your moodle needs network connectivity, please check proxy settings. '''Solution''' Your moodle needs network connectivity, please check proxy settings.
Line 48:
Line 48:
=== moodlesimplepie_testcase::test_redirect === === moodlesimplepie_testcase::test_redirect ===



<code>Failed asserting that 'cURL Error: Operation timed out after 2000 milliseconds with 0 bytes received' is null.</syntaxhighlight> <syntaxhighlight lang="php">Failed asserting that 'cURL Error: Operation timed out after 2000 milliseconds with 0 bytes received' is null.</syntaxhighlight>



'''Solution''' Your moodle needs network connectivity, please check proxy settings '''Solution''' Your moodle needs network connectivity, please check proxy settings
Line 54:
Line 54:
=== collatorlib_testcase::test_asort_objects_by_method === === collatorlib_testcase::test_asort_objects_by_method ===



<code>Collation aware sorting not supported, PHP extension "intl" is not available.</syntaxhighlight> <syntaxhighlight lang="php">Collation aware sorting not supported, PHP extension "intl" is not available.</syntaxhighlight>



'''Solution''' Install php intl extension. '''Solution''' Install php intl extension.
Line 62:
Line 62:
===  moodlelib_testcase::test_fix_utf8 === ===  moodlelib_testcase::test_fix_utf8 ===



<code>Failed asserting that false is identical to 'aaabbb'.</syntaxhighlight> <syntaxhighlight lang="php">Failed asserting that false is identical to 'aaabbb'.</syntaxhighlight>



'''Solution''' This problem indicates buggy iconv. See [http://tracker.moodle.org/browse/MDL-33007] for discussion.  So this is a real problem, to be fixed in a future integration cycle '''Solution''' This problem indicates buggy iconv. See [http://tracker.moodle.org/browse/MDL-33007] for discussion.  So this is a real problem, to be fixed in a future integration cycle
Line 68:
Line 68:
=== filestoragelib_testcase::test_get_file_preview === === filestoragelib_testcase::test_get_file_preview ===



<code>Failed asserting that false is an instance of class "stored_file".</syntaxhighlight> <syntaxhighlight lang="php">Failed asserting that false is an instance of class "stored_file".</syntaxhighlight>



'''Solution''' Unfortunately, the php GD extension is a requirement for this test (see MDL-36447). '''Solution''' Unfortunately, the php GD extension is a requirement for this test (see MDL-36447).



Go to your Moodle directory and type <code>php admin/tool/phpunit/cli/util.php --drop</syntaxhighlight>, then reinitialise PHPunit and run the test again. Go to your Moodle directory and type <syntaxhighlight lang="php">php admin/tool/phpunit/cli/util.php --drop</syntaxhighlight>, then reinitialise PHPunit and run the test again.



===core_ddl_testcase::test_row_size_limits=== ===core_ddl_testcase::test_row_size_limits===



<code>Row size limit reached in MySQL using InnoDB, configure server to use innodb_file_format=Barracuda and innodb_file_per_table=1</syntaxhighlight> <syntaxhighlight lang="php">Row size limit reached in MySQL using InnoDB, configure server to use innodb_file_format=Barracuda and innodb_file_per_table=1</syntaxhighlight>



""Solution"" default InnoDB database tables in MySQL cannot handle more than 10 text columns, so innodb file format should be Barracuda (see MDL-46971) ""Solution"" default InnoDB database tables in MySQL cannot handle more than 10 text columns, so innodb file format should be Barracuda (see MDL-46971)



Running <code>php admin/cli/mysql_compressed_rows.php</syntaxhighlight> will solve the problem. Running <syntaxhighlight lang="php">php admin/cli/mysql_compressed_rows.php</syntaxhighlight> will solve the problem.



===  core_phpunit_advanced_testcase::test_locale_reset === ===  core_phpunit_advanced_testcase::test_locale_reset ===
Line 114:
Line 114:
This occurs on Mac installs from experience. The reason this occurs is because DBUnit was not installed during the PHPUnit installation via PEAR. This occurs on Mac installs from experience. The reason this occurs is because DBUnit was not installed during the PHPUnit installation via PEAR.



'''Solution''' In terminal type: <code>sudo pear install -f phpunit/DbUnit</syntaxhighlight> '''Solution''' In terminal type: <syntaxhighlight lang="php">sudo pear install -f phpunit/DbUnit</syntaxhighlight>



=== !!! Error reading from database !!!!! Unicode data in a Unicode-only collation or ntext data cannot be sent to clients using DB-Library (such as ISQL) or ODBC version 3.7 or earlier. === === !!! Error reading from database !!!!! Unicode data in a Unicode-only collation or ntext data cannot be sent to clients using DB-Library (such as ISQL) or ODBC version 3.7 or earlier. ===
Line 143:
Line 143:



You need both to: You need both to:
# Have python and pip installed and the <code>$CFG->pathtopython</syntaxhighlight> config value pointing to the python executable. # Have python and pip installed and the <syntaxhighlight lang="php">$CFG->pathtopython</syntaxhighlight> config value pointing to the python executable.
# Have the ''moodlemlbackend'' python package installed: <code>pip install moodlemlbackend</syntaxhighlight> # Have the ''moodlemlbackend'' python package installed: <syntaxhighlight lang="php">pip install moodlemlbackend</syntaxhighlight>
to get all the python backend tests being run and, hopefully, passing. to get all the python backend tests being run and, hopefully, passing.

`Mudrd8mz: Text replacement - "`" to ""

2021-07-14T13:02:21Z

Text replacement - "</code>" to "</syntaxhighlight>"

Stronk7: mlbackend_python problems

2017-11-06T16:51:25Z

mlbackend_python problems

← Older revision		Revision as of 16:51, 6 November 2017
Line 139:		Line 139:

	Likely that you've got git setting autocrlf set to true and its altered the line endings. Set autocrlf to false in your git config and reset your checkout following [https://help.github.com/articles/dealing-with-line-endings/#refreshing-a-repository-after-changing-line-endings this guide].		Likely that you've got git setting autocrlf set to true and its altered the line endings. Set autocrlf to false in your git config and reset your checkout following [https://help.github.com/articles/dealing-with-line-endings/#refreshing-a-repository-after-changing-line-endings this guide].

			=== Some tests are skipped with message "Skipping \mlbackend_python\processor as the predictor is not ready" ===

			You need both to:
			# Have python and pip installed and the <code>$CFG->pathtopython</code> config value pointing to the python executable.
			# Have the ''moodlemlbackend'' python package installed: <code>pip install moodlemlbackend</code>
			to get all the python backend tests being run and, hopefully, passing.

Stronk7: sensitive collations continue being required, and utf8mb4_bin is the only available one. Also added MariaDB, just in case.

2017-05-04T11:19:02Z

sensitive collations continue being required, and utf8mb4_bin is the only available one. Also added MariaDB, just in case.

← Older revision		Revision as of 11:19, 4 May 2017
Line 26:		Line 26:
	<code>Unique index is accent insensitive, this may cause problems for non-ascii languages. This is usually caused by accent insensitive default collation.</code>		<code>Unique index is accent insensitive, this may cause problems for non-ascii languages. This is usually caused by accent insensitive default collation.</code>

	'''Solution''' Use the ~~utf8mb4_unicode_ci~~ collation on your database for unit tests on MySQL		'''Solution''' Use the utf8mb4_bin collation on your database for unit tests on MySQL/MariaDB

	=== dml_testcase::test_sql_binary_equal ===		=== dml_testcase::test_sql_binary_equal ===
Line 32:		Line 32:
	<code>SQL operator "=" is expected to be case sensitive Failed asserting that 1 matches expected 2.</code>		<code>SQL operator "=" is expected to be case sensitive Failed asserting that 1 matches expected 2.</code>

	'''Solution''' Use the ~~utf8mb4_unicode_ci~~ collation on your database for unit tests on MySQL		'''Solution''' Use the utf8mb4_bin collation on your database for unit tests on MySQL/MariaDB

	=== grading_manager_testcase::test_tokenize===		=== grading_manager_testcase::test_tokenize===
Line 38:		Line 38:
	<code>A test using UTF-8 characters has failed. Consider updating PHP and PHP's PCRE or INTL extensions (MDL-30494) Failed asserting that false is true.</code>		<code>A test using UTF-8 characters has failed. Consider updating PHP and PHP's PCRE or INTL extensions (MDL-30494) Failed asserting that false is true.</code>

	'''Solution''' Use the ~~utf8mb4_unicode_ci~~ collation on your database for unit tests on MySQL		'''Solution''' Use the utf8mb4_bin collation on your database for unit tests on MySQL/MariaDB

	=== moodlesimplepie_testcase::test_getfeed ===		=== moodlesimplepie_testcase::test_getfeed ===

Poltawski: /* Specific failures */

2017-05-04T07:14:31Z

Specific failures

← Older revision		Revision as of 07:14, 4 May 2017
Line 32:		Line 32:
	<code>SQL operator "=" is expected to be case sensitive Failed asserting that 1 matches expected 2.</code>		<code>SQL operator "=" is expected to be case sensitive Failed asserting that 1 matches expected 2.</code>

	'''Solution''' Use the utf8mb4_unicode_ci collation on your database for unit tests		'''Solution''' Use the utf8mb4_unicode_ci collation on your database for unit tests on MySQL

	=== grading_manager_testcase::test_tokenize===		=== grading_manager_testcase::test_tokenize===
Line 38:		Line 38:
	<code>A test using UTF-8 characters has failed. Consider updating PHP and PHP's PCRE or INTL extensions (MDL-30494) Failed asserting that false is true.</code>		<code>A test using UTF-8 characters has failed. Consider updating PHP and PHP's PCRE or INTL extensions (MDL-30494) Failed asserting that false is true.</code>

	'''Solution''' ~~These tests should pass if you use~~ the ~~<code>utf8_bin</code>~~ collation on your database for unit tests~~, but we recommend <code>utf8_unicode_ci</code> for actual live Moodle sites. Work is being done to resolve this issue, read more about the [[Database collation issue]] for further info.~~		'''Solution''' Use the utf8mb4_unicode_ci collation on your database for unit tests on MySQL

	=== moodlesimplepie_testcase::test_getfeed ===		=== moodlesimplepie_testcase::test_getfeed ===

Poltawski: /* dml_testcase::test_unique_index_collation_trouble */

2017-05-04T07:14:12Z

dml_testcase::test_unique_index_collation_trouble

← Older revision		Revision as of 07:14, 4 May 2017
Line 26:		Line 26:
	<code>Unique index is accent insensitive, this may cause problems for non-ascii languages. This is usually caused by accent insensitive default collation.</code>		<code>Unique index is accent insensitive, this may cause problems for non-ascii languages. This is usually caused by accent insensitive default collation.</code>

	'''Solution''' ~~These tests should pass if you use~~ the ~~<code>utf8_bin</code>~~ collation on your database for unit tests~~, but we recommend <code>utf8_unicode_ci</code> for actual live Moodle sites. Work is being done to resolve this issue, read more about the [[Database collation issue]] for further info.~~		'''Solution''' Use the utf8mb4_unicode_ci collation on your database for unit tests on MySQL

	=== dml_testcase::test_sql_binary_equal ===		=== dml_testcase::test_sql_binary_equal ===

Poltawski: /* dml_testcase::test_sql_binary_equal */

2017-05-04T07:13:46Z

dml_testcase::test_sql_binary_equal

← Older revision		Revision as of 07:13, 4 May 2017
Line 32:		Line 32:
	<code>SQL operator "=" is expected to be case sensitive Failed asserting that 1 matches expected 2.</code>		<code>SQL operator "=" is expected to be case sensitive Failed asserting that 1 matches expected 2.</code>

	'''Solution''' ~~These tests should pass if you use~~ the ~~<code>utf8_bin</code>~~ collation on your database for unit tests~~, but we recommend <code>utf8_unicode_ci</code> for actual live Moodle sites. Work is being done to resolve this issue, read more about the [[Database collation issue]] for further info.~~		'''Solution''' Use the utf8mb4_unicode_ci collation on your database for unit tests

	=== grading_manager_testcase::test_tokenize===		=== grading_manager_testcase::test_tokenize===

Poltawski: https://tracker.moodle.org/browse/MDL-42218

2016-07-18T13:18:38Z

https://tracker.moodle.org/browse/MDL-42218

← Older revision		Revision as of 13:18, 18 July 2016
Line 90:		Line 90:
	* Debian/Centos: "sudo localedef -v -c -i en_AU -f UTF-8 en_AU.UTF-8"		* Debian/Centos: "sudo localedef -v -c -i en_AU -f UTF-8 en_AU.UTF-8"
	* Ubuntu: "sudo locale-gen en_AU.UTF-8"		* Ubuntu: "sudo locale-gen en_AU.UTF-8"

			=== core_cache_config_writer_testcase::test_add_edit_delete_plugin_instance ===

			Failed asserting that an array has the key 'addplugintest'.

			'''Solution''' Set opcache.enable_cli = 0

	=== MSSQL failures with core_course_externallib_testcase===		=== MSSQL failures with core_course_externallib_testcase===

Emerrill: /* core_phpunit_advanced_testcase::test_locale_reset */ Marking which one works for Debian

2016-03-30T13:29:36Z

core_phpunit_advanced_testcase::test_locale_reset: Marking which one works for Debian

← Older revision		Revision as of 13:29, 30 March 2016
Line 88:		Line 88:
	'''Solution''' Install the AU locale on your server if you want to run phpunit. Here are sample commands for installing the en_AU locale:		'''Solution''' Install the AU locale on your server if you want to run phpunit. Here are sample commands for installing the en_AU locale:

	* Centos: "sudo localedef -v -c -i en_AU -f UTF-8 en_AU.UTF-8"		* Debian/Centos: "sudo localedef -v -c -i en_AU -f UTF-8 en_AU.UTF-8"
	* Ubuntu: "sudo locale-gen en_AU.UTF-8"		* Ubuntu: "sudo locale-gen en_AU.UTF-8"

Poltawski: /* The test file should not contain section named "[lots of content]" */

2015-10-27T18:17:59Z

The test file should not contain section named "[lots of content]"

← Older revision		Revision as of 18:17, 27 October 2015
Line 130:		Line 130:
	- NLS_NUMERIC_CHARACTERS to ., (dot & comma)		- NLS_NUMERIC_CHARACTERS to ., (dot & comma)

	=== The test file should not contain section named "[lots of content]" ===		=== The test file "evolution.test" should not contain section named "[lots of content]" ===

	Likely that you've got git setting autocrlf set to true and its altered the line endings. Set autocrlf to false in your git config and reset your checkout following [https://help.github.com/articles/dealing-with-line-endings/#refreshing-a-repository-after-changing-line-endings this guide].		Likely that you've got git setting autocrlf set to true and its altered the line endings. Set autocrlf to false in your git config and reset your checkout following [https://help.github.com/articles/dealing-with-line-endings/#refreshing-a-repository-after-changing-line-endings this guide].

← Older revision		Revision as of 13:03, 14 July 2021
Line 5:		Line 5:
	When I was running tests on oracle I was getting phpunit sefaulting.. --[[User:Dan Poltawski\|Dan Poltawski]] 00:29, 16 May 2012 (WST)		When I was running tests on oracle I was getting phpunit sefaulting.. --[[User:Dan Poltawski\|Dan Poltawski]] 00:29, 16 May 2012 (WST)

	'''Solution''' Set statement_cache_size in php.ini: <~~code~~>oci8.statement_cache_size = 0</syntaxhighlight>		'''Solution''' Set statement_cache_size in php.ini: <syntaxhighlight lang="php">oci8.statement_cache_size = 0</syntaxhighlight>

	(More info: [https://bugs.php.net/bug.php?id=49803 PHP Bug #49803]).		(More info: [https://bugs.php.net/bug.php?id=49803 PHP Bug #49803]).
Line 24:		Line 24:
	=== dml_testcase::test_unique_index_collation_trouble===		=== dml_testcase::test_unique_index_collation_trouble===

	<~~code~~>Unique index is accent insensitive, this may cause problems for non-ascii languages. This is usually caused by accent insensitive default collation.</syntaxhighlight>		<syntaxhighlight lang="php">Unique index is accent insensitive, this may cause problems for non-ascii languages. This is usually caused by accent insensitive default collation.</syntaxhighlight>

	'''Solution''' Use the utf8mb4_bin collation on your database for unit tests on MySQL/MariaDB		'''Solution''' Use the utf8mb4_bin collation on your database for unit tests on MySQL/MariaDB
Line 30:		Line 30:
	=== dml_testcase::test_sql_binary_equal ===		=== dml_testcase::test_sql_binary_equal ===

	<~~code~~>SQL operator "=" is expected to be case sensitive Failed asserting that 1 matches expected 2.</syntaxhighlight>		<syntaxhighlight lang="php">SQL operator "=" is expected to be case sensitive Failed asserting that 1 matches expected 2.</syntaxhighlight>

	'''Solution''' Use the utf8mb4_bin collation on your database for unit tests on MySQL/MariaDB		'''Solution''' Use the utf8mb4_bin collation on your database for unit tests on MySQL/MariaDB
Line 36:		Line 36:
	=== grading_manager_testcase::test_tokenize===		=== grading_manager_testcase::test_tokenize===

	<~~code~~>A test using UTF-8 characters has failed. Consider updating PHP and PHP's PCRE or INTL extensions (MDL-30494) Failed asserting that false is true.</syntaxhighlight>		<syntaxhighlight lang="php">A test using UTF-8 characters has failed. Consider updating PHP and PHP's PCRE or INTL extensions (MDL-30494) Failed asserting that false is true.</syntaxhighlight>

	'''Solution''' Use the utf8mb4_bin collation on your database for unit tests on MySQL/MariaDB		'''Solution''' Use the utf8mb4_bin collation on your database for unit tests on MySQL/MariaDB
Line 42:		Line 42:
	=== moodlesimplepie_testcase::test_getfeed ===		=== moodlesimplepie_testcase::test_getfeed ===

	<~~code~~>Failed to load the sample RSS file. Please check your proxy settings in Moodle. %s</syntaxhighlight>		<syntaxhighlight lang="php">Failed to load the sample RSS file. Please check your proxy settings in Moodle. %s</syntaxhighlight>

	'''Solution''' Your moodle needs network connectivity, please check proxy settings.		'''Solution''' Your moodle needs network connectivity, please check proxy settings.
Line 48:		Line 48:
	=== moodlesimplepie_testcase::test_redirect ===		=== moodlesimplepie_testcase::test_redirect ===

	<~~code~~>Failed asserting that 'cURL Error: Operation timed out after 2000 milliseconds with 0 bytes received' is null.</syntaxhighlight>		<syntaxhighlight lang="php">Failed asserting that 'cURL Error: Operation timed out after 2000 milliseconds with 0 bytes received' is null.</syntaxhighlight>

	'''Solution''' Your moodle needs network connectivity, please check proxy settings		'''Solution''' Your moodle needs network connectivity, please check proxy settings
Line 54:		Line 54:
	=== collatorlib_testcase::test_asort_objects_by_method ===		=== collatorlib_testcase::test_asort_objects_by_method ===

	<~~code~~>Collation aware sorting not supported, PHP extension "intl" is not available.</syntaxhighlight>		<syntaxhighlight lang="php">Collation aware sorting not supported, PHP extension "intl" is not available.</syntaxhighlight>

	'''Solution''' Install php intl extension.		'''Solution''' Install php intl extension.
Line 62:		Line 62:
	=== moodlelib_testcase::test_fix_utf8 ===		=== moodlelib_testcase::test_fix_utf8 ===

	<~~code~~>Failed asserting that false is identical to 'aaabbb'.</syntaxhighlight>		<syntaxhighlight lang="php">Failed asserting that false is identical to 'aaabbb'.</syntaxhighlight>

	'''Solution''' This problem indicates buggy iconv. See [http://tracker.moodle.org/browse/MDL-33007] for discussion. So this is a real problem, to be fixed in a future integration cycle		'''Solution''' This problem indicates buggy iconv. See [http://tracker.moodle.org/browse/MDL-33007] for discussion. So this is a real problem, to be fixed in a future integration cycle
Line 68:		Line 68:
	=== filestoragelib_testcase::test_get_file_preview ===		=== filestoragelib_testcase::test_get_file_preview ===

	<~~code~~>Failed asserting that false is an instance of class "stored_file".</syntaxhighlight>		<syntaxhighlight lang="php">Failed asserting that false is an instance of class "stored_file".</syntaxhighlight>

	'''Solution''' Unfortunately, the php GD extension is a requirement for this test (see MDL-36447).		'''Solution''' Unfortunately, the php GD extension is a requirement for this test (see MDL-36447).

	Go to your Moodle directory and type <~~code~~>php admin/tool/phpunit/cli/util.php --drop</syntaxhighlight>, then reinitialise PHPunit and run the test again.		Go to your Moodle directory and type <syntaxhighlight lang="php">php admin/tool/phpunit/cli/util.php --drop</syntaxhighlight>, then reinitialise PHPunit and run the test again.

	===core_ddl_testcase::test_row_size_limits===		===core_ddl_testcase::test_row_size_limits===

	<~~code~~>Row size limit reached in MySQL using InnoDB, configure server to use innodb_file_format=Barracuda and innodb_file_per_table=1</syntaxhighlight>		<syntaxhighlight lang="php">Row size limit reached in MySQL using InnoDB, configure server to use innodb_file_format=Barracuda and innodb_file_per_table=1</syntaxhighlight>

	""Solution"" default InnoDB database tables in MySQL cannot handle more than 10 text columns, so innodb file format should be Barracuda (see MDL-46971)		""Solution"" default InnoDB database tables in MySQL cannot handle more than 10 text columns, so innodb file format should be Barracuda (see MDL-46971)

	Running <~~code~~>php admin/cli/mysql_compressed_rows.php</syntaxhighlight> will solve the problem.		Running <syntaxhighlight lang="php">php admin/cli/mysql_compressed_rows.php</syntaxhighlight> will solve the problem.

	=== core_phpunit_advanced_testcase::test_locale_reset ===		=== core_phpunit_advanced_testcase::test_locale_reset ===
Line 114:		Line 114:
	This occurs on Mac installs from experience. The reason this occurs is because DBUnit was not installed during the PHPUnit installation via PEAR.		This occurs on Mac installs from experience. The reason this occurs is because DBUnit was not installed during the PHPUnit installation via PEAR.

	'''Solution''' In terminal type: <~~code~~>sudo pear install -f phpunit/DbUnit</syntaxhighlight>		'''Solution''' In terminal type: <syntaxhighlight lang="php">sudo pear install -f phpunit/DbUnit</syntaxhighlight>

	=== !!! Error reading from database !!!!! Unicode data in a Unicode-only collation or ntext data cannot be sent to clients using DB-Library (such as ISQL) or ODBC version 3.7 or earlier. ===		=== !!! Error reading from database !!!!! Unicode data in a Unicode-only collation or ntext data cannot be sent to clients using DB-Library (such as ISQL) or ODBC version 3.7 or earlier. ===
Line 143:		Line 143:

	You need both to:		You need both to:
	# Have python and pip installed and the <~~code~~>$CFG->pathtopython</syntaxhighlight> config value pointing to the python executable.		# Have python and pip installed and the <syntaxhighlight lang="php">$CFG->pathtopython</syntaxhighlight> config value pointing to the python executable.
	# Have the ''moodlemlbackend'' python package installed: <~~code~~>pip install moodlemlbackend</syntaxhighlight>		# Have the ''moodlemlbackend'' python package installed: <syntaxhighlight lang="php">pip install moodlemlbackend</syntaxhighlight>
	to get all the python backend tests being run and, hopefully, passing.		to get all the python backend tests being run and, hopefully, passing.

← Older revision		Revision as of 13:02, 14 July 2021
Line 5:		Line 5:
	When I was running tests on oracle I was getting phpunit sefaulting.. --[[User:Dan Poltawski\|Dan Poltawski]] 00:29, 16 May 2012 (WST)		When I was running tests on oracle I was getting phpunit sefaulting.. --[[User:Dan Poltawski\|Dan Poltawski]] 00:29, 16 May 2012 (WST)

	'''Solution''' Set statement_cache_size in php.ini: <code>oci8.statement_cache_size = 0</~~code~~>		'''Solution''' Set statement_cache_size in php.ini: <code>oci8.statement_cache_size = 0</syntaxhighlight>

	(More info: [https://bugs.php.net/bug.php?id=49803 PHP Bug #49803]).		(More info: [https://bugs.php.net/bug.php?id=49803 PHP Bug #49803]).
Line 24:		Line 24:
	=== dml_testcase::test_unique_index_collation_trouble===		=== dml_testcase::test_unique_index_collation_trouble===

	<code>Unique index is accent insensitive, this may cause problems for non-ascii languages. This is usually caused by accent insensitive default collation.</~~code~~>		<code>Unique index is accent insensitive, this may cause problems for non-ascii languages. This is usually caused by accent insensitive default collation.</syntaxhighlight>

	'''Solution''' Use the utf8mb4_bin collation on your database for unit tests on MySQL/MariaDB		'''Solution''' Use the utf8mb4_bin collation on your database for unit tests on MySQL/MariaDB
Line 30:		Line 30:
	=== dml_testcase::test_sql_binary_equal ===		=== dml_testcase::test_sql_binary_equal ===

	<code>SQL operator "=" is expected to be case sensitive Failed asserting that 1 matches expected 2.</~~code~~>		<code>SQL operator "=" is expected to be case sensitive Failed asserting that 1 matches expected 2.</syntaxhighlight>

	'''Solution''' Use the utf8mb4_bin collation on your database for unit tests on MySQL/MariaDB		'''Solution''' Use the utf8mb4_bin collation on your database for unit tests on MySQL/MariaDB
Line 36:		Line 36:
	=== grading_manager_testcase::test_tokenize===		=== grading_manager_testcase::test_tokenize===

	<code>A test using UTF-8 characters has failed. Consider updating PHP and PHP's PCRE or INTL extensions (MDL-30494) Failed asserting that false is true.</~~code~~>		<code>A test using UTF-8 characters has failed. Consider updating PHP and PHP's PCRE or INTL extensions (MDL-30494) Failed asserting that false is true.</syntaxhighlight>

	'''Solution''' Use the utf8mb4_bin collation on your database for unit tests on MySQL/MariaDB		'''Solution''' Use the utf8mb4_bin collation on your database for unit tests on MySQL/MariaDB
Line 42:		Line 42:
	=== moodlesimplepie_testcase::test_getfeed ===		=== moodlesimplepie_testcase::test_getfeed ===

	<code>Failed to load the sample RSS file. Please check your proxy settings in Moodle. %s</~~code~~>		<code>Failed to load the sample RSS file. Please check your proxy settings in Moodle. %s</syntaxhighlight>

	'''Solution''' Your moodle needs network connectivity, please check proxy settings.		'''Solution''' Your moodle needs network connectivity, please check proxy settings.
Line 48:		Line 48:
	=== moodlesimplepie_testcase::test_redirect ===		=== moodlesimplepie_testcase::test_redirect ===

	<code>Failed asserting that 'cURL Error: Operation timed out after 2000 milliseconds with 0 bytes received' is null.</~~code~~>		<code>Failed asserting that 'cURL Error: Operation timed out after 2000 milliseconds with 0 bytes received' is null.</syntaxhighlight>

	'''Solution''' Your moodle needs network connectivity, please check proxy settings		'''Solution''' Your moodle needs network connectivity, please check proxy settings
Line 54:		Line 54:
	=== collatorlib_testcase::test_asort_objects_by_method ===		=== collatorlib_testcase::test_asort_objects_by_method ===

	<code>Collation aware sorting not supported, PHP extension "intl" is not available.</~~code~~>		<code>Collation aware sorting not supported, PHP extension "intl" is not available.</syntaxhighlight>

	'''Solution''' Install php intl extension.		'''Solution''' Install php intl extension.
Line 62:		Line 62:
	=== moodlelib_testcase::test_fix_utf8 ===		=== moodlelib_testcase::test_fix_utf8 ===

	<code>Failed asserting that false is identical to 'aaabbb'.</~~code~~>		<code>Failed asserting that false is identical to 'aaabbb'.</syntaxhighlight>

	'''Solution''' This problem indicates buggy iconv. See [http://tracker.moodle.org/browse/MDL-33007] for discussion. So this is a real problem, to be fixed in a future integration cycle		'''Solution''' This problem indicates buggy iconv. See [http://tracker.moodle.org/browse/MDL-33007] for discussion. So this is a real problem, to be fixed in a future integration cycle
Line 68:		Line 68:
	=== filestoragelib_testcase::test_get_file_preview ===		=== filestoragelib_testcase::test_get_file_preview ===

	<code>Failed asserting that false is an instance of class "stored_file".</~~code~~>		<code>Failed asserting that false is an instance of class "stored_file".</syntaxhighlight>

	'''Solution''' Unfortunately, the php GD extension is a requirement for this test (see MDL-36447).		'''Solution''' Unfortunately, the php GD extension is a requirement for this test (see MDL-36447).

	Go to your Moodle directory and type <code>php admin/tool/phpunit/cli/util.php --drop</~~code~~>, then reinitialise PHPunit and run the test again.		Go to your Moodle directory and type <code>php admin/tool/phpunit/cli/util.php --drop</syntaxhighlight>, then reinitialise PHPunit and run the test again.

	===core_ddl_testcase::test_row_size_limits===		===core_ddl_testcase::test_row_size_limits===

	<code>Row size limit reached in MySQL using InnoDB, configure server to use innodb_file_format=Barracuda and innodb_file_per_table=1</~~code~~>		<code>Row size limit reached in MySQL using InnoDB, configure server to use innodb_file_format=Barracuda and innodb_file_per_table=1</syntaxhighlight>

	""Solution"" default InnoDB database tables in MySQL cannot handle more than 10 text columns, so innodb file format should be Barracuda (see MDL-46971)		""Solution"" default InnoDB database tables in MySQL cannot handle more than 10 text columns, so innodb file format should be Barracuda (see MDL-46971)

	Running <code>php admin/cli/mysql_compressed_rows.php</~~code~~> will solve the problem.		Running <code>php admin/cli/mysql_compressed_rows.php</syntaxhighlight> will solve the problem.

	=== core_phpunit_advanced_testcase::test_locale_reset ===		=== core_phpunit_advanced_testcase::test_locale_reset ===
Line 114:		Line 114:
	This occurs on Mac installs from experience. The reason this occurs is because DBUnit was not installed during the PHPUnit installation via PEAR.		This occurs on Mac installs from experience. The reason this occurs is because DBUnit was not installed during the PHPUnit installation via PEAR.

	'''Solution''' In terminal type: <code>sudo pear install -f phpunit/DbUnit</~~code~~>		'''Solution''' In terminal type: <code>sudo pear install -f phpunit/DbUnit</syntaxhighlight>

	=== !!! Error reading from database !!!!! Unicode data in a Unicode-only collation or ntext data cannot be sent to clients using DB-Library (such as ISQL) or ODBC version 3.7 or earlier. ===		=== !!! Error reading from database !!!!! Unicode data in a Unicode-only collation or ntext data cannot be sent to clients using DB-Library (such as ISQL) or ODBC version 3.7 or earlier. ===
Line 143:		Line 143:

	You need both to:		You need both to:
	# Have python and pip installed and the <code>$CFG->pathtopython</~~code~~> config value pointing to the python executable.		# Have python and pip installed and the <code>$CFG->pathtopython</syntaxhighlight> config value pointing to the python executable.
	# Have the ''moodlemlbackend'' python package installed: <code>pip install moodlemlbackend</~~code~~>		# Have the ''moodlemlbackend'' python package installed: <code>pip install moodlemlbackend</syntaxhighlight>
	to get all the python backend tests being run and, hopefully, passing.		to get all the python backend tests being run and, hopefully, passing.