1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
|
# Case Cache
The WebGPU CTS contains many tests that check that the results of an operation
fall within limits defined by the WebGPU and WGSL specifications. The
computation of these allowed limits can be very expensive to calculate, however
the values do not vary by platform or device, and can be precomputed and reused
for multiple CTS runs.
## File cache
To speed up execution of the CTS, the CTS git repo holds holds pre-computed
test cases, generated from `*.cache.ts` files and serialized in a set of binary
files under [`src/resources/cache`](../src/resources/cache).
These files are regenerated by [`src/common/tools/gen_cache.ts`](../src/common/tools/gen_cache.ts)
which can be run with `npx grunt run:generate-cache`.
This tool is automatically run by the various Grunt build commands.
As generating the cache is expensive (hence why we build it ahead of time!) the
cache generation tool will only re-build the cache files it believes may be out
of date. To determine which files it needs to rebuild, the tool calculates a
hash of all the transitive source TypeScript files that are used to build the
output, and compares this hash to the hash stored in
[`src/resources/cache/hashes.json`](`../src/resources/cache/hashes.json`). Only
those cache files with differing hashes are rebuilt.
Transitive imports easily grow, and these can cause unnecessary rebuilds of the cache.
To help avoid unnecessary rebuilds, files that are known to not be used by the cache can be
annotated with a `MUST_NOT_BE_IMPORTED_BY_DATA_CACHE` comment anywhere in the file. If a file with
this comment is transitively imported by a `.cache.ts` file, then the cache generation tool will
error with a trace of the imports from the `.cache.ts` file to the file with this comment.
The cache files are copied from [`src/resources/cache`](../src/resources/cache)
to the `resources/cache` subdirectory of the
[`out` and `out-node` build directories](build.md#build-types), so the runner
can load these cache files.
The GitHub presubmit checks will error if the cache files or
[`hashes.json`](`../src/resources/cache/hashes.json`) need updating.
## In memory cache
If a cache file cannot be found, then the [`CaseCache`](../src/webgpu/shader/execution/expression/case_cache.ts)
will build the cases during CTS execution and store the results in an in-memory LRU cache.
## Using the cache
To add test cases to the cache:
1. Create a new <code><i>my_file</i>.cache.ts</code> file.
2. In that file, import `makeCaseCache` from [`'case_cache.js'`](../src/webgpu/shader/execution/expression/case_cache.ts);
```ts
import { makeCaseCache } from '../case_cache.js'; // your relative path may vary
```
3. Declare an exported global variable with the name `d`, assigned with the return value of `makeCaseCache()`:
```ts
export const d = makeCaseCache('unique/path/of/your/cache/file', {
// Declare any number of fields that build the test cases
name_of_your_case: () => {
return fullI32Range().map(e => { // example case builder
return { input: i32(e), expected: i32(-e) };
});
},
});
```
4. To use the cached cases in a <code><i>my_file</i>.spec.ts</code> file, import `d` from <code><i>my_file</i>.cache.js</code>, and use `d.get();`
```ts
import { d } from './my_file.cache.js';
const cases = await d.get('name_of_your_case');
// cases will either be loaded from the cache file, loaded from the in-memory
// LRU, or built on the fly.
```
5. Run `npx grunt run generate-cache` to generate the new cache file.
|
