Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Run everything with unpinned selenium versions #71

Open
stronk7 opened this issue Feb 18, 2022 · 3 comments
Open

Run everything with unpinned selenium versions #71

stronk7 opened this issue Feb 18, 2022 · 3 comments

Comments

@stronk7
Copy link
Member

stronk7 commented Feb 18, 2022

With the release of Chrome 98 (and the corresponding Selenium image), we should be able to perform all CI runs unpinned.

I've just added a commit to the "testing" branch:

testing~1...testing

And going to launch a bunch of jobs to verify how that change behaves.

  • 39_STABLE:

    • Goutte (unrelated, but): Build Status
    • Chrome (boost, headless): Build Status
    • Chrome (classic, headed): Build Status
    • Firefox (boost, headed): Build Status
    • Firefox (classic, headless): Build Status
  • 310_STABLE:

    • Goutte (unrelated, but): Build Status
    • Chrome (boost, headless): Build Status
    • Chrome (classic, headed): Build Status
    • Firefox (boost, headed): Build Status
    • Firefox (classic, headless): Build Status
  • 311_STABLE:

    • Goutte (unrelated, but): Build Status
    • Chrome (boost, headless): Build Status
    • Chrome (classic, headed): Build Status
    • Firefox (boost, headed): Build Status
    • Firefox (classic, headless): Build Status
  • master:

    • Goutte (unrelated, but): Build Status
    • Chrome (boost, headless): Build Status
    • Chrome (classic, headed): Build Status
    • Firefox (boost, headed): Build Status
    • Firefox (classic, headless): Build Status

Notes:

Just creating the issue to have it registered and a place to annotate results and notes.

Ciao :-)

@andrewnicols
Copy link
Collaborator

New Selenium release (4.6.0) with the latest Chrome and Firefox versions:

Firefox:

  • Master: Build Status
  • 400: Build Status
  • 311: Build Status
  • 39: Build Status

Chrome:

  • Master: Build Status
  • 400: Build Status
  • 311: Build Status
  • 39: Build Status

@andrewnicols
Copy link
Collaborator

3.9 and 3.11 are failing because of a step which was introduced for 3.11 onwards and was not backported.
https://tracker.moodle.org/browse/MDL-76207 raised which should resolve this.

@andrewnicols
Copy link
Collaborator

New Selenium release (4.6.0) with the latest Chrome and Firefox versions after MDL-76207:

Firefox:

  • Master: Build Status
  • 400: Build Status
  • 311: Build Status
  • 39: Build Status

Chrome:

  • Master: Build Status
  • 400: Build Status
  • 311: Build Status
  • 39: Build Status

andrewnicols added a commit to andrewnicols/moodle-ci-runner that referenced this issue Nov 15, 2022
These are now passing with all of our tests.

Fixes moodlehq#71
andrewnicols added a commit that referenced this issue Aug 30, 2023
These are now passing with all of our tests.

Fixes #71
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants