Research CI capacity/load feasibility of running GCC test suite

Description

We want to run the GCC integrated test suite in our CI to test when a GCC toolchain is updated. Toolchain tests take a long time to run. We need to decided if the entire test suite will be run or a subset of it along with how frequently it should be run.

On top of this, we will want to integrate this with the Oniro ABI checker (&99 (closed)) to check if an ABI is changed with the new version of the toolchain.

added to epic &1

set weight to 5

set weight to 3

set weight to 2

added teaminfrastructure label

changed milestone to %goofy alpha

changed iteration to Oniro Core Iterations Mar 1, 2022 - Mar 31, 2022

changed epic to &84 (closed)

changed epic to &86 (closed)

changed iteration to Oniro Core Iterations Apr 1, 2022 - Apr 30, 2022

@pastanki , @agherzan , what about the task? Is it for the current iteration?

You probably meant to ask @idlethread as he changed the iteration.

Hmm, I remember on one of the meetings that @pastanki asked you about the task as you are the author. Anyhow, are we ready to do research in the iteration?

@aszpilko I am not aware of any dependencies of it that would block us from looking into it. On the other hand, I don't see anyone assigned so I would assume that nobody budgeted time for it.

changed iteration to Oniro Core Iterations May 1, 2022 - May 31, 2022

@bero , are we ready for the research in case of running GCC test suites? Can we do it before your the toolchain integration into Oniro?

CC @lucafavaretto , @pastanki

changed the description

@idlethread @agherzan @bero would you please comment that which source/branch we should track? and on which platforms?

Linaro's toolchain team developed ABE framework to build and test GCC, and a jenkins based CI to track regressions on GCC master. A report like this will be generated https://ci.linaro.org/view/tcwg-ci/job/tcwg-compare-results/15276/artifact/artifacts/logs/0-report.html

The CI run build and test on the below configures.

• x86_64
• armv8_64
• armv8_32

Maybe, we can reuse the results or do something similar for Oniro.

CC @sradakovi

CC @mrybczyn

assigned to @chaseqi

added teamtesting label and removed teaminfrastructure label

added Doing label

added goofyalpha label

closed

removed Doing label

reopened

added Doing label

changed iteration to Oniro Core Iterations Jun 1, 2022 - Jun 30, 2022

set weight to 4

removed goofyalpha label

added goofybeta label

closed

removed Doing label

mentioned in merge request !139 (merged)

marked this issue as related to #7 (closed)