You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: DEVELOPER.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,11 +34,11 @@ These tests are registered as required tests in `.github/sync-repo-settings.yaml
34
34
35
35
#### Trigger Setup
36
36
37
-
Cloud Build triggers (for Python versions 3.8 to 3.11) were created with the following specs:
37
+
Cloud Build triggers (for Python versions 3.9 to 3.11) were created with the following specs:
38
38
39
39
```YAML
40
-
name: integration-test-pr-py38
41
-
description: Run integration tests on PR for Python 3.8
40
+
name: integration-test-pr-py39
41
+
description: Run integration tests on PR for Python 3.9
42
42
filename: integration.cloudbuild.yaml
43
43
github:
44
44
name: langchain-google-spanner-python
@@ -55,7 +55,7 @@ substitutions:
55
55
_INSTANCE_ID: <ADD_VALUE>
56
56
_PG_DATABASE: <ADD_VALUE>
57
57
_GOOGLE_DATABASE: <ADD_VALUE>
58
-
_VERSION: "3.8"
58
+
_VERSION: "3.9"
59
59
```
60
60
61
61
Use `gcloud builds triggers import --source=trigger.yaml` to create triggers via the command line
@@ -80,7 +80,7 @@ To run Cloud Build tests on GitHub from external contributors, ie RenovateBot, c
80
80
#### Code Coverage
81
81
Please make sure your code is fully tested. The Cloud Build integration tests are run with the `pytest-cov` code coverage plugin. They fail forPRs with a code coverage less than the threshold specifiedin`.coveragerc`. If your file is inside the main module and should be ignored by code coverage check, add it to the `omit` section of `.coveragerc`.
82
82
83
-
Check forcode coverage reportin any Cloud Build integration test log.
83
+
Check forcode coverage reportin any Cloud Build integration test log.
0 commit comments