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

pythonPackages.flaky: 3.5.3 -> 3.6.1 #68411

Merged
merged 1 commit into from Sep 16, 2019
Merged

Conversation

prusnak
Copy link
Member

@prusnak prusnak commented Sep 10, 2019

Motivation for this change

Version update. This update fixes annoying bug box/flaky#156

Might be worth backporting to 19.09.

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.
Notify maintainers

cc @

@prusnak
Copy link
Member Author

prusnak commented Sep 16, 2019

@disassembler should we backport this to 19.09?

vcunat added a commit that referenced this pull request Sep 16, 2019
This reverts commit b44fca1.
I'm moving this to the staging branch.
It's a huge rebuild (on the order of 20k jobs), and it seems like that
was not noticed, and I can't see sufficient motivation to skip ahead of
e.g. the CVE fixes we have in staging-next.
vcunat added a commit that referenced this pull request Sep 16, 2019
This reverts commit a95a53a.
i.e. the change is moved from the master branch to staging.
vcunat added a commit that referenced this pull request Sep 16, 2019
This reverts commit 755c9f3.
I'm moving this to the staging-19.09 branch, similarly to a95a53a.
It's a huge rebuild (on the order of 20k jobs), and it seems like that
was not noticed, and I can't see sufficient motivation to skip ahead of
other changes in staging-19.09.  Here my motivation is mainly to reduce
the total amount of work necessary for Hydra.
vcunat added a commit that referenced this pull request Sep 16, 2019
This reverts commit 047e326.
i.e. the change is moved from the release-19.09 branch to staging-19.09.
@vcunat
Copy link
Member

vcunat commented Sep 16, 2019

As shown by GitHub, I took the liberty of moving this change to the staging branches without asking – because of causing lots of work for Hydra (apparently unintentionally). It should just delay having this change for a bit – possibly something like a week, in case of master.

dtzWill pushed a commit to dtzWill/nixpkgs that referenced this pull request Jan 1, 2020
This reverts commit a95a53a.
i.e. the change is moved from the master branch to staging.

(cherry picked from commit 14f5e92)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants