Thanks Isuru. If you see any issues again, I'd like to dig into it. Could 
have been transient, or could be a browser-specific problem we need to 
address.

Also, I'm interested to know more about the complexity of our YAML syntax. 
(I don't disagree, I'm mainly curious what specifically you tripped over.)

On Wednesday, January 30, 2019 at 10:17:15 AM UTC-5, Isuru Fernando wrote:
>
> The azure build log link didn't work for me when Aaron sent it 2 days ago 
> and now it opens at the correct line just fine.
>
> Isuru
>
> On Wed, Jan 30, 2019 at 7:34 AM Matt Cooper <vtbas...@gmail.com 
> <javascript:>> wrote:
>
>> (Azure Pipelines PM chiming in.)
>>
>> Aaron, can you send me a screenshot what you see when you click that log 
>> link? For me it opens directly to the line, as it's intended to do. I'm 
>> using Firefox, and most of the team uses Chrome - it's possible we have a 
>> bug though.
>>
>> With no additional clicks, here's what I see:
>>
>> On Tuesday, January 29, 2019 at 1:59:25 PM UTC-5, Aaron Meurer wrote:
>>>
>>> The question is if its worth it, given the other issues Azure has. 
>>> Keep in mind that we have to maintain whatever we set up. 
>>>
>>> For benchmarks, I don't know if any public CI is appropriate. You 
>>> really need a dedicated machine so you can get consistent runtimes. 
>>> Code quality tests are done as part of the test suite already 
>>> (test_code_quality.py). 
>>>
>>> I'm not opposed to the idea of using some other CI for other tests. I 
>>> think it should be driven by a real need, though, not just saying we 
>>> should use the resource because it is there. There are other options 
>>> too, such as CircleCI and AppVeyor. 
>>>
>>> Aaron Meurer 
>>>
>>> On Tue, Jan 29, 2019 at 3:09 AM S.Y. Lee <syle...@gmail.com> wrote: 
>>> > 
>>> > There had been some issues with azure pipelines with conda environment 
>>> setups, and I would also agree that some features are not better than 
>>> travis. 
>>> > 
>>> > However, I have a question that, if they are offering free resources 
>>> for open source projects, 
>>> > we may allocate some of the tests to azure, which can either reduce 
>>> overall build time, 
>>> > or making some space for running benchmarks or code quality tests. 
>>> > 
>>> > Would there be any reason making this idea naive? 
>>> > 
>>> > -- 
>>> > You received this message because you are subscribed to the Google 
>>> Groups "sympy" group. 
>>> > To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to sympy+un...@googlegroups.com. 
>>> > To post to this group, send email to sy...@googlegroups.com. 
>>> > Visit this group at https://groups.google.com/group/sympy. 
>>> > To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/sympy/3bd7d189-b67e-457f-ac3b-994d3c5deda0%40googlegroups.com.
>>>  
>>>
>>> > For more options, visit https://groups.google.com/d/optout. 
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "sympy" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to sympy+un...@googlegroups.com <javascript:>.
>> To post to this group, send email to sy...@googlegroups.com <javascript:>
>> .
>> Visit this group at https://groups.google.com/group/sympy.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sympy/702492e8-8233-417a-aeba-a9cde5aeb668%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/sympy/702492e8-8233-417a-aeba-a9cde5aeb668%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sympy" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sympy+unsubscr...@googlegroups.com.
To post to this group, send email to sympy@googlegroups.com.
Visit this group at https://groups.google.com/group/sympy.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sympy/7b98fac0-f9c8-413d-9885-c3eb33aafc25%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to