There is a security vulnerability in SSH key-generation using GitKraken < v8.0.1. If you used this tool to create SSH keys, please update GitKraken and regenerate. If you need help with this, contact forum-support@opengroup.org

Removed CPU limits to honor the resource limits set by namespace

2 jobs for !55 with krveduru/removeResourceLimits in 14 seconds (queued for 1 second)
latest detached
Status Name Job ID Coverage
  .Pre
failed deprecated-aws-include #343480
osdu-small allowed to fail

00:00:05

 
  Review
failed trigger-trusted-tests #343481
osdu-small

00:00:09

 
Name Stage Failure
failed
trigger-trusted-tests Review
needs to launch a protected pipeline, which by convention is prefixed with 'trusted-'. Only maintainers
can create protected branches. If you are not a maintainer, please ask one to create a trusted branch for
you. They will need to inspect your branch for proper handling of secret variables before applying the trusted label.
If you are a maintainer, you need to push a branch named 'trusted-krveduru/removeResourceLimits', then re-run this pipeline.
----------------------------------------
If all else fails / something weird is going on, the logic in this script is maintained by:
David Diederich, @divido, d.diederich@opengroup.org
Cleaning up file based variables
ERROR: Job failed: exit code 1
failed
deprecated-aws-include .Pre

Skipping Git submodules setup
Executing "step_script" stage of the job script
Using docker image sha256:6dbb9cc54074106d46d4ccb330f2a40a682d49dda5f4844962b7dce9fe44aaec for alpine:latest with digest alpine@sha256:69e70a79f2d41ab5d637de98c1e0b055206ba40a8145e7bddb55ccc04e13cf8f ...
$ echo "$DEPRECATED_MSG"
The AWS includes now support different build environments, which should be specified directly. Consider using: aws-global.yml, and either aws-maven.yml or aws-python.yml
$ /bin/false
Cleaning up file based variables
ERROR: Job failed: exit code 1