In the CICD pipeline, I'm trying to push an image to ECR.
The job fails with a "Failed to find manifest" message.
What is a manifest and what does this error message mean? I've google it and was honestly surprised to come up with no quality results.
in .gitlab-ci.yml I am using trigger to use different CI configurations.
When running a pipeline, it shows the status as passed even that the downstream pipeline failed.
example:
How can I make the pipeline status to display failed when the downstream pipeline is failing?
i use global variables in jenkins to set build and deploy configuration.
but i want to restrict this variables at only dedicated job.
someone said the Envinjector plugin could do it. so i installed it but i can not find the build configuration like the image below
enter image description here
i use jenkins 2.277.4 version and Envinjector 2.4.0 version
and my job is multibranch pipeline job
below image is my job image
enter image description here
In my failed GitLab Pipeline , there is nothing useful message in the logs ,where can i find more useful message of how the building failed?
I launch a tensorflow task on ML Engine and after about 2 minutes I keep getting an error message "The replica master 0 exited with a non-zero status of 1."
(The task incidentally runs fine with ml-engine local.)
Question: Is there any place or log file where can I see further information on what happened?
The logs viewer just gives the following:
{
insertId: "ibal72g1rxhr63"
logName: "projects/**-***-ml/logs/ml.googleapis.com%2Fcnn180322_170649"
receiveTimestamp: "2018-03-22T17:08:38.344282172Z"
resource: {
labels: {
job_id: "cnn180322_170649"
project_id: "**-***-ml"
task_name: "service"
}
type: "ml_job"
}
severity: "ERROR"
textPayload: "The replica master 0 exited with a non-zero status of 1."
timestamp: "2018-03-22T17:08:38.344282172Z"
}
Thanks in advance for any pointers!
The solution to the apparent lack of log files was missing permission to write to the logs.
Under IAM & admin, adding the Logs Writer role the account cloud-ml-service#<project_id>.iam.gserviceaccount.com solved the problem and enables the master and workers to write log messages to Stackdriver as expected.
For a similar discussion and some additional information, see Stackdriver logs not available for Cloud ML jobs since migration to V2
Thanks to all for giving input!
Stackdriver agents can monitor many metrics and give details about ML engine. For more details, please refer here. AFAIK, Normal event logging and Stackdriver agents are the only tools to monitor the ML jobs on GCP.
Please note that Python 2.7 which is used in Tensorflow works with relative imports. It is possible that you locally used Python 3.4 which worked with absolute imports. That is why it worked locally but not on Google Cloud. You can refer to this post to modify your import statement. So, if you include the line “from __future__ import absolute_import” at the top of your code, before the line “import tensorflow as tf” , your code may work.