[automated-testing] Build failed without running the test

[Jonathan Holloway]

On Thu, Aug 9, 2018 at 10:15 AM Yaniv Kaul <ykaul at redhat.com> wrote:

>
>
> On Thu, Aug 9, 2018 at 6:12 PM, Jonathan Holloway <jholloway at redhat.com>
> wrote:
>
>> I'm not sure what commit at the Glusto level has to do with the issue at
>> hand, but as an update...
>> I opened a ticket on the Glusto github to research the issue caused by
>> pytest 3.3.0 dropping support for earlier versions of Python.
>> There are multiple solutions, and the pytest community is also working a
>> ticket on the same issue.
>>
>> Requiring gcc as part of the Glusto install is not a viable option, and
>> in the meantime the options I am currently exploring are:
>>
>
> Pulling in gcc as a stopgap sounds reasonable to me.
> glusto is not meant to be run (yet?) on production. On dev/qe systems
> there's nothing wrong with installing gcc.
>

Glusto is meant to be run in any environment, but production standards will
vary from shop to shop.
I'm trying to maintain that spirit of product and environment independence
to avoid breaking it elsewhere.
That's where I was coming from with gcc as a requirement not being viable
at the Glusto layer.


>
>> - Changing the pytest install_requirement in setup.py to pytest<3.3.0
>> (not a complete fix on systems with 3.3+ already installed).
>> - Rolling a container with the earlier combination of python and pytest.
>> - Porting to Python3 (in progress).
>>
>>
> That would be great!
> Y.
>
>
>> Let me know if you have any feedback. I'll be happy to discuss the issue.
>>
>> Cheers,
>> Jonathan
>>
>>
>>
>> On Tue, Jul 31, 2018 at 11:33 PM Nigel Babu <nigelb at redhat.com> wrote:
>>
>>> Given only Jonathan has commit access to glusto, I've gone ahead and
>>> modified the playbook to install gcc. Please retry your tests.
>>>
>>> On Wed, Aug 1, 2018 at 9:54 AM Nigel Babu <nigelb at redhat.com> wrote:
>>>
>>>> Looks like we're pulling in a newer version of pytest that now depends
>>>> on scandir. We'll need to pin glusto to a specific version of pytest or
>>>> install GCC on the build servers so that scandir can be installed.
>>>>
>>>> On Tue, Jul 31, 2018 at 10:50 PM Vignesh <sselvan at redhat.com> wrote:
>>>>
>>>>> +1
>>>>> It's failing for me too.
>>>>>
>>>>> Regards
>>>>> Vignesh
>>>>>
>>>>> On Tue, Jul 31, 2018 at 7:08 PM, Vitalii Koriakov <vkoriako at redhat.com
>>>>> > wrote:
>>>>>
>>>>>> Hello all.
>>>>>> It seems jenkins is broken.
>>>>>> It fails without running test
>>>>>>
>>>>>> https://ci.centos.org/job/gluster_glusto-patch-check/850/console
>>>>>>
>>>>>> Could smbd help?
>>>>>>
>>>>>> Regards,
>>>>>> Vitalii Koriakov
>>>>>> _______________________________________________
>>>>>> automated-testing mailing list
>>>>>> automated-testing at gluster.org
>>>>>> https://lists.gluster.org/mailman/listinfo/automated-testing
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Regards,
>>>>>
>>>>> SRi VIGNESH SELVAN
>>>>>
>>>>> ASSOCIATE QUALITY ENGINEER
>>>>>
>>>>> Red Hat
>>>>>
>>>>> <https://www.redhat.com/>
>>>>>
>>>>> T: +91-804612865
>>>>> <https://red.ht/sig>
>>>>> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
>>>>>
>>>>> _______________________________________________
>>>>> automated-testing mailing list
>>>>> automated-testing at gluster.org
>>>>> https://lists.gluster.org/mailman/listinfo/automated-testing
>>>>>
>>>>
>>>>
>>>> --
>>>> nigelb
>>>>
>>>
>>>
>>> --
>>> nigelb
>>> _______________________________________________
>>> automated-testing mailing list
>>> automated-testing at gluster.org
>>> https://lists.gluster.org/mailman/listinfo/automated-testing
>>>
>>
>> _______________________________________________
>> automated-testing mailing list
>> automated-testing at gluster.org
>> https://lists.gluster.org/mailman/listinfo/automated-testing
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gluster.org/pipermail/automated-testing/attachments/20180809/b8fce665/attachment-0001.html>