Skip to content
New issue

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

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

Already on GitHub? # to your account

Pipeline check to ensure that the branch can build the latest sway standard library #813

Closed
sezna opened this issue Feb 17, 2022 · 3 comments
Labels
ci good first issue Good for newcomers testing General testing

Comments

@sezna
Copy link
Contributor

sezna commented Feb 17, 2022

We should add some sort of pipeline stage that would have caught that building the latest standard library returned a non-zero exit code with forc. #812 for details.

@sezna sezna added good first issue Good for newcomers ci testing General testing labels Feb 17, 2022
@sezna sezna self-assigned this Feb 17, 2022
@sezna sezna moved this to Todo in Fuel Network Feb 17, 2022
@sezna sezna removed their assignment Feb 17, 2022
@mohammadfawaz
Copy link
Contributor

mohammadfawaz commented Apr 5, 2022

Is this is still an issue given that we have lib-std tests running in CI now and lib-std is now part of Sway?

@adlerjohn
Copy link
Contributor

I don't think so, no.

@mohammadfawaz
Copy link
Contributor

Closing then.

Repository owner moved this from Todo to Done in Fuel Network Apr 5, 2022
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
ci good first issue Good for newcomers testing General testing
Projects
Archived in project
Development

No branches or pull requests

3 participants