Fix chromedriver headless syntax for v120#12160
Closed
andreslucena wants to merge 6 commits intodevelopfrom
Closed
Fix chromedriver headless syntax for v120#12160andreslucena wants to merge 6 commits intodevelopfrom
andreslucena wants to merge 6 commits intodevelopfrom
Conversation
Member
Author
|
I can't reproduce the failing specs locally as it seems that google-chrome v120 is just too bleeding edge and not even my operating system has a working version: $ sudo apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
docker-scan-plugin gconf-service gconf-service-backend gconf2-common libgconf-2-4 libwmf0.2-7 linux-headers-6.2.6-76060206 linux-headers-6.4.6-76060406 linux-headers-6.4.6-76060406-generic linux-image-6.4.6-76060406-generic
linux-modules-6.4.6-76060406-generic
Use 'sudo apt autoremove' to remove them.
The following packages have been kept back:
lldb
The following packages will be upgraded:
google-chrome-stable
1 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 105 MB of archives.
After this operation, 4.292 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://apt.pop-os.org/proprietary jammy/main amd64 google-chrome-stable amd64 120.0.6099.109-1 [105 MB]
Err:1 http://apt.pop-os.org/proprietary jammy/main amd64 google-chrome-stable amd64 120.0.6099.109-1
File has unexpected size (104920896 != 104995956). Mirror sync in progress? [IP: 13.224.115.4 80]
Hashes of expected file:
- SHA512:b52970891f84b67645c451c414d852f6642c9e9c73cf1eac21da4c5ef1063a6c5e8149452a6c3a0c8db7462a3c141220047b0c7e7bc7979f6ebe8da0b3a81b32
- SHA256:49c149401f5f6357161ed14ef06a50f32b822da3b502fc8057995b9ea4ab3c2b
- SHA1:77c335292fe19c0f04bd3901e2514089cabbd0b4 [weak]
- MD5Sum:10c1d788d2095aaab106686f0a9754f2 [weak]
- Filesize:104995956 [weak]
E: Failed to fetch http://apt.pop-os.org/proprietary/pool/jammy/main/binary-amd64/g/google-chrome-stable/google-chrome-stable_current_amd64.deb File has unexpected size (104920896 != 104995956). Mirror sync in progress? [IP: 13.224.115.4 80]
Hashes of expected file:
- SHA512:b52970891f84b67645c451c414d852f6642c9e9c73cf1eac21da4c5ef1063a6c5e8149452a6c3a0c8db7462a3c141220047b0c7e7bc7979f6ebe8da0b3a81b32
- SHA256:49c149401f5f6357161ed14ef06a50f32b822da3b502fc8057995b9ea4ab3c2b
- SHA1:77c335292fe19c0f04bd3901e2514089cabbd0b4 [weak]
- MD5Sum:10c1d788d2095aaab106686f0a9754f2 [weak]
- Filesize:104995956 [weak]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?So, in the mean time, as we have a broken test suite, we'll go ahead with #12159 |
65c6273 to
a3a749e
Compare
Member
Author
|
Closing this in favour of #12351 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🎩 What? Why?
Related to the failing spec from #12159, in Selenium they mention that we should fix the syntax of the arguments.
(Same as in #12159, I'm labeling as a fix so we can backport this)
Testing
All the test suite should be green