public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Martin Jambor <mjambor@suse.cz>
To: Siddhartha Sen <siddhartha99.sen@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: [GSOC] variations in testsuite results
Date: Wed, 28 Nov 2018 17:47:00 -0000	[thread overview]
Message-ID: <ri6k1kxktrh.fsf@suse.cz> (raw)
In-Reply-To: <CA+iicpGQHmmeSWYV=9AobnHTL13Urr0Jx2fUzj-DQRYkHvg7WQ@mail.gmail.com>

Hi Siddhartha,

On Tue, Nov 27 2018, Siddhartha Sen wrote:
> I am Siddhartha Sen,currently pursuing my B.Tech degree in Information
> Science and Engineering,2nd year. I have taken a keen interest in your
> projects and have some ideas of my own as well. I am really interested in
> working with you in G-SOC 2019.

We are delighted.

> I am proficient in C and C++ and am eager
> to work on brushing my skills in whichever field required. I have already
> checked out the GCC trunk source-code and am being able to build GCC from
> it.I have run the testsuite and saved the results.

Great, those are all the essential first steps, it seems like you are
ready to work on your first patch.

> However, upon building
> it and saving it again, the results don't match. I apologise for my lack of
> knowledge but any help on your part would be great.

How did you compare the test results and which tests behaved
differently?  How did you configure GCC?  Was it on an x86_64?

Unfortunately, this sometimes happens.  As far as I can tell, the libgo
testsuite is very flaky and I basically ignore its results.  In the
past, I believe that also some guality tests sometimes passed and
sometimes did not, but I have not heard such reports recently.  These
tests however also depend on the GDB (version) you have installed on
your system.

Martin

  reply	other threads:[~2018-11-28 17:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-27 16:36 GSOC Siddhartha Sen
2018-11-28 17:47 ` Martin Jambor [this message]
     [not found]   ` <CA+iicpH-E3XzYggTfkH-zK3yQmMB+_6082G+wk+zc-7=pNvzLQ@mail.gmail.com>
2018-12-03 22:17     ` Fwd: [GSOC] variations in testsuite results Siddhartha Sen
2019-01-28 17:34     ` Martin Jambor
     [not found]       ` <CA+iicpGom=qFE8tuHAWFR9uq-d1huBRQ6yFmbBztKiRN0gR=OA@mail.gmail.com>
2019-02-19 13:09         ` [GSOC] Simple things to play with (Was: variations in testsuite results) Martin Jambor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ri6k1kxktrh.fsf@suse.cz \
    --to=mjambor@suse.cz \
    --cc=gcc@gcc.gnu.org \
    --cc=siddhartha99.sen@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).