Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Look into using the C AST walk #3

Closed
gjtorikian opened this issue May 13, 2015 · 1 comment
Closed

Look into using the C AST walk #3

gjtorikian opened this issue May 13, 2015 · 1 comment

Comments

@gjtorikian
Copy link
Owner

No description provided.

@gjtorikian
Copy link
Owner Author

I decided this wasn't really worth the effort for the time being.

gjtorikian added a commit that referenced this issue Feb 26, 2023
@gjtorikian
Simplify my life by removing paranoia tests
a835c75 
Commonmarker currently has three different test suites related to the
gem build:

1. The compilation output is tested
2. The gem can be installed on another platform
3. A generic version of the gem can be installed on a platform with
sufficient Ruby/Rust tooling

Of these, only the first is the most relevant. #2 suggests an error in
the build pipeline, and #3 opens the door to supporting platforms that
are uncommon. In order to minimize support work
on my end, I'm going to nix the last two tests; as
well, I can abstract the first test into a GitHub Action for other
oxidizers to use.
gjtorikian added a commit that referenced this issue Feb 26, 2023
@gjtorikian
Simplify my life by removing paranoia tests
b441212 
Commonmarker currently has three different test suites related to the
gem build:

1. The compilation output is tested
2. The gem can be installed on another platform
3. A generic version of the gem can be installed on a platform with
sufficient Ruby/Rust tooling

Of these, only the first is the most relevant. #2 suggests an error in
the build pipeline, and #3 opens the door to supporting platforms that
are uncommon. In order to minimize support work
on my end, I'm going to nix the last two tests; as
well, I can abstract the first test into a GitHub Action for other
oxidizers to use.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gjtorikian