I have a scheduled job that runs every morning, apparently since yesterday something is not going as planned in the job. And it is still running
The job from yesterday is still running (normally it takes about 14 minutes) And the scheduled job from today started too. But this is also running to long
I do not have an option anywhere (i can find) that gives me the option to cancel the running jobs.....
Any one have an idea where I can cancel these jobs?
You can cancel the job by doing the following:
First, go to the job result page (click on the id of the job in cloud dataprep).
Then, you should see a button in top right corner to view the dataflow job.
Click on it.
In the dataflow UI, there is a button to stop the job.
The problem you are experiencing could possibly not be resolved via the normal procedure as 'Hugues' described.
There is a bug in dataprep since 20 june causing dataprep jobs to remain in the status 'in progress' while they are actually finished in dataflow.
Hopefully google will solve the issue soon!
Related
I have recently updated a CircleCI workflow that originally just had a test job, to have an optional deploy step that requires manual approval.
Previously on GitHub, the commit would get a green tick when tests were completed. However, now since there is a pending job in the workflow, it never changes to a tick unless the deploy job is also executed.
Is there any way to specify that I only care about the test job and give a tick once that job is complete, rather than waiting for the entire workflow to complete?
This screenshot illustrates the problem (notice the icon next to the commit sha1 is still "pending"):
Unfortunately this is still not possible in the CircleCI/GitHub integration (April 2022).
You can comment/vote here or here to hopefully help moving this up in priority...
Is there a way to edit a user on a scheduled job in Rundeck? There are jobs scheduled and running but it needs to be edited.
The only way right now is to edit the job with the desired user and save it again. Take a look at this answer.
We are currently checking the test plan module on our Azure Devops server and I'm facing an issue that the community may help.
According to this once a test run has been marked as failed or blocked there is no way to resume the test once the raised defects have been resolved. You either have to mark the test run as paused (so as to be granted the "resume" option) or reset the whole test to active in which case you loose all your progress and need to start over. Two questions:
This "workaround" works as long as you are careful and save the test run as paused. Otherwise if a failed step exists the run is saved as failed. Once this is done I have found no way of changing it to "paused" so as to get the resume option. Is there a way I'm missing?
In the test list under a specific suite you get the current test run outcome and state of test case. In case of "Paused" you don't have a way to know if the test execution is paused or you are utilizing the aforementioned workaround (e.g. a bug is registered). I cannot see a way that I could enhance the test run with some information that would signal this (there is no wit template I have found) on the grid. So is the standard query module (bringing testcases and associated bugs with state) the only way?
thanks
For the first question, if the test case is on status Failed and you retest the test case, all test steps need to be redone. Also there is no resume-button. This is by design. For now, set the status to Paused can resume the test, but it cannot truly reflect the result. As far as I know, there is no other way.
You could add your request for this feature(For example: when status = Failed/Block, the restore button is enable) on our UserVoice site , which is our main forum for product suggestions.After suggest raised, you can vote and add your comments for this feedback. The product team would provide the updates if they view it.
For the second question, as workaround , you can also add tags to paused test cases for labeling.
My understanding is if the bug was in Activity, the new code will be used since Activity does not have the concept of version. But what if there is a bug in Workflow code and causing some workflows to fail (or even worse, not fail but stuck), we fixed the bug and deployed the new version, but those failing workflows are stuck on old versions. Is there a way to automatically move those failed / stuck workflows to new version and re-run them?
This happening a lot to us because we just started to learn to use Cadence/Temporal
Thank you in advance!
It depends on the bug.
For bugs that cause workflow to get stuck (in Go a nil pointer dereferencing causes panic which blocks the workflow progress by default) deploying the new version of the code is usually enough to unblock them.
If the bugfix requires backwards incompatible change then the best option would be to reset workflow to the point before the bug. This way workflow will be rolled back and continue through the new code.
For situation when the breakage of workflow code is caused by a new bad build you can rollback the workers to the previous build and mark that build as broken and all workflows going to roll back their state to before that build automatically. See "Recovery from bad deployment" section of the Temporal documentation.
If you are using ElasticSearch integration then you can also perform batch reset of multiple workflows using a predicate to select workflows that match some criteria. See "Signal, cancel, terminate workflows as a batch job" section. Besides the name of the section the batch jobs apply to reset operations as well.
I did some tests with Actions on Google but it was with the wrong account so I deleted the project. Once I created the new one with the good account, I discovered that the invocation isn't deleted so I can't use it anymore.
Did I miss something to get it completely deleted?
I've received the mail about the 24h hour to recover the project but it's been more than 24h now.
This happened to me. Support told me that there was a way to "undo" the project deletion and once un-deleted I could change the name so that the old one could be re-used. I forget the details but that option wasn't available for me. They told me I could wait a month or so until the project was physically deleted from their cloud or I could submit a ticket to delete it and wait a week. That's what I did.