ci: Switch to using geckodriver#6541
Conversation
6de85b5 to
75c9868
Compare
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #6541 +/- ##
=======================================
Coverage 88.82% 88.83%
=======================================
Files 285 285
Lines 40230 40224 -6
=======================================
- Hits 35734 35732 -2
+ Misses 4496 4492 -4 ☔ View full report in Codecov by Sentry. |
…racker into ci-selenium-geckodriver
jennifer-richards
left a comment
There was a problem hiding this comment.
Looks ok to me (and tests run, though with a couple failures, on my m2 mac)
jennifer-richards
left a comment
There was a problem hiding this comment.
Withdrew my approval - noticed that the geckodriver tests didn't actually run here. I think it pulls the standard base image, so doesn't have geckodriver installed. Testing locally, there are some changes needed.
The inputs are hidden and managed by JS, so click the visible elements instead.
Waiting for the button to be clickable does not work because the modal is still fading in, so does not actually close. Would be better to check for it responding, but I haven't found the right way to do that yet.
|
Those commits fix the selenium tests under |
|
With the last commit, all tests pass for me. |
Sending '\n' does not seem to work as it did before, so click the option instead. Also reverted some fixme hacks that seem to be obe.
rjsparks
left a comment
There was a problem hiding this comment.
Please move this to draft until it passes in both CI and on both mac and windows developer's platforms
|
You need to rebuild the base docker image locally first to have geckodriver available in the dev image. |
That's what I've done locally (mac). Can you check whether the tests I touched work on your system? (I'm a little worried that I may have undone workarounds that are platform dependent in my purported fixes) |
|
For me (m2 mac, geckodriver 0.33.0 (a80e5fd61076 2023-04-02 18:31 +0000)): I previously ran the whole suite (without the |
|
Tests passed now... |
|
Tests are still passing for me on my M2. Still have the bootstrapping problem for running the selenium tests on github CI, though. |
|
geckodriver added to the base image. |
|
What can we do to get insight into why geckodriver is crashing in the test container? |
|
@rjsparks Use the tests debug script:
While this will run in the same environment setup as GHA, including the container being limited to 2 cores and 7GB of RAM, you'll be running in arm64, while GHA is using x64. So if you don't get the errors, a x64 environment would be needed to properly reproduce. I was not able to reproduce the crash on my side... |
|
What's in |
|
@larseggert https://github.com/ietf-tools/datatracker/suites/18134236487/artifacts/1045634129 The recurring error being: |
|
Adding This is a long standing firefox specific bug that they can't be bothered to fix. |
Because that works also on
amd64.