[Bug]: Getting error [karma]: { inspect: [Function: inspect] } when running test_js in LMS/CMS

[Rodra]

Describe the bug that you are seeing.

Having all last images pulled (LMS, CMS, chrome and firefox) and also LMS and CMS running up and OK, when accessing the CMS/LMS shell using make cms-shell or make lms-shell and trying to run the unit tests using paver test_js I get the error [karma]: { inspect: [Function: inspect] } on tests set up resulting in now tests being ran.

Did this happen on the host (your machine or the remote instance) or in the container?

Inside the container

Steps to reproduce.

1. Run the following commands to update devstack.
2. Have the LMS and CMS up and running.
3. Enter the CMS shell using make cms-shell.
4. Run paver test_js.
5. Error:

========================================
 Running tests for cms javascript
========================================
29 11 2023 16:15:48.319:WARN [watcher]: Pattern "/edx/app/edxapp/edx-platform/cms/static/jasmine.cms.conf.js" does not match any file.
(node:1878) Warning: Accessing non-existent property 'VERSION' of module exports inside circular dependency
(Use `node --trace-warnings ...` to show where the warning was created)
29 11 2023 16:15:50.737:INFO [karma]: Karma v0.13.22 server started at http://localhost:9876/
changed name to firefox via Selenium Webdriver
29 11 2023 16:15:50.747:INFO [launcher.selenium-webdriver]: SeleniumWebdriverBrowser (kid:81579023) created
29 11 2023 16:15:50.748:INFO [launcher]: Starting browser firefox via Selenium Webdriver
29 11 2023 16:15:50.750:INFO [launcher.selenium-webdriver]: starting firefox via Selenium Webdriver
29 11 2023 16:15:50.758:INFO [launcher.selenium-webdriver]: sending driver to url http://localhost:9876/?id=81579023
29 11 2023 16:15:57.969:ERROR [karma]: { inspect: [Function: inspect] }
29 11 2023 16:15:57.975:INFO [launcher.selenium-webdriver]: requested to kill, session id is 66adfde7-12f7-45d1-8e4e-518774438e40

What system was this issue seen on?

Apple Intel

[github-actions]

Follow-up checklist (for Arch-BOM usage)

• Is the issue flaky or consistent?
• Does it affect multiple people or multiple types of systems?
• Update the devstack troubleshooting documentation page if necessary
  • Do we need a new troubleshooting section?
  • Did a troubleshooting section already exist, but it wasn't easy to find given the symptoms?
  • If a recurring issue, should we ticket an automated resolution in place of the doc?