-
-
Notifications
You must be signed in to change notification settings - Fork 12.7k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
python.pkgs.hypothesis: 3.11.0 -> 3.11.1
- Loading branch information
Showing
1 changed file
with
2 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2050213
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@FRidh I get this error building something on Darwin using latest master.
2050213
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I think you may have the wrong hash here @FRidh - I get
0damf6zbm0db2a3gfwrbbj92yal576wpmhhchc0w0np8vdnax70n
.2050213
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@FRidh: this is a mass rebuild commit (and perhaps some other commits around as well). More than half of all jobs are now rebuilt by Hydra on master. Go with such commits through staging first, please :-(
If you find it difficult to see what's a mass rebuild, you can use a WIP of mine; discussion on #19045.
2050213
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is partly my fault, I merged something that introduced a bunch of extra python dependencies into the darwin stdenv.
2050213
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not darwin-specific.
2050213
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2050213
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So in the script I have to check whether we are using a)
fetchPypi
or b) an url that containspypi
. Otherwise, it should abort.2050213
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't understand what mess you mean.
2050213
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@vcunat it took a month for commits that went into staging to arrive in master because there were a) commits that weren't fixed and/or b) evaluations that did not finish.
In any case, I've fixed the Hypothesis issue. I think its best to directly merge staging back in master so that Hydra won't build two different sets.
2050213
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For at least a week I was repeatedly killing the staging evaluations exactly because there were more and more mass rebuilds coming to master, so staging would never catch up (because it's low-priority set on Hydra). It's true that the Eelco's change also took me some time to fix most of the failing packages due to newly detected bad RPATH items.
Hmm, merged then. It's certainly better not to build it twice, though I would have preferred to do the rebuild on staging instead, as that's what it's for.