Closed tobias-urdin closed 1 year ago
should note that I'm talking about the mysql based jobs, for example py38-mysql-file
asking about changed pyparsing error msg in issue here https://github.com/pyparsing/pyparsing/issues/504 related to postgresql job failure
@rafaelweingartner @mrunge this fixes CI, the mysql issue that I saw and spend hours on debugging was an actual mysql issue and nothing with deps, I will work on getting this fixes and fix all branches
@rafaelweingartner @mrunge this fixes CI, the mysql issue that I saw and spend hours on debugging was an actual mysql issue and nothing with deps, I will work on getting this fixes and fix all branches
Thanks! We have been debugging it as well. Today we reached the same point as you. It was working here because we were using different MySQL versions =(
@tobias-urdin are you going to merge this one? Then, I can cherry-pick in my patches to fix other issues, such as the PIP one, and the optimization patch that we have there as well.
This was just for testing, I've opened new PRs against stable branches and master to resolve the CI, I will gladly look at any improvement or other fixes when that is merged and we are green again.
do not merge!
this tests the jobs excluding the upgrade jobs.
there is currently a bug somewhere in the db layer relating to sqlalchemy that makes it not returns the rows in the database when doing the select() function call for the resource history
also the gnocchi code base is not yet prepared for sqlalchemy 2.0 upgrade, if anybody wants to help with that as well that's appreciated, the workflow would be: