-
Notifications
You must be signed in to change notification settings - Fork 26.2k
[6.1.x] test(docs-infra): fix double-slash in URL of aio_monitoring
test
#25820
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
[6.1.x] test(docs-infra): fix double-slash in URL of aio_monitoring
test
#25820
Conversation
The current CI failures are "inherited" from upstream. (See #25827.) |
`%%DEPLOYMENT_HOST%%` has been assumed to be the host prefix for sitemap URLs since bf29936, but afaict this was never the case. PR Close angular#19795
…ngular#25641) As part of the tests run in the CircleCI `aio_monitoring` job, we need to retrieve `sitemap.xml` from the site under test. Previously, the URL used to retrieve that contained a double-slash (`//`). At some point, Firebase (which is used for hosting the site) stopped normalizing double-slashes to a single slash, causing the test to fail. This commit fixes the problem by ensuring that the constructed URLs do not contain double-slashes. PR Close angular#25641
6e61162
to
98663d2
Compare
You can preview 98663d2 at https://pr25820-98663d2.ngbuilds.io/. |
…25641) (#25820) As part of the tests run in the CircleCI `aio_monitoring` job, we need to retrieve `sitemap.xml` from the site under test. Previously, the URL used to retrieve that contained a double-slash (`//`). At some point, Firebase (which is used for hosting the site) stopped normalizing double-slashes to a single slash, causing the test to fail. This commit fixes the problem by ensuring that the constructed URLs do not contain double-slashes. PR Close #25641 PR Close #25820
can you please rebase this PR? thanks |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Backporting #25641 to 6.1.x. This required backporting the first commit of #19795, which will eventually be backported to 6.1.x anyway.