-
-
Notifications
You must be signed in to change notification settings - Fork 699
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
[16.0][OU-IMP] project: bump version to 1.3 #4362
base: 16.0
Are you sure you want to change the base?
[16.0][OU-IMP] project: bump version to 1.3 #4362
Conversation
6f3d882
to
51e27fb
Compare
Hi @remi-filament. Could you take a look on the CI error ?
|
Hi @remytms
I tried looking at the tests for last commit on PR 4289, and it seems these tests were not run :
So I am not sure if these tests should be working on OCA CI ? Also, it seems to me that on fresh Odoo 16 with demo data, allow_milestones are all false (checked on Odoo runbot) :
Any hint here would be appreciated ? (maybe the above is not the reason why the test is failing ?) |
Hi @legalsylvain I was, our comments came almost at the same time. I do not understand why the test is failing, when looking at previous execution (on PR that added project or on #4361 I made this morning), I do not see this failure, but also, I do not see any hint that this test was run, so I suspect that this test may never have been run before, is that possible ? |
Shouldn't it be better to rerun a new analysis? and then do the necessary changes to adapt to the new results? |
Hi @MiquelRForgeFlow I did a new analysis, you have the following changes which should not have any impact : If you think there is no added interest to move to this latest version in OpenUpgrade script, I can simply close this PR. |
I don't think Can you add it? |
@remi-filament Hi Rémi, In short, I think that Stefan is right, the function I didn't look why theses tests does not fail previously. About the fact of setting |
Odoo PR odoo/odoo#144035 implemented a new version for project 1.3.
When discussing about #4361 @pedrobaeza suggested that it should be better to get the latest version in OpenUpgrade, so I just renamed version from 16.0.1.2 to 16.0.1.3.