Wednesday, 2020-12-02

*** sboyron has quit IRC00:07
*** weshay|ruck is now known as weshay|pto00:41
*** dklyle has quit IRC00:48
*** ociuhandu has joined #openstack-infra01:03
*** ociuhandu has quit IRC01:08
*** vesper11 has joined #openstack-infra01:09
*** Goneri has quit IRC01:27
*** rcernin has quit IRC01:37
*** rcernin has joined #openstack-infra01:39
*** bdodd has quit IRC01:57
*** carloss has quit IRC02:02
*** rlandy has quit IRC02:15
*** ysandeep|away is now known as ysandeep02:18
*** ajitha has joined #openstack-infra02:32
*** rcernin has quit IRC02:36
*** rfolcOUT has joined #openstack-infra02:50
*** ociuhandu has joined #openstack-infra02:52
*** ociuhandu has quit IRC02:56
*** iurygregory|pto has quit IRC03:01
*** rfolcOUT has quit IRC03:05
*** rcernin has joined #openstack-infra03:06
*** bdodd has joined #openstack-infra03:31
*** vishalmanchanda has joined #openstack-infra04:38
*** ociuhandu has joined #openstack-infra04:40
*** ociuhandu has quit IRC04:45
*** soniya29 is now known as soniya29|sick04:56
*** ykarel has joined #openstack-infra05:23
*** evrardjp has quit IRC05:33
*** evrardjp has joined #openstack-infra05:33
*** rcernin has quit IRC05:43
*** rcernin has joined #openstack-infra05:55
*** matt_kosut has joined #openstack-infra06:10
*** zbr has quit IRC06:13
*** zbr has joined #openstack-infra06:14
*** hamalq has quit IRC06:17
*** hamalq has joined #openstack-infra06:18
*** ociuhandu has joined #openstack-infra06:28
*** gyee has quit IRC06:30
*** ociuhandu has quit IRC06:33
*** sboyron has joined #openstack-infra06:42
*** lmiccini has joined #openstack-infra06:49
*** sboyron has quit IRC06:55
*** ociuhandu has joined #openstack-infra07:02
*** ociuhandu has quit IRC07:06
*** zzzeek has quit IRC07:13
*** zzzeek has joined #openstack-infra07:14
*** eolivare has joined #openstack-infra07:27
*** lpetrut has joined #openstack-infra07:38
*** rcernin has quit IRC07:38
*** rcernin has joined #openstack-infra07:44
*** rcernin has quit IRC07:48
*** slaweq has joined #openstack-infra07:56
*** zxiiro has quit IRC07:57
*** hashar has joined #openstack-infra08:00
*** rcernin has joined #openstack-infra08:01
*** hashar has quit IRC08:04
*** hashar has joined #openstack-infra08:04
*** sboyron has joined #openstack-infra08:05
*** mmethot_ has joined #openstack-infra08:07
*** ociuhandu has joined #openstack-infra08:08
*** ociuhandu has quit IRC08:08
*** mmethot has quit IRC08:09
*** ociuhandu has joined #openstack-infra08:09
*** jcapitao has joined #openstack-infra08:12
*** ociuhandu has quit IRC08:15
*** rcernin has quit IRC08:16
*** ociuhandu has joined #openstack-infra08:22
*** ociuhandu has quit IRC08:27
*** rpittau|afk is now known as rpittau08:28
*** rcernin has joined #openstack-infra08:32
*** andrewbonney has joined #openstack-infra08:34
*** ociuhandu has joined #openstack-infra08:39
*** zbr has quit IRC08:44
*** ociuhandu has quit IRC08:45
*** zbr has joined #openstack-infra08:45
*** ociuhandu has joined #openstack-infra08:45
*** rcernin has quit IRC08:46
*** zbr has quit IRC08:47
*** zbr has joined #openstack-infra08:47
*** zbr has quit IRC08:49
*** tkajinam has quit IRC08:49
*** zbr has joined #openstack-infra08:49
*** zbr has quit IRC08:52
*** zbr has joined #openstack-infra08:52
*** jpena|off is now known as jpena08:57
*** lucasagomes has joined #openstack-infra09:02
*** tosky has joined #openstack-infra09:05
*** derekh has joined #openstack-infra09:07
*** sshnaidm is now known as sshnaidm|ruck09:34
*** xek has joined #openstack-infra09:36
*** rcernin has joined #openstack-infra09:42
*** rcernin has quit IRC09:42
*** ociuhandu has quit IRC09:49
*** carloss has joined #openstack-infra09:54
*** sshnaidm|ruck has quit IRC10:01
*** sshnaidm has joined #openstack-infra10:01
*** happyhemant has joined #openstack-infra10:05
*** ociuhandu has joined #openstack-infra10:16
*** ociuhandu has quit IRC10:16
*** gfidente has joined #openstack-infra10:21
openstackgerritMerged openstack/project-config master: Remove openstack-python and openstack-docs job for x/vmtp project.  https://review.opendev.org/c/openstack/project-config/+/76405410:22
*** ociuhandu has joined #openstack-infra10:26
*** ykarel_ has joined #openstack-infra10:27
*** ykarel_ is now known as ykarel|lunch10:28
*** ykarel has quit IRC10:29
*** hashar is now known as hasharLunch10:32
*** icey_ has joined #openstack-infra10:43
*** icey has quit IRC10:44
*** ociuhandu has quit IRC10:46
*** ociuhandu has joined #openstack-infra10:46
*** ociuhandu has quit IRC10:48
*** ociuhandu has joined #openstack-infra10:48
*** ramishra_ has joined #openstack-infra10:54
*** sshnaidm is now known as sshnaidm|afk10:55
*** ramishra has quit IRC10:57
*** ysandeep is now known as ysandeep|afk11:04
*** dtantsur|afk is now known as dtantsur11:19
*** ykarel|lunch is now known as ykarel11:30
*** ykarel_ has joined #openstack-infra11:35
*** ykarel has quit IRC11:38
*** sshnaidm|afk is now known as sshnaidm|ruck11:39
*** icey_ has quit IRC11:44
*** icey has joined #openstack-infra11:58
*** ociuhandu has quit IRC12:02
*** iurygregory has joined #openstack-infra12:03
*** jcapitao is now known as jcapitao_lunch12:06
*** rfolcOUT has joined #openstack-infra12:06
*** rfolco has joined #openstack-infra12:07
*** ociuhandu has joined #openstack-infra12:23
*** ociuhandu has quit IRC12:27
*** ociuhandu has joined #openstack-infra12:29
zbrclarkb: fungi: corvus what can we do to lower the amount of time reviews are stalling waiting for infra-cores?12:30
*** dtantsur is now known as dtantsur|brb12:31
zbrthat is particularly an issue if you are on EU timezones as I doubt user can ping anyone on irc before ~2PM GMT.12:32
*** ociuhandu has quit IRC12:33
*** jpena is now known as jpena|lunch12:36
*** vesper11 has quit IRC12:53
*** ociuhandu has joined #openstack-infra12:53
*** Goneri has joined #openstack-infra12:55
*** ociuhandu has quit IRC12:57
*** eharney has joined #openstack-infra13:01
*** hamalq has quit IRC13:01
*** jcapitao_lunch is now known as jcapitao13:03
*** hamalq has joined #openstack-infra13:05
*** ociuhandu has joined #openstack-infra13:10
*** rlandy has joined #openstack-infra13:18
*** ociuhandu has quit IRC13:22
*** ykarel_ is now known as ykarel13:30
*** ysandeep|afk is now known as ysandeep13:30
*** hasharLunch is now known as hashar13:43
*** dtantsur|brb is now known as dtantsur13:46
*** lbragstad has quit IRC13:50
*** jpena|lunch is now known as jpena13:51
*** ociuhandu has joined #openstack-infra13:53
fungizbr: ianw and frickler are usually around earlier than that13:55
*** lbragstad has joined #openstack-infra13:55
zbrfungi: i tried getting ianw on irc few times and was quite hard based on timestamps, I think he may in Asia (or working nights)13:57
*** ociuhandu has quit IRC13:58
fungiaustralia13:58
fungiand yeah we're a little thin in between with frickler on vacation at the moment13:59
fungiis there something urgent/broken? i'm just catching up on e-mail/scrollback now and about to go into a conference call meeting but can take a look shortly13:59
*** ociuhandu has joined #openstack-infra14:02
zbrsadly is an endemic issue, i do have examples but i doubt they count as urgent.14:05
zbrstill, if various changes pile up, i endup loosing interest in doing anything on repos which have stalling PRs (not counting those with requested changes)14:05
*** ociuhandu has quit IRC14:06
zbralso the timing makes it harder because i mostly have 2-4h a day when i may be able to engage on irc with a core reviewer.14:06
zbri have no idea what is the best way to addresses it, but i have the impression that it would not sort-itself out naturally14:07
*** dchen has quit IRC14:09
zbrmaybe clarkb or corvus can help with https://review.opendev.org/c/opendev/gerritlib/+/72996614:09
*** auristor has quit IRC14:10
fungizbr: given you seem to have addressed clarkb's most recent question in that (as well as his and corvus's earlier questions) i'm going ahead and approving it14:16
zbrhttps://review.opendev.org/c/opendev/gerritlib/+/754784 should be no brainer, removes platforms which we didn't even test.14:19
*** ociuhandu has joined #openstack-infra14:49
*** ociuhandu has quit IRC14:51
*** ociuhandu has joined #openstack-infra14:52
*** zxiiro has joined #openstack-infra14:53
*** xek has quit IRC14:57
*** xek has joined #openstack-infra14:58
*** ociuhandu has quit IRC14:58
*** hashar is now known as hasharAway15:05
zbrbasepython = python3 is quite dangerous entry to have in tox.ini, it confuses tox into user other interpreters even when you do "tox -e py3X"15:05
zbrthe tools warns about it, but continues to run with mismatching interpreter.15:06
zbrfungi: thanks for gerritlib merge, now i can run the tests locally on any version of python.15:09
*** auristor has joined #openstack-infra15:09
fungizbr: yes, "basepython = python3" does unexpected things for pyXY testenvs, unless you also add "ignore_basepython_conflict = True" in the global [tox] section (supposedly that will eventually become the default behavior after a transitional period)15:12
*** ociuhandu has joined #openstack-infra15:12
fungihttps://tox.readthedocs.io/en/latest/config.html#conf-ignore_basepython_conflict15:13
zbryeah, i am reading it again, but i am not sure if wisdom is what i get by reading it again, these two paragraphs.....15:15
zbri personally do not see the use of that option, as someone that very often specifies explicit python versions when I run tests.15:16
fungii agree the explanation for that option in their documentation is lacking clarity. in short it's the fix they implemented for the bug we raised about that confusing behavior15:16
zbrI do find tox behaving as expected only when both entries are missing from tox.ini files.15:17
fungito rephrase the explanation, ignore_basepython_conflict allows you to continue to get python 3.8 when you tox -e py38 even if you have basepython for your testenv set to something else like python3.715:17
fungihttps://codesearch.opendev.org/?q=ignore_basepython_conflict15:18
fungiwe've relied on it heavily in the python 2->3 transition15:18
*** ociuhandu has quit IRC15:20
zbrand the cost of breaking when someone added basepython=python3.6 on a specific environment.15:20
zbrthere are cases when someone wants to run an environment with only a particular version of python, linting could be such case.15:20
zbras it is know that some linters give different results based on what version of python you use, even if your project may support a wide range of pythons.15:21
zbri know, about =python3 as a hack during transition, added it myself to many repos.15:21
zbrbut imho, python3 was an unversioned/ubdetermined python3.15:22
*** ysandeep is now known as ysandeep|away15:23
zbri guess that a better approach is to use "py3" for those that do not care about version, and avoid using ignore_basepython_conflict and base-python.15:24
*** ociuhandu has joined #openstack-infra15:26
fungii'm not sure what you're asserting breaks15:26
fungiif you create an explicit [testenv:py38] and then set basepython = python3.7 inside that, yes i'm not sure exactly what it will do, that might still use python3.8 instead15:27
fungiwhen ignore_basepython_conflict is set true15:27
*** kmarc has joined #openstack-infra15:27
fungiit seems like an unusual corner case though, rare enough that you can probably afford other workarounds for a project which needs to do something that strange15:28
zbryeah, just dicovered this 5s ago. a lot of magic behind tox.15:28
zbrin old versions of tox using ignore_basepython_conflict was recipe for disaster (getting CI to report passed for unexpected version of python)15:29
*** dklyle has joined #openstack-infra15:29
zbrfungi: do you recommend including only "py3" in envlist or full list of supported versions?15:30
fungii thought it was widely known in openstack circles for the past couple of years. it came up when we first started trying to switch the default python away from 2.7 and we raised it as a bug at the time. they gave us ignore_basepython_conflict in tox 3.1.0 so we could have a cleaner solution than making explicit [testenv:pyXY] entries just so we could override basepython differently in each one15:30
*** ociuhandu has quit IRC15:31
fungizbr: i'm an advocate of keeping envlist limited to py3 rather than sticking py36,py37,py38,py39 in there for a few reasons: 1. most devs are unlikely to have every one of those interpreter versions installed, 2. local testing with one python version is generally good enough and having the ci system catch your very version-specific bug for you instead isn't the end of the world, 3. it avoids needing15:32
fungito remember to constantly edit the envlist line every time your supported interpreter versions change15:32
fungialso 4. it's not hard to explicitly tox -e py38 if your default python3 is 3.7 but you know you have 3.8 installed and you want to specifically test with it15:33
zbri have to agree the keeping the list maintained is a pita and because i can still mention explicit version, is ok. if i see ci to fail with specific version, I can run with that locally.15:33
zbri do happen to use pyenv and have an insane versions of pythons, but i am sure that is not the average dev experience15:34
fungimy opinion is that tox is also not the right place to declare what python versions your project supports, that's why we have package metadata15:34
zbryep, but tox declares the test matrix, and including all versions in the test matrix is usually a good idea.15:35
fungiand yeah, that's more or less what i do too (i don't use pyenv, i just make each python from the git source tree and make altinstall to a subpath of my homedir, then deep-link from ~/bin into those)15:35
zbrmaybe gabor will add a feature to get the list from setupcfg15:35
fungiwould probably want to parse both setup.cfg (that's not just a pbr thing, setuptools supports it too) and pyproject.toml (presumptive successor)15:36
zbrapparently on gerritbot stestr brings a perverse amount of deprecation warnings from subunit, which seams unmaintained.15:41
*** lpetrut has quit IRC15:41
zbrin fact i see unittest2 being installed which should never happen on py3 projects.15:41
fungimight be worth checking with mtreinish on those15:49
fungibut fair warning, you're not going to be able to get rid of every last deprecation warning on newer pythons until https://github.com/pypa/setuptools/issues/2086 is fixed in a new release of setuptools and the vendored copy in Python 3.8 and later updated with it15:50
fungialso probably not until python 3.6 is dropped entirely since it's unlikely the setuptools in it will ever be updated to a version which calls importlib instead of imp15:51
fungior, alternatively, getting rid of setuptools entirely i guess (that's been on the pbr to do list for a while)15:51
fungibut yeah, at the moment even the latest versions of setuptools still call lib2to3 so that's going to raise deprecation warnings until it's addressed15:53
*** slaweq has quit IRC15:54
clarkbzbr: I'm not fully caught up on scrollback but helping us enables us to help you. I'm not sure if you've noticed but the last couple of months have been incredibly busy for infra root for a number of reasons15:54
clarkbI don't have time to do reviews on most things right now15:55
zbrsadly, the user-lookup in gerrit seams unusable, like 10s+ to return values.15:55
clarkbalso the constant complaining is really making it hard for me to want to bother15:55
clarkbbecause it feels like the end result of all this work is that everyone is just unhappy and unwilling to help15:56
fungizbr: what "user lookup"? the rest api? it's returning quickly for me15:56
*** slaweq has joined #openstack-infra15:56
fungialso system load on the server doesn't seem to be as bad today: http://cacti.openstack.org/cacti/graph.php?action=view&local_graph_id=26&rra_id=all15:56
zbrlookup is usually the term used for UI elements that perform server side searches, when you try to add someone to a review.15:56
fungistill not great, but maybe the fix to where we disabled autogc in the correct file had some positive impact15:57
zbrthere performance seams to vary a lot from moment to moment, sometimes is <1s, sometimes nothing.15:57
fungiyeah, the server is still struggling under heavy load at peak utilization since the upgrade. we're trying lots of options to get it under control15:57
zbri think that we need to assure that user lists are always in cache as this is very common activity: to add reviewers.15:58
fungizbr: i appreciate your desire to state the obvious, we've already tuned the accounts cache to be as large as gerrit seems to want to use15:58
zbron the other hand, I have the impression that the auto-completer is smarter15:58
*** ociuhandu has joined #openstack-infra15:59
fungicurrently, the accounts cache has a 99% hit ratio in memory and 100% hit ratio on disk (it's a disk-backed cache for that one)16:00
zbrmaybe is something else, like reaching http server connection limits?16:01
fungiwell, we've been keeping tabs on the apache mod_status scoreboard too16:04
zbri wonder if there is a browser plugin which can be used to report average response time, having few users reporting it could make use identify bottlenecks much easier than on irc.16:05
fungiit's fairly idle at the moment, most workers are either in waiting for connection or open slot with no current process16:05
zbrlong time ago i used new relic for something like that.16:05
clarkbI don't think we need more people reporting issues at thsi point, we have the logs and metrics we've been looking at and have been picking off one thing at a time16:05
clarkbif we exhaust our abilities doing ^ then we can start looking at other tools16:06
clarkband so far it seems the work we have done has improved things16:06
fungiand yeah, next on the list is switching from java 8 to 11, which is supposed to help performance as well16:09
fungithen it's probably time to start looking at updating to gerrit 3.3 which also supposedly has some performance improvements16:10
*** redrobot has quit IRC16:11
clarkbya, though at least one person had trouble upgraded on the mailing list yesterday (I helped them by pointing out the manual downgrade steps). I expect we'll want to do a fair bit of testing for that one (not 3.2 levels but enough to be happy with it first)16:11
clarkbin theory it is a very easy upgrade though, only one schema update and no index updates16:12
zbrwhile the attention-set seams like a good replacement for assignee, i doubt we want to jump so soon on 3.3, lets other pay the cost of being an early adopter.16:12
zbrbut java 11, seams like best next approach, we cannot escape it anyway.16:13
fungiwell, the difference between 3.2 and 3.3 isn't substantial, and if it fixes some of our performance issues it might be worth doing sooner so long as some cursory testing doesn't identify problems16:13
fungithey've supposedly also started supporting java 15 with gerrit 3.3, but that does seem like a risky jump given the bugs they've found16:14
clarkbfungi: jgit had problems i don't know if they fixed them yet on 1516:15
fungiyeah, it's stuff like that which makes me squeamish about moving to openjdk 15 just yet16:16
fungithey apparently realized they were missing testing for it until very recently too16:16
clarkbluca reports running 3.2 on java 11 since day one at gerrithub so fairly confident in that update16:16
mtreinishfungi: unittest2 is still a dep for released testtools. It was a rolling backport from stdlib unittest but stopped backporting things around. It's still needed for python 3.4 testtools support, which the released testtools still supports16:20
fungizbr: ^ maybe that helps you16:20
fungithanks mtreinish!16:21
mtreinishthe next release of testtools should drop that requirement, I just need another maintainer to review: https://github.com/testing-cabal/testtools/pull/27716:21
clarkbmtreinish: o/ ohai its been a long time16:22
clarkbmtreinish: still making computers do crazy things at really cold tempuratures?16:22
zbrmtreinish: nice to see you here! any chance for a refresh on stestr deps to bring them more towards py36-py39 range?16:22
zbrwith the risk of upsetting some around here, i am more of pytest user.16:23
fungisounds like the testtools update needs to happen first16:23
fungisince stestr depends on it16:23
clarkbzbr: and as we're happy to point out the use of stestr which sticks to standards means you can use pytest if you choose to16:23
mtreinishclarkb: hey, yeah still doing the quantum computing stuff. It's been fun so far16:23
clarkbzbr: but if we use pytest then alternatives are unlikely to work due to its lack of adhering to standards16:24
mtreinishzbr: yeah what fungi said stestr depends on testtools for it's realtime results streaming. I've removed most of the dependency on testtools from stestr at this point, but that piece is still critical16:24
zbri am aware of risks, while is possible to use pytest with pure unittest tests, its real power comes when you diverge from the standards.16:25
fungisure, but diverging from standards also carries plenty of cost16:26
zbrwhat can we do about testools? it does not seam to actively maintained.16:27
zbrmy impression is that the CI is broken and I open PRs to drop unittest2 1.5 years old.16:28
mtreinishit's not super active, I try my best to keep on top of it. But I have been busier with work projects than I was expecting when I agreed to be added as a maintainer16:28
zbrshould we just fork it, fix what we care about and release that fork?16:29
mtreinishif I get sufficient reviews on #277 and once that merges I can prepare a new testtools release16:29
mtreinishbut also instead of forking it, why not get some people to volunteer to work on it. I can discuss adding maintainers in the core group. I don't think there would be much opposition16:30
fungiyeah, if there are enough people to maintain a fork, then they could potentially be volunteers to just help maintain the original instead?16:31
zbrmtreinish: i already have a very long list of projects i nurture, so I can only help with packaging and fixes like these, not real development.16:31
zbrlike fixing broken CI, fixing dependency conflict16:32
* zbr hates forking, is last resort action.16:33
*** lmiccini has quit IRC16:35
zbrmtreinish: my github id is ssbarnea, happy to help addressing these deprecations (hopefully we do not endup having to fix 50 other dependencies),16:35
mtreinishwell is there anything big besides the unittest2 thing. I think that was the only big deprecation/compat issue with modern python versions16:57
*** Guest18921 has joined #openstack-infra16:58
*** gyee has joined #openstack-infra16:58
*** Guest18921 is now known as redrobot17:01
*** ykarel is now known as ykarel|away17:04
*** rpittau is now known as rpittau|afk17:04
*** ykarel|away has quit IRC17:09
*** ykarel|away has joined #openstack-infra17:17
*** gbutnaru has joined #openstack-infra17:19
*** ykarel|away has quit IRC17:22
*** ociuhandu has quit IRC17:23
*** lucasagomes has quit IRC17:25
*** ociuhandu has joined #openstack-infra17:28
*** ociuhandu has quit IRC17:28
mtreinishfungi, clarkb: this looks like a pbr issue: https://github.com/testing-cabal/testtools/pull/281/checks?check_run_id=1487744938#step:6:11117:29
mtreinishit's running 'pip install .[test]' in the ci job and it looks like pip can't find the version correctly with the setuptools extra17:29
mtreinishand the new pip depsolver isn't happy with that17:30
fungioh, right, i'm always confused by github's requirements to sign into my account there before i can look at public ci logs17:30
fungi ERROR: Cannot install testtools and testtools[test]==0.0.0 because these package versions have conflicting dependencies.17:31
fungithat?17:31
fungilooks almost certainly related to this week's pip release which enables the new dep solver17:32
fungii'm not sure it's a pbr-specific problem, looks more like whatever test harness is trying to install the project into the venv17:33
fungimtreinish: i'm not super familiar with github workflows, but i think this is the problem: https://github.com/testing-cabal/testtools/blob/master/.github/workflows/test.yml#L4517:36
fungii think new pip won't allow you to install both testtools and testtools[extras]17:37
fungithough i can't quite tell where testtools by itself is getting installed17:38
mtreinishI don't think it installs testtools by itself17:38
*** artom has quit IRC17:38
mtreinishthe only line that is installing testtools is l45 there17:38
mtreinishthe weirdness comes in with the extra, because pretty much everything in there depends on testtools: https://github.com/testing-cabal/testtools/blob/master/setup.cfg#L2717:39
fungioh, that's what it is, i bet17:39
fungiso yeah it wants to install testtools as a dependency of the things in testtools[extra]17:40
fungiresulting in a conflicting circular dependency17:40
fungii guess the ==0.0.0 there is the real problem then? the version metadata from the git repo isn't being applied?17:41
mtreinishyeah, that's what I was thinking17:42
fungii'll experiment and see if i can reproduce in a straightforward way17:42
*** eolivare has quit IRC17:44
*** sshnaidm|ruck is now known as sshnaidm|afk17:47
fungiit's not as simple as just installing the master branch tip's [test] extra into a venv17:49
fungiSuccessfully installed argparse-1.4.0 extras-1.0.0 fixtures-3.0.0 linecache2-1.0.0 pbr-5.5.1 python-mimeparse-1.6.0 testresources-2.0.1 testscenarios-0.5.0 testtools-2.4.1.dev24 traceback2-1.4.0 unittest2-1.1.017:54
*** jcapitao has quit IRC17:54
fungiso at least in my local testing pbr seems to be supplying a version number based on the state of the git repo17:54
mtreinishoh, I wonder if it's a shallow clone issue. I think by default gha does a shallow clone of the checkout17:55
mtreinishso I bet the tags aren't there17:55
fungithat's what i'm starting to suspect17:55
fungiit's acting like there's no git for pbr to reference17:55
fungii'm seeing if blowing away .git gives me similar behavior17:56
fungiokay, not quite... the error condition is definitely different when pbr has no .git17:58
fungii'll test the limited clone theory17:58
fungiso if i clone with --no-tags i get the same error18:00
fungimtreinish: and if i git pull --tags then it works18:01
fungiso my guess would be github actions is setting up the clone with --no-tags or equivalent18:01
*** jpena is now known as jpena|off18:02
fungior git fetch --tags is probably safer for this case18:02
fungidefinitely lmk if that doesn't make it go and i can keep digging?18:03
mtreinishthanks18:06
mtreinishyeah I'll push a PR to update the job definition, there is an option to just do a full clone (I've had to do that in other jobs before that need the full history, like with reno)18:06
*** lpetrut has joined #openstack-infra18:09
fungioh, good point, a shallow clone won't have the objects for the tags to correspond to, so yeah you might need at least the full history of that branch18:11
*** derekh has quit IRC18:14
*** hasharAway is now known as hashar18:15
zbrthe issue is not pbr specific, i got the same issue with setuptools-scm when lacking full clone.18:16
zbrbut it could prove as a good idea to attempt to go a git pull tags from inside pbr before failing.18:16
*** andrewbonney has quit IRC18:19
fungiwell, that may not help if the clone is shallow as mtreinish suggests, in which case you really do need to clone differently18:20
mtreinishwell it was an issue with reno, but the full history matters more there. Just having the tag metadata might be enough I haven't tried it18:24
zbrif so is right, it may be possible https://stackoverflow.com/questions/6802145/how-to-convert-a-git-shallow-clone-to-a-full-clone18:24
zbrimho only tags matter for, but it may be interesting to make some tests, maybe we can avoid the 0.0.0 fallback for some users.18:25
fungioh, neat, i didn't realize you could adjust the depth when fetching18:25
fungiand missed that --unshallow became a fetch option too18:26
zbrsadly I did not see get me last 2 tags.18:26
*** gfidente is now known as gfidente|afk18:40
*** dtantsur is now known as dtantsur|afk18:47
*** vishalmanchanda has quit IRC18:58
*** ramishra_ has quit IRC19:00
*** artom has joined #openstack-infra19:15
*** iurygregory has quit IRC19:29
*** dhill has quit IRC20:02
*** dhill has joined #openstack-infra20:07
*** vesper11 has joined #openstack-infra20:15
*** vesper has joined #openstack-infra20:19
*** vesper11 has quit IRC20:19
*** hashar has quit IRC20:23
*** lpetrut has quit IRC20:29
*** dhill has quit IRC20:53
*** vesper has quit IRC21:06
*** raissa has joined #openstack-infra21:15
*** dhill has joined #openstack-infra21:18
*** rfolco has quit IRC21:20
*** iurygregory has joined #openstack-infra21:28
*** vesper11 has joined #openstack-infra21:30
*** sboyron has quit IRC21:43
*** raissa has quit IRC21:45
*** gbutnaru has quit IRC22:06
*** matt_kosut has quit IRC22:27
*** matt_kosut has joined #openstack-infra22:28
*** matt_kosut has quit IRC22:33
*** rcernin has joined #openstack-infra22:34
*** ajitha has quit IRC22:35
*** tkajinam has joined #openstack-infra23:00
*** slaweq has quit IRC23:02
*** rlandy has quit IRC23:23
*** dchen has joined #openstack-infra23:37
*** Goneri has quit IRC23:50
*** happyhemant has quit IRC23:54

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!