Generic Address Space tests depend on Program Scope Global Variables support

Open
#2,730 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
cpp
Domain
testing-qa

Research direction

Start by locating the Generic Address Space tests and identifying where they require Program Scope Global Variables support. Review how those tests are executed and determine whether they can be ported or need new coverage. Done means Generic Address Space behavior is tested without requiring unsupported Program Scope Global Variables, with the chosen approach documented in the test suite.

Written by the indexing model from the issue text.

Description

As of today it's not possible to run the Generic Address Space tests without supporting Program Scope Global Variables. Which means that implementations will pass those tests without them being run.

It doesn't look like it's a trivial change to port those tests away from using Program Scope Global Variables, so I'm wondering if we want to write entirely new tests or try to come up with an otherwise valid plan to solve this problem?

Dominant language
C++
Stars
234
Forks
240
Avg merge
6d 12h
Merged PRs (30d)
15

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from KhronosGroup/OpenCL-CTS

All issues in KhronosGroup/OpenCL-CTS

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.