test-prof | Ruby Tests Profiling Toolbox | Monitoring library

I've just found where was the error. If there is someone, with the same problem, this post might help you. I solved the problem by deleting assimp (I am not sure which version was that, but I cloned the repo from github a few months ago), and then I added newer version. After that I don't have a problem mentioned in my previous post. Now mWeights in mBones is populated with data, compared to screenshot I left in the question above.

For anyone who's wondering: You can fix this by adding a few variables to your CI/CD configuration.

The ones I added were:

I have found the problem.

So I have found the issue. In angular.json file i have 2 projects both have the test block configured and that was causing it to run twice. Removing the last project test block resolved it. Not sure how Angular 4 was running the TDD only once while with the same configuration Angular 7 run it twice.

Based on issue Karma 1.6 breaks Headless support for Chrome created on github, it is related to the slower machine and happens, because it took > 60 seconds before test bundle was parsed and executed by Chrome and therefore test run was started and communicated back to Karma server. Reasons why it may take long vary.

There are 2 ways to handle timeout:

Investigate why your test bundle loads >60 seconds and make sure it loads faster.

1. Increase browserNoActivityTimeout to highter value, so test bundle has enough time to load.
2. This particular appearance of timeout does not seem to be a Karma issue, but rather problem in the project or misconfiguration.

Based on the Derek's comment

There was a connection that was disconnecting too soon.

He found that in /static/karma.js, when the socket was created, there was a timeout value that is hardcoded to 2 seconds (see below). He just added another 0 to make it 20 seconds and the connection stayed open long enough for the server to respond to the initial request. karma/client/main.js

Lines 14 to 20 in e79463b

Same documentation also includes a section for setting up the credentials. Check it out here http://docs.aws.amazon.com/sdk-for-net/v3/developer-guide/net-dg-config-creds.html

It doesn't give an example of setting up the credentials using the appSettings.json file because they don't think it's the right (secure) way to do it.

Here is from the introduction part of the section about setting up the credentials:

Don't put literal access keys in your application, including the project's App.config or Web.config file. If you do, you create a risk of accidentally exposing your credentials if, for example, you upload the project to a public repository.

To make tests use Spring context you need to run them with SpringRunner. In your example you use Parameterized runner, which makes test ignore Spring context and as a result IfProfileValue annotation is being ignored.

Try adding dataType: 'json' into your ajax parameters
You wouldn't need parseJSON I hope.

The final code becomes

Short answer: If your bundle is non-SNAPSHOT then there's no attempt to fetch "newer" released version. For maven each non-SNAPSHOT is immutable.

Longer answer: If by I have to updated some of the bundles you mean mvn clean install new version to your ~/.m2/repository, then it should be picked up by Fuse - assuming that ~/.m2/repository is one of your default repositories - please check org.ops4j.pax.url.mvn PID, org.ops4j.pax.url.mvn.defaultRepositories property.

If however you want Fuse to download newer version of non-SNAPSHOT artifact from some remote repository (Nexus, Artifactory, ...), then a version in local repository is preferred. By default, in Fuse 6.3, this local repository is in $FUSE_HOME/data/repository. There's special option in org.ops4j.pax.url.mvn PID called org.ops4j.pax.url.mvn.updateReleases that allows you to set non canonical Maven behavior to actually update non-SNAPSHOTs.

In fabric mode (which you're using) it's a bit more complex.

There is fabric-agent configuration of maven resolver in io.fabric8.agent PID and org.ops4j.pax.url.mvn.* properties - their meaning is the same as org.ops4j.pax.url.mvn PID and org.ops4j.pax.url.mvn.* properties in standalone mode.

In order to verify how Maven resolution works, you can uncomment these log settings in karaf profile: