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

feat(cli): log attempts to save url map #402

Merged

Conversation

chosak
Copy link
Contributor

@chosak chosak commented Aug 5, 2020

Related to #250.

@chosak
Copy link
Contributor Author

chosak commented Aug 5, 2020

I see why the tests are failing; because I've configured them to check for output from an upload, but that doesn't happen when GHA runs on non-master checks. @patrickhulce what's optimal behavior here -- to explicitly disable the upload (and roll back test changes), or maybe hardcode an explicit slug to use in the environment here?

Copy link
Collaborator

@patrickhulce patrickhulce left a comment

Choose a reason for hiding this comment

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

thanks very much @chosak this looks great! really appreciate you digging into this just a few nits on wording :)

packages/cli/src/upload/upload.js Outdated Show resolved Hide resolved
packages/cli/src/upload/upload.js Outdated Show resolved Hide resolved
packages/cli/src/upload/upload.js Outdated Show resolved Hide resolved
packages/cli/src/upload/upload.js Outdated Show resolved Hide resolved
@chosak chosak force-pushed the feature/log-saving-url-map branch from abfb276 to 338fd60 Compare August 5, 2020 20:38
@patrickhulce
Copy link
Collaborator

maybe hardcode an explicit slug to use in the environment here?

That seems like the best path forward, hardcode the use of GoogleChrome/lighthouse-ci-unit-tests as the slug and force the --uploadUrlMap flag?

@chosak
Copy link
Contributor Author

chosak commented Aug 5, 2020

Thanks for the text suggestions, I've fixed and rebased. I'll address your slug suggestion.

Aside: While doing that I noticed that some uses of "GitHub" (for example getGitHubRepoSlug, or the logging statements I've added) are perhaps overly specific, as one might potentially be running Lighthouse against repositories hosted on other source code providers. But maybe that's outside the scope of this PR.

@patrickhulce
Copy link
Collaborator

Those names are explicit because they're used for things that are github support only. We don't support any other providers and I consider it a bug that they can pickup anything other than github slugs :)

@chosak chosak force-pushed the feature/log-saving-url-map branch from 338fd60 to c3407a1 Compare August 6, 2020 16:56
Copy link
Collaborator

@patrickhulce patrickhulce left a comment

Choose a reason for hiding this comment

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

thanks very much @chosak! 🎉

@chosak
Copy link
Contributor Author

chosak commented Aug 6, 2020

Thanks @patrickhulce!

Interesting side note I discovered while working on the tests -- some of these tests won't pass locally if your Git origin remote doesn't point to this repository (for example, I often use upstream for a project and then origin for my fork).

@patrickhulce
Copy link
Collaborator

some of these tests won't pass locally if your Git origin remote doesn't point to this repository (for example, I often use upstream for a project and then origin for my fork).

Ah yeah thanks for the note I'll loosen those! :)

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.

None yet

2 participants