mirror of
https://github.com/php/php-src.git
synced 2025-08-15 21:48:51 +02:00
ext/dba/tests: sort expected test output (#14962)
* ext/dba/tests/setup/setup_dba_tests.inc: sort test output Iterating through a database with firstkey() and nextkey() is guaranteed to retrieve all rows, but apparently not in any particular order. This is causing a test failure for at least one user, so we steal the sort() approach from GDBM to ensure that the output is predictable. * ext/dba/tests/dba_*.phpt: sort expected test output The actual output is now sorted for consistency, so we need to update the expected output as well. As a nice side effect, some differences in the expected outputs for the various engines have been eliminated. Closes GH-14786 * ext/pgsql/tests/80_bug14383.phpt: sort expected test output This test uses a routine from ext/dba that now sorts its (actual) output, so we have to sort the expected output here as well. * ext/dba/tests/setup/setup_dba_tests.inc: update comment After doing some more digging, it looks like GDBM isn't the only engine where the iteration order with firstkey() and nextkey() might change unexpectedly.
This commit is contained in:
parent
ab449a7e46
commit
44b0baf705
8 changed files with 47 additions and 32 deletions
|
@ -39,12 +39,12 @@ bool(true)
|
|||
bool(true)
|
||||
Try to remove key 1 again
|
||||
bool(false)
|
||||
[key10]name10: Content String 10
|
||||
[key30]name30: Content String 30
|
||||
key2: Content String 2
|
||||
key4: Another Content String
|
||||
key5: The last content string
|
||||
name9: Content String 9
|
||||
[key10]name10: Content String 10
|
||||
[key30]name30: Content String 30
|
||||
Total keys: 6
|
||||
Key 1 exists? N
|
||||
Key 2 exists? Y
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue