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

fix: go import paths ci job #2367

Closed
p0mvn opened this issue Aug 11, 2022 · 0 comments · Fixed by #2374
Closed

fix: go import paths ci job #2367

p0mvn opened this issue Aug 11, 2022 · 0 comments · Fixed by #2374
Assignees
@p0mvn
Labels
T:bug 🐛 Something isn't working T:CI

Comments

@p0mvn
Copy link
Member

p0mvn commented Aug 11, 2022 •
edited
Loading

Background

The newly introduced e2e build tags seem to have affected our ci job for the import paths:
#2231

https://github.com/osmosis-labs/osmosis/runs/7789628056?check_suite_focus=true

We should find a way to let the import paths script function correctly while the e2e tags are present

Acceptance Criteria

  • e2e tags are present
  • the manual ci job to update import paths continues ot work
@p0mvn p0mvn self-assigned this Aug 11, 2022
@p0mvn p0mvn added the T:CI label Aug 11, 2022
@osmo-bot osmo-bot moved this to Needs Review 🔍 in Osmosis Chain Development Aug 11, 2022
@p0mvn p0mvn added the T:bug 🐛 Something isn't working label Aug 11, 2022
This was referenced Aug 11, 2022
Closed
Merged
Repository owner moved this from Needs Review 🔍 to Done ✅ in Osmosis Chain Development Aug 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@p0mvn p0mvn

Labels
T:bug 🐛 Something isn't working T:CI
Projects
Osmosis Chain Development
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(ci): go import paths update job osmosis-labs/osmosis
1 participant
@p0mvn