<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:04:22 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>[INTTEST-25] Variety of python erorrs while building docs after adding integration/test submodule to docs repo</title>
                <link>https://jira.opendaylight.org/browse/INTTEST-25</link>
                <project id="10189" key="INTTEST">integration-test</project>
                    <description>&lt;p&gt;When building I get errors like:&lt;/p&gt;

&lt;p&gt;&amp;gt; Importing test library &apos;/Users/ckd/git-reps/docs/docs/submodules/integration/test/csit/libraries/riotdm.py&apos; failed: ImportError: No module named requests&lt;/p&gt;

&lt;p&gt;And many others like:&lt;br/&gt;
&amp;gt; sed: 1: &quot;SxpLib.robot.html&quot;: invalid command code S&lt;br/&gt;
&amp;gt; sed: 1: &quot;Tcpdump.robot.html&quot;: invalid command code T&lt;/p&gt;

&lt;p&gt;Talking to Thanh in IRC, it sounds like these are currently expected with how the buildchain to produce robot docs interacts with being run from a VM that doesn&apos;t have the full CSIT suite installed, but are harmless.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="19361">INTTEST-25</key>
            <summary>Variety of python erorrs while building docs after adding integration/test submodule to docs repo</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                                <status id="5" iconUrl="https://jira.opendaylight.org/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10000">Done</resolution>
                                        <assignee username="zxiiro">Thanh Ha (zxiiro)</assignee>
                                    <reporter username="colindixon">Colin Dixon</reporter>
                        <labels>
                    </labels>
                <created>Tue, 5 Jul 2016 18:51:06 +0000</created>
                <updated>Thu, 19 Oct 2017 17:51:40 +0000</updated>
                            <resolved>Fri, 8 Jul 2016 18:56:00 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="35051" author="colin@colindixon.com" created="Tue, 5 Jul 2016 18:52:10 +0000"  >&lt;p&gt;If these are going to be present, we should at least document it. If they can be hidden, it would help to make the docs build output more readable, but of course has risks of hiding real errors.&lt;/p&gt;</comment>
                            <comment id="35052" author="zxiiro" created="Tue, 5 Jul 2016 18:54:45 +0000"  >&lt;p&gt;I&apos;ll take this as an action item. Hiding the errors is low risk because we&apos;d only be hiding it for the libdoc that&apos;s used to generate the robot details and that specific error is expected. The rest of the doc build should still report proper errors.&lt;/p&gt;</comment>
                            <comment id="35053" author="zxiiro" created="Tue, 5 Jul 2016 21:00:15 +0000"  >&lt;p&gt;Proposed patch: &lt;a href=&quot;https://git.opendaylight.org/gerrit/41353&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/41353&lt;/a&gt;&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|i01ln3:</customfieldvalue>

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