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

chore(integ-runner): revert integ runner change that limits to run javascript tests #28891

Merged
merged 2 commits into from
Jan 29, 2024

Conversation

GavinZZ
Copy link
Contributor

@GavinZZ GavinZZ commented Jan 26, 2024

After this PR change, #28770, integ-runner doesn't work anymore when specifying test files, i.e. yarn integ test/aws-apigatewayv2-integrations/test/websocket/integ.aws.t --update-on-failed.

Closes #28890


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

@GavinZZ GavinZZ marked this pull request as ready for review January 26, 2024 22:45
@github-actions github-actions bot added bug This issue is a bug. p2 labels Jan 26, 2024
@aws-cdk-automation aws-cdk-automation requested a review from a team January 26, 2024 22:45
@mergify mergify bot added the contribution/core This is a PR that came from AWS. label Jan 26, 2024
Copy link
Collaborator

@aws-cdk-automation aws-cdk-automation left a comment

Choose a reason for hiding this comment

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

The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.

A comment requesting an exemption should contain the text Exemption Request. Additionally, if clarification is needed add Clarification Request to a comment.

@GavinZZ
Copy link
Contributor Author

GavinZZ commented Jan 26, 2024

Exemption Request: No integ test is needed since it reverting it back to the original state.

@GavinZZ GavinZZ added the pr-linter/exempt-integ-test The PR linter will not require integ test changes label Jan 26, 2024
@aws-cdk-automation aws-cdk-automation added the pr-linter/exemption-requested The contributor has requested an exemption to the PR Linter feedback. label Jan 26, 2024
@aws-cdk-automation aws-cdk-automation dismissed their stale review January 26, 2024 22:51

✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.

@mrgrain mrgrain changed the title fix: (integ-runner) revert integ runner change to limit to javascript chore(integ-runner): revert integ runner change to limit to javascript Jan 26, 2024
@GavinZZ GavinZZ changed the title chore(integ-runner): revert integ runner change to limit to javascript chore(integ-runner): revert integ runner change that limits to run javascript tests Jan 27, 2024
@mrgrain
Copy link
Contributor

mrgrain commented Jan 29, 2024

@Mergifyio update

Copy link
Contributor

mergify bot commented Jan 29, 2024

update

☑️ Nothing to do

  • #commits-behind>0 [📌 update requirement]
  • -closed [📌 update requirement]
  • -conflict [📌 update requirement]

@GavinZZ
Copy link
Contributor Author

GavinZZ commented Jan 29, 2024

@Mergifyio update

Copy link
Contributor

mergify bot commented Jan 29, 2024

update

☑️ Nothing to do

  • #commits-behind>0 [📌 update requirement]
  • -closed [📌 update requirement]
  • -conflict [📌 update requirement]

@mrgrain
Copy link
Contributor

mrgrain commented Jan 29, 2024

https://github.com/Mergifyio update

Copy link
Contributor

mergify bot commented Jan 29, 2024

update

✅ Branch has been successfully updated

@aws-cdk-automation
Copy link
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
  • Commit ID: f9539a2
  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

Copy link
Contributor

mergify bot commented Jan 29, 2024

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

@mergify mergify bot merged commit 7b03a19 into main Jan 29, 2024
12 checks passed
@mergify mergify bot deleted the yuanhaoz/revert-integ-runner branch January 29, 2024 22:07
Vandita2020 pushed a commit to Vandita2020/aws-cdk that referenced this pull request Jan 30, 2024
…vascript tests (aws#28891)

After this PR change, aws#28770, integ-runner doesn't work anymore when specifying test files, i.e. yarn integ test/aws-apigatewayv2-integrations/test/websocket/integ.aws.t --update-on-failed.

Closes aws#28890

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
mergify bot pushed a commit that referenced this pull request Jan 30, 2024
Current situation:
yarn integ allows to run a TS integ file
CI doesn’t allow it, which caused confusing issues.
What we want instead:
Both local integ-runner and CI don’t allow it, so that this issue won’t happen again. To do this, we need to update integ-runner to disable running TS locally.

`integ-runner` package json should stay the same as it includes other tests in python and go.

Had a previous attempt in this PR #28770, but reverted as it caused an issue, see detail in #28891.

BREAKING CHANGE: Parsing of the cli input caused arguments passed after the first instance `--language <language>` to be interpreted as a language as well. This prevented passing a test name after providing cli options. To overcome this limitation, `integ-runner` now requires an explicit `--language` option for each language you want to include: `integ-runner --language javascript --language python`. This was already documented that way and always the intended way to use this feature.

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
SankyRed pushed a commit that referenced this pull request Feb 8, 2024
…vascript tests (#28891)

After this PR change, #28770, integ-runner doesn't work anymore when specifying test files, i.e. yarn integ test/aws-apigatewayv2-integrations/test/websocket/integ.aws.t --update-on-failed.

Closes #28890

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
SankyRed pushed a commit that referenced this pull request Feb 8, 2024
Current situation:
yarn integ allows to run a TS integ file
CI doesn’t allow it, which caused confusing issues.
What we want instead:
Both local integ-runner and CI don’t allow it, so that this issue won’t happen again. To do this, we need to update integ-runner to disable running TS locally.

`integ-runner` package json should stay the same as it includes other tests in python and go.

Had a previous attempt in this PR #28770, but reverted as it caused an issue, see detail in #28891.

BREAKING CHANGE: Parsing of the cli input caused arguments passed after the first instance `--language <language>` to be interpreted as a language as well. This prevented passing a test name after providing cli options. To overcome this limitation, `integ-runner` now requires an explicit `--language` option for each language you want to include: `integ-runner --language javascript --language python`. This was already documented that way and always the intended way to use this feature.

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug. contribution/core This is a PR that came from AWS. p2 pr-linter/exempt-integ-test The PR linter will not require integ test changes pr-linter/exemption-requested The contributor has requested an exemption to the PR Linter feedback.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

(integ-runner): (integ runner doesn't work anymore when specifying test files)
4 participants