enter image description here
'dbt run' get stuck, and when I check the running queries in the database, there's nothing. It suddenly stops without any error messages.
When I try to run each model alone using 'dbt run --select model' it works.
Please help
Related
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?
I am trying to run a selenium script and the application also runs fine. But in some case all a sudden application goes down and this can happens at any stage of run the script.
So how to handle this because if Application goes down An Error page opens up and in script i may be trying to click a button or verifying something which doesn't happen and throws a exception.
Looks like its an application issue. You need to report the issue. Also it looks like you need to improve your infrastructure so that your application can run smoothly.
No recommaned: If you need to test it anyway, please add Thread.sleep(2000) after click() to make script execution slow.
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
While executing PhantomJS from a Jenkins job, I get regularly error codes 255 as follows :
20140804 18:43:55.362,10,SEVERE,"Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (PhantomJS Unit Test) on project XXXXXX: Command execution failed. Process exited with an error: 255 (Exit value: 255) -> [Help 1]",hudson.maven.Maven3Builder$MavenExecutionListener,
I ran Maven in debug mode, but I could not get more information. The issue appears after all tests have been run. There is one single failure, but the build is not supposed to fail.
Have you experienced this behavior ? What might be the cause for error code 255 and how to fix it ?
Thank you in advance !
I've finally found the problem and the solution.
One of our teams wrote a custom jasmin test runner for phantom.js which was calling phantom.exit(-1) with no log message under specific circumstances. As values not within [0-255] range are illegal from the point of view of phantomjs, it was exiting with an error code 255. We added log messages and changed the return code and now everything's fine.
Hope this helps.
Im using Resque + RedisToGo for my background jobs. I am having trouble running background tasks on Heroku. Its strange because, the first time I run a background job, it gets executed without any issues. But when I run it again, it doesnt execute. I would have to run "heroku restart', every other time for a background to complete successfully....
For example. If I have the following code in my Resque background action:
module EncodeSong
#queue = :encode_song
def self.perform(media_id, s3_file_url)
puts 'foobar'
media = Media.find(media_id)
puts 'media id is supposed to be here'
puts media.id
puts s3_file_url
end
end
In "heroku console", I do:
Resque.enqueue(EncodeSong, 26, 'http://actual_bucket_name.s3.amazonaws.com/unencoded/users/1/songs/test.mp3')
In "heroku logs", I can see the 4 "puts", when I run the above code for the first time. But running it a second time, only returns 'foobar'. The other "puts" are not displayed.....
I suspect that it is not able to run "media = Media.find(media_id)", the second time around. This is only happening on the production server on Heroku. On our local development machine, we do not experience this problem.... Anyone know what is wrong?
PS. I have tried enabling Heroku logs, but still don't get any useful response. I have followed this tutorial to set up Heroku with Resque
Seems like your job is failing (probably you're right about the 'media = Media.find' line). Look through the resque admin interface. Look for failed jobs, there you'll find the backtrace of each failed job.
Hope this helps.