The code always stops at 60%
Everytime I run this pre-processing code, it will stuck at 60%. Then, I cannot open another session when I click the "ssh" near the instance in the window only if I cancel the session for this crashed running code.
Also, if I use local ubuntu to connect this remote GCE, it will also stuck at 60% and when I open another terminal to conncect the GCE, it will show "ssh_exchange_identification: read: Connection reset by peer".
Hope someone can help me, I would really appreciate your help. Thanks a lot!
Related
I have a test that run 30 times open & close a sub-webpage. And if I manually close and reopen, the web app runs okay, no issues at all.
If I use TestCafe to close and reopen for 30 times, I have error on the browser after around 20 times:
Error code: out of memory. like the screenshot shows.
And this will make my test hang then disconnect. I wonder is there any difference on TestCafe when storing & removing cache? Has anyone encountered or know about this issue?
Any help is really appreciated!
It can depend on the environment (website, operation system, hardware, etc.). If it can be reproduced on any machine, please submit an issue to the TestCafe repository.
I have made sure that the mac does not sleep by adjusting the settings in the system preferences. Jenkins will start the test on a schedule, the browser comes up but the test fails because the page is blank.
The same test works with no problem if the mac is unlocked or the screen save is not up.
I cannot leave the mac unlocked because the test runs at night and its a security issue.
Has anyone encountered this issue? And have a solution. Please share.
Attaching some logs. This image will give an idea of what I am describing.
You can try to run tests on locked computer when:
you set your display never turn off, when you lock your computer
you made sure, that computer never goes in hibernate or sleeping mode
If it will not work you can use two more possibilities:
run your tests on headless browser. Here is a pretty good explanation how to do it.
run your tests on a remote screen via VNC or RDP
EDIT:
You can try not lock the screen, but instead start the screensaver, and require the screensaver to immediately require a password.
I'd like to boot VirtualBox to the external hard drive I have that runs Windows 8 To Go, as the computer running virtual box is one that I can't boot to the drive during certain hours, but I'd still like to be able to interact with the OS on that drive.
I found a guide for creating a raw VM DK disk file for my external drive, and ran the commands for it in an administrator command prompt, which was listed as a requirement in the article I was reading.
At first, I'd boot to the drive with my VirtualBox machine, and it would ask me to enter the BitLocker encryption password.
I'd enter it, and before the spinning circles of the Windows loading logo would make a complete rotation, VBox would give me an error popup saying "Error: VERR_ACCESS DENIED".
I researched the issue a bit online and found that some users had resolved this issue by turning on 'Use host I/O cache' on the VirtualBox Storage controller.
I tried this, and the machine did indeed make it farther and stopped displaying an error message, only now it stays on the windows loading screen indefinitely, or may even restart itself.
I checked the log file and am seeing several non-displayed error messages of 'VERR_ACCESS DENIED".
Running virtual box itself as an administrator has had no effect.
Has anyone else tried this successfully? Does anyone have any tips?
I'd appreciate productive suggestions instead of criticism against 'why' I'm doing something.
Thank you!
I'm using the karma-script-launcher to open a virtual machine/browser/url but when the tests are complete I don't know how to close everything.
If I leave the browser open in the virtual machine it eventually stops trying to reconnect - no error message just fails to reconnect. I'm not sure if this is a bug or not. I can't see why you wouldn't want the browser indefinitely trying to reconnect? What ever the reason it leaves me needing to close and re-open the browser each time I run the tests. But if I'm using the script launcher I don't see how this is possible.
Thanks for any help
not quite sure if this covers your answer but I stumbled over your question while looking for a solution to a similar issue, so let me explain - in case someone else encounters this issue.
Was running karma unit tests on codeship ci environment for a nodejs app.
Tests were successful, however the test would keep watching and wouldn't shut down, thus setting the tests to 'passed' - instead it would idle and after a while timeout, setting the tests to 'failed'.
Setting the option singleRun to true within the karma config helped.
Hope this helps anyone who's having the same issue.
Sorry if not topical enough :S
This is been making my programming really frustrating lately.
I´m in Argentina right now connecting to a U.S. server via SSH. Understandably, the pings are a bit higher here (around 200ms on average) so when I SSH into the server there is a slightly noticeable lag between each keystroke. This is fine and easy enough to work with.
What isn´t easy to work with is that about every 5 minutes or so, SSH will completely hang and take about 3-5 minutes to return back a prompt. I know the server is not bogged down because I can easily open several new connections while I´m waiting for one to return (in fact this is the only way I´ve been able to work). And when SSH finally comes back I can see it has actually been working away in the background (large file downloads was a good way to test this) but it just hasn´t been updating my screen.
Does anyone have an idea what might be causing this?
Few other facts: the server is Ubuntu and I'm connecting with Mac OS X. I have keepalive turned on in the SSH settings. It is most likely to hang when I hold down a key (for example a left or right arrow to scroll) which sends a lot of keys quickly. In fact I can reliably reproduce the hang by logging in and holding down any key like "a" - it never makes it past a full line of "a"'s before hanging. This just started when I connected internationally for the first time so I´m assuming it has something to do with that (latency?) but can´t say for sure.
Odd. I can't help you with your problem but I have a tip to make it less annoying: Use screen(1). This will keep your shell on the other end alive and you can continue whatever you were doing after reconnecting.
If you only need to run a command on the other side, I suggest to pass the command as an option to ssh (it will connect, run the command, display the result and disconnect).
I think it was some problem with the ISP down here in argentina. When I switched to another wireless network with another ISP it started working. They are probably playing some port throttling games or who knows what.
Try adjusting your TCP window size.
I'm used to ssh over high latency links - 600ms. It is slow but I rarely had any problems. To start with - open another terminal window, ping your server and watch the connection. Tell us what you see.
Try sshing in with a few verbose flags (ssh -vv[vv] somehost) and seeing if there's anything indicative printed around the time it hangs.
Well, I am now connected to a different wireless network and the problem seems to have disappeared. I can't say for sure what exactly was causing it (and I don't have login access to the wireless router) but this seems to suggest it was something on the router, and not the server or client computer.
Both the old router and the new router were Linksys WRT54G's so I'm not sure what the problem was. Hope it helps someone!
I was having a similar problem with 'cat' and even 'ls -l' causing ssh to hang (on Ubuntu). Adjusting MTU size to 1400 fixed it for me.