Skip to content
This repository has been archived by the owner on Apr 24, 2024. It is now read-only.

CI fails at mdbook job #1320

Closed
chr-schr opened this issue Apr 21, 2024 · 4 comments · Fixed by #1332
Closed

CI fails at mdbook job #1320

chr-schr opened this issue Apr 21, 2024 · 4 comments · Fixed by #1332
Assignees
Labels
bug Something isn't working CI

Comments

@chr-schr
Copy link
Contributor

Describe the Bug

With #1306 now fixed, CI fails at the mdbook job when updating the crates-io registry.

Here are some examples:
PR #1303 Pipeline
PR #1297 Pipeline
PR #1298 Pipeline

Error message

#14 [builder 7/7] RUN cargo install --git https://github.com/ElektraInitiative/mdbook-generate-summary mdbook-generate-summary --locked
#14 0.286     Updating git repository `[https://github.com/ElektraInitiative/mdbook-generate-summary`](https://github.com/ElektraInitiative/mdbook-generate-summary%60)
#14 0.899   Installing mdbook-generate-summary v0.1.1 (https://github.com/ElektraInitiative/mdbook-generate-summary#39d7f777)
#14 0.912     Updating crates.io index
#14 42.56 error: Unable to update registry `crates-io`
#14 42.56 
#14 42.56 Caused by:
#14 42.56   failed to fetch `[https://github.com/rust-lang/crates.io-index`](https://github.com/rust-lang/crates.io-index%60)
#14 42.56 
#14 42.56 Caused by:
#14 42.56   network failure seems to have happened
#14 42.56   if a proxy or similar is necessary `net.git-fetch-with-cli` may help here
#14 42.56   https://doc.rust-lang.org/cargo/reference/config.html#netgit-fetch-with-cli
#14 42.56 
#14 42.56 Caused by:
#14 42.56   SSL error: unknown error; class=Ssl (16)
#14 ERROR: process "/bin/sh -c cargo install --git https://github.com/ElektraInitiative/mdbook-generate-summary mdbook-generate-summary --locked" did not complete successfully: exit code: 101

Steps to Reproduce the Problem

Run CI

Expected Result

CI either passes or fails on newly introduced or changed code

Actual Result

CI fails to complete mdbook job

PermaplanT version

see linked PRs

Operating System

Windows

Browser

Chrome

Versions of other relevant software/extensions

No response

Additional info/logs

No response

@chr-schr chr-schr added bug Something isn't working CI labels Apr 21, 2024
@markus2330
Copy link
Contributor

Thx for this beautiful issue! ❤️

We already had this issue before, unfortunately nothing showed up when the admin investigated the network.

Does restarting help?

Does it always fail on the same agent?

Can someone reproduce it locally?

@chr-schr chr-schr linked a pull request Apr 22, 2024 that will close this issue
29 tasks
@chr-schr
Copy link
Contributor Author

chr-schr commented Apr 22, 2024

@markus2330
I tried to fix it by increasing the retry count on network issues and it seems to help: PR 1332 Pipeline

Not sure if that's enough for the time being or @filo14 should take another look

@chr-schr
Copy link
Contributor Author

But logs of the mdbook jobs don't seem to be preserved if successful?

image

image

markus2330 added a commit that referenced this issue Apr 22, 2024
<!--
Check relevant points but **please do not remove entries**.
-->

Trying to fix this issue by increasing the ``CARGO_NET_RETRY``
environment variable to ``10``.
Fixes #1320

## Basics

<!--
These points need to be fulfilled for every PR.
-->

- [x] The PR is rebased with current master
- [x] I added a line to [changelog.md](/doc/changelog.md)
- [x] Details of what I changed are in the commit messages
- [x] References to issues, e.g. `close #X`, are in the commit messages
and changelog
- [x] The buildserver is happy

<!--
If you have any troubles fulfilling these criteria, please write about
the trouble as comment in the PR.
We will help you, but we cannot accept PRs that do not fulfill the
basics.
-->

## Checklist

<!--
For documentation fixes, spell checking, and similar none of these
points below need to be checked.
Otherwise please check below points when getting a PR done.
If nothing is to be done, please check them, too.
-->

- [ ] I fully described what my PR does in the documentation
- [ ] I fixed all affected documentation
- [ ] I fixed the introduction tour
- [ ] I wrote migrations in a way that they are compatible with already
present data
- [ ] I fixed all affected decisions
- [ ] I added automated tests or a [manual test
protocol](../doc/tests/manual/protocol.md)
- [ ] I added code comments, logging, and assertions as appropriate
- [ ] I translated all strings visible to the user
- [ ] I mentioned [every code or
binary](https://github.com/ElektraInitiative/PermaplanT/blob/master/.reuse/dep5)
not directly written or done by me in [reuse
syntax](https://reuse.software/)
- [ ] I created left-over issues for things that are still to be done
- [ ] Code is conforming to [our Architecture](/doc/architecture)
- [ ] Code is conforming to [our Guidelines](/doc/guidelines)
- [ ] Code is consistent to [our Design Decisions](/doc/decisions)
- [ ] Exceptions to any guidelines are documented

## First Time Checklist

<!--
These points are only relevant when creating a PR the first time.
-->

- [ ] I have installed and I am using [pre-commit
hooks](../doc/contrib/README.md#Hooks)
- [ ] I am using [Tailwind CSS
Linting](https://tailwindcss.com/blog/introducing-linting-for-tailwindcss-intellisense)

## Review

<!--
Reviewers can copy&check the following to their review.
Also the checklist above can be used.
But also the PR creator should check these points when getting a PR
done:
-->

- [ ] I've tested the code via issue description
- [ ] I've tested the code via requirements
- [ ] I've tested the code with concurrency (several browsers on the
same map)
- [ ] I've read through the code
- [ ] I've read through the documentation
- [ ] I've checked conformity to guidelines
- [ ] I've checked conformity to requirements
- [ ] I've checked that the requirements are automatically tested
@markus2330
Copy link
Contributor

Let us reopen if it fails again. Otherwise I think this solution is fine. Network problems are hard to debug.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working CI
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants