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

Retrieve and save error logs eagerly #379

Open
SomeoneSerge opened this issue Nov 27, 2023 · 4 comments
Open

Retrieve and save error logs eagerly #379

SomeoneSerge opened this issue Nov 27, 2023 · 4 comments

Comments

@SomeoneSerge
Copy link

AFAIU, currently the build logs are retrieved during the Report generation, after all of the builds have been finished:

write_error_logs(self.attrs, directory)

In case of mass-rebuilds where a nixpkgs-review run might take a couple of days the build logs can get garbage-collected by that time, and nixpkgs-review would spit out empty files:

❯ bat logs/blender.log 
───────┬────────────────────────────────────────────────────────────────────────────────────────────
       │ File: logs/blender.log   <EMPTY>
@Mic92
Copy link
Owner

Mic92 commented Nov 27, 2023

Maybe we should just disable this step if we go over some threshold of packages?

@Mic92
Copy link
Owner

Mic92 commented Nov 27, 2023

We currently don't have a notification mechanism if an attribute is built.

@SomeoneSerge
Copy link
Author

I thought nom displays the built and failed packages. Maybe json-internal includes some build result message?

Maybe we should just disable this step if we go over some threshold of packages?

The thing is, logs are the main reason I run nixpkgs-review 😅

@Mic92
Copy link
Owner

Mic92 commented Nov 27, 2023

Might be a solution. I haven't yet digged into how json-internal works. I know however that it's not reliable in nom when having remote builders. Some builds are reported pending also they already have finished.

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

No branches or pull requests

2 participants