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
legendary-gl: 0.20.1 -> 0.20.6 #110823
legendary-gl: 0.20.1 -> 0.20.6 #110823
Conversation
This is a semi-automatic executed nixpkgs-review which is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch). Result of 1 package built:
The following issues got detected with the above build packages. legendary-gl: Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
|
This is a semi-automatic executed nixpkgs-review which is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch). Result of 1 package built:
The following issues got detected with the above build packages. legendary-gl: Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
|
change parameter from "requests" to "legendary" Co-authored-by: Sandro <sandro.jaeckel@gmail.com>
This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch). Result of 1 package built:
|
On January 30, 2021 8:17:16 PM UTC, Wanja Chresta ***@***.***> wrote:
@wchresta requested changes on this pull request.
> };
propagatedBuildInputs = [ requests ];
disabled = pythonOlder "3.8";
+ doCheck = false;
Even though legendary-gl does not define any tests, I would still prefer to leave doCheck as-is. For now, it doesn't make a difference, and if they ever add tests in the future, we're already in the right place.
Otherwise LGTM!
>
+ doCheck = false;
```suggestion
```
Very well! I'll change it in a bit. 😊
|
Please leave the tests disabled. |
Thank you, @equirosa :) |
I copied this from jonringer and added an automated way to check the build logs for it.
The maintainer should check the release notes and if there are new tests adjust the package to execute them. pythonImportsCheck checks for missing packages which catches most of the bugs. If the package is more complicated and requires patching than the maintainer should test it properly anyway. For example if we switch from PyPi to GitHub sources we do not want tests to be executed if they wheren't run before and have potentially failing tests. And the default way we execute tests with setuptools is phasing out anyway and most test suites require pytest. |
Motivation for this change
New versions released with some improvements:
https://github.com/derrod/legendary/releases/tag/0.20.6
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)