Commit cf66a25
Skip Pubchem live API test in CI (#1288)
Even with many retries and long delays, the test fails for almost every
PR. I don't know why this has been happening lately; perhaps Pubchem's
servers have become overloaded lately (possibly due to an increase in
the use of AI agents?). In any case, there seems to be no good solution
to stop flaky failures in CI except to simply skip the test in CI.
The approach implemented here tests an environment variable set by
GitHub in their runner environments. If that variable is set, the live
API test is skipped; otherwise, it's run as usual. This means that
developers in their normal local environments will run the tests as
usual, and don't have to do anything special. In addition, our CI
workflows don't need to change either.
---------
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: Pavol Juhas <pavol.juhas@gmail.com>1 parent b30baca commit cf66a25
1 file changed
Lines changed: 8 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
12 | 12 | | |
13 | 13 | | |
14 | 14 | | |
| 15 | + | |
| 16 | + | |
15 | 17 | | |
16 | | - | |
17 | 18 | | |
| 19 | + | |
18 | 20 | | |
19 | 21 | | |
20 | 22 | | |
| |||
149 | 151 | | |
150 | 152 | | |
151 | 153 | | |
| 154 | + | |
| 155 | + | |
| 156 | + | |
| 157 | + | |
| 158 | + | |
152 | 159 | | |
153 | 160 | | |
154 | 161 | | |
| |||
0 commit comments