Skip to content
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

Finished substitutions erroneously shown as in progress #144

Open
Atemu opened this issue Jul 18, 2024 · 3 comments
Open

Finished substitutions erroneously shown as in progress #144

Atemu opened this issue Jul 18, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@Atemu
Copy link

Atemu commented Jul 18, 2024

This happened during a remote store + remote build (--store ssh-ng://machine where the store machine has remote builders configured).

┃                      │     │                             ┌─ ↓ ⏵ ncompress-5.0 from [1] ⏱ 22m46s
┃                      │     │                          ┌─ ↓ ✔ libXpm-3.5.17 from [1]
┃                      │     │                       ┌─ ✔ gd-2.3.3 on [5] ⏱ 14s
┃                      │     │                       │  ┌─ ↓ ⏵ pango-1.52.2.tar.xz from [1] ⏱ 22m40s
┃                      │     │                       ├─ ✔ pango-1.52.2 on [4] ⏱ 39s
┃                      │     │                    ┌─ ✔ graphviz-10.0.1 on [4] ⏱ 2m9s

nom says it's substituting some paths whose dependents have already finished building which obviously can't be correct.

Speculation:

This might be due to the fact that the path was already present on the remote (but not the local machine nom runs on) and therefore isn't considered?

@maralorn
Copy link
Owner

thx for the report. I witness something like that regularly myself. Not sure yet what exactly is going on there.

@maralorn maralorn added the bug Something isn't working label Jul 18, 2024
@Atemu
Copy link
Author

Atemu commented Jul 18, 2024

As a workaround, you could at least consider a build/substitute to be done when a dependent starts realising.

@maralorn
Copy link
Owner

I hope we can find a better solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants