The test is for our REST API that it returns a bad request if we try to pass missing information to the POST.
As said in title, this works fine locally, it also looks like it's fine when you look at the build log in Team City...
JetBrains.TeamCity.PlatformProcessRunner.v4.0.msil.exe Information: 0 : Response, Status=400 (BadRequest), Method=POST, Url=http://localhost:7447/api/letters, Message='Content-type='application/json; charset=utf-8', content-length=unknown'
But it's showing as a failure and that build step fails :(
The only mention of error I can find in the stack trace is...
------- Stderr: -------
JetBrains.TeamCity.PlatformProcessRunner.v4.0.msil.exe Information: 0 :
That's it.. I'm at a total loss as to what's going wrong here and what to do about it.
It was asp.net API issue. We had the following config being enabled for our unit test projects.
Config.EnableSystemDiagnosticsTracing();
Unfortunately this causes TeamCity to register an error after each test (maybe because we aren’t responding with a 200 status code, but I haven’t tested this bit) with no error information.
Removed this line and it fixed the problem.
Related
Following the ODATA V4 tutorial in step 2: app runs against mockserver, tips are given to run it against a real server. Used the existing index.html as test/mockServer.html and created a new index.html, pointing to ComponentSupport for oninit. Added cors-anywhere and adjusted the manifest. Works well, both mockserver and real.
That was in step 2 and the app worked fine also against a real server. Fast-forward to step 5 and I notice the app fails to load any data when running against a real server. Long story short, the backend is throwing an error, not even "count" together with "top" is accepted. I checked the docs for ODATA, "count" does not seem to be an exclusive option.
Am I fundamentally misunderstanding the way ODATA works? I am especially puzzled by the fact that the mockserver runs fine.
EDIT: created bugreport
As reported in the closing comment of my bugreport, Microsoft has confirmed the issue: "This was due to an error in the version of the OData WebAPI library we were using in the backing service. I have an update with various fixes, including updating to the latest WebAPI library that contains this fix, that I just haven't pushed out to production yet. Let me see when if I can get that deployed."
Got a problem when I followed the tutorial 1 in cyTargetlinker. Every step is smooth until I reached step 4 after I selected "2" for the "overlap threshold" functionality. It gave a sign "Caught exception executing task" with a statement "Untitled (org.cytargetlinker.app.internal.tasks.FilterOverlapTask). I further checked the automation and it stated that there was an error 500 response code. Anyone know how to solve this problem?
I download Cytoscape 3.8.0 and intalled cyTargetLinker app.
Thanks.
An error 500 indicates a problem with the CyTargetLinker web service. I know that some of the web sites at Maastricht have been offline due to a recent hack, but I don't know if that's the problem. You might try e-mailing the App authors (go to http://apps.cytoscape.org/apps/cytargetlinker and click on e-mail).
-- scooter
i tried everything to solve this but since two days i'm blocked.
i need IwNui Api in my application to build interface for my application iOs, but when adding this package to the mkb project with this line 'subproject IwNUI', Visual studio block on this trace error :
Building project: c:/Users/PC/Documents/testaaaa/testaaaa.mkb
1>c:/Users/PC/Documents/testaaaa/testaaaa.mkb(14): warning : filename case does not match the filesystem: c:/marmalade/6.2/modules/IwNUI/IwNUI.mkf
1> Executing: 'c:\marmalade\6.2\s3e\bin\mdev.bat update'
1> Downloading: http://source.madewithmarmalade.com/packages/6.2/Packages
1> Downloading: https://raw.github.com/marmalade/mdev-package-list/master/6.2?1365852339.42
1>CUSTOMBUILD : error : error downloading url: https://raw.github.com/marmalade/mdev-package-list/master/6.2?1365852339.42 (<urlopen error (8, 'EOF occurred in violation of protocol')>)
1>c:/marmalade/6.2/modules/iwutil/iwutil.mkf(19): error : Executing 'c:\marmalade\6.2\s3e\bin\mdev.bat update' failed. (return code 1)
1> FAILED (error code=3)
Even every examples of marmalde launchap which use Iw** api can't be build because the dowload of : https://raw.github.com/marmalade/mdev-package-list/master/6.2?1365852339.42 is not working.
I saw tips on some pages but these not fixed it for me (delete folder in roaming/appdata/marmalade , close firewall, try with old sdk 6.2.1,6.2.0,6.1 etc)
I'm open to every suggestions, my development was going well until i need an UI to going forward. I'm beginner in interface development and if a different and easy way exist for adding a Ios UI i'm also interested in.
Thanks a lot for reading, dams
Marmalade needs the mdev package to function properly, thus you've to download it anyways, there're now way you can skip it. The problem is with your internet connection. Probably it's not accepting HTTPS connections. Try using some other internet provider or check using some friends' wifi. I always get this error when my internet is slow and the download gets timeout. Changing the internet plan is the only thing that might help.
In case it gives the same error on other internet connection, then it might be some issues with how you set up marmalade, Try reinstalling it.
We have a situation where our builds have stopped executing in a stable manner.
At a rate of about one every three we receive either TF215096 or TF215097 errors & the Build fails.
If we then restart the Build controller, it works again - until next time.
The errors we get are:
TF215096: An error occurred while connecting to controller vstfs:///Build/Controller/1: There was no endpoint listening at ht*p://XXXX that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
TF215096: An error occurred while connecting to controller XXX - Controller: Could not connect to ht*p://XXX. TCP error code 10061: No connection could be made because the target machine actively refused it 192.168.XXX.XXX:XXX.
TF215097: An error occurred while initializing a build for build definition \XXX: Team Foundation services are not available from server ht*p://XXX. Technical information (for administrator): The underlying connection was closed: A connection that was expected to be kept alive was closed by the server.
TF215097: An error occurred while initializing a build for build definition \YYY: An error occurred while receiving the HTTP response to ht*p://XXX. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details.
Server logs provide with little info, at least we 've found nothing that helps us resolve the situation. Various searches in the Net were also not productive.
Does anybody had these/similar issues? Any ideas on how/where to look for a resolution?
Thank you very much in advance for any input!
Yeah it does sound like you have some connectivity issues. You can try enabling SOAP tracing on both the build machine and the server (if possible) to see if there is any error. If it still does not give you any new information, contact Microsoft by filing a Connect Bug to get help.
I am not sure if it will help you but I have ran into similar issues with build agents and ended up just deleting and re-creating the agent. You may try deleting your controller/agent and adding it back in. A brute-force solution but a good starting point. If that doesn't resolve the issue at least you can eliminate the controller/agent as the issue and take a look at network/server related issues.
Today is a happy day, since we managed to get to the bottom of the matter. Sorry #Duat that I'm taking away the 'answer' checkmark - but it turned out that the problem was quite different from what you (and anybody else) has predicted.
In my last update I was about to forward the matter to MS, when we realized that our Firewall was misbehaving in the name resolution. So we assumed this was the culprit & awaited for this to resolve. After this was resolved, we STILL had the same issues and we went again re-examining the situation.
We isolated the problem within our Build Process, more specific with a custom code activity included in our build solution.
I had implemented a code activity that would kick in at the final steps of every build. This activity was about gathering BuildDetails about the running build & add them as a new line in a 'BuildLog.xls'. Implementation made use of Microsoft.Office.Interop.Excel.This excel sheet resides in another server (NOT on the Servers where the controller/agents reside).
During development of this activity I was faced with issues like this, but after I was done no instances of EXCEL were left hanging. So I thought this was done & dealt with.
With try & error, we observed that when this activity wouldn't ran, no problems would occur.
With this activity running, the very first build after a build-controller reset would succeed, any next build had a certain chance to fail. Once any build failed, no other would succeed until another build-controller reset.
I have only a general understanding of what the problem was (Excel-call is DCOM, TFS services are WCF : How on earth would they interfere?! Why would this sometimes succeed and sometimes fail?! ).
The provided diagnostics were no help either, in fact they mislead us into a loop that continued for months.
If I ever find the time, I 'd like to cleanly reproduce the error & make a Server Fault question out of it...
After removal of this activity it works! I now searched in SO & found this, where J.Saunders comments: "In general, you should never use Office Interop from a server environment". It's ironic that once you get to the bottom of any difficult issue, the whole universe seems to have known about it except you...
I have a nightly team build that is reporting errors from the test step but zero errors in the summary. This results in a partial success.
alt text http://jonesie.net.nz/content/binary/buildsnip.jpg
I cant see any errors in the full build log but maybe it's just the quantity of warnings??
Anyone got any ideas?
Thanks
The Running tests task failed....if any non-essential task fails, this results in a Partially Succeeded status. Can you post the MSBuild file being used, specifically the Running tests section?
That being said, you should always pay attention to the warnings and resolve them whenever possible...they are warnings for a reason. They often alert you to unintended behavior in your code (e.g. a property that doesn't override properly).
Try searching for the string "error :" in the log file.
MSBuild will automatically generate an error if it sees this string in the output anywhere.
So even if the string happens to be "error : 0" (as in everything is just peachy), MSBuild will still exit with an error!
This issue has also been documented here:
http://social.msdn.microsoft.com/forums/en-US/msbuild/thread/77eb8b02-8cd7-4d32-acad-3ab0dc308d78/