Hi Piotr As I mentioned in my previous email ... the path with the geckodriver will no longer work. The last time I worked together with Infra to get it working and we did that by changing the way the Jenkins Agent is started. This change however had negative issues on the availability of the nodes, so infra changed back to the default way.
So I could whip up a PR that disables the parts that are failing the build, but this should only be an intermediate solution. You want me to do that? Chris Am 27.08.20, 19:58 schrieb "Piotr Zarzycki" <[email protected]>: Guys, There is a response from INFRA [1] - if someone have time to look it would be good. Our build is failing for a long time now. Unfortunately I'm pretty busy lately and will be for the next week. [1] https://issues.apache.org/jira/browse/INFRA-20679 Thanks, Piotr czw., 13 sie 2020 o 11:15 Piotr Zarzycki <[email protected]> napisał(a): > Hi Guys, > > I have raised jira [1] for infra to install gecko > > [1] https://issues.apache.org/jira/browse/INFRA-20679 > > Thanks, > Piotr > > wt., 11 sie 2020 o 19:18 Christofer Dutz <[email protected]> > napisał(a): > >> Hi Piotr, >> >> The windows agents are now started differently, therefore no longer an >> interactive user session is available. >> So even if you installed the geckodriver, it wouldn't be able to run >> anymore. >> >> So the options are: >> 1) Disable the test (not ideal) >> 2) Port the test to a framework that is able to work without the >> interactive user session (like cypress.io or maybe others) >> >> I would strongly opt for option 2 as I built these tests years ago to >> address a pretty severe problem. >> >> I did like the idea of having a pure virtual browser, that can work >> without any form of graphic system. >> >> Chris >> >> >> >> >> Am 11.08.20, 18:59 schrieb "Piotr Zarzycki" <[email protected]>: >> >> Thanks Chris I will read it. >> >> My question remains anyone know what should I install on machine to >> move >> forward? >> >> On Tue, Aug 11, 2020, 6:53 PM Christofer Dutz < >> [email protected]> >> wrote: >> >> > So the discussion I was referring to was this one: >> > >> > >> > >> https://lists.apache.org/thread.html/r8c971418756b3be47175854b512d4b0b3b28a740b73f1990696eef23%40%3Cdev.royale.apache.org%3E >> > >> > I suggested to give cypress.io a try. >> > >> > Chris >> > >> > Am 11.08.20, 18:50 schrieb "Christofer Dutz" < >> [email protected]>: >> > >> > I don't remember the thread and exactly when, but I posted some >> > possible options then. >> > >> > So I thought, if you could happen to dig out the issue, there >> might be >> > some answers. >> > >> > But don't bother ... I'll do the search. >> > >> > Chris >> > >> > Am 11.08.20, 17:48 schrieb "Piotr Zarzycki" < >> [email protected] >> > >: >> > >> > Hi Chris, >> > >> > How is this help to resolve the issue ? >> > >> > wt., 11 sie 2020 o 17:34 Christofer Dutz < >> > [email protected]> >> > napisał(a): >> > >> > > Hi Piotr, >> > > >> > > that was why I suggested to change the web-driver >> framework to >> > one that >> > > doesn't require an agent like that. >> > > >> > > Chris >> > > >> > > >> > > Am 11.08.20, 16:59 schrieb "Piotr Zarzycki" < >> > [email protected]>: >> > > >> > > Hi Guys, >> > > >> > > Does anyone know what plugin should be installed in >> order to >> > overcome >> > > this >> > > issue [1] - Our build on new server is failing. >> > > >> > > I see gecko, but I'm not entirely sure what should I >> put in >> > jira as a >> > > installation request. >> > > >> > > [1] >> > > >> > https://ci-builds.apache.org/job/Royale/job/Royale-asjs/11/console >> > > >> > > Thanks, >> > > -- >> > > >> > > Piotr Zarzycki >> > > >> > > >> > >> > -- >> > >> > Piotr Zarzycki >> > >> > >> > >> >> > > -- > > Piotr Zarzycki > -- Piotr Zarzycki
