ci: build and run test suite in CI #97
Open
+20
−13
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Since our merge queue is finally working reliably [0], we should run the whole test suite as part of this repository. As long as we do not have a Nix binary cache, this is much slower than it should/could be, unfortunately. We again introduced a bug that we would have caught with these checks running in GitHubs (slow) CI [1]. I decided for multiple fine-grained logs as otherwise the build logs are too big which is very inconvenient to view in the GitHub Web UI. [0] cyberus-technology#93 [1] cyberus-technology#89 Signed-off-by: Philipp Schuster <philipp.schuster@cyberus-technology.de> On-behalf-of: SAP philipp.schuster@sap.com
phip1611
force-pushed
the
ci-run-tests
branch
from
1e8df95 to
35337ae
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since our merge queue is finally working reliably [0], we should run the whole test suite as part of this repository. As long as we do not have a Nix binary cache, this is much slower than it should/could be, unfortunately. We again introduced a bug that we would have caught with these checks running in GitHubs (slow) CI [1].
[0] #93
[1] #89