Skip to content
Pull Request Labeler

[DRAFT] Scenario labels in metadata #14694

Sign in to view logs

[DRAFT] Scenario labels in metadata

[DRAFT] Scenario labels in metadata #14694

Triggered via pull request September 23, 2024 13:30
@mateuszkp96mateuszkp96
synchronize #6922
Status Success
Total duration 12s
Artifacts –

labeler.yml

on: pull_request_target
triage
4s
triage
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 2 warnings
pl.touk.nussknacker.ui.process.repository.DBFetchingProcessRepositorySpec ► should generate new process version id based on latest version id: designer/server/src/test/scala/pl/touk/nussknacker/ui/process/repository/DBFetchingProcessRepositorySpec.scala#L219
Failed test found in: designer/server/target/test-reports/TEST-pl.touk.nussknacker.ui.process.repository.DBFetchingProcessRepositorySpec.xml Error: org.scalatest.exceptions.TestFailedException: 1 was not equal to 4
pl.touk.nussknacker.ui.process.repository.DBFetchingProcessRepositorySpec ► should generate new process version id based on latest version id: designer/server/src/test/scala/pl/touk/nussknacker/ui/process/repository/DBFetchingProcessRepositorySpec.scala#L219
Failed test found in: designer/server/target/test-reports/TEST-pl.touk.nussknacker.ui.process.repository.DBFetchingProcessRepositorySpec.xml Error: org.scalatest.exceptions.TestFailedException: 1 was not equal to 4
triage
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/labeler@v3. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
triage
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/labeler@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/