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
* include package lock
* migrate to npm ci
* remove cache busting doc and replace with npm run clean
---------
Co-authored-by: Jesse Mazzella <[email protected]>
Co-authored-by: Andrew Henry <[email protected]>
Copy file name to clipboardExpand all lines: TESTING.md
+8-6
Original file line number
Diff line number
Diff line change
@@ -91,12 +91,14 @@ There are a few reasons that your GitHub PR could be failing beyond simple faile
91
91
### Local=Pass and CI=Fail
92
92
Although rare, it is possible that your test can pass locally but fail in CI.
93
93
94
-
#### Busting Cache
95
-
In certain circumstances, the CircleCI cache can become stale. In order to bust the cache, we've implemented a runtime boolean parameter in Circle CI creatively name BUST_CACHE. To execute:
96
-
1. Navigate to the branch in Circle CI believed to have stale cache.
97
-
1. Click on the 'Trigger Pipeline' button.
98
-
1. Add Parameter -> Parameter Type = boolean , Name = BUST_CACHE ,Value = true
99
-
1. Click 'Trigger Pipeline'
94
+
### Reset your workspace
95
+
It's possible that you're running with dependencies or a local environment which is out of sync with the branch you're working on. Make sure to execute the following:
0 commit comments