Fix test failures in 4.0.x (missing schema definition, etc)

This should cover it.

The last submitted patch, 2: lingotek-n3361327-2.patch, failed testing. View results →

That's good - it's down from 321 failures to only 31.

Down to 19! Nice!

Adding the fix for drupal CI issue on 4.0.x here

Resetting the previous commit since we got some fatal errors instead

A couple of questions here that might help me contribute a little better than I have been.

These tests are required for D10 (so PHP 8.1). This ticket appears to be for D9.5, but it is a blocker for #3288313. And there is also #3344857 that seems to cover this issue + a number of other test-related errors. D9.5 is EOL on 1 November. We also appear to have a D10 build issue that doesn't seem to be resolved in any of these tickets and relates to the composer permissions afforded the cweagans patch library.

My first question is, what is a plan of attack to get Lingotek to D10?

My second question is, given that there are roughly 7,000 phpstan errors thrown up on my D10 build (using Drupal check) on the tests alone and just 19 being thrown for the D9.5 build above and the matter of D9.5 EOL, is it meaningful putting effort into D9.5 at all?

Probably, I am missing something/a whole lot – apologies in advance.

Trying to fix the build on 9.5 will mean there's a cleaner slate to work from for D10, so that on the D10 issue it'll be easier to tell whether test failures are because of the D10 changes or an existing bug.

With #16, 100% tests are passing on my local, not sure whats the deal with "Composer Config Failure"

Sounds like an infrastructure problem.

The composer problems have been fixed elsewhere, the latest patch now just has five errors.

Is this redundant now?

Yes, I believe that this was covered in #3288313. @npaudyal001, could you confirm and then close this issue please?

I think if you're going to list the 4.0.x branch as still maintained then the tests should still be fixed. On the other hand, if you're going to mark the 4.0.x branch unsupported then this could be closed.

Automatically closed - issue fixed for 2 weeks with no activity.