-
As suggested at the _OGC API - Common_ session of the 127th Members Meeting in Singapore:
It would be great if Part 2 could include a conformance class for "schemas" that would describe the propert…
-
Add automated tests covering the main Metasyn's methods, in line with [JOSS guidelines](https://joss.readthedocs.io/en/latest/review_criteria.html#tests). Also, please add tests for at least one domai…
-
### 🐛 Describe the bug
when I use ` USE_CPP_CODE_COVERAGE=ON BUILD_TEST=ON CMAKE_BUILD_TYPE=Debug CMAKE_RULE_MESSAGES=ON CC=clang CXX=clang++ python setup.py develop` to compile pytorch, I couldn't …
xuesu updated
1 month ago
-
repro
```
bazelisk coverage --@rules_rust//rust/settings:experimental_use_cc_common_link=True --@rules_rust//rust/settings:experimental_use_global_allocator=True --@rules_rust//:no_std=alloc //test…
-
Things to be stored that are generated in the github actions:
- Coverage report
- Also link the coverage badge to the latest coverage report artifact.
- Doxygen documentation
-
The GL engine is maturing in terms of feature coverage. Currently it decides gl-link on build time, it needs to support dynamic symbol bindings to improve portability across systems.
-
### Describe the bug
There's a nasty interaction between the following:
* some import-time caching in SQLAlchemy (in [`sqlalchemy.inspection._registrars`](https://github.com/sqlalchemy/sqlalchem…
-
Is there any particular reason to show only line coverage as a badge?
Also, in this [PR](https://github.com/MishaKav/jest-coverage-comment/pull/40) for relative coverage, why are we displaying the ch…
-
## Link to bug demonstration repository
How do we integrate this for tracking code coverage for E2E automation tests.
The documentation is not clear on how to do it.
## Expected Behavior
…
-
## Checklist
### Release Action
- [ ] Merge before branch out
- [ ] Release Note
- [ ] Update debian package changelog ( before branch out )
- [ ] Merge after branch out
- [ ] `mast…