dbt cloud status bar issue - dbt

I have a strange dbt behaviour.
When I run models or tests in dbt cloud, some of them passes, some fails. When I click on 'System Logs' dropdown or logs of each models, it shows the result of run and information about the run. The command, which I used (for instance, 'dbt test') also marked as completed. But on the status bar that maps execution process of each task with its results all the steps of the run are placed only in queue tab.
What's the problem?

Related

Viewing test results for a failure on bamboo

I run the test on bamboo with selenium technology and the test tab does not show the test failure, how I can view the test failure?
To see test results (including info which test caused fail) you need to add proper parser task to your job. There are many available parser tasks i.e. JUnit Parser, NUnit Parser, TestNG Parser.
The important thing is to move parser task under Final tasks bar (parser will execute even if previous task fail).
You don't have any test failures. In fact, no tests were running in this build as you can see in line
0 test in total
You job may have failed for one of 2 reasons:
Actual failure of the job. Check detailed log on Logs tab to see if this is the case
It may have also failed because you configured it to fail when there was no tests (and in this case there was no tests indeed) as we see. The corresponding configuration would look like this:

Post build task not working [Jenkins]

Can someone please help. I am trying to trigger a post-build action using the post-build action plugin. The log text that I inputted is returning false, hence not performing a post-build action. When I don't enter any text, it returns true.
This is a simple freestyle project that should print test if it matches the text
Post build setting
This is the console output returning false
Console output returning false
This is the output with no text
Output with no text
Any help will be appreciated. All I want to do is perform a post-build action depending on if my build fails or passes. Alternate solution is welcomed
Thanks
The root cause is your job has no any log out in Job Build Stage, please see Post build task plugin's help, this plugin will search job build log to find the text you specified in plugin.
A quick way to re-try is add a Build Step to print out something:
1. Execture shell (if job executed on Linux machine)
2. Execute windows batch (if job execute on Window machine)
A Job configure example:

How to get test history

I have many builds with failed tests.
I learn one test and want to find last build, where this test was succesfully.
How I can find this build or how I can get test results history?
If as a post-build step you are publishing your test results, you should be able to go to the job page and see the test results graph. If you are looking for the last build where all tests passed, you can click on "enlarge" under the graph. You will then see a high level view of all the builds from which you should be able to see the last build where all tests passed.
If you are looking for the last time a particular test passed, you can click on the latest build in the test results graph, drill down to the particular test you are interested in, and then click the previous build button until you find a build where that test passed.
If you aren't publishing your test results, you may be able to write some groovy code to scan through your build results, but beyond that I don't know of a way to find what your looking for without publishing test results in your post-build.

Different test results from Instrument and command line

I have a automated test script written in UIAutomation. If I run it from the Instrument, all tests are passed. If I run it from the command line, one of the test case will fail and result in the termination of test script running.
The failing test case is about triggering a UIAActivityIndictor and then show an Alert window.
I did some search online, and people are saying that the command line is faster than the Instrument. Sometimes, you need to make sure the UIAElement is valid. However, in my case, at that test case, it seems the command line lost the UIAElements hierarchy of the app. The result of logElementTree is only the target and the app, no window at all. And the UI seems frozen.
Any suggestions would be helpful.
I faced with similar issues. When UI is completely frozen it means that application has been put in infinite loop. In my case NSLog with huge output was the cause. To check that:
1) put really big sleep at some point in your script
2) run the script
3) attach xcode to the app: debug->attach to a process->your app's process
4) wait until freeze happen. Make sure of it manually
5) in xcode press pause execution
6) now you can see in stacktrace where the app is hanging

Kettle: Run in Repository with Preview of execution

This is my Transformation
Run in local gives me a good log and allows me to Preview results of a step. (eg what went wrong and where, what data do I have in each step)
When I run it in Repository, it just gives me a link to check status, where logs are present BUT text only and I cannot Preview Data in each step.
Is there any way to get this? (I also have a Carte server running, my code call it to run, but for debugging I need to run from Kettle UI)