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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

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

From: Marc-André Laperle <marc-andre.laperle@xxxxxxxxxxxx>
Date: Fri, 8 May 2015 02:47:54 +0000
Accept-language: en-US
Delivered-to: tracecompass-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/tracecompass-dev>
List-help: <mailto:tracecompass-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/tracecompass-dev>, <mailto:tracecompass-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/tracecompass-dev>, <mailto:tracecompass-dev-request@eclipse.org?subject=unsubscribe>
Thread-index: AdCJOVnUo7TBLXlPTzGj0/G8ASTDZg==
Thread-topic: Use specific commit for test CTF traces?

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

Follow-Ups:
- Re: [tracecompass-dev] Use specific commit for test CTF traces?
  - From: Alexandre Montplaisir

Prev by Date: Re: [tracecompass-dev] Trace Compass now requires Eclipse 4.5
Next by Date: Re: [tracecompass-dev] Use specific commit for test CTF traces?
Previous by thread: [tracecompass-dev] Trace Compass now requires Eclipse 4.5
Next by thread: Re: [tracecompass-dev] Use specific commit for test CTF traces?
Index(es):
- Date
- Thread

Breadcrumbs