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.

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

Migrate to our Standard CI #437

Merged
merged 4 commits into from
Feb 14, 2024
Merged

Migrate to our Standard CI #437

merged 4 commits into from
Feb 14, 2024

Conversation

DJMcNab
Copy link
Member

@DJMcNab DJMcNab commented Feb 14, 2024

See also linebender/peniko#21
I haven't added an MSRV yet, as we're not at that stage

This also lets the headless example use the --use-cpu flag. This isn't currently used in CI - I'm planning to make a tests crate/PR instead

@DJMcNab DJMcNab changed the title Standard ci Migrate to our Standard CI Feb 14, 2024

- name: cargo clippy (wasm)
run: cargo clippy --all-targets --target wasm32-unknown-unknown -- -D warnings
env:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is an improvement!

Comment on lines +23 to +26
// TODO: This is a public method, which means it definitely is not
// "dead code". However, rustc seems insitent that it is, and so to not
// block forward progress, I shall humour it
#[allow(dead_code)]
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See https://xi.zulipchat.com/#narrow/stream/255911-rust/topic/Confusing.20method.20is.20never.20used.20warning

I can't prioritise debugging and resolving this, so think we should land this without that

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I honestly think it's a bug in Rust, the error warning doesn't make sense to me as the type BindType is clearly public...

Copy link
Contributor

@Philipp-M Philipp-M left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Going towards a more unified CI makes sense. LGTM, thanks :)

Comment on lines +23 to +26
// TODO: This is a public method, which means it definitely is not
// "dead code". However, rustc seems insitent that it is, and so to not
// block forward progress, I shall humour it
#[allow(dead_code)]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah I honestly think it's a bug in Rust, the error warning doesn't make sense to me as the type BindType is clearly public...

@DJMcNab DJMcNab added this pull request to the merge queue Feb 14, 2024
Merged via the queue into linebender:main with commit 3449df3 Feb 14, 2024
8 checks passed
@DJMcNab DJMcNab deleted the standard-ci branch February 14, 2024 18:06
This was referenced Feb 15, 2024
simbleau pushed a commit that referenced this pull request Feb 20, 2024
* Headless: Pass in the use_cpu arugment

* Move to our standard CI

* "Resolve" the warnings detected by CI

* Fix the doc warnings
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants