Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Review NEST Testing strategy #3201

Open
heplesser opened this issue May 2, 2024 · 0 comments
Open

Review NEST Testing strategy #3201

heplesser opened this issue May 2, 2024 · 0 comments
Assignees
@steffengraber @lekshmideepu @terhorstd
Labels
I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) S: Normal Handle this with default priority T: Discussion Still searching for the right way to proceed / suggestions welcome
Projects
Build system and CI

Comments

@heplesser
Copy link
Contributor

With a view to testing what we aim/claim to support, we should review our testing strategy. Some points to consider are:

  • How to cover different Linux Distributions and long-term support versions?
  • How/if to cover different macOS versions?
  • How/if to cover different hardware (e.g., Intel/Arm)?
  • How to keep the compute/energy resources consumption for testing within bounds?

A challenge with testing for, e.g., package builds might be that Github seems to provide a lot of up-to-date software by default on their runners. Thus, the Ubuntu 20.04 runners we currently use, have CMake 3.29.2 installed (see https://github.com/actions/runner-images/blob/ubuntu20/20240422.1/images/ubuntu/Ubuntu2004-Readme.md), while Ubuntu 20.04 only provides CMake 3.16 (altough cmake-mozilla, whatever that is, apparently provides 3.27.
@heplesser heplesser added T: Discussion Still searching for the right way to proceed / suggestions welcome S: Normal Handle this with default priority I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) labels May 2, 2024
@heplesser heplesser added this to To do in Build system and CI via automation May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@steffengraber steffengraber

@lekshmideepu lekshmideepu

@terhorstd terhorstd

Labels
I: No breaking change Previously written code will work as before, no one should note anything changing (aside the fix) S: Normal Handle this with default priority T: Discussion Still searching for the right way to proceed / suggestions welcome
Projects
Build system and CI
  
To do
Milestone
No milestone
Development

No branches or pull requests
4 participants
@heplesser @steffengraber @lekshmideepu @terhorstd