Bug#1031114: fwd
Major releases are monthly, so v111 will be uploaded in a month, and v112 the month after that. Versions for stable are handled through security uploads, so 110 is currently in bullseye-security and sid (but not yet bookworm due to the migration issues). The ci tests don't really affect bullseye, but there could be breakage with other stuff. On February 12, 2023 4:16:18 PM EST, William Desportes wrote: >Hi, > >> I'm not sure if I should backport the patch to debian's 110 or not. > >It depends on if the version will stay for a long time (a Debian version for >example) or not. >I released the fix so either way it should be okay. for some reason the user >dir option was not needed on CIs. maybe it was on my workstation at this time. > >You could provide backports for this package too, is there a reason you do not >provide backports?
Bug#1031114: fwd
Hi, > I'm not sure if I should backport the patch to debian's 110 or not. It depends on if the version will stay for a long time (a Debian version for example) or not. I released the fix so either way it should be okay. for some reason the user dir option was not needed on CIs. maybe it was on my workstation at this time. You could provide backports for this package too, is there a reason you do not provide backports?
Bug#1031114: fwd
On Sun, 12 Feb 2023 11:41:17 +0100 William Desportes wrote: > Control: tags -1 + pending > Control: forwarded -1 https://salsa.debian.org/js-team/jquery-timepicker/-/commit/21f37b5345ccd800507ca3293d12de70ccee5437 > > It seems like this selenium issue was right: https://github.com/SeleniumHQ/selenium/issues/11634 > > I removed the user-data-dir option. > > On GitLab Salsa I had re-run a job and reproduced the failure: https://salsa.debian.org/js-team/jquery-timepicker/-/jobs/3937872#L495 > > Now it's fixed: https://salsa.debian.org/js-team/jquery-timepicker/-/jobs/3937932#L451 > > Thanks for figuring this out! I found a fix has been committed upstream to chromium driver: https://chromium.googlesource.com/chromium/src/+/b8dc3864aa0ad1048d43353e681bb9d95d7a4a83%5E%21/ https://chromium-review.googlesource.com/c/chromium/src/+/4238878 The bug reports (https://bugs.chromium.org/p/chromedriver/issues/detail?id=4357 and https://bugs.chromium.org/p/chromium/issues/detail?id=1414672) say: "It is going to land in branch 112. Appx. 1 - 2 weeks after it (needed for testing) we will back marge it to the branch 111 and, possibly, to the branch 110" "As a quick workaround you can try passing "--headless=new" instead of "--headless".' I'm not sure if I should backport the patch to debian's 110 or not.
Bug#1031114: fwd
Control: tags -1 + pending Control: forwarded -1 https://salsa.debian.org/js-team/jquery-timepicker/-/commit/21f37b5345ccd800507ca3293d12de70ccee5437 It seems like this selenium issue was right: https://github.com/SeleniumHQ/selenium/issues/11634 I removed the user-data-dir option. On GitLab Salsa I had re-run a job and reproduced the failure: https://salsa.debian.org/js-team/jquery-timepicker/-/jobs/3937872#L495 Now it's fixed: https://salsa.debian.org/js-team/jquery-timepicker/-/jobs/3937932#L451
