Tests that spawn processes hang forever
This started a couple days ago, all tests that we have that spawn processes now hang, the processes never finish and stay hanged up forever.
Were there any environment changes over these past few weeks?
Running the same tests on our local development machines shows no issues.
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Feodor Fitsner on 28 May, 2015 03:35 PM
Hi Mauricio,
The last update was on May 12th: http://www.appveyor.com/updates
Can you remember the exact date it started happening? What testing framework is that? What process do you call? How do you call that process?
- Feodor
2 Posted by mlinhares on 28 May, 2015 03:56 PM
The first failure was 6 days ago, these tests spawn one of our programs.
When running without spawning the code runs fine, when we spawn the process
it always hangs forever at the appveyor environment.
-
Maurício Linhares
Software Engineer - The Neat Company
Support Staff 3 Posted by Feodor Fitsner on 28 May, 2015 04:20 PM
What was the last successful build (project/version)? Have you changed project settings or appveyor.yml since that time?
- Feodor
4 Posted by mlinhares on 29 May, 2015 12:47 PM
No changes to appveyor.yml, the last successful build was the build 1.5.212
of the spi-service repo. Username is neat-appveyor.
-
Maurício Linhares
Software Engineer - The Neat Company
5 Posted by lasse.schuirman... on 29 May, 2015 04:10 PM
We have a similar issue, just with one build however: https://ci.appveyor.com/project/sils1297/coala/build/1.0.242/job/qsoicjoswcgimuoy
It just hang before doing anything. All other builds did build fine. Maybe its related. Please let me know if I need to open a new issue for this to be adressed.
Support Staff 6 Posted by Feodor Fitsner on 29 May, 2015 04:18 PM
I see. This last 1.5.212 successful build was on May 22nd. And you tried to rebuild that
b39aa4288commit but no avail. There were like 16 successful builds between May 12th (the most recent update to workers) and May 22nd. When build worker updated, started and snapshot is made its state is immutable; any updates like Windows updates are disabled.There might be some external dependencies (nuget, npm, bower, etc.) that changed.
Support Staff 7 Posted by Feodor Fitsner on 29 May, 2015 04:20 PM
@Lasse - nope, it's not a similar issue. Looks like some sporadic error.
Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:56 AM.