+1 maintenance report - 28th and 29th November

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

+1 maintenance report - 28th and 29th November

Lucas Kanashiro
Hi,

My +1 maint shift was supposed to be the whole week but there are some side projects that did not allow me to do so. I have worked on +1 maint yesterday and today. I focused mainly on ruby packages, there is a small change where rubygems was extracted from the interpreter source package and now it has its own source package (which also ships bundler). Many packages FTBFS and tests failed because of uninstallability issues (rubygems and bundler), to fix it I needed to:

- ruby-defaults: sync version 1:2.7+2 from Debian unstable. rubygems will not migrate without this new version.
- rubygems: investigated test failures. Fixed in Debian version 3.2.0~rc.2-4 (should land in proposed soon).

Fixed FTBFS because rubygems binaries are not installable:

- rails
- ruby-serverengine
- ruby-apollo-upload-server
- ruby-jekyll-polyglot
- ruby-jquery-ui-rails
- ruby-asset-sync
- ruby-dalli
- ruby-data-migrate
- ruby-enumerize
- ruby-execjs
- ruby-jekyll-default-layout
- ruby-jekyll-feed
- ruby-jekyll-include-cache
- ruby-jekyll-readme-index
- ruby-jekyll-seo-tag
- ruby-jekyll-toc
- ruby-leaflet-rails
- ruby-specinfra
- ruby-strptime
- ruby-webpacker

Test failures because rubygems binaries are not installable:

- ruby-backbone-on-rails
- ruby-bootstrap-sass
- ruby-bootstrap-switch-rails
- ruby-markdown-it-html5-embed
- ruby-rails-assets-corejs-typeahead
- ruby-rails-assets-fine-uploader
- ruby-rails-assets-jquery
- ruby-rails-assets-jquery-nicescroll
- ruby-rails-assets-jquery.are-you-sure
- ruby-rails-assets-markdown-it-diaspora-mention
- ruby-rails-assets-perfect-scrollbar

Some of those tests might fail because they need some extra triggers. I am still waiting for results and I will keep tracking them, and also the new ruby-defaults and rubygems tests.

Some work unrelated to the ruby-defaults/rubygems changes:

- ruby-pygements.rb: run tests with the right triggers in arm64 and armhf (migrated).
- ruby-activeldap: run tests with the right triggers in amd64 and armhf (migrated)
- prometheus-sql-exporter: run tests with the right triggers in armhf (migrated).
- ruby-doorkeeper-openid-connect: run tests in all arches with proper triggers to unblock ruby-doorkeeper (migrated).
- ruby-doorkeeper-openid-connect: request another amd64 build to pull in ruby-doorkeeper from proposed. FTBFS fixed.
- rclone: request another build in ppc64el. It seems like a flaky test. FTBFS fixed.

--
ubuntu-devel mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Reply | Threaded
Open this post in threaded view
|

Re: +1 maintenance report - 26th and 27th November

Lucas Kanashiro
Sorry, in the subject it should be 26th and 27th (not 28th and 29th :)

On Fri, Nov 27, 2020 at 5:41 PM Lucas Kanashiro <[hidden email]> wrote:
Hi,

My +1 maint shift was supposed to be the whole week but there are some side projects that did not allow me to do so. I have worked on +1 maint yesterday and today. I focused mainly on ruby packages, there is a small change where rubygems was extracted from the interpreter source package and now it has its own source package (which also ships bundler). Many packages FTBFS and tests failed because of uninstallability issues (rubygems and bundler), to fix it I needed to:

- ruby-defaults: sync version 1:2.7+2 from Debian unstable. rubygems will not migrate without this new version.
- rubygems: investigated test failures. Fixed in Debian version 3.2.0~rc.2-4 (should land in proposed soon).

Fixed FTBFS because rubygems binaries are not installable:

- rails
- ruby-serverengine
- ruby-apollo-upload-server
- ruby-jekyll-polyglot
- ruby-jquery-ui-rails
- ruby-asset-sync
- ruby-dalli
- ruby-data-migrate
- ruby-enumerize
- ruby-execjs
- ruby-jekyll-default-layout
- ruby-jekyll-feed
- ruby-jekyll-include-cache
- ruby-jekyll-readme-index
- ruby-jekyll-seo-tag
- ruby-jekyll-toc
- ruby-leaflet-rails
- ruby-specinfra
- ruby-strptime
- ruby-webpacker

Test failures because rubygems binaries are not installable:

- ruby-backbone-on-rails
- ruby-bootstrap-sass
- ruby-bootstrap-switch-rails
- ruby-markdown-it-html5-embed
- ruby-rails-assets-corejs-typeahead
- ruby-rails-assets-fine-uploader
- ruby-rails-assets-jquery
- ruby-rails-assets-jquery-nicescroll
- ruby-rails-assets-jquery.are-you-sure
- ruby-rails-assets-markdown-it-diaspora-mention
- ruby-rails-assets-perfect-scrollbar

Some of those tests might fail because they need some extra triggers. I am still waiting for results and I will keep tracking them, and also the new ruby-defaults and rubygems tests.

Some work unrelated to the ruby-defaults/rubygems changes:

- ruby-pygements.rb: run tests with the right triggers in arm64 and armhf (migrated).
- ruby-activeldap: run tests with the right triggers in amd64 and armhf (migrated)
- prometheus-sql-exporter: run tests with the right triggers in armhf (migrated).
- ruby-doorkeeper-openid-connect: run tests in all arches with proper triggers to unblock ruby-doorkeeper (migrated).
- ruby-doorkeeper-openid-connect: request another amd64 build to pull in ruby-doorkeeper from proposed. FTBFS fixed.
- rclone: request another build in ppc64el. It seems like a flaky test. FTBFS fixed.

--
ubuntu-devel mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel