Hi Bill, On Wed, Jun 9, 2010 at 10:29 AM, Bill Hart <[email protected]> wrote:
<SNIP> > It's better to talk about specific examples. Which ones do you think > we should give a red and why? Remember this matrix is supposed to > indicate which kinds of arch/OS combinations a user should expect MPIR > to work out of the box on (assuming their compiler works and their > machine is set up correctly). In light of this, here is how I would color each cell in the test matrix. * FreeBSD, k8: build: yes; check: pass; tune: yes; test suite failed with FAIL. Therefore, green. * Linux, Itanium (iras): build: yes; check: pass; tune: yes; test suite failed with FAIL. Therefore, green. * Linux, ultrasparc2 (gcc54): build: yes; check: pass; tune: yes; test suite failed with FAIL. Therefore, green. * Solaris, core2 (fulvia): build: yes. Therefore, green. You have to excuse my misunderstanding here, but let me try to define how colouring for cells in the test matrix works: * white -- system unavailable for testing. * green -- at least these commands run successfully: ./configure && make * orange -- some issue with this command: make tune * red -- ./configure fails; or if it succeeds and make fails. I have edited the test matrix according to the above rules for colour coding. -- Regards Minh Van Nguyen -- You received this message because you are subscribed to the Google Groups "mpir-devel" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/mpir-devel?hl=en.
