Re: [tracecompass-dev] Use specific commit for test CTF traces?

[Matthew Khouzam <matthew.khouzam@xxxxxxxxxxxx>]

I think ideally we would pull master, but that the ctf testsuite git
should have a staging branch. the staging branch would be timeboxed,
like say 1 week. You put a test there we have one week to make the
parser work for master or ignore the test. We could have a separate job
just for staging and that would be IMO the best of both worlds.

On 15-05-08 08:38 AM, Bernd Hufmann wrote:
> Hello
>
> could we have a special Jenkins Job that runs in the night and just
> verifies the ctf-testsuite's master branch? If there are new traces
> added and it fails then we would know right away. Nobody would need to
> check it manually.
>
> For Trace Compass master and stable branches, however, we would build
> from a specific commit so that we don't get these surprise test
> failures when submitting patches to Gerrit or nightly build.
>
> It should not be hard to setup such a Jenkins job. First master branch
> is checked out then we could apply a patch before running the build.
>
> /Bernd
>
> On 05/08/2015 12:09 AM, Alexandre Montplaisir wrote:
>> Hi Marc-André,
>>
>> I was thinking about the same thing, after today's breakage ;)
>>
>> The advantage of always pulling the ctf-testsuite's master branch is
>> that we don't have to think about it, new tests come in and we get
>> notified right away if we are non-conforming. Making this process
>> manual would add more burden to the maintainers.
>>
>> But having the possibility to point to a specific commit could be
>> useful. I would still leave master pointing to ctf-testsuite's HEAD,
>> but in stable branches we could point to a specific commit instead.
>> That way those won't break unexpectedly, and as you mention, it
>> guarantees that the branch keeps working in the future.
>>
>> Thoughts?
>>
>> Cheers,
>> Alex
>>
>>
>> On 2015-05-07 10:47 PM, Marc-André Laperle wrote:
>>> Hi,
>>>
>>> I'm wondering if we should use a specific commit when pulling the
>>> ctf-testsuite when running the tests. I think it would be good
>>> because it would let older Trace Compass commits still execute tests
>>> properly and would also reduce the risk of "bad surprises",
>>> especially around release ;) We can periodically update that commit,
>>> whenever we have time to tackle more CTF improvements.
>>>
>>> Let me know what you think,
>>> Marc-Andre
>>>
>>>
>>
>> _______________________________________________
>> tracecompass-dev mailing list
>> tracecompass-dev@xxxxxxxxxxx
>> To change your delivery options, retrieve your password, or
>> unsubscribe from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/tracecompass-dev
>
>
> _______________________________________________
> tracecompass-dev mailing list
> tracecompass-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or
> unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/tracecompass-dev