Hi, I know this is a strange question but I have a horrible bug.
I'm trying to run Karma test runner which uses chrome.
On 29.08 the build succeeded with chrome 84.0.4147.
https://ci.appveyor.com/project/IsraelHikingHost/site/builds/34923360
On 05.09 the build failed (chrome doesn't respond to Karma connection and times out), but I don't know which version of chrome was there.
https://ci.appveyor.com/project/IsraelHikingHost/site/builds/35039521
I know that version 85.0.4183 was released on 25.08 but I don't know when was the image updated with this change.
I opened an issue for chrome, but I'm not 100% sure the issue is with the latest released version (although I can't think of another cause to the issue I'm facing).
I tried to revert the commits which might have caused the issue but it didn't help...
Thanks ahead for all your hard work! I really enjoy appveyor!
When was chrome update on image VS 2019?
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
#1 Posted by harel.mazor on 02 Oct, 2020 09:26 PM
Found it here:
https://www.appveyor.com/updates/
It seems that chrome was updated at 29.08 probably right after my build...
Raises the probability that this is a chrome bug...
#2 Posted by Feodor Fitsner Support staff on 03 Oct, 2020 08:25 PM
Do you still need any help from us to investigate the issue?
#3 Posted by harel.mazor on 03 Oct, 2020 08:30 PM
If you guys know someone from the chrome team who can help move this investigation forward and help solve this issue. Otherwise there's nothing more I need.
Thanks for checking with me.
#4 Posted by harel.mazor on 04 Oct, 2020 06:31 AM
Actually, Feodor, I just came up with something I can check.
Is there a way to use an older image of vs 2019? i.e. can I somehow use the image that was used in the build that succeeded in order to run the latest code?
or is there a way to configure which version of chrome to use in the build machine?
I want to make sure the problem is with chrome and not my code, but I'm not entirely sure how to do it besides run the code that passed on the latest image (which will result in testing only part of the problem).
#5 Posted by Feodor Fitsner Support staff on 05 Oct, 2020 02:29 AM
Sure, you can try
Previous Visual Studio 2019image.#6 Posted by harel.mazor on 05 Oct, 2020 05:44 AM
I'm not sure this is what I need.
According to the following page:
https://www.appveyor.com/updates/
I need the following image:
Visual Studio 2019 image update on July 29, 2020
Which is not the previous one, but the one before it.
Is there a way to tell the build worker to use this one (Jul 29)?
Is there another way you are familiar with to maybe install an older version of Chrome?
#7 Posted by Feodor Fitsner Support staff on 05 Oct, 2020 05:29 PM
Current
Previous Visual Studio 2019image is pointing to August 29th update. Unfortunately, we are not maintaining images older than "previous" one.I'd offer you to uninstall Chrome during the build and install older one, but for some reason it's problematic to find installers of older builds of Chrome. Maybe you can play with Edge of that's Chromium's bug?..
#8 Posted by harel.mazor on 05 Oct, 2020 06:28 PM
I've tried to use edge with Karma but the adapter is old and not maintained so it doesn't work on my PC, I doubt it will work on the build machine.
Currently Ubuntu is running an older version so I can switch to use that as a last resort.
I would like to avoid trying to install older version of chrome if this is not something you guys provide easily like changing node version, or Ruby...
I've opened a ticket for the chromium project, I hope they will fix the issue sooner than later...
Thanks for taking the time to review my issue! :-)