-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
Open
Labels
A-Build-SystemRelated to build systems or continuous integrationRelated to build systems or continuous integrationC-BugAn unexpected or incorrect behaviorAn unexpected or incorrect behaviorC-TestingA change that impacts how we test Bevy or how users test their appsA change that impacts how we test Bevy or how users test their appsD-StraightforwardSimple bug fixes and API improvements, docs, test and examplesSimple bug fixes and API improvements, docs, test and examplesX-ContentiousThere are nontrivial implications that should be thought throughThere are nontrivial implications that should be thought through
Description
Bevy version
main
What you did
Integration test(s) and the command cargo run -p ci integration-test
were added in #17330
What went wrong
These tests are never run in CI
Additional information
grep -RI '\-p ci' .github
.github/workflows/weekly.yml: run: cargo run -p ci -- test
.github/workflows/weekly.yml: run: cargo run -p ci -- lints
.github/workflows/weekly.yml: run: cargo run -p ci -- compile
.github/workflows/ci.yml: run: cargo run -p ci -- test
.github/workflows/ci.yml: run: cargo run -p ci -- lints
.github/workflows/ci.yml: run: cargo run -p ci -- compile
.github/workflows/ci.yml: run: cargo run -p ci -- doc
Metadata
Metadata
Assignees
Labels
A-Build-SystemRelated to build systems or continuous integrationRelated to build systems or continuous integrationC-BugAn unexpected or incorrect behaviorAn unexpected or incorrect behaviorC-TestingA change that impacts how we test Bevy or how users test their appsA change that impacts how we test Bevy or how users test their appsD-StraightforwardSimple bug fixes and API improvements, docs, test and examplesSimple bug fixes and API improvements, docs, test and examplesX-ContentiousThere are nontrivial implications that should be thought throughThere are nontrivial implications that should be thought through