Subject: Re: [boost] [Range] Proposal: a sub-maintainer of Boost.Range
From: Vicente J. Botet Escriba (vicente.botet_at_[hidden])
Date: 2012-12-19 05:38:50
Le 19/12/12 10:17, Nathan Ridge a écrit :
>> However, if I were you, I would wait until some of the test bots cycled, to make sure that nothing is broken - then merge to release.
> I assume I'm supposed to be looking here  and here . I have a
> few questions about what I'm seeing:
> 1. At , I see a number of yellow "fail" boxes. The legend describes
> this as "failure on a newly added test/compiler". Should I be worried
> about these?
Yes. It is up to the maintainer to update the
status/expected_results.xml file to indicate that this is a test running
correctly, so that a regression is seen red instead of yellow.
Unfortunately I don't think a lot of maintainers know that an even those
that know (as me) don't maintain this file.
> 2. At , I see that Boost.Range has "issues": the 'type_erased' test
> is failing (in yellow colour) on a number of testers. Looking back
> at , I see those yellow boxes under 'type_erased' and the
> corresponding testers, but I also see yellow boxes under other tests,
> which do not show up as issues in . What makes 'type_erased'
> special that its failure causes an "issue", but not the failure of
> other tests?
I think this is a summary for some compilers, but I don't know which
ones and why not all the testers are considered.
> 3. Is there a way to look at older test results, so that I can compare
> test results from before my commit to test results from after my
> commit, so that I can see whether my commit specifically broke
No that I know. You can try to see if testers that did a run before your
commit are working or not.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk