Skip to content

ci: update series to most recent ecosystem#550

Open
Hyask wants to merge 1 commit intomainfrom
skia/ci_update_series
Open

ci: update series to most recent ecosystem#550
Hyask wants to merge 1 commit intomainfrom
skia/ci_update_series

Conversation

@Hyask
Copy link
Contributor

@Hyask Hyask commented Jan 5, 2026

This PR is also an excuse for running the CI now and confirm that it's broken in the same way as the resolute FTBFS: https://bugs.launchpad.net/apport/+bug/2137479

@github-actions
Copy link

github-actions bot commented Jan 5, 2026

Hey! Hyask has not signed the Canonical CLA which is required to get this contribution merged on this project.

Please head over to https://ubuntu.com/legal/contributors to read more about it.

@codecov
Copy link

codecov bot commented Jan 5, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.33%. Comparing base (ca397b2) to head (1169a80).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #550      +/-   ##
==========================================
- Coverage   84.34%   84.33%   -0.01%     
==========================================
  Files         104      104              
  Lines       20814    20814              
  Branches     3254     3192      -62     
==========================================
- Hits        17555    17554       -1     
- Misses       2816     2817       +1     
  Partials      443      443              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@Hyask Hyask force-pushed the skia/ci_update_series branch 2 times, most recently from e0d2f4d to 9e26955 Compare January 5, 2026 15:33
Signed-off-by: Florent 'Skia' Jacquet <skia@ubuntu.com>
@Hyask Hyask force-pushed the skia/ci_update_series branch from 2cd647d to 1169a80 Compare January 6, 2026 09:26
@bdrung
Copy link
Member

bdrung commented Jan 9, 2026

Can you split this PR into multiple (drop oracular, add resolute, update debian stable) since the CI is failing?

@Hyask
Copy link
Contributor Author

Hyask commented Jan 15, 2026

@bdrung
Oops, missed that comment, sorry.
I see you already opened another PR for Oracular, but didn't merge. Is there a reason?
Also, yes, CI is failing, it's in the process of being fixed through Ubuntu (for the Resolute part at least), so I guess I'll revisit this when it'll have a chance of becoming green.

@bdrung
Copy link
Member

bdrung commented Jan 16, 2026

I fought with the new repository setting (signed commit). oracular is merged. Now we need to land #553 to get the CI green.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants