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

staging-next 2023-04-05 #224806

Merged
merged 663 commits into from
Apr 12, 2023
Merged

staging-next 2023-04-05 #224806

merged 663 commits into from
Apr 12, 2023

Conversation

mweinelt
Copy link
Member

@mweinelt mweinelt commented Apr 5, 2023

@uninsane
Copy link
Contributor

regression for sequoia: it builds on master (01e82e9) but errors when compiling tests on staging-next: https://hydra.nixos.org/build/215044201/nixlog/4

@vcunat
Copy link
Member

vcunat commented Apr 11, 2023

Yes, rustc upgrade caused a few packages to fail to build. As always, as far as I remember.

@uninsane
Copy link
Contributor

sequoia upstream has a patch which seems to fix this. our sequoia package is already one version behind, so i'll throw up a PR against master later today to update it in a way which also unbreaks it for staging-next.

upstream changelog:
<https://gitlab.com/sequoia-pgp/sequoia/-/compare/sq%2Fv0.27.0...sq%2Fv0.28.0>

changes to the nix package:
- removes the cherry-picked 7916f90421 patch that made it into 0.28.0
- cherry-picks upstream commit 4dc6e624c2 which adds support for newer
  rust versions but didn't make the 0.28.0 release. see
  <#224806>
- adds an update script. future routine updates can be automated with
  `nix-shell maintainers/scripts/update.nix --argstr package sequoia`
@uninsane uninsane mentioned this pull request Apr 11, 2023
12 tasks
github-actions bot and others added 7 commits April 12, 2023 00:02
This fixes parts in llvmPackages_{13,rocm}
e.g. build .clang for testing.
Longterm mass-rebuild fix should come in PR #225846
...into staging-next
In particular, this fixes build after rustc upgrade.
It's weird but this single test started failing in this staging-next
iteration, on all four 64-bit platforms.
I thought this will be better than not having any grafana,
as it's only a single test and our .tests still build.
@vcunat vcunat merged commit 2a32918 into master Apr 12, 2023
@vcunat
Copy link
Member

vcunat commented Apr 12, 2023

I think all major issues were resolved, even though some just in a temporary hacky way.

@@ -31,6 +32,7 @@ stdenv.mkDerivation (finalAttrs: {
libdrm
numactl
valgrind
gcc.cc.libgcc # TODO: unhack this?
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, I'm sorry. Some people run into this unexpected strictness (evaluating even on platforms that are unsupported/broken for the package). Hopefully it will be OK now.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please try #225846 it is the proper fix for this.

@ghost
Copy link

ghost commented Apr 12, 2023

d0bb9ed is causing CI to fail for all PRs targeting staging. Please revert it.

@vcunat
Copy link
Member

vcunat commented Apr 12, 2023

For reference, that commit was amended in fe2ecaf which should fix the CI.

@lblasc
Copy link
Contributor

lblasc commented Apr 19, 2023

Binaries generated by crate2nix (buildRustCrate) are much bigger after this staging iteration, debug and release are affected.

I've tested on some internal crate.

Commit before merge bf839a4b2031557eb43e77d39d343b7ecc84c692:

150M    result/bin

After merge:

1.2G    result/bin

@vcunat
Copy link
Member

vcunat commented Apr 19, 2023

Perhaps bring that up on more specific places, e.g. PR #220373
(seems to be the most likely culprit, at a quick glance)

@ghost
Copy link

ghost commented Apr 20, 2023

Before #210843 buildRustCrate was unconditionally stripping all builds, including debug builds. That was fixed by #210843. Maybe you're doing a debug build? If so, either switch to doing a release build or else strip manually.

I've tested on some internal crate.

Please post a complete reproducer in #210843 if it was the cause; if not, please open a new issue and reference it here. Because github is still stuck in the 1970s, before the world discovered threaded discussions.

@trofi

This comment was marked as outdated.

@trofi

This comment was marked as outdated.

@ghost
Copy link

ghost commented Aug 23, 2023

@trofi this staging-next cycle closed over four months ago; I think you posted your comments in the wrong thread? Also they appear to be exact duplicates of comments you posted elsewhere, and you then immediately marked them as outdated. Are you using some kind of git-hub API client that is doing this?

@trofi
Copy link
Contributor

trofi commented Aug 23, 2023

I posted the comment in the wring branch as github UI shown only this branch as a source branch. I realized it too late and re-posted comment to the intended branch that I suspect caused the regression.

I marked comments here as hidden as Obsolete because they are not directly relevant to this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

None yet