-
Notifications
You must be signed in to change notification settings - Fork 126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: Build only netwerk
component on CI
#2164
Conversation
Failed Interop TestsQUIC Interop Runner, client vs. server neqo-latest as client
neqo-latest as server
All resultsSucceeded Interop TestsQUIC Interop Runner, client vs. server neqo-latest as client
neqo-latest as server
Unsupported Interop TestsQUIC Interop Runner, client vs. server neqo-latest as client
neqo-latest as server
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2164 +/- ##
==========================================
- Coverage 95.39% 95.38% -0.01%
==========================================
Files 112 112
Lines 36373 36373
==========================================
- Hits 34697 34696 -1
- Misses 1676 1677 +1 ☔ View full report in Codecov by Sentry. |
Signed-off-by: Lars Eggert <[email protected]>
neqo_glue
on CIneqo_glue
on CI
neqo_glue
on CInetwerk
component on CI
@mxinden the
|
Sorry for leading you astray here. As discussed on Slack, I guess there is no way to build |
This seems to be impossible. |
Save some trees by only building the
netwerk
bits of Firefox in CI. To build the entire browser, do a manualworkload_dispatch
.