From 387102411d8fab50e2dc11963884bca9f3649644 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Vladim=C3=ADr=20=C4=8Cun=C3=A1t?= <v@cunat.cz>
Date: Sat, 21 Jan 2023 09:53:45 +0100
Subject: [PATCH] python3Packages.scipy: schedule as big-parallel on Hydra

After 9503adb666001 the tests can take many hours or even time out:
https://hydra.nixos.org/job/nixpkgs/staging-next/python310Packages.scipy.x86_64-linux#tabs-charts
That's because without big-parallel we use --cores 2;
I just hope that with big-parallel it won't be exploding
like described around the 9503adb666001 commit.

(cherry picked from commit 020eb79d627550160864631e869c48ad67ecbe02)
---
 pkgs/development/python-modules/scipy/default.nix | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/pkgs/development/python-modules/scipy/default.nix b/pkgs/development/python-modules/scipy/default.nix
index 457a9c622a12..9091563bb4e8 100644
--- a/pkgs/development/python-modules/scipy/default.nix
+++ b/pkgs/development/python-modules/scipy/default.nix
@@ -75,6 +75,8 @@ buildPythonPackage rec {
     runHook postCheck
   '';
 
+  requiredSystemFeatures = [ "big-parallel" ]; # the tests need lots of CPU time
+
   passthru = {
     blas = numpy.blas;
   };