Uh oh!
There was an error while loading. Please reload this page.
feat: [WIP] The first stage of nox implementation - #468
Conversation
mf2199
commented
Aug 25, 2020
Below is the initial test log. Most deprecation warnings were omitted for better readability, leaving a few as an example. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
@c24t For the reference, here's the As you might see, the assertion errors are the same as with |
c24t
commented
Aug 25, 2020
SGTM as long as we've got the same failing tests in each version. Looks like 2.7 and 3.5 aren't installed on your machine? Hopefully those have the same failures. |
c24t
commented
Aug 25, 2020
If the goal is to replace tox with nox, can we remove |
mf2199
commented
Aug 25, 2020
Sure thing, both Done! |
c24t
left a comment
There was a problem hiding this comment.
LGTM to go ahead, next step is to get these (previously failing) tests working under nox and add support for multiple django versions.
mf2199
commented
Aug 25, 2020
Sounds like plan, thanks! Shall it be a separate PR or an amendment to this one? |
c24t
commented
Aug 25, 2020
A separate PR SGTM. One more wrinkle though, python-spanner-django/.kokoro/build.sh Lines 32 to 38 in 11222db tox with nox. |
mf2199
commented
Aug 25, 2020
👍 Good catch! Done. Just for kicks, installed Py27, Py35, and re-ran the tests - no additional errors. |
c24t
commented
Aug 25, 2020
I see 43b186e removes |
mf2199
commented
Aug 25, 2020
Totally, as we add |
Actually, this may not even be necessary, as |
As suggested in #466 , this represents the first item of the recommended list aimed to implement
noxtesting automation in multiple steps.Change list:
noxfile.pywith the same targets as the existingtox.ini[the commented areas reflect future targets];.gitignore.From the results of the initial testing, the code has numerous assertion errors, see the test log below, which appear to be "normal" errors related to failing tests rather the test setup as such. Similar errors observed when using the
toxframework.Towards #474