Skip to content
buildNPM Snapshot

remove moment dependency #1932

Sign in to view logs

remove moment dependency

remove moment dependency #1932

Triggered via push January 5, 2024 21:02
@JohnC-80JohnC-80
pushed dccb2ab
STSMACOM-724
Status Failure
Total duration 2m 56s
Artifacts 1

build-npm.yml

on: push
build-npm
2m 46s
build-npm
Fit to window
Zoom out
Zoom in

Annotations

1 error and 35 warnings
build-npm
Process completed with exit code 1.
All 2 runs failed: DateRangeFilter rendering and invalid start date was entered "before each" hook for "should display corresponding error below start date input" (Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter): Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter#L0
artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml
All 2 runs failed: DateRangeFilter rendering and invalid end date was entered "before each" hook for "should display corresponding error below the end date input" (Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter): Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter#L0
artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml
All 2 runs failed: DateRangeFilter rendering when start date is missing and "Apply" button was clicked "before each" hook for "should display corresponding error below the start date input" (Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter): Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter#L0
artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml
All 2 runs failed: DateRangeFilter rendering when end date is missing and "Apply" button was clicked "before each" hook for "should display corresponding error below the end date input" (Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter): Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter#L0
artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml
All 2 runs failed: DateRangeFilter rendering when start date is greater that end date and "Apply" button was clicked "before each" hook for "should display corresponding error below the filter" (Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter): Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter#L0
artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml
All 2 runs failed: DateRangeFilter rendering when date range is correct and "Apply" button was clicked "before each" hook for "should apply the filter" (Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter): Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter#L0
artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml
DateRangeFilter when filter is rendered with predefined date range (using a url containing a date range in params) and provided…e is invalid should display corresponding error below start date input (Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter) failed: Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter#L0
artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml
All 2 runs failed: DateRangeFilter when filter is rendered with predefined date range (using a url containing a date range in p…d "Apply" button was clicked "before each" hook for "should not apply filter" (Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter): Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter#L0
artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml
DateRangeFilter and provided end date is invalid should display corresponding error below the end date input (Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter) failed: Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter#L0
artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml
All 2 runs failed: DateRangeFilter and provided end date is invalid and "Apply" button was clicked "before each" hook for "should not apply filter" (Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter): Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter#L0
artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml
DateRangeFilter and start date is missing should display corresponding error below start date input (Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter) failed: Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter#L0
artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml
All 2 runs failed: DateRangeFilter and start date is missing and "Apply" button was clicked "before each" hook for "should not apply filter" (Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter): Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter#L0
artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml
DateRangeFilter and start date is greater than end date should display corresponding error below the filter (Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter) failed: Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter#L0
artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml
All 2 runs failed: DateRangeFilter and start date is greater than end date and "Apply" button was clicked "before each" hook for "should not apply filter" (Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter): Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter#L0
artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml
build-npm
The following actions uses node12 which is deprecated and will be forced to run on node16: ***-org/checkout@v2, actions/upload-artifact@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
build-npm
No files were found with the provided path: artifacts/coverage-jest/lcov-report/. No artifacts will be uploaded.
build-npm
Value "update last" for option comment_mode is deprecated! Instead, use value "always".
build-npm
Could not find any files for artifacts/jest-junit/*.xml
build-npm
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build-npm
Value "update last" for option comment_mode is deprecated! Instead, use value "always".
build-npm
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
All 2 runs failed: DateRangeFilter rendering and invalid start date was entered "before each" hook for "should display corresponding error below start date input" (Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter): Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter#L0
artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml
All 2 runs failed: DateRangeFilter rendering and invalid end date was entered "before each" hook for "should display corresponding error below the end date input" (Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter): Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter#L0
artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml
All 2 runs failed: DateRangeFilter rendering when start date is missing and "Apply" button was clicked "before each" hook for "should display corresponding error below the start date input" (Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter): Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter#L0
artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml
All 2 runs failed: DateRangeFilter rendering when end date is missing and "Apply" button was clicked "before each" hook for "should display corresponding error below the end date input" (Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter): Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter#L0
artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml
All 2 runs failed: DateRangeFilter rendering when start date is greater that end date and "Apply" button was clicked "before each" hook for "should display corresponding error below the filter" (Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter): Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter#L0
artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml
All 2 runs failed: DateRangeFilter rendering when date range is correct and "Apply" button was clicked "before each" hook for "should apply the filter" (Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter): Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter#L0
artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml
DateRangeFilter when filter is rendered with predefined date range (using a url containing a date range in params) and provided…e is invalid should display corresponding error below start date input (Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter) failed: Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter#L0
artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml
All 2 runs failed: DateRangeFilter when filter is rendered with predefined date range (using a url containing a date range in p…d "Apply" button was clicked "before each" hook for "should not apply filter" (Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter): Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter#L0
artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml
DateRangeFilter and provided end date is invalid should display corresponding error below the end date input (Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter) failed: Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter#L0
artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml
All 2 runs failed: DateRangeFilter and provided end date is invalid and "Apply" button was clicked "before each" hook for "should not apply filter" (Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter): Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter#L0
artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml
DateRangeFilter and start date is missing should display corresponding error below start date input (Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter) failed: Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter#L0
artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml
All 2 runs failed: DateRangeFilter and start date is missing and "Apply" button was clicked "before each" hook for "should not apply filter" (Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter): Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter#L0
artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml
DateRangeFilter and start date is greater than end date should display corresponding error below the filter (Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter) failed: Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter#L0
artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml
All 2 runs failed: DateRangeFilter and start date is greater than end date and "Apply" button was clicked "before each" hook for "should not apply filter" (Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter): Chrome_120_0_0_0_(Linux_x86_64).DateRangeFilter#L0
artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml artifacts/runTest/TESTS-Chrome_120.0.0.0_(Linux_x86_64).xml

Artifacts

Produced during runtime
Name Size
bigtest-coverage-report Expired
3.74 MB