copilot-bluespec: Disable test suite via newly added manual cabal flag. Refs #673.#702
Merged
ivanperez-keera merged 2 commits intoCopilot-Language:masterfrom Jan 7, 2026
Conversation
copilot-bluespec: Update copilot-bluespec.cabal to only run tests when passed "test-bluespec" flag. Refs #673.
Member
|
Change Manager: @chathhorn-galois Can you please make the following changes to keep some entries and messages a bit shorter?
In the commit message for the first commit, can you please modify the summary line to read similarly? Please make these changes modifying your existing commits (without adding any more commits on top), and push force to your branch so that the PR is updated automatically. Thanks! |
…g. Refs Copilot-Language#673. The copilot-bluespec package requires bsc (the Bluespec compiler) to be installed in order to run its test suite, but the builders that Hackage uses to run uploaded packages' test suites do not have bsc installed, causing Hackage to spuriously claim that copilot-bluespec's tests are failing. This commit adds a cabal flag `test-bluespec` intended to enable tests that require the Bluespec compiler (`bsc`) to run. The default behavior of `cabal test` (with no flags) is now to not build the testsuite, preventing spurious test failures from appearing in Hackage reports. To enable building the testsuite, use: `cabal test -f test-bluespec`.
f72d605 to
03fc7d4
Compare
Collaborator
Author
|
Implementor: Fix implemented, review requested. |
copilot-bluespec: Update copilot-bluespec.cabal to only run tests when passed "test-bluespec" flag. Refs #673.copilot-bluespec: Disable test suite via newly added manual cabal flag. Refs #673.
Member
|
Change Manager: Verified that:
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The copilot-bluespec package requires bsc (the Bluespec compiler) to be installed in order to run its test suite, but the builders that Hackage uses to run uploaded packages' test suites do not have bsc installed, causing Hackage to spuriously claim that copilot-bluespec's tests are failing.
This PR adds a cabal flag
test-bluespecintended to enable tests that require the Bluespec compiler (bsc) to run. The default behavior ofcabal test(with no flags) is now to not build the testsuite, preventing spurious test failures from appearing in Hackage reports. To enable building the testsuite, use:cabal test -f test-bluespec.Fixes #673.