Just want to confirm that I should make 4.1 an M1? Or should it be a RC1? I'll start the release process on Monday.
Volodymyr On 2024/01/16 17:54:49 Volodymyr Siedlecki wrote: > Sounds good. I'll comment out the integration tests for the release. > > Expected a vote out sometime next week! > > Thanks, > Volodymyr > > On 2024/01/16 13:45:46 Thomas Andraschko wrote: > > Hi, > > > > in worst case you can comment out the integration modules in POM for now. > > i currently fix some bugs in MF 4.0.x and will merge them into 4.1 and 5.0. > > If you could do a release next week, it would be great (both 4.0 and 4.1). > > > > Best regards, > > Thomas > > > > > > Am Mi., 10. Jan. 2024 um 16:57 Uhr schrieb Volodymyr Siedlecki < > > volos...@apache.org>: > > > > > Hi, > > > > > > I've been trying to get a successful build locally on my machine for the > > > release, but I've encountered errors with the integration tests: > > > > > > Caused by: > > > org.jboss.arquillian.drone.webdriver.binary.downloading.source.MissingBinaryException: > > > There wasn’t found any binary on the url: > > > https://chromedriver.storage.googleapis.com/114.0.5735.90/chromedriver_mac64_m1.zip > > > at > > > org.jboss.arquillian.drone.webdriver.binary.handler.ChromeDriverBinaryHandler$ChromeStorageSources.getLatestRelease(ChromeDriverBinaryHandler.java:129) > > > at > > > org.jboss.arquillian.drone.webdriver.binary.downloading.source.UrlStorageSource.getLatestRelease(UrlStorageSource.java:59) > > > at > > > org.jboss.arquillian.drone.webdriver.binary.handler.AbstractBinaryHandler.downloadAndPrepare(AbstractBinaryHandler.java:175) > > > at > > > org.jboss.arquillian.drone.webdriver.binary.handler.AbstractBinaryHandler.checkAndSetBinary(AbstractBinaryHandler.java:61) > > > … 14 more > > > > > > The problem above should be fixed via > > > https://github.com/arquillian/arquillian-extension-drone/pull/401 > > > > > > I then tried on Linux, but I can’t get it running either > > > > > > java.lang.RuntimeException: > > > Unable to instantiate Drone via > > > org.openqa.selenium.chrome.ChromeDriver(ChromeOptions): > > > org.openqa.selenium.SessionNotCreatedException: Could not start a new > > > session. Response code 500. Message: unknown error: Chrome failed to > > > start: > > > exited abnormally. > > > (unknown error: DevToolsActivePort file doesn’t exist) > > > (The process started from chrome location /usr/bin/google-chrome is no > > > longer running, so ChromeDriver is assuming that Chrome has crashed.) > > > > > > > > > https://chromedriver.chromium.org/downloads recommends to use "chrome for > > > testing" instead. > > > > > > https://googlechromelabs.github.io/chrome-for-testing/ > > > > > > Current chrome binary is 120.0.6099.199, but the endpoints are down for > > > the stable upcoming API for a previous version. This also causes errors > > > since chrome binary and the chromedriver need to match versions (which I > > > also tried via '-Dwebdriver.chrome.driver', but it still failed). > > > > > > I'll try a few other things, and hope there are more updates to chrome, > > > selenium, and arquillian. Right now I'm a bit stuck. > > > > > > Volodymyr > > > > > > On 2024/01/04 10:04:14 Paul Nicolucci wrote: > > > > +1 from me! > > > > > > > > Thanks, > > > > > > > > Paul Nicolucci > > > > > > > > On Thu, Jan 4, 2024, 4:32 AM Thomas Andraschko < > > > andraschko.tho...@gmail.com> > > > > wrote: > > > > > > > > > +1 (both 4.1 and 4.0) > > > > > just fixing some minor issues and applying PRs, we are ready tomorrow > > > > > > > > > > > > > > > Am Mi., 3. Jan. 2024 um 22:17 Uhr schrieb Melloware < > > > > > melloware...@gmail.com>: > > > > > > > > > >> No objection from me. > > > > >> > > > > >> On 1/3/2024 4:14 PM, Volodymyr Siedlecki wrote: > > > > >> > Hello, > > > > >> > > > > > >> > May I start a 4.1 M1 release for MyFaces? Let me know if there are > > > > >> > objections. > > > > >> > > > > > >> > Additionally, I'm still working on a 4.0.2 release, but focusing on > > > > >> > getting a passing TCK first. > > > > >> > > > > > >> > Best, > > > > >> > > > > > >> > Volodymyr > > > > >> > > > > >> -- > > > > >> Melloware > > > > >> melloware@ > > > > >> > > > > >> > > > > > > > > > >
