docker-robot-framework
docker-robot-framework copied to clipboard
Not rendering the pages properly when using the Chromium browser
We have a project where we run multiple test cases every day using different versions of our product(Nightly, Beta and Production). And we are seeing an issue with Chromium browser where the pages were not properly rendering and showing just a white blank page.
We have a wait and timeout value of upto 30 minutes to render the page completely but unfortunately it wasn't working.
Our test execution environment details are as follows:
- Docker Host with 12GB Memory running Amazon Linux OS and uses 4 Cores of MD EPYC 7R32.
- Docker Image is the latest one with Chromium 86.0
- We have provided the below listed flags to the browser --disable-gpu --disable-dev-shm-usage --no-sandbox --no-proxy-server
- We tried running the same container image with different docker hosts, including MB Pro 15, but the issue was persisted in all of the environments.
Any help would be appreciated, TIA.
can you run a mount with /var/log/chromedriver as a volume and see what the logs outputted say? You can read more about it here: https://github.com/ppodgorsek/docker-robot-framework#accessing-the-logs
Sure. I'll try that and update the details here
Just a reminder that i have uploaded the chromedriver logs.
I dont see any errors in the logs that jump out, does it work if you use firefox? Does it use webgL?
We could see this issue with Firefox as well but not as consistent as with chrome. We don't use WebgL and the code is written mostly on JS and Angular.
i looked a bit closer, i still dont see any errors other than these which seems to imply your app was not logged in. Also if it really is a rendering issue its unlikely to be something we can fix other than pointing you to the upstream team.
[1608800552.349][DEBUG]: DevTools WebSocket Event: Log.entryAdded 26DF6AA31ADE3F646CF575AA0FDB6E23 { "entry": { "level": "error", "networkRequestId": "1291.3595", "source": "network", "text": "Failed to load resource: the server responded with a status of 401 ()", "timestamp": 1.6088005518592961e+12, "url": "https://device.domain.com/scportal/wdsModule/SubscribePublish" } } [1608800552.514][DEBUG]: DevTools WebSocket Response: DOM.getDocument (id=3836) 26DF6AA31ADE3F646CF575AA0FDB6E23 { "root": { "backendNodeId": 2390, "baseURL": "https://device.domain.com/scportal/login.jsp?CUSTOM_MESSAGE=You%20were%20logged%20off%20because%20your%20authentication%20token%20has%20expired.", "childNodeCount": 2, "children": [ { "backendNodeId": 2391, "localName": "", "nodeId": 194, "nodeName": "html", "nodeType": 10, "nodeValue": "", "parentId": 193, "publicId": "", "systemId": "" }, { "attributes": [ "lang", "en-us" ], "backendNodeId": 2392, "childNodeCount": 2, "children": [ { "attributes": [ ], "backendNodeId": 2393, "childNodeCount": 7, "localName": "head", "nodeId": 196, "nodeName": "HEAD", "nodeType": 1, "nodeValue": "", "parentId": 195 }, { "attributes": [ "onload", "resetDynamic();checkCookies();ie8SVGShims()" ], "backendNodeId": 2397, "childNodeCount": 5, "localName": "body", "nodeId": 197, "nodeName": "BODY", "nodeType": 1, "nodeValue": "", "parentId": 195 } ], "frameId": "26DF6AA31ADE3F646CF575AA0FDB6E23", "localName": "html", "nodeId": 195, "nodeName": "HTML", "nodeType": 1, "nodeValue": "", "parentId": 193 } ], "documentURL": "https://device.domain.com/scportal/login.jsp?CUSTOM_MESSAGE=You%20were%20logged%20off%20because%20your%20authentication%20token%20has%20expired.", "localName": "", "nodeId": 193, "nodeName": "#document", "nodeType": 9, "nodeValue": "", "xmlVersion": "" } }
Thank you for your help. I'll discuss this findings with our dev team and also I'll raise a query regarding this in robotframework resouces group. Will keep you updated with the results.
What is the status of this issue? Has it been resolved and can it be closed?
Closing due to inactivity.