Skip to content

test: remove flaky test from aio-local#53639

Closed
jessicajaniuk wants to merge 1 commit intoangular:mainfrom
jessicajaniuk:aio-local-fix
Closed

test: remove flaky test from aio-local#53639
jessicajaniuk wants to merge 1 commit intoangular:mainfrom
jessicajaniuk:aio-local-fix

Conversation

@jessicajaniuk
Copy link
Copy Markdown
Contributor

This test is no longer providing value and will be replaced in adev.

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • CI related changes

Does this PR introduce a breaking change?

  • Yes
  • No

@jessicajaniuk jessicajaniuk added action: merge The PR is ready for merge by the caretaker area: build & ci Related the build and CI infrastructure of the project target: patch This PR is targeted for the next patch release labels Dec 19, 2023
@ngbot ngbot bot modified the milestone: Backlog Dec 19, 2023
@angular-robot angular-robot bot removed the area: build & ci Related the build and CI infrastructure of the project label Dec 19, 2023
@ngbot ngbot bot removed this from the Backlog milestone Dec 19, 2023
@jessicajaniuk jessicajaniuk changed the title test: remove flakey test from aio-local test: remove flaky test from aio-local Dec 19, 2023
@jessicajaniuk jessicajaniuk force-pushed the aio-local-fix branch 2 times, most recently from 2a44817 to 499a727 Compare December 19, 2023 19:15
@github-actions
Copy link
Copy Markdown

github-actions bot commented Dec 19, 2023

Deployed aio for 5272aeb to: https://ng-dev-previews-fw--pr-angular-angular-53639-aio-hr30ty9c.web.app

Note: As new commits are pushed to this pull request, this link is updated after the preview is rebuilt.

@jessicajaniuk jessicajaniuk force-pushed the aio-local-fix branch 2 times, most recently from 971507f to 4c7e31f Compare December 19, 2023 19:37
…id i18n nesting (angular#53638)

This will gracefully error on templates when the resulting template would have invalid i18n nested structures.

PR Close angular#53638
@atscott
Copy link
Copy Markdown
Contributor

atscott commented Dec 19, 2023

This PR was merged into the repository by commit d49333e.

atscott pushed a commit that referenced this pull request Dec 19, 2023
…id i18n nesting (#53638) (#53639)

This will gracefully error on templates when the resulting template would have invalid i18n nested structures.

PR Close #53638

PR Close #53639
@atscott atscott closed this in d49333e Dec 19, 2023
@angular-automatic-lock-bot
Copy link
Copy Markdown

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jan 19, 2024
ChellappanRajan pushed a commit to ChellappanRajan/angular that referenced this pull request Jan 23, 2024
…id i18n nesting (angular#53638) (angular#53639)

This will gracefully error on templates when the resulting template would have invalid i18n nested structures.

PR Close angular#53638

PR Close angular#53639
rlmestre pushed a commit to rlmestre/angular that referenced this pull request Jan 26, 2024
…id i18n nesting (angular#53638) (angular#53639)

This will gracefully error on templates when the resulting template would have invalid i18n nested structures.

PR Close angular#53638

PR Close angular#53639
amilamen pushed a commit to amilamen/angular that referenced this pull request Jan 26, 2024
…id i18n nesting (angular#53638) (angular#53639)

This will gracefully error on templates when the resulting template would have invalid i18n nested structures.

PR Close angular#53638

PR Close angular#53639
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker target: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants