Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-75208

Problems with Oracle 21 (phpunit testing failures)

    XMLWordPrintable

Details

    • MOODLE_401_STABLE
    • MOODLE_311_STABLE, MOODLE_400_STABLE
    • Hide

      Automated, by CI runs:

      • Ensure that all the PHPUnit jobs (all DBs) are passing ok.
      • Similarly, this shouldn't cause any regression in other (behat) tests.
      Show
      Automated, by CI runs: Ensure that all the PHPUnit jobs (all DBs) are passing ok. Similarly, this shouldn't cause any regression in other (behat) tests.

    Description

      For Moodle 4.1 Oracle requirements were raised from 11g to 19c (given support timeframes... see MDL-71747 for more info).

      So, we created a new moodle-db-oracle:21 image to be used by CIs and other tools. Oracle 21c was picked, instead of 19c, because it has official XE images and offered better compatibility with the pre-existing (also XE) 11g image.

      Some initial benchmarking has shown that the 21 image is noticeably slower than the 11 one (say 25%, not accurate number!) and this may impact some of the failures we are getting. But not all!

      Here there are some recent runs, using the Oracle 21c image:

      This issue is about to investigate how we can get them back to pass, analysing the causes for all the failures. So, some su-issues should be created about each individual failure type.

      Also, maybe the images themselves need some improvements (that could impact positively to results) and efforts will be done in that area too.

      Ultimately, if this takes too long, we can, in an interim way, skip some of those tests to ensure that everything else continues working ok with Oracle. Till then, we'll get near-consistent failures with Oracle in master (4.1dev).

      Attachments

        Issue Links

          Activity

            People

              stronk7 Eloy Lafuente (stronk7)
              stronk7 Eloy Lafuente (stronk7)
              Simey Lameze Simey Lameze
              Jun Pataleta Jun Pataleta
              CiBoT CiBoT
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 0 minutes
                  0m
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 2 days, 4 hours, 43 minutes
                  2d 4h 43m

                  Clockify

                    Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.