<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:37:37 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>OpenDaylight JIRA</title>
    <link>https://jira.opendaylight.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.20.10</version>
        <build-number>820010</build-number>
        <build-date>22-06-2022</build-date>
    </build-info>


<item>
            <title>[RELENG-149] tox/pre-commit failing in integration-test-tox-verify-master: failing to checkout robot-tidy repo master branch</title>
                <link>https://jira.opendaylight.org/browse/RELENG-149</link>
                <project id="10164" key="RELENG">releng</project>
                    <description>&lt;p&gt;Not sure the root cause yet, but some things I noticed.&lt;/p&gt;

&lt;p&gt;the high level problem is saying that we can&apos;t check out &apos;master&apos; branch of&lt;br/&gt;
the robot-tidy hook:&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
[INFO] Initializing environment &lt;span class=&quot;code-keyword&quot;&gt;for&lt;/span&gt; https:&lt;span class=&quot;code-comment&quot;&gt;//github.com/guykisel/pre-commit-robotframework-tidy.
&lt;/span&gt;An unexpected error has occurred: CalledProcessError: command: (&lt;span class=&quot;code-quote&quot;&gt;&apos;/usr/bin/git&apos;&lt;/span&gt;, &lt;span class=&quot;code-quote&quot;&gt;&apos;checkout&apos;&lt;/span&gt;, &lt;span class=&quot;code-quote&quot;&gt;&apos;master&apos;&lt;/span&gt;)
&lt;span class=&quot;code-keyword&quot;&gt;return&lt;/span&gt; code: 1
expected &lt;span class=&quot;code-keyword&quot;&gt;return&lt;/span&gt; code: 0
stdout: (none)
stderr:
    error: pathspec &lt;span class=&quot;code-quote&quot;&gt;&apos;master&apos;&lt;/span&gt; did not match any file(s) known to git.
    
Check the log at /home/jenkins/.cache/pre-commit/pre-commit.log
ERROR: InvocationError &lt;span class=&quot;code-keyword&quot;&gt;for&lt;/span&gt; command /w/workspace/integration-test-tox-verify-master/.tox/pre-commit/bin/pre-commit run --all-files (exited with code 1)
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;

&lt;p&gt;pre-commit is installing importlib-resources which recently released 2.0.0 and that&lt;br/&gt;
is showing up as incompatible with the virtualenv==20.0.21 that is also installed&lt;br/&gt;
with pre-commit.&lt;/p&gt;

&lt;p&gt;lftools has us locked to pre-commit==2.2.0, although a new release of that (2.5.0)&lt;br/&gt;
also came out this week.&lt;/p&gt;

&lt;p&gt;I cannot reproduce this locally, so trying to figure out slowly in the sandbox.&lt;/p&gt;</description>
                <environment></environment>
        <key id="32749">RELENG-149</key>
            <summary>tox/pre-commit failing in integration-test-tox-verify-master: failing to checkout robot-tidy repo master branch</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="5" iconUrl="https://jira.opendaylight.org/images/icons/priorities/trivial.svg">Lowest</priority>
                        <status id="6" iconUrl="https://jira.opendaylight.org/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10000">Done</resolution>
                                        <assignee username="zxiiro">Thanh Ha (zxiiro)</assignee>
                                    <reporter username="jluhrsen">Jamo Luhrsen</reporter>
                        <labels>
                    </labels>
                <created>Wed, 10 Jun 2020 04:22:05 +0000</created>
                <updated>Tue, 11 Aug 2020 18:42:50 +0000</updated>
                            <resolved>Tue, 11 Aug 2020 18:42:50 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                                                                                <comments>
                            <comment id="68193" author="jluhrsen" created="Wed, 10 Jun 2020 04:48:05 +0000"  >&lt;p&gt;We can merge &lt;a href=&quot;https://git.opendaylight.org/gerrit/c/integration/test/+/90364&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/c/integration/test/+/90364&lt;/a&gt; to get unblocked, but that is removing our&lt;br/&gt;
robot-tidy check which is really helpful to keep our code style reasonable.&lt;/p&gt;</comment>
                            <comment id="68207" author="zxiiro" created="Thu, 11 Jun 2020 14:09:43 +0000"  >&lt;p&gt;Resolved with &lt;a href=&quot;https://git.opendaylight.org/gerrit/c/integration/test/+/90393&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/c/integration/test/+/90393&lt;/a&gt;. Not sure why &apos;master&apos; keeps failing but workaround this by pinning a specific hash id instead. Very strange... It&apos;s like the upstream repo is broken somehow when cloned via pre-commit.&lt;/p&gt;</comment>
                            <comment id="68208" author="jluhrsen" created="Thu, 11 Jun 2020 19:57:42 +0000"  >&lt;p&gt;ok, workaround is merged. I re-opened this, assigned to me and marked it with lowest priority. At some point in the future&lt;br/&gt;
I&apos;ll likely come across this open ticket again and I can try to change the robot-tidy-pre-commit repo back to master to see&lt;br/&gt;
if it works. this is a very weird issue. weird that it just started happening too.&lt;/p&gt;</comment>
                            <comment id="68209" author="jluhrsen" created="Thu, 11 Jun 2020 23:09:56 +0000"  >&lt;p&gt;Something has changed somewhere in our environment that is breaking pre-commit when it tries to &apos;git checkout master&apos; on some&lt;br/&gt;
repos. The exact problem for that is not known, but we are using a 7+ year old version of git on these build VMs. If we upgrade to&lt;br/&gt;
version XXX, the problem is fixed. here is a log of the job working. you can see some steps in there to upgrade git, although I guess&lt;br/&gt;
the proper fix is to get this upgraded and baked in to the build VM to start with.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/builder-copy-sandbox-logs/783/console-timestamp.log.gz&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/builder-copy-sandbox-logs/783/console-timestamp.log.gz&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="68210" author="jluhrsen" created="Thu, 11 Jun 2020 23:10:43 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.opendaylight.org/secure/ViewProfile.jspa?name=abelur&quot; class=&quot;user-hover&quot; rel=&quot;abelur&quot;&gt;abelur&lt;/a&gt; do you know how we can get git upgraded in our centos7 build systems that run these tox verify jobs?&lt;/p&gt;</comment>
                            <comment id="68211" author="zxiiro" created="Fri, 12 Jun 2020 00:44:52 +0000"  >&lt;p&gt;Proposed a fix in common-packer &lt;a href=&quot;https://gerrit.linuxfoundation.org/infra/c/releng/common-packer/+/64261&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://gerrit.linuxfoundation.org/infra/c/releng/common-packer/+/64261&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;It appears LF scripts were trying to get an up to date Git however failed to install due to package name change in IUS repo.&lt;/p&gt;</comment>
                            <comment id="68532" author="zxiiro" created="Tue, 11 Aug 2020 18:42:50 +0000"  >&lt;p&gt;This is fixed at this point.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                            <customfield id="customfield_11400" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i03sz3:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>