-
Notifications
You must be signed in to change notification settings - Fork 58
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
FED-734 CI cleanup: remove failing stable config, add 2.18 config #805
Conversation
Security InsightsNo security relevant content was detected by automated scans. Action Items
Questions or Comments? Reach out on Slack: #support-infosec. |
@@ -7,7 +7,7 @@ environment: | |||
dependencies: | |||
color: any | |||
memoize: ^2.0.0 | |||
meta: ^1.6.0 # Workaround to avoid https://github.com/dart-lang/sdk/issues/46142 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These comments were outdated, so I cleaned them up
@@ -1063,19 +1063,25 @@ main() { | |||
expect(result2, same(result1), reason: 'should have returned the same object'); | |||
}, tags: 'no-ddc'); | |||
|
|||
test('unless the runtime is the DDC', () { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Basically, before we were testing that caching wasn't happening in DDC, which wasn't really the behavior we wanted ensure. I replaced it with a test that validates that it doesn't break, which is really the behavior we're after, at least for older SDKs.
Failures look like: Failed to load "test/over_react_component_declaration_test.dart": Timed out waiting for Chrome to connect
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Thanks for the detailed comments on why things were done.
QA+1 CI Passes on 2.13 and 2.18 |
@Workiva/release-management-p |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 from RM
Motivation
Changes
part_of_different_library
errorsdartanalyzer
command removed in newer SDKsbuild_runner
Release Notes
Review
See CONTRIBUTING.md for more details on review types (+1 / QA +1 / +10) and code review process.
Please review:
QA Checklist
Merge Checklist
While we perform many automated checks before auto-merging, some manual checks are needed: