Ivan, if Petr can`t help here, how can we change it out own ?
May be we need some help from pmc chair or someone else ?
>
>>
>>Igniters. Almost half of a year passed since this thread begun. We
>>released 0.4.0, we adopted travis-ci and use it as primary source for
>>test results but nothing
Igniters. Almost half of a year passed since this thread begun. We
released 0.4.0, we adopted travis-ci and use it as primary source for
test results but nothing changed in TC
1. We use deprecated pytest-runner (even here
(https://pypi.org/project/pytest-runner) you can see deprecation
notice and
Igor, I've never talked about complete removal of TC builds.
I just suggested to add TC jobs for different python versions and use
travis heavily.
Currently, we have done most of the tasks, except of run TC tests on
different python's versions.
пт, 22 янв. 2021 г. в 15:16, Igor Sapego :
> Ivan
Ivan,
Though I generally agree with the approach you've suggested, I can see
a problem here. Since we now have a separate repos for thin clients, for
some features we may need to introduce changes to Ignite and python-thin
repos in a single ticket and we should have an ability to run tests on with
Hello, Ivan.
I’m +1 for your proposal.
> 25 дек. 2020 г., в 13:14, Ivan Daschinsky написал(а):
>
> Hi folks!
>
> Since we already have a separate repo for thin-clients [1], [2]
> I'd like to propose some improvements in development process/
>
> 1. We should simplify and automate unit tests ru
Hi folks!
Since we already have a separate repo for thin-clients [1], [2]
I'd like to propose some improvements in development process/
1. We should simplify and automate unit tests run for different versions of
python
2. We should add travis integration per commit and pr. Tests could be run
agai
