markparz (Thu, 02 Feb 2017 23:34:46 GMT):
Autogenerated messages of Fabric builds
salmanbaset (Fri, 03 Feb 2017 01:20:52 GMT):
Has joined the channel.
yacovm (Fri, 03 Feb 2017 01:43:44 GMT):
Has joined the channel.
JonathanTan (Fri, 03 Feb 2017 01:52:39 GMT):
Has joined the channel.
grapebaba (Fri, 03 Feb 2017 02:21:59 GMT):
Has joined the channel.
cbf (Fri, 03 Feb 2017 06:32:20 GMT):
Has joined the channel.
cca88 (Fri, 03 Feb 2017 08:19:01 GMT):
Has joined the channel.
dave.enyeart (Fri, 03 Feb 2017 11:19:21 GMT):
Has joined the channel.
jdockter (Fri, 03 Feb 2017 11:37:50 GMT):
Has joined the channel.
silliman (Fri, 03 Feb 2017 13:55:57 GMT):
Has joined the channel.
gormand (Fri, 03 Feb 2017 14:25:01 GMT):
Has joined the channel.
ssaddem (Fri, 03 Feb 2017 15:51:19 GMT):
Has joined the channel.
rameshthoomu (Fri, 03 Feb 2017 18:16:14 GMT):
Has joined the channel.
jimthematrix (Fri, 03 Feb 2017 19:37:22 GMT):
Has joined the channel.
karkal (Fri, 03 Feb 2017 19:51:59 GMT):
Has joined the channel.
bsmita (Fri, 03 Feb 2017 20:03:37 GMT):
Has joined the channel.
SriramaSharma (Sat, 04 Feb 2017 01:30:45 GMT):
Has joined the channel.
bryanhuang (Mon, 06 Feb 2017 04:37:54 GMT):
Has joined the channel.
ray (Mon, 06 Feb 2017 04:43:54 GMT):
Has joined the channel.
david.peyronnin (Mon, 06 Feb 2017 09:47:53 GMT):
Has joined the channel.
weeds (Mon, 06 Feb 2017 20:23:30 GMT):
Has joined the channel.
binhn (Tue, 07 Feb 2017 02:51:16 GMT):
Has joined the channel.
crazybit (Tue, 07 Feb 2017 05:32:42 GMT):
Has joined the channel.
yacovm (Tue, 07 Feb 2017 09:37:26 GMT):
Is there a problem with CI?
https://jenkins.hyperledger.org/job/fabric-verify-x86_64/6259/console
kenzhang (Tue, 07 Feb 2017 14:34:46 GMT):
Has joined the channel.
umasuthan (Tue, 07 Feb 2017 16:05:54 GMT):
Has joined the channel.
harrijk (Tue, 07 Feb 2017 19:28:27 GMT):
Has joined the channel.
patchpon (Wed, 08 Feb 2017 01:15:57 GMT):
Has joined the channel.
mbaizan (Wed, 08 Feb 2017 14:25:57 GMT):
Has joined the channel.
jkirke (Wed, 08 Feb 2017 16:34:04 GMT):
Has joined the channel.
yacovm (Wed, 08 Feb 2017 21:48:04 GMT):
```
21:44:52 The TEST_PKGS variable is not set. Defaulting to a blank string.
21:44:52 Creating unittest_vp_1
21:44:54 Creating unittest_unit-tests_1
21:44:57
21:44:57 ERROR: for unit-tests Cannot start service unit-tests: Cannot link to a non running container: /unittest_vp_1 AS /unittest_unit-tests_1/unittest_vp_1
21:44:57 Encountered errors while bringing up the project.
21:44:57 Makefile:103: recipe for target 'unit-test' failed
21:44:57 make: *** [unit-test] Error 1
```
Seems like this happens 2 times in a row in https://gerrit.hyperledger.org/r/#/c/5715/
yacovm (Wed, 08 Feb 2017 21:48:16 GMT):
@rjones any known issues or just bad luck?
rjones (Wed, 08 Feb 2017 21:48:16 GMT):
Has joined the channel.
yacovm (Wed, 08 Feb 2017 21:48:21 GMT):
@aso
aso (Wed, 08 Feb 2017 21:48:21 GMT):
Has joined the channel.
rjones (Wed, 08 Feb 2017 21:48:50 GMT):
no known issues.
aso (Wed, 08 Feb 2017 21:54:23 GMT):
@rjones any obvious reason why the CI run keeps failing here? https://gerrit.hyperledger.org/r/#/c/5715/
rjones (Wed, 08 Feb 2017 21:55:45 GMT):
@aso there is still no known reason that depends on ci infra that causes that particular build to fail.
aso (Wed, 08 Feb 2017 21:56:20 GMT):
fair enough - thx, I'll dig deeper
rjones (Wed, 08 Feb 2017 21:59:54 GMT):
@aso looking here at the sea of red: https://jenkins.hyperledger.org/job/fabric-verify-x86_64/ I would guess master is broken
aso (Wed, 08 Feb 2017 22:00:16 GMT):
aha....
aso (Wed, 08 Feb 2017 22:01:00 GMT):
yeah, that would explain it
aso (Wed, 08 Feb 2017 22:01:07 GMT):
and.. ouch
rjones (Wed, 08 Feb 2017 22:03:19 GMT):
that's only a guess on my part, but it is an informed guess
yacovm (Wed, 08 Feb 2017 22:03:31 GMT):
@aso 's patch builds on my machine
rjones (Wed, 08 Feb 2017 22:03:46 GMT):
on the tip of master?
aso (Wed, 08 Feb 2017 22:03:54 GMT):
yeah but the `unit-test` makefile target is broken on my machine as well
yacovm (Wed, 08 Feb 2017 22:04:06 GMT):
hmmm
yacovm (Wed, 08 Feb 2017 22:04:09 GMT):
good point
rjones (Wed, 08 Feb 2017 22:04:20 GMT):
do some `git blame`
yacovm (Wed, 08 Feb 2017 22:04:39 GMT):
let me run `make unit-tests` first
yacovm (Wed, 08 Feb 2017 22:05:41 GMT):
```
yacovm@yacoVM ~/OBC/shared/gopath/src/github.com/hyperledger/fabric (master) $ make unit-tests
mkdir -p build/image/peer/payload
cp build/docker/bin/peer peer/core.yaml build/msp-sampleconfig.tar.bz2 build/genesis-sampleconfig.tar.bz2 build/image/peer/payload
cd unit-test && docker-compose up --abort-on-container-exit --force-recreate && docker-compose down
Creating unittest_vp_1
Creating unittest_unit-tests_1
Attaching to unittest_vp_1, unittest_unit-tests_1
vp_1 | WARNING: no logs are available with the 'none' log driver
unit-tests_1 | Obtaining list of tests to run for the following packages: github.com/hyperledger/fabric/gossip/...DONE!
unit-tests_1 | Running tests...
unit-tests_1 | ? github.com/hyperledger/fabric/gossip/api [no test files]
```
aso (Wed, 08 Feb 2017 22:05:50 GMT):
oh...
aso (Wed, 08 Feb 2017 22:05:55 GMT):
and what's your git head?
yacovm (Wed, 08 Feb 2017 22:06:09 GMT):
```
Merge: 9011c66 7ef83d0
Author: Srinivasan Muralidharan
yacovm (Wed, 08 Feb 2017 22:23:39 GMT):
Also I did in a vagrant environment- pulled latest master and `make dist-clean unit-tests` and it works...
rjones (Wed, 08 Feb 2017 22:30:24 GMT):
rebase to tip of master then?
baohua (Thu, 09 Feb 2017 03:03:30 GMT):
Has joined the channel.
baohua (Thu, 09 Feb 2017 03:04:04 GMT):
Hi, anyone can help look at this ci build? Seems some container cannot start, but do not show any reason. Thanks https://jenkins.hyperledger.org/job/fabric-verify-x86_64/6350/console
baohua (Thu, 09 Feb 2017 03:04:18 GMT):
The patchset is at https://gerrit.hyperledger.org/r/#/c/5701
harrijk (Thu, 09 Feb 2017 04:17:53 GMT):
@baohua It looks like the peer container failed to start possibly due to your environment variable change.
harrijk (Thu, 09 Feb 2017 04:19:54 GMT):
`make unit-test` issues a docker-compose up command that starts a fabric-peer container and a test-env container.
harrijk (Thu, 09 Feb 2017 04:20:33 GMT):
So if either container cannot be started the `make unit-test` command will fail
baohua (Thu, 09 Feb 2017 05:49:49 GMT):
@harrijk Thanks. Could u point out why it's failed? Do not see any clue. And it passed in my local server :(
baohua (Thu, 09 Feb 2017 05:56:03 GMT):
aha, know what happens, will fix it, thanks!
aso (Thu, 09 Feb 2017 08:18:49 GMT):
any news @baohua ?
baohua (Thu, 09 Feb 2017 08:19:45 GMT):
about the ci error? @aso
aso (Thu, 09 Feb 2017 08:20:18 GMT):
yup
baohua (Thu, 09 Feb 2017 08:33:14 GMT):
Has fixed with rebasing to latest code :)
aso (Thu, 09 Feb 2017 08:55:06 GMT):
not for me...
aso (Thu, 09 Feb 2017 12:10:14 GMT):
so, I'm not sure what I'm doing wrong but... I've rebased https://gerrit.hyperledger.org/r/#/c/5715/ on the latest ,master and it still won't build
baohua (Thu, 09 Feb 2017 12:45:50 GMT):
yes, maybe try to build locally to see if can find more clues. Sometimes, the given log has limited info.
rameshthoomu (Thu, 09 Feb 2017 16:50:40 GMT):
@greg.haskins @rjones : @cbf and @mastersingh24 agreed to publish hackfest v1.0 images to hyperledger dockerhub tagged as v1.0.0-preview.
mastersingh24 (Thu, 09 Feb 2017 16:50:40 GMT):
Has joined the channel.
greg.haskins (Thu, 09 Feb 2017 16:50:40 GMT):
Has joined the channel.
greg.haskins (Thu, 09 Feb 2017 16:52:33 GMT):
im not sure what that means, but if it involves pushing image out manually verses going through the release pipeline, I would discourage it
rameshthoomu (Thu, 09 Feb 2017 16:55:08 GMT):
We have release jobs to publish images based on tag but not on a specific commit..
greg.haskins (Thu, 09 Feb 2017 16:55:19 GMT):
i understand
greg.haskins (Thu, 09 Feb 2017 16:55:30 GMT):
you wouldnt want to release on a commit anyway
greg.haskins (Thu, 09 Feb 2017 16:55:41 GMT):
ive covered this before, but if you want to do this right:
greg.haskins (Thu, 09 Feb 2017 16:55:58 GMT):
cut a branch at the commit you want, push a release CR on that branch, tag it, done
greg.haskins (Thu, 09 Feb 2017 16:56:07 GMT):
thats the right way, and the way I would advise
greg.haskins (Thu, 09 Feb 2017 16:56:52 GMT):
also note that the branch name should reflect that its a stream, not a tag
rameshthoomu (Thu, 09 Feb 2017 16:57:19 GMT):
agree.. @cbf and @mastersingh24 inputs please?
greg.haskins (Thu, 09 Feb 2017 16:57:38 GMT):
e.g. branch names like v1.0.0-preview and tags like v1.0.0-preview-1, v1.0.0-preview-2, etc
greg.haskins (Thu, 09 Feb 2017 16:57:56 GMT):
long story short, branch name should not == tag name...tags are a subset
greg.haskins (Thu, 09 Feb 2017 16:59:07 GMT):
but that said, I would also discourage releasing from that older release, much progress has been made
greg.haskins (Thu, 09 Feb 2017 16:59:18 GMT):
theres a little wiggle room given "preview" name though
greg.haskins (Thu, 09 Feb 2017 16:59:40 GMT):
but, for instance, I would like to see the FAB-678 support be included
greg.haskins (Thu, 09 Feb 2017 16:59:52 GMT):
otherwise, those artifacts will not be that interesting to many use cases
greg.haskins (Thu, 09 Feb 2017 17:01:16 GMT):
im more flexible on that, but pls do not put adhoc images out there
greg.haskins (Thu, 09 Feb 2017 17:01:20 GMT):
thats really bad
cbf (Thu, 09 Feb 2017 17:39:13 GMT):
@greg.haskins may need to wait til I get settled with wifi but this image is already 'out there' just not in hyperledger org. We had to do some things to get it bootstrapped which is not in the codebase. The point is to get something in dev hands rather than waiting for 2-3 weeks.
cbf (Thu, 09 Feb 2017 17:39:36 GMT):
@mastersingh24 ^^
greg.haskins (Thu, 09 Feb 2017 17:40:13 GMT):
i just think there is a difference between something that is "out there" and something that is available under hyperledger/fabric
greg.haskins (Thu, 09 Feb 2017 17:40:47 GMT):
ideally, anything that is there can be repeatably built from source and referred back to, etc
greg.haskins (Thu, 09 Feb 2017 17:41:20 GMT):
the sane way to do that is a matching tag created from a release pipeline
greg.haskins (Thu, 09 Feb 2017 17:42:24 GMT):
I dont think it will be hard to produce a release from the referenced commits that @rameshthoomu is referring to
greg.haskins (Thu, 09 Feb 2017 17:42:37 GMT):
so, that is how I would advise we proceed
greg.haskins (Thu, 09 Feb 2017 17:50:41 GMT):
another argument would be w.r.t. $arch support, etc
greg.haskins (Thu, 09 Feb 2017 17:51:07 GMT):
pushing it through the pipeline will result in a repeatable process and a full suite of images for all architectures, etc
greg.haskins (Thu, 09 Feb 2017 17:51:31 GMT):
I dont think this will be hard, we have all the plumbing already in place
greg.haskins (Thu, 09 Feb 2017 17:54:13 GMT):
basically, we need a list of the commits from each repo we want to release from @rameshthoomu, the agreement of what the branch/tag name should be from all of us, the creation of said branches at the commit by @rjones: and then minimally pushing the release-related CRs and tags by me
greg.haskins (Thu, 09 Feb 2017 17:54:30 GMT):
(or anyone, but I am willing to drive it)
rameshthoomu (Thu, 09 Feb 2017 18:04:37 GMT):
@greg.haskins : here are the commits for `fabric# c7b3fe0` and `fabric-ca# 6294c57` (commits used in hackfest images)
greg.haskins (Thu, 09 Feb 2017 18:05:10 GMT):
ok, phase 1 complete: phase 2 (names)
greg.haskins (Thu, 09 Feb 2017 18:05:25 GMT):
v1.0.0-preview branch, v1.0.0-preview-1 release tag?
rameshthoomu (Thu, 09 Feb 2017 18:07:27 GMT):
looks good to me.. but others inputs?
rameshthoomu (Thu, 09 Feb 2017 18:07:53 GMT):
I am working on creating ca job to publish ca images..
greg.haskins (Thu, 09 Feb 2017 18:08:34 GMT):
ok, but going forward, we should make the CI integration just be something like "make docker-release"
greg.haskins (Thu, 09 Feb 2017 18:08:54 GMT):
and let the local build decide what that constitutes
rameshthoomu (Thu, 09 Feb 2017 18:09:50 GMT):
sure I will work on that later
rameshthoomu (Thu, 09 Feb 2017 18:11:24 GMT):
@rjones could you please create a new repository for fabric-ca image in docker hub.. `hyperledger/fabric-ca`
greg.haskins (Thu, 09 Feb 2017 18:11:27 GMT):
ok...we can make that universal across the repos
rameshthoomu (Thu, 09 Feb 2017 18:11:42 GMT):
yes..
greg.haskins (Thu, 09 Feb 2017 18:12:26 GMT):
but this is a good highlight why the process I mention above should be followed
greg.haskins (Thu, 09 Feb 2017 18:12:43 GMT):
if fabric-ca.git needs a mod to support pushing to dockerhub, we can do it as a CR in that branch
greg.haskins (Thu, 09 Feb 2017 18:14:18 GMT):
IOW, its very rare that a random commit-id would make a suitable release...you usually minimally need to update the version numbers, etc
bmos299 (Thu, 09 Feb 2017 20:31:30 GMT):
Has joined the channel.
rjones (Thu, 09 Feb 2017 21:04:19 GMT):
@rameshthoomu https://hub.docker.com/r/hyperledger/fabric-ca/
rjones (Thu, 09 Feb 2017 21:04:34 GMT):
I apologize for the delay, I was on the road all morning
rameshthoomu (Thu, 09 Feb 2017 21:09:03 GMT):
Thanks ry
binhn (Fri, 10 Feb 2017 17:14:57 GMT):
@rameshthoomu something is wrong with CI - CR verification failed with
```
17:00:33 --2017-02-10 17:00:33-- https://jenkins.hyperledger.org/job/fabric-verify-x86_64/6577/consoleText
17:01:13 Resolving jenkins.hyperledger.org (jenkins.hyperledger.org)... failed: Temporary failure in name resolution.
```
rjones (Fri, 10 Feb 2017 17:49:50 GMT):
@binhn which change?
binhn (Fri, 10 Feb 2017 17:51:03 GMT):
https://gerrit.hyperledger.org/r/#/c/5509 tried to reverify -- it's been 2 days now
rameshthoomu (Fri, 10 Feb 2017 17:53:35 GMT):
above issue could be a network issue.. Observed similar error in other builds.. Now every thing seems working fine..
rameshthoomu (Fri, 10 Feb 2017 17:54:57 GMT):
`[91mW: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/InRelease Temporary failure resolving 'archive.ubuntu.com'`
rameshthoomu (Fri, 10 Feb 2017 18:08:27 GMT):
@greg.haskins : fabric-ca release jobs are ready and we have repository available for ca images in dockerhub.
rameshthoomu (Fri, 10 Feb 2017 18:42:55 GMT):
also I have updated `sfhackfest` folder referring to hyperledger docker images..PS https://gerrit.hyperledger.org/r/#/c/5617/ (WIP). Once images are published to docker hub will request for merge..
greg.haskins (Fri, 10 Feb 2017 18:51:28 GMT):
@rameshthoomu ok, we just need to agree on the branch name, have @rjones create them, and then we can start the CR process
greg.haskins (Fri, 10 Feb 2017 18:51:49 GMT):
did we decide on "v1.0.0-preview"
greg.haskins (Fri, 10 Feb 2017 18:52:12 GMT):
(I assume only @rjones can create them)
greg.haskins (Fri, 10 Feb 2017 18:52:15 GMT):
maybe that is not the case
rjones (Fri, 10 Feb 2017 18:52:20 GMT):
any committer may create them
greg.haskins (Fri, 10 Feb 2017 18:52:26 GMT):
ah, ok, my bad, sorry
greg.haskins (Fri, 10 Feb 2017 18:52:42 GMT):
still need consensus on the name, though
rjones (Fri, 10 Feb 2017 18:52:50 GMT):
no apology required! it's confusing
greg.haskins (Fri, 10 Feb 2017 18:52:59 GMT):
yeah, i might need guidance on how
greg.haskins (Fri, 10 Feb 2017 18:53:10 GMT):
can I just say "refs/for/foo" to create "foo" ?
rjones (Fri, 10 Feb 2017 18:54:49 GMT):
not sure, try it in lf-sandbox? anyway, I usually do it in the UI (https://gerrit.hyperledger.org/r/#/admin/projects/fabric-chaintool,branches for instance)
rjones (Fri, 10 Feb 2017 18:55:05 GMT):
if you're logged in, do you see a "create branch" button?
rjones (Fri, 10 Feb 2017 18:55:36 GMT):
I'm about 75% certain if you, as a committer, created and pushed a branch, it would show up.
greg.haskins (Fri, 10 Feb 2017 18:56:36 GMT):
ah, yes I do
greg.haskins (Fri, 10 Feb 2017 18:56:53 GMT):
I see the button for sure...i can use that worst case
greg.haskins (Fri, 10 Feb 2017 18:57:03 GMT):
ill try the refs/for method too when the time comes, just to see
greg.haskins (Fri, 10 Feb 2017 18:57:12 GMT):
actually i guess I can try it against sandbox
greg.haskins (Fri, 10 Feb 2017 18:58:52 GMT):
```Greg:lf-sandbox ghaskins$ git push origin HEAD:refs/for/branch-test
Total 0 (delta 0), reused 0 (delta 0)
remote: Processing changes: refs: 1, done
To ssh://gerrit.hyperledger.org:29418/lf-sandbox
! [remote rejected] HEAD -> refs/for/branch-test (branch branch-test not found)
error: failed to push some refs to 'ssh://greg.haskins@gerrit.hyperledger.org:29418/lf-sandbox'```
greg.haskins (Fri, 10 Feb 2017 18:58:58 GMT):
nope, but this is actually a good thing
greg.haskins (Fri, 10 Feb 2017 18:59:18 GMT):
would be easy to do something like "refs/for/mister" by accident
greg.haskins (Fri, 10 Feb 2017 19:00:36 GMT):
but since we have a few acks for "v1.0.0-preview" and no nacks, i can just go ahead and put them through
greg.haskins (Fri, 10 Feb 2017 19:00:44 GMT):
not like we can delete the branch later
greg.haskins (Fri, 10 Feb 2017 19:00:44 GMT):
not like we can't delete the branch later
greg.haskins (Fri, 10 Feb 2017 19:00:57 GMT):
@rameshthoomu what was the commit ids per repo again?
greg.haskins (Fri, 10 Feb 2017 19:01:15 GMT):
nm, i found it: https://chat.hyperledger.org/channel/fabric-ci?msg=3awyexq3yppGd3rJ2
rameshthoomu (Fri, 10 Feb 2017 19:01:21 GMT):
yes
rameshthoomu (Fri, 10 Feb 2017 19:02:36 GMT):
@rjones please review https://gerrit.hyperledger.org/r/#/c/5863/
rameshthoomu (Fri, 10 Feb 2017 19:03:31 GMT):
Thanks.. it's merged
greg.haskins (Fri, 10 Feb 2017 19:03:36 GMT):
https://gerrit.hyperledger.org/r/gitweb?p=fabric-ca.git;a=shortlog;h=refs%2Fheads%2Fv1.0.0-preview
greg.haskins (Fri, 10 Feb 2017 19:03:51 GMT):
https://gerrit.hyperledger.org/r/gitweb?p=fabric.git;a=shortlog;h=refs%2Fheads%2Fv1.0.0-preview
greg.haskins (Fri, 10 Feb 2017 19:08:18 GMT):
https://gerrit.hyperledger.org/r/#/c/5865/
rjones (Fri, 10 Feb 2017 19:12:23 GMT):
@rameshthoomu I see the -merge and -verify jobs are disabled - on purpose? https://jenkins.hyperledger.org/view/fabric-app/
greg.haskins (Fri, 10 Feb 2017 19:12:26 GMT):
https://gerrit.hyperledger.org/r/#/c/5871/
rameshthoomu (Fri, 10 Feb 2017 19:16:02 GMT):
yes...In verify and merge we are verifying `make docker` which in included in `release` jobs..
rameshthoomu (Fri, 10 Feb 2017 19:16:02 GMT):
yes...In verify and merge we are verifying `make docker` which is included in `release` jobs..
binhn (Sat, 11 Feb 2017 16:31:20 GMT):
ci seems to act up again
04:53:56 ERROR: for unit-tests Cannot start service unit-tests: Cannot link to a non running container: /unittest_vp_1 AS /unittest_unit-tests_1/unittest_vp_1
surabhi (Sat, 11 Feb 2017 17:58:49 GMT):
Has joined the channel.
C0rWin (Sun, 12 Feb 2017 14:58:22 GMT):
Has joined the channel.
eheads (Mon, 13 Feb 2017 05:57:25 GMT):
Has joined the channel.
yacovm (Mon, 13 Feb 2017 08:20:44 GMT):
https://gerrit.hyperledger.org/r/#/c/5931/ CI job has finished successfully but no +1 from gerrit...
lafenicecc (Mon, 13 Feb 2017 09:16:45 GMT):
Has joined the channel.
lafenicecc (Mon, 13 Feb 2017 09:20:35 GMT):
@rjones https://gerrit.hyperledger.org/r/#/c/5933/ CI is hanging for too long. Could you help restart the CI? Thanks!
aso (Mon, 13 Feb 2017 09:50:44 GMT):
Has left the channel.
rameshthoomu (Mon, 13 Feb 2017 14:00:18 GMT):
@lafenicecc : re-trigged .
rjones (Mon, 13 Feb 2017 14:18:55 GMT):
@yacovm If you read carefully, it triggered two builds and only one has run
yacovm (Mon, 13 Feb 2017 14:19:23 GMT):
ah but why is that?
yacovm (Mon, 13 Feb 2017 14:19:27 GMT):
why were 2 builds triggered?
yacovm (Mon, 13 Feb 2017 14:19:34 GMT):
ahh bdd?
rjones (Mon, 13 Feb 2017 14:27:03 GMT):
Because it's a commit on 0.6
yacovm (Mon, 13 Feb 2017 14:39:36 GMT):
ok
dbshah (Mon, 13 Feb 2017 16:57:33 GMT):
Has joined the channel.
rameshthoomu (Mon, 13 Feb 2017 17:42:54 GMT):
@rjones trivial patch https://gerrit.hyperledger.org/r/#/c/5967/ verified this in sandbox (https://jenkins.hyperledger.org/sandbox/job/fabric-sdk-node-verify-x86_64/20/consoleText)
rjones (Mon, 13 Feb 2017 18:05:29 GMT):
@rameshthoomu Merged
rameshthoomu (Mon, 13 Feb 2017 18:12:51 GMT):
thanks @rjones
rameshthoomu (Mon, 13 Feb 2017 18:53:28 GMT):
@rjones: patch has been submitted to disable power verify and merge jobs CI till the issue FAB-1784 is fixed.
rameshthoomu (Mon, 13 Feb 2017 18:53:40 GMT):
https://gerrit.hyperledger.org/r/#/c/5969/
rjones (Mon, 13 Feb 2017 18:53:42 GMT):
Good
rjones (Mon, 13 Feb 2017 18:54:51 GMT):
Merged
rjones (Mon, 13 Feb 2017 20:41:24 GMT):
Discussion of fabric* repo CI
jimthematrix (Mon, 13 Feb 2017 21:26:07 GMT):
hi @rjones @rameshthoomu can we install SoftHSM lib on the fabric-sdk-node CI servers so that the pkcs11 test cases can run?
```
// To run this test case, install SoftHSM2 library at this link:
// https://wiki.opendnssec.org/display/SoftHSMDOCS/SoftHSM+Documentation+v2
// After installing the library, you need to initialize at least one token
// which will be used below. For the 'pin' property in the configuration
// object below, use the 'user PIN' value (not SO PIN) and please set it to
// '1234' so the code below can run successfully
```
rjones (Mon, 13 Feb 2017 21:34:20 GMT):
@jimthematrix what, explicitly, do I need to do to install them?
jimthematrix (Mon, 13 Feb 2017 21:39:18 GMT):
I don't have the exact steps documented, was following the steps here https://wiki.opendnssec.org/display/SoftHSMDOCS/SoftHSM+Documentation+v2 and i used a pre-built download rather than building from source. other than that it's pretty following the "Installing" steps verbatim with all defaults
jimthematrix (Mon, 13 Feb 2017 21:39:18 GMT):
I don't have the exact steps documented, was following the steps here https://wiki.opendnssec.org/display/SoftHSMDOCS/SoftHSM+Documentation+v2 and i used a pre-built download rather than building from source. other than that it's pretty much following the "Installing" steps verbatim with all defaults
adc (Tue, 14 Feb 2017 10:27:21 GMT):
Has joined the channel.
adc (Tue, 14 Feb 2017 10:27:24 GMT):
Hi All, does someone understand why this is failing: https://jenkins.hyperledger.org/job/fabric-verify-x86_64/6943/console ? Please, help needed.
mastersingh24 (Tue, 14 Feb 2017 10:41:31 GMT):
Hey @adc - I really don't know what causes that error - it seems to crop up every now and then for no reason related to the actual change. Hopefully someone on this channel can help with it
adc (Tue, 14 Feb 2017 10:42:00 GMT):
let's see, thanks for the reply
yacovm (Tue, 14 Feb 2017 10:48:28 GMT):
from tests I made, this "cannot attach to non running container" error is only a symptom and not a cause.
The real cause is that the process in the container immediately upon startup
yacovm (Tue, 14 Feb 2017 10:49:18 GMT):
unit-tests/docker-compose.yaml : ` - CORE_VM_DOCKER_ATTACHSTDOUT=true` toggles this from what I know
adc (Tue, 14 Feb 2017 10:53:17 GMT):
I think I found the problem: I was able to isolate the following case. In that change-set I modify shim/chaincode.go to import "github.com/hyperledger/fabric/protos/utils"
adc (Tue, 14 Feb 2017 10:53:28 GMT):
if I remove that import and the calls associated
adc (Tue, 14 Feb 2017 10:53:38 GMT):
the error disappears
yacovm (Tue, 14 Feb 2017 10:53:43 GMT):
aha!
adc (Tue, 14 Feb 2017 10:53:49 GMT):
if I put back in then the error appears again
adc (Tue, 14 Feb 2017 10:53:55 GMT):
it is systematic.
adc (Tue, 14 Feb 2017 10:54:09 GMT):
but still I don't know why that import causes the problem
yacovm (Tue, 14 Feb 2017 10:54:11 GMT):
can you run the unit tests locally though?
adc (Tue, 14 Feb 2017 10:54:18 GMT):
I'm doing that
yacovm (Tue, 14 Feb 2017 10:54:19 GMT):
maybe you have an import cycle?
adc (Tue, 14 Feb 2017 10:54:26 GMT):
I found that corner case locally
adc (Tue, 14 Feb 2017 10:54:43 GMT):
I don't know, golang should report import cycles
adc (Tue, 14 Feb 2017 10:56:25 GMT):
I think @muralisr can help here
muralisr (Tue, 14 Feb 2017 10:56:25 GMT):
Has joined the channel.
adc (Tue, 14 Feb 2017 10:56:35 GMT):
so it is not the java-shim as I was thinking
vpaprots (Tue, 14 Feb 2017 11:49:52 GMT):
Has joined the channel.
mastersingh24 (Tue, 14 Feb 2017 13:03:21 GMT):
protos will be the death of us :(
coolsvap (Tue, 14 Feb 2017 13:03:21 GMT):
Has joined the channel.
mastersingh24 (Tue, 14 Feb 2017 13:04:32 GMT):
that or bad organization of packages. or both :(
rnsastry (Wed, 15 Feb 2017 04:30:53 GMT):
Has joined the channel.
yuki-kon (Wed, 15 Feb 2017 16:48:35 GMT):
Has joined the channel.
greg.haskins (Wed, 15 Feb 2017 20:33:10 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=JvyMRmWAwxxHLTDDe) @yacovm That is helpful for debugging chaincode problems...in this case, the problem is in the peer container
greg.haskins (Wed, 15 Feb 2017 20:34:19 GMT):
in cases where you get that "vp_1" error in the unit tests, this is the culprit for being too quiet: https://github.com/hyperledger/fabric/blob/923bf3a8e774249344b09c535b726799aec865bd/unit-test/docker-compose.yml#L3
greg.haskins (Wed, 15 Feb 2017 20:34:35 GMT):
simply remove that line, and the peer log will present itself
greg.haskins (Wed, 15 Feb 2017 20:34:57 GMT):
we need a JIRA to make that go to some file rather than /dev/null
yacovm (Wed, 15 Feb 2017 20:47:58 GMT):
Aha! Thanks a lot for this @greg.haskins ! Thats super helpful.
rameshthoomu (Wed, 15 Feb 2017 20:48:46 GMT):
@greg.haskins I am submitting patch for this
wutongtree (Thu, 16 Feb 2017 09:53:47 GMT):
Has joined the channel.
yacovm (Thu, 16 Feb 2017 15:21:13 GMT):
@rameshthoomu @greg.haskins any updates on the patch?
rameshthoomu (Thu, 16 Feb 2017 15:21:54 GMT):
@yacovm testing changes.. will submit in 1 hr
yacovm (Thu, 16 Feb 2017 15:22:01 GMT):
thanks a lot
divyank (Thu, 16 Feb 2017 18:29:56 GMT):
Has joined the channel.
ylsGit (Fri, 17 Feb 2017 02:27:58 GMT):
Has joined the channel.
baohua (Fri, 17 Feb 2017 03:26:19 GMT):
hi, one ci task seems hang, could anyone help stop? thanks! https://jenkins.hyperledger.org/job/fabric-sdk-py-verify-x86_64/39/console
rameshthoomu (Fri, 17 Feb 2017 04:08:05 GMT):
@baohua done..
baohua (Fri, 17 Feb 2017 05:32:39 GMT):
thanks!
greg.haskins (Fri, 17 Feb 2017 19:33:39 GMT):
@rjones: any thoughts on this failure: https://jenkins.hyperledger.org/job/fabric-verify-x86_64/7129/console
greg.haskins (Fri, 17 Feb 2017 19:34:15 GMT):
I am creating a new docker client, but I use the existing fabric-specific variant (consuming our endpoint config, etc
greg.haskins (Fri, 17 Feb 2017 19:34:33 GMT):
and this works when I run the UTs locally but not on jenkins
greg.haskins (Fri, 17 Feb 2017 19:34:44 GMT):
not sure where the disconnect is
muralisr (Fri, 17 Feb 2017 20:19:26 GMT):
@greg.haskins (I'm sure you saw this) `Error starting container: Failed to generate platform-specific docker build: Error uploading input to container: write unix @->/var/run/docker.sock: write: broken pipe`
muralisr (Fri, 17 Feb 2017 20:19:40 GMT):
could be a transient network issue
muralisr (Fri, 17 Feb 2017 20:19:40 GMT):
could be a transient network issue ?
greg.haskins (Fri, 17 Feb 2017 20:37:10 GMT):
@muralisr I dont think its transient
greg.haskins (Fri, 17 Feb 2017 20:37:21 GMT):
something isnt happy within the jenkins environment
greg.haskins (Fri, 17 Feb 2017 20:37:24 GMT):
still trying to figure it out
muralisr (Fri, 17 Feb 2017 20:37:25 GMT):
ok
greg.haskins (Fri, 17 Feb 2017 20:37:29 GMT):
it works fine locally
muralisr (Fri, 17 Feb 2017 20:37:34 GMT):
ok
greg.haskins (Fri, 17 Feb 2017 20:37:47 GMT):
heres what I dont get
greg.haskins (Fri, 17 Feb 2017 20:38:11 GMT):
I use the cutils.NewDockerClient() to get a handle to dockerd, just like all our other code in dockercontroller.go
greg.haskins (Fri, 17 Feb 2017 20:38:24 GMT):
(that should handle the vm.endpoint, etc, etc, correctly)
greg.haskins (Fri, 17 Feb 2017 20:38:45 GMT):
and on top of that, it seems like the client.CreateContainer() worked prior to the upload failure
greg.haskins (Fri, 17 Feb 2017 20:39:25 GMT):
but for whatever reason, and only on jenkins, the dockerd seems to puke when I make that second call
greg.haskins (Fri, 17 Feb 2017 20:40:15 GMT):
The logic is here on L153: https://gerrit.hyperledger.org/r/#/c/6167/1/core/chaincode/platforms/util/utils.go
greg.haskins (Fri, 17 Feb 2017 20:40:51 GMT):
what I dont understand is I would think L137 would have failed too if it were some kind of bad connection to dockerd
greg.haskins (Fri, 17 Feb 2017 20:41:37 GMT):
ill probably need help from @rjones to sort this out
muralisr (Fri, 17 Feb 2017 20:47:32 GMT):
@greg.haskins the z logs are a bit more interesting
muralisr (Fri, 17 Feb 2017 20:47:38 GMT):
```18:13:19 unit-tests_1 | getting deployment spec for chaincode spec: type:GOLANG chaincode_id:
muralisr (Fri, 17 Feb 2017 20:49:07 GMT):
actually this one has a bit of common signature with the x86_64
muralisr (Fri, 17 Feb 2017 20:49:09 GMT):
```
muralisr (Fri, 17 Feb 2017 20:49:21 GMT):
```18:13:19 unit-tests_1 | getting deployment spec for chaincode spec: type:GOLANG chaincode_id:
greg.haskins (Fri, 17 Feb 2017 20:54:12 GMT):
that is interesting
greg.haskins (Fri, 17 Feb 2017 20:54:35 GMT):
I had seen those types of errors during development, but I fixed it with this: https://gerrit.hyperledger.org/r/#/c/6167/1/images/ccenv/Dockerfile.in
greg.haskins (Fri, 17 Feb 2017 20:55:03 GMT):
Im not sure why they are still complaining after the Dockerfile was fixed, however
greg.haskins (Fri, 17 Feb 2017 20:55:41 GMT):
might have to turn up the dockercontroller to DEBUG
rjones (Fri, 17 Feb 2017 20:59:37 GMT):
@greg.haskins is two hours too late - or Monday better for you?
rjones (Fri, 17 Feb 2017 21:00:01 GMT):
I'm in shuttle busses and departure lounges today
greg.haskins (Fri, 17 Feb 2017 21:03:12 GMT):
@rjones no problem
greg.haskins (Fri, 17 Feb 2017 21:10:47 GMT):
@muralisr its very strange, you can see the "mkdir -p /chaincode/input" succeed
rjones (Fri, 17 Feb 2017 21:38:15 GMT):
@greg.haskins so tonight or Monday?
greg.haskins (Fri, 17 Feb 2017 21:38:29 GMT):
sure, works for me
greg.haskins (Fri, 17 Feb 2017 21:38:32 GMT):
thanks ry
dave.enyeart (Sat, 18 Feb 2017 17:45:36 GMT):
@rameshthoomu @greg.haskins @cbf could you or another CI expert comment on the failures in https://gerrit.hyperledger.org/r/#/c/5995/ please? @ruslan.kryukov
ruslan.kryukov (Sat, 18 Feb 2017 17:45:36 GMT):
Has joined the channel.
yacovm (Sat, 18 Feb 2017 17:49:35 GMT):
@dave.enyeart :
https://chat.hyperledger.org/channel/fabric-ci?msg=4WkzXMqpNqdw5Ms8i
dave.enyeart (Sat, 18 Feb 2017 17:52:32 GMT):
@yacovm Looks like it doesnt even get to the chaincode tests, or am i missing something? ```15:51:25 ERROR: for unit-tests Cannot start service unit-tests: Cannot link to a non running container: /unittest_vp_1 AS /unittest_unit-tests_1/vp_1```
dave.enyeart (Sat, 18 Feb 2017 17:52:32 GMT):
@yacovm Looks like it doesnt even get to the chaincode tests, or am i missing something?
yacovm (Sat, 18 Feb 2017 17:53:00 GMT):
yeah in the link- greg talks about this
dave.enyeart (Sat, 18 Feb 2017 17:53:01 GMT):
```15:51:25 ERROR: for unit-tests Cannot start service unit-tests: Cannot link to a non running container: /unittest_vp_1 AS /unittest_unit-tests_1/vp_1```
yacovm (Sat, 18 Feb 2017 17:53:19 GMT):
I think the best option for you now is to reverify
dave.enyeart (Sat, 18 Feb 2017 17:53:26 GMT):
did that multiple times
yacovm (Sat, 18 Feb 2017 17:53:29 GMT):
but I was trying to explain the reason it happens...
dave.enyeart (Sat, 18 Feb 2017 17:53:31 GMT):
and same problem on local
yacovm (Sat, 18 Feb 2017 17:53:38 GMT):
oh on local too?
yacovm (Sat, 18 Feb 2017 17:53:42 GMT):
so do what greg proposed then
dave.enyeart (Sat, 18 Feb 2017 17:55:07 GMT):
i thought the container wasnt even starting... what does CORE_VM_DOCKER_ATTACHSTDOUT=true do for us?
yacovm (Sat, 18 Feb 2017 17:55:27 GMT):
no that was my bad, you can try to remove the log driver in his link
dave.enyeart (Sat, 18 Feb 2017 17:55:56 GMT):
@ruslan.kryukov has been troubleshooting most... do you have any specific questions Ruslan?
ruslan.kryukov (Sat, 18 Feb 2017 17:56:55 GMT):
No, Now I'm trying to find a reason why unit-test fails
dave.enyeart (Sat, 18 Feb 2017 17:57:33 GMT):
ok, please reach out for help on this channel when you have questions
ruslan.kryukov (Sat, 18 Feb 2017 17:58:00 GMT):
good, okay
yacovm (Sat, 18 Feb 2017 18:00:32 GMT):
@ruslan.kryukov take a look at Greg's message in https://chat.hyperledger.org/channel/fabric-ci?msg=wyB6WuxDeBrCSDeFh
yacovm (Sat, 18 Feb 2017 18:00:48 GMT):
try it out, it perhaps will show you the cause of the peer's downfall
ruslan.kryukov (Sat, 18 Feb 2017 18:03:25 GMT):
nothing changed :(
rameshthoomu (Sat, 18 Feb 2017 18:04:40 GMT):
@ruslan.kryukov I got the same error when I run your patch but after remove all the existing containers it's working for me..
rameshthoomu (Sat, 18 Feb 2017 18:05:22 GMT):
can you try make unit-test after removing `vp` and `unit-test` containers
ruslan.kryukov (Sat, 18 Feb 2017 18:15:39 GMT):
I've found failed test
ruslan.kryukov (Sat, 18 Feb 2017 18:15:59 GMT):
core/ledger/kvledger/txmgmt/txmgr/commontests/pkg_test.go
rameshthoomu (Sat, 18 Feb 2017 18:16:23 GMT):
@ruslan.kryukov when I re-run the test peer is crashing ```vp_1 | panic: runtime error: invalid memory address or nil pointer dereference
vp_1 | [signal SIGSEGV: segmentation violation code=0x1 addr=0x8 pc=0x98c31f]
vp_1 |
vp_1 | goroutine 1 [running]:
vp_1 | panic(0xbc4100, 0xc420012040)
vp_1 | /opt/go/src/runtime/panic.go:500 +0x1a1
vp_1 | github.com/hyperledger/fabric/common/ledger/blkstorage/fsblkstorage.(*blockIndex).indexBlock(0xc4201fb710, 0xc421353f90, 0xc00, 0x0)
vp_1 | /opt/gopath/src/github.com/hyperledger/fabric/common/ledger/blkstorage/fsblkstorage/blockindex.go:94 +0xff
vp_1 | github.com/hyperledger/fabric/common/ledger/blkstorage/fsblkstorage.(*blockfileMgr).addBlock(0xc4201e9920, 0xc42135d680, 0x1, 0xc4201fb9c0)
vp_1 | /opt/gopath/src/github.com/hyperledger/fabric/common/ledger/blkstorage/fsblkstorage/blockfile_mgr.go:305 +0x3b7
vp_1 | github.com/hyperledger/fabric/common/ledger/blkstorage/fsblkstorage.(*fsBlockStore).AddBlock(0xc420207e60, 0xc42135d680, 0x20, 0xc4201fb9b0)
vp_1 | /opt/gopath/src/github.com/hyperledger/fabric/common/ledger/blkstorage/fsblkstorage/fs_blockstore.go:42 +0x39
vp_1 | github.com/hyperledger/fabric/core/ledger/kvledger.(*kvLedger).Commit(0xc42132c840, 0xc42135d680, 0x0, 0x0)
vp_1 | /opt/gopath/src/github.com/hyperledger/fabric/core/ledger/kvledger/kv_ledger.go:289 +0x1f1
vp_1 | github.com/hyperledger/fabric/core/ledger/ledgermgmt.(*closableLedger).Commit(0xc420207f00, 0xc42135d680, 0x1269f60, 0xc420207f00)
vp_1 |
ruslan.kryukov (Sat, 18 Feb 2017 18:17:34 GMT):
Got it
ruslan.kryukov (Sat, 18 Feb 2017 18:42:08 GMT):
I almost done
ruslan.kryukov (Sat, 18 Feb 2017 19:44:57 GMT):
Cool! I've run 'make unit-test 'on my local machine and currently tests are running... Give me a second to wait for all tests to finish please and I'll commit them :)
rameshthoomu (Sat, 18 Feb 2017 20:00:32 GMT):
@ruslan.kryukov Seems it's working now after your fix..
ruslan.kryukov (Sat, 18 Feb 2017 20:02:27 GMT):
yep
ruslan.kryukov (Sat, 18 Feb 2017 20:54:38 GMT):
please check test core/common/validation/config_test.go on master branch result 'fail'
ruslan.kryukov (Sat, 18 Feb 2017 20:55:58 GMT):
config_test.go:56: ValidateTransaction failed, err Transaction is not valid. Got [], expected [njqfCQXmrQ7pOm+czl1npclVPV6AEDCCYGEl45kaEsU=]
dave.enyeart (Sat, 18 Feb 2017 21:08:08 GMT):
@ruslan.kryukov Latest failures will be fixed by:
https://gerrit.hyperledger.org/r/#/c/6225/
ruslan.kryukov (Sat, 18 Feb 2017 21:11:16 GMT):
Oh, okay, but how jenkins set +1 https://gerrit.hyperledger.org/r/#/c/6193/ ?
dave.enyeart (Sat, 18 Feb 2017 21:13:27 GMT):
that one started a little bit before yours. problem must have gotten introduced right between them. you had unlucky timing :(
ruslan.kryukov (Sat, 18 Feb 2017 21:14:09 GMT):
:)
dave.enyeart (Sat, 18 Feb 2017 21:14:43 GMT):
hang in there, https://gerrit.hyperledger.org/r/#/c/6225 should get merged as soon as it passes verification
ruslan.kryukov (Sat, 18 Feb 2017 21:16:03 GMT):
Good, I'm waiting for
ruslan.kryukov (Sat, 18 Feb 2017 23:46:39 GMT):
done
murrekatt (Mon, 20 Feb 2017 13:25:18 GMT):
Has joined the channel.
aso (Mon, 20 Feb 2017 13:55:58 GMT):
Has joined the channel.
aso (Tue, 21 Feb 2017 10:25:51 GMT):
https://jenkins.hyperledger.org/job/fabric-verify-x86_64/7342/console
```
10:22:15 [32munit-tests_1 |[0m ok github.com/hyperledger/fabric/events 9.055s coverage: 81.0% of statements
10:22:29 [32munit-tests_1 |[0m ? github.com/hyperledger/fabric/events/consumer [no test files]
10:22:49 [32munit-tests_1 |[0m ? github.com/hyperledger/fabric/events/producer [no test files]
10:23:04 Build timed out (after 120 minutes). Marking the build as failed.
```
aso (Tue, 21 Feb 2017 10:26:20 GMT):
it was gonna be a successful CI but now for some reason CI runs proceed at a glacial pace and so they time out
aso (Tue, 21 Feb 2017 10:30:05 GMT):
any chance anyone can look into this?
aso (Tue, 21 Feb 2017 10:31:01 GMT):
```
08:22:19 Triggered by Gerrit: http://gerrit.hyperledger.org/r/6283
....
09:23:35 Creating unittest_vp_1
09:23:57 Creating unittest_unit-tests_1
```
aso (Tue, 21 Feb 2017 10:31:13 GMT):
it *only* took 1 hour to setup the unit tests
rameshthoomu (Tue, 21 Feb 2017 14:10:06 GMT):
@aso it could be a network issue.. try to re-run the tests with `reverify`
rameshthoomu (Tue, 21 Feb 2017 14:11:21 GMT):
ok now I see you did that already and tests are passed
rjones (Tue, 21 Feb 2017 17:32:10 GMT):
@rameshthoomu why are we getting rid of make linter? https://gerrit.hyperledger.org/r/#/c/6317/3/jjb/fabric/fabric-macros.yaml
rameshthoomu (Tue, 21 Feb 2017 17:33:43 GMT):
one min.. let me check.. I thought this is part of `unit-test`
rameshthoomu (Tue, 21 Feb 2017 17:33:47 GMT):
give me a sec
rameshthoomu (Tue, 21 Feb 2017 17:34:12 GMT):
no it's not part of unit-test target
rameshthoomu (Tue, 21 Feb 2017 17:34:16 GMT):
will update patch
rjones (Tue, 21 Feb 2017 17:34:34 GMT):
ok
rameshthoomu (Tue, 21 Feb 2017 17:36:13 GMT):
updated
rameshthoomu (Tue, 21 Feb 2017 17:36:23 GMT):
sorry
rameshthoomu (Tue, 21 Feb 2017 17:36:38 GMT):
I overlooked it..
rjones (Tue, 21 Feb 2017 17:39:09 GMT):
merged
rameshthoomu (Tue, 21 Feb 2017 17:39:21 GMT):
Thank you
rjones (Tue, 21 Feb 2017 21:39:19 GMT):
User User_1 added by rjones.
vpaprots (Wed, 22 Feb 2017 02:55:49 GMT):
I spent the last two-three days playing a lot of time with unit-tests.. just when did they start taking so long! This "manual resume" hack in run.sh came very handy:
```diff --git a/unit-test/run.sh b/unit-test/run.sh
index e4f8ee6..fd66992 100755
--- a/unit-test/run.sh
+++ b/unit-test/run.sh
@@ -8,7 +8,9 @@ TEST_PKGS=${TEST_PKGS:-github.com/hyperledger/fabric/...}
echo -n "Obtaining list of tests to run for the following packages: ${TEST_PKGS}"
# Some examples don't play nice with `go test`
+
PKGS=`go list ${TEST_PKGS} 2> /dev/null | \
+ sed '1,/orderer\/common\/broadcast/d' | \
grep -v /vendor/ | \
grep -v /build/ | \
grep -v /bddtests/ | \
```
just change the sed command to skip the first to whatever passed last and it will resume.. (though.. it would be great to learn that there is a better way)
binhn (Wed, 22 Feb 2017 10:32:57 GMT):
CI on Z is failing again on https://gerrit.hyperledger.org/r/#/c/6335/
https://jenkins.hyperledger.org/job/fabric-verify-z/3036/ : FAILURE
It has been very unreliable.
harrijk (Wed, 22 Feb 2017 13:25:24 GMT):
@bihn I will ask the providers of the z machines to provide me with dedicated cpus... what has been happening is that when the previous build is being deleted, the steal time for the z Linux machine increasing dramatically which elongates the delete operation and thus causes timeouts on the Jenkins end.
harrijk (Wed, 22 Feb 2017 13:25:24 GMT):
@binhn I will ask the providers of the z machines to provide me with dedicated cpus... what has been happening is that when the previous build is being deleted, the steal time for the z Linux machine increasing dramatically which elongates the delete operation and thus causes timeouts on the Jenkins end.
harrijk (Wed, 22 Feb 2017 13:25:24 GMT):
@binhn I will ask the providers of the z machines to provide me with dedicated cpus... what has been happening is that when the previous build is being deleted, the steal time for the z Linux machine increases dramatically which elongates the delete operation and thus causes timeouts on the Jenkins end.
harrijk (Wed, 22 Feb 2017 13:59:25 GMT):
@binhn I have emailed the providers of my z Linux machines about the resource issue.
muralisr (Wed, 22 Feb 2017 14:26:17 GMT):
@harrijk just FYI if it helps
muralisr (Wed, 22 Feb 2017 14:26:28 GMT):
on the failing CI I see this
muralisr (Wed, 22 Feb 2017 14:26:32 GMT):
Message Attachments
muralisr (Wed, 22 Feb 2017 14:26:40 GMT):
and on the succeeding CI this
muralisr (Wed, 22 Feb 2017 14:27:29 GMT):
Message Attachments
harrijk (Wed, 22 Feb 2017 14:27:29 GMT):
Thanks. I believe I know what is causing this and I have contacted the providers of the z Linux guests.
muralisr (Wed, 22 Feb 2017 14:27:33 GMT):
ok
harrijk (Wed, 22 Feb 2017 14:31:42 GMT):
Metaphorically, this comes down to "stuffing 100 lbs into a 1 lb sack". :)
muralisr (Wed, 22 Feb 2017 15:13:29 GMT):
ah .. that would be an interesting excercise :-)
psa (Wed, 22 Feb 2017 15:55:07 GMT):
Has joined the channel.
vpaprots (Wed, 22 Feb 2017 16:30:56 GMT):
@rameshthoomu An idea I had.. a number of times I have found it very difficult to track down the build failure messages in the jenkins log.. could we insert some eyecatches in the build script after the make finished running?
vpaprots (Wed, 22 Feb 2017 16:31:15 GMT):
something easy, say add 20 '\n'
vpaprots (Wed, 22 Feb 2017 16:32:35 GMT):
i.e. the error you were just helping me with.. https://jenkins.hyperledger.org/job/fabric-ca-verify-ppc64le/241/console.. the actual error is burried in the text:
```
07:10:13 vendor/github.com/miekg/pkcs11/pkcs11.go:29:18: fatal error: ltdl.h: No such file or directory
07:10:13 compilation terminated.
07:10:42 Makefile:95: recipe for target 'bin/fabric-ca' failed
```
vpaprots (Wed, 22 Feb 2017 16:33:41 GMT):
(while we are at it.. I find it 'impressive' that nobody taught jenkins to render VT100 3-bit color scheme!! would be nice to have logs in color :( )
vpaprots (Wed, 22 Feb 2017 16:33:57 GMT):
@rjones ^
harrijk (Wed, 22 Feb 2017 16:41:59 GMT):
Looks like libtool needs to be installed on the power machines (??)
rameshthoomu (Wed, 22 Feb 2017 16:42:57 GMT):
yes @harrijk
muralisr (Wed, 22 Feb 2017 21:51:14 GMT):
@rameshthoomu @rjones noticing failures like the following on a few CRs from x86_64... Z seems to be ok
muralisr (Wed, 22 Feb 2017 21:51:33 GMT):
`20:12:06 Build timed out (after 120 minutes). Marking the build as failed.`
muralisr (Wed, 22 Feb 2017 21:52:41 GMT):
`https://jenkins.hyperledger.org/job/fabric-verify-x86_64/7439/console`
rjones (Wed, 22 Feb 2017 21:52:50 GMT):
@muralisr: @jwagantall is my backup and she is looking in to this issue. I'll be OOF for 2 weeks starting 02-MAR
rjones (Wed, 22 Feb 2017 21:53:00 GMT):
also: please no more DMs :)
muralisr (Wed, 22 Feb 2017 21:53:19 GMT):
sure ... no worries :-)
muralisr (Wed, 22 Feb 2017 21:53:29 GMT):
wasn't sure if you were aware of this already, that's all
jwagantall (Wed, 22 Feb 2017 21:53:33 GMT):
here is a new run for that job in particular https://jenkins.hyperledger.org/job/fabric-verify-x86_64/7454/
jwagantall (Wed, 22 Feb 2017 21:53:48 GMT):
im monitoring it as well... meanwhile i figure what happened
muralisr (Wed, 22 Feb 2017 21:54:01 GMT):
thanks @jwagantall
yacovm (Wed, 22 Feb 2017 21:58:45 GMT):
Is it possible to perhaps pin jwagantall's name on the description of this channel / ci-pipeline channel until you're back?
yacovm (Wed, 22 Feb 2017 21:58:53 GMT):
(just a proposal)
yacovm (Wed, 22 Feb 2017 21:59:06 GMT):
so people that don't know this won't ping you in vain?
rjones (Wed, 22 Feb 2017 21:59:40 GMT):
please don't DM her, either
yacovm (Wed, 22 Feb 2017 21:59:54 GMT):
I'm not saying I will/am
rjones (Wed, 22 Feb 2017 21:59:58 GMT):
all of these private conversations are making handoffs and coverage difficult
yacovm (Wed, 22 Feb 2017 22:00:54 GMT):
when I said ping I actually meant to tag with '@'
rjones (Wed, 22 Feb 2017 22:01:05 GMT):
I added it to the channel topic - is that what you meant?
yacovm (Wed, 22 Feb 2017 22:01:33 GMT):
yeah, thanks!
bartcant (Thu, 23 Feb 2017 02:12:34 GMT):
Has joined the channel.
bart.cant@gmail.com (Thu, 23 Feb 2017 02:16:19 GMT):
Has joined the channel.
greg.haskins (Thu, 23 Feb 2017 13:17:58 GMT):
@rjones @rameshthoomu something seems wrong with the node-sdk CI
greg.haskins (Thu, 23 Feb 2017 13:18:02 GMT):
https://gerrit.hyperledger.org/r/#/c/5429/7
greg.haskins (Thu, 23 Feb 2017 13:18:17 GMT):
its running both -verify and -merge when only -verify should have run (I think)
greg.haskins (Thu, 23 Feb 2017 13:18:25 GMT):
(ignore the failure, I am sure that is me)
harrijk (Thu, 23 Feb 2017 13:26:42 GMT):
It looks like the -merge job is triggered on "Patchset Created" rather than "Change Merged"
rjones (Thu, 23 Feb 2017 16:05:07 GMT):
https://github.com/hyperledger/ci-management/commit/88fe08972ef97d0599907b4fb51bf42985fd144b
jojocheung (Fri, 24 Feb 2017 08:34:52 GMT):
Has joined the channel.
muralisr (Fri, 24 Feb 2017 12:26:48 GMT):
@harrijk Z CI issues cropping up again
muralisr (Fri, 24 Feb 2017 12:28:03 GMT):
for example https://jenkins.hyperledger.org/job/fabric-verify-z/3194/consoleFull https://jenkins.hyperledger.org/job/fabric-verify-z/3200/console for CR https://gerrit.hyperledger.org/r/#/c/6469 and https://gerrit.hyperledger.org/r/#/c/6279/ resp.
muralisr (Fri, 24 Feb 2017 12:28:38 GMT):
messages like ```04:35:17 ARCH=s390x
04:35:17 PATH=/opt/go/bin:$GOPATH/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:~/npm/bin:/usr/local/bin:/usr/bin
04:35:17 GOROOT=/opt/go/
04:35:17 GOPATH=$WORKSPACE/gopath
04:35:17
04:35:17 [EnvInject] - Variables injected successfully.
04:35:17 [EnvInject] - Injecting contributions.
04:35:17 Building remotely on hyp-z-linuxone-07 (hyp-fabric-z) in workspace /w/workspace/fabric-verify-z
04:35:17 [ssh-agent] Looking for ssh-agent implementation...
04:35:17 [ssh-agent] Java/JNR ssh-agent
04:35:17 [ssh-agent] Registered BouncyCastle on the remote agent
04:35:17 [ssh-agent] Started.
04:35:17 [ssh-agent] Using credentials hyperledger-jobbuilder (Gerrit Checkout)
04:35:18 Wiping out workspace first.
04:35:18 java.io.IOException: remote file operation failed: /w/workspace/fabric-verify-z/gopath/src/github.com/hyperledger/fabric at hudson.remoting.Channel@6c416e6f:hyp-z-linuxone-07: java.io.IOException: Unable to delete '/w/workspace/fabric-verify-z/gopath/src/github.com/hyperledger/fabric/core/chaincode/platforms/car/test/msp/sampleconfig/keystore'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts.```
harrijk (Fri, 24 Feb 2017 14:18:00 GMT):
Thanks.
harrijk (Fri, 24 Feb 2017 14:18:35 GMT):
I know what the issue is and I've informed the provider of the issue and told them to take immediate action.
rameshthoomu (Fri, 24 Feb 2017 14:19:35 GMT):
Thanks @harrijk.. I see most of the builds triggered on hyp-z-linuxone-14 and hyp-z-linuxone-06 nodes..
binhn (Fri, 24 Feb 2017 14:23:36 GMT):
what you guys think about removing z-linux CI? it hasn't been stabled and causing so much delay in getting the CRs merged. I know it's important to do CI on all but z hasn't been stabled since it's introduced
binhn (Fri, 24 Feb 2017 14:23:36 GMT):
what you guys think about removing z-linux CI? it hasn't been stable and causing so much delay in getting the CRs merged. I know it's important to do CI on all but z hasn't been stabled since it's introduced
rameshthoomu (Fri, 24 Feb 2017 14:24:28 GMT):
@binhn will disable for now..
binhn (Fri, 24 Feb 2017 14:24:50 GMT):
thanks
harrijk (Fri, 24 Feb 2017 14:26:32 GMT):
@binhn I am working with the LinuxONE cloud folks to resolve the CPU resource shortage issue. For now let's go to a non-voting mode for fabric z jobs.
harrijk (Fri, 24 Feb 2017 14:27:14 GMT):
When the CPU resource shortage is resolved, we'll go back to having z vote for the fabric jobs.
binhn (Fri, 24 Feb 2017 14:27:36 GMT):
thanks
harrijk (Fri, 24 Feb 2017 14:27:48 GMT):
It is essential to have z as a voting member. There have been countless CRs that have broken z.
RangaOnkaram (Fri, 24 Feb 2017 15:25:22 GMT):
Has joined the channel.
wisam.mohammed (Sun, 26 Feb 2017 03:08:26 GMT):
Has joined the channel.
mayerwa (Mon, 27 Feb 2017 13:58:40 GMT):
Has joined the channel.
JonathanLevi (Mon, 27 Feb 2017 19:40:08 GMT):
Has joined the channel.
JonathanLevi (Mon, 27 Feb 2017 19:40:49 GMT):
Yes, I agree with @harrijk. We have missed it a few times...
rjones (Tue, 28 Feb 2017 15:01:52 GMT):
neat!
kletkeman (Tue, 28 Feb 2017 15:18:37 GMT):
Has joined the channel.
rameshthoomu (Tue, 28 Feb 2017 16:17:09 GMT):
Docker Images are being published on below commits
====> FABRIC PEER COMMIT NUMBER - a0d032b ====> FABRIC CA COMMIT NUMBER - c9fb04e ====> FABRIC SDK NODE COMMIT NUMBER - d3fcbe2
```
rameshthoomu/fabric-orderer-x86_64:x86_64-0.7.0-snapshot-a0d032b
rameshthoomu/fabric-peer-x86_64:x86_64-0.7.0-snapshot-a0d032b
rameshthoomu/fabric-javaenv-x86_64:x86_64-0.7.0-snapshot-a0d032b
rameshthoomu/fabric-ccenv-x86_64:x86_64-0.7.0-snapshot-a0d032b
rameshthoomu/fabric-ca-x86_64:x86_64-0.7.0-snapshot-c9fb04e
Docker images for "Power" and "System z" are also available by modifying the last component in the repository based on the desired architecture. The above images represent the Intel versions.
Intel = x86_64
Power = ppc64le
System z = s390x
```
The images are also saved with the tag of : **latest**.
rjones (Tue, 28 Feb 2017 16:25:04 GMT):
@rameshthoomu did you do anything further to enable hyp-jenkins-rocketchat-l, or did it just start working?
rameshthoomu (Tue, 28 Feb 2017 16:25:27 GMT):
it just started working..
rjones (Tue, 28 Feb 2017 16:25:37 GMT):
¯\_(ツ)_/¯
rameshthoomu (Tue, 28 Feb 2017 16:26:05 GMT):
I think latest patches might have fixed the issue
rjones (Tue, 28 Feb 2017 16:26:10 GMT):
I wonder why it's talking in here instead of #jenkins-robot
rameshthoomu (Tue, 28 Feb 2017 16:27:19 GMT):
oh is this the channel I have to post Jenkins build results? I have manually given #fabric-ci channel in one my test job..
rjones (Tue, 28 Feb 2017 16:27:58 GMT):
oh? cool, I didn't know the jobs could direct the output to given channels. You're teaching me something
rameshthoomu (Tue, 28 Feb 2017 16:32:38 GMT):
I am planning to create a *custom message* to send the above mentioned build output.. sample reference here https://jenkins.hyperledger.org/sandbox/job/test_rocket/configure
rjones (Tue, 28 Feb 2017 16:46:36 GMT):
neat!
rameshthoomu (Tue, 28 Feb 2017 18:17:15 GMT):
We are observing issues while pulling images from dockerhub..
```18:09:00 [fabric-verify-x86_64] $ /bin/bash -eu /tmp/hudson7594786996972914821.sh
18:09:01 Unable to find image 'hyperledger/fabric-baseimage:x86_64-0.3.0' locally
18:11:02 Pulling repository docker.io/hyperledger/fabric-baseimage
18:11:02 docker: Could not reach any registry endpoint.
18:11:02 See 'docker run --help'.
```
rjones (Tue, 28 Feb 2017 19:11:53 GMT):
@rameshthoomu big AWS outage right now
rameshthoomu (Tue, 28 Feb 2017 19:12:15 GMT):
ok
rjones (Tue, 28 Feb 2017 19:12:35 GMT):
https://techcrunch.com/2017/02/28/amazon-aws-s3-outage-is-breaking-things-for-a-lot-of-websites-and-apps/ for instance
rjones (Tue, 28 Feb 2017 19:12:35 GMT):
https://techcrunch.com/2017/02/28/amazon-aws-s3-outage-is-breaking-things-for-a-lot-of-websites-and-apps/ for instance3
rameshthoomu (Tue, 28 Feb 2017 19:13:00 GMT):
I think we have to re-run the failed builds once it's back..
rjones (Tue, 28 Feb 2017 20:12:50 GMT):
@rameshthoomu did you make a yaml version of that job config?
rameshthoomu (Tue, 28 Feb 2017 20:21:08 GMT):
@rjones which job you are referring? rocket chat integration ?
rjones (Tue, 28 Feb 2017 20:21:19 GMT):
yes
rameshthoomu (Tue, 28 Feb 2017 20:21:43 GMT):
haven't done.. but will do in sometime..
mastersingh24 (Tue, 28 Feb 2017 20:35:53 GMT):
so reading this - CI is down and out while AWS is down and out?
mastersingh24 (Tue, 28 Feb 2017 20:36:24 GMT):
since we can't pull anything external (since apparently every repo is stored on AWS S3?)
rjones (Tue, 28 Feb 2017 20:52:18 GMT):
@mastersingh24 the issue is github and dockerhub are down.
rjones (Tue, 28 Feb 2017 20:52:53 GMT):
it's a fine distinction, but there isn't much we can do.
rameshthoomu (Wed, 01 Mar 2017 14:09:36 GMT):
All, Docker Images are being published on below commits
=====> FABRIC PEER COMMIT NUMBER - 6325834 ====> FABRIC CA COMMIT NUMBER - c9fb04e =====> FABRIC SDK NODE COMMIT NUMBER - 817fa85
```
rameshthoomu/fabric-orderer-x86_64:x86_64-0.7.0-snapshot-6325834b
rameshthoomu/fabric-peer-x86_64:x86_64-0.7.0-snapshot-6325834b
rameshthoomu/fabric-javaenv-x86_64:x86_64-0.7.0-snapshot-6325834b
rameshthoomu/fabric-ccenv-x86_64:x86_64-0.7.0-snapshot-6325834b
rameshthoomu/fabric-ca-x86_64:x86_64-0.7.0-snapshot-c9fb04e
Docker images for "Power" and "System z" are also available by modifying the last component in the repository based on the desired architecture. The above images represent the Intel versions.
Intel = x86_64
Power = ppc64le
System z = s390x
```
The images are also saved with the tag of : *latest*.
scottz (Wed, 01 Mar 2017 21:50:42 GMT):
Has joined the channel.
mastersingh24 (Thu, 02 Mar 2017 14:23:11 GMT):
guys - can we modify CI to start using cached images / versions of things?
mastersingh24 (Thu, 02 Mar 2017 14:23:39 GMT):
bunch of crap failing because it can't pull down dependencies which have not changed in forever - e.g. maven stuff
rameshthoomu (Thu, 02 Mar 2017 14:48:54 GMT):
@mastersingh24 will look into this..
rameshthoomu (Thu, 02 Mar 2017 14:48:54 GMT):
sure that helps
mastersingh24 (Thu, 02 Mar 2017 15:08:17 GMT):
thanks - it's not urgent given everything else we are doing - I can add a JIRA for it
mastersingh24 (Thu, 02 Mar 2017 15:08:23 GMT):
just some food for thought ;)
rameshthoomu (Thu, 02 Mar 2017 15:08:43 GMT):
sure that helps
rameshthoomu (Thu, 02 Mar 2017 15:43:28 GMT):
All, Docker Images are being published on below commits
====> FABRIC PEER COMMIT NUMBER - 565a758 ====> FABRIC CA COMMIT NUMBER - 878804c ====> FABRIC SDK NODE COMMIT NUMBER - 4702e5b
```
rameshthoomu/fabric-orderer-x86_64:x86_64-0.7.0-snapshot-565a758
rameshthoomu/fabric-peer-x86_64:x86_64-0.7.0-snapshot-565a758
rameshthoomu/fabric-javaenv-x86_64:x86_64-0.7.0-snapshot-565a758
rameshthoomu/fabric-ccenv-x86_64:x86_64-0.7.0-snapshot-565a758
rameshthoomu/fabric-ca-x86_64:x86_64-0.7.0-snapshot-878804c
Docker images for "Power" and "System z" are also available by modifying the last component in the repository based on the desired architecture. The above images represent the Intel versions.
Intel = x86_64
Power = ppc64le
System z = s390x
```
The images are also saved with the tag of : *latest*.
rameshthoomu (Thu, 02 Mar 2017 15:43:28 GMT):
All, Docker Images are being published on below commits
`====> FABRIC PEER COMMIT# 509d8ed ====> FABRIC CA COMMIT# f18b6b7 ====> FABRIC SDK NODE COMMIT# d99495f ===> FABRIC SDK JAVA COMMIT# c0dd14b`
```
rameshthoomu/fabric-orderer-x86_64:x86_64-0.7.0-snapshot-509d8ed
rameshthoomu/fabric-peer-x86_64:x86_64-0.7.0-snapshot-509d8ed
rameshthoomu/fabric-javaenv-x86_64:x86_64-0.7.0-snapshot-509d8ed
rameshthoomu/fabric-ccenv-x86_64:x86_64-0.7.0-snapshot-509d8ed
rameshthoomu/fabric-ca-x86_64:x86_64-0.7.0-snapshot-f18b6b7
Docker images for "Power" and "System z" are also available by modifying the last component in the repository based on the desired architecture. The above images represent the Intel versions.
Intel = x86_64
Power = ppc64le
System z = s390x
```
The images are also saved with the tag of : *latest*
simsc (Thu, 02 Mar 2017 22:19:56 GMT):
Has joined the channel.
rickr (Thu, 02 Mar 2017 22:25:59 GMT):
Has joined the channel.
yong (Fri, 03 Mar 2017 03:26:28 GMT):
Has joined the channel.
yong (Fri, 03 Mar 2017 03:26:53 GMT):
[yong@bogon fabric]$ sudo -E make docker
Building build/docker/bin/peer
# github.com/hyperledger/fabric/vendor/github.com/miekg/pkcs11
vendor/github.com/miekg/pkcs11/pkcs11.go:30:18: fatal error: ltdl.h: No such file or directory
#include
yong (Fri, 03 Mar 2017 03:27:21 GMT):
[yong@bogon fabric]$ sudo -E make docker
Building build/docker/bin/peer
# github.com/hyperledger/fabric/vendor/github.com/miekg/pkcs11
vendor/github.com/miekg/pkcs11/pkcs11.go:30:18: fatal error: ltdl.h: No such file or directory
#include
Willson (Fri, 03 Mar 2017 03:55:10 GMT):
Has joined the channel.
rameshthoomu (Fri, 03 Mar 2017 04:11:52 GMT):
@yong please install libtool
yong (Fri, 03 Mar 2017 05:38:29 GMT):
@rameshthoomu Thanks,I install libtool
Ratnakar (Fri, 03 Mar 2017 14:48:12 GMT):
Has joined the channel.
rameshthoomu (Fri, 03 Mar 2017 15:25:07 GMT):
All, end-to-end (node sdk) tests are failing consistently. Fix is on the way. https://gerrit.hyperledger.org/r/#/c/6789/
rameshthoomu (Fri, 03 Mar 2017 15:26:27 GMT):
Will re-run the tests once fix is in place and based on the result will publish images.
rahulhegde (Fri, 03 Mar 2017 16:09:48 GMT):
Has joined the channel.
weeds (Fri, 03 Mar 2017 16:14:00 GMT):
@rameshtoomu today i got a question on what "application" code we have running in the CLI ( i suspect example 2).. and what type of "applicaiton" code are we running in the CI for Nodejs.sdk and Java.sdk
weeds (Fri, 03 Mar 2017 16:14:07 GMT):
can you please clarify here
weeds (Fri, 03 Mar 2017 16:14:33 GMT):
@rameshthoomu ^^
weeds (Fri, 03 Mar 2017 16:18:43 GMT):
@tsnyder this is the channel your team should look at to understand docker images,.. and the status of CI running
tsnyder (Fri, 03 Mar 2017 16:18:44 GMT):
Has joined the channel.
v_thirugnanam (Fri, 03 Mar 2017 16:20:21 GMT):
Has joined the channel.
weeds (Fri, 03 Mar 2017 16:21:42 GMT):
btw, this is the change set people can take a look at that I referred to describing the CLI tests- https://gerrit.hyperledger.org/r/#/c/6607/8
tsnyder (Fri, 03 Mar 2017 16:21:45 GMT):
Thanks
rameshthoomu (Fri, 03 Mar 2017 16:24:22 GMT):
yes @weeds.. All three e2e tests are using example02..
ManjeetGambhir (Fri, 03 Mar 2017 16:25:00 GMT):
Has joined the channel.
ManjeetGambhir (Fri, 03 Mar 2017 16:26:22 GMT):
@rameshthoomu java End2endIT is also included?
rameshthoomu (Fri, 03 Mar 2017 16:27:10 GMT):
yes
ManjeetGambhir (Fri, 03 Mar 2017 16:27:20 GMT):
thanks
weeds (Fri, 03 Mar 2017 16:27:34 GMT):
jav ent is the container for java chaincode
weeds (Fri, 03 Mar 2017 16:27:50 GMT):
@rameshthoomu you are adding the java sdk pieces in the output today of results of your ci- yes?
bmos299 (Fri, 03 Mar 2017 16:46:11 GMT):
The java e2e tests have been added but did not pass today, that is why there is not post to the channel. The bug is being tracked in https://jira.hyperledger.org/browse/FAB-2623.
forgeRW (Fri, 03 Mar 2017 17:11:40 GMT):
Has joined the channel.
weeds (Fri, 03 Mar 2017 17:34:12 GMT):
@rameshthoomu only hyperledger is mapped to go path- Evidently someone fixed that in vagrant to include local dev- but not visible in CLI container..it's a barrier that really needs to gotten rid of I think- do we think this is obsoleted by chaincode builder that Greg Built? the issue is #2587
rameshthoomu (Fri, 03 Mar 2017 17:36:03 GMT):
checking issue #2587
rickr (Fri, 03 Mar 2017 17:38:41 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=NjMTux9KMFCCTf88s) @bmos299 @muralisr `2017-03-03 16:24:50 ERROR Chain:1011 - Sending proposal to peer failed because of gRPC failure=Status{code=UNKNOWN, description=Failure while looking up the ledger testchainid, cause=null}` Is the most like issue here that peer is configured to not support the default *testchainid* ? this is what we are getting back from the peer on a chaincode install .. sdk verifiy test pass where I know testchaindid channel is enabled
rameshthoomu (Fri, 03 Mar 2017 17:56:20 GMT):
user has to mount his chaincode path to CLI container so that it chaincode will be available for executing in CLI.. @greg.haskins any inputs?
greg.haskins (Fri, 03 Mar 2017 18:03:50 GMT):
personally, i would not encourage running the CLI from within docker
greg.haskins (Fri, 03 Mar 2017 18:04:06 GMT):
I think its awkward for our users
greg.haskins (Fri, 03 Mar 2017 18:04:48 GMT):
but, if I were going to, I would perhaps use something like "-v`pwd`:/mnt -w /mnt" so I had local code available
greg.haskins (Fri, 03 Mar 2017 18:05:33 GMT):
this is probably compounded by GOPATH requirements and CLI-in-docker awkwardness and GOLANG chaincode
greg.haskins (Fri, 03 Mar 2017 18:05:43 GMT):
I would suggest using native CLI and chaintool ;)
greg.haskins (Fri, 03 Mar 2017 18:05:43 GMT):
I would suggest using native CLI and/or chaintool ;)
suryalanka (Fri, 03 Mar 2017 19:17:39 GMT):
Has joined the channel.
rahulhegde (Fri, 03 Mar 2017 20:19:20 GMT):
@rameshthoomu - can we get update on the fabric-image as Rick did mention about it as configuration issue.
rahulhegde (Fri, 03 Mar 2017 20:19:20 GMT):
@rameshthoomu - can we get update on the fabric-image as Rick did mention about it as configuration issue. This will help us download this images and work on the copy.
rameshthoomu (Fri, 03 Mar 2017 20:23:44 GMT):
@rahulhegde which configuration issue you are specifying?
rahulhegde (Fri, 03 Mar 2017 20:24:06 GMT):
https://jira.hyperledger.org/browse/FAB-2623
rameshthoomu (Fri, 03 Mar 2017 20:25:54 GMT):
We are seeing end-to-end (node) and (sdk) tests are failing.. @rickr is checking with developer on the failures
rameshthoomu (Fri, 03 Mar 2017 20:26:39 GMT):
will publish images once tests are successful..
rickr (Fri, 03 Mar 2017 20:27:40 GMT):
I gave @muralisr the screen shot of the issue you were seeing.
rahulhegde (Fri, 03 Mar 2017 20:27:49 GMT):
@rameshthoomu we are anticipating these fabric-images which are compatible to the Fabric-Java SDK. Thanks - I hope we will receive a update soon. Could you give a tentative time where we can come and check for the next update?
rahulhegde (Fri, 03 Mar 2017 20:32:02 GMT):
A separate question - did the March 1 published images pass all test cases for Fabric Java SDK?
rameshthoomu (Fri, 03 Mar 2017 20:34:25 GMT):
Will post build results and images here after successful run..
ManjeetGambhir (Fri, 03 Mar 2017 20:35:04 GMT):
@rameshthoomu thanks , we are waiting eagerly
weeds (Fri, 03 Mar 2017 20:39:40 GMT):
@rahulhegde I would suggest looking tomorrow- people working on problems now Rahul. I know it's painful ;-)
wlahti (Fri, 03 Mar 2017 21:42:24 GMT):
Has joined the channel.
tuand (Fri, 03 Mar 2017 21:43:16 GMT):
Has joined the channel.
rickr (Fri, 03 Mar 2017 21:53:44 GMT):
I got the latest fabric and I'm seeing this now too `Failure while looking up the ledger testchainid, cause=null}. Was verified:false
at org.hyperledger.fabric.sdkintegration.End2endIT.runChain(End2endIT.java:231)`
rickr (Fri, 03 Mar 2017 21:54:03 GMT):
peer start up : https://jpst.it/UH0F
rickr (Fri, 03 Mar 2017 21:54:40 GMT):
I can start up a later build exactly the same way and I don't see that error
rickr (Fri, 03 Mar 2017 21:54:56 GMT):
@muralisr @rameshthoomu
muralisr (Fri, 03 Mar 2017 21:56:27 GMT):
muralisr 4:43 PM
I think the best option is to add -o option to `peer node start`
well I should say "another option"
and use it only with testchainid
@C0rWin what do you think ?
muralisr (Fri, 03 Mar 2017 21:56:38 GMT):
@C0rWin what do you think ?
C0rWin (Fri, 03 Mar 2017 21:58:07 GMT):
Well, from the error message it looks like this has nothing to do with ordering service endpoints?
rickr (Fri, 03 Mar 2017 22:00:37 GMT):
There is no obvious error on the peer side https://jpst.it/UH4G
muralisr (Fri, 03 Mar 2017 22:02:48 GMT):
@C0rWin the problem I think is that peer is started to use testchainID and the config block tries to reach orderer in 127.0.0.1:7050
muralisr (Fri, 03 Mar 2017 22:02:48 GMT):
@C0rWin the problem I think is that peer is started to use testchainID and the config block tries to reach orderer at 127.0.0.1:7050
muralisr (Fri, 03 Mar 2017 22:03:16 GMT):
which is fine in native/docker envs
muralisr (Fri, 03 Mar 2017 22:03:27 GMT):
but won't work when orderer in docker
C0rWin (Fri, 03 Mar 2017 22:03:36 GMT):
this is not what printed in the error log
C0rWin (Fri, 03 Mar 2017 22:03:50 GMT):
> I got the latest fabric and I'm seeing this now too `Failure while looking up the ledger testchainid, cause=null}. Was verified:false
C0rWin (Fri, 03 Mar 2017 22:04:43 GMT):
``` c := committer.NewLedgerCommitter(ledger, txvalidator.NewTxValidator(cs))
ordererAddresses := configtxManager.ChannelConfig().OrdererAddresses()
if len(ordererAddresses) == 0 {
return errors.New("No orderering service endpoint provided in configuration block")
}```
C0rWin (Fri, 03 Mar 2017 22:04:57 GMT):
so this should be the error message
muralisr (Fri, 03 Mar 2017 22:05:06 GMT):
hmm
rickr (Fri, 03 Mar 2017 22:05:08 GMT):
I've not see seen error reliably being printed on peer error logs when the sdk sees them
muralisr (Fri, 03 Mar 2017 22:05:17 GMT):
there *is* a service endpoint
muralisr (Fri, 03 Mar 2017 22:05:31 GMT):
except its not reachable as its 127.0.0.1:7050
C0rWin (Fri, 03 Mar 2017 22:05:46 GMT):
or
C0rWin (Fri, 03 Mar 2017 22:05:49 GMT):
```func NewDeliverService(gossip blocksprovider.GossipServiceAdapter, endpoints []string) (DeliverService, error) {
indices := rand.Perm(len(endpoints))
for _, idx := range indices {
logger.Infof("Creating delivery service to get blocks from the ordering service, %s", endpoints[idx])
dialOpts := []grpc.DialOption{grpc.WithInsecure(), grpc.WithTimeout(3 * time.Second), grpc.WithBlock()}
if comm.TLSEnabled() {
dialOpts = append(dialOpts, grpc.WithTransportCredentials(comm.InitTLSForPeer()))
} else {
dialOpts = append(dialOpts, grpc.WithInsecure())
}
conn, err := grpc.Dial(endpoints[idx], dialOpts...)
if err != nil {
logger.Errorf("Cannot dial to %s, because of %s", endpoints[idx], err)
continue
}
return NewFactoryDeliverService(gossip, &blocksDelivererFactoryImpl{conn}, conn), nil
}
return nil, fmt.Errorf("Wasn't able to connect to any of ordering service endpoints %s", endpoints)
}```
C0rWin (Fri, 03 Mar 2017 22:06:14 GMT):
so in case of ordering service endpoint problem
muralisr (Fri, 03 Mar 2017 22:06:17 GMT):
maybe that's also there in the logs...
C0rWin (Fri, 03 Mar 2017 22:06:23 GMT):
this should be one of the errors
muralisr (Fri, 03 Mar 2017 22:06:28 GMT):
can you check @rickr
C0rWin (Fri, 03 Mar 2017 22:06:30 GMT):
so need to be checked
C0rWin (Fri, 03 Mar 2017 22:06:38 GMT):
before jumping into solution :)
muralisr (Fri, 03 Mar 2017 22:07:17 GMT):
Im going by the fact that there's no way 127.0.0.1 can be reached ... :-)
muralisr (Fri, 03 Mar 2017 22:07:22 GMT):
but you are right of course
muralisr (Fri, 03 Mar 2017 22:07:27 GMT):
lets look for that string
rickr (Fri, 03 Mar 2017 22:08:06 GMT):
what are you asking me to look for ?
C0rWin (Fri, 03 Mar 2017 22:08:08 GMT):
``` if chainID != "" {
// here we handle uniqueness check and ACLs for proposals targeting a chain
lgr := peer.GetLedger(chainID)
if lgr == nil {
return nil, errors.New(fmt.Sprintf("Failure while looking up the ledger %s", chainID))
}
if _, err := lgr.GetTransactionByID(txid); err == nil {
return nil, fmt.Errorf("Duplicate transaction found [%s]. Creator [%x]. [%s]", txid, shdr.Creator, err)
}
// check ACL - we verify that this proposal
// complies with the policy of the chain
if err = e.checkACL(signedProp, chdr, shdr, hdrExt); err != nil {
return &pb.ProposalResponse{Response: &pb.Response{Status: 500, Message: err.Error()}}, err
}
}```
C0rWin (Fri, 03 Mar 2017 22:08:59 GMT):
```func (e *Endorser) commitTxSimulation(proposal *pb.Proposal, chainID string, signer msp.SigningIdentity, pResp *pb.ProposalResponse, blockNumber uint64) error {
tx, err := putils.CreateSignedTx(proposal, signer, pResp)
if err != nil {
return err
}
lgr := peer.GetLedger(chainID)
if lgr == nil {
return fmt.Errorf("failure while looking up the ledger")
}
txBytes, err := proto.Marshal(tx)
if err != nil {
return err
}
block := common.NewBlock(blockNumber, []byte{})
block.Data.Data = [][]byte{txBytes}
block.Header.DataHash = block.Data.Hash()
if err = lgr.Commit(block); err != nil {
return err
}
return nil
}```
muralisr (Fri, 03 Mar 2017 22:09:14 GMT):
@rickr one of the strings in
muralisr (Fri, 03 Mar 2017 22:09:16 GMT):
```
C0rWin (Fri, 03 Mar 2017 22:09:22 GMT):
so it looks like no `testchainid` ledger was ever created
muralisr (Fri, 03 Mar 2017 22:09:32 GMT):
```func NewDeliverService(gossip blocksprovider.GossipServiceAdapter, endpoints []string) (DeliverService, error) {
indices := rand.Perm(len(endpoints))
for _, idx := range indices {
logger.Infof("Creating delivery service to get blocks from the ordering service, %s", endpoints[idx])
dialOpts := []grpc.DialOption{grpc.WithInsecure(), grpc.WithTimeout(3 * time.Second), grpc.WithBlock()}
if comm.TLSEnabled() {
dialOpts = append(dialOpts, grpc.WithTransportCredentials(comm.InitTLSForPeer()))
} else {
dialOpts = append(dialOpts, grpc.WithInsecure())
}
conn, err := grpc.Dial(endpoints[idx], dialOpts...)
if err != nil {
logger.Errorf("Cannot dial to %s, because of %s", endpoints[idx], err)
continue
}
return NewFactoryDeliverService(gossip, &blocksDelivererFactoryImpl{conn}, conn), nil
}
return nil, fmt.Errorf("Wasn't able to connect to any of ordering service endpoints %s", endpoints)
}```
C0rWin (Fri, 03 Mar 2017 22:09:38 GMT):
at least according to the code
C0rWin (Fri, 03 Mar 2017 22:10:12 GMT):
```Cannot dial to 127.0.0.1:7050```
C0rWin (Fri, 03 Mar 2017 22:10:21 GMT):
this should be a string
C0rWin (Fri, 03 Mar 2017 22:10:26 GMT):
most likely
C0rWin (Fri, 03 Mar 2017 22:10:34 GMT):
if there is a problem w/ ordering service
rickr (Fri, 03 Mar 2017 22:11:02 GMT):
I change my orderer to listen on 0.0.0.0
rickr (Fri, 03 Mar 2017 22:13:15 GMT):
`2017-03-03 22:10:43.837 UTC [msp] newIdentity -> DEBU 1e1 Creating identity instance for ID &{DEFAULT DEFAULT}
create default chain [testchainid] failed with No orderering service endpoint provided in configuration block2017-03-03 22:10:43.838 UTC [peer] Initialize -> INFO 1e3 Loading chain testchainid
2017-03-03 22:10:43.838 UTC [ledgermgmt] OpenLedger -> INFO 1e4 Opening ledger with id = testchainid`
rickr (Fri, 03 Mar 2017 22:13:46 GMT):
2017-03-03 22:10:43.838 UTC [peer] Initialize -> WARN 1e5 Failed to load ledger testchainid(Ledger already opened)
wlahti (Fri, 03 Mar 2017 22:19:19 GMT):
Which brings things back to the original question I posed: I've created a new foo.configtx file but I'm not sure what needs to be done on the config block side of things. I can generate it without a problem but it's unclear what to do so the javasdk tests use it.
C0rWin (Fri, 03 Mar 2017 22:19:24 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=pD6rGZyyBTPirWJmM) @rickr this won't help, the problem here is opposite, the peer cannot reach the ordering service
C0rWin (Fri, 03 Mar 2017 22:19:35 GMT):
and least this is a working hypothesis right now
C0rWin (Fri, 03 Mar 2017 22:20:23 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=u9jxsoJ9y4Kz8T7BD) @wlahti have you tried to ask this on #fabric-sdk-java ?
wlahti (Fri, 03 Mar 2017 22:21:14 GMT):
It was suggested by the group to discuss that here.
C0rWin (Fri, 03 Mar 2017 22:22:15 GMT):
ok
C0rWin (Fri, 03 Mar 2017 22:22:25 GMT):
but need someone familiar w/ java sdk, no?
wlahti (Fri, 03 Mar 2017 22:22:59 GMT):
Right, that would be @rickr or @tuand
rickr (Fri, 03 Mar 2017 22:23:17 GMT):
@wlahti I don't think we are getting that far with the very latest build ... currently we don't install chain code at all and we don't use configtx file
rickr (Fri, 03 Mar 2017 22:23:33 GMT):
at that point
C0rWin (Fri, 03 Mar 2017 22:24:07 GMT):
you are using `testchainid`, right?
rickr (Fri, 03 Mar 2017 22:24:15 GMT):
y
C0rWin (Fri, 03 Mar 2017 22:24:20 GMT):
got it
C0rWin (Fri, 03 Mar 2017 22:24:28 GMT):
need to look on it
C0rWin (Fri, 03 Mar 2017 22:24:51 GMT):
not sure the problem is w/ ordering service endpoint configuration
C0rWin (Fri, 03 Mar 2017 22:25:12 GMT):
I can add an option to override it for testchainid
rickr (Fri, 03 Mar 2017 22:26:32 GMT):
the scenario is this we use testchained to install chaincode. Then we instantiate invoke and query all on the testchain .. Then we go another pass where we create a chain `foo` instantiate invoke and query on that chain
yacovm (Fri, 03 Mar 2017 22:26:58 GMT):
so... just uh, a thought- is this testchainid going to be deprecated at some point?
C0rWin (Fri, 03 Mar 2017 22:28:16 GMT):
hope so
C0rWin (Fri, 03 Mar 2017 22:28:32 GMT):
my guess it's here only to support SDK part
C0rWin (Fri, 03 Mar 2017 22:28:46 GMT):
once SDK will be able to work with configuration block it will be out of use
muralisr (Fri, 03 Mar 2017 22:32:35 GMT):
```2017-03-03 21:39:21.355 UTC [msp] GetLocalMSP -> DEBU 1df Returning existing local MSP
2017-03-03 21:39:21.355 UTC [msp] DeserializeIdentity -> INFO 1e0 Obtaining identity
2017-03-03 21:39:21.356 UTC [msp] newIdentity -> DEBU 1e1 Creating identity instance for ID &{DEFAULT DEFAULT}
create default chain [testchainid] failed with No orderering service endpoint provided in configuration block```
C0rWin (Fri, 03 Mar 2017 22:32:55 GMT):
nice!
muralisr (Fri, 03 Mar 2017 22:33:01 GMT):
I see that in @rickr logs https://justpaste.it/1447g
C0rWin (Fri, 03 Mar 2017 22:33:39 GMT):
ok
C0rWin (Fri, 03 Mar 2017 22:34:01 GMT):
so going to add `-o` parameter to cover the testchainid case
C0rWin (Fri, 03 Mar 2017 22:34:10 GMT):
@muralisr are you ok with it?
C0rWin (Fri, 03 Mar 2017 22:34:27 GMT):
btw, what is the plan to depricate `testchainid`?
muralisr (Fri, 03 Mar 2017 22:35:44 GMT):
let me ge one more thing @C0rWin ... going to look at the logs from CI too
C0rWin (Fri, 03 Mar 2017 22:35:55 GMT):
sure
C0rWin (Fri, 03 Mar 2017 22:36:03 GMT):
wait, CI?
muralisr (Fri, 03 Mar 2017 22:37:00 GMT):
yes
muralisr (Fri, 03 Mar 2017 22:37:01 GMT):
docker
muralisr (Fri, 03 Mar 2017 22:43:38 GMT):
Message Attachments
muralisr (Fri, 03 Mar 2017 22:43:50 GMT):
https://jenkins.hyperledger.org/sandbox/job/e2e_java_x86_64/2/artifact/gopath/src/github.com/hyperledger/fabric-sdk-java/src/test/fixture/src/dockerlogfile.log
muralisr (Fri, 03 Mar 2017 22:44:43 GMT):
but one thing I'm confused @C0rWin ... wouldn't I have at least 1 entry 127.0.0.1:7050
muralisr (Fri, 03 Mar 2017 22:45:09 GMT):
I wouldn't expect "No ordering service endpoint..."
muralisr (Fri, 03 Mar 2017 22:45:30 GMT):
maybe I'm not reading the code right...
C0rWin (Fri, 03 Mar 2017 22:50:11 GMT):
``` chainID := util.GetTestChainID()
// add readers, writers and admin policies for the default chain
policyTemplate := configtx.NewSimpleTemplate(
policies.TemplateImplicitMetaAnyPolicy([]string{application.GroupKey}, msp.ReadersPolicyKey),
policies.TemplateImplicitMetaAnyPolicy([]string{application.GroupKey}, msp.WritersPolicyKey),
policies.TemplateImplicitMetaMajorityPolicy([]string{application.GroupKey}, msp.AdminsPolicyKey),
)
// We create a genesis block for the test
// chain with its MSP so that we can transact
block, err := genesis.NewFactoryImpl(
configtx.NewCompositeTemplate(
test.ApplicationOrgTemplate(),
policyTemplate)).Block(chainID)
if nil != err {
panic(fmt.Sprintf("Unable to create genesis block for [%s] due to [%s]", chainID, err))
}```
C0rWin (Fri, 03 Mar 2017 22:50:31 GMT):
no one configures here endpoints as far as I can see from the code
C0rWin (Fri, 03 Mar 2017 22:50:40 GMT):
unless it's done in other place
muralisr (Fri, 03 Mar 2017 23:20:33 GMT):
@C0rWin so we need to add "-o" option ?
C0rWin (Fri, 03 Mar 2017 23:20:46 GMT):
looks so
muralisr (Fri, 03 Mar 2017 23:21:01 GMT):
ok... I'm still missing something
C0rWin (Fri, 03 Mar 2017 23:25:05 GMT):
what?
muralisr (Fri, 03 Mar 2017 23:40:31 GMT):
I need to check something first @C0rWin
rahulhegde (Fri, 03 Mar 2017 23:42:29 GMT):
@Ratnakar could please confirm if below commit will be available as part of this release
* https://jira.hyperledger.org/browse/FAB-2560 will be available as part of this release.
* https://github.com/hyperledger/fabric/commit/167b14aa03a66805c6a6be6091c3fa2925f9ac7d
Is there a way I can check this next time?
rahulhegde (Fri, 03 Mar 2017 23:42:29 GMT):
@Ratnakar could please confirm if below commit will be available as part of this release
* https://jira.hyperledger.org/browse/FAB-2560
* https://github.com/hyperledger/fabric/commit/167b14aa03a66805c6a6be6091c3fa2925f9ac7d
Is there a way I can check this next time?
Ratnakar (Sat, 04 Mar 2017 00:28:51 GMT):
@rahulhegde I think @dave.enyeart and @chris.elder are the right people to comment on your question
chris.elder (Sat, 04 Mar 2017 00:28:51 GMT):
Has joined the channel.
muralisr (Sat, 04 Mar 2017 00:43:41 GMT):
just got back to this... CLI also fails with latest when using `peer node start` ... (for some reason I thought it worked) so @C0rWin it does appear we need to add the "-o" option ... till we remove testchainid...
C0rWin (Sat, 04 Mar 2017 01:04:34 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=WYQDbEsGnKrbyLWRa) @muralisr just pushed new CR: https://gerrit.hyperledger.org/r/#/c/6821/
rickr (Sat, 04 Mar 2017 03:15:23 GMT):
FYI So I changed my end2end test to use two created chains .. not the test chain. The e2e test just interacts with one orderer and peer. I start this in vagrant naively (no docker) runs to completion no issues. Now when I submit to gerrit the verify job fails. There is a timeout on sending the instantiate proposal .. two min timeout is set .
```
02:48:41 Mar 04, 2017 2:48:41 AM io.grpc.internal.ManagedChannelImpl
rickr (Sat, 04 Mar 2017 03:15:23 GMT):
FYI So I changed my end2end test to use two created chains .. not the test chain. The e2e test just interacts with one orderer and peer. I start peer/orderer in vagrant naively (no docker) runs to completion no issues. Now when I submit to gerrit the verify job fails. There is a timeout on sending the instantiate proposal .. two min timeout is set .
```
02:48:41 Mar 04, 2017 2:48:41 AM io.grpc.internal.ManagedChannelImpl
rickr (Sat, 04 Mar 2017 03:15:23 GMT):
FYI So I changed my end2end test to use two created chains .. not the test chain. The e2e test just interacts with one orderer and peer. I start peer/orderer in vagrant natively (no docker) runs to completion no issues. Now when I submit to gerrit the verify job fails. There is a timeout on sending the instantiate proposal .. two min timeout is set .
```
02:48:41 Mar 04, 2017 2:48:41 AM io.grpc.internal.ManagedChannelImpl
rickr (Sat, 04 Mar 2017 03:15:23 GMT):
FYI So I changed my end2end test to use two created chains .. not the test chain. The e2e test just interacts with one orderer and peer. I start peer/orderer in vagrant natively (no docker) runs to completion no issues. Now when I submit to gerrit the verify job fails. There is a timeout on sending the instantiate proposal .. two min timeout is set .
```
02:48:41 Mar 04, 2017 2:48:41 AM io.grpc.internal.ManagedChannelImpl
rickr (Sat, 04 Mar 2017 03:15:23 GMT):
FYI So I changed my end2end test to use two created chains .. not the test chain. The e2e test just interacts with one orderer and peer. I start peer/orderer in vagrant natively (no docker) runs to completion no issues. Now when I submit to gerrit the verify job fails. There is a timeout on sending the instantiate proposal .. two min timeout is set .
```
02:48:41 Mar 04, 2017 2:48:41 AM io.grpc.internal.ManagedChannelImpl
rickr (Sat, 04 Mar 2017 03:15:23 GMT):
FYI So I changed my end2end test to use two created chains .. not the test chain. The e2e test just interacts with one orderer and peer. I start peer/orderer in vagrant natively (no docker) runs to completion no issues. Now when I submit to gerrit the verify job fails. There is a timeout on sending the instantiate proposal to the orderer .. two min timeout is set .
```
02:48:41 Mar 04, 2017 2:48:41 AM io.grpc.internal.ManagedChannelImpl
rickr (Sat, 04 Mar 2017 03:19:34 GMT):
@muralisr ^^
rickr (Sat, 04 Mar 2017 03:32:39 GMT):
```
2:48:23
02:48:23 -------------------------------------------------------
02:48:23 T E S T S
02:48:23 -------------------------------------------------------
02:48:23 Running org.hyperledger.fabric.sdkintegration.End2endIT
02:48:25 Mar 04, 2017 2:48:25 AM io.grpc.internal.ManagedChannelImpl
rickr (Sat, 04 Mar 2017 03:33:20 GMT):
docker log https://jenkins.hyperledger.org/job/fabric-sdk-java-verify-x86_64/209/artifact/src/test/fixture/src/dockerlogfile.log
dave.enyeart (Sat, 04 Mar 2017 03:53:08 GMT):
@rahulhegde A release has not been cut yet, therefore all master changes already marked as Merged in gerrit will be included in next release (including the changes you highlighted)
czar0 (Sat, 04 Mar 2017 11:22:35 GMT):
Has joined the channel.
rickr (Sat, 04 Mar 2017 12:05:37 GMT):
when I'm using the configtx tool with SampleSingleMSPSolo profile I see addresses like 127.0.0.1 addresses `AnchorPeers:[map[Host:127.0.0.1 Port:7051]`
how does that work in docker ?
yacovm (Sat, 04 Mar 2017 12:14:00 GMT):
@rickr just use `peer0:7051`, etc.
rahulhegde (Sat, 04 Mar 2017 12:33:48 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=raWPxALKM88XNaiPh) @dave.enyeart
rahulhegde (Sat, 04 Mar 2017 12:33:48 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=raWPxALKM88XNaiPh) @dave.enyeart so if I have to check the status myself https://gerrit.hyperledger.org/r/#/q/Fab-2560 merged and updated is something I need to pick up.
rahulhegde (Sat, 04 Mar 2017 12:33:48 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=raWPxALKM88XNaiPh) @dave.enyeart. Thanks for the update. So if I have to check the status myself https://gerrit.hyperledger.org/r/#/q/Fab-2560 merged and updated column value, I need to pick up.
rahulhegde (Sat, 04 Mar 2017 12:33:48 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=raWPxALKM88XNaiPh) @dave.enyeart Thank you for the update. So if I have to check the status myself https://gerrit.hyperledger.org/r/#/q/Fab-2560 merged and updated column value, I need to pick up.
rahulhegde (Sat, 04 Mar 2017 12:33:48 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=raWPxALKM88XNaiPh) @dave.enyeart Thank you for the update. So if I have to check the status myself https://gerrit.hyperledger.org/r/#/q/Fab-2560 merged and updated column value for master branch, I need to pick up.
muralisr (Sat, 04 Mar 2017 13:41:43 GMT):
@rickr `02:48:41 INFO: [ManagedChannelImpl@66c61024] Created with target localhost:7050` ....localhost is not reachable address
muralisr (Sat, 04 Mar 2017 13:41:43 GMT):
@rickr `02:48:41 INFO: [ManagedChannelImpl@66c61024] Created with target localhost:7050` ....localhost is not reachable address across docker containers
muralisr (Sat, 04 Mar 2017 13:41:51 GMT):
suspect a configuration issue
rickr (Sat, 04 Mar 2017 13:44:28 GMT):
where is that log snippet from ?
muralisr (Sat, 04 Mar 2017 13:44:53 GMT):
```02:48:41 Mar 04, 2017 2:48:41 AM io.grpc.internal.ManagedChannelImpl
rickr (Sat, 04 Mar 2017 13:46:36 GMT):
is that what I mentioned with how the genesis block is created with 127.0.0.1 addresses
rickr (Sat, 04 Mar 2017 13:51:29 GMT):
Our config has not changed verify build was working. The addresses were reachable for installing and send the initiate proposoal . The timeout occured waiting for the eventhub to send us the block with the transaction id as completed
rickr (Sat, 04 Mar 2017 13:53:22 GMT):
FYI need to be away for couple of hours .. This is either the issue above with genesis block having 127.. addresses or another bug server side issue
rickr (Sat, 04 Mar 2017 13:55:13 GMT):
There was also no connection error for sending the transaction to the Orderer
rickr (Sat, 04 Mar 2017 13:57:58 GMT):
```[32mvp0_1 |[0m [31m2017-03-04 02:48:29.109 UTC [deliveryClient] NewDeliverService -> ERRO 2cc[0m Cannot dial to 127.0.0.1:7050, because of grpc: timed out when dialing```
rickr (Sat, 04 Mar 2017 13:58:48 GMT):
gotta go ...
rameshthoomu (Sat, 04 Mar 2017 15:51:34 GMT):
@muralisr : Successfully executed end-to-end (CLI) jobs with non-default channelID on all three platforms (x, p and z).. Observed end-to-end (node) and end-to-end (java) tests are failing with default channelID.
muralisr (Sat, 04 Mar 2017 15:52:42 GMT):
Thanks @rameshthoomu what is the commit level please ?
rameshthoomu (Sat, 04 Mar 2017 15:52:55 GMT):
sure.. will provide
rameshthoomu (Sat, 04 Mar 2017 15:52:55 GMT):
end-to-end (CLI) with non-default channel ID is on below commits
`====> FABRIC COMMIT NUMBER 2724ba4 ====> FABRIC CA COMMIT NUMBER - 3021231 `
and end-to-end (node) and end-to-end (java) are failing on below commits
`====> FABRIC COMMIT NUMBER 2724ba4 ====> FABRIC CA COMMIT NUMBER - 3021231 ========> FABRIC JAVA COMMIT NUMBER - c0dd14b =========> FABRIC NODE COMMIT NUMBER - d99495f.. Refer FAB issue# FAB-2623 for more updates on the sdk failures
rameshthoomu (Sat, 04 Mar 2017 15:52:55 GMT):
end-to-end (CLI) with non-default channel ID is on below commits
`====> FABRIC COMMIT NUMBER 2724ba4 ====> FABRIC CA COMMIT NUMBER - 3021231 `
and end-to-end (node) and end-to-end (java) are failing on below commits
`====> FABRIC COMMIT NUMBER 2724ba4 ====> FABRIC CA COMMIT NUMBER - 3021231 ========> FABRIC JAVA COMMIT NUMBER - c0dd14b =========> FABRIC NODE COMMIT NUMBER - d99495f`.. Refer FAB issue# FAB-2623 for more updates on the sdk failures
rameshthoomu (Sat, 04 Mar 2017 15:55:10 GMT):
====> FABRIC COMMIT NUMBER 2724ba4 ====> FABRIC CA COMMIT NUMBER - 3021231
muralisr (Sat, 04 Mar 2017 16:14:32 GMT):
@rameshthoomu thanks
muralisr (Sat, 04 Mar 2017 16:19:07 GMT):
a quick status update - (1) end to end tests with channel create/join works (2) using testchainid (ie, starting without `--peer-defaultchainid` as in `peer node start` works in non-docker (for example, vagrant) environments where orderer is reachable on 127.0.0.1 (3) using testchainid in docker needs a orderer-endpoint info to be supplied and is being worked under https://gerrit.hyperledger.org/r/#/c/6821/
muralisr (Sat, 04 Mar 2017 16:19:07 GMT):
a quick status update - (1) end to end tests with channel create/join works (2) using testchainid (ie, starting without `--peer-defaultchainid` as in `peer node start` works in non-docker (for example, vagrant) environments where orderer is reachable on 127.0.0.1 works (3) using testchainid in docker needs a orderer-endpoint info to be supplied and is being worked under https://gerrit.hyperledger.org/r/#/c/6821/
muralisr (Sat, 04 Mar 2017 16:26:01 GMT):
the node and java CI tests depend upon (3) and hence fail
ManjeetGambhir (Sat, 04 Mar 2017 19:45:21 GMT):
@rameshthoomu Ramesh any idea about fabric and Fabric-ca images with Java sdk working , will be available ?
muralisr (Sat, 04 Mar 2017 20:39:42 GMT):
@ManjeetGambhir see that https://gerrit.hyperledger.org/r/#/c/6821 is up for review
muralisr (Sat, 04 Mar 2017 20:39:49 GMT):
checking it out as we speak
muralisr (Sat, 04 Mar 2017 20:40:00 GMT):
stay tuned please
rickr (Sat, 04 Mar 2017 20:51:51 GMT):
https://gerrit.hyperledger.org/r/#/c/6823/
Passess verify
End2end no longer uses testchainid
configtx files were update for Docker image
https://jpst.it/ULeA
rickr (Sat, 04 Mar 2017 20:51:51 GMT):
https://gerrit.hyperledger.org/r/#/c/6823/
Passess verify
End2end no longer uses testchainid
configtx files were update for Docker image
configtx.yaml https://jpst.it/ULeA
rickr (Sat, 04 Mar 2017 20:51:51 GMT):
https://gerrit.hyperledger.org/r/#/c/6823/
Passess verify
End2end no longer uses testchainid
configtx files were updated for Docker image
configtx.yaml https://jpst.it/ULeA
rickr (Sat, 04 Mar 2017 20:51:58 GMT):
Message Attachments
ManjeetGambhir (Sat, 04 Mar 2017 21:45:33 GMT):
@muralisr thanks. Keeping eye on your image post
muralisr (Sat, 04 Mar 2017 21:56:12 GMT):
@rickr are you suggesting we use this for CI ?
muralisr (Sat, 04 Mar 2017 21:56:12 GMT):
@rickr are you suggesting we use 6823 for CI ?
rickr (Sat, 04 Mar 2017 22:24:25 GMT):
Not sure how we want to proceed but moved off soon deprecated `testchaiId` and once I fixed configtx block as I pointed to as not being right java sdk is creating and joining peers
muralisr (Sat, 04 Mar 2017 22:25:29 GMT):
I think using channel bar is a better test than using `testchainid`
muralisr (Sat, 04 Mar 2017 22:26:31 GMT):
the fact we ran into trouble with the later was not due to a bug but just that it was tailored for dev envs than docker/CI
rameshthoomu (Sat, 04 Mar 2017 23:09:05 GMT):
@muralisr @rickr : Tested and verified patch https://gerrit.hyperledger.org/r/#/c/6823 in CI on `FABRIC_COMMIT=5b48469` and `FABRIC CA COMMIT= 3021231`
Here is the build reference: https://jenkins.hyperledger.org/sandbox/job/behave_latest/3
rameshthoomu (Sat, 04 Mar 2017 23:09:05 GMT):
@muralisr @rickr : Tested and verified patch https://gerrit.hyperledger.org/r/#/c/6823 in CI on `FABRIC_COMMIT=5b48469` and `FABRIC CA COMMIT= 3021231`
Here is the build reference: https://jenkins.hyperledger.org/sandbox/job/behave_latest/3
rameshthoomu (Sat, 04 Mar 2017 23:09:05 GMT):
@muralisr @rickr : Verified patch https://gerrit.hyperledger.org/r/#/c/6823 in CI on `FABRIC_COMMIT=5b48469` and `FABRIC CA COMMIT= 3021231`
Here is the build reference: https://jenkins.hyperledger.org/sandbox/job/behave_latest/3
ManjeetGambhir (Sat, 04 Mar 2017 23:30:53 GMT):
@rameshthoomu is above mentioned build compatible with fabric java sdk?
muralisr (Sat, 04 Mar 2017 23:33:48 GMT):
@ManjeetGambhir it is
ManjeetGambhir (Sat, 04 Mar 2017 23:34:44 GMT):
@muralisr can we download dockers images for fabric and fabric_ca?
rameshthoomu (Sat, 04 Mar 2017 23:36:32 GMT):
@ManjeetGambhir I have to publish them.. Once #6823 is merged.. will publish
ManjeetGambhir (Sat, 04 Mar 2017 23:38:06 GMT):
@rameshthoomu thanks..will wait for your next post
rameshthoomu (Sat, 04 Mar 2017 23:39:17 GMT):
sure. Will update here..
muralisr (Sat, 04 Mar 2017 23:53:35 GMT):
@ManjeetGambhir with https://gerrit.hyperledger.org/r/#/c/6821 in and with the right configuration, CI should pass for all e2e tests, node, java and base
muralisr (Sat, 04 Mar 2017 23:53:55 GMT):
@rameshthoomu can you update when ready please ?
muralisr (Sat, 04 Mar 2017 23:54:01 GMT):
I need to step out for a bit
ManjeetGambhir (Sat, 04 Mar 2017 23:54:26 GMT):
@muralisr thanks
rameshthoomu (Sat, 04 Mar 2017 23:59:30 GMT):
sure... I am on it.. Will update the status in sometime..
ManjeetGambhir (Sun, 05 Mar 2017 00:46:24 GMT):
@rameshthoomu any eta ?
rameshthoomu (Sun, 05 Mar 2017 00:48:21 GMT):
All, Docker Images are being published on below commits
`====> FABRIC PEER COMMIT# 509d8ed ====> FABRIC CA COMMIT# f18b6b7 ====> FABRIC SDK NODE COMMIT# d99495f ===> FABRIC SDK JAVA COMMIT# c0dd14b`
```
rameshthoomu/fabric-orderer-x86_64:x86_64-0.7.0-snapshot-509d8ed
rameshthoomu/fabric-peer-x86_64:x86_64-0.7.0-snapshot-509d8ed
rameshthoomu/fabric-javaenv-x86_64:x86_64-0.7.0-snapshot-509d8ed
rameshthoomu/fabric-ccenv-x86_64:x86_64-0.7.0-snapshot-509d8ed
rameshthoomu/fabric-ca-x86_64:x86_64-0.7.0-snapshot-f18b6b7
Docker images for "Power" and "System z" are also available by modifying the last component in the repository based on the desired architecture. The above images represent the Intel versions.
Intel = x86_64
Power = ppc64le
System z = s390x
```
The images are also saved with the tag of : *latest*
rameshthoomu (Sun, 05 Mar 2017 00:48:21 GMT):
All, Docker Images are being published on below commits.. end-to-end (CLI) , end-to-end (node) and end-to-end (Java) tests are working as expected on below commits.
`====> FABRIC PEER COMMIT# 509d8ed ====> FABRIC CA COMMIT# f18b6b7 ====> FABRIC SDK NODE COMMIT# d99495f ===> FABRIC SDK JAVA COMMIT# c0dd14b`
```
rameshthoomu/fabric-orderer-x86_64:x86_64-0.7.0-snapshot-509d8ed
rameshthoomu/fabric-peer-x86_64:x86_64-0.7.0-snapshot-509d8ed
rameshthoomu/fabric-javaenv-x86_64:x86_64-0.7.0-snapshot-509d8ed
rameshthoomu/fabric-ccenv-x86_64:x86_64-0.7.0-snapshot-509d8ed
rameshthoomu/fabric-ca-x86_64:x86_64-0.7.0-snapshot-f18b6b7
Docker images for "Power" and "System z" are also available by modifying the last component in the repository based on the desired architecture. The above images represent the Intel versions.
Intel = x86_64
Power = ppc64le
System z = s390x
```
The images are also saved with the tag of : *latest*
rameshthoomu (Sun, 05 Mar 2017 00:48:21 GMT):
All, Docker Images are being published on below commits.. end-to-end (CLI) , end-to-end (node) tests are working as expected on below commits. We see JAVA SDK end-to-end tests are failing..
`====> FABRIC PEER COMMIT# 23872a2 ====> FABRIC CA COMMIT# cd8802b ====> FABRIC SDK NODE COMMIT# 6e792c5 ===> FABRIC SDK JAVA COMMIT# 0d0a3b8 (FAILED)`
```
rameshthoomu/fabric-orderer-x86_64:x86_64-0.7.0-snapshot-23872a2
rameshthoomu/fabric-peer-x86_64:x86_64-0.7.0-snapshot-23872a2
rameshthoomu/fabric-javaenv-x86_64:x86_64-0.7.0-snapshot-23872a2
rameshthoomu/fabric-ccenv-x86_64:x86_64-0.7.0-snapshot-23872a2
rameshthoomu/fabric-ca-x86_64:x86_64-0.7.0-snapshot-cd8802b
Docker images for "Power" and "System z" are also available by modifying the last component in the repository based on the desired architecture. The above images represent the Intel versions.
Intel = x86_64
Power = ppc64le
System z = s390x
```
The images are also saved with the tag of : *latest*
ManjeetGambhir (Sun, 05 Mar 2017 00:57:08 GMT):
@rameshthoomu thanks
rahulhegde (Sun, 05 Mar 2017 19:55:28 GMT):
I am having problem in running e2e_cli with March 4th images. Creation of channel passes however the peer join fails.
` ./network_setup.sh up `
```
ff\xe2}\xd5q\xa0\x1f\x1a\x19\x02 \x1e\xaf\x8d\x13\x1b\xa6-R\u007f/\xed_\xe9\a\xfd5\x93\f\x1d\xf7Ũ\x9a\xe4C\xa2+\xd8\xcb gu" >metadata:
rahulhegde (Sun, 05 Mar 2017 19:55:28 GMT):
I am having problem in running e2e_cli with March 4th images. Creation of channel passes however the peer join fails.
` ./network_setup.sh up `
```
ff\xe2}\xd5q\xa0\x1f\x1a\x19\x02 \x1e\xaf\x8d\x13\x1b\xa6-R\u007f/\xed_\xe9\a\xfd5\x93\f\x1d\xf7Ũ\x9a\xe4C\xa2+\xd8\xcb gu" >metadata:
rahulhegde (Sun, 05 Mar 2017 19:55:28 GMT):
I am having problem in running e2e_cli with March 4th images. Creation of channel passes however the peer join fails.
` ./network_setup.sh up `
```
ff\xe2}\xd5q\xa0\x1f\x1a\x19\x02 \x1e\xaf\x8d\x13\x1b\xa6-R\u007f/\xed_\xe9\a\xfd5\x93\f\x1d\xf7Ũ\x9a\xe4C\xa2+\xd8\xcb gu" >metadata:
rahulhegde (Sun, 05 Mar 2017 20:01:59 GMT):
@rameshthoomu, @weeds - Do we have docker-composer file which uses couch-db as state-ledger for the latest build (4th March). SF Hackfest images were supported with couch-db and since our work is centric with couch-db, we would like to have it.
rameshthoomu (Sun, 05 Mar 2017 20:51:10 GMT):
@rahulhegde join channel worked for me on Mar 4th images..
rahulhegde (Sun, 05 Mar 2017 20:52:17 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=HhWWud8G9EQohKuX6) @rameshthoomu Can you help me identify the problem?
rameshthoomu (Sun, 05 Mar 2017 20:52:37 GMT):
could you please share me peer log file..
rahulhegde (Sun, 05 Mar 2017 20:53:02 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=JjZ4tudzP6xPL5w7A) @rameshthoomu sure.
rahulhegde (Sun, 05 Mar 2017 20:53:02 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=JjZ4tudzP6xPL5w7A) @rameshthoomu sure. Is there debug level - I need to set to get the logs as docker logs peer0 is empty - I am seeing this first time?
rahulhegde (Sun, 05 Mar 2017 20:55:22 GMT):
I am ` docker log ` command giving no logs.
rahulhegde (Sun, 05 Mar 2017 20:55:22 GMT):
I am mean ` docker log ` command giving no logs.
rahulhegde (Sun, 05 Mar 2017 20:55:22 GMT):
I am mean ` docker logs peer0 ` command giving no logs.
rahulhegde (Sun, 05 Mar 2017 20:55:22 GMT):
I mean ` docker logs peer0 ` command giving no logs.
rameshthoomu (Sun, 05 Mar 2017 20:55:56 GMT):
`docker logs -f peer0`
rahulhegde (Sun, 05 Mar 2017 20:56:44 GMT):
```
developer@rahul-Inspiron-3442:~/workspace/playtime/go-workspace/src/github.com/hyperledger/fabric/examples/e2e_cli$ docker-compose -f docker-compose.yaml ps
WARNING: The CHANNEL_NAME variable is not set. Defaulting to a blank string.
Name Command State Ports
---------------------------------------------------------------------------------------------------
cli /bin/bash -c ./scripts/scr ... Up
orderer orderer Up 0.0.0.0:7050->7050/tcp
peer0 peer node start --peer-def ... Up 0.0.0.0:7051->7051/tcp, 0.0.0.0:7053->7053/tcp
peer1 peer node start --peer-def ... Up 0.0.0.0:8051->7051/tcp, 0.0.0.0:8053->7053/tcp
peer2 peer node start --peer-def ... Up 0.0.0.0:9051->7051/tcp, 0.0.0.0:9053->7053/tcp
peer3 peer node start --peer-def ... Up 0.0.0.0:10051->7051/tcp, 0.0.0.0:10053->7053/tcp
developer@rahul-Inspiron-3442:~/workspace/playtime/go-workspace/src/github.com/hyperledger/fabric/examples/e2e_cli$ docker logs -f peer0
^C
developer@rahul-Inspiron-3442:~/workspace/playtime/go-workspace/src/github.com/hyperledger/fabric/examples/e2e_cli$ docker logs peer0
developer@rahul-Inspiron-3442:~/workspace/playtime/go-workspace/src/github.com/hyperledger/fabric/examples/e2e_cli$
```
rahulhegde (Sun, 05 Mar 2017 20:56:55 GMT):
am i missing something?
rameshthoomu (Sun, 05 Mar 2017 20:58:18 GMT):
in this setup peer container is setup to error.. ` CORE_LOGGING_LEVEL=ERROR` I think you are not getting any errors in peer
rameshthoomu (Sun, 05 Mar 2017 20:58:18 GMT):
in this setup peer container log level is set to error.. ` CORE_LOGGING_LEVEL=ERROR` I think you are not getting any errors in peer
rahulhegde (Sun, 05 Mar 2017 20:58:53 GMT):
hmm - let me change it to DEBUG in peer yml file
rahulhegde (Sun, 05 Mar 2017 20:59:30 GMT):
and perform ./network_setup.sh up
rameshthoomu (Sun, 05 Mar 2017 20:59:46 GMT):
provide channel name..
rameshthoomu (Sun, 05 Mar 2017 21:00:00 GMT):
`./network_setup.sh up testchannel`
rahulhegde (Sun, 05 Mar 2017 21:00:01 GMT):
mychannel - default
rameshthoomu (Sun, 05 Mar 2017 21:02:11 GMT):
ok you can try that
rahulhegde (Sun, 05 Mar 2017 21:02:36 GMT):
peer logs are just scrolling - how do i pass u logs, is it snapshot?
rahulhegde (Sun, 05 Mar 2017 21:02:54 GMT):
i have used testchannel.
rahulhegde (Sun, 05 Mar 2017 21:03:33 GMT):
should i pass it over here - by redirecting the log to a file?
rameshthoomu (Sun, 05 Mar 2017 21:03:58 GMT):
yes that's better..
rahulhegde (Sun, 05 Mar 2017 21:04:05 GMT):
ok
rameshthoomu (Sun, 05 Mar 2017 21:04:06 GMT):
rocket chat support .txt format..
rameshthoomu (Sun, 05 Mar 2017 21:04:14 GMT):
DM me the log files
rahulhegde (Sun, 05 Mar 2017 21:06:12 GMT):
and has the limit of 2mb :)
rahulhegde (Sun, 05 Mar 2017 21:07:39 GMT):
Message Attachments
rameshthoomu (Sun, 05 Mar 2017 21:07:54 GMT):
ok
rahulhegde (Sun, 05 Mar 2017 21:08:00 GMT):
I have tgz that file, so u will have tar -zxvf.
rahulhegde (Sun, 05 Mar 2017 21:11:53 GMT):
This is error i see on the Peer CLI
```
2017-03-05 21:00:46.851 UTC [msp] Sign -> DEBU 005 Sign: digest: 6248FD9E5D3FFFB8E58833F4BB501933D6404D162EF67F6D35B0750AF6655B46
Error: proposal failed (err: rpc error: code = 2 desc = Failed to deserialize creator identity, err Expected MSP ID DEFAULT, received Org0MSP)
Usage:
peer channel join [flags]
```
rahulhegde (Sun, 05 Mar 2017 21:12:29 GMT):
is it related to certificate inside channel configuration?
Ratnakar (Sun, 05 Mar 2017 21:13:31 GMT):
Not really sure why PEER is expecting MSP ID as DEFAULT that is wrong . some thing went wrong in the process
Ratnakar (Sun, 05 Mar 2017 21:14:07 GMT):
Not really sure if he hasn't alterered the scripts or any thing
rameshthoomu (Sun, 05 Mar 2017 21:14:32 GMT):
@rahulhegde what changes you have made to the existing setup with the new images?
rahulhegde (Sun, 05 Mar 2017 21:16:34 GMT):
1. I am using https://github.com/hyperledger/fabric/tree/master/examples/e2e_cli
2. Next changed the image tag in docker-composer.yaml to use 4th March fabric-images for orderer, peer and cli.
rahulhegde (Sun, 05 Mar 2017 21:18:03 GMT):
do u want me to print env from any container?
Ratnakar (Sun, 05 Mar 2017 21:25:27 GMT):
@rahulhegde Can you share your docker-compose file ?
If you haven't modified any thing else it should work , I am curious to know if it is any thing to do with docker-compose
rahulhegde (Sun, 05 Mar 2017 21:26:47 GMT):
sure - I will pass it right now.
rahulhegde (Sun, 05 Mar 2017 21:27:33 GMT):
Message Attachments
rahulhegde (Sun, 05 Mar 2017 21:28:08 GMT):
Message Attachments
Ratnakar (Sun, 05 Mar 2017 21:29:54 GMT):
Could you check why the `image: rameshthoomu/fabric-peer-x86_64:x86_64-0.7.0-snapshot-509d8ed` is misising in your base file
rameshthoomu (Sun, 05 Mar 2017 21:29:58 GMT):
I see peer image is pointing to hyperledger
rahulhegde (Sun, 05 Mar 2017 21:31:26 GMT):
hmm :(
rameshthoomu (Sun, 05 Mar 2017 21:32:20 GMT):
That could be the problem..
rahulhegde (Sun, 05 Mar 2017 21:32:23 GMT):
let me give a try - i think I modified some different peer file in e2e.
rameshthoomu (Sun, 05 Mar 2017 21:32:46 GMT):
ok
Ratnakar (Sun, 05 Mar 2017 21:34:37 GMT):
If this doesn't work probably we would need add corresponding cli image as well to match with the TAG
```
ccenv:
container_name: ccenv
build: ./
image: rameshthoomu/fabric-ccenv-x86_64:x86_64-0.7.0-snapshot-509d8ed
```
Ratnakar (Sun, 05 Mar 2017 21:34:37 GMT):
If this doesn't work probably we would need add corresponding `ccenv` image as well to match with the TAG
```
ccenv:
container_name: ccenv
build: ./
image: rameshthoomu/fabric-ccenv-x86_64:x86_64-0.7.0-snapshot-509d8ed
```
Ratnakar (Sun, 05 Mar 2017 21:34:37 GMT):
If this doesn't work probably we would need add corresponding `ccenv` image as well to match with the TAG
```
ccenv:
container_name: ccenv
image: rameshthoomu/fabric-ccenv-x86_64:x86_64-0.7.0-snapshot-509d8ed
```
Ratnakar (Sun, 05 Mar 2017 21:34:37 GMT):
If this doesn't work, probably we would need add corresponding `ccenv` image as well to match with the TAG
```
ccenv:
container_name: ccenv
image: rameshthoomu/fabric-ccenv-x86_64:x86_64-0.7.0-snapshot-509d8ed
```
rahulhegde (Sun, 05 Mar 2017 21:35:58 GMT):
Join is success however instantiate is giving error.
Ratnakar (Sun, 05 Mar 2017 21:36:07 GMT):
not exactly the same .. but with some tweaks
rameshthoomu (Sun, 05 Mar 2017 21:36:16 GMT):
ok try this in docker-compose
``` ccenv_latest:
container_name: ccenv_latest
build: ./ccenv
image: hyperledger/fabric-ccenv:latest
volumes:
- ./ccenv:/opt/gopath/src/github.com/hyperledger/fabric/orderer/ccenv
ccenv_snapshot:
container_name: ccenv_snapshot
build: ./ccenv
image: hyperledger/fabric-ccenv:x86_64-0.7.0-snapshot-509d8ed
volumes:
- ./ccenv:/opt/gopath/src/github.com/hyperledger/fabric/orderer/ccenv
```
Ratnakar (Sun, 05 Mar 2017 21:36:23 GMT):
yeah I shall give a tweak to make it work
rahulhegde (Sun, 05 Mar 2017 21:36:31 GMT):
```
Instantiating chaincode on Peer2/Org1 ...
2017-03-05 21:34:35.368 UTC [logging] InitFromViper -> DEBU 001 Setting default logging level to DEBUG for command 'chaincode'
2017-03-05 21:34:35.407 UTC [msp] GetLocalMSP -> DEBU 002 Returning existing local MSP
2017-03-05 21:34:35.407 UTC [msp] GetDefaultSigningIdentity -> DEBU 003 Obtaining default signing identity
2017-03-05 21:34:35.407 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 004 Using default escc
2017-03-05 21:34:35.408 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 005 Using default vscc
2017-03-05 21:34:35.434 UTC [msp] Sign -> DEBU 006 Sign: plaintext: 0A91050A5B0803220B74657374636861...314D53500A04657363630A0476736363
2017-03-05 21:34:35.434 UTC [msp] Sign -> DEBU 007 Sign: digest: DFB2348419A3FA2BF14952534505CF83991CEDE203574061982642F04E7F2844
Error: Error endorsing chaincode: rpc error: code = 2 desc = Error starting container: Failed to generate platform-specific docker build: Error creating container: no such image
Usage:
peer chaincode instantiate [flags]
```
rameshthoomu (Sun, 05 Mar 2017 21:36:51 GMT):
could be problem with ccenv image..
rahulhegde (Sun, 05 Mar 2017 21:36:53 GMT):
let me check ccenv-image is downloaded
rahulhegde (Sun, 05 Mar 2017 21:37:17 GMT):
sorry confused - do i put above tweak in my composer?
rameshthoomu (Sun, 05 Mar 2017 21:37:29 GMT):
yes
rameshthoomu (Sun, 05 Mar 2017 21:38:38 GMT):
or you can do this `docker tag rameshthoomu/fabric-ccenv-x86_64:x86_64-0.7.0-snapshot-509d8ed hyperledger/fabric-ccenv:x86_64-0.7.0-snapshot-509d8e`
rameshthoomu (Sun, 05 Mar 2017 21:38:38 GMT):
or you can do this `docker tag rameshthoomu/fabric-ccenv-x86_64:x86_64-0.7.0-snapshot-509d8ed hyperledger/fabric-ccenv:x86_64-0.7.0-snapshot-509d8ed`
rahulhegde (Sun, 05 Mar 2017 21:40:44 GMT):
what is ccenv?
rahulhegde (Sun, 05 Mar 2017 21:41:00 GMT):
there is nothing in e2e folder
rahulhegde (Sun, 05 Mar 2017 21:42:24 GMT):
does it do the same thing as tag - by adding a dockerfile as done in SFHackfest?
rameshthoomu (Sun, 05 Mar 2017 21:42:31 GMT):
yes
rahulhegde (Sun, 05 Mar 2017 21:42:52 GMT):
let me take it from sfhackfest and update in that file as
rahulhegde (Sun, 05 Mar 2017 21:43:10 GMT):
FROM hyperledger/fabric-ccenv:x86_64-0.7.0-snapshot-509d8ed
rahulhegde (Sun, 05 Mar 2017 21:43:12 GMT):
?
rameshthoomu (Sun, 05 Mar 2017 21:43:30 GMT):
no `FROM rameshthoomu/fabric-ccenv-x86_64:x86_64-0.7.0-snapshot-509d8ed`
rameshthoomu (Sun, 05 Mar 2017 21:43:34 GMT):
use this
rahulhegde (Sun, 05 Mar 2017 21:43:42 GMT):
ok
rahulhegde (Sun, 05 Mar 2017 21:47:47 GMT):
===================== All GOOD, End-2-End execution completed =====================
rameshthoomu (Sun, 05 Mar 2017 21:49:19 GMT):
will add these instructions in end-to-end readme file
rameshthoomu (Sun, 05 Mar 2017 21:50:17 GMT):
regarding couchdb docker-compose file.. @AdnanC is working on it.. will get back to you tomorrow
AdnanC (Sun, 05 Mar 2017 21:50:17 GMT):
Has joined the channel.
rahulhegde (Sun, 05 Mar 2017 21:51:01 GMT):
First - thank you @rameshthoomu and @Ratnakar for excellent support.
rahulhegde (Sun, 05 Mar 2017 21:51:28 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=gyzpdXPGoXgCfjgRz) @rameshthoomu Ok - do keep us updated.
rameshthoomu (Sun, 05 Mar 2017 21:52:24 GMT):
sure will do..
rahulhegde (Sun, 05 Mar 2017 21:55:14 GMT):
It's ratnakar e2e folder - that's the place i changed first and then i realized - this setup requires compilation of configtxgen. Is there a plan/request, to have fabric-tools image having pre-compiled binaries like configtxgen?
rahulhegde (Sun, 05 Mar 2017 21:55:14 GMT):
It's ratnakar e2e folder - that's the place i changed first and then i realized - this setup requires compilation of configtxgen and forgot to do the same in e2e_cli.
Is there a plan/request, to have fabric-tools image having pre-compiled binaries like configtxgen?
rameshthoomu (Sun, 05 Mar 2017 21:59:07 GMT):
I am not sure on this. but will check with @greg.haskins.. and get back to you..
guoger (Mon, 06 Mar 2017 02:12:24 GMT):
Has joined the channel.
guoger (Mon, 06 Mar 2017 02:13:37 GMT):
Do we produce continuous images from fabric CI? Where can I fetch it?
rahulhegde (Mon, 06 Mar 2017 02:42:59 GMT):
This is first time - we had to transfer fabric-baseos.image to our network to e2e_cli on 4th March; may we know what is this use of this image and is ccenv image not sufficient for building up chaincode docker image?
rahulhegde (Mon, 06 Mar 2017 02:42:59 GMT):
This is first time - we had to transfer fabric-baseos.image to our network to e2e_cli on 4th March; may we know what is this use of this image and is ccenv image not sufficient for building up chaincode docker image?
https://github.com/hyperledger/fabric/blob/master/peer/core.yaml#L305
rahulhegde (Mon, 06 Mar 2017 02:42:59 GMT):
@rameshthoomu This is first time - we had to transfer fabric-baseos.image to our network to e2e_cli on 4th March; may we know what is this use of this image and is ccenv image not sufficient for building up chaincode docker image?
https://github.com/hyperledger/fabric/blob/master/peer/core.yaml#L305
rahulhegde (Mon, 06 Mar 2017 02:42:59 GMT):
@rameshthoomu This is first time - we had to transfer fabric-baseos.image to our network to run e2e_cli using 4th March fabric images; may we know what is this use of this base-os image and why ccenv image is not sufficient for building up chaincode docker image?
I got following reference from peer yml file https://github.com/hyperledger/fabric/blob/master/peer/core.yaml#L305
yong (Mon, 06 Mar 2017 03:16:32 GMT):
root@fu-yong:/opt/gopath/src/github.com/hyperledger/fabric/docs/source# docker-compose -f docker-2peer.yml up
Starting orderer
Starting peer1
Starting peer0
Starting cli
Attaching to orderer, peer0, peer1, cli
orderer | standard_init_linux.go:178: exec user process caused "exec format error"
peer0 | standard_init_linux.go:178: exec user process caused "exec format error"
orderer exited with code 1
peer1 | standard_init_linux.go:178: exec user process caused "exec format error"
peer0 exited with code 1
peer1 exited with code 1
^CGracefully stopping... (press Ctrl+C again to force)
Stopping cli ... done
my docker version：
root@fu-yong:/opt/gopath/src/github.com/hyperledger/fabric/docs/source# docker version
Client:
Version: 17.03.0-ce
API version: 1.26
Go version: go1.7.5
Git commit: 3a232c8
Built: Tue Feb 28 08:01:32 2017
OS/Arch: linux/amd64
Server:
Version: 17.03.0-ce
API version: 1.26 (minimum version 1.12)
Go version: go1.7.5
Git commit: 3a232c8
Built: Tue Feb 28 08:01:32 2017
OS/Arch: linux/amd64
Experimental: false
jimthematrix (Mon, 06 Mar 2017 03:18:19 GMT):
@rameshthoomu @jjjjibm https://jenkins.hyperledger.org/job/fabric-sdk-node-verify-x86_64/626/console, the error seems to indicate a login problem, was the softhsm library in the CI job initialized with a token slot using the expected user pin `98765432`?
jjjjibm (Mon, 06 Mar 2017 03:18:19 GMT):
Has joined the channel.
rameshthoomu (Mon, 06 Mar 2017 03:26:44 GMT):
@jimthematrix yes softhsm2 was installed with that pin in CI environment. and this was done by @vpaprots https://github.com/hyperledger/ci-management/commit/d0ded17a10a0abdb83e8be492abaa342831d13f4#diff-98153cebe3c582dc2f19b7f45714fb71R163
rameshthoomu (Mon, 06 Mar 2017 03:29:13 GMT):
@jjjjibm provided fix for this on friday.. Will test with her change and let you know the update.. I am not sure whether fix is addressing pin related change..
ManjeetGambhir (Mon, 06 Mar 2017 03:41:25 GMT):
@jimthematrix I am using fabric images published and downloaded master java sdk E2EIT but getting below error
ManjeetGambhir (Mon, 06 Mar 2017 03:41:27 GMT):
2017-03-05 22:39:15 ERROR Chain:1011 - Sending proposal to peer failed because of gRPC failure=Status{code=UNKNOWN, description=Failed to deserialize creator identity, err Expected MSP ID Org0MSP, received DEFAULT, cause=null}
java.lang.Exception: io.grpc.StatusRuntimeException: UNKNOWN: Failed to deserialize creator identity, err Expected MSP ID Org0MSP, received DEFAULT
at org.hyperledger.fabric.sdk.Chain.sendProposalToPeers(Chain.java:1011)
at org.hyperledger.fabric.sdk.Chain.sendInstallProposal(Chain.java:882)
at org.hyperledger.fabric.sdkintegration.End2endIT.runChain(End2endIT.java:171)
at org.hyperledger.fabric.sdkintegration.End2endIT.setup(End2endIT.java:117)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:678)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
Caused by: io.grpc.StatusRuntimeException: UNKNOWN: Failed to deserialize creator identity, err Expected MSP ID Org0MSP, received DEFAULT
at io.grpc.Status.asRuntimeException(Status.java:545)
at io.grpc.stub.ClientCalls$UnaryStreamToFuture.onClose(ClientCalls.java:442)
at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.close(ClientCallImpl.java:481)
at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.access$600(ClientCallImpl.java:398)
at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:513)
at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:52)
at io.grpc.internal.SerializingExecutor$TaskRunner.run(SerializingExecutor.java:154)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
ManjeetGambhir (Mon, 06 Mar 2017 03:41:38 GMT):
Any suggestion Jim?
jimthematrix (Mon, 06 Mar 2017 03:45:30 GMT):
@rameshthoomu the library initialization needs to be done before the test could run, so it needs to be part of the CI job build step. The failure above was from the fix that @jjjjibm Uploaded which apparently achieved its purpose of finding the right libpath for the CI environment but failed at the next step of trying to login using the lib
jimthematrix (Mon, 06 Mar 2017 03:48:55 GMT):
@ManjeetGambhir The error is caused by the signing identity using the wrong msp id (has been using the value "DEFAULT"), I believe Rick is looking at this issue right now and we were just chatting about this today
ManjeetGambhir (Mon, 06 Mar 2017 03:49:14 GMT):
Thanks @jimthematrix
ManjeetGambhir (Mon, 06 Mar 2017 12:37:25 GMT):
@rickr when do you think, fix will be available for above error?
weeds (Mon, 06 Mar 2017 12:57:51 GMT):
Hi Manjeet, the test that we finally got to run over the weekend was the standard create initial configuration, isntall and instantiate chaincode, and exercise chaincode using the default MSP Id with fabric_CA, we have not gotten to the next step of looking at the CA that comes from a different vendor. The other thing that still has to be done is a 2nd orderer has to come in. Can we work with what we have today until Rick and Jim get the appropriate fixes in?
weeds (Mon, 06 Mar 2017 12:58:23 GMT):
@ManjeetGambhir ^^
ManjeetGambhir (Mon, 06 Mar 2017 13:06:22 GMT):
@weeds Sharon, Rahul has taken images provided by @rameshthoomu on Saturday and we are using all default setting and running fabric , fabric ca and all supporting images and getting above error by sdk
rickr (Mon, 06 Mar 2017 13:27:47 GMT):
@ManjeetGambhir From the error it appears the sdk is sending an MSPID of DEFAULT which is all we support at the moment. AFAIK the setup we've run against the Fabric (Peer) has only ever expected "DEFAULT" . Not sure why in your setup this is different. May help to get peer logs for this too
ManjeetGambhir (Mon, 06 Mar 2017 13:32:03 GMT):
@rickr if you look ,same error @rahulhegde posted for cli, when tested the images inside environmet.and @rameshthoomu helped him.can you please check @rameshthoomu as well. I saw peer logs but no exception. Will post you the peer logs soon
rickr (Mon, 06 Mar 2017 14:49:21 GMT):
@ManjeetGambhir moving MSPID error to #fabric-sdk-java channel please
rahulhegde (Mon, 06 Mar 2017 15:56:22 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=fG9Rok5oRMxfXvR9F) @rahulhegde @rameshthoomu
Reposting if this was missed in the chat.
jjjjibm (Mon, 06 Mar 2017 16:49:39 GMT):
@jimthematrix, I can't find the old joblog now, but when I read it Saturday, it seemed it could not find any library. I just pushed some inspection rework into Gerrit so I will soon have a new joblog to look at.
jjjjibm (Mon, 06 Mar 2017 16:55:14 GMT):
@jimthematrix Inspecting the new job log .. I stand corrected. It found /usr/lib/x86_64-linux-gnu/softhsm/libsofthsm2.so
jjjjibm (Mon, 06 Mar 2017 18:07:00 GMT):
@jimthematrix @rameshthoomu I am going to see if I can replicate this on my '06' VM
jjjjibm (Mon, 06 Mar 2017 18:07:43 GMT):
It works fine on my 1.0 VM, but I used a different install method for softhsm2 on my 1.0 VM
jjjjibm (Mon, 06 Mar 2017 18:33:26 GMT):
@rameshthoomu @jimthematrix ibmadmin@jcw06NodeSDK:/$ sudo apt-get -qq install -y softhsm2
[sudo] password for ibmadmin:
E: Unable to locate package softhsm2
ibmadmin@jcw06NodeSDK:/$
jjjjibm (Mon, 06 Mar 2017 18:33:29 GMT):
hmmmn
ManjeetGambhir (Mon, 06 Mar 2017 19:28:14 GMT):
@rameshthoomu thanks Ramesh for helping ..Now e2e with default MSP is working
ManjeetGambhir (Mon, 06 Mar 2017 19:29:09 GMT):
@weeds @jimthematrix @muralisr @rickr thanks everyone for support to run Java e2e
jjjjibm (Mon, 06 Mar 2017 20:54:42 GMT):
@rameshthoomu @jimthematrix I cannot recreate on either vagrant vm or my Ubuntu .6 VM. How can I inspect the output of softhsm2-util --init-token --slot 0 --label "ForFabric" --so-pin 1234 --pin 98765432 ?
rahulhegde (Mon, 06 Mar 2017 22:12:34 GMT):
@rameshthoomu I see in e2e_cli, we have used ORDERER_IP, do i need to change any docker composer configuration so it can start using service name - orderer, I cannot use it now?
rahulhegde (Mon, 06 Mar 2017 22:14:13 GMT):
Is this a defect?
```
CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peer/peer1/localMspConfig CORE_PEER_ADDRESS=peer1:7051 CORE_PEER_LOCALMSPID=Org1MSP peer chaincode invoke -o 172.23.0.3:7050 -C mychannel -n mycc -c '{"Args":["query","a"]}'
2017-03-06 22:07:53.983 UTC [msp] Sign -> DEBU 007 Sign: digest: 0AAB0BAB361194E6159C42036D5847A3022F890688942A8937ECD8D325617E90
2017-03-06 22:07:53.984 UTC [chaincodeCmd] chaincodeInvokeOrQuery -> INFO 008 Invoke result: version:1 response:
rahulhegde (Mon, 06 Mar 2017 22:18:42 GMT):
3. Can I get the documentation for ` -P "OR('Org0MSP.member','Org1MSP.member')" ` sent as part of chaincode instantiate?
Should the instantiation fails with -P AND (a replace for OR) option if the chaincode is not installed on one of the organization?
rahulhegde (Mon, 06 Mar 2017 22:18:42 GMT):
3.
* Can I get the documentation for ` -P "OR('Org0MSP.member','Org1MSP.member')" ` sent as part of chaincode instantiate?
* Should the instantiation fails with -P AND (a replace for OR) option if the chaincode is not installed on one of the organization?
* Currently -P option is only supported for instantiate and I hope this will also be supported for invoke?
rahulhegde (Mon, 06 Mar 2017 22:24:02 GMT):
A typo noticed on E2E_CLI, PEER3_IP queries peer2 node information however this variable is only used for printing - https://github.com/hyperledger/fabric/blob/master/examples/e2e_cli/scripts/script.sh#L8
rameshthoomu (Mon, 06 Mar 2017 22:32:12 GMT):
@muralisr @Ratnakar need your inputs on these questions?
muralisr (Mon, 06 Mar 2017 22:32:20 GMT):
@rahulhegde let's take non CI questions for fabric-* please ? ... I'll answer the 3 questions here for now
muralisr (Mon, 06 Mar 2017 22:32:40 GMT):
docs / source / endorsement-policies.rst has documentation on endorsement policies
muralisr (Mon, 06 Mar 2017 22:33:17 GMT):
I'd expect to validation to fail if you required 2 signatures but sent TX with only one endorsement
muralisr (Mon, 06 Mar 2017 22:34:02 GMT):
-P on instantiate basically says "all invokes to this instantiated chaincode on this channel should use this policy"
muralisr (Mon, 06 Mar 2017 22:34:30 GMT):
(so there's no per-invoke policy)
WeDoIoE (Tue, 07 Mar 2017 00:15:58 GMT):
Has joined the channel.
rahulhegde (Tue, 07 Mar 2017 01:38:10 GMT):
@AdnanC @rameshthoomu Can we get an update on the docker-composer file that will use couch-db.
AdnanC (Tue, 07 Mar 2017 02:19:00 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=pe3QwBQB8i5dD8BKG) @rahulhegde I am working on it, we are also making some security changes to couchdb, should submit for review tonight or tomorrow.
rahulhegde (Tue, 07 Mar 2017 03:00:54 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=Afd2HzKRrsLSF5wGa) @AdnanC Thanks for the update, hoping to get the reviewed copy by tomorrow.
rahulhegde (Tue, 07 Mar 2017 03:01:51 GMT):
@greg.haskins - copying on this channel - CI passed Fabric-Images of 4th March.
ManjeetGambhir (Tue, 07 Mar 2017 03:53:41 GMT):
@rickr do you know how to get read,write set and proposalrequest in BlockEvent by blocklistener?
ManjeetGambhir (Tue, 07 Mar 2017 03:54:24 GMT):
I can not see from blockevent ,any api to directly get mentioned above
harsha (Tue, 07 Mar 2017 04:13:54 GMT):
Has joined the channel.
VikasJakhar (Tue, 07 Mar 2017 16:33:37 GMT):
Has joined the channel.
rahulhegde (Tue, 07 Mar 2017 22:18:14 GMT):
@rameshthoomu why is the orderer as a service name not working in the e2e_cli example i.e. https://github.com/hyperledger/fabric/blob/master/examples/e2e_cli/scripts/script.sh#L85 ORDERER_IP is used. I tried changing it to orderer as per docker container service name but was not able to connect. I see service name for peer0/1/2/3 works.
Can you help what can i do here?
rahulhegde (Tue, 07 Mar 2017 22:18:14 GMT):
@rameshthoomu why is the orderer as a service name not working in the e2e_cli example i.e. https://github.com/hyperledger/fabric/blob/master/examples/e2e_cli/scripts/script.sh#L85 ORDERER_IP is used. I tried changing it to orderer as per docker container service name but was not able to connect. I see service name for peer0/1/2/3 works.
Can you help on what should be done to resolve it?
Ratnakar (Tue, 07 Mar 2017 22:24:35 GMT):
@rahulhegde we saw in some systems the address is not getting resolved hence we used perl command to get that address and used it instead. This is the docker which is fails to resolve the address I think
Ratnakar (Tue, 07 Mar 2017 22:24:35 GMT):
@rahulhegde we saw in some systems the address is not getting resolved hence we used perl command to get that address and used it instead. This is the docker which fails to resolve the address I think
Ratnakar (Tue, 07 Mar 2017 22:26:34 GMT):
Is this command https://github.com/hyperledger/fabric/blob/master/examples/e2e_cli/scripts/script.sh#L4 not giving the address ?
Ratnakar (Tue, 07 Mar 2017 22:26:34 GMT):
Is this command https://github.com/hyperledger/fabric/blob/master/examples/e2e_cli/scripts/script.sh#L4 not giving you the orderer address ?
rahulhegde (Tue, 07 Mar 2017 22:43:23 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=cave6mx6nQXb8Ns7Y) @Ratnakar It gives me the right IP.
Q - the previous SF-Hackfest images, it was able to resolve the orderer as service name and now the new image aren't. I am using the same OS box for running these fabric-images. However the peer resolution works fine with 4th March Images.
Ratnakar (Tue, 07 Mar 2017 22:54:46 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=Kxa3oRaHLsqhzEEAB) @rahulhegde I think @greg.haskins would be able to help us in understanding what changed building the orderer image in the recent past.
greg.haskins (Tue, 07 Mar 2017 22:56:35 GMT):
can you give me the synopsis of what is working...way to swamped to wade through the chat log but would be happy to help
greg.haskins (Tue, 07 Mar 2017 22:56:35 GMT):
can you give me the synopsis of what isnt working...way to swamped to wade through the chat log but would be happy to help
greg.haskins (Tue, 07 Mar 2017 22:56:35 GMT):
can you give me the synopsis of what isnt working...way too swamped to wade through the chat log but would be happy to help
Ratnakar (Tue, 07 Mar 2017 23:03:28 GMT):
With the sfhackfest images published few weeks ago , with tag `sfhackfest22017/fabric-ca:x86_64-0.7.0-snapshot-6294c57`
orderer address is getting resolved in CLI container , here is the line I am referring `https://github.com/hyperledger/fabric/blob/master/examples/sfhackfest/channel_test.sh#L44`
Where as with latest images the orderer is not getting resolved
ex: https://github.com/hyperledger/fabric/blob/master/examples/e2e_cli/scripts/script.sh#L48, @rahulhegde wanted to avoid using PERL script to fetch the orderer address.
Ratnakar (Tue, 07 Mar 2017 23:03:28 GMT):
@greg.haskins Thankyou
With the sfhackfest images published few weeks ago , with tag `sfhackfest22017/fabric-ca:x86_64-0.7.0-snapshot-6294c57`
orderer address is getting resolved in CLI container , here is the line I am referring `https://github.com/hyperledger/fabric/blob/master/examples/sfhackfest/channel_test.sh#L44`
Where as with latest images the orderer is not getting resolved
ex: https://github.com/hyperledger/fabric/blob/master/examples/e2e_cli/scripts/script.sh#L48, @rahulhegde wanted to avoid using PERL script to fetch the orderer address.
Ratnakar (Tue, 07 Mar 2017 23:03:28 GMT):
@greg.haskins Thankyou
With the sfhackfest images published few weeks ago , with tag `sfhackfest22017/fabric-ca:x86_64-0.7.0-snapshot-6294c57`
orderer address is getting resolved in CLI container , here is the line I am referring https://github.com/hyperledger/fabric/blob/master/examples/sfhackfest/channel_test.sh#L44
Where as with latest images the orderer is not getting resolved
ex: https://github.com/hyperledger/fabric/blob/master/examples/e2e_cli/scripts/script.sh#L48, @rahulhegde wanted to avoid using PERL script to fetch the orderer address.
Ratnakar (Tue, 07 Mar 2017 23:05:37 GMT):
Here is what @rahulhegde says
```
why is the orderer as a service name not working in the e2e_cli example i.e. https://github.com/hyperledger/fabric/blob/master/examples/e2e_cli/scripts/script.sh#L85 ORDERER_IP is used. I tried changing it to orderer as per docker container service name but was not able to connect. I see service name for peer0/1/2/3 works.
```
Ratnakar (Tue, 07 Mar 2017 23:26:09 GMT):
^^ @greg.haskins
greg.haskins (Tue, 07 Mar 2017 23:28:08 GMT):
how is the orderer being launched in relation to the CA?
greg.haskins (Tue, 07 Mar 2017 23:28:36 GMT):
is it all part of a composition?
greg.haskins (Tue, 07 Mar 2017 23:32:10 GMT):
i assume you are talkign about this composition: https://github.com/hyperledger/fabric/blob/master/examples/e2e_cli/docker-compose.yaml ?
rahulhegde (Tue, 07 Mar 2017 23:32:30 GMT):
E2E CLI docker-composer file = https://github.com/hyperledger/fabric/blob/master/examples/e2e_cli/docker-compose.yaml
SF Hackfest docker-composer file = https://github.com/hyperledger/fabric/blob/master/examples/sfhackfest/docker-compose-gettingstarted.yml
greg.haskins (Tue, 07 Mar 2017 23:32:32 GMT):
and the CLI container is having trouble resolving "orderer"
rahulhegde (Tue, 07 Mar 2017 23:33:25 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=bKNYkZFTj495xmeuL) @greg.haskins that's right but peer0/1/2/3 gets resolved.
greg.haskins (Tue, 07 Mar 2017 23:33:36 GMT):
from the cli container?
greg.haskins (Tue, 07 Mar 2017 23:33:40 GMT):
or just in general?
rahulhegde (Tue, 07 Mar 2017 23:33:51 GMT):
That's right - tried from CLI container.
greg.haskins (Tue, 07 Mar 2017 23:33:58 GMT):
hmm, thats odd
greg.haskins (Tue, 07 Mar 2017 23:34:18 GMT):
based on what i see/know, i would expect all of the components expressed in the depends_on statement to be resolvable
greg.haskins (Tue, 07 Mar 2017 23:34:29 GMT):
this isnt a swarm based setup or anything is it?
greg.haskins (Tue, 07 Mar 2017 23:34:43 GMT):
its just vanilla compose running on one host?
rahulhegde (Tue, 07 Mar 2017 23:37:42 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=6ormN3K3a74rnFzLP) @greg.haskins Just 1 host machine.
greg.haskins (Tue, 07 Mar 2017 23:38:28 GMT):
ok...i have to run for a bit...but I would poke around within the CLI container from the bash prompt with things like dig/nslookup
greg.haskins (Tue, 07 Mar 2017 23:38:50 GMT):
afaict, docker should be surfacing "orderer" in a way that it would resolve
rahulhegde (Wed, 08 Mar 2017 12:35:04 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=JkXffNk9Yxrh9EkrG) Hi @AdnanC Do we have the reviewed docker-composer file that uses couch-db
AdnanC (Wed, 08 Mar 2017 13:17:28 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=qxvttNGN7PDh46iJc) @rahulhegde the changest went out for review last night, you can take a look here https://gerrit.hyperledger.org/r/#/c/6947/ it may change upon receiving reviewer comments, but you are welcome to try it out by E.g cherry-picking it.
Suma (Wed, 08 Mar 2017 15:42:30 GMT):
Has joined the channel.
rahulhegde (Wed, 08 Mar 2017 15:47:54 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=NPzNnivpqoZRMYvbg) @AdnanC Thank you for the update.
Q1: I will be good if I just use the docker-composer specifying the couch-db node/service addition (like couchdb0) (https://gerrit.hyperledger.org/r/#/c/6947/3/examples/e2e_cli/docker-compose.yaml) which is similar to SF-Hackfest Images docker-composer file?
Q2: I have the 4th March Fabric-CI Docker-Image; Do I need to update my Fabric-Images, is there any code dependency post-4th March. Can you please check/confirm with Dave?
Q3: You to mention about the security changes - what are these addition?
rahulhegde (Wed, 08 Mar 2017 15:47:54 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=NPzNnivpqoZRMYvbg) @AdnanC
Q1: I will be good if I just use the docker-composer specifying the couch-db node/service addition (like couchdb0) which is similar to SF-Hackfest Images docker-composer file?
Q2: I have the 4th March Fabric-CI Docker-Image; Do I need to update my Fabric-Images, is there any code dependency post-4th March. Can you please check/confirm with Dave?
rahulhegde (Wed, 08 Mar 2017 15:47:54 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=NPzNnivpqoZRMYvbg) @AdnanC
Q1: I will be good if I just use the docker-composer specifying the couch-db node/service addition (like couchdb0) which is similar to SF-Hackfest Images docker-composer file?
Q2: I have the 4th March Fabric-CI Docker-Image; Do I need to update my Fabric-Images, is there any code dependency post-4th March. Can you please check/confirm with Dave?
Q3: You to mention about the security changes - what are these addition?
rahulhegde (Wed, 08 Mar 2017 15:47:54 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=NPzNnivpqoZRMYvbg) @AdnanC
Q1: I will be good if I just use the docker-composer specifying the couch-db node/service addition (like couchdb0) (https://gerrit.hyperledger.org/r/#/c/6947/3/examples/e2e_cli/docker-compose.yaml) which is similar to SF-Hackfest Images docker-composer file?
Q2: I have the 4th March Fabric-CI Docker-Image; Do I need to update my Fabric-Images, is there any code dependency post-4th March. Can you please check/confirm with Dave?
Q3: You to mention about the security changes - what are these addition?
AdnanC (Wed, 08 Mar 2017 15:52:35 GMT):
@rahulhegde Q1: yes, if, in the docker-compose file, you add the couch containers and add the necessary environmentr variables in peer, you should be good to go. In other words, you can uncomment all the comments from 6947 patchset docker-compose file and it should work. You will have to to `make couchdb` though as a part of prerequisite.
AdnanC (Wed, 08 Mar 2017 15:52:35 GMT):
@rahulhegde Q1: yes, if, in the docker-compose file, you add the couch containers and add the necessary environmentr variables in peer, you should be good to go. In other words, you can uncomment all the comments from 6947 patchset docker-compose file and it should work
AdnanC (Wed, 08 Mar 2017 15:54:45 GMT):
Q2, I am willing to say it should work, but let me check with @dave.enyeart
rahulhegde (Wed, 08 Mar 2017 15:59:06 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=rPEqpaMMYbgCgZn9c) @AdnanC
Oh I didn't see ` make couchdb ` - can I use the klaemo/couchdb which was used as part of SF Hackfest?
AdnanC (Wed, 08 Mar 2017 16:02:12 GMT):
@rahulhegde We recommend using the fabric-couchdb, its pretty similar to klaemo-couchDB with some extra configs for security and compatibility
rahulhegde (Wed, 08 Mar 2017 16:18:23 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=9tmdwhGNdR4xPKoD9) @AdnanC - Not sure of the response - however we always wait on the fabric-CI channel to provide images. Looks like this might now take some more time, if Klaemo/couch image is not compatible.
May be if you can add a note on compatibility with klaemo/couch-db (1 more point to be discussed with Dave?).
Let us know Dave' view on the compatibility with th March Fabric-CI image - Point 2.
AdnanC (Wed, 08 Mar 2017 16:26:46 GMT):
@rahulhegde I will talk with @rameshthoomu on means of providing the fabric-couchdb image. Fabric has been using the fabric-couchdb instead of klaemo-couchdb for unit-testing, and the fabric developer tools will also use fabric-couchdb moving forward (change waiting to get merged). And I will get reconfitmation from Dave.
dave.enyeart (Wed, 08 Mar 2017 16:36:24 GMT):
@rahulhegde Latest updates should be compatible with March 4th (although we cant guarantee compatibility with prior images in general, in this case it looks ok)
dave.enyeart (Wed, 08 Mar 2017 16:36:52 GMT):
You can use either klaemo-couchdb or fabric-couchdb, there is no significant difference
dave.enyeart (Wed, 08 Mar 2017 16:37:37 GMT):
some minor config differences, you should get slightly better performance on fabric-couchdb, but both are equally functinoal
dave.enyeart (Wed, 08 Mar 2017 16:37:37 GMT):
some minor config differences, you should get slightly better performance on fabric-couchdb, but both are equally functional
rahulhegde (Wed, 08 Mar 2017 16:47:34 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=9mE4FdsLBLAYWAZMu) @dave.enyeart
That' nice @dave.enyeart - I will use the klaemo/couch db, Thanks @AdnanC. I will give a try and ping you if there is any help required.
rahulhegde (Wed, 08 Mar 2017 16:47:34 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=9mE4FdsLBLAYWAZMu) @dave.enyeart
That' nice @dave.enyeart - I will use the klaemo/couch image, Thanks @AdnanC. I will give a try and ping you if there is any help required.
rameshthoomu (Wed, 08 Mar 2017 22:51:46 GMT):
All, Docker Images are being published on below commits.. end-to-end (CLI) , end-to-end (node) tests are working as expected on below commits.
`====> FABRIC PEER COMMIT# 23872a2 ====> FABRIC CA COMMIT# cd8802b ====> FABRIC SDK NODE COMMIT# 6e792c5 ===> FABRIC SDK JAVA COMMIT# 0d0a3b8 (FAILED)`
```
rameshthoomu/fabric-orderer-x86_64:x86_64-0.7.0-snapshot-23872a2
rameshthoomu/fabric-peer-x86_64:x86_64-0.7.0-snapshot-23872a2
rameshthoomu/fabric-javaenv-x86_64:x86_64-0.7.0-snapshot-23872a2
rameshthoomu/fabric-ccenv-x86_64:x86_64-0.7.0-snapshot-23872a2
rameshthoomu/fabric-ca-x86_64:x86_64-0.7.0-snapshot-cd8802b
Docker images for "Power" and "System z" are also available by modifying the last component in the repository based on the desired architecture. The above images represent the Intel versions.
Intel = x86_64
Power = ppc64le
System z = s390x
```
The images are also saved with the tag of : *latest*
tuand (Wed, 08 Mar 2017 22:55:32 GMT):
what's the `FABRIC SDK JAVA COMMIT# 0d0a3b8 (FAILED)` thing , @rameshthoomu ?
rameshthoomu (Wed, 08 Mar 2017 22:56:36 GMT):
end-to-end (java) tests are failing..
rameshthoomu (Wed, 08 Mar 2017 22:56:36 GMT):
end-to-end (java) tests are failing on latest commit
tuand (Wed, 08 Mar 2017 22:58:41 GMT):
but we're publishing the images anyway ?
rickr (Wed, 08 Mar 2017 23:05:11 GMT):
@tuand Yeah ofcourse who cares about Java!
rameshthoomu (Wed, 08 Mar 2017 23:06:55 GMT):
@rickr @tuand : end-to-end tests are failing from past couple of days and people are asking for images on latest commits.. We publish images every day once all tests pass
tuand (Wed, 08 Mar 2017 23:10:56 GMT):
https://gerrit.hyperledger.org/r/#/c/7029/ takes care of the sdk-java build fails ...
tuand (Wed, 08 Mar 2017 23:13:06 GMT):
somewhat off-topic but since fabric/fabric-ca/fabric-sdk-node/fabric-sdk-java are dependent on each other, can we have end-to-end tests as part of each build ?
rameshthoomu (Wed, 08 Mar 2017 23:17:41 GMT):
yes @tuand; I have submitted patch and it's merged.. https://gerrit.hyperledger.org/r/#/c/6997/
rameshthoomu (Wed, 08 Mar 2017 23:18:02 GMT):
we run these end-to-end tests for every fabric verify and merge commits
tuand (Wed, 08 Mar 2017 23:19:31 GMT):
am i not a good straight man, ramesh ? :D
rameshthoomu (Wed, 08 Mar 2017 23:23:15 GMT):
:) I am working on integrating end-2-end tests on every commit of fabric-ca, fabric-sdk-java and fabric-sdk-node
rahulhegde (Wed, 08 Mar 2017 23:47:54 GMT):
@dave.enyeart @AdnanC
I was able to run the Marbles02 and run d use_index, sort functionality, this is good. Thanks.
Q: This should be couch-db question but if you can help - when we define a index, what's the use of sort field in it?
1 thing - that came during my test - please check if this has to be recorded as defect - whenever a non-existance DesignDocument or IndexName is supplied to the Peer CLI query, the transaction time's out.
```
root@1baa4af83e34:/opt/gopath/src/github.com/hyperledger/fabric/peer# CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peer/peer0/localMspConfig CORE_PEER_ADDRESS=peer0:7051 CORE_PEER_LOCALMSPID=Org0MSP peer chaincode query -o 172.23.0.6:7050 -C mychannel -n marble -c '{"Args":["queryMarbles","{\"selector\":{\"docType\":{\"$eq\":\"marble\"},\"owner\":{\"$eq\":\"rahul\"},\"size\":{\"$gt\":0}},\"fields\":[\"docType\",\"owner\",\"size\"],\"sort\":[{\"size\":\"asc\"}],\"use_index\":\"_design/indexSizeSortDoc1\", \"limit\":4}"]}'
2017-03-08 23:36:45.235 UTC [logging] InitFromViper -> DEBU 001 Setting default logging level to DEBUG for command 'chaincode'
2017-03-08 23:36:45.236 UTC [msp] GetLocalMSP -> DEBU 002 Returning existing local MSP
2017-03-08 23:36:45.236 UTC [msp] GetDefaultSigningIdentity -> DEBU 003 Obtaining default signing identity
2017-03-08 23:36:45.238 UTC [msp] Sign -> DEBU 004 Sign: plaintext: 0A91050A5B080322096D796368616E6E...6F6331222C20226C696D6974223A347D
2017-03-08 23:36:45.238 UTC [msp] Sign -> DEBU 005 Sign: digest: 477EDAC36C05902652744AC51883B8686345A53C874CF4C5C21F0DA26B38E256
Error: Error endorsing query: rpc error: code = 2 desc = Error executing chaincode: Failed to execute transaction (Timeout expired while executing transaction)
```
However the same query on the couch-db database endpoint, return immediately
```
{"error":"unknown_error","reason":"Unknown Error: mango_idx :: {no_usable_index,no_index_matching_name}"}
```
rahulhegde (Wed, 08 Mar 2017 23:47:54 GMT):
@dave.enyeart @AdnanC
I was able to run the Marbles02 and run d use_index, sort functionality, this is good. Thanks.
Q: This should be couch-db question but if you can help - when we define a index, what's the use of sort field in it?
1 thing - that came during my test - please check if this has to be recorded as defect - whenever a non-existance DesignDocument or IndexName is supplied to the Peer CLI query, the transaction time's out.
```
root@1baa4af83e34:/opt/gopath/src/github.com/hyperledger/fabric/peer# CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peer/peer0/localMspConfig CORE_PEER_ADDRESS=peer0:7051 CORE_PEER_LOCALMSPID=Org0MSP peer chaincode query -o 172.23.0.6:7050 -C mychannel -n marble -c '{"Args":["queryMarbles","{\"selector\":{\"docType\":{\"$eq\":\"marble\"},\"owner\":{\"$eq\":\"rahul\"},\"size\":{\"$gt\":0}},\"fields\":[\"docType\",\"owner\",\"size\"],\"sort\":[{\"size\":\"asc\"}],\"use_index\":\"_design/indexSizeSortDoc1\", \"limit\":4}"]}'
2017-03-08 23:36:45.235 UTC [logging] InitFromViper -> DEBU 001 Setting default logging level to DEBUG for command 'chaincode'
2017-03-08 23:36:45.236 UTC [msp] GetLocalMSP -> DEBU 002 Returning existing local MSP
2017-03-08 23:36:45.236 UTC [msp] GetDefaultSigningIdentity -> DEBU 003 Obtaining default signing identity
2017-03-08 23:36:45.238 UTC [msp] Sign -> DEBU 004 Sign: plaintext: 0A91050A5B080322096D796368616E6E...6F6331222C20226C696D6974223A347D
2017-03-08 23:36:45.238 UTC [msp] Sign -> DEBU 005 Sign: digest: 477EDAC36C05902652744AC51883B8686345A53C874CF4C5C21F0DA26B38E256
Error: Error endorsing query: rpc error: code = 2 desc = Error executing chaincode: Failed to execute transaction (Timeout expired while executing transaction)
```
However the same query on the couch-db database endpoint, return immediately
```
{"error":"unknown_error","reason":"Unknown Error: mango_idx :: {no_usable_index,no_index_matching_name}"}
```
dave.enyeart (Thu, 09 Mar 2017 00:23:16 GMT):
@rahulhegde it probably timed out due to retries. Retry logic will be enhanced before v1 GA: https://jira.hyperledger.org/browse/FAB-2709
dave.enyeart (Thu, 09 Mar 2017 00:23:16 GMT):
@rahulhegde it probably timed out due to retries. Retry logic will be enhanced before v1 GA so that expected errors like this don't go into a retry loop: https://jira.hyperledger.org/browse/FAB-2709
dave.enyeart (Thu, 09 Mar 2017 00:23:41 GMT):
You should see the warnings/errors in peer log
dave.enyeart (Thu, 09 Mar 2017 00:29:12 GMT):
Concerning the index question... In order for sorts to work it needs an underlying index with the sort fields defined, to support the sort. Do you have a specific question?
rahulhegde (Thu, 09 Mar 2017 01:59:37 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=hX8yz5DuSSNniHFRJ) @dave.enyeart I have posted it on #fabric-ledger
C0rWin (Thu, 09 Mar 2017 14:38:27 GMT):
I see that there is end-2-end test being connecting to the gerrit and it keeps failing: https://gerrit.hyperledger.org/r/#/c/7009/ and https://jenkins.hyperledger.org/job/fabric-verify-end-2-end-x86_64/19/ while looking into results: https://jenkins.hyperledger.org/job/fabric-verify-end-2-end-x86_64/19/artifact/gopath/src/github.com/hyperledger/fabric/examples/e2e_cli/results.log looks like test passed fine.
```Query Result: 90
2017-03-09 13:14:44.928 UTC [main] main -> INFO 006[0m Exiting.....
===================== Query on PEER3 on channel 'mychannel' is successful =====================
===================== All GOOD, End-2-End execution completed =====================
```
C0rWin (Thu, 09 Mar 2017 14:38:53 GMT):
any reason why this considered as failure?
yury (Thu, 09 Mar 2017 14:50:17 GMT):
Has joined the channel.
yury (Thu, 09 Mar 2017 14:51:38 GMT):
I want to push in gerrit
But I get error
To ssh://gerrit.hyperledger.org:29418/fabric
! [remote rejected] HEAD -> refs/for/master (you are not allowed to upload merges)
error: failed to push some refs to 'ssh://YuryAndreev@gerrit.hyperledger.org:29418/fabric'
I do "git push origin HEAD:refs/for/master"
yury (Thu, 09 Mar 2017 14:51:38 GMT):
I want to push in gerrit, but I get error
To ssh://gerrit.hyperledger.org:29418/fabric
! [remote rejected] HEAD -> refs/for/master (you are not allowed to upload merges)
error: failed to push some refs to 'ssh://YuryAndreev@gerrit.hyperledger.org:29418/fabric'
I do "git push origin HEAD:refs/for/master"
rameshthoomu (Thu, 09 Mar 2017 14:52:32 GMT):
@C0rWin As part of this E2E job, we are verifying `e2e (CLI), e2e (node) and e2e (java)`.. I see java e2e tests are failed in this build https://jenkins.hyperledger.org/job/fabric-verify-end-2-end-x86_64/19/
rameshthoomu (Thu, 09 Mar 2017 14:53:22 GMT):
@yury It seems last commit in your git log is merge commit..
kushnir.grigoriy (Thu, 09 Mar 2017 15:38:18 GMT):
Has joined the channel.
tuand (Thu, 09 Mar 2017 18:24:19 GMT):
hi @rameshthoomu , looks like https://jenkins.hyperledger.org/job/fabric-verify-end-2-end-x86_64/19 did not pick up the sdk-java fix ... commit log says `SDK_JAVA_COMMIT=======> 0d0a3b8` , should have used `61e24bd [FAB-2706] CI always uses latest Fabric/CA`
rameshthoomu (Thu, 09 Mar 2017 18:40:34 GMT):
I see change reflected after build# 20
Senthil1 (Fri, 10 Mar 2017 03:00:40 GMT):
Has joined the channel.
Basug (Fri, 10 Mar 2017 13:20:26 GMT):
Has joined the channel.
Basug (Fri, 10 Mar 2017 15:10:32 GMT):
Is there a docker-compose file for java env for hyperledger 0.6 ?
Basug (Fri, 10 Mar 2017 15:10:40 GMT):
or 0.6.1 preview
rameshthoomu (Fri, 10 Mar 2017 15:14:42 GMT):
All, Docker Images are being published on below commits.. end-to-end (CLI) , end-to-end (NODE) and end-to-end (JAVA) tests are working as expected on below commits.
`====> FABRIC PEER COMMIT# 3295920 ====> FABRIC CA COMMIT# df922a1 ====> FABRIC SDK NODE COMMIT# e2edc9b ===> FABRIC SDK JAVA COMMIT# 9cd3b75`
```
rameshthoomu/fabric-orderer-x86_64:x86_64-0.7.0-snapshot-3295920
rameshthoomu/fabric-peer-x86_64:x86_64-0.7.0-snapshot-3295920
rameshthoomu/fabric-javaenv-x86_64:x86_64-0.7.0-snapshot-3295920
rameshthoomu/fabric-ccenv-x86_64:x86_64-0.7.0-snapshot-3295920
rameshthoomu/fabric-ca-x86_64:x86_64-0.7.0-snapshot-df922a1
Docker images for "Power" and "System z" are also available by modifying the last component in the repository based on the desired architecture. The above images represent the Intel versions.
Intel = x86_64
Power = ppc64le
System z = s390x
```
The images are also saved with the tag of : *latest*
rameshthoomu (Fri, 10 Mar 2017 15:14:42 GMT):
All, Docker Images are being published on below commits.. end-to-end (CLI) , end-to-end (NODE) and end-to-end (JAVA) tests are working as expected on below commits.
`====> FABRIC PEER COMMIT# 3295920 ====> FABRIC CA COMMIT# df922a1 ====> FABRIC SDK NODE COMMIT# e2edc9b ===> FABRIC SDK JAVA COMMIT# 9cd3b75`
```
rameshthoomu/fabric-orderer-x86_64:x86_64-0.7.0-snapshot-3295920
rameshthoomu/fabric-peer-x86_64:x86_64-0.7.0-snapshot-3295920
rameshthoomu/fabric-javaenv-x86_64:x86_64-0.7.0-snapshot-3295920
rameshthoomu/fabric-ccenv-x86_64:x86_64-0.7.0-snapshot-3295920
rameshthoomu/fabric-ca-x86_64:x86_64-0.7.0-snapshot-df922a1
Docker images for "Power" and "System z" are also available by modifying the last component in the repository based on the desired architecture. The above images represent the Intel versions.
Intel = x86_64
Power = ppc64le
System z = s390x
```
The images are also saved with the tag of : *latest*
rameshthoomu (Fri, 10 Mar 2017 15:14:42 GMT):
All, Docker Images are being published on below commits.. end-to-end (CLI) , end-to-end (NODE) and end-to-end (JAVA) tests are working as expected on below commits.
`====> FABRIC PEER COMMIT# 3295920 ====> FABRIC CA COMMIT# df922a1 ====> FABRIC SDK NODE COMMIT# e2edc9b ===> FABRIC SDK JAVA COMMIT# 9cd3b75`
```
rameshthoomu/fabric-orderer-x86_64:x86_64-0.7.0-snapshot-3295920
rameshthoomu/fabric-peer-x86_64:x86_64-0.7.0-snapshot-3295920
rameshthoomu/fabric-javaenv-x86_64:x86_64-0.7.0-snapshot-3295920
rameshthoomu/fabric-ccenv-x86_64:x86_64-0.7.0-snapshot-3295920
rameshthoomu/fabric-couchdb-x86_64:x86_64-0.7.0-snapshot-3295920
rameshthoomu/fabric-ca-x86_64:x86_64-0.7.0-snapshot-df922a1
Docker images for "Power" and "System z" are also available by modifying the last component in the repository based on the desired architecture. The above images represent the Intel versions.
Intel = x86_64
Power = ppc64le
System z = s390x
```
The images are also saved with the tag of : *latest*
JatinderBali (Fri, 10 Mar 2017 15:42:27 GMT):
Has joined the channel.
simsc (Sat, 11 Mar 2017 00:04:00 GMT):
couch db included above
zakir2k (Sat, 11 Mar 2017 06:54:46 GMT):
Has joined the channel.
rahulhegde (Sun, 12 Mar 2017 01:40:14 GMT):
@rameshthoomu I am facing a problem in running the E2E CLI on 10th March Fabric Images. I see my orderer doesn't stand up and gives
```
2017-03-12 01:35:47.514 UTC [common/config] initializeProtosStruct -> DEBU 050 Processing field: CreationPolicy
2017-03-12 01:35:47.514 UTC [orderer/multichain] newLedgerResources -> CRIT 051 Error creating configtx manager and handlers: Error deserializing key IngressPolicyNames for group /Channel/Orderer: Unexpected key IngressPolicyNames
```
VikasJakhar (Sun, 12 Mar 2017 18:14:11 GMT):
Hi..any resolution yet ?
C0rWin (Mon, 13 Mar 2017 08:56:49 GMT):
I'm trying to build a `baseos` and `baseimage` for ARM architecture. Where I can find docker files for these images?
weeds (Mon, 13 Mar 2017 10:42:00 GMT):
@mastersingh24 Hi Gari- I know you were looking at the TLS stuff- Any chance you saw the problem on E2E CLi- or did that get fixed with the latest check in last night? Just curious
weeds (Mon, 13 Mar 2017 10:42:18 GMT):
looking at ^^ @rahulhegde
mastersingh24 (Mon, 13 Mar 2017 10:43:28 GMT):
@C0rWin - https://github.com/hyperledger/fabric-baseimage - but @greg.haskins can probably help more with baseos
mastersingh24 (Mon, 13 Mar 2017 10:44:43 GMT):
@weeds @rahulhegde - I never saw the issues above with the current code
C0rWin (Mon, 13 Mar 2017 11:28:38 GMT):
@mastersingh24 thanks, just figured out the existence of this project :)
C0rWin (Mon, 13 Mar 2017 11:28:51 GMT):
trying to compile new images for ARM architecture
C0rWin (Mon, 13 Mar 2017 11:29:26 GMT):
@greg.haskins wondering whenever this architecture is something we would like to publish on dockerhub?
rahulhegde (Mon, 13 Mar 2017 12:09:34 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=NaiyKfsWc46bx2P3i) @mastersingh24
GM Gari - Is there one who can assist in resolving this issue.
mastersingh24 (Mon, 13 Mar 2017 12:17:07 GMT):
@rahulhegde - I'm not sure how you are setting things up - but perhaps you are using a "block" generated with a prior version of tool to bootstrap the orderer?
greg.haskins (Mon, 13 Mar 2017 12:43:29 GMT):
@C0rWin I would welcome another architecture
greg.haskins (Mon, 13 Mar 2017 12:44:18 GMT):
the only real requirement from my perspective is that someone sponsor a set of workers for jenkins that are reliable/fast enough
greg.haskins (Mon, 13 Mar 2017 12:44:44 GMT):
all of the base* images are built from fabric-baseimage.git
greg.haskins (Mon, 13 Mar 2017 12:44:51 GMT):
just do "make docker" in that repo
greg.haskins (Mon, 13 Mar 2017 12:49:32 GMT):
@C0rWin do note that "make docker" tries to publish the resulting images to dockerhub...use "make docker-local" for a variant that does everything _except_ publish
mastersingh24 (Mon, 13 Mar 2017 12:50:26 GMT):
@greg.haskins - one question - I was trying to figure out where you actually set the base bits for the images - I guess really I'm asking where is moby linux coming from?
greg.haskins (Mon, 13 Mar 2017 12:50:47 GMT):
moby?
mastersingh24 (Mon, 13 Mar 2017 12:51:07 GMT):
in baseos? I know the Docker for Mac uses it as the underlying VM
mastersingh24 (Mon, 13 Mar 2017 12:51:35 GMT):
when I `docker exec` into say fabric-peer I see root@moby
greg.haskins (Mon, 13 Mar 2017 12:51:41 GMT):
not sure how moby factors in, but our baseimage is just based on ubuntu 16.04 (for x86, anyway)
greg.haskins (Mon, 13 Mar 2017 12:51:58 GMT):
i think the Z/P folks swapped that out for something else in the debian family
mastersingh24 (Mon, 13 Mar 2017 12:52:41 GMT):
actually - sorry - I think that was for the chaincode containers
greg.haskins (Mon, 13 Mar 2017 12:52:49 GMT):
thats weird...the docker-for-mac environment must be setting PS1 or something
mastersingh24 (Mon, 13 Mar 2017 12:53:06 GMT):
yeah - that's what I am thinking
mastersingh24 (Mon, 13 Mar 2017 12:53:27 GMT):
I'll investigate in my copious spare time ;)
greg.haskins (Mon, 13 Mar 2017 12:53:29 GMT):
in any case, if you use an upstream build on x86, you are getting ubuntu 16.04 in the containers
greg.haskins (Mon, 13 Mar 2017 12:53:47 GMT):
"baseos" is just a minimal install
mihaig (Mon, 13 Mar 2017 12:56:12 GMT):
Has joined the channel.
C0rWin (Mon, 13 Mar 2017 13:06:12 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=HqrccY6iszrvuQYA8) @greg.haskins I guess my question is, what is the next steps once I've tested images for ARM locally?
greg.haskins (Mon, 13 Mar 2017 13:07:53 GMT):
basically, you need to work with the CI folks like @rjones @jwagantall @rameshthoomu to get ARM builders added to the jenkins worker cluster and also to add ARM to the ci-management JJBs
greg.haskins (Mon, 13 Mar 2017 13:08:33 GMT):
also, if there ends up being changes that you need (for instance, to fabric-baseimage), you can just submit those as normal CRs and I can review them
greg.haskins (Mon, 13 Mar 2017 13:09:33 GMT):
hopefully they are minimal but there are slight variances between X/P/Z so I wouldnt be surprised if ARM has slightly different requirements as well
greg.haskins (Mon, 13 Mar 2017 13:11:19 GMT):
my general attitude is: I would encourage the platform author(s) to stay as close to the x86 base as possible, but ultimately I dont care as long as you are willing to support it and don't break x86 in the process.
greg.haskins (Mon, 13 Mar 2017 13:11:36 GMT):
one thing to keep in mind is that downstream users _will_ expect "apt-get" to work
greg.haskins (Mon, 13 Mar 2017 13:11:59 GMT):
so you are best staying debian/ubuntu centric, else you will open up a whole different can of worms
greg.haskins (Mon, 13 Mar 2017 13:13:45 GMT):
(honestly, we probably need to address the whole reliance on "apt-get" thing...but that is a whole different problem
greg.haskins (Mon, 13 Mar 2017 13:14:22 GMT):
I know folks have expressed interest in making the distro choice configurable
C0rWin (Mon, 13 Mar 2017 13:14:47 GMT):
For now I've just changed the initial platform image w/o any additional changes and looks like I'm able to build it on my RPi device
greg.haskins (Mon, 13 Mar 2017 13:15:01 GMT):
very cool
greg.haskins (Mon, 13 Mar 2017 13:15:24 GMT):
looks like we need an RPi cluster for LF and we are good to go ;)
C0rWin (Mon, 13 Mar 2017 13:15:48 GMT):
>I know folks have expressed interest in making the distro choice configurable
^^^ Is there a way to specify platform for base image I'd like to build locally? with `make docker-local`?
greg.haskins (Mon, 13 Mar 2017 13:16:06 GMT):
its just standard dockerfile stuff
greg.haskins (Mon, 13 Mar 2017 13:16:24 GMT):
theres not a parameter to the build though, no
greg.haskins (Mon, 13 Mar 2017 13:18:13 GMT):
its driven from here:
greg.haskins (Mon, 13 Mar 2017 13:18:14 GMT):
https://github.com/hyperledger/fabric-baseimage/blob/master/Makefile#L11
C0rWin (Mon, 13 Mar 2017 13:29:27 GMT):
great, thanks
C0rWin (Mon, 13 Mar 2017 13:30:48 GMT):
@greg.haskins so I've just added `DOCKER_BASE_armv7l=armv7/armhf-ubuntu`
greg.haskins (Mon, 13 Mar 2017 13:31:45 GMT):
Seems what I expected
rickr (Mon, 13 Mar 2017 13:51:05 GMT):
@jimthematrix FAB2755 fix https://gerrit.hyperledger.org/r/#/c/7157/
antoniovassell (Mon, 13 Mar 2017 16:30:17 GMT):
Has joined the channel.
greg.haskins (Mon, 13 Mar 2017 17:03:22 GMT):
@rameshthoomu @bmos299 this is probably of interest to you: https://gerrit.hyperledger.org/r/#/c/7163/
greg.haskins (Mon, 13 Mar 2017 17:03:53 GMT):
completely untested/WIP at the moment, I just wanted to get it out there since there is activity surrounding alternate docker repos
greg.haskins (Mon, 13 Mar 2017 17:05:09 GMT):
the gist of it is, it would be possible to do something like "DOCKER_NS=myrepo:2343 make docker" and the entire build will be reconfigured to produce images/binaries that use that new namespace
greg.haskins (Mon, 13 Mar 2017 17:05:35 GMT):
e.g. myrepo:2345/fabric-peer instead of hyperledger/fabric-peer
greg.haskins (Mon, 13 Mar 2017 17:06:04 GMT):
i would guess this would be of use to QA/CI primarily
bmos299 (Mon, 13 Mar 2017 17:15:09 GMT):
@greg.haskins @rameshthoomu @binhn @markparz @weeds I have created: https://jira.hyperledger.org/browse/FAB-2764 for publishing images to the community when the CI passes the e2e test with and w/o tls.
dave.enyeart (Mon, 13 Mar 2017 19:01:42 GMT):
@bmos299 and team - A lot of people have been asking how they can try CouchDB. I'd like to get the CouchDB docker extensions to e2e in there prior to publish. Please review: https://gerrit.hyperledger.org/r/#/c/7097/. You'll see that the docker compose is extended with optional (commented out) CouchDB statements. Initially we were going to have a 2nd docker compose for CouchDB enabled environments, but dual maintenance and keeping them in sync looked like it was going to be an issue, therefore we went with the optional/comments approach. I'm open to ideas though.
laprice (Mon, 13 Mar 2017 20:47:48 GMT):
Has joined the channel.
krupabathia (Tue, 14 Mar 2017 12:38:57 GMT):
Has joined the channel.
snehas (Tue, 14 Mar 2017 13:21:53 GMT):
Has joined the channel.
AbhilekhSingh (Tue, 14 Mar 2017 13:23:36 GMT):
Has joined the channel.
wwendy (Tue, 14 Mar 2017 13:47:48 GMT):
Has joined the channel.
hycind (Tue, 14 Mar 2017 19:00:40 GMT):
Has joined the channel.
dhuseby (Tue, 14 Mar 2017 22:54:29 GMT):
Has joined the channel.
snehas (Wed, 15 Mar 2017 06:39:49 GMT):
Hi All,
We are using latest images mentioned below
rameshthoomu/fabric-orderer-x86_64:x86_64-0.7.0-snapshot-3295920
rameshthoomu/fabric-peer-x86_64:x86_64-0.7.0-snapshot-3295920
rameshthoomu/fabric-ccenv-x86_64:x86_64-0.7.0-snapshot-3295920
rameshthoomu/fabric-couchdb-x86_64:x86_64-0.7.0-snapshot-3295920
rameshthoomu/fabric-ca-x86_64:x86_64-0.7.0-snapshot-df922a1
These images are loaded on VM and VM does not have internet connection.
After starting all services. We deployed the chaincode on peer0 and ran following command in CLI container
CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peer/peer0/localMspConfig CORE_PEER_ADDRESS=peer0:7051 CORE_PEER_LOCALMSPID=Org0MSP peer chaincode instantiate -o 172.21.0.2:7050 -C a2bcls -n example04 -v 1.0 -p github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example04 -c '{"Args":["init","eventid","100"]}' -P "OR('Org0MSP.member','Org1MSP.member')"
But getting below error:-
Error: Error endorsing chaincode: rpc error: code = 2 desc = Error starting container: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
Please advice.
mychewcents (Wed, 15 Mar 2017 12:31:19 GMT):
Has joined the channel.
balashevich (Wed, 15 Mar 2017 12:33:31 GMT):
Has joined the channel.
hycind (Wed, 15 Mar 2017 12:53:40 GMT):
Hi All,
hycind (Wed, 15 Mar 2017 12:53:40 GMT):
Hi All,
I've been trying to locally build Fabric v1. The code I pulled from github mentions this in the makefile [BASE_VERSION = 0.7.0].
So, is there code that reflects the BASE_VERSION as 1.0.0 ? If yes, where/how do I download that?
Thanks!
silliman (Wed, 15 Mar 2017 13:11:11 GMT):
@rameshthoomu Hello Ramesh, I really appreciate the messages you post in here with the docker tags, and the commit levels for the various repositories- the last such message of which you posted on March 10. I just went out to your repo on DockerHub and saw that there have been several more recent versions for each of these repos. Am I safe to infer that since you have not published a similar message in here listing new commit levels, that these more recent versions have not passed whatever set of tests you or others have decided are necessary to pass before you put in an update here? Generally speaking, when working with Fabric v1.0, I've settled into a groove of working at the commit levels that you've last posted in here.
rameshthoomu (Wed, 15 Mar 2017 13:22:19 GMT):
@silliman I post images with commit levels in #fabric-ci channel only after successfully execute end-to-end tests. today if you see x86_64 CI job passed all tests and published images whereas s390x and power jobs are failed to execute node (e2e) job. Looking into these build failures now.. After successful e2e tests on all platforms will post images with commit levels.
rameshthoomu (Wed, 15 Mar 2017 13:25:29 GMT):
Will post new set of images in sometime.. s390x and power jobs are in-progress.
silliman (Wed, 15 Mar 2017 13:29:31 GMT):
@rameshthoomu Thanks Ramesh, that's what I thought but wanted to make sure- today was the first time I peeked at your repos up on DockerHub and when I saw the newer tags I wanted to make sure. I typically just either *git clone* to a new environment or *git pull* to update an existing environment and then I'll *git checkout* to your most recently posted commit levels when stability is my goal.
rameshthoomu (Wed, 15 Mar 2017 13:32:49 GMT):
sure that is right way to do.. But if you are working on x86 environment pls use latest images published today..
mrshah-ibm (Wed, 15 Mar 2017 13:45:32 GMT):
Has joined the channel.
davidkel (Wed, 15 Mar 2017 15:41:17 GMT):
Has joined the channel.
sstone1 (Wed, 15 Mar 2017 16:14:23 GMT):
Has joined the channel.
dselman (Wed, 15 Mar 2017 16:15:05 GMT):
Has joined the channel.
shamckm (Thu, 16 Mar 2017 07:21:42 GMT):
Has joined the channel.
rameshthoomu (Thu, 16 Mar 2017 13:08:09 GMT):
All, Docker Images are being published on below commits.. end-to-end (CLI) , end-to-end (NODE) and end-to-end (JAVA) tests are working as expected on below commits.
`=======> FABRIC COMMIT# - 14055d7 =======> FABRIC CA COMMIT#- 3565f84 =======> FABRIC SDK NODE COMMIT# - dfaba4f =====> FABRIC SDK JAVA COMMIT# - 3c767e5`
```
rameshthoomu/fabric-orderer-x86_64:x86_64-0.7.0-snapshot-14055d7
rameshthoomu/fabric-peer-x86_64:x86_64-0.7.0-snapshot-14055d7
rameshthoomu/fabric-javaenv-x86_64:x86_64-0.7.0-snapshot-14055d7
rameshthoomu/fabric-ccenv-x86_64:x86_64-0.7.0-snapshot-14055d7
rameshthoomu/fabric-couchdb-x86_64:x86_64-0.7.0-snapshot-14055d7
rameshthoomu/fabric-ca-x86_64:x86_64-0.7.0-snapshot-3565f84
Docker images for "System z" are also available by modifying the last component in the repository based on the desired architecture. The above images represent the Intel versions.
Intel = x86_64
System z = s390x
```
The images are also saved with the tag of : *latest*
dselman (Thu, 16 Mar 2017 13:09:04 GMT):
:thumbsup:
davidkel (Thu, 16 Mar 2017 13:55:59 GMT):
@rameshthoomu Are these the official alpha images ?
rameshthoomu (Thu, 16 Mar 2017 13:58:57 GMT):
No..
rameshthoomu (Thu, 16 Mar 2017 14:02:08 GMT):
Soon we will publish official images to hyperledger dockerhub account..
davidkel (Thu, 16 Mar 2017 14:05:14 GMT):
ok, many thanks
mastersingh24 (Thu, 16 Mar 2017 16:43:55 GMT):
@rameshthoomu - are you also going to publish the fabric-ca image as well?
rameshthoomu (Thu, 16 Mar 2017 16:46:09 GMT):
@greg.haskins has to create a release tag in fabric-ca repository..
greg.haskins (Thu, 16 Mar 2017 16:46:25 GMT):
its gated on a CR merge
greg.haskins (Thu, 16 Mar 2017 16:47:07 GMT):
7263/7265
greg.haskins (Thu, 16 Mar 2017 16:47:09 GMT):
https://gerrit.hyperledger.org/r/#/c/7265/
greg.haskins (Thu, 16 Mar 2017 16:47:34 GMT):
once that pair goes in, I will push a tag (assuming I have rights, that remains to be seen)
greg.haskins (Thu, 16 Mar 2017 16:48:20 GMT):
note to maintainers: please commit the entire stack at 7265 using the "Merge with parents" option that gerrit has
rickr (Thu, 16 Mar 2017 22:19:43 GMT):
Can we get posted the apha commit levels here ?
rameshthoomu (Thu, 16 Mar 2017 22:41:29 GMT):
yes.
rameshthoomu (Thu, 16 Mar 2017 23:13:07 GMT):
ALL, Published **fabric** and **fabric-ca** alpha images to hyperledger docker hub. Below are the image references https://hub.docker.com/u/hyperledger/. These images were built on **v1.0.0-alpha** Tag. npm on **1.0.0-alpha**
end2end (CLI), (NODE), (JAVA) tests are worked as expected on below commits:
`===> FABRIC# - fa3d88c ===> FABRIC CA# - b587a48 ===> FABRIC SDK NODE# - dfaba4f ===> FABRIC SDK JAVA - 38516f0`
```
hyperledger/fabric-orderer:x86_64-1.0.0-alpha
hyperledger/fabric-peer:x86_64-1.0.0-alpha
hyperledger/fabric-javaenv:x86_64-1.0.0-alpha
hyperledger/fabric-ccenv:x86_64-1.0.0-alpha
hyperledger/fabric-couchdb:x86_64-1.0.0-alpha
hyperledger/fabric-zookeeper:x86_64-1.0.0-alpha
hyperledger/fabric-kafka:x86_64-1.0.0-alpha
hyperledger/fabric-ca:x86_64-1.0.0-alpha
```
Docker images for "System z & Power" are also available by modifying the last component in the repository based on the desired architecture. The above images represent the Intel versions.
```
Intel = x86_64
System z = s390x
Power = ppc64le
```
rameshthoomu (Fri, 17 Mar 2017 01:43:04 GMT):
if you use above images, please pull ccenv image with the same tag `docker pull hyperledger/fabric-ccenv:x86_64-1.0.0-alpha` or add below lines to docker-compose file
``` ccenv:
image: hyperledger/fabric-ccenv:x86_64-1.0.0-alpha
container_name: ccenv
```
rameshthoomu (Fri, 17 Mar 2017 01:43:04 GMT):
if you use above images, please pull ccenv image with the same tag `docker pull hyperledger/fabric-ccenv:x86_64-0.7.0-snapshot-a785a4c` or add below lines to docker-compose file
``` ccenv:
image: rameshthoomu/fabric-ccenv:x86_64-0.7.0-snapshot-a785a4c
container_name: ccenv
```
rameshthoomu (Fri, 17 Mar 2017 01:43:04 GMT):
if you use above images, please pull ccenv image with the same tag `docker pull hyperledger/fabric-ccenv:x86_64-1.0.0-alpha` or add below lines to docker-compose file
``` ccenv:
image: rameshthoomu/fabric-ccenv:x86_64-1.0.0-alpha
container_name: ccenv
```
RahulBagaria (Fri, 17 Mar 2017 04:00:33 GMT):
Has joined the channel.
nvlasov (Fri, 17 Mar 2017 06:51:38 GMT):
Has joined the channel.
lehors (Fri, 17 Mar 2017 14:13:54 GMT):
Has joined the channel.
obigass (Fri, 17 Mar 2017 14:28:48 GMT):
Has joined the channel.
mohamoud.egal (Fri, 17 Mar 2017 15:41:43 GMT):
Has joined the channel.
debrajo (Fri, 17 Mar 2017 16:49:05 GMT):
Has joined the channel.
jtrayfield (Fri, 17 Mar 2017 18:20:31 GMT):
Has joined the channel.
jtrayfield (Fri, 17 Mar 2017 20:23:01 GMT):
is there any standardized docker-compose file for the alpha?
rameshthoomu (Fri, 17 Mar 2017 20:32:38 GMT):
@jtrayfield no.. You just have to add above tag to the existing image reference in docker-compose file..
jtrayfield (Fri, 17 Mar 2017 20:33:23 GMT):
where can I find a recent docker-compose file?
rameshthoomu (Fri, 17 Mar 2017 20:33:58 GMT):
https://github.com/hyperledger/fabric/blob/master/examples/e2e_cli/docker-compose.yaml
jtrayfield (Fri, 17 Mar 2017 20:34:11 GMT):
thanks!
Basug (Fri, 17 Mar 2017 22:20:56 GMT):
@here could we replace the above images in getting started docker-compose ?
ZionTam (Sat, 18 Mar 2017 00:21:02 GMT):
Has joined the channel.
ZionTam (Sat, 18 Mar 2017 00:28:03 GMT):
@rameshthoomu The sample code sfhackfest seems not work with 1.0 alpha images,some errors and finally only order iamge start successfully
rameshthoomu (Sat, 18 Mar 2017 00:30:55 GMT):
@ZionTam so many new functionality added after sfhackfest and the commands and code is not compatible with alpha images.. to explore more on new functionality please see this https://github.com/hyperledger/fabric/tree/master/examples/e2e_cli
ZionTam (Sat, 18 Mar 2017 00:32:17 GMT):
thanks @rameshthoomu
rangak (Sat, 18 Mar 2017 00:53:19 GMT):
Has joined the channel.
Xiao (Sat, 18 Mar 2017 03:08:58 GMT):
Has joined the channel.
AbhilekhSingh (Sun, 19 Mar 2017 06:29:31 GMT):
I tried e2e_cli docker compose file with latest alpha release
AbhilekhSingh (Sun, 19 Mar 2017 06:29:46 GMT):
getting this error on peer0 logs
AbhilekhSingh (Sun, 19 Mar 2017 06:29:48 GMT):
Error: Error endorsing chaincode: rpc error: code = 2 desc = Error starting container: Failed to generate platform-specific docker build: Error uploading input to container: API error (404): {"message":"lstat /var/lib/docker/aufs/mnt/ca0ec7deafe6e1f346e66fe5ec36ca3c1f8b28eacee943cb883eb4597bf9b7d3/chaincode/input: no such file or directory"}
AbhilekhSingh (Sun, 19 Mar 2017 06:30:16 GMT):
Anyone has any idea why it is happening?
little51 (Sun, 19 Mar 2017 08:59:05 GMT):
Has joined the channel.
fennelD7 (Sun, 19 Mar 2017 13:46:32 GMT):
Has joined the channel.
liuhuanyuxfq (Mon, 20 Mar 2017 00:52:44 GMT):
Has joined the channel.
pradeeppadmarajaiah (Mon, 20 Mar 2017 04:12:33 GMT):
Has joined the channel.
vineet.timble (Mon, 20 Mar 2017 11:48:22 GMT):
Has joined the channel.
vineet.timble (Mon, 20 Mar 2017 11:50:46 GMT):
LATEST tag is missing from most of new images (orderer, ca). Is this intentional?
rameshthoomu (Mon, 20 Mar 2017 13:02:22 GMT):
Yes
rameshthoomu (Mon, 20 Mar 2017 13:03:22 GMT):
We have to pull images with tag.. if you are referring alpha images .. pls pull them with 1.0.0-alpha
rjones (Mon, 20 Mar 2017 17:00:13 GMT):
@vineet.timble LATEST won't work when you have multiple arches in one repo
ananth_s (Mon, 20 Mar 2017 17:41:03 GMT):
Has joined the channel.
ZionTam (Mon, 20 Mar 2017 23:36:12 GMT):
when i try e2e_cli,all containers work except cli container,got below with `docker ps -a`
```
589744cde53d hyperledger/fabric-peer "/bin/bash -c './s..." 5 minutes ago Exited (0) 3 minutes ago cli
```
any idea?
rameshthoomu (Tue, 21 Mar 2017 01:31:21 GMT):
@ZionTam CLI container exit after completion of `script.sh`.. https://github.com/hyperledger/fabric/blob/master/examples/e2e_cli/docker-compose.yaml#L206
rameshthoomu (Tue, 21 Mar 2017 01:32:30 GMT):
please add `sleep 1000` at Line 206.. so that CLI container will not exit even after completion of script.sh..
xiangyw (Tue, 21 Mar 2017 01:43:01 GMT):
Has joined the channel.
ZionTam (Tue, 21 Mar 2017 03:31:41 GMT):
@rameshthoomu yeah,just notice that,thanks
AbhilekhSingh (Tue, 21 Mar 2017 08:56:00 GMT):
Hi I'm trying e2e_cli example on alpha release
AbhilekhSingh (Tue, 21 Mar 2017 08:56:01 GMT):
Error: proposal failed (err: rpc error: code = 2 desc = Block number should have been 1 but was 0)
AbhilekhSingh (Tue, 21 Mar 2017 08:56:09 GMT):
Getting this error on cli
AbhilekhSingh (Tue, 21 Mar 2017 08:56:19 GMT):
Anyone has any idea why it is happening?
xuzhao103389 (Tue, 21 Mar 2017 11:37:16 GMT):
Has joined the channel.
xuzhao103389 (Tue, 21 Mar 2017 11:37:42 GMT):
Hi where can I download the fabric V1.0 alpha?
harsha (Tue, 21 Mar 2017 11:47:42 GMT):
@xuzhao103389 If you are referring to docker-images they're published here https://hub.docker.com/u/hyperledger/
harsha (Tue, 21 Mar 2017 11:48:48 GMT):
Also they have the following tag `hyperledger/fabric-peer:$ARCH-1.0.0-alpha`
xuzhao103389 (Tue, 21 Mar 2017 11:51:43 GMT):
thanks a million
xuzhao103389 (Tue, 21 Mar 2017 11:59:05 GMT):
can I download the latest source code from https://github.com/hyperledger/fabric?
harsha (Tue, 21 Mar 2017 12:06:38 GMT):
Yes, the above link is read-only mirror to https://gerrit.hyperledger.org/r/#/admin/projects/fabric
knibals (Tue, 21 Mar 2017 16:34:06 GMT):
Has joined the channel.
jeffgarratt (Tue, 21 Mar 2017 18:28:31 GMT):
Has joined the channel.
jeffgarratt (Tue, 21 Mar 2017 18:30:30 GMT):
@AbhilekhSingh can you post the logs?
Shadow-Hawk (Wed, 22 Mar 2017 03:36:37 GMT):
Has joined the channel.
xuzhao103389 (Wed, 22 Mar 2017 11:05:27 GMT):
Hi , I download the source code from https://github.com/hyperledger/fabric, and then I do " https://github.com/hyperledger/fabric", the tests failed at :
adduser: Warning: The home directory `/var/lib/zookeeper' does not belong to the user you are currently creating.
update-alternatives: using /etc/zookeeper/conf_example to provide /etc/zookeeper/conf (zookeeper-conf) in auto mode
Processing triggers for libc-bin (2.23-0ubuntu5) ...
---> f7d7546726d1
Removing intermediate container 772bf70b0027
Step 4/6 : ADD docker-entrypoint.sh /docker-entrypoint.sh
---> bbee4c36f8f7
Removing intermediate container 962f180dc15e
Step 5/6 : ENTRYPOINT /docker-entrypoint.sh
---> Running in 9d4e1ea98694
---> 61b7e219cba9
Removing intermediate container 9d4e1ea98694
Step 6/6 : CMD orderer
---> Running in 50092d148267
---> 3fee4833e6f6
Removing intermediate container 50092d148267
Successfully built 3fee4833e6f6
zookeeper uses an image, skipping
kafka0 uses an image, skipping
orderer0 uses an image, skipping
zookeeper uses an image, skipping
kafka2 uses an image, skipping
kafka1 uses an image, skipping
kafka0 uses an image, skipping
orderer0 uses an image, skipping
Running behave tests
/bin/sh: 1: behave: not found
Makefile:138: recipe for target 'behave' failed
make: *** [behave] Error 127
xuzhao103389 (Wed, 22 Mar 2017 11:05:56 GMT):
the command is "make dist-clean all"
Yinsheng (Thu, 23 Mar 2017 03:49:05 GMT):
Has joined the channel.
AbhilekhSingh (Thu, 23 Mar 2017 06:20:13 GMT):
Is there any docker image which has both peer cli and fabric ca client installed?
AbhilekhSingh (Thu, 23 Mar 2017 06:21:02 GMT):
I have to do the transaction from peer cli using user(register and enrolled from fabric-ca client)
Willson (Thu, 23 Mar 2017 06:36:01 GMT):
Has left the channel.
matanyahu (Thu, 23 Mar 2017 10:58:11 GMT):
Has joined the channel.
tegan (Thu, 23 Mar 2017 14:47:39 GMT):
Has joined the channel.
jtrayfield (Thu, 23 Mar 2017 15:36:13 GMT):
I'm having trouble with e2e_cli: the orderer exits with:
2017-03-23 15:33:02.503 UTC [msp] Setup -> DEBU 00f Setting up MSP instance OrdererMSP
2017-03-23 15:33:02.503 UTC [msp] newIdentity -> DEBU 010 Creating identity instance for ID &{OrdererMSP IDENTITY}
2017-03-23 15:33:02.503 UTC [msp] newIdentity -> DEBU 011 Creating identity instance for ID &{OrdererMSP IDENTITY}
2017-03-23 15:33:02.503 UTC [msp] newIdentity -> DEBU 012 Creating identity instance for ID &{OrdererMSP IDENTITY}
panic: Unable to bootstrap orderer. Error reading genesis block file: open /var/hyperledger/orderer/orderer.block: no such file or directory
jtrayfield (Thu, 23 Mar 2017 15:37:49 GMT):
maybe as a result of cli error?
2017-03-23 15:33:06.670 UTC [msp] GetDefaultSigningIdentity -> DEBU 003 Obtaining default signing identity
Error connecting: rpc error: code = 14 desc = grpc: RPC failed fast due to transport failure
Ratnakar (Thu, 23 Mar 2017 15:57:32 GMT):
As per this link https://github.com/hyperledger/fabric/blob/master/examples/e2e_cli/end-to-end.rst#manually-generate-the-artifacts-optional
Can you try to generate the files under `crypto/orderer`
cd e2e_cli
configtxgen -profile TwoOrgs -outputBlock ./crypto/orderer/orderer.block
configtxgen -profile TwoOrgs -outputCreateChannelTx ./crypto/orderer/channel.tx -channelID mychannel
Ratnakar (Thu, 23 Mar 2017 15:57:32 GMT):
@jtrayfield
As per this link https://github.com/hyperledger/fabric/blob/master/examples/e2e_cli/end-to-end.rst#manually-generate-the-artifacts-optional
Can you try to generate the files under `crypto/orderer`
cd e2e_cli
configtxgen -profile TwoOrgs -outputBlock ./crypto/orderer/orderer.block
configtxgen -profile TwoOrgs -outputCreateChannelTx ./crypto/orderer/channel.tx -channelID mychannel
Ratnakar (Thu, 23 Mar 2017 15:59:19 GMT):
or consider moving already generated files `ordere.block` and `channel.tx` to directory `crypto/orderer`
when you run manually you would need to do this manually. `network_setup.sh` will do all these things for you. Please look at the script for more details
Ratnakar (Thu, 23 Mar 2017 15:59:19 GMT):
or consider moving already generated files `ordere.block` and `channel.tx` to directory `crypto/orderer`
when you run manually you would need to do all this. `network_setup.sh` will do all these things for you. Please look at the script for more details
jtrayfield (Thu, 23 Mar 2017 16:01:46 GMT):
@Ratnakar
emdall:e2e_cli jtray$ ./network_setup.sh up
setting to default channel 'mychannel'
Channel name - mychannel
Building configtxgen
can't load package: package github.com/hyperledger/fabric/core/chaincode/shim: cannot find package "github.com/hyperledger/fabric/core/chaincode/shim" in any of:
/usr/local/go/src/github.com/hyperledger/fabric/core/chaincode/shim (from $GOROOT)
/Users/jtray/git2/fabric/src/github.com/hyperledger/fabric/core/chaincode/shim (from $GOPATH)
find: /Users/jtray/git2/fabric/src/github.com/hyperledger/fabric/core/chaincode/shim: No such file or directory
Ratnakar (Thu, 23 Mar 2017 16:03:14 GMT):
are you running the script from `fabric repo` ?
jtrayfield (Thu, 23 Mar 2017 16:03:57 GMT):
emdall:fabric jtray$ pwd
/Users/jtray/git2/fabric
emdall:fabric jtray$ git status
On branch master
Your branch is up-to-date with 'origin/master'.
Ratnakar (Thu, 23 Mar 2017 16:06:24 GMT):
@jtrayfield Not really sure if you followed the instructions provided here https://github.com/hyperledger/fabric/blob/master/examples/e2e_cli/end-to-end.rst#prerequisites
looks like you cloned the repo but you donot have GOPATH set or Go is not installed.
can you check this once please https://github.com/hyperledger/fabric/blob/master/examples/e2e_cli/end-to-end.rst#prerequisites
jtrayfield (Thu, 23 Mar 2017 16:07:51 GMT):
emdall:fabric jtray$ cd $GOPATH/src/github.com/hyperledger/fabric/devenv
-bash: cd: /Users/jtray/git2/fabric/src/github.com/hyperledger/fabric/devenv: No such file or directory
emdall:fabric jtray$ echo $GOPATH
/Users/jtray/git2/fabric
jtrayfield (Thu, 23 Mar 2017 16:08:07 GMT):
what's GOPATH supposed to be set to?
jtrayfield (Thu, 23 Mar 2017 16:13:28 GMT):
@Ratnakar also:
emdall:fabric jtray$ find . -name channel.tx
emdall:fabric jtray$ find . -name ordere.block
emdall:fabric jtray$
jkilpatr (Thu, 23 Mar 2017 16:14:35 GMT):
Has joined the channel.
Ratnakar (Thu, 23 Mar 2017 16:17:34 GMT):
As i mentioned before you would need to install Go and setup few things, Can you follow the instructions from here http://hyperledger-fabric.readthedocs.io/en/latest/dev-setup/devenv.html
jtrayfield (Thu, 23 Mar 2017 16:19:42 GMT):
I have go installed
jtrayfield (Thu, 23 Mar 2017 16:49:05 GMT):
emdall:fabric jtray$ make configtxgen
build/bin/configtxgen
CGO_CFLAGS=" " GOBIN=/Users/jtray/go/src/github.com/hyperledger/fabric/build/bin go install -ldflags "-X github.com/hyperledger/fabric/common/metadata.Version=1.0.0-snapshot-8d3275f -X github.com/hyperledger/fabric/common/metadata.BaseVersion=0.3.0 -X github.com/hyperledger/fabric/common/metadata.BaseDockerLabel=org.hyperledger.fabric" github.com/hyperledger/fabric/common/configtx/tool/configtxgen
# github.com/hyperledger/fabric/vendor/github.com/miekg/pkcs11
vendor/github.com/miekg/pkcs11/pkcs11.go:29:10: fatal error: 'ltdl.h' file not found
#include
rameshthoomu (Thu, 23 Mar 2017 16:55:42 GMT):
@jtrayfield install libtool
jtrayfield (Thu, 23 Mar 2017 17:29:14 GMT):
@rameshthoomu thanks, it seems to be working now
joshuajeeson (Fri, 24 Mar 2017 14:11:48 GMT):
Has joined the channel.
troyronda (Sun, 26 Mar 2017 00:45:58 GMT):
Has joined the channel.
mastersingh24 (Sun, 26 Mar 2017 16:30:12 GMT):
are we down for the count here?
rickr (Sun, 26 Mar 2017 18:43:19 GMT):
@rameshthoomu Seems like verify job builder is not kicking in https://gerrit.hyperledger.org/r/#/c/7445/4
mastersingh24 (Sun, 26 Mar 2017 18:51:49 GMT):
all jobs are stalled because all worker nodes are apparently offline
mastersingh24 (Sun, 26 Mar 2017 18:52:39 GMT):
of course I don't blame people, but come on - there's got to be some type of redundancy for this stuff :(
rickr (Sun, 26 Mar 2017 19:01:07 GMT):
redundancy is a waist for things that should never fail.
rickr (Sun, 26 Mar 2017 19:01:07 GMT):
redundancy is a waste for things that should never fail.
mastersingh24 (Sun, 26 Mar 2017 19:19:46 GMT):
redundancy is the piece which makes it appear to never fail. so from that perspective I'll agree
mastersingh24 (Sun, 26 Mar 2017 19:23:01 GMT):
Message Attachments
mastersingh24 (Sun, 26 Mar 2017 20:15:37 GMT):
also - why do fabric jobs only run against x86?
yacovm (Sun, 26 Mar 2017 20:56:54 GMT):
ah there was a time when they ran against both
yacovm (Sun, 26 Mar 2017 20:56:57 GMT):
but it got cancelled
yacovm (Sun, 26 Mar 2017 20:57:26 GMT):
because we were very pressed to deliver everything for alpha ;)
yacovm (Sun, 26 Mar 2017 20:58:16 GMT):
I assume it was a temporary thing, but you know how temporary changes tend to stay for a long time
muralisr (Sun, 26 Mar 2017 21:02:24 GMT):
@yacovm also, IIRC, the z jobs used to fail dues to some file system permissions thing periodically
yacovm (Sun, 26 Mar 2017 21:02:53 GMT):
I don't remember the reason but I remember that they did fail w.h.p
yacovm (Sun, 26 Mar 2017 21:03:54 GMT):
It has been a month since, I wonder if it got fixed
yacovm (Sun, 26 Mar 2017 21:05:02 GMT):
Wait, actually maybe I'm wrong @muralisr ? I remember we removed *voting*, but did we really remove the Z jobs entirely?
yacovm (Sun, 26 Mar 2017 21:05:17 GMT):
@harrijk do you remember anything?
harrijk (Sun, 26 Mar 2017 21:06:19 GMT):
The z jobs are running in silent mode (no voting) for fabric
harrijk (Sun, 26 Mar 2017 21:07:32 GMT):
the file system permissions issue hopefully has now been resolved after the merging of CR 6905
yacovm (Sun, 26 Mar 2017 21:07:45 GMT):
where? https://jenkins.hyperledger.org/
harrijk (Sun, 26 Mar 2017 21:07:59 GMT):
6905?
harrijk (Sun, 26 Mar 2017 21:08:11 GMT):
I think that's the change you just merged for me
harrijk (Sun, 26 Mar 2017 21:08:25 GMT):
I suppose it will take a while before everyone is using it
yacovm (Sun, 26 Mar 2017 21:08:27 GMT):
no I mean where are the jobs running
harrijk (Sun, 26 Mar 2017 21:08:34 GMT):
In jenkins
yacovm (Sun, 26 Mar 2017 21:08:41 GMT):
where in my link :)
harrijk (Sun, 26 Mar 2017 21:09:02 GMT):
https://jenkins.hyperledger.org/view/fabric/job/fabric-verify-z/
yacovm (Sun, 26 Mar 2017 21:09:24 GMT):
ah you're right!
yacovm (Sun, 26 Mar 2017 21:09:38 GMT):
This isn't silent mode... this is stealth mode
fennelD7 (Mon, 27 Mar 2017 00:37:53 GMT):
Message Attachments
fennelD7 (Mon, 27 Mar 2017 00:38:38 GMT):
I've found that I can install different chaincodes on two peers in the same channel(same chaincode names) last week.
fennelD7 (Mon, 27 Mar 2017 00:42:19 GMT):
Then we found out that the chaincode container and image were not up really, invoke functions were able to issue, query functions returned no responses.
fennelD7 (Mon, 27 Mar 2017 01:22:34 GMT):
Well, in my test just now, Images/Containers were up, invoke functions are working well.
Instantiation is the key! botn chaincodes installed successfully, then all peers execute the instantiated one.
fennelD7 (Mon, 27 Mar 2017 04:41:56 GMT):
In my new test, chaincode installed on peer0 always succeed. No matter what sequence they were installed and instantiated. I think this might be a bug. Started a jira with my logs in it, https://jira.hyperledger.org/browse/FAB-2888
jimthematrix (Mon, 27 Mar 2017 12:59:54 GMT):
@rameshthoomu do we capture the docker instances' logs in these builds? https://jenkins.hyperledger.org/job/fabric-sdk-node-verify-x86_64/732/
jimthematrix (Mon, 27 Mar 2017 13:00:09 GMT):
it's been failing due to mysterious reasons
rickr (Mon, 27 Mar 2017 13:00:28 GMT):
@rameshthoomu Seems like all HLJSDK tests are running but some jenkins misconfig is making it fail at the end -> https://jenkins.hyperledger.org/job/fabric-sdk-java-verify-x86_64/372/console
```
04:23:57 ERROR: your Apache Maven build is setup to use a config with id jenkins-log-archives-settings but can not find the config
04:23:57 ERROR: Build step failed with exception
04:23:57 java.lang.IllegalStateException: your Apache Maven build is setup to use a config with id jenkins-log-archives-settings but can not find the config
04:23:57 at org.jenkinsci.plugins.configfiles.maven.job.MvnSettingsProvider.supplySettings(MvnSettingsProvider.java:76)
04:23:57 at jenkins.mvn.SettingsProvider.getSettingsFilePath(SettingsProvider.java:53)
04:23:57 at jenkins.mvn.SettingsProvider.getSettingsRemotePath(SettingsProvider.java:70)
04:23:57 at hudson.tasks.Maven.perform(Maven.java:331)
04:23:57 at org.jenkinsci.plugins.postbuildscript.PostBuildScript.processBuildSteps(PostBuildScript.java:204)
04:23:57 at org.jenkinsci.plugins.postbuildscript.PostBuildScript.processScripts(PostBuildScript.java:143)
04:23:57 at org.jenkinsci.plugins.postbuildscript.PostBuildScript._perform(PostBuildScript.java:105)
04:23:57 at org.jenkinsci.plugins.postbuildscript.PostBuildScript.perform(PostBuildScript.java:85)
04:23:57 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
04:23:57 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)
04:23:57 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720)
04:23:57 at hudson.model.Build$BuildExecution.post2(Build.java:185)
04:23:57 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665)
04:23:57 at hudson.model.Run.execute(Run.java:1753)
04:23:57 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
04:23:57 at hudson.model.ResourceController.execute(ResourceController.java:98)
04:23:57 at hudson.model.Executor.run(Executor.java:404)
04:23:57 Build step 'Execute a set of scripts' marked build as failure
04:23:57 Archiving artifacts
04:23:58 Recording fingerprints
04:23:58 Finished: FAILURE```
nhrishi (Mon, 27 Mar 2017 13:06:36 GMT):
Has joined the channel.
rameshthoomu (Mon, 27 Mar 2017 13:40:04 GMT):
@rickr yes we are observing same issue in all other CI builds..
rameshthoomu (Mon, 27 Mar 2017 13:40:24 GMT):
we have posted this to @rjones in #ci-pipeline
rickr (Mon, 27 Mar 2017 13:40:35 GMT):
thx for being on top of it
jimthematrix (Mon, 27 Mar 2017 14:33:15 GMT):
@rameshthoomu do we have the docker output for the verify build?
rameshthoomu (Mon, 27 Mar 2017 14:34:00 GMT):
Hi @jimthematrix..
rameshthoomu (Mon, 27 Mar 2017 14:35:21 GMT):
we are piping out docker out put to a file but we are archiving that on build output.. Submitted patch https://gerrit.hyperledger.org/r/#/c/7467/
rameshthoomu (Mon, 27 Mar 2017 14:36:58 GMT):
will run this job https://jenkins.hyperledger.org/job/fabric-sdk-node-verify-x86_64/732/ in sandbox env and will provide the log output
jimthematrix (Mon, 27 Mar 2017 14:47:09 GMT):
thanks Ramesh!
ineiti (Mon, 27 Mar 2017 14:57:01 GMT):
Has joined the channel.
ineiti (Mon, 27 Mar 2017 15:00:39 GMT):
Hi there - I'm interested in the performance of the consensus-algorithms used in hyperledger/fabric. I managed to set up 100 nodes on docker using the scripts from https://github.com/yeasy/docker-compose-files/tree/master/hyperledger/1.0, but now I'm stuck because I have to re-compile for other consensus-algorithms. Are there any pointers that I could use?
rjones (Mon, 27 Mar 2017 17:23:33 GMT):
@rickr @jimthematrix log shipping is working again, thank you for your forbearance
jimthematrix (Mon, 27 Mar 2017 17:42:35 GMT):
Thanks Ry!
rameshthoomu (Mon, 27 Mar 2017 17:48:40 GMT):
thanks @rjones
muralisr (Tue, 28 Mar 2017 13:54:25 GMT):
@ineiti sounds interesting and useful... perhaps try on fabric-consensus ?
vpaprots (Wed, 29 Mar 2017 16:52:48 GMT):
@rameshthoomu @bsmita are you aware of any ppc ci problems for fabric ca? https://gerrit.hyperledger.org/r/#/c/6727 only PPC fails. Closest I can find is:
```
15:56:44 Step 4 : RUN groupadd -r openldap && useradd -r -g openldap openldap
15:56:53 ---> Running in ebfefcf723a9
15:57:01 ---> 87dc7e914192
15:57:01 Build step 'Execute shell' marked build as failure
```
bsmita (Wed, 29 Mar 2017 18:42:13 GMT):
@vpaprots I ran "make all" passed fine and also the latest build passed. https://jenkins.hyperledger.org/job/fabric-ca-verify-ppc64le/453/
jimthematrix (Wed, 29 Mar 2017 20:34:48 GMT):
@rameshthoomu can you update the node SDK CI's that runs the test/fixtures/docker-compose.yaml so that it does "make couchdb" in addition to "make docker" in fabric? I just uploaded https://gerrit.hyperledger.org/r/#/c/7555/ that switches from "couchdb" image to "fabric-couchdb" image, but that image is not being produced by "make docker", must run "make couchdb"
rameshthoomu (Wed, 29 Mar 2017 21:00:03 GMT):
will submit that change now.. in node-sdk, we are building images using `make peer-docker` and `make order-docker`..
rameshthoomu (Wed, 29 Mar 2017 21:00:30 GMT):
I will change this to `make docker` and it should build couchdb image aswell.
rameshthoomu (Wed, 29 Mar 2017 21:16:31 GMT):
@jimthematrix I have submitted patch.. will re-test #7555 after merge CI patch..
rameshthoomu (Wed, 29 Mar 2017 21:43:28 GMT):
@jimthematrix re-triggered https://gerrit.hyperledger.org/r/#/c/7555 and it passed after update CI script
rameshthoomu (Wed, 29 Mar 2017 21:43:38 GMT):
https://jenkins.hyperledger.org/view/fabric-sdk-node/job/fabric-sdk-node-verify-x86_64/758/
jimthematrix (Wed, 29 Mar 2017 23:49:52 GMT):
@rameshthoomu nice! now both platforms have SUCCESS!
rameshthoomu (Wed, 29 Mar 2017 23:54:02 GMT):
Cool
crazybit (Thu, 30 Mar 2017 10:23:23 GMT):
need to start the orderer service in a seperated process if start the peer with development mode?
crazybit (Thu, 30 Mar 2017 10:23:23 GMT):
need to start the orderer service in a seperated process if the peer is started in development mode?
yacovm (Thu, 30 Mar 2017 10:54:03 GMT):
you always do
yacovm (Thu, 30 Mar 2017 10:54:12 GMT):
the ordering service is a different binary
muralisr (Thu, 30 Mar 2017 14:13:21 GMT):
@crazybit only difference between dev and non-dev mode is who manages the chaincode startup ... in dev mode the user starts the chaincode and attaches to the peer while in non dev mode the peer launches the chaincode. All other flows remain same
muralisr (Fri, 31 Mar 2017 11:51:02 GMT):
@rjones @rameshthoomu I see `Build timed out (after 120 minutes).` happen more and more at random points in the unit-test CI recently... for example https://jenkins.hyperledger.org/job/fabric-verify-x86_64/9065/consoleFull, https://jenkins.hyperledger.org/job/fabric-verify-x86_64/9062/consoleFull,
rameshthoomu (Fri, 31 Mar 2017 13:02:03 GMT):
Yes murali I see these failures intermittently but no clue
rameshthoomu (Fri, 31 Mar 2017 13:05:03 GMT):
Will check and let you know.. do you want me retrigger these builds now?
tuand (Fri, 31 Mar 2017 13:45:36 GMT):
Has left the channel.
rameshthoomu (Fri, 31 Mar 2017 15:21:11 GMT):
All, Docker Images are being published on below commits.. end-to-end (CLI) , end-to-end (NODE) and end-to-end (JAVA) tests are working as expected on below commits.
`=======> FABRIC COMMIT# - a785a4c =======> FABRIC CA COMMIT#- bad8552 =======> FABRIC SDK NODE COMMIT# - 00e8ab8 =====> FABRIC SDK JAVA COMMIT# - 315420e`
```
rameshthoomu/fabric-orderer-x86_64:x86_64-0.7.0-snapshot-a785a4c
rameshthoomu/fabric-peer-x86_64:x86_64-0.7.0-snapshot-a785a4c
rameshthoomu/fabric-javaenv-x86_64:x86_64-0.7.0-snapshot-a785a4c
rameshthoomu/fabric-ccenv-x86_64:x86_64-0.7.0-snapshot-a785a4c
rameshthoomu/fabric-couchdb-x86_64:x86_64-0.7.0-snapshot-a785a4c
rameshthoomu/fabric-ca-x86_64:x86_64-0.7.0-snapshot-bad8552
Docker images for "System z" are also available by modifying the last component in the repository based on the desired architecture. The above images represent the Intel versions.
Intel = x86_64
System z = s390x
```
The images are also saved with the tag of : *latest*
rameshthoomu (Fri, 31 Mar 2017 15:21:11 GMT):
All, Docker Images are being published on below commits.. end-to-end (CLI) , end-to-end (NODE) and end-to-end (JAVA) tests are working as expected on below commits.
`=======> FABRIC COMMIT# - a785a4c =======> FABRIC CA COMMIT#- bad8552 =======> FABRIC SDK NODE COMMIT# - 00e8ab8 =====> FABRIC SDK JAVA COMMIT# - 315420e`
```
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-snapshot-a785a4c
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-snapshot-a785a4c
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-snapshot-a785a4c
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-snapshot-a785a4c
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-snapshot-a785a4c
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-snapshot-bad8552
Docker images for "System z" are also available by modifying the last component in the repository based on the desired architecture. The above images represent the Intel versions.
Intel = x86_64
System z = s390x
```
The images are also saved with the tag of : *latest*
rameshthoomu (Fri, 31 Mar 2017 15:26:45 GMT):
if you use above images, please pull ccenv image with the same tag `docker pull hyperledger/fabric-ccenv:x86_64-0.7.0-snapshot-a785a4c` or add below lines to docker-compose file
``` ccenv:
image: rameshthoomu/fabric-ccenv:x86_64-0.7.0-snapshot-a785a4c
container_name: ccenv
```
rameshthoomu (Fri, 31 Mar 2017 15:26:45 GMT):
if you use above images, please pull ccenv image with the same tag `docker pull rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-snapshot-a785a4c` or add below lines to docker-compose file
``` ccenv:
image: rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-snapshot-a785a4c
container_name: ccenv
```
ManjeetGambhir (Fri, 31 Mar 2017 15:27:20 GMT):
any plan for alpha.x
rameshthoomu (Fri, 31 Mar 2017 15:28:46 GMT):
@ManjeetGambhir Will let you know..
rahulhegde (Fri, 31 Mar 2017 17:25:00 GMT):
@rameshthoomu you will have to correct the version ` 0.7.0 ` to ` 1.0.0 `
rameshthoomu (Fri, 31 Mar 2017 18:13:38 GMT):
updated
harsha (Sat, 01 Apr 2017 03:41:13 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=Q6sjSDpS3QvEaSfJE) @rameshthoomu Hi Ramesh, don't we have the images published for ppc64le ?
rameshthoomu (Sat, 01 Apr 2017 03:42:36 GMT):
No Harsha.. Power node in Sandbox is having some problem..
rameshthoomu (Sat, 01 Apr 2017 03:43:08 GMT):
I have cleaned workspace and ran builds but they are failing
rameshthoomu (Sat, 01 Apr 2017 03:43:22 GMT):
Have to check more
harsha (Sat, 01 Apr 2017 03:44:18 GMT):
Sure thing, Thank you for the update
abutler (Sat, 01 Apr 2017 13:46:52 GMT):
Has joined the channel.
ManjeetGambhir (Sat, 01 Apr 2017 16:31:47 GMT):
trying to run docker compose file provided by java sdk commit level mentioned ,but ca server is not coming up
showing error sh: 1: fabric-ca-server: not found
ManjeetGambhir (Sat, 01 Apr 2017 16:35:16 GMT):
docker compose config :
ManjeetGambhir (Sat, 01 Apr 2017 16:35:18 GMT):
ca0:
image: hyperledger/fabric-ca
environment:
- FABRIC_CA_HOME=/etc/hyperledger/fabric-ca-server
ports:
- "7054:7054"
# ca_PeerOrg1 uses the key of peerOrg1 so any new registration is automatically included in peerOrg1
command: sh -c 'fabric-ca-server start --ca.certfile /etc/hyperledger/fabric-ca-server-config/peerOrg1-cert.pem --ca.keyfile /etc/hyperledger/fabric-ca-server-config/d8a5b3cac1b821f6e4b487ceaf1fd239cdcfc310894150908b90f05e9179556a_sk -b admin:adminpw ${ORG_HYPERLEDGER_FABRIC_SDKTEST_INTEGRATIONTESTS_CA_TLS} --tls.certfile /etc/hyperledger/tls/cas/peerOrg1/cert.pem --tls.keyfile /etc/hyperledger/tls/cas/peerOrg1/key.pem -d'
volumes:
- ./e2e-2Orgs/crypto-config/peerOrganizations/peerOrg1/ca/:/etc/hyperledger/fabric-ca-server-config
- ./e2e-2Orgs/tls:/etc/hyperledger/tls
container_name: ca_peerOrg1
ManjeetGambhir (Sat, 01 Apr 2017 16:36:19 GMT):
ca0:
image: rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-snapshot-a785a4c
environment:
- FABRIC_CA_HOME=/etc/hyperledger/fabric-ca-server
ports:
- "7054:7054"
# ca_PeerOrg1 uses the key of peerOrg1 so any new registration is automatically included in peerOrg1
command: sh -c 'fabric-ca-server start --ca.certfile /etc/hyperledger/fabric-ca-server-config/peerOrg1-cert.pem --ca.keyfile /etc/hyperledger/fabric-ca-server-config/d8a5b3cac1b821f6e4b487ceaf1fd239cdcfc310894150908b90f05e9179556a_sk -b admin:adminpw ${ORG_HYPERLEDGER_FABRIC_SDKTEST_INTEGRATIONTESTS_CA_TLS} --tls.certfile /etc/hyperledger/tls/cas/peerOrg1/cert.pem --tls.keyfile /etc/hyperledger/tls/cas/peerOrg1/key.pem -d'
volumes:
- ./e2e-2Orgs/crypto-config/peerOrganizations/peerOrg1/ca/:/etc/hyperledger/fabric-ca-server-config
- ./e2e-2Orgs/tls:/etc/hyperledger/tls
container_name: ca_peerOrg1
ManjeetGambhir (Sat, 01 Apr 2017 16:38:01 GMT):
ignore it
AbhishekSeth (Tue, 04 Apr 2017 06:24:31 GMT):
Has joined the channel.
marek.dapps (Tue, 04 Apr 2017 16:37:16 GMT):
Has joined the channel.
yong (Thu, 06 Apr 2017 03:14:51 GMT):
Has left the channel.
dongming (Fri, 07 Apr 2017 13:38:30 GMT):
Has joined the channel.
vpaprots (Fri, 07 Apr 2017 16:52:26 GMT):
Hi @greg.haskins ran into a strange issue, orderer binary wont start inside docker.. but the native one is just fine..
vpaprots (Fri, 07 Apr 2017 16:52:52 GMT):
spent sone time tracking things down.. do you know who added this:
```
DOCKER_GO_LDFLAGS += -linkmode external -extldflags '-static -lpthread'
```
greg.haskins (Fri, 07 Apr 2017 16:53:09 GMT):
@vpaprots yeah, that is me, but I did that a while back
vpaprots (Fri, 07 Apr 2017 16:53:20 GMT):
(oh.. this should had probably gone to dev env.. whoops)
greg.haskins (Fri, 07 Apr 2017 16:53:29 GMT):
np, lets move there
vpaprots (Fri, 07 Apr 2017 16:53:44 GMT):
Inviting myself
ray (Sat, 08 Apr 2017 16:18:33 GMT):
Has left the channel.
mychewcents (Sun, 09 Apr 2017 12:09:09 GMT):
Has left the channel.
Jay (Mon, 10 Apr 2017 01:35:39 GMT):
Has joined the channel.
zian (Mon, 10 Apr 2017 13:57:17 GMT):
Has joined the channel.
jkilpatr (Mon, 10 Apr 2017 17:16:02 GMT):
so the behave tests are run in python on the local machine but against hyperledger components in docker?
sanchezl (Mon, 10 Apr 2017 20:18:13 GMT):
Has joined the channel.
sanchezl (Mon, 10 Apr 2017 20:19:36 GMT):
@jkilpatr, yes.
sanchezl (Mon, 10 Apr 2017 20:22:13 GMT):
I've noticed that our Jira server does not pick up git commits from the fabric-sdk-java repository. This means that unless we manually add a link to the code review, there is no automatic link between the issue and the commit (which leads to the code review)
sanchezl (Mon, 10 Apr 2017 20:22:13 GMT):
I've noticed that our Jira server does not pick up git commits from the fabric-sdk-java repository. This means that unless we manually add a link to the code review, there is no automatic link between the issue and the commit (which leads to the code review). Is this a know issue?
rjones (Mon, 10 Apr 2017 20:47:41 GMT):
@sanchezl when I look here https://jira.hyperledger.org/browse/FAB-3064 , for instance, it looks like it is picking up git commits
rjones (Mon, 10 Apr 2017 20:48:01 GMT):
@sanchezl JIRA only picks up committed code, not code that is in review
sanchezl (Mon, 10 Apr 2017 20:49:12 GMT):
Ha. Ok. I must of been doing something wrong. Thanks for looking into it.
Lin-YiTang (Tue, 11 Apr 2017 21:19:50 GMT):
Has joined the channel.
msoumeit (Wed, 12 Apr 2017 17:06:13 GMT):
Has joined the channel.
YashGanthe (Fri, 14 Apr 2017 13:27:43 GMT):
Has joined the channel.
mwagner (Tue, 18 Apr 2017 20:36:19 GMT):
Has joined the channel.
jimthematrix (Tue, 18 Apr 2017 23:15:28 GMT):
@rjones @rameshthoomu the fabric-sdk-node verifying jobs have been behaving strangely in the last two weeks, in about half of the x84_64 builds we saw REQUEST_TIMEOUT on a synchronous request from the SDK to the endorser peers (the timeout is already set to 30s), often times the problem corrects itself after a reverify (or two)
jimthematrix (Tue, 18 Apr 2017 23:15:28 GMT):
@rjones @rameshthoomu the fabric-sdk-node verifying jobs have been behaving strangely in the last two weeks, in about half of the builds we saw REQUEST_TIMEOUT on a synchronous request from the SDK to the endorser peers (the timeout is already set to 30s), often times the problem corrects itself after a reverify (or two)
jimthematrix (Tue, 18 Apr 2017 23:16:57 GMT):
on top of that the s390 build has consistently demonstrated the REQUEST_TIMEOUT and has never been successful
jimthematrix (Tue, 18 Apr 2017 23:18:29 GMT):
(actually I take it back, in the latest build #302 s390 actually succeeded, for the first time in a long time: https://jenkins.hyperledger.org/job/fabric-sdk-node-verify-s390x/)
rameshthoomu (Tue, 18 Apr 2017 23:46:51 GMT):
@jimthematrix Node tests are failing past few days with this error https://jira.hyperledger.org/browse/FAB-3008
rameshthoomu (Tue, 18 Apr 2017 23:47:44 GMT):
this issue has been fixed today..
rameshthoomu (Tue, 18 Apr 2017 23:50:59 GMT):
from now on if any failure related to REQUEST_Timeout will check.. Also, @harrijk worked on s390x build failures..
rickr (Wed, 19 Apr 2017 03:01:33 GMT):
Not see that with the java sdk
davidkel (Wed, 19 Apr 2017 15:47:44 GMT):
@rameshthoomu I've noticed that the docker images you publish haven't been updated for a couple of days, but a change in the node-sdk that was published to npm today means that it doesn't work with the images on docker. Would it be possible to get them updated ? Also noticed that the most recent image isn't tagged 'latest'. As I have found these docker images invaluable for testing the continual change of the v1.0 release cycle.
rameshthoomu (Wed, 19 Apr 2017 15:54:37 GMT):
@davidkel yes we are seeing node and java end-to-end tests are failing.. Looking into the test failures.. Will publish once all tests work as expected
rameshthoomu (Wed, 19 Apr 2017 15:55:38 GMT):
Release job trigger build push only after all tests (end-to-end tests) works as expected..
davidkel (Wed, 19 Apr 2017 16:02:40 GMT):
@rameshthoomu thanks for the update. Is there a reason why latest tag points to images 16 days ago yet there are newer images on docker hub ?
rameshthoomu (Wed, 19 Apr 2017 16:03:15 GMT):
which docker hub you are referring?
jimthematrix (Wed, 19 Apr 2017 17:31:37 GMT):
@rameshthoomu about the request timeout errors I mentioned above, it's still happening unpredictably, in this CR https://gerrit.hyperledger.org/r/#/c/7909/ the s390 was green but x86_64 experienced the timeout
rjones (Wed, 19 Apr 2017 17:36:35 GMT):
@jimthematrix @rameshthoomu given that successful jobs take no more than 20 minutes we should probably lower the timeout on https://jenkins.hyperledger.org/job/fabric-sdk-node-verify-s390x/buildTimeTrend
rjones (Wed, 19 Apr 2017 17:37:18 GMT):
job 310 has been "finished" for almost 20 minutes
jimthematrix (Wed, 19 Apr 2017 17:47:15 GMT):
@rjones I'm just wondering about that, https://jenkins.hyperledger.org/job/fabric-sdk-node-verify-x86_64/841/console, it's been stuck in that state where the build is done but not returning for a long time
rjones (Wed, 19 Apr 2017 17:47:49 GMT):
I can kill both of them
rjones (Wed, 19 Apr 2017 17:47:54 GMT):
if you like
jimthematrix (Wed, 19 Apr 2017 17:53:59 GMT):
would killing them cause them to fail? if not yes please
rjones (Wed, 19 Apr 2017 17:56:07 GMT):
they will fail but I can retrigger them
rjones (Wed, 19 Apr 2017 17:56:16 GMT):
I mean, they're going to fail eventually
jimthematrix (Wed, 19 Apr 2017 17:57:16 GMT):
so I still don't understand why they are stuck like that even though the tests are complete?
rjones (Wed, 19 Apr 2017 17:58:34 GMT):
my guess is the job was blocking on something else
rjones (Wed, 19 Apr 2017 17:59:05 GMT):
https://logs.hyperledger.org/jobbuilder/vex-yul-hyp-jenkins-1/fabric-sdk-node-verify-s390x/310/console-timestamp.log.gz looks different than what I saw before, so killing the test caused a bunch of spew in the logs
rjones (Wed, 19 Apr 2017 18:00:17 GMT):
wrong log, this is the one I was looking at before: https://logs.hyperledger.org/jobbuilder/vex-yul-hyp-jenkins-1/fabric-sdk-node-verify-x86_64/841/console-timestamp.log.gz
jimthematrix (Wed, 19 Apr 2017 18:29:55 GMT):
in the latest build it's doing that again, seems like whatever the post-test steps are (guess it's collecting logs and publishing them somewhere?) they are taking longer than the build/test themselves: https://jenkins.hyperledger.org/job/fabric-sdk-node-verify-s390x/312/console
rjones (Wed, 19 Apr 2017 18:32:50 GMT):
log collecting only and publishing only takes about 90 seconds, usually
rjones (Wed, 19 Apr 2017 18:33:23 GMT):
and I don't think that's it, since when I cancel the build, it does the collection/publishing at that time
jimthematrix (Wed, 19 Apr 2017 18:35:48 GMT):
mysterious...
jimthematrix (Wed, 19 Apr 2017 18:40:33 GMT):
@rjones can I ask you to abort the following builds again?
https://jenkins.hyperledger.org/job/fabric-sdk-node-verify-s390x/312/ (1/2)
https://jenkins.hyperledger.org/job/fabric-sdk-node-verify-x86_64/843/ (2/2)
jimthematrix (Wed, 19 Apr 2017 18:41:12 GMT):
i just uploaded another changeset to compensate for the REQUEST_TIMEOUT on the x86 build
jimthematrix (Wed, 19 Apr 2017 18:41:12 GMT):
i just uploaded another patch to compensate for the REQUEST_TIMEOUT on the x86 build
rjones (Wed, 19 Apr 2017 18:42:32 GMT):
done
jimthematrix (Wed, 19 Apr 2017 18:42:49 GMT):
thanks
rameshthoomu (Wed, 19 Apr 2017 19:49:53 GMT):
All, Docker Images are being published on below commits.. end-to-end (CLI) , and end-to-end (JAVA) tests are working as expected on below commits but we see sdk-node tests
are failing. JIRA# FAB-3260
`===> FABRIC# - 7e0cff2 ===> FABRIC CA# - e583181 ===> FABRIC SDK JAVA - 981f70d`
```
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-snapshot-7e0cff2
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-snapshot-7e0cff2
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-snapshot-7e0cff2
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-snapshot-7e0cff2
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-snapshot-7e0cff2
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-snapshot-7e0cff2
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-snapshot-7e0cff2
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-snapshot-e583181
```
Docker images for "System z & Power" are also available by modifying the last component in the repository based on the desired architecture. The above images represent the Intel versions.
```
Intel = x86_64
System z = s390x
Power = ppc64le
```
adeshpande (Wed, 19 Apr 2017 19:58:27 GMT):
Has joined the channel.
latitiah (Wed, 19 Apr 2017 19:58:58 GMT):
Has joined the channel.
adeshpande (Wed, 19 Apr 2017 19:59:11 GMT):
@rameshthoomu Can you please give me site URL from where I can download these images ? Normally Rahul do it so I really don't know
rameshthoomu (Wed, 19 Apr 2017 20:00:30 GMT):
https://hub.docker.com/r/rameshthoomu/
adeshpande (Wed, 19 Apr 2017 20:02:31 GMT):
thanks
davidkel (Wed, 19 Apr 2017 21:55:52 GMT):
@rameshthoomu do you plan to mark them as latest as I was hoping to have a script that could always pull the latest version that you publish for testing
rjones (Wed, 19 Apr 2017 21:57:49 GMT):
@davidkel there really can't be a latest
rjones (Wed, 19 Apr 2017 21:58:35 GMT):
I see that is not the case
rameshthoomu (Wed, 19 Apr 2017 22:03:43 GMT):
@davidkel I publish images with snapshot tag but not with latest tag.. We have script to pull images from hyperledger docker hub and tag it as latest https://github.com/hyperledger/fabric/blob/master/examples/e2e_cli/download-dockerimages.sh
rameshthoomu (Wed, 19 Apr 2017 22:08:45 GMT):
I am submitting a patch to pull images based on user choice.. meanwhile you can modify existing script to pull images from rameshthoomu dockerhub..
davidkel (Wed, 19 Apr 2017 22:13:04 GMT):
@rameshthoomu many thanks for the info and pointer to the script.
jimthematrix (Thu, 20 Apr 2017 02:14:29 GMT):
@rameshthoomu we really need to dig into the build issue I mentioned above, in the latest merge build for 7909:
```21:56:35 [21:56:35] Finished 'test' after 5.37 min
23:26:18 Build timed out (after 120 minutes). Marking the build as failed.```
jimthematrix (Thu, 20 Apr 2017 02:15:06 GMT):
running the test only took 5min but the build got stuck for 2 hours! and then timed out, marking it as failed
jimthematrix (Thu, 20 Apr 2017 02:15:06 GMT):
running the test (successfully) only took 5min but the build got stuck for 2 hours! and then timed out, marking it as failed
jimthematrix (Thu, 20 Apr 2017 02:15:36 GMT):
all the node SDK builds have been plagued by this problem since yesterday
artemius22 (Thu, 20 Apr 2017 07:56:42 GMT):
Has joined the channel.
rjones (Thu, 20 Apr 2017 11:05:46 GMT):
@jimthematrix @rameshthoomu @jwagantall I am out for the next three days, but I will outline how I would debug this. I would publish this job directly to sandbox and make sure it repros. then, I would ask @harrijk to add your key to the machine in sandbox and ssh in to it. Check to see which processes are running _before_ a build, _during_ the build, and _once the build is hung_. I'm willing to bet there is a child process that is wedged. then look in to _why_ the child process gets spawned.
rjones (Thu, 20 Apr 2017 11:07:13 GMT):
@jimthematrix @rameshthoomu @jwagantall since this is recent behavior, and all of the tests are local, to me it rules out anything at our hosting provider. That it is only happening to this one project leads me to think it is a recent change _in this project_ causing the issue.
rjones (Thu, 20 Apr 2017 11:12:02 GMT):
@jimthematrix @rameshthoomu also, that the issue reproduces on the Z systems as well as X rules out hosting issues
jimthematrix (Thu, 20 Apr 2017 11:59:44 GMT):
@rjones your analysis makes sense to me, I'm starting to think the same. will see if we can reproduce on local machines first
rjones (Thu, 20 Apr 2017 12:11:24 GMT):
OK
rameshthoomu (Thu, 20 Apr 2017 13:47:31 GMT):
@jimthematrix I have tested in power machine and able to reproduce this issue
jimthematrix (Thu, 20 Apr 2017 13:47:50 GMT):
yes i can reproduce it locally as well
jimthematrix (Thu, 20 Apr 2017 13:48:11 GMT):
has to do with some recent code changes in the e2e test
rameshthoomu (Thu, 20 Apr 2017 13:49:00 GMT):
I have reverted your patch (7909) and started testing..
jimthematrix (Thu, 20 Apr 2017 13:56:29 GMT):
i think the offending change are in some patch before that... but do let me know what happens in your environment...
rameshthoomu (Thu, 20 Apr 2017 14:01:14 GMT):
sure
cbf (Thu, 20 Apr 2017 16:46:02 GMT):
@greg.haskins @vpaprots regarding the note on pkcs11 build issues
cbf (Thu, 20 Apr 2017 16:46:14 GMT):
would it help to have canonical's help here?
cbf (Thu, 20 Apr 2017 16:46:45 GMT):
I spoke with one of the senior execs over there and they are interested in how they can help with Hyperledger and fabric specifically
cbf (Thu, 20 Apr 2017 16:46:45 GMT):
I spoke with one of the senior execs over there and they are interested in how they can help with Hyperledger and Fabric specifically
cbf (Thu, 20 Apr 2017 16:47:20 GMT):
@mastersingh24 ^^
vpaprots (Thu, 20 Apr 2017 16:49:22 GMT):
I think this is more up to the card vendors to support Ubuntu. And then support various versions. I think they would have to, but often its RHEL for enterprise and the default tested platform for the vendors
vpaprots (Thu, 20 Apr 2017 16:50:00 GMT):
the issue is also that fabric itself now becomes 'based on an OS'
vpaprots (Thu, 20 Apr 2017 16:52:14 GMT):
hmm.. that said.. flipping my hats, speaking for IBM crypto card.. the pkcs11 opencryptoki library and the linux ap driver.. thats all open source
vpaprots (Thu, 20 Apr 2017 16:53:05 GMT):
RHEL packages opencryptoki from sourceforge into RPMs
vpaprots (Thu, 20 Apr 2017 16:54:52 GMT):
and it looks like ubuntu does too: http://packages.ubuntu.com/yakkety/opencryptoki
vpaprots (Thu, 20 Apr 2017 16:55:21 GMT):
comes down to weather it was tested together
vpaprots (Thu, 20 Apr 2017 16:57:11 GMT):
@MikeGardiner ^^ a few cents for your card might be appreciated (see note in https://jira.hyperledger.org/browse/FAB-3196)
MikeGardiner (Thu, 20 Apr 2017 16:57:12 GMT):
Has joined the channel.
jwagantall (Thu, 20 Apr 2017 17:41:47 GMT):
@rameshthoomu did your test succeeded? I noticed that changes before https://gerrit.hyperledger.org/r/#/c/7909/ seem to have passed pre-verification compared to this last one..
jimthematrix (Thu, 20 Apr 2017 18:14:54 GMT):
@jwagantall @rameshthoomu https://gerrit.hyperledger.org/r/#/c/8319/
rameshthoomu (Thu, 20 Apr 2017 18:14:58 GMT):
I tried running tests on reverted code but I see couple of issues with ca configuration.. But @jimthematrix found the root cause of the issue..
jimthematrix (Thu, 20 Apr 2017 18:15:06 GMT):
problem identified and this above fix should take care of
jimthematrix (Thu, 20 Apr 2017 18:15:06 GMT):
problem identified and this above fix should take care of it
jwagantall (Thu, 20 Apr 2017 18:15:18 GMT):
looking at it now..
rameshthoomu (Thu, 20 Apr 2017 18:15:32 GMT):
Thanks @jimthematrix
jimthematrix (Thu, 20 Apr 2017 18:43:34 GMT):
@rameshthoomu another topic, right now the SDK builds always build fabric images from scratch, which on average takes 30min or so, which the SDK tests themselves take only 3-5min. can this be streamlined such that the fabric merge builds publishes to a private docker registry and for the SDK builds to pull from there? it'll speed up the builds dramatically
rameshthoomu (Thu, 20 Apr 2017 18:47:59 GMT):
yes we can do that.. but I see few concerns.. 1) when we trigger node-sdk patch, it has to pull latest commit images from docker hub.. 2) will see how much time it will take to push and pull images from docker hub..
rameshthoomu (Thu, 20 Apr 2017 18:48:43 GMT):
I would suggest create JIRA task and we can discuss and get input on this..
jimthematrix (Thu, 20 Apr 2017 18:48:44 GMT):
fabric-baseimage takes a while
jimthematrix (Thu, 20 Apr 2017 18:48:48 GMT):
sure
jimthematrix (Thu, 20 Apr 2017 18:49:26 GMT):
should actually have that and fabric-baseos built into the VM
jimthematrix (Thu, 20 Apr 2017 18:49:31 GMT):
will create a JIRA
rameshthoomu (Thu, 20 Apr 2017 18:50:35 GMT):
ok will look into this..
jimthematrix (Thu, 20 Apr 2017 18:52:00 GMT):
https://jira.hyperledger.org/browse/FAB-3278
rameshthoomu (Thu, 20 Apr 2017 18:52:51 GMT):
ok
dave.enyeart (Fri, 21 Apr 2017 15:52:10 GMT):
@rameshthoomu I'll move the discussion to the fabric-ci channel.... many of the fabric CI Verifications are failing due to timeout in the last day.
dave.enyeart (Fri, 21 Apr 2017 15:52:13 GMT):
Here's a good example of a timeout that just happened:
https://jenkins.hyperledger.org/job/fabric-verify-x86_64/10069/console
```15:10:40 unit-tests_1 | ? github.com/hyperledger/fabric/core/scc [no test files]
15:12:17 unit-tests_1 | ok github.com/hyperledger/fabric/core/scc/cscc 5.092s coverage: 64.9% of statements
15:13:07 unit-tests_1 | ok github.com/hyperledger/fabric/core/scc/escc 0.163s coverage: 84.6% of statements
15:14:34 unit-tests_1 | ok github.com/hyperledger/fabric/core/scc/lscc 0.662s coverage: 80.2% of statements
15:16:02 unit-tests_1 | ok github.com/hyperledger/fabric/core/scc/qscc 6.340s coverage: 62.5% of statements
15:16:48 unit-tests_1 | ? github.com/hyperledger/fabric/core/scc/samplesyscc [no test files]
15:17:26 Build timed out (after 120 minutes). Marking the build as failed.```
rameshthoomu (Fri, 21 Apr 2017 17:31:05 GMT):
@dave.enyeart looking into it..
jwagantall (Fri, 21 Apr 2017 17:32:44 GMT):
@jimthematrix Is this change good for fixing the timeouts? https://gerrit.hyperledger.org/r/#/c/8319/ I believe we have some verification issues :(
binhn (Fri, 21 Apr 2017 17:37:05 GMT):
in general, more unit-tests have been introduced into the code and will continue the next few weeks, so we either increase the timeout or look to reduce the tests that take the most of time. Of course the better solution is to have faster build env
binhn (Fri, 21 Apr 2017 17:38:30 GMT):
@simsc if we are looking to increase coverage, we need to fix the build env
simsc (Fri, 21 Apr 2017 17:53:51 GMT):
yes, just talking to ramesh, he can post an update
rameshthoomu (Fri, 21 Apr 2017 17:54:00 GMT):
@binhn will increase timeout to 180 or 240 mins as a temporary fix..
binhn (Fri, 21 Apr 2017 17:57:01 GMT):
yes, temporary fix. Let's make sure that it doesn't stay permanent; otherwise, that'd only prolong the inevitable death of the process
rameshthoomu (Fri, 21 Apr 2017 18:14:01 GMT):
@jwagantall yes this has to fix node sdk timeout issues..
rameshthoomu (Fri, 21 Apr 2017 18:14:25 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=pSboEh4vAuxt78sLJ) @jwagantall yes this has to fix node-sdk build timeout issues..
rameshthoomu (Fri, 21 Apr 2017 18:15:06 GMT):
now we are hitting build timeout issues while running fabric unit-tests..
jwagantall (Fri, 21 Apr 2017 18:19:18 GMT):
@rameshthoomu @jimthematrix can we revert https://gerrit.hyperledger.org/r/#/c/7909 and merge it back once https://gerrit.hyperledger.org/r/#/c/8319 is ready?
jwagantall (Fri, 21 Apr 2017 18:19:50 GMT):
that way we can at least fix sdk
jwagantall (Fri, 21 Apr 2017 18:46:35 GMT):
@rameshthoomu @harrijk Can we enable some of the offline nodes? hyp-z-linuxnode?
rameshthoomu (Fri, 21 Apr 2017 18:47:47 GMT):
@jwagantall If this is regarding build timeout errors I see z nodes are completing unit-tests average 48 mins.
rameshthoomu (Fri, 21 Apr 2017 18:48:30 GMT):
https://jenkins.hyperledger.org/job/fabric-verify-z/buildTimeTrend
jimthematrix (Fri, 21 Apr 2017 19:09:50 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=FEAgYreeLCCv8BjXz) @jwagantall reverting 7909 won't fix the build breaks. 3 separate fixes are needed, i've submitted an update to https://gerrit.hyperledger.org/r/#/c/8011/ that has all 3 fixes
jimthematrix (Fri, 21 Apr 2017 19:10:35 GMT):
however we are currently blocked by @mastersingh24 updating https://gerrit.hyperledger.org/r/#/c/8349
jwagantall (Fri, 21 Apr 2017 19:11:59 GMT):
Thanks @jimthematrix I see he was working on it today actively ..
harrijk (Fri, 21 Apr 2017 20:21:33 GMT):
@jwagantall My plan is to fully replace the offline set of z minions with the 10 z minions that are currently online. There are stability issues with the z minions that are currently offline. Eventually, I'd like the offline z minions removed/deleted from production (we'll keep -13) online to the sandbox.
harrijk (Fri, 21 Apr 2017 20:27:20 GMT):
Since bringing the new z minions online, they have performed very well.
rameshthoomu (Fri, 21 Apr 2017 20:31:06 GMT):
@harrijk @jwagantall move this discussion to #ci-pipeline
harrijk (Fri, 21 Apr 2017 20:46:03 GMT):
@rameshthoomu will do.
dave.enyeart (Fri, 21 Apr 2017 22:16:34 GMT):
@rameshthoomu there are two urgent fixes to unit tests available:
https://gerrit.hyperledger.org/r/#/c/8399/
https://gerrit.hyperledger.org/r/#/c/8391/
But due to today's test infrastructure issues they aren't getting a CI job of their own. Could you (or another CI power user) prioritize these so that they can get merged, which will improve overall CI health.
dave.enyeart (Fri, 21 Apr 2017 22:16:34 GMT):
@rameshthoomu there are two urgent fixes to unit tests available:
https://gerrit.hyperledger.org/r/#/c/8399/
https://gerrit.hyperledger.org/r/#/c/8391/
But due to today's CI infrastructure issues they aren't getting a CI job of their own. Could you (or another CI power user) prioritize these so that they can get merged, which will improve overall CI health.
rameshthoomu (Fri, 21 Apr 2017 22:20:20 GMT):
@dave.enyeart CI triggered build on this patch https://jenkins.hyperledger.org/job/fabric-verify-x86_64/10140/console
rameshthoomu (Fri, 21 Apr 2017 22:20:46 GMT):
I see @JonathanLevi given +1 on this patch https://gerrit.hyperledger.org/r/#/c/8399
dave.enyeart (Fri, 21 Apr 2017 22:21:07 GMT):
great, thx
rameshthoomu (Fri, 21 Apr 2017 22:23:04 GMT):
I requested @jwagantall to add more x86_64 nodes to CI pipeline.. We are discussing this in #ci-pipeline channel..
rameshthoomu (Fri, 21 Apr 2017 22:23:13 GMT):
She is working on this
dave.enyeart (Fri, 21 Apr 2017 22:23:25 GMT):
great, thx (again)
ManjeetGambhir (Sun, 23 Apr 2017 19:32:37 GMT):
Hi @rameshthoomu any plan today for new images release with fix for timeout to order to peer
rameshthoomu (Sun, 23 Apr 2017 20:53:35 GMT):
I see java and node e2e tests are failing on latest commits..
ManjeetGambhir (Sun, 23 Apr 2017 22:06:35 GMT):
Did it have above mentioned fixes ??
ManjeetGambhir (Mon, 24 Apr 2017 01:25:26 GMT):
@rameshthoomu any idea about the release ?
jimthematrix (Mon, 24 Apr 2017 17:31:47 GMT):
@rameshthoomu seems like node SDK CI jobs are not being triggered: https://gerrit.hyperledger.org/r/#/c/8263/
rameshthoomu (Mon, 24 Apr 2017 17:32:18 GMT):
yes.. we had issues in CI today morning.. Re-triggering all effected builds..
rameshthoomu (Mon, 24 Apr 2017 17:32:44 GMT):
re-triggered this patch
jimthematrix (Mon, 24 Apr 2017 18:41:50 GMT):
@rameshthoomu now the error: `fatal: Could not read from remote repository.`
rameshthoomu (Mon, 24 Apr 2017 18:43:07 GMT):
yes discussing in #ci-pipeline channel about this issue..
rameshthoomu (Mon, 24 Apr 2017 18:43:19 GMT):
not sure what permissions changed..
rameshthoomu (Mon, 24 Apr 2017 22:09:38 GMT):
CI issue is fixed.. re-triggered #8263 patch and it failed while executing node-sdk tests..
Senthil1 (Wed, 26 Apr 2017 17:55:46 GMT):
Any issue with CI? Build is not triggered for https://gerrit.hyperledger.org/r/#/c/8557/
Senthil1 (Wed, 26 Apr 2017 17:58:05 GMT):
Never mind..
dave.enyeart (Thu, 27 Apr 2017 11:06:33 GMT):
@rameshthoomu and all, Andbody know why Verifications aren't getting kicked off the last 10 hours?
dave.enyeart (Thu, 27 Apr 2017 11:06:33 GMT):
@rameshthoomu @rjones and all, Andbody know why Verifications aren't getting kicked off the last 10 hours?
dave.enyeart (Thu, 27 Apr 2017 12:13:11 GMT):
for example: https://gerrit.hyperledger.org/r/#/c/6793/
rameshthoomu (Thu, 27 Apr 2017 12:40:32 GMT):
@dave.enyeart Builds are in queue
rameshthoomu (Thu, 27 Apr 2017 12:41:06 GMT):
Seems Jenkins master is in trouble.. it's showing Jenkins is shutting down
rameshthoomu (Thu, 27 Apr 2017 12:42:33 GMT):
@rjones @jwagantall Could you please restart Jenkins
rjones (Thu, 27 Apr 2017 13:25:11 GMT):
@rameshthoomu fixed
rameshthoomu (Thu, 27 Apr 2017 13:27:07 GMT):
Thanks @ry.. almost 300 builds are in queue
dave.enyeart (Thu, 27 Apr 2017 16:29:37 GMT):
@rjones I assume you already know, but just in case, looks like jenkins is not responding and verifications are not getting kicked off
rjones (Thu, 27 Apr 2017 16:33:00 GMT):
@dave.enyeart yes, I see that. I'll restart it.
manish-sethi (Thu, 27 Apr 2017 16:59:22 GMT):
Has joined the channel.
manish-sethi (Thu, 27 Apr 2017 17:02:56 GMT):
@rjones I am not able to see the build outputs. e.g., https://jenkins.hyperledger.org/job/fabric-verify-x86_64/10631/. After some time the webpage shows an HTTP 504 gateway timeout error.
rjones (Thu, 27 Apr 2017 17:03:35 GMT):
yes, jenkins is having issues, and I'm waiting for builds to complete so I can restart it
manish-sethi (Thu, 27 Apr 2017 17:04:05 GMT):
OK, sure. thanks
rjones (Thu, 27 Apr 2017 17:04:20 GMT):
now I see some of these jobs have been running for three hours - I will just restart it
rjones (Thu, 27 Apr 2017 17:34:20 GMT):
@here please do not retrigger any builds right now
vugranam (Fri, 28 Apr 2017 12:12:35 GMT):
Has joined the channel.
jkirke (Fri, 28 Apr 2017 15:04:29 GMT):
Has left the channel.
jimthematrix (Fri, 28 Apr 2017 15:34:15 GMT):
@rjones feel free to abandon the two builds for https://gerrit.hyperledger.org/r/#/c/8389/
rameshthoomu (Fri, 28 Apr 2017 17:08:28 GMT):
fabric-end-to-end builds #2307 and 2308 are stuck.. killing them..
jimthematrix (Fri, 28 Apr 2017 17:25:51 GMT):
@rameshthoomu when I need to push an 1.0.0-alpha fix in node SDK, how does the CI job know what's the corresponding fabric and fabric-ca commit levels it should clone?
jimthematrix (Fri, 28 Apr 2017 17:25:56 GMT):
```17:06:41 + git clone ssh://hyperledger-jobbuilder@gerrit.hyperledger.org:29418/fabric-ca /w/workspace/fabric-sdk-node-verify-x86_64/gopath/src/github.com/hyperledger/fabric-ca
17:06:41 Cloning into '/w/workspace/fabric-sdk-node-verify-x86_64/gopath/src/github.com/hyperledger/fabric-ca'...
17:06:49 Total 5470 (delta 22), reused 5409 (delta 22)
17:06:50 + cd /w/workspace/fabric-sdk-node-verify-x86_64/gopath/src/github.com/hyperledger/fabric-ca
17:06:50 ++ git log -1 --pretty=format:%h
17:06:50 + CA_COMMIT=4b58d5c
17:06:50 + echo '======> CA_COMMIT <======= 4b58d5c'
17:06:50 ======> CA_COMMIT <======= 4b58d5c
jimthematrix (Fri, 28 Apr 2017 17:26:23 GMT):
this is the output of @sstone1 fix for the alpha: https://gerrit.hyperledger.org/r/#/c/8727
jimthematrix (Fri, 28 Apr 2017 17:33:37 GMT):
got it:
```git log -1
jimthematrix (Fri, 28 Apr 2017 17:34:12 GMT):
so it'll always get the master HEAD. this obviously won't work with alpha fixes
rjones (Fri, 28 Apr 2017 17:34:57 GMT):
you could change the script to change branches, but this way madness lies
rjones (Fri, 28 Apr 2017 17:35:47 GMT):
once you make them branch-aware, you're committing to branching every project at once (basically)
kostas (Fri, 28 Apr 2017 17:42:43 GMT):
Has joined the channel.
rameshthoomu (Fri, 28 Apr 2017 18:39:51 GMT):
@jimthematrix seems all e2e builds are stuck.. I see they are stuck while executing update channel tests in node-sdk..
rjones (Fri, 28 Apr 2017 18:43:46 GMT):
need to set a timeout on those builds
rjones (Fri, 28 Apr 2017 18:43:54 GMT):
like, 30 minutes or something
jimthematrix (Fri, 28 Apr 2017 18:57:53 GMT):
@rameshthoomu it's very likely a test code problem similar to the one I fixed earlier in https://gerrit.hyperledger.org/r/#/c/8011
jimthematrix (Fri, 28 Apr 2017 18:57:57 GMT):
i'll take a look
rameshthoomu (Fri, 28 Apr 2017 19:00:58 GMT):
sure will kill these builds now..
jimthematrix (Sun, 30 Apr 2017 18:44:02 GMT):
@rameshthoomu @rjones please kill these builds:
https://jenkins.hyperledger.org/job/fabric-sdk-node-verify-s390x/395/
https://jenkins.hyperledger.org/job/fabric-sdk-node-verify-x86_64/928/
rameshthoomu (Sun, 30 Apr 2017 18:44:25 GMT):
Ok
rameshthoomu (Sun, 30 Apr 2017 18:50:11 GMT):
done..
jimthematrix (Sun, 30 Apr 2017 18:54:32 GMT):
thanks!
rjones (Sun, 30 Apr 2017 19:20:54 GMT):
@rameshthoomu need to set a time limit on those builds of like 20 minutes, then cancel and mark failed
rameshthoomu (Sun, 30 Apr 2017 19:22:05 GMT):
Ok
rjones (Sun, 30 Apr 2017 20:57:56 GMT):
unless you see jobs that ended in success that were over 20, it looked like the ones that worked all completed around 14 minutes
rjones (Sun, 30 Apr 2017 20:58:38 GMT):
I guess there were a couple around 30: https://jenkins.hyperledger.org/job/fabric-sdk-node-verify-s390x/buildTimeTrend
rjones (Sun, 30 Apr 2017 20:59:21 GMT):
these seem to succeed by 30 minutes, so a timeout of 45? https://jenkins.hyperledger.org/job/fabric-sdk-node-verify-x86_64/buildTimeTrend
rameshthoomu (Mon, 01 May 2017 15:33:09 GMT):
@jimthematrix did you get chance to look into node-sdk e2e test stuck issue while querying chaincode?
rameshthoomu (Mon, 01 May 2017 15:34:38 GMT):
@rjones I have submitted patch on build timeout https://gerrit.hyperledger.org/r/#/c/8779/
rameshthoomu (Mon, 01 May 2017 15:35:36 GMT):
I have provided build-timeout in each job based on the buildTimeTrend..
jwagantall (Mon, 01 May 2017 15:53:42 GMT):
@rameshthoomu I thought we were going to correct this with Jim's patch.. :( i think is the most appropriated way ..
jwagantall (Mon, 01 May 2017 15:54:03 GMT):
Also,, did we said we needed to make a cleanup of tests we had?
rjones (Mon, 01 May 2017 15:54:44 GMT):
@jwagantall I already merged it :( I can revert
jwagantall (Mon, 01 May 2017 15:56:37 GMT):
oh.. no biggie... if Jim's change still requires some work then Ramesh's change will definately help us in the meantime.. but we do need to see what @jimthematrix says about his patch being able to fix this the better way
jwagantall (Mon, 01 May 2017 15:56:59 GMT):
and the cleanup of tests, which i dont remember if i dream we talk about it or we actually did
rameshthoomu (Mon, 01 May 2017 16:02:04 GMT):
@jwagantall I parametrized builtimeout based on buildTimeTrend.. So this patch removed hardcoded 240 mins build timeout..
dave.enyeart (Mon, 01 May 2017 17:26:43 GMT):
@rameshthoomu Can you check https://gerrit.hyperledger.org/r/#/c/8645/. Only two of three verifications ran. Did the simple verify get turned off? should i simply reverify?
rameshthoomu (Mon, 01 May 2017 17:27:33 GMT):
checking..
rameshthoomu (Mon, 01 May 2017 17:41:06 GMT):
no change in reverify functionality in CI.. `reverify` is triggering all three builds but in this patch I see only two builds are triggered..
dave.enyeart (Mon, 01 May 2017 18:03:43 GMT):
@rameshthoomu why only two in this case? should i just reverify and hope for three next time?
rameshthoomu (Mon, 01 May 2017 18:34:19 GMT):
yes. pls do that for now..
rjones (Mon, 01 May 2017 18:34:30 GMT):
@rameshthoomu I already did that.
rameshthoomu (Mon, 01 May 2017 18:34:48 GMT):
ok
dave.enyeart (Mon, 01 May 2017 18:49:07 GMT):
@rameshthoomu @rjones Here's another strange one: https://gerrit.hyperledger.org/r/#/c/8541/ from @chris.elder . This time the simple verification ran and reported SUCCESS, but if you drill into the console report it shows a unit test failure. https://jenkins.hyperledger.org/job/fabric-verify-x86_64/10943/consoleFull.
dave.enyeart (Mon, 01 May 2017 18:49:07 GMT):
@rameshthoomu @rjones Here's another strange one: https://gerrit.hyperledger.org/r/#/c/8541/ from @chris.elder . This time the simple verification ran and reported SUCCESS, but if you drill into the console report it shows a test failure. https://jenkins.hyperledger.org/job/fabric-verify-x86_64/10943/consoleFull.
dave.enyeart (Mon, 01 May 2017 18:49:31 GMT):
How could a unit test failure result in a SUCCESS?
dave.enyeart (Mon, 01 May 2017 18:49:49 GMT):
I will reverify that one as well.
jimthematrix (Mon, 01 May 2017 19:06:06 GMT):
@rameshthoomu @jwagantall I've fixed all the issues in https://gerrit.hyperledger.org/r/#/c/8389/ and expect the hang to go away, the problem is though the build is taking longer than the timeout and is killed before it got a chance to run through
jimthematrix (Mon, 01 May 2017 19:07:18 GMT):
I think a 60min timeout as a start would be prudent and it can take hints from the successful builds trend
rjones (Mon, 01 May 2017 19:09:35 GMT):
it failed in 14 seconds.
rjones (Mon, 01 May 2017 19:10:19 GMT):
it failed because the workspace isn't clean, there's another process running, or something. @jimthematrix
rjones (Mon, 01 May 2017 19:11:10 GMT):
@jimthematrix looking here successful builds take 14-30 minutes: https://jenkins.hyperledger.org/job/fabric-sdk-node-verify-s390x/buildTimeTrend no need for a 60 minute timeout
jimthematrix (Mon, 01 May 2017 19:11:39 GMT):
I was looking at the x86 build: https://jenkins.hyperledger.org/job/fabric-sdk-node-verify-x86_64/933/
jimthematrix (Mon, 01 May 2017 19:13:19 GMT):
a typical build on x86 would be >40min
jimthematrix (Mon, 01 May 2017 19:13:42 GMT):
sometimes just build fabric and fabric-ca docker images would take that long
jimthematrix (Mon, 01 May 2017 19:36:20 GMT):
@rjones @rameshthoomu @jwagantall please set a longer timeout asap so I can restart the build
rameshthoomu (Mon, 01 May 2017 19:41:47 GMT):
@jimthematrix I see max 30-33 mins is build time on successful node-sdk builds.. I think it's okay to run with 40 mins
jimthematrix (Mon, 01 May 2017 19:42:57 GMT):
I highly doubt the CI job VMs are consistently enough (are they on shared hardware right?) to work with a 3min margin
jimthematrix (Mon, 01 May 2017 19:43:41 GMT):
I've seen too many builds taking longer than that, and if the VMs are on shared hosts then it's susceptible to the `noisy neighbor` problem right?
jimthematrix (Mon, 01 May 2017 19:46:13 GMT):
https://jenkins.hyperledger.org/job/fabric-sdk-node-verify-x86_64/933 for instance, was just able to start `npm install` when it got aborted by the timer
jimthematrix (Mon, 01 May 2017 19:47:12 GMT):
to be honest I don't think using the trend is a good idea, the VMs don't have dedicated resources
jimthematrix (Mon, 01 May 2017 19:48:23 GMT):
the timeout should be set to what's the maximum tolerable length before all VMs get committed and none were being released
jimthematrix (Mon, 01 May 2017 19:48:57 GMT):
node SDK verify builds are not that highly demanded (relative lower rate of CRs compared to fabric)
rameshthoomu (Mon, 01 May 2017 19:50:38 GMT):
yes I agree on build #933..
jimthematrix (Mon, 01 May 2017 19:51:44 GMT):
we've been struggling to get clean builds, I just don't want to introduce another factor that would add more failed builds
jimthematrix (Mon, 01 May 2017 20:14:36 GMT):
@rameshthoomu @rjones @jwagantall has the timeout been updated yet?
rameshthoomu (Mon, 01 May 2017 20:14:54 GMT):
yes..
jimthematrix (Mon, 01 May 2017 20:14:59 GMT):
just triggered another reverify
jwagantall (Mon, 01 May 2017 20:15:02 GMT):
yes
rameshthoomu (Mon, 01 May 2017 20:19:28 GMT):
@harrijk I see permissions issue while wiping out the work space. @https://jenkins.hyperledger.org/job/fabric-sdk-node-verify-s390x/401/console.. any idea why the script is not deleting workspace?
rameshthoomu (Mon, 01 May 2017 20:19:38 GMT):
https://jenkins.hyperledger.org/job/fabric-sdk-node-verify-s390x/400/console
harrijk (Mon, 01 May 2017 20:20:30 GMT):
Hi. I'll take a look... it could be a new file that I need to search for in the script.
harrijk (Mon, 01 May 2017 20:21:17 GMT):
Yep. It's a new file. Let change the script.
rjones (Mon, 01 May 2017 20:30:21 GMT):
@harrijk why not just remove and recreate the build directory? `rm -rf workspace; mkdir workspace; chown jenkins.jenkins workspace` or whatever
harrijk (Mon, 01 May 2017 20:31:24 GMT):
@rjones sure, i can give that a shot. thanks for the suggestion.
rjones (Mon, 01 May 2017 20:32:00 GMT):
be careful - I sort of made that up on the fly, there may be more to it than that :)
harrijk (Mon, 01 May 2017 20:32:23 GMT):
understood. :wink:
latitiah (Mon, 01 May 2017 21:16:48 GMT):
I'm trying to post some changes to the draft branch for use by someone else, but am unable to do so any longer. Do we no longer have this capability?
latitiah (Mon, 01 May 2017 21:17:12 GMT):
`git push origin HEAD:refs/for/draft`
latitiah (Mon, 01 May 2017 21:18:12 GMT):
nm!
latitiah (Mon, 01 May 2017 21:18:18 GMT):
Brain-fart!
latitiah (Mon, 01 May 2017 21:18:39 GMT):
`git push origin HEAD:refs/drafts/master`
weeds (Tue, 02 May 2017 13:27:10 GMT):
@rameshthoomu what is the latest status on the build/ci this morning?
rameshthoomu (Tue, 02 May 2017 13:28:38 GMT):
Hi Sharon.. I see e2e tests are still failing
rameshthoomu (Tue, 02 May 2017 13:31:11 GMT):
Will send out the FAB numbers of each failure soon. I am in scrum meeting now..
weeds (Tue, 02 May 2017 13:34:54 GMT):
Thanks
weeds (Tue, 02 May 2017 17:12:20 GMT):
can we get the fab numbers listed as "highest for bugs" and indicate what the failures are please?
weeds (Tue, 02 May 2017 17:12:22 GMT):
thanks!
weeds (Tue, 02 May 2017 17:17:11 GMT):
https://jira.hyperledger.org/browse/FAB-3563
weeds (Tue, 02 May 2017 17:17:14 GMT):
is the one I know about
rameshthoomu (Tue, 02 May 2017 17:21:41 GMT):
All, Docker Images are being published on below commits.. end-to-end (CLI) and end-to-end (SDK-NODE) tests **are working as expected** on below commits. fabric-sdk-java end-2-end tests are failing. **JIRA FAB-3378**
`===> FABRIC# - 8b38631 ===> FABRIC CA# - 4f86663 ===> FABRIC SDK JAVA - a9666db ===> FABRIC SDK NODE - 8da372e`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-snapshot-4f86663
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-snapshot-8b38631
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-snapshot-8b38631
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-snapshot-8b38631
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-snapshot-8b38631
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-snapshot-8b38631
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-snapshot-8b38631
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-snapshot-8b38631
```
Docker images for "System z & Power" are also available by modifying the last component in the repository based on the desired architecture. The above images represent the Intel versions.
```
Intel = x86_64
System z = s390x
Power = ppc64le
```
rameshthoomu (Tue, 02 May 2017 17:23:55 GMT):
https://jira.hyperledger.org/browse/FAB-3378 (Java e2e test failure)
pmullaney (Tue, 02 May 2017 22:43:42 GMT):
Has joined the channel.
bmkor (Wed, 03 May 2017 05:33:10 GMT):
Has joined the channel.
weeds (Wed, 03 May 2017 11:25:25 GMT):
@rameshthoomu @bmos299 Team- wanted you aware that Ramesh/Barry agreed to have a daily run in the morning EST time and post the results of the build/CI tests every day whether they fail/pass on the fabric-ci channel (typically they had only posted when they passed. When they are failures- they have been opening "highest" bugs). I think this should help everyone with a bit more clarity. Meanwhile. @Ratnakar is working to get us to a single set of compose scripts/docker image that we can utilize in the CI so our results are more consistent when we run all the tests- he's comparing what he's done with what Greg Haskins has done to see if he missed anything. Once that is done, @rameshthoomu will include in the daily run . I posted this on the maintainer channel as well asking for input.
weeds (Wed, 03 May 2017 12:46:47 GMT):
we want tarballs to go to nexus 3 and images for peer/ca to go on docker hub when we cut the new image
rameshthoomu (Wed, 03 May 2017 12:47:50 GMT):
All, Docker Images are being published on below commits.. end-to-end (CLI) and end-to-end (SDK-NODE) tests *are working as expected* on below commits. fabric-sdk-java end-2-end tests are failing. *JIRA FAB-3378
`===> FABRIC# - 2df18bf ===> FABRIC CA# - 34ddbee ===> FABRIC SDK JAVA - a9666db ===> FABRIC SDK NODE - 80d8508`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-snapshot-34ddbee
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-snapshot-2df18bf
rameshthoomu/fabric-kafka-x86_64:pc64le-1.0.0-snapshot-2df18bf
rameshthoomu/fabric-zookeeper-x86_64:pc64le-1.0.0-snapshot-2df18bf
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-snapshot-2df18bf
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-snapshot-2df18bf
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-snapshot-2df18bf
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-snapshot-2df18bf
```
Docker images for "System z & Power" are also available by modifying the last component in the repository based on the desired architecture. The above images represent the Intel versions.
```
Intel = x86_64
System z = s390x
Power = ppc64le
```
https://jira.hyperledger.org/browse/FAB-3378 (Java e2e test failures)
https://jira.hyperledger.org/browse/FAB-3550 (Behave tests failures)
rameshthoomu (Wed, 03 May 2017 12:47:50 GMT):
All, Docker Images are being published on below commits to Power and Z.. end-to-end (SDK-NODE) tests are failed in *x86_64* and working as expected on *power* and *z* on below commits.
===> FABRIC# - a48169d ===> FABRIC CA# - 71fa531 ===> FABRIC SDK JAVA - c1a616e ===> FABRIC SDK NODE - 80d8508`
```
rameshthoomufabric-ca-s390x:s390x-1.0.0-snapshot-71fa531
rameshthoomufabric-couchdb-s390x:s390x-1.0.0-snapshot-a48169d
rameshthoomufabric-kafka-s390x:s390x-1.0.0-snapshot-a48169d
rameshthoomufabric-zookeeper-s390x:s390x-1.0.0-snapshot-a48169d
rameshthoomufabric-orderer-s390x:s390x-1.0.0-snapshot-a48169d
rameshthoomufabric-peer-s390x:s390x-1.0.0-snapshot-a48169d
rameshthoomufabric-javaenv-s390x:s390x-1.0.0-snapshot-a48169d
rameshthoomufabric-ccenv-s390x:s390x-1.0.0-snapshot-a48169d
```
Docker images for "System z & Power" are also available by modifying the last component in the repository based on the desired architecture.
```
System z = s390x
Power = ppc64le
```
https://jira.hyperledger.org/browse/FAB-3378 (Java e2e test failures)
https://jira.hyperledger.org/browse/FAB-3550 (Behave tests failures)
https://jira.hyperledger.org/browse/FAB-3657 (Node e2e test failures)
rameshthoomu (Wed, 03 May 2017 12:47:50 GMT):
All, Docker Images are being published on below commits.. end-to-end (CLI) and end-to-end (SDK-NODE) tests *are working as expected* on below commits. fabric-sdk-java end-2-end tests are failing. *JIRA FAB-3378.
===> FABRIC# - 2df18bf ===> FABRIC CA# - 4f86663 ===> FABRIC SDK JAVA - a9666db===> FABRIC SDK NODE - 80d8508`
```
rameshthoomufabric-ca-x86_64:x86_64-1.0.0-snapshot-4f86663
rameshthoomufabric-couchdb-x86_64:x86_64-1.0.0-snapshot-2df18bf
rameshthoomufabric-kafka-x86_64:x86_64-1.0.0-snapshot-2df18bf
rameshthoomufabric-zookeeper-x86_64:x86_64-1.0.0-snapshot-2df18bf
rameshthoomufabric-orderer-x86_64:x86_64-1.0.0-snapshot-2df18bf
rameshthoomufabric-peer-x86_64:x86_64-1.0.0-snapshot-2df18bf
rameshthoomufabric-javaenv-x86_64:x86_64-1.0.0-snapshot-2df18bf
rameshthoomufabric-ccenv-x86_64:x86_64-1.0.0-snapshot-2df18bf
```
Docker images for "System z & Power" are also available by modifying the last component in the repository based on the desired architecture.
```
Intel = x86_64
System z = s390x
Power = ppc64le
```
https://jira.hyperledger.org/browse/FAB-3378 (Java e2e test failures)
https://jira.hyperledger.org/browse/FAB-3550 (Behave tests failures)
rameshthoomu (Wed, 03 May 2017 12:47:50 GMT):
All, Docker Images are being published on below commits.. end-to-end (CLI) and end-to-end (SDK-NODE) tests *are working as expected* on below commits. fabric-sdk-java end-2-end tests are failing. *JIRA FAB-3378.
===> FABRIC# - 2df18bf ===> FABRIC CA# - 4f86663 ===> FABRIC SDK JAVA - a9666db===> FABRIC SDK NODE - 80d8508`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-snapshot-4f86663
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-snapshot-2df18bf
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-snapshot-2df18bf
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-snapshot-2df18bf
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-snapshot-2df18bf
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-snapshot-2df18bf
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-snapshot-2df18bf
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-snapshot-2df18bf
```
Docker images for "System z & Power" are also available by modifying the last component in the repository based on the desired architecture.
```
Intel = x86_64
System z = s390x
Power = ppc64le
```
https://jira.hyperledger.org/browse/FAB-3378 (Java e2e test failures)
https://jira.hyperledger.org/browse/FAB-3550 (Behave tests failures)
bmos299 (Wed, 03 May 2017 13:03:46 GMT):
@rameshthoomu thanks.
weeds (Wed, 03 May 2017 14:04:57 GMT):
@rameshthoomu THANK YOU!
rjones (Wed, 03 May 2017 22:35:21 GMT):
@here we have escalated the Jenkins restart issue to our hosting provider and will re-enable Jenkins once we work with them
jimthematrix (Wed, 03 May 2017 23:20:48 GMT):
@rjones thanks, was noticing this earlier when builds were not triggered
jimthematrix (Wed, 03 May 2017 23:21:02 GMT):
just curious, who's our hosting provider?
farhan3 (Wed, 03 May 2017 23:39:02 GMT):
Has joined the channel.
rameshthoomu (Thu, 04 May 2017 13:07:31 GMT):
end-2-end tests are failed in x86_64 platform.. Still tests are running in power.. Will update the status once done..
rameshthoomu (Thu, 04 May 2017 13:51:56 GMT):
All, Docker Images are being published on below commits to Power and Z.. end-to-end (SDK-NODE) tests are failed in *x86_64* and working as expected on *power* and *z* on below commits.
===> FABRIC# - a48169d ===> FABRIC CA# - 71fa531 ===> FABRIC SDK JAVA - c1a616e ===> FABRIC SDK NODE - 80d8508`
```
rameshthoomufabric-ca-s390x:s390x-1.0.0-snapshot-71fa531
rameshthoomufabric-couchdb-s390x:s390x-1.0.0-snapshot-a48169d
rameshthoomufabric-kafka-s390x:s390x-1.0.0-snapshot-a48169d
rameshthoomufabric-zookeeper-s390x:s390x-1.0.0-snapshot-a48169d
rameshthoomufabric-orderer-s390x:s390x-1.0.0-snapshot-a48169d
rameshthoomufabric-peer-s390x:s390x-1.0.0-snapshot-a48169d
rameshthoomufabric-javaenv-s390x:s390x-1.0.0-snapshot-a48169d
rameshthoomufabric-ccenv-s390x:s390x-1.0.0-snapshot-a48169d
```
Docker images for "System z & Power" are also available by modifying the last component in the repository based on the desired architecture.
```
System z = s390x
Power = ppc64le
```
https://jira.hyperledger.org/browse/FAB-3378 (Java e2e test failures)
https://jira.hyperledger.org/browse/FAB-3550 (Behave tests failures)
https://jira.hyperledger.org/browse/FAB-3657 (Node e2e test failures)
rameshthoomu (Thu, 04 May 2017 13:51:56 GMT):
All, Docker Images are being published on below commits to Power and Z.. end-to-end (SDK-NODE) tests are failed in *x86_64* and working as expected on *power* and *z* on below commits.
===> FABRIC# - a48169d ===> FABRIC CA# - 71fa531 ===> FABRIC SDK JAVA - c1a616e ===> FABRIC SDK NODE - 80d8508`
```
rameshthoomu/fabric-ca-s390x:s390x-1.0.0-snapshot-71fa531
rameshthoomu/fabric-couchdb-s390x:s390x-1.0.0-snapshot-a48169d
rameshthoomu/fabric-kafka-s390x:s390x-1.0.0-snapshot-a48169d
rameshthoomu/fabric-zookeeper-s390x:s390x-1.0.0-snapshot-a48169d
rameshthoomu/fabric-orderer-s390x:s390x-1.0.0-snapshot-a48169d
rameshthoomu/fabric-peer-s390x:s390x-1.0.0-snapshot-a48169d
rameshthoomu/fabric-javaenv-s390x:s390x-1.0.0-snapshot-a48169d
rameshthoomu/fabric-ccenv-s390x:s390x-1.0.0-snapshot-a48169d
```
Docker images for "System z & Power" are also available by modifying the last component in the repository based on the desired architecture.
```
System z = s390x
Power = ppc64le
```
https://jira.hyperledger.org/browse/FAB-3378 (Java e2e test failures)
https://jira.hyperledger.org/browse/FAB-3550 (Behave tests failures)
https://jira.hyperledger.org/browse/FAB-3657 (Node e2e test failures)
rjones (Thu, 04 May 2017 17:45:26 GMT):
@here emergency outage for Jenkins for VM migration to new hypervisor
ishan.gulhane (Thu, 04 May 2017 17:58:24 GMT):
Has joined the channel.
rameshthoomu (Fri, 05 May 2017 12:34:51 GMT):
All, Docker Images are being published on below commits. end-to-end (CLI), end-to-end (SDK-NODE) and end-to-end (Java SDK) tests are working as expected on below commits.
===> FABRIC# - 8c4fa8e ===> FABRIC CA# - 71fa531 ===> FABRIC SDK JAVA - bac2b54 ===> FABRIC SDK NODE - dc026c6`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-snapshot-71fa531
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-snapshot-8c4fa8e
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-snapshot-8c4fa8e
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-snapshot-8c4fa8e
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-snapshot-8c4fa8e
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-snapshot-8c4fa8e
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-snapshot-8c4fa8e
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-snapshot-8c4fa8e
```
Docker images for "System z & Power" are also available by modifying the last component in the repository based on the desired architecture.
```
System z = s390x
Power = ppc64le
```
https://jira.hyperledger.org/browse/FAB-3550 (Behave tests failures)
rameshthoomu (Sat, 06 May 2017 17:52:33 GMT):
Hi All, Observed node, java e2e tests are failing on below commits levels
=======> FABRIC PEER COMMIT NUMBER - 154160e =======> FABRIC CA COMMIT NUMBER - 616ccdd =======> FABRIC SDK NODE COMMIT NUMBER - dc026c6
FAB-3690 (Node e2e tests failures)
FAB-3688 (Java SDK e2e tests failures)
rameshthoomu (Sat, 06 May 2017 18:00:33 GMT):
Hi All, `Node SDK` and `Java SDK` e2e tests are failing on below commits and e2e (CLI) is working as expected on all three platforms.
`=======> FABRIC# - 154160e =====> FABRIC CA# - 616ccdd =====> FABRIC SDK NODE# - dc026c6 =====> fa6dc538`
Created JIRA items for the above failures
https://jira.hyperledger.org/browse/FAB-3690 (Node SDK e2e test failures)
https://jira.hyperledger.org/browse/FAB-3688 (Java SDK e2e test failures)
rameshthoomu (Sat, 06 May 2017 18:00:33 GMT):
Hi All, `Node SDK` and `Java SDK` e2e tests are failing on below commits and e2e (CLI) is working as expected on all three platforms.
`=======> FABRIC# - 154160e =====> FABRIC CA# - 616ccdd =====> FABRIC SDK NODE# - dc026c6 FABRIC SDK JAVA# =====> fa6dc538`
Created JIRA items for the above failures
https://jira.hyperledger.org/browse/FAB-3690 (Node SDK e2e test failures)
https://jira.hyperledger.org/browse/FAB-3688 (Java SDK e2e test failures)
mffrench (Mon, 08 May 2017 11:45:53 GMT):
Has joined the channel.
rameshthoomu (Mon, 08 May 2017 12:07:20 GMT):
Hi All, `Node SDK` and `Java SDK` e2e tests are failing on below commits and e2e (CLI) is working as expected on all three platforms.
=====> FABRIC# - c346b06 =====> FABRIC CA# - 73a4215 =====> FABRIC SDK NODE# - 595ed51 -- FABRIC SDK JAVA# ======> fa6dc53
Created JIRA items for the above failures
https://jira.hyperledger.org/browse/FAB-3690 (Node SDK e2e test failures)
https://jira.hyperledger.org/browse/FAB-3688 (Java SDK e2e test failures)
https://jira.hyperledger.org/browse/FAB-3550 (Behave tests failures)
jtclark (Mon, 08 May 2017 14:45:34 GMT):
Has joined the channel.
scottz (Mon, 08 May 2017 16:45:00 GMT):
I see lots of these error msgs and my HF verification failed for my gerrit submission request. I made changes only to some test directories, which should not affect any existing code or tests. Is this a known issue? 16:26:12 unit-tests_1 | 2017-05-08 16:26:09.420 UTC [inproccontroller] func1 -> ERRO 36f chaincode-support ended with err: Received nil message, ending chaincode stream
wlahti (Mon, 08 May 2017 17:03:26 GMT):
@scottz I was just looking at the jenkins end2end results for your CR as well. I'm seeing the same thing locally when running the e2e after pulling the latest changes:`16:22:38 Error: Error endorsing query: rpc error: code = 2 desc = failed to obtain cds for mycc - could not find chaincode with name 'mycc'`
wlahti (Mon, 08 May 2017 17:03:26 GMT):
@scottz I was just looking at the jenkins end2end results for your CR as well. I'm seeing the same thing locally when running the e2e after pulling the latest changes: ```16:22:38 Error: Error endorsing query: rpc error: code = 2 desc = failed to obtain cds for mycc - could not find chaincode with name 'mycc'```
wlahti (Mon, 08 May 2017 17:03:26 GMT):
@scottz I was just looking at the jenkins end2end results for your CR as well. I'm seeing the same thing locally when running the e2e after pulling the latest changes: ` 16:22:38 Error: Error endorsing query: rpc error: code = 2 desc = failed to obtain cds for mycc - could not find chaincode with name 'mycc' `
wlahti (Mon, 08 May 2017 17:04:03 GMT):
Definitely seems like something went in that broke the e2e within the last few hours. Trying to track it down.
wlahti (Mon, 08 May 2017 17:09:06 GMT):
I've checked out recent changes up to CR 8961 and everything's still working there. Trying CR 9069 now. Seems like it should either be that one or 9073 that introduced the issue.
wlahti (Mon, 08 May 2017 17:14:04 GMT):
Definitely caused by 9069.
rameshthoomu (Mon, 08 May 2017 17:56:57 GMT):
yes @wlahti I see end-2-end merge job is failed https://jenkins.hyperledger.org/job/fabric-merge-end-2-end-x86_64/441/
wlahti (Mon, 08 May 2017 18:49:36 GMT):
@mastersingh24 is working to resolve this.
rameshthoomu (Mon, 08 May 2017 18:53:19 GMT):
ok
kostas (Mon, 08 May 2017 20:07:20 GMT):
Folks, any idea why the end-2-end job here reports a failure: https://gerrit.hyperledger.org/r/#/c/9045/
kostas (Mon, 08 May 2017 20:07:51 GMT):
But if you check the full logs here: https://jenkins.hyperledger.org/job/fabric-merge-end-2-end-x86_64/447/ you see that the test passed?
rameshthoomu (Mon, 08 May 2017 20:18:22 GMT):
@kostas node end-2-end tests are failing..
kostas (Mon, 08 May 2017 20:19:11 GMT):
@rameshthoomu: Please see https://jenkins.hyperledger.org/job/fabric-merge-end-2-end-x86_64/447/consoleFull
kostas (Mon, 08 May 2017 20:19:23 GMT):
And search for "=============E2E TEST PASSED==========" string.
rameshthoomu (Mon, 08 May 2017 20:20:33 GMT):
end-2-end (CLI) tests are working as expected but I see node e2e tests are failing
```
00:20:43.987 1..66
00:20:43.988 # tests 66
00:20:43.988 # pass 46
00:20:43.988 # fail 20
00:20:43.988
``
kostas (Mon, 08 May 2017 20:21:09 GMT):
Ah, it's the node test that fails.
kostas (Mon, 08 May 2017 20:21:13 GMT):
Gotcha.
rameshthoomu (Mon, 08 May 2017 20:21:17 GMT):
yes
rameshthoomu (Tue, 09 May 2017 13:18:00 GMT):
All, Docker Images are being published on below commits. end-to-end (CLI), end-to-end (SDK-NODE) and end-to-end (Java SDK) tests are working as expected on below commits.
`===> FABRIC# - 0fe5cb2 ===> FABRIC CA# - 92aec7f ===> FABRIC SDK JAVA - d436247 ===> FABRIC SDK NODE - b9da073`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-snapshot-92aec7f
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-snapshot-0fe5cb2
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-snapshot-0fe5cb2
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-snapshot-0fe5cb2
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-snapshot-0fe5cb2
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-snapshot-0fe5cb2
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-snapshot-0fe5cb2
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-snapshot-0fe5cb2
```
Docker images for "System z" are also available by modifying the last component in the repository based on the desired architecture.
```
System z = s390x
```
https://jira.hyperledger.org/browse/FAB-3550 (Behave tests failures)
rameshthoomu (Tue, 09 May 2017 13:18:00 GMT):
All, Docker Images are being published on below commits. **end-to-end (CLI)**, **end-to-end (SDK-NODE)** and **end-to-end (Java SDK)** tests are working as expected on below commits.
`===> FABRIC# - 0fe5cb2 ===> FABRIC CA# - 92aec7f ===> FABRIC SDK JAVA - d436247 ===> FABRIC SDK NODE - b9da073`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-snapshot-92aec7f
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-snapshot-0fe5cb2
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-snapshot-0fe5cb2
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-snapshot-0fe5cb2
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-snapshot-0fe5cb2
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-snapshot-0fe5cb2
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-snapshot-0fe5cb2
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-snapshot-0fe5cb2
```
Docker images for "System z" are also available by modifying the last component in the repository based on the desired architecture.
```
System z = s390x
```
https://jira.hyperledger.org/browse/FAB-3550 (Behave tests failures)
ericmvaughn (Tue, 09 May 2017 17:55:13 GMT):
Has joined the channel.
joshuajeeson (Tue, 09 May 2017 20:42:22 GMT):
Where can I find the instructions to build from source ?
harsha (Wed, 10 May 2017 07:59:29 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=qBJfpr7HqsjZZAm9M) @rameshthoomu So Ramesh, no ppc64le docker images were published ?
rameshthoomu (Wed, 10 May 2017 13:12:50 GMT):
All, Docker Images are being published on below commits. **end-to-end (CLI)** tests are working as expected on all three platforms (x, p and z).. Below are the observations
fabric-sdk-node e2e tests are working as expected on x86_64 platform but failed in s390x.. Had issue with power node..will re-trigger once the node is ready
fabric-sdk-java e2e tests are failing
`===> FABRIC# - 0fe5cb2 ===> FABRIC CA# - 92aec7f ===> FABRIC SDK JAVA - d436247 ===> FABRIC SDK NODE - 4f3f000`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-snapshot-92aec7f
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-snapshot-0fe5cb2
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-snapshot-0fe5cb2
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-snapshot-0fe5cb2
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-snapshot-0fe5cb2
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-snapshot-0fe5cb2
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-snapshot-0fe5cb2
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-snapshot-0fe5cb2
```
Docker images for "System z" are also available by modifying the last component in the repository based on the desired architecture.
```
System z = s390x
```
rameshthoomu (Wed, 10 May 2017 13:18:54 GMT):
All, Docker Images are being published on below commits. **end-to-end (CLI)** tests are working as expected on all three platforms (x, p and z).. Below are the observations on SDK tests
```
fabric-sdk-node e2e tests are working as expected on x86_64 platform but failed on s390x. Had issue with power node in sandbox..will re-trigger once the node is ready
fabric-sdk-java e2e tests are failing..Below are the issues in JIRA.
```
`===> FABRIC# - 9d6cec8 ===> FABRIC CA# - ed5ed51===> FABRIC SDK JAVA - d436247 ===> FABRIC SDK NODE - 4f3f000`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-snapshot-ed5ed51
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-snapshot-9d6cec8
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-snapshot-9d6cec8
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-snapshot-9d6cec8
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-snapshot-9d6cec8
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-snapshot-9d6cec8
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-snapshot-9d6cec8
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-snapshot-9d6cec8
rameshthoomu/fabric-testenv-x86_64:x86_64-1.0.0-snapshot-9d6cec8
```
https://jira.hyperledger.org/browse/FAB-3769 ( java sdk e2e test failures)
https://jira.hyperledger.org/browse/FAB-3768 (node sdk e2e tests failures)
rameshthoomu (Wed, 10 May 2017 13:18:54 GMT):
All, Docker Images are being published on below commits. **end-to-end (CLI)** tests are working as expected on all three platforms (x, p and z).. Below are the observations on SDK tests
```
fabric-sdk-node e2e tests are working as expected on x86_64 platform but failed on s390x. Had issue with power node in sandbox..will re-trigger once the node is ready
fabric-sdk-java e2e tests are failing. FABRIC commit is on # f2e94b3 when running java e2e tests. Below are the issues in JIRA.
```
`===> FABRIC# - 9d6cec8 ===> FABRIC CA# - ed5ed51===> FABRIC SDK JAVA - d436247 ===> FABRIC SDK NODE - 4f3f000`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-snapshot-ed5ed51
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-snapshot-9d6cec8
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-snapshot-9d6cec8
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-snapshot-9d6cec8
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-snapshot-9d6cec8
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-snapshot-9d6cec8
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-snapshot-9d6cec8
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-snapshot-9d6cec8
rameshthoomu/fabric-testenv-x86_64:x86_64-1.0.0-snapshot-9d6cec8
```
https://jira.hyperledger.org/browse/FAB-3769 ( java sdk e2e test failures)
https://jira.hyperledger.org/browse/FAB-3768 (node sdk e2e tests failures)
joshuajeeson (Wed, 10 May 2017 14:12:17 GMT):
Cannot find package : github.com/stretchr/testify/assert
joshuajeeson (Wed, 10 May 2017 14:12:38 GMT):
this is in pkcs11_test.go
rameshthoomu (Wed, 10 May 2017 16:43:58 GMT):
@gennadyl seems gossip tests are stuck in loop.. Please see this build https://jenkins.hyperledger.org/job/fabric-verify-x86_64/11391/console
gennadyl (Wed, 10 May 2017 16:43:58 GMT):
Has joined the channel.
rameshthoomu (Wed, 10 May 2017 16:45:33 GMT):
shall I kill this build?
rameshthoomu (Wed, 10 May 2017 18:00:27 GMT):
@jjjjibm @jimthematrix I have tested node based PKCS tests in sandbox.. I see softhsm2 environment is ready and able to run PKCS tests successfully.. But I see 1 test case is failing.. Please go through the below build output link and let me know if you need any help from us..
rameshthoomu (Wed, 10 May 2017 18:00:28 GMT):
https://jenkins.hyperledger.org/sandbox/job/fabric-sdk-node-verify-x86_64/1/consoleText
rameshthoomu (Wed, 10 May 2017 18:01:30 GMT):
search with `node test/unit/pkcs11.js` to directly jump into the tests..
jimthematrix (Wed, 10 May 2017 19:17:00 GMT):
@rameshthoomu cool that's encouraging, was definitely failing more than just 1 test before. so this is encouraging progress. will take a look...
rameshthoomu (Wed, 10 May 2017 19:17:16 GMT):
sure
latitiah (Wed, 10 May 2017 20:06:35 GMT):
Does anyone know if we have the capability to delete our last patchset/revision submitted in a CR?
rjones (Wed, 10 May 2017 20:08:25 GMT):
@latitiah update the one you want and push it again
rjones (Wed, 10 May 2017 20:08:52 GMT):
I mean, check out the revision you want, rebase it, git commit --amend etc, push again
latitiah (Wed, 10 May 2017 20:09:10 GMT):
Yeah, I was trying to hold on to the votes that I already had with the last revision
rjones (Wed, 10 May 2017 20:09:21 GMT):
they're gone
latitiah (Wed, 10 May 2017 20:10:25 GMT):
oh well - thx anyway
gennadyl (Thu, 11 May 2017 08:15:18 GMT):
@rameshthoomu You can kill it, but I did it intentionally - I hope it will fail at some point
gennadyl (Thu, 11 May 2017 08:16:36 GMT):
I left it to run over the night
rameshthoomu (Thu, 11 May 2017 13:12:46 GMT):
All, Docker Images are being published on below commits. **end-to-end (CLI)**, ** end-to-end (NODE) ** and end-to-end (JAVA) tests are working as expected on all three platforms (x, p and z).
`===> FABRIC# - 51b9f4e ===> FABRIC CA# - ed5ed51===> FABRIC SDK JAVA - 4e1a4a6 ===> FABRIC SDK NODE - a705a81`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-snapshot-ed5ed51
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-snapshot-51b9f4e
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-snapshot-51b9f4e
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-snapshot-51b9f4e
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-snapshot-51b9f4e
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-snapshot-51b9f4e
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-snapshot-51b9f4e
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-snapshot-51b9f4e
rameshthoomu/fabric-testenv-x86_64:x86_64-1.0.0-snapshot-51b9f4e
```
Docker images for "System z & power" are also available by modifying the last component in the repository based on the desired architecture.
```
System z = s390x
power = ppc64le
```
rameshthoomu (Fri, 12 May 2017 12:41:32 GMT):
All, Docker Images are being published on below commits. **end-to-end (CLI)**, ** end-to-end (NODE) ** and end-to-end (JAVA) tests are working as expected on x86. Observed build node issues on z and power. Will resove and re-trigger.
`===> FABRIC# - a892fcd ===> FABRIC CA# - c1bb6c4===> FABRIC SDK JAVA - 6396796 ===> FABRIC SDK NODE - 8e87875`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-snapshot-c1bb6c4
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-snapshot-a892fcd
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-snapshot-a892fcd
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-snapshot-a892fcd
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-snapshot-a892fcd
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-snapshot-a892fcd
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-snapshot-a892fcd
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-snapshot-a892fcd
rameshthoomu/fabric-testenv-x86_64:x86_64-1.0.0-snapshot-a892fcd
```
rameshthoomu (Fri, 12 May 2017 12:41:32 GMT):
All, Docker Images are being published on below commits. **end-to-end (CLI)**, ** end-to-end (NODE) ** and **end-to-end (JAVA)** tests are working as expected on x86. Observed build node issues on z and power. Will resove and re-trigger.
`===> FABRIC# - a892fcd ===> FABRIC CA# - c1bb6c4===> FABRIC SDK JAVA - 6396796 ===> FABRIC SDK NODE - 8e87875`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-snapshot-c1bb6c4
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-snapshot-a892fcd
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-snapshot-a892fcd
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-snapshot-a892fcd
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-snapshot-a892fcd
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-snapshot-a892fcd
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-snapshot-a892fcd
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-snapshot-a892fcd
rameshthoomu/fabric-testenv-x86_64:x86_64-1.0.0-snapshot-a892fcd
```
Observed behave tests are failing inconsistently.. Will work with Jeff
raidinesh80 (Fri, 12 May 2017 13:35:11 GMT):
Has joined the channel.
markparz (Fri, 12 May 2017 18:29:09 GMT):
@jeffgarratt ^^
jeffgarratt (Fri, 12 May 2017 18:34:09 GMT):
@markparz working with him
markparz (Fri, 12 May 2017 18:34:25 GMT):
thanks man
rameshthoomu (Mon, 15 May 2017 13:14:45 GMT):
All, Docker Images are being published on below commits. **end-to-end (CLI)**, ** end-to-end (NODE) ** and **end-to-end (JAVA)** tests are working as expected on x86, s390x and power.
`===> FABRIC# - 2470d35 ===> FABRIC CA# - f6c4283 ===> FABRIC SDK JAVA - b179b31 ===> FABRIC SDK NODE - 8e0c434`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-snapshot-f6c4283
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-snapshot-2470d35
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-snapshot-2470d35
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-snapshot-2470d35
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-snapshot-2470d35
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-snapshot-2470d35
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-snapshot-2470d35
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-snapshot-2470d35
rameshthoomu/fabric-testenv-x86_64:x86_64-1.0.0-snapshot-2470d35
```
Docker images for "System z & power" are also available by modifying the last component in the repository based on the desired architecture.
```
System z = s390x
power = ppc64le
```
FAB-3908 - behave tests are failing intermittently
rameshthoomu (Mon, 15 May 2017 13:21:49 GMT):
tested SDK (node & java) e2e tests on alpha2 docker images -- working as expected..
weeds (Mon, 15 May 2017 13:22:21 GMT):
thanks- where is the image cut and posted again?
weeds (Mon, 15 May 2017 13:22:27 GMT):
@rameshthoomu
rameshthoomu (Mon, 15 May 2017 13:23:09 GMT):
posted in #fabric-release channel
rameshthoomu (Mon, 15 May 2017 14:09:00 GMT):
@here published **alpha2 docker images** of **peer, orderer, ccenv, javaenv, couchdb, kafka, zookeeper and fabric-ca** for each platform (x86_64, s390x and ppc64le) to hyperledger dockerhub. https://hub.docker.com/r/hyperledger/
```
ppc64le-1.0.0-alpha2
x86_64-1.0.0-alpha2
s390x-1.0.0-alpha2
```
also, published **1.0.0-alpha2** npm modules of **fabric-ca-client** and **fabric-client** to npm repository
Working on fabric-sdk-java jar release. Will update once done.
cbf (Mon, 15 May 2017 18:06:28 GMT):
what about platform binaries for configtxgen and cryptogen?
rameshthoomu (Mon, 15 May 2017 18:14:06 GMT):
Patch is out for review.. https://gerrit.hyperledger.org/r/#/c/8939/.. Working on this
rangak (Tue, 16 May 2017 02:20:58 GMT):
Has left the channel.
weeds (Tue, 16 May 2017 11:51:09 GMT):
Hi @rameshthoomu I never saw you post on the fabric-sdk-java jar release ( I also so 8939 but it does not looked like it was approved yet- wondering if you requested on the pr review channel)
rameshthoomu (Tue, 16 May 2017 12:16:33 GMT):
@weeds fabric-sdk-java jar release still in progress.. last week we have published java snapshot release to https://nexus.hyperledger.org/content/repositories/snapshots/org/hyperledger/fabric-sdk-java/fabric-sdk-java/ but @jwagantall suggested not to publish to "snapshot" or "release" targets. She submitted WIP patch to publish jar to "staging" target. We will complete this by today after noon..
rameshthoomu (Tue, 16 May 2017 12:16:44 GMT):
https://gerrit.hyperledger.org/r/#/c/9373/
rameshthoomu (Tue, 16 May 2017 12:18:45 GMT):
Regarding patch# 8939, I have asked @mastersingh24 to review..
rameshthoomu (Tue, 16 May 2017 12:23:36 GMT):
All, Docker Images are being published on below commits. **end-to-end (CLI)**, ** end-to-end (NODE) ** and **end-to-end (JAVA)** tests are working as expected on x86, s390x and power.
`===> FABRIC# - fa98b46 ===> FABRIC CA# - f6c4283 ===> FABRIC SDK JAVA - 2155405 ===> FABRIC SDK NODE - 40fae27`
```
rameshthoomu/fabric-ca-x86_64x86_64-1.0.0-alpha3-snapshot-f6c4283
rameshthoomu/fabric-couchdb-x86_64x86_64-1.0.0-alpha3-snapshot-fa98b46
rameshthoomu/fabric-kafka-x86_64x86_64-1.0.0-alpha3-snapshot-fa98b46
rameshthoomu/fabric-zookeeper-x86_64x86_64-1.0.0-alpha3-snapshot-fa98b46
rameshthoomu/fabric-orderer-x86_64x86_64-1.0.0-alpha3-snapshot-fa98b46
rameshthoomu/fabric-peer-x86_64x86_64-1.0.0-alpha3-snapshot-fa98b46
rameshthoomu/fabric-javaenv-x86_64x86_64-1.0.0-alpha3-snapshot-fa98b46
rameshthoomu/fabric-ccenv-x86_64x86_64-1.0.0-alpha3-snapshot-fa98b46
rameshthoomu/fabric-testenv-x86_64x86_64-1.0.0-alpha3-snapshot-fa98b46
```
Docker images for "System z & power" are also available by modifying the last component in the repository based on the desired architecture.
```
System z = s390x
power = ppc64le
```
FAB-3908 - behave tests are failing intermittently (updated comment in JIRA, will close this if it is not reproducing)
anik (Wed, 17 May 2017 11:42:57 GMT):
Has joined the channel.
rameshthoomu (Wed, 17 May 2017 13:12:22 GMT):
All, Docker Images are being published on below commits. **end-to-end (CLI)** tests are working as expected but observed **CA server is crashing** while executing end-to-end (NODE) tests.
**end-to-end (JAVA)** tests are working as expected as it is using alpha2 docker images.
`====> FABRIC# - b2e64e1 ==> FABRIC CA# - 9bfde7e ===> FABRIC SDK JAVA# - 2155405 ====> FABRIC SDK NODE# - 40fae27`
```
FAB-3908 - behave tests are failing intermittently (updated comment in JIRA, will close this if it is not reproducing)
FAB-3974 - ca server is crashing on latest fabric-ca commits.
```
tarcisiocjr (Thu, 18 May 2017 00:38:00 GMT):
Has joined the channel.
rameshthoomu (Thu, 18 May 2017 13:04:05 GMT):
All, Docker Images are being published on below commits. **end-to-end (CLI)**, ** end-to-end (NODE) ** and **end-to-end (JAVA)** tests are working as expected on x86, s390x and power.
`===> FABRIC# -8ec7571 ===> FABRIC CA# - 10d8d01 ===> FABRIC SDK JAVA - 2fad9ae ===> FABRIC SDK NODE - 6268056`
```
rameshthoomu/fabric-ca-x86_64x86_64-1.0.0-alpha3-snapshot-10d8d01
rameshthoomu/fabric-couchdb-x86_64x86_64-1.0.0-alpha3-snapshot-8ec7571
rameshthoomu/fabric-kafka-x86_64x86_64-1.0.0-alpha3-snapshot-8ec7571
rameshthoomu/fabric-zookeeper-x86_64x86_64-1.0.0-alpha3-snapshot-8ec7571
rameshthoomu/fabric-orderer-x86_64x86_64-1.0.0-alpha3-snapshot-8ec7571
rameshthoomu/fabric-peer-x86_64x86_64-1.0.0-alpha3-snapshot-8ec7571
rameshthoomu/fabric-javaenv-x86_64x86_64-1.0.0-alpha3-snapshot-8ec7571
rameshthoomu/fabric-ccenv-x86_64x86_64-1.0.0-alpha3-snapshot-8ec7571
rameshthoomu/fabric-testenv-x86_64x86_64-1.0.0-alpha3-snapshot-8ec7571
```
Docker images for "System z & power" are also available by modifying the last component in the repository based on the desired architecture.
```
System z = s390x
power = ppc64le
```
FAB-3908 - behave tests are failing intermittently (updated comment in JIRA, will close this if it is not reproducing)
rameshthoomu (Thu, 18 May 2017 13:04:05 GMT):
All, Docker Images are being published on below commits. **end-to-end (CLI)**, ** end-to-end (NODE) ** and **end-to-end (JAVA)** tests are working as expected on x86, s390x and power.
`===> FABRIC# -8ec7571 ===> FABRIC CA# - 10d8d01 ===> FABRIC SDK JAVA - 2fad9ae ===> FABRIC SDK NODE - 6268056`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-alpha3-snapshot-10d8d01
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-alpha3-snapshot-8ec7571
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-alpha3-snapshot-8ec7571
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-alpha3-snapshot-8ec7571
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-alpha3-snapshot-8ec7571
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-alpha3-snapshot-8ec7571
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-alpha3-snapshot-8ec7571
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-alpha3-snapshot-8ec7571
rameshthoomu/fabric-testenv-x86_64:x86_64-1.0.0-alpha3-snapshot-8ec7571
```
Docker images for "System z & power" are also available by modifying the last component in the repository based on the desired architecture.
```
System z = s390x
power = ppc64le
```
FAB-3908 - behave tests are failing intermittently (updated comment in JIRA, will close this if it is not reproducing)
rahulhegde (Thu, 18 May 2017 14:15:04 GMT):
@rameshthoomu
Q => I see a new image - rameshthoomu/fabric-testenv-x86_64x86_64-1.0.0-alpha3-snapshot-8ec7571 ==> how do i use it/purpose?
rameshthoomu (Thu, 18 May 2017 14:17:46 GMT):
@rahulhegde one of the docker-compose file is referring testenv docker image.. ex: https://github.com/hyperledger/fabric/blob/master/examples/e2e_cli/docker-compose-cli.yaml#L37
rameshthoomu (Thu, 18 May 2017 14:18:19 GMT):
I am submitting patch to map this to peer image..
rameshthoomu (Thu, 18 May 2017 14:18:54 GMT):
if my patch merge, then we don't need this e2e test execution..
rahulhegde (Thu, 18 May 2017 14:27:43 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=Jx4BfaBmxyxvmabNw) @rameshthoomu
Ok - i see peer,orderer, softhsm copied as part of it and peer CLI test run using that.. something new!
rahulhegde (Thu, 18 May 2017 14:30:48 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=wnu3uDuf2iWJrGWc6) @rameshthoomu
Was this in context of fabric-testenv-x86_64x86_64-1.0.0-alpha3-snapshot-8ec7571?
rameshthoomu (Thu, 18 May 2017 14:31:17 GMT):
yes
rameshthoomu (Thu, 18 May 2017 14:31:45 GMT):
Will wait for the review comments on this change..
rahulhegde (Thu, 18 May 2017 14:41:05 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=vMCKYgvkhAsaCaKq5) @rameshthoomu OK
rameshthoomu (Fri, 19 May 2017 13:18:14 GMT):
All, Docker Images are being published on below commits. **end-to-end (CLI)**, ** end-to-end (NODE) ** and **end-to-end (JAVA)** tests are working as expected on x86, s390x and power.
`===> FABRIC# -f647b6f ===> FABRIC CA# - 8206d83 ===> FABRIC SDK JAVA - 2fad9ae ===> FABRIC SDK NODE - 75c199e`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-alpha3-snapshot-8206d83
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-alpha3-snapshot-f647b6f
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-alpha3-snapshot-f647b6f
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-alpha3-snapshot-f647b6f
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-alpha3-snapshot-f647b6f
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-alpha3-snapshot-f647b6f
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-alpha3-snapshot-f647b6f
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-alpha3-snapshot-f647b6f
rameshthoomu/fabric-testenv-x86_64:x86_64-1.0.0-alpha3-snapshot-f647b6f
```
Docker images for "System z & power" are also available by modifying the last component in the repository based on the desired architecture.
```
System z = s390x
power = ppc64le
```
FAB-3908 - behave tests are failing intermittently (updated comment in JIRA, will close this if it is not reproducing)
yedendra (Sat, 20 May 2017 14:24:06 GMT):
Has joined the channel.
rameshthoomu (Mon, 22 May 2017 13:00:28 GMT):
All, Docker Images are being published on below commits. **end-to-end (CLI)**, ** end-to-end (NODE) ** and **end-to-end (JAVA)** tests are working as expected on x86, s390x and power.
`===> FABRIC# -5759ee4 ===> FABRIC CA# - 8206d83 ===> FABRIC SDK JAVA - 10323e4 ===> FABRIC SDK NODE - c3b5cb9`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-alpha3-snapshot-8206d83
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-alpha3-snapshot-5759ee4
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-alpha3-snapshot-5759ee4
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-alpha3-snapshot-5759ee4
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-alpha3-snapshot-5759ee4
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-alpha3-snapshot-5759ee4
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-alpha3-snapshot-5759ee4
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-alpha3-snapshot-5759ee4
```
Docker images for "System z & power" are also available by modifying the last component in the repository based on the desired architecture.
```
System z = s390x
power = ppc64le
```
rahulhegde (Mon, 22 May 2017 14:48:01 GMT):
Hello - as part of E2E CLI (alpha-3); I see we do anchor peer update explicitly. Is this step mandatory; previously on (19th April Fabric-Image) we didn't?
rahulhegde (Mon, 22 May 2017 14:48:01 GMT):
Hello - as part of E2E CLI (alpha-3); I see we do anchor peer update explicitly (scripts.sh). Is this step mandatory; previously on (19th April Fabric-Image) we didn't?
rahulhegde (Mon, 22 May 2017 16:39:04 GMT):
@rameshthoomu - I see the crypto-material generation methodology has changed and now it is using yaml as input. Is it compulsory to use the same way or the previous crypto material should be good?
rameshthoomu (Mon, 22 May 2017 16:56:12 GMT):
@rahulhegde if you latest fabric commits it is compulsory..
rameshthoomu (Mon, 22 May 2017 16:56:12 GMT):
@rahulhegde if you use latest fabric commits then it is compulsory..
rahulhegde (Mon, 22 May 2017 17:10:13 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=mLx5EximGPEqcNGF8) @rameshthoomu Ok. what has changed from generating the crypto-config?
rahulhegde (Mon, 22 May 2017 18:07:03 GMT):
@rameshthoomu Does the doman and organization name specified in the crypto-gen tool play a role in identity verification?
jimthematrix (Mon, 22 May 2017 18:35:51 GMT):
@rameshthoomu @jwagantall a trivial update request for node SDK CI jobs: https://jira.hyperledger.org/browse/FAB-4092
jimthematrix (Mon, 22 May 2017 18:36:05 GMT):
please let me know if you have any questions. thanks!
rjones (Mon, 22 May 2017 19:25:43 GMT):
@jimthematrix I set this variable in both sandbox and production. @rameshthoomu @jwagantall
jwagantall (Mon, 22 May 2017 19:26:13 GMT):
thanks a ton @rjones!
jimthematrix (Mon, 22 May 2017 20:22:58 GMT):
thanks @rjones!
rameshthoomu (Tue, 23 May 2017 13:15:02 GMT):
All, Docker Images are being published on below commits. **end-to-end (CLI)**, ** end-to-end (NODE) ** and **end-to-end (JAVA)** tests are working as expected on x86, s390x and power.
`===> FABRIC# -52f1942 ===> FABRIC CA# - 8206d83 ===> FABRIC SDK JAVA - 10323e4 ===> FABRIC SDK NODE - b02f7a0`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-alpha3-snapshot-8206d83
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-alpha3-snapshot-52f1942
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-alpha3-snapshot-52f1942
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-alpha3-snapshot-52f1942
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-alpha3-snapshot-52f1942
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-alpha3-snapshot-52f1942
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-alpha3-snapshot-52f1942
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-alpha3-snapshot-52f1942
```
Docker images for "System z & power" are also available by modifying the last component in the repository based on the desired architecture.
```
System z = s390x
power = ppc64le
```
vpaprots (Tue, 23 May 2017 14:01:59 GMT):
@rameshthoomu would you mind having a look at https://gerrit.hyperledger.org/r/#/c/9441/ please? Getting some intermittent errors, 4 times now (over several days)..
rameshthoomu (Tue, 23 May 2017 14:03:00 GMT):
checking
vpaprots (Tue, 23 May 2017 14:03:09 GMT):
thanks
rameshthoomu (Tue, 23 May 2017 14:04:32 GMT):
it seems to me this is one of the timeout issue
rameshthoomu (Tue, 23 May 2017 14:07:14 GMT):
will retrigger
jimthematrix (Tue, 23 May 2017 15:14:40 GMT):
@rameshthoomu @rjones @jwagantall another minor CI update request: https://jira.hyperledger.org/browse/FAB-4119
jimthematrix (Tue, 23 May 2017 15:14:42 GMT):
thanks!
rameshthoomu (Tue, 23 May 2017 15:15:35 GMT):
Will check this
rameshthoomu (Tue, 23 May 2017 16:13:03 GMT):
@muralisr @aambati unit-test merge job is failed on this patch set https://gerrit.hyperledger.org/r/#/c/9665/
```
00:38:51.163 unit-tests_1 | --- FAIL: Test_Start (3.13s)
00:38:51.164 unit-tests_1 | assertions.go:219:
Error Trace: dockercontroller_test.go:231
00:38:51.165 unit-tests_1 |
dockercontroller_test.go:140
00:38:51.166 unit-tests_1 |
Error: An error is expected but got nil. %s
00:38:51.167 unit-tests_1 |
Messages: Expected failure but succeeded
```
aambati (Tue, 23 May 2017 16:13:03 GMT):
Has joined the channel.
muralisr (Tue, 23 May 2017 16:29:06 GMT):
thanks, @rameshthoomu
muralisr (Tue, 23 May 2017 16:29:11 GMT):
will check
muralisr (Tue, 23 May 2017 16:52:58 GMT):
@aambati I think the err1 fix went to the wrong lines
muralisr (Tue, 23 May 2017 16:53:06 GMT):
might as well use different variables
muralisr (Tue, 23 May 2017 16:53:06 GMT):
might as well do the same fix everywhere with different variables
jimthematrix (Tue, 23 May 2017 17:17:16 GMT):
@rjones maybe there's a misunderstanding, but I'm not seeing the `PKCS11_TESTS` environment variable being set in https://jenkins.hyperledger.org/job/fabric-sdk-node-verify-x86_64/configure-readonly/. the pkcs11 tests are not being executed as a result in today's builds
jimthematrix (Tue, 23 May 2017 17:17:16 GMT):
@rjones maybe there's a misunderstanding, but I'm seeing the `PKCS11_TESTS` environment variable being set in https://jenkins.hyperledger.org/job/fabric-sdk-node-verify-x86_64/configure-readonly/. the pkcs11 tests are not being executed as a result in today's builds
jimthematrix (Tue, 23 May 2017 17:18:34 GMT):
actually, never mind
jimthematrix (Tue, 23 May 2017 17:18:45 GMT):
i see it's in there from the test output
jimthematrix (Tue, 23 May 2017 17:54:43 GMT):
@rameshthoomu @rjones @jwagantall another minor CI update request: https://jira.hyperledger.org/browse/FAB-4119
thanks!
rjones (Tue, 23 May 2017 18:08:40 GMT):
@rameshthoomu are you looking at 4119 or should I?
rameshthoomu (Tue, 23 May 2017 18:09:38 GMT):
will work on this.. but will do this by EOD.. Working on fabric-ca documentation build
rjones (Tue, 23 May 2017 18:38:13 GMT):
Ok
aambati (Tue, 23 May 2017 19:02:40 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=7YtboH9cmLGDpfds9) Murali and I debugged this problem, we found the root cause...in this case, the test case actually caught a code bug...I will submit a change set
aambati (Tue, 23 May 2017 19:02:40 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=7YtboH9cmLGDpfds9) @rameshthoomu Murali and I debugged this problem, we found the root cause...in this case, the test case actually caught a code bug...I will submit a change set
rjones (Tue, 23 May 2017 19:09:28 GMT):
Tests finding bugs? Excellent!
muralisr (Tue, 23 May 2017 19:09:56 GMT):
Indeed, there have been a few of those @rjones
muralisr (Tue, 23 May 2017 19:10:14 GMT):
excellent, as you say :-)
rameshthoomu (Wed, 24 May 2017 13:23:40 GMT):
All, Docker Images are being published on below commits. **end-to-end (CLI)**, ** end-to-end (NODE) ** and **end-to-end (JAVA)** tests are working as expected on x86, s390x and power.
`===> FABRIC# -59e0b94 ===> FABRIC CA# - bae7666 ===> FABRIC SDK JAVA - 457ac61 ===> FABRIC SDK NODE - ff69ba4`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-alpha3-snapshot-bae7666
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-alpha3-snapshot-59e0b94
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-alpha3-snapshot-59e0b94
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-alpha3-snapshot-59e0b94
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-alpha3-snapshot-59e0b94
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-alpha3-snapshot-59e0b94
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-alpha3-snapshot-59e0b94
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-alpha3-snapshot-59e0b94
```
Docker images for "System z & power" are also available by modifying the last component in the repository based on the desired architecture.
```
System z = s390x
power = ppc64le
```
aambati (Wed, 24 May 2017 14:03:26 GMT):
I am not able to get good builds due to random unit test failures
lately, i have been seeing this test fail:
```
FAIL: TestCreateChainWithWaitSuccess (5.09s)
21:56:02 unit-tests_1 | create_test.go:233: expected create command to succeed
21:56:02 unit-tests_1 | Received error: EOF
21:56:02 unit-tests_1 | Received error: EOF
21:56:02 unit-tests_1 | Received error: EOF
21:56:02 unit-tests_1 | Error receiving: EOF
21:56:02 unit-tests_1 | Error: timeout waiting for channel creation
```
Sometimes this test fails with `port in use` error
Anyone working on these failures?
baohua (Wed, 24 May 2017 14:06:04 GMT):
Has left the channel.
rameshthoomu (Wed, 24 May 2017 14:08:04 GMT):
@aambati we are seeing unit-tests are failing intermittently.. @muralisr given fix to the port in use issue... Are you executing tests are latest fabric commits?
rameshthoomu (Wed, 24 May 2017 14:08:04 GMT):
@aambati unit-tests are failing intermittently with all weird errors .. @muralisr given fix to the port in use issue... Are you executing tests are latest fabric commits?
harsha (Wed, 24 May 2017 14:22:12 GMT):
`make unit-tests` fails across `ppc64le` and `x64_64`
```
Building build/docker/bin/peer
# github.com/hyperledger/fabric/peer/channel
peer/channel/deliverclient.go:118: not enough arguments in call to InitCmdFactory
Makefile:182: recipe for target 'build/docker/bin/peer' failed
make: *** [build/docker/bin/peer] Error 2 ```
harsha (Wed, 24 May 2017 14:22:41 GMT):
^^^ @muralisr @rameshthoomu
aambati (Wed, 24 May 2017 14:26:43 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=myonBJiStGB7mLR73) @rameshthoomu yes, i am using the latest code...i will rebase and try
aambati (Wed, 24 May 2017 14:26:43 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=myonBJiStGB7mLR73) @rameshthoomu yes, i think am using the latest code...but i will rebase again and try
rameshthoomu (Wed, 24 May 2017 14:28:11 GMT):
ok
aambati (Wed, 24 May 2017 14:29:06 GMT):
i do see an open defect for TestCreateChainWithWaitSuccess failure: https://jira.hyperledger.org/browse/FAB-4128
aambati (Wed, 24 May 2017 14:29:06 GMT):
i do see an open defect for TestCreateChainWithWaitSuccess failure: https://jira.hyperledger.org/browse/FAB-4128 ...it was opened last night
rameshthoomu (Wed, 24 May 2017 15:52:19 GMT):
@harsha please create issue in JIRA.. I see this is happening intermittently.. @muralisr here is one more reference to the same failure https://jenkins.hyperledger.org/job/fabric-sdk-java-verify-x86_64/772/console
harsha (Wed, 24 May 2017 16:04:00 GMT):
@rameshthoomu @harrijk I see a JIRA already in place https://jira.hyperledger.org/browse/FAB-4142
rameshthoomu (Wed, 24 May 2017 16:05:51 GMT):
I think fix is in-review https://gerrit.hyperledger.org/r/#/c/9757/
kiranarshakota (Thu, 25 May 2017 06:23:14 GMT):
Has joined the channel.
rameshthoomu (Thu, 25 May 2017 13:13:29 GMT):
All, Docker Images are being published on below commits. **end-to-end (CLI)**, ** end-to-end (NODE) ** and **end-to-end (JAVA)** tests are working as expected on x86, s390x and power.
`===> FABRIC# -6e0ec1f ===> FABRIC CA# - ee71b0a ===> FABRIC SDK JAVA - 465d871 ===> FABRIC SDK NODE - 105d16c`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-alpha3-snapshot-ee71b0a
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-alpha3-snapshot-6e0ec1f
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-alpha3-snapshot-6e0ec1f
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-alpha3-snapshot-6e0ec1f
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-alpha3-snapshot-6e0ec1f
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-alpha3-snapshot-6e0ec1f
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-alpha3-snapshot-6e0ec1f
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-alpha3-snapshot-6e0ec1f
```
Docker images for "System z & power" are also available by modifying the last component in the repository based on the desired architecture.
```
System z = s390x
power = ppc64le
```
aambati (Thu, 25 May 2017 13:56:18 GMT):
@rameshthoomu can you pls look at this build failure: https://gerrit.hyperledger.org/r/#/c/8913/
rameshthoomu (Thu, 25 May 2017 13:56:42 GMT):
checking
aambati (Thu, 25 May 2017 13:56:53 GMT):
all the jobs failed and it seems like test execution failed abruptly
aambati (Thu, 25 May 2017 13:58:14 GMT):
oh, i see the problem
aambati (Thu, 25 May 2017 13:58:16 GMT):
nm
aambati (Thu, 25 May 2017 13:58:56 GMT):
```13:50:39 # github.com/hyperledger/fabric/peer/channel
13:50:39 peer/channel/deliverclient.go:118: not enough arguments in call to InitCmdFactory
13:50:44 Makefile:182: recipe for target 'build/docker/bin/peer' failed
13:50:44 make: *** [build/docker/bin/peer] Error 2
13:50:44 Build step 'Execute shell' marked build as failure```
aambati (Thu, 25 May 2017 13:59:00 GMT):
may be i need to rebase
rameshthoomu (Thu, 25 May 2017 18:03:55 GMT):
@aambati re-triggered build and it worked now.
rameshthoomu (Fri, 26 May 2017 13:29:24 GMT):
All, Docker Images are being published on below commits. **end-to-end (CLI)**, ** end-to-end (NODE) ** and **end-to-end (JAVA)** tests are working as expected on x86, s390x and power.
`===> FABRIC# -5caa571 ===> FABRIC CA# - 406df3c ===> FABRIC SDK JAVA - 465d871 ===> FABRIC SDK NODE - b7eb1d4`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-alpha3-snapshot-406df3c
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-alpha3-snapshot-5caa571
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-alpha3-snapshot-5caa571
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-alpha3-snapshot-5caa571
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-alpha3-snapshot-5caa571
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-alpha3-snapshot-5caa571
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-alpha3-snapshot-5caa571
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-alpha3-snapshot-5caa571
```
Docker images for "System z & power" are also available by modifying the last component in the repository based on the desired architecture.
```
System z = s390x
power = ppc64le
```
bmalavan (Sat, 27 May 2017 15:30:49 GMT):
Has joined the channel.
C0rWin (Mon, 29 May 2017 12:43:59 GMT):
it seems that e2e test fails on CI
C0rWin (Mon, 29 May 2017 12:44:13 GMT):
looks like it has been broken :/
C0rWin (Mon, 29 May 2017 12:47:07 GMT):
https://jenkins.hyperledger.org/job/fabric-verify-end-2-end-x86_64/3848/console
https://jenkins.hyperledger.org/job/fabric-verify-end-2-end-x86_64/3842/console
https://jenkins.hyperledger.org/job/fabric-verify-end-2-end-x86_64/3847/console
https://jenkins.hyperledger.org/job/fabric-verify-end-2-end-x86_64/3841/console
rameshthoomu (Tue, 30 May 2017 13:32:00 GMT):
@C0rWin Created JIRA issue # 4204. Issue is fixed now..
rameshthoomu (Tue, 30 May 2017 13:32:22 GMT):
All, Docker Images are being published on below commits. **end-to-end (CLI)**, ** end-to-end (NODE) ** and **end-to-end (JAVA)** tests are working as expected on x86, s390x and power.
`===> FABRIC# -d2bfa74 ===> FABRIC CA# - 0f73bdc ===> FABRIC SDK JAVA - 7fe73c4 ===> FABRIC SDK NODE - b7eb1d4`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-alpha3-snapshot-0f73bdc
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-alpha3-snapshot-d2bfa74
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-alpha3-snapshot-d2bfa74
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-alpha3-snapshot-d2bfa74
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-alpha3-snapshot-d2bfa74
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-alpha3-snapshot-d2bfa74
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-alpha3-snapshot-d2bfa74
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-alpha3-snapshot-d2bfa74
```
Docker images for "System z & power" are also available by modifying the last component in the repository based on the desired architecture.
```
System z = s390x
power = ppc64le
```
jimthematrix (Tue, 30 May 2017 17:32:34 GMT):
hi @rameshthoomu @tongli do you have a recommendation for java test coverage library? @rickr is looking into JCoCo (https://wiki.jenkins-ci.org/display/JENKINS/JaCoCo+Plugin), i assume installing this in the CI VMs is not gonna be difficult? or should we stay with cobertura since that's already installed (and used by node SDK jobs)?
tongli (Tue, 30 May 2017 17:32:35 GMT):
Has joined the channel.
tongli (Tue, 30 May 2017 17:43:21 GMT):
@jimthematrix have not worked with java for quite some time. Can not really comment on the tools, installing packages at CI is not an issue. just need these tools to be fast and be able to choose selective packages to test.
tongli (Tue, 30 May 2017 17:44:28 GMT):
we are looking to run only affected unit-test by a patch. and run full unit-test when patch set already got two +2s.
tongli (Tue, 30 May 2017 17:45:05 GMT):
this is to make sure that we do not miss anything and at the same time have a fast turn around time.
rameshthoomu (Tue, 30 May 2017 19:23:13 GMT):
Will work on Jcoco.. JJB is supporting https://docs.openstack.org/infra/jenkins-job-builder/publishers.html?highlight=jacoco#publishers.jacoco
rameshthoomu (Tue, 30 May 2017 19:23:52 GMT):
Will create JJB to include this in CI.. will work with @rickr
rameshthoomu (Tue, 30 May 2017 19:25:49 GMT):
@rickr let me know once the patch is ready to generate coverage reports..
rameshthoomu (Wed, 31 May 2017 13:07:27 GMT):
All, Docker Images are being published on below commits. **end-to-end (CLI)**, ** end-to-end (NODE) ** and **end-to-end (JAVA)** tests are working as expected on x86, s390x and power.
`===> FABRIC# -5ba27bf ===> FABRIC CA# - 0f73bdc ===> FABRIC SDK JAVA - 1b72c0e ===> FABRIC SDK NODE - dc1b011`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-alpha3-snapshot-0f73bdc
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-alpha3-snapshot-5ba27bf
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-alpha3-snapshot-5ba27bf
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-alpha3-snapshot-5ba27bf
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-alpha3-snapshot-5ba27bf
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-alpha3-snapshot-5ba27bf
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-alpha3-snapshot-5ba27bf
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-alpha3-snapshot-5ba27bf
```
Docker images for "System z & power" are also available by modifying the last component in the repository based on the desired architecture.
```
System z = s390x
power = ppc64le
```
tongli (Wed, 31 May 2017 14:20:41 GMT):
@rjones ping.
rjones (Wed, 31 May 2017 17:04:07 GMT):
@tongli yes?
tongli (Wed, 31 May 2017 17:04:57 GMT):
@rjones, good afternoon, I was talking with ramesh earlier today. Would like to ask you a question about the events coming from Gerrit.
rjones (Wed, 31 May 2017 17:05:13 GMT):
ask away
tongli (Wed, 31 May 2017 17:05:29 GMT):
we would like to know if the events coming from Gerrit can be passed to jobs.
tongli (Wed, 31 May 2017 17:05:53 GMT):
so that we know the change id of patch set. and possibly other information such as current +2 reviews.
rjones (Wed, 31 May 2017 17:07:31 GMT):
looking here for instance: https://logs.hyperledger.org/jobbuilder/vex-yul-hyp-jenkins-1/fabric-verify-x86_64/12453/console.log.gz
rjones (Wed, 31 May 2017 17:07:31 GMT):
looking here for instance: https://logs.hyperledger.org/jobbuilder/vex-yul-hyp-jenkins-1/fabric-verify-x86_64/12453/_build-enviroment-variables.txt.gz
rjones (Wed, 31 May 2017 17:07:51 GMT):
search for `GERRIT_PATCHSET_REVISION`
rjones (Wed, 31 May 2017 17:08:24 GMT):
actually, look here: https://logs.hyperledger.org/jobbuilder/vex-yul-hyp-jenkins-1/fabric-verify-x86_64/12453/_build-enviroment-variables.txt.gz
rjones (Wed, 31 May 2017 17:09:04 GMT):
`GERRIT_CHANGE_ID` shows the change ID
tongli (Wed, 31 May 2017 17:09:19 GMT):
ah, that is passed to the job as env variable?
rjones (Wed, 31 May 2017 17:09:35 GMT):
everything in that file is, yes
rjones (Wed, 31 May 2017 17:10:10 GMT):
well, everything with the prefix `GERRIT_`
rjones (Wed, 31 May 2017 17:10:40 GMT):
at the time these particular jobs are triggered, there are no votes
tongli (Wed, 31 May 2017 17:11:41 GMT):
great.
tongli (Wed, 31 May 2017 17:12:23 GMT):
All these variables get passed to job scripts so that these script can use them, right? want to confirm this.
rjones (Wed, 31 May 2017 17:12:55 GMT):
yes. what is your proposed use?
rjones (Wed, 31 May 2017 17:14:15 GMT):
there will be jobs that exist without corresponding gerrit events, and I'm not sure if a re-triggered job will have every single one of those set, for instance
tongli (Wed, 31 May 2017 17:20:20 GMT):
@rjones, I would like to add some logic so that when jobs are run, if there are already two +2 reviews, we run full unit-tests, if less than two +2, we run patch set affected unit-test.
tongli (Wed, 31 May 2017 17:20:49 GMT):
it will be just a bit script to see if a given patchset has how many +2 reviews.
tongli (Wed, 31 May 2017 17:21:18 GMT):
that is how I would like these things to be used.
rjones (Wed, 31 May 2017 17:21:59 GMT):
I'm not sure we can pass that in
rjones (Wed, 31 May 2017 17:22:37 GMT):
gerrit does have a JSON API, so you could query it then parse the results
rjones (Wed, 31 May 2017 17:23:31 GMT):
@tongli this is the plugin we're using: https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger
tongli (Wed, 31 May 2017 17:23:58 GMT):
REVIEWS=`GET https://gerrit.hyperledger.org/r/changes/$GERRIT_CHANGE_ID/reviewers | grep '"Code-Review": "+2"' | wc -l`
tongli (Wed, 31 May 2017 17:24:27 GMT):
I think we will just do curl get.
tongli (Wed, 31 May 2017 17:24:45 GMT):
use a bit of script for that.
rjones (Wed, 31 May 2017 17:27:12 GMT):
could you work with @rameshthoomu to try that out in the sandbox?
rjones (Wed, 31 May 2017 17:27:40 GMT):
I don't know if you'll have enough permissions to call that API in jenkins (but you might!)
tongli (Wed, 31 May 2017 17:40:24 GMT):
sure, will test it out first.
tongli (Wed, 31 May 2017 19:38:14 GMT):
https://logs.hyperledger.org/jobbuilder/vex-yul-hyp-jenkins-1/fabric-verify-x86_64/12453/_build-enviroment-variables.txt.gz
rameshthoomu (Wed, 31 May 2017 19:44:56 GMT):
I don't see these variables in sandbox... I triggered this job manually https://jenkins.hyperledger.org/sandbox/job/fabric-verify-x86_64/ from sandbox
rameshthoomu (Wed, 31 May 2017 19:45:17 GMT):
https://logs.hyperledger.org/sandbox/vex-yul-hyp-jenkins-2/fabric-verify-x86_64/5/_build-enviroment-variables.txt.gz
rjones (Wed, 31 May 2017 20:07:16 GMT):
like I said - if you manually trigger it, the gerrit trigger doesn't pass anything in
rameshthoomu (Thu, 01 Jun 2017 12:48:31 GMT):
All, Docker Images are being published on below commits. **end-to-end (CLI)**, ** end-to-end (NODE) ** and **end-to-end (JAVA)** tests are working as expected on x86 and s390x.
`===> FABRIC# -89f1da4 ===> FABRIC CA# - e4e0a0d ===> FABRIC SDK JAVA - 9f670a6 ===> FABRIC SDK NODE - a494295`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-alpha3-snapshot-e4e0a0d
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-alpha3-snapshot-89f1da4
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-alpha3-snapshot-89f1da4
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-alpha3-snapshot-89f1da4
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-alpha3-snapshot-89f1da4
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-alpha3-snapshot-89f1da4
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-alpha3-snapshot-89f1da4
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-alpha3-snapshot-89f1da4
```
Docker images for "System z" are also available by modifying the last component in the repository based on the desired architecture.
```
System z = s390x
```
observed e2e tests are failed in power node with grpc connection error.. Re-triggered the job again.. WIll update once done.
jpatchell (Thu, 01 Jun 2017 14:23:17 GMT):
Has joined the channel.
jpatchell (Thu, 01 Jun 2017 15:27:52 GMT):
I'm running into issues with the CI and my change that I submitted ( https://gerrit.hyperledger.org/r/#/c/9875/2 ). Does anyone have some ideas as to why it is failing?
rameshthoomu (Thu, 01 Jun 2017 15:38:32 GMT):
@jpatchell looking into this
rameshthoomu (Thu, 01 Jun 2017 16:45:59 GMT):
Updated docker images for power
re-triggered e2e tests on power node and this time it worked successfully.. uploaded below docker images
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-alpha3-snapshot-e4e0a0d
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-alpha3-snapshot-72e4d1a
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-alpha3-snapshot-72e4d1a
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-alpha3-snapshot-72e4d1a
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-alpha3-snapshot-72e4d1a
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-alpha3-snapshot-72e4d1a
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-alpha3-snapshot-72e4d1a
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-alpha3-snapshot-72e4d1a
```
rameshthoomu (Fri, 02 Jun 2017 11:04:49 GMT):
All, Docker Images are being published on below commits. **end-to-end (CLI)**, ** end-to-end (NODE) ** and **end-to-end (JAVA)** tests are working as expected on x86 and s390x.
`===> FABRIC# -3b40efa ===> FABRIC CA# - 5722d96 ===> FABRIC SDK JAVA - 15d2faf ===> FABRIC SDK NODE - 9898763`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-alpha3-snapshot-5722d96
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-alpha3-snapshot-3b40efa
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-alpha3-snapshot-3b40efa
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-alpha3-snapshot-3b40efa
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-alpha3-snapshot-3b40efa
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-alpha3-snapshot-3b40efa
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-alpha3-snapshot-3b40efa
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-alpha3-snapshot-3b40efa
```
Docker images for "System z" are also available by modifying the last component in the repository based on the desired architecture.
```
System z = s390x
```
observed e2e tests are failed in power node with grpc connection error.. Re-triggered the job again.. WIll update once done.
tongli (Fri, 02 Jun 2017 19:00:44 GMT):
really need some helping soul to help get this merged. https://gerrit.hyperledger.org/r/#/c/9811, please help out reviewing , this patch is to make our CI run a lot faster for all patch sets.
tongli (Fri, 02 Jun 2017 19:01:23 GMT):
@here, really need some helping soul to help get this merged. https://gerrit.hyperledger.org/r/#/c/9811, please help out reviewing , this patch is to make our CI run a lot faster for all patch sets.
cbf (Fri, 02 Jun 2017 19:02:07 GMT):
@tongli the channel to use to make a plea for reviews is #fabric-pr-review ;-)
tongli (Fri, 02 Jun 2017 19:02:25 GMT):
ok. I try there too.
tongli (Fri, 02 Jun 2017 19:02:26 GMT):
thanks.
weeds (Sun, 04 Jun 2017 12:03:57 GMT):
@rameshtoomu Ramesh, I need some clarity- I see your run, but then I see things in the daily Jenkins- https://jenkins.hyperledger.org/view/Daily/
weeds (Sun, 04 Jun 2017 12:03:57 GMT):
@rameshthoomu Ramesh, I need some clarity- I see your run, but then I see things in the daily Jenkins- https://jenkins.hyperledger.org/view/Daily/
weeds (Sun, 04 Jun 2017 12:04:11 GMT):
Why are these so different? I'm really confused by this, but maybe not understanding the difference?
weeds (Sun, 04 Jun 2017 12:06:11 GMT):
jenkins says we are failing and yet you are saying all the tests are passing as expected
weeds (Sun, 04 Jun 2017 12:11:15 GMT):
except for the one piece you highighted
rameshthoomu (Sun, 04 Jun 2017 15:36:31 GMT):
@weeds Daily I run e2e jobs (node) (java) (cli) in sandbox and publish docker images and post the result back to #fabric-ci RC channel... Where as in daily Jenkins (community Jenkins), we run daily test suite (fabric/test/regression/daily) like chaincode tests..
rameshthoomu (Sun, 04 Jun 2017 15:38:51 GMT):
Couple of the patches are in review. Once they are merged will integrate them in daily test suite and run in community Jenkins.. till then we fetch these open patches from gerrit test these patches from sandbox jenkins..
cbf (Sun, 04 Jun 2017 21:59:02 GMT):
@rameshthoomu which patches? I looked for things that were mergable and there was nothing
cbf (Sun, 04 Jun 2017 21:59:02 GMT):
@rameshthoomu which patches? I looked for things that were mergeable and there was nothing
rameshthoomu (Sun, 04 Jun 2017 22:01:46 GMT):
Couple of @Nishi and @Sandeep patches are in review.. and I am working on keeping @AdnanC ledger tests and @dongming PTE tests in community daily test suite..
Sandeep (Sun, 04 Jun 2017 22:01:46 GMT):
Has joined the channel.
Nishi (Sun, 04 Jun 2017 22:01:47 GMT):
Has joined the channel.
rameshthoomu (Sun, 04 Jun 2017 22:02:34 GMT):
Will complete this by tomorrow..
guruce (Mon, 05 Jun 2017 07:28:22 GMT):
Has joined the channel.
rameshthoomu (Mon, 05 Jun 2017 12:35:04 GMT):
All, Docker Images are being published on below commits. **end-to-end (CLI)**, ** end-to-end (NODE) ** and **end-to-end (JAVA)** tests are working as expected on x86, s390x. and ppc64le
`===> FABRIC# -f6abb18 ===> FABRIC CA# - 4435ed8 ===> FABRIC SDK JAVA - 5ced72d ===> FABRIC SDK NODE - 63ea71d`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-alpha3-snapshot-4435ed8
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-alpha3-snapshot-f6abb18
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-alpha3-snapshot-f6abb18
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-alpha3-snapshot-f6abb18
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-alpha3-snapshot-f6abb18
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-alpha3-snapshot-f6abb18
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-alpha3-snapshot-f6abb18
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-alpha3-snapshot-f6abb18
```
Docker images for "System z & power" are also available by modifying the last component in the repository based on the desired architecture.
```
System z = s390x
power = ppc64le
```
bmos299 (Mon, 05 Jun 2017 13:51:35 GMT):
I think the confusion is that for the daily run that publishes the image there is *not a Jenkins dashboard* view. If the test fails, Ramesh opens Jira Bugs. If it passes, we publish images. Now, for the daily testsuite from the https://github.com/hyperledger/fabric/tree/master/test/regression/daily folder, this is run in the Jenkins sandbox and published to, https://jenkins.hyperledger.org/sandbox/job/daily/test_results_analyzer/. It is not run everyday and actually runs from @rameshthoomu private repo. At this point it was more of a PoC for the community and needs to made production ready asap.
jpatchell (Mon, 05 Jun 2017 17:17:08 GMT):
@rameshthoomu Any update on https://gerrit.hyperledger.org/r/#/c/9875/2?
rameshthoomu (Mon, 05 Jun 2017 19:00:59 GMT):
@jpatchell I see this patch set is failing consistently https://gerrit.hyperledger.org/r/#/c/9875/2.. Running this in local build machine..
rameshthoomu (Mon, 05 Jun 2017 19:01:14 GMT):
will let you know the status soon..
harsha (Mon, 05 Jun 2017 19:12:34 GMT):
@rameshthoomu I see power specific docker images to be updated last 4 days back https://hub.docker.com/r/rameshthoomu/fabric-peer-ppc64le/tags/
harsha (Mon, 05 Jun 2017 19:12:34 GMT):
@rameshthoomu I see power specific docker images were updated 4 days back https://hub.docker.com/r/rameshthoomu/fabric-peer-ppc64le/tags/
harsha (Mon, 05 Jun 2017 19:12:42 GMT):
Am I checking the right URL ?
rameshthoomu (Mon, 05 Jun 2017 19:19:02 GMT):
oh wait.. configuration issue.. fixed now. will update the status soon..
harsha (Mon, 05 Jun 2017 19:19:30 GMT):
Sure thing.
rameshthoomu (Mon, 05 Jun 2017 21:14:37 GMT):
@harsha e2e tests are failing in sandbox power-1 node..
rjones (Mon, 05 Jun 2017 21:19:51 GMT):
@rameshthoomu I thought power was no longer supported?
rameshthoomu (Mon, 05 Jun 2017 21:24:08 GMT):
@rjones yes. Have a job to run e2e tests on power node in sandbox.. Will check with @SriramaSharma on this and will disable this test from sandbox..
rjones (Mon, 05 Jun 2017 21:25:08 GMT):
ok
rameshthoomu (Mon, 05 Jun 2017 21:29:48 GMT):
@jpatchell I have verified these failures ( https://gerrit.hyperledger.org/r/#/c/9875/2) and didn't see CI related issues involved in this failure.. Ran this tests manually in local machine and observed same failures.
rameshthoomu (Mon, 05 Jun 2017 21:30:09 GMT):
if possible could you please rebase this patch set and try again please..
SriramaSharma (Mon, 05 Jun 2017 23:32:55 GMT):
@rameshthoomu @rjones power was disabled only for gating builds as it was taking long build time. We have been working on it in the background and are now seeing same build time for verify-fabric builds as seen for x86. Once we do some more tests for consistency in results, we will propose back to community to include power for verify-builds in a week's time. Until then request you continue to have e2e tests on sandbox as it ensures that we are fine without build issues on daily basis.
SriramaSharma (Mon, 05 Jun 2017 23:32:55 GMT):
@rameshthoomu @rjones power was disabled only for gating builds as it was taking log build time. We have been working on it in the background and are now seeing same build time for verify-fabric builds as seen for x86. Once we do some more tests for consistency in results, we will propose back to community to include power for verify-builds in a week's time. Until then request you continue to have e2e tests on sandbox as it ensures that we are fine without build issues on daily basis.
rjones (Mon, 05 Jun 2017 23:33:29 GMT):
ok I see now thank you
rameshthoomu (Tue, 06 Jun 2017 13:24:37 GMT):
All, Docker Images are being published on below commits. **end-to-end (CLI)**, ** end-to-end (NODE) ** and **end-to-end (JAVA)** tests are working as expected on x86 and s390x.
`===> FABRIC# -88d4845 ===> FABRIC CA# - a2fb8ea ===> FABRIC SDK JAVA - 00e6c80 ===> FABRIC SDK NODE - 4f03644`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-alpha3-snapshot-a2fb8ea
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-alpha3-snapshot-88d4845
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-alpha3-snapshot-88d4845
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-alpha3-snapshot-88d4845
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-alpha3-snapshot-88d4845
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-alpha3-snapshot-88d4845
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-alpha3-snapshot-88d4845
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-alpha3-snapshot-88d4845
```
Docker images for "System z " are also available by modifying the last component in the repository based on the desired architecture.
```
System z = s390x
```
Observed e2e (cli) tests are failing on power node (on available node in sandbox)
rameshthoomu (Tue, 06 Jun 2017 13:26:56 GMT):
@harsha I still see e2e tests are failing in power node.. Could you please test on another node or can you run this manually in sandbox power node..
harsha (Tue, 06 Jun 2017 14:45:51 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=So2i9X4RPBXggAGvR) @rameshthoomu tested on my build system `e2e_cli` is working fine. Let me check on blockchain-1 and will ping back.
rameshthoomu (Tue, 06 Jun 2017 15:06:47 GMT):
sure thanks
lehors (Tue, 06 Jun 2017 15:49:23 GMT):
hi there
lehors (Tue, 06 Jun 2017 15:49:42 GMT):
so, unfortunately it seems that our CI remains quite unreliable
lehors (Tue, 06 Jun 2017 15:50:29 GMT):
I made a change to the docs and the build job failed
lehors (Tue, 06 Jun 2017 15:50:51 GMT):
https://gerrit.hyperledger.org/r/#/c/10155/
lehors (Tue, 06 Jun 2017 15:51:03 GMT):
the build failed on Z
rameshthoomu (Tue, 06 Jun 2017 15:52:03 GMT):
@lehors looking into this..
lehors (Tue, 06 Jun 2017 15:52:09 GMT):
hold on, wrong link: https://gerrit.hyperledger.org/r/#/c/10155/
lehors (Tue, 06 Jun 2017 15:52:16 GMT):
argh
lehors (Tue, 06 Jun 2017 15:52:25 GMT):
https://gerrit.hyperledger.org/r/#/c/9469/
lehors (Tue, 06 Jun 2017 15:52:31 GMT):
finally got it right
rameshthoomu (Tue, 06 Jun 2017 15:54:31 GMT):
Unit-tests on z and behave tests are failed..
rameshthoomu (Tue, 06 Jun 2017 15:54:31 GMT):
Unit-tests on z and node e2e tests are failed..
rameshthoomu (Tue, 06 Jun 2017 15:54:55 GMT):
it seems network issue caused unit-test failures on z..
rameshthoomu (Tue, 06 Jun 2017 15:54:59 GMT):
```
00:06:17.875 > Could not download guava.jar (com.google.guava:guava:18.0)
00:06:17.875 > Could not get resource 'https://repo1.maven.org/maven2/com/google/guava/guava/18.0/guava-18.0.jar'.
00:06:17.875 > Connection reset
00:06:17.875
```
lehors (Tue, 06 Jun 2017 15:55:01 GMT):
which is totally unrelated to my change...
lehors (Tue, 06 Jun 2017 15:55:13 GMT):
I see
lehors (Tue, 06 Jun 2017 15:55:55 GMT):
hard to guard against that but maybe we should have a retry or something
rameshthoomu (Tue, 06 Jun 2017 15:56:09 GMT):
and I see node e2e tests are failed and it could be intermittent issue.
rameshthoomu (Tue, 06 Jun 2017 15:56:21 GMT):
no will re-trrigger those two failed jobs..
rameshthoomu (Tue, 06 Jun 2017 15:57:07 GMT):
done
rameshthoomu (Tue, 06 Jun 2017 15:57:33 GMT):
Will see other results of these jobs in other patch sets..
rameshthoomu (Tue, 06 Jun 2017 15:57:33 GMT):
Will see results of these jobs in other patch sets..
lehors (Tue, 06 Jun 2017 15:58:54 GMT):
ok, thanks
lehors (Tue, 06 Jun 2017 15:59:51 GMT):
can I restart the build myself? or do you have special privileges?
rameshthoomu (Tue, 06 Jun 2017 16:00:41 GMT):
yes I can re-trigger specific builds..
rameshthoomu (Tue, 06 Jun 2017 16:01:05 GMT):
triggered both failed jobs.. Will monitor this run..
shimos (Tue, 06 Jun 2017 17:01:42 GMT):
Has joined the channel.
rameshthoomu (Tue, 06 Jun 2017 17:04:45 GMT):
@lehors got +1 (verified) on https://gerrit.hyperledger.org/r/#/c/9469
rjones (Tue, 06 Jun 2017 18:16:21 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=bjcqWEs24LptfsjyA) @lehors if you leave a comment on your change that is "reverify" (nothing else, just that word) it should retrigger the builds.
lehors (Tue, 06 Jun 2017 19:15:12 GMT):
@rameshthoomu @rjones thanks!
rameshthoomu (Tue, 06 Jun 2017 21:33:25 GMT):
fabric go unit-tests are failing.. https://jira.hyperledger.org/browse/FAB-4434
jeffgarratt (Tue, 06 Jun 2017 23:37:36 GMT):
@rameshthoomu I cannot refresh https://jenkins.hyperledger.org/job/fabric-verify-x86_64
jeffgarratt (Tue, 06 Jun 2017 23:37:55 GMT):
my job failed and I cannot see the results. Anyone else having this issue?
rameshthoomu (Tue, 06 Jun 2017 23:40:02 GMT):
will check..
rameshthoomu (Tue, 06 Jun 2017 23:41:52 GMT):
@rjones @jwagantall Jenkins is not accessible.. Getting 504 error
rameshthoomu (Tue, 06 Jun 2017 23:41:52 GMT):
@rjones Jenkins is not accessible.. Getting 504 error
rjones (Tue, 06 Jun 2017 23:42:13 GMT):
@rameshthoomu yes, we're discussing in #ci-pipeline
rameshthoomu (Tue, 06 Jun 2017 23:42:27 GMT):
oh sorry.. didn't check there.
rameshthoomu (Wed, 07 Jun 2017 11:47:15 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=8cKjpxMoqGAsXcjv8) @harsha Did you check e2e tests on blockchain-1 (sandbox power node) ?
rameshthoomu (Wed, 07 Jun 2017 11:53:17 GMT):
All, Docker Images are being published on below commits. **end-to-end (CLI)**, ** end-to-end (NODE) ** and **end-to-end (JAVA)** tests are working as expected on x86 and s390x.
`===> FABRIC# -52853f8 ===> FABRIC CA# - c9372be ===> FABRIC SDK JAVA - 99f321b ===> FABRIC SDK NODE - 4f03644`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-alpha3-snapshot-c9372be
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-alpha3-snapshot-52853f8
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-alpha3-snapshot-52853f8
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-alpha3-snapshot-52853f8
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-alpha3-snapshot-52853f8
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-alpha3-snapshot-52853f8
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-alpha3-snapshot-52853f8
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-alpha3-snapshot-52853f8
```
Docker images for "System z " are also available by modifying the last component in the repository based on the desired architecture.
```
System z = s390x
```
Observed e2e (cli) tests are failing only on power node available in sandbox. @harsha is working on this.
rameshthoomu (Wed, 07 Jun 2017 11:53:17 GMT):
All, Docker Images are being published on below commits. **end-to-end (CLI)**, ** end-to-end (NODE) ** and **end-to-end (JAVA)** tests are working as expected on x86 and s390x.
`===> FABRIC# -52853f8 ===> FABRIC CA# - c9372be ===> FABRIC SDK JAVA - 99f321b ===> FABRIC SDK NODE - 4f03644`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-alpha3-snapshot-c9372be
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-alpha3-snapshot-52853f8
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-alpha3-snapshot-52853f8
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-alpha3-snapshot-52853f8
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-alpha3-snapshot-52853f8
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-alpha3-snapshot-52853f8
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-alpha3-snapshot-52853f8
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-alpha3-snapshot-52853f8
```
Docker images for "System z " are also available by modifying the last component in the repository based on the desired architecture.
```
System z = s390x
```
Observed e2e (cli) tests are failing only on power node available in sandbox. @harsha is working on this.
rameshthoomu (Wed, 07 Jun 2017 11:53:17 GMT):
All, Docker Images are being published on below commits. **end-to-end (CLI)**, ** end-to-end (NODE) ** and **end-to-end (JAVA)** tests are working as expected on x86 and s390x.
`===> FABRIC# -52853f8 ===> FABRIC CA# - c9372be ===> FABRIC SDK JAVA - 99f321b ===> FABRIC SDK NODE - 4f03644`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-alpha3-snapshot-c9372be
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-alpha3-snapshot-52853f8
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-alpha3-snapshot-52853f8
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-alpha3-snapshot-52853f8
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-alpha3-snapshot-52853f8
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-alpha3-snapshot-52853f8
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-alpha3-snapshot-52853f8
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-alpha3-snapshot-52853f8
rameshthoomu/fabric-tools-x86_64:x86_64-1.0.0-alpha3-snapshot-52853f8
```
Docker images for "System z " are also available by modifying the last component in the repository based on the desired architecture.
```
System z = s390x
```
Observed e2e (cli) tests are failing only on power node available in sandbox. @harsha is working on this.
harsha (Wed, 07 Jun 2017 12:15:43 GMT):
@rameshthoomu I have observed `orderer container` is crashing whilst executing `network_setup up` further investigating the logs shows the cause to be `go-panic`
harsha (Wed, 07 Jun 2017 12:15:43 GMT):
@rameshthoomu I have observed `orderer container` is crashing whilst executing `./network_setup.sh up` further investigating the orderer logs shows the cause to be `go-panic`
tongli (Wed, 07 Jun 2017 12:16:23 GMT):
@rameshthoomu in office now, if you wanna to stop by.
davidkel (Wed, 07 Jun 2017 12:29:30 GMT):
@rameshthoomu do you know when the next unstable publish to npm for the node sdk will be ? There is a fix which has been merged but the latest unstable currently doesn't have it.
rameshthoomu (Wed, 07 Jun 2017 13:26:29 GMT):
@davidkel I see unstable version is published a day ago fabric-ca-client@1.0.0-snapshot.65 and fabric-client@1.0.0-snapshot.65
davidkel (Wed, 07 Jun 2017 13:26:59 GMT):
@rameshthoomu unfortunately that snapshot doesn't contain a fix I need
rameshthoomu (Wed, 07 Jun 2017 13:27:43 GMT):
Could you please provide the fix patchset..
davidkel (Wed, 07 Jun 2017 13:28:25 GMT):
I can give you the Jira which is fab-4374 and the history from got shows a merge on it was done
davidkel (Wed, 07 Jun 2017 13:28:25 GMT):
I can give you the Jira which is fab-4374 and the history from git shows a merge on it was done
rameshthoomu (Wed, 07 Jun 2017 13:28:33 GMT):
sure will check
davidkel (Wed, 07 Jun 2017 13:29:20 GMT):
Thank you. I wanted to test it as the fix needs to get into the next release
rameshthoomu (Wed, 07 Jun 2017 13:30:30 GMT):
try using this version fabric-ca-client@1.0.0-snapshot.64
rameshthoomu (Wed, 07 Jun 2017 13:30:43 GMT):
fabric-client@1.0.0-snapshot.64
davidkel (Wed, 07 Jun 2017 13:32:05 GMT):
ok, will try any reason why the latest snapshot containers an older codebase to .64 ?
davidkel (Wed, 07 Jun 2017 13:32:05 GMT):
ok, will try any reason why the latest snapshot contains an older codebase to .64 ?
rameshthoomu (Wed, 07 Jun 2017 13:34:43 GMT):
no the latest snapshot is .65.. But .64 version is associated to the fix patch set.. https://gerrit.hyperledger.org/r/#/c/10169/
davidkel (Wed, 07 Jun 2017 13:35:28 GMT):
ok, can I be confident that this fix will make it into the next stable release being done today ?
rameshthoomu (Wed, 07 Jun 2017 13:41:02 GMT):
the fix should be available in .64 and .65 snapshot versions.. not sure why .65 version doesn't have the fix you are looking for. @jimthematrix could you please look into this..
davidkel (Wed, 07 Jun 2017 13:43:11 GMT):
Thanks, I see the fix in .64 testing it now.
rahulhegde (Wed, 07 Jun 2017 17:32:12 GMT):
We just upgraded to new Fabric Images (5th June) and found that peer install is failing (e2e cli).
```
2017-06-07 17:29:44.725 UTC [msp] GetDefaultSigningIdentity -> DEBU 005 Obtaining default signing identity
2017-06-07 17:29:44.725 UTC [golang-platform] getCodeFromFS -> DEBU 006 getCodeFromFS bsl/clsnet-cls-chaincode/public
Error: Error getting chaincode code chaincode: Error getting chaincode package bytes: Error obtaining imports: go list: failed with error: "exec: not started"
```
rahulhegde (Wed, 07 Jun 2017 17:32:12 GMT):
@rameshthoomu
We just upgraded to new Fabric Images (i.e. 5th June) and found that peer install is failing (e2e cli).
```
2017-06-07 17:29:44.725 UTC [msp] GetDefaultSigningIdentity -> DEBU 005 Obtaining default signing identity
2017-06-07 17:29:44.725 UTC [golang-platform] getCodeFromFS -> DEBU 006 getCodeFromFS bsl/clsnet-cls-chaincode/public
Error: Error getting chaincode code chaincode: Error getting chaincode package bytes: Error obtaining imports: go list: failed with error: "exec: not started"
```
Chaincode is accessible via peer CLI container - ls $GOPATH/src/bsl/clsnet-cls-chaincode/public
rahulhegde (Wed, 07 Jun 2017 17:32:12 GMT):
@rameshthoomu @Ratnakar
We just upgraded to new Fabric Images (i.e. 5th June) and found that peer install is failing (e2e cli).
```
2017-06-07 17:29:44.725 UTC [msp] GetDefaultSigningIdentity -> DEBU 005 Obtaining default signing identity
2017-06-07 17:29:44.725 UTC [golang-platform] getCodeFromFS -> DEBU 006 getCodeFromFS bsl/clsnet-cls-chaincode/public
Error: Error getting chaincode code chaincode: Error getting chaincode package bytes: Error obtaining imports: go list: failed with error: "exec: not started"
```
Chaincode is accessible via peer CLI container - ls $GOPATH/src/bsl/clsnet-cls-chaincode/public
rameshthoomu (Wed, 07 Jun 2017 18:19:51 GMT):
@rahulhegde publishing tools image now.. will let you know once done..
rahulhegde (Wed, 07 Jun 2017 18:30:40 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=JkbjeqMQfy2j5Wmfr) @rameshthoomu
Hope fabric-tool image will be compatible with the 5th June Fabric-CI published fabric images?
bmos299 (Wed, 07 Jun 2017 18:31:28 GMT):
@rahulhegde you are aware of the change https://github.com/hyperledger/fabric/blob/master/examples/e2e_cli/docker-compose-cli.yaml#L42 and @rameshthoomu is working on building the image or you can do a make docker and which will build you the fabric-tools image.
xixuejia (Wed, 07 Jun 2017 18:35:42 GMT):
Has joined the channel.
rahulhegde (Wed, 07 Jun 2017 18:37:43 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=YQX3YuxGiCGPBdP3x) @bmos299
Hi Barry,
Yes - I just came to know about fabric-tool images, @rameshthoomu, @Ratnakar informed me. We use a similar E2E CLI script for bootstrapping our network and it worked on 19th May Fabric Images .
We don't have build system inside our org, so we won't be able to do it.
rahulhegde (Wed, 07 Jun 2017 18:37:43 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=YQX3YuxGiCGPBdP3x) @bmos299
Hi Barry,
Yes - I just came to know about fabric-tool image, @rameshthoomu, @Ratnakar informed me. We use a similar E2E CLI script for bootstrapping our network and it worked on 19th May Fabric Images .
We don't have build system inside our org, so we won't be able to do it.
rameshthoomu (Wed, 07 Jun 2017 18:42:41 GMT):
@rahulhegde please try now.. [ ](https://chat.hyperledger.org/channel/fabric-ci?msg=BidDxuZh6XCdW5nqq) @rameshthoomu
rahulhegde (Wed, 07 Jun 2017 18:47:39 GMT):
We will try these new images - thank you.
bmos299 (Wed, 07 Jun 2017 19:33:23 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=z4MZjNnQ93hQBkyXv) @rahulhegde Please keep us posted.
jimthematrix (Thu, 08 Jun 2017 13:02:04 GMT):
@rameshthoomu @rjones @jwagantall in the last couple of days we are getting quite a few runs in fabric-sdk-node verify builds where the x86 build failed erratically, and it takes one or sometimes two `reverify` runs to get a clean build. in the meanwhile s390 builds have been always reliable
jimthematrix (Thu, 08 Jun 2017 13:02:29 GMT):
see this as an example: https://gerrit.hyperledger.org/r/#/c/10321/
rameshthoomu (Thu, 08 Jun 2017 13:05:32 GMT):
@jimthematrix looking into this..
rameshthoomu (Thu, 08 Jun 2017 13:22:38 GMT):
All, Docker Images are being published on below commits. **end-to-end (CLI)**, ** end-to-end (NODE) ** and **end-to-end (JAVA)** tests are working as expected on x86 and s390x.
`===> FABRIC# -85ccddc ===> FABRIC CA# - c9372be ===> FABRIC SDK JAVA# - fbbfa7c ===> FABRIC SDK NODE# - 7d62c53`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-alpha3-snapshot-c9372be
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-alpha3-snapshot-85ccddc
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-alpha3-snapshot-85ccddc
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-alpha3-snapshot-85ccddc
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-alpha3-snapshot-85ccddc
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-alpha3-snapshot-85ccddc
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-alpha3-snapshot-85ccddc
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-alpha3-snapshot-85ccddc
rameshthoomu/fabric-tools-x86_64:x86_64-1.0.0-alpha3-snapshot-85ccddc
```
Docker images for "System z " are also available by modifying the last component in the repository based on the desired architecture.
```
System z = s390x
```
FAB-4451 - e2e tests are failing on sandbox power nodes.
jimthematrix (Thu, 08 Jun 2017 13:32:40 GMT):
@rameshthoomu https://gerrit.hyperledger.org/r/#/c/10321 verify on x86 failed again (3rd time now)
rameshthoomu (Thu, 08 Jun 2017 13:48:13 GMT):
I don't see any difference in z and x86 job configuration.. Looking more into the failure log.. Could you pls rebase the patch?
rameshthoomu (Thu, 08 Jun 2017 14:24:15 GMT):
@jimthematrix again failed even after rebase..
jyellick (Thu, 08 Jun 2017 14:48:22 GMT):
Has joined the channel.
jimthematrix (Thu, 08 Jun 2017 15:24:26 GMT):
also the same test (instantiate chaincode) ran fine in fabric verify e2e build, but failing consistently in fabric-sdk-node verify
jimthematrix (Thu, 08 Jun 2017 15:24:26 GMT):
also the same test (instantiate chaincode) ran fine in fabric verify e2e build, but failing consistently in fabric-sdk-node x86 verify
rameshthoomu (Thu, 08 Jun 2017 15:31:02 GMT):
testing fix.. will let you know the update
jimthematrix (Thu, 08 Jun 2017 15:31:55 GMT):
thanks
rameshthoomu (Thu, 08 Jun 2017 15:52:28 GMT):
@jimthematrix seems it's working now..
rameshthoomu (Thu, 08 Jun 2017 15:53:03 GMT):
re-triggered the release merge job..
jyellick (Thu, 08 Jun 2017 16:50:25 GMT):
Are we tracking the very high rate of CI failure for fabric? It seems to be > 50% false positive over the last 24 hours
rameshthoomu (Thu, 08 Jun 2017 16:53:50 GMT):
@jyellick we had this issue but this issue was fixed..
rameshthoomu (Thu, 08 Jun 2017 16:54:11 GMT):
Could you please specify the build # for reference..
jyellick (Thu, 08 Jun 2017 16:54:40 GMT):
Fixed as of what time?
rameshthoomu (Thu, 08 Jun 2017 16:55:29 GMT):
day before yesterday..
rameshthoomu (Thu, 08 Jun 2017 16:55:52 GMT):
if the patch set is not on that commit then we may see same failure.. in that case rebase may work..
rameshthoomu (Thu, 08 Jun 2017 16:56:27 GMT):
https://jira.hyperledger.org/browse/FAB-4412
jyellick (Thu, 08 Jun 2017 16:57:33 GMT):
For instance https://gerrit.hyperledger.org/r/#/c/10273/
jyellick (Thu, 08 Jun 2017 16:58:27 GMT):
Okay, I will try rebasing, thanks
rameshthoomu (Thu, 08 Jun 2017 17:00:53 GMT):
@jyellick also this error and it caused failure on many verify builds https://jira.hyperledger.org/browse/FAB-4434
jyellick (Thu, 08 Jun 2017 17:01:03 GMT):
https://jenkins.hyperledger.org/job/fabric-verify-x86_64/13018/console
https://jenkins.hyperledger.org/job/fabric-verify-x86_64/13019/console
THese two failed recently and off current master
jyellick (Thu, 08 Jun 2017 17:01:42 GMT):
Yes, I made sure to rebase after 4434
rameshthoomu (Thu, 08 Jun 2017 17:03:01 GMT):
ok
jimthematrix (Thu, 08 Jun 2017 17:15:15 GMT):
@rameshthoomu fabric-sdk-node CI on x86 finally gives good builds again, thanks! I'm very curious what did you have to do to fix it?
rjones (Thu, 08 Jun 2017 17:43:50 GMT):
@jimthematrix perhaps this? https://gerrit.hyperledger.org/r/#/c/10355/1/jjb/fabric-sdk-node/include-raw-npm-publish.sh
rameshthoomu (Thu, 08 Jun 2017 17:48:13 GMT):
@rjones @jimthematrix I have updated the cleanup script.. now job clean `tmp/hfc* /tmp/npm* and hfc-key-store` these from x86..
rameshthoomu (Thu, 08 Jun 2017 17:48:43 GMT):
we have a cleanup script in z build nodes to do this..
rjones (Thu, 08 Jun 2017 17:54:32 GMT):
strange - x86 nodes shouldn't have anything to clean up, since they're new each time, no?
rameshthoomu (Thu, 08 Jun 2017 17:55:37 GMT):
yes that's the reason I didn't add this script earlier... But after I add this line in sandbox it worked and the same worked in production CI..
rameshthoomu (Thu, 08 Jun 2017 17:56:13 GMT):
not sure if that is the fix.. observed most of the builds passed after applied this patch.
jimthematrix (Thu, 08 Jun 2017 17:56:38 GMT):
interesting, I would have expected that clean up to make a difference, those tmp folder are not used any longer for a long time, now we are using $TMPDIR/hfc/* for all temp folders created during test run
jimthematrix (Thu, 08 Jun 2017 17:56:38 GMT):
interesting, I wouldn't have expected that clean up to make a difference, those tmp folder are not used any longer for a long time, now we are using $TMPDIR/hfc/* for all temp folders created during test run
rjones (Thu, 08 Jun 2017 17:57:23 GMT):
I'm skeptical
jimthematrix (Thu, 08 Jun 2017 17:57:42 GMT):
me too
rameshthoomu (Thu, 08 Jun 2017 21:24:07 GMT):
@cbf @weeds @bmos299 @rjones @jwagantall
Update on **beta release** from CI:
1) fabric-binaries -- `Pushed`
https://nexus.hyperledger.org/content/repositories/releases/org/hyperledger/fabric/fabric-binary/
2) fabric-ca images -- `Pushed`
https://hub.docker.com/r/hyperledger/fabric-ca/tags/
3) fabric docker images -- `Pushed`
https://hub.docker.com/r/hyperledger/fabric-peer/tags/
4) npm modules -- `Pushed`
https://www.npmjs.com/package/fabric-ca-client
https://www.npmjs.com/package/fabric-client
5) fabric-sdk-java -- `Published to maven`
http://repo1.maven.org/maven2/org/hyperledger/fabric-sdk-java/fabric-sdk-java/
Sync is in-progress https://mvnrepository.com/artifact/org.hyperledger.fabric-sdk-java/fabric-sdk-java
bmos299 (Thu, 08 Jun 2017 21:25:11 GMT):
Thank you @rameshthoomu
rjones (Thu, 08 Jun 2017 21:27:40 GMT):
very nice
cbf (Thu, 08 Jun 2017 21:28:22 GMT):
sweet
weeds (Thu, 08 Jun 2017 21:28:28 GMT):
nice job guys!
rjones (Thu, 08 Jun 2017 21:29:35 GMT):
@rameshthoomu how do I tell what keys signed http://repo1.maven.org/maven2/org/hyperledger/fabric-sdk-java/fabric-sdk-java/1.0.0-beta/ for instance? I see keys, but I don't see a file that says "this release signed by jwagantall@lf...."
rameshthoomu (Thu, 08 Jun 2017 21:31:05 GMT):
these are signed by `hyperledgerci` user
rameshthoomu (Thu, 08 Jun 2017 21:31:17 GMT):
checking..
rjones (Thu, 08 Jun 2017 21:32:17 GMT):
what did we do all of this work for - the detached signatures and everything? where is the private key for `hyperledgerci`? is it published in a directory
rameshthoomu (Thu, 08 Jun 2017 21:47:32 GMT):
I am not sure on private key for hyerpledgerci.. all I did was followed steps mentioned here http://central.sonatype.org/pages/working-with-pgp-signatures.html.
jwagantall (Thu, 08 Jun 2017 22:25:25 GMT):
Ramesh,,, that looks like the right commands... but how did it appeared as me? :(
jwagantall (Thu, 08 Jun 2017 22:25:35 GMT):
are those the newest ones?
rameshthoomu (Thu, 08 Jun 2017 23:51:40 GMT):
No.. these are published using hyperledgerci user.. Will check and let you know about the singing process..
jyellick (Fri, 09 Jun 2017 02:28:19 GMT):
@rameshthoomu Could you take a look at https://gerrit.hyperledger.org/r/#/c/10333/ ? You can see that in the 4 times that CI has run, one of the targets has failed every time (though every target has succeeded at least once)
rameshthoomu (Fri, 09 Jun 2017 02:30:11 GMT):
@jyellick checking
rameshthoomu (Fri, 09 Jun 2017 02:32:02 GMT):
I see one of the unit-test is failed with timeout error message..
```
00:44:12.305 unit-tests_1 | panic: test timed out after 20m0s
00:44:12.305 unit-tests_1 |
00:44:12.306 unit-tests_1 | goroutine 93 [running]:
```
rameshthoomu (Fri, 09 Jun 2017 02:32:35 GMT):
will re-trigger this build..
jyellick (Fri, 09 Jun 2017 02:34:55 GMT):
My concern is that after 4 runs through CI, there have been 4 failures, (even though the CR seems to be error free). It makes it very difficult to determine whether a CR's CI status is valid or not.
jyellick (Fri, 09 Jun 2017 02:34:55 GMT):
My concern is that after 4 runs through CI (today), there have been 4 failures, (even though the CR seems to be error free). It makes it very difficult to determine whether a CR's CI status is valid or not.
rameshthoomu (Fri, 09 Jun 2017 02:46:16 GMT):
@jyellick I see 3 different failures and above error is repeated in two of the build failures.. Will create a JIRA ticket for this and will take up to the developer
rameshthoomu (Fri, 09 Jun 2017 02:46:16 GMT):
@jyellick I see 3 different failures and all are with unit-tests.. I see the same error in one of the merged build and it repeated in two of the build failures.. Will create a JIRA ticket for this and will take up to the developer
jyellick (Fri, 09 Jun 2017 02:47:27 GMT):
Should I report erroneous CI failures here any time I see them?
jyellick (Fri, 09 Jun 2017 02:47:42 GMT):
I was only reporting because they seemed to be occurring with greater frequency
rameshthoomu (Fri, 09 Jun 2017 02:48:13 GMT):
sure please report here.. This is the channel to discuss about all the ci failures/status..
jyellick (Fri, 09 Jun 2017 02:52:09 GMT):
Thanks @rameshthoomu
rameshthoomu (Fri, 09 Jun 2017 03:22:26 GMT):
@jyellick https://jira.hyperledger.org/browse/FAB-4489
rameshthoomu (Fri, 09 Jun 2017 03:57:19 GMT):
finally got +1 on this patch https://gerrit.hyperledger.org/r/#/c/10333/..
rameshthoomu (Fri, 09 Jun 2017 15:01:47 GMT):
All, Docker Images are being published on below commits. **end-to-end (CLI)**, ** end-to-end (NODE) ** and **end-to-end (JAVA)** tests are working as expected on x86.
`===> FABRIC# -88ea3ee ===> FABRIC CA# - 60f4fae ===> FABRIC SDK JAVA# - a405626a ===> FABRIC SDK NODE# - 24d6899`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-rc1-snapshot-60f4fae
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-rc1-snapshot-88ea3ee
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-rc1-snapshot-88ea3ee
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-rc1-snapshot-88ea3ee
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-rc1-snapshot-88ea3ee
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-rc1-snapshot-88ea3ee
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-rc1-snapshot-88ea3ee
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-rc1-snapshot-88ea3ee
rameshthoomu/fabric-tools-x86_64:x86_64-1.0.0-rc1-snapshot-88ea3ee
```
Docker images on z are available on below commits
```
s390x-1.0.0-rc1-snapshot-60f4fae (ca)
s390x-1.0.0-rc1-snapshot-1038278 (fabric)
```
FAB-4451 - e2e tests are failing on sandbox power nodes. https://gerrit.hyperledger.org/r/#/c/10325/
xixuejia (Fri, 09 Jun 2017 18:10:41 GMT):
```18:08:02
18:08:02 reverify" -DGERRIT_EVENT_ACCOUNT_EMAIL=xixuejia@gmail.com -DGERRIT_PATCHSET_NUMBER=1 ******** "-DGERRIT_CHANGE_OWNER_NAME=Xi Xue Jia" clean deploy -V -B -q -Dmaven.repo.local=/tmp/r
18:08:02 Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T16:41:47+00:00)
18:08:02 Maven home: /w/tools/hudson.tasks.Maven_MavenInstallation/apache-maven-3.3.9
18:08:02 Java version: 1.8.0_131, vendor: Oracle Corporation
18:08:02 Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
18:08:02 Default locale: en_US, platform encoding: UTF-8
18:08:02 OS name: "linux", version: "4.4.0-47-generic", arch: "amd64", family: "unix"
18:08:16 [description-setter] Description set: Build logs: https://logs.hyperledger.org/jobbuilder/vex-yul-hyp-jenkins-1/fabric-verify-x86_64/13177
18:08:16 Skipping Cobertura coverage report as build was not UNSTABLE or better ...
18:08:18 Finished: FAILURE``` Got this error @rameshthoomu can you help?
rameshthoomu (Fri, 09 Jun 2017 18:11:16 GMT):
Could you please share the build number or patch set?
rameshthoomu (Fri, 09 Jun 2017 18:11:40 GMT):
above is the maven log..
xixuejia (Fri, 09 Jun 2017 18:11:58 GMT):
https://gerrit.hyperledger.org/r/#/c/10407/1
rameshthoomu (Fri, 09 Jun 2017 18:12:01 GMT):
actual error should be out above to this..
rameshthoomu (Fri, 09 Jun 2017 18:12:07 GMT):
ok looking into it..
xixuejia (Fri, 09 Jun 2017 18:12:22 GMT):
Thanks!
rameshthoomu (Fri, 09 Jun 2017 18:14:32 GMT):
I see goimport errors in both x86_64 and z nodes
```
00:00:54.838 The following files contain goimports errors
00:00:54.838 common/cauthdsl/cauthdsl_builder.go
00:00:54.838 The goimports command must be run for these files
00:00:55.218 Makefile:180: recipe for target 'linter' failed
00:00:55.218 make: *** [linter] Error 1
```
xixuejia (Fri, 09 Jun 2017 18:14:50 GMT):
ah, I see. Thanks!
jyellick (Sun, 11 Jun 2017 15:36:18 GMT):
@rameshthoomu I am seeing a wide variety of CI failures here: https://gerrit.hyperledger.org/r/#/c/10445/
The latest build timed out after 240 minutes, with sporadic failures across the other runs
yacovm (Sun, 11 Jun 2017 15:36:40 GMT):
Same thing, I think the CI physical server are under load
yacovm (Sun, 11 Jun 2017 15:36:53 GMT):
the bccsp tests are CPU-intensive and they take 5 min in CI now
yacovm (Sun, 11 Jun 2017 15:36:53 GMT):
the `bccsp/sw` tests are CPU-intensive and they take 5 min in CI now - doesn't make sense unless the physical CPU cores are under severe load.
in a 2-core VM it takes under 40sec
rameshthoomu (Sun, 11 Jun 2017 16:32:57 GMT):
Hi @jyellick verified couple of build results and observed the same error.. It seems network glitch on x86_64 nodes. Will ask @rjones @jwagantall to look into this
rameshthoomu (Sun, 11 Jun 2017 16:33:36 GMT):
I see recent/latest builds are passing.. Could you please reverify
rjones (Sun, 11 Jun 2017 21:59:40 GMT):
@yacovm @rameshthoomu the name of the minion tells you the spec - the x86_64 minions are 4 core, 4 gig of ram
yacovm (Sun, 11 Jun 2017 22:00:35 GMT):
ah? how do you derive the cores and RAM?
yacovm (Sun, 11 Jun 2017 22:00:45 GMT):
isn't 64 - 64 bits?
yacovm (Sun, 11 Jun 2017 22:01:04 GMT):
where is the name?
yacovm (Sun, 11 Jun 2017 22:02:16 GMT):
but now I see in the console `21:10:52 CPUs: 4`
yacovm (Sun, 11 Jun 2017 22:03:30 GMT):
Still, I've seen a CI log today that reported it took 5 minutes for a crypto unit test suite that takes 40 seconds on a 2-core VM on my laptop, any idea what could it be?
yacovm (Sun, 11 Jun 2017 22:03:30 GMT):
Still, I've seen a CI log today that reported it took 5 minutes for a crypto unit test suite that takes 40 seconds on a 2-core VM on my laptop, any idea what could it be?
Actually it's still like this: https://jenkins.hyperledger.org/job/fabric-verify-x86_64/13282/console `github.com/hyperledger/fabric/bccsp/sw 284.250s `
yacovm (Sun, 11 Jun 2017 22:03:30 GMT):
Still, I've seen a CI log today that reported it took 5 minutes for a crypto unit test suite that takes 40 seconds on a 2-core VM on my laptop, any idea what could it be?
Actually it's still like this: https://jenkins.hyperledger.org/job/fabric-verify-x86_64/13282/console `github.com/hyperledger/fabric/bccsp/sw 284.250s `
rjones (Mon, 12 Jun 2017 01:26:29 GMT):
@yacovm if you look here at the top: https://jenkins.hyperledger.org/job/fabric-verify-x86_64/13282/consoleFull you will see a line that starts `Building remotely on ubuntu1604-x86_64-4c-4g-2011 ...`
rjones (Mon, 12 Jun 2017 01:27:12 GMT):
parse that minion name as `ubuntu 16.04`, on `x86_64`, with `4 cores` and `4 gigs of ram` followed by a nonce
rjones (Mon, 12 Jun 2017 01:27:12 GMT):
parse that minion name as `ubuntu 16.4`, on `x86_64`, with `4 cores` and `4 gigs of ram` followed by a nonce
rameshthoomu (Mon, 12 Jun 2017 15:18:53 GMT):
All, Docker Images are being published on below commits. **end-to-end (CLI)**, ** end-to-end (NODE) ** and **end-to-end (JAVA)** tests are working as expected on x86 and s390x.
`===> FABRIC# - d51e2ad ===> FABRIC CA# - 1424b33 ===> FABRIC SDK JAVA# - 9992851 ===> FABRIC SDK NODE# - 680762e`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-rc1-snapshot-1424b33
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-rc1-snapshot-d51e2ad
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-rc1-snapshot-d51e2ad
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-rc1-snapshot-d51e2ad
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-rc1-snapshot-d51e2ad
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-rc1-snapshot-d51e2ad
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-rc1-snapshot-d51e2ad
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-rc1-snapshot-d51e2ad
rameshthoomu/fabric-tools-x86_64:x86_64-1.0.0-rc1-snapshot-d51e2ad
```
Docker images for "System z " are also available by modifying the last component in the repository based on the desired architecture.
```
System z = s390x
```
FAB-4451 - e2e tests are failing on sandbox power nodes. https://gerrit.hyperledger.org/r/#/c/10325/
rahulhegde (Mon, 12 Jun 2017 16:34:24 GMT):
@rameshthoomu
Do we have the changeset information for fabric-beta release, I am not able to find your post. Thanks.
rameshthoomu (Mon, 12 Jun 2017 16:42:26 GMT):
@rahulhegde I didn't publish beta images to rameshthoomu docker hub account.. But I see I have published images after beta is released and this is the fabric commit# `88ea3ee`
rameshthoomu (Mon, 12 Jun 2017 16:43:11 GMT):
If you need beta images you can pull from hyperledger or if you need I will publish to my account..
rahulhegde (Mon, 12 Jun 2017 16:44:08 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=9pM2EkwHmQ78Swjyn) @rameshthoomu
No I need the commit number only as we will have to build fabric-sdk for java. Is the JAR also published as part of Beta Release?
rameshthoomu (Mon, 12 Jun 2017 16:44:27 GMT):
yes..
rameshthoomu (Mon, 12 Jun 2017 16:44:43 GMT):
https://mvnrepository.com/artifact/org.hyperledger.fabric-sdk-java/fabric-sdk-java
rahulhegde (Mon, 12 Jun 2017 16:45:16 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=MdQNFKfLgfGe9Tg5Z) @rameshthoomu Cool - that's all i need. Thanks.
rameshthoomu (Mon, 12 Jun 2017 16:46:13 GMT):
sure thanks
rahulhegde (Mon, 12 Jun 2017 19:43:09 GMT):
@muralisr @bmos299
I am running on hyperledger beta fabric images and my chaincode instantiation fails, this used to pass on Alpha3 (19th May Images). Our chaincode refers to another package and seems there is something changed the way Peer CLI instantiates the chaincode.
```
2017-06-12 19:34:02.077 UTC [msp/identity] Sign -> DEBU 009 Sign: digest: DCCA7DE03A3B63CA3B84A29637CE6339E90B5C1C5E3101F5A35FE66364260EFA
Error: Error endorsing chaincode: rpc error: code = Unknown desc = Error starting container: Failed to generate platform-specific docker build: Error returned from build: 1 "chaincode/input/src/github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02/chaincode_example02.go:28:2: cannot find package "github.com/shopspring/decimal" in any of:
/chaincode/input/src/github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02/vendor/github.com/shopspring/decimal (vendor tree)
/opt/go/src/github.com/shopspring/decimal (from $GOROOT)
/chaincode/input/src/github.com/shopspring/decimal (from $GOPATH)
/opt/gopath/src/github.com/shopspring/decimal
```
Is this again related to ` govendor ` ==> I am running 2 command ` govendor init ` and ` govendor add external+ ` inside the chaincode folder ?
jimthematrix (Mon, 12 Jun 2017 20:09:19 GMT):
@rahulhegde so you guys use the peer CLI to install and instantiate chaincode?
jimthematrix (Mon, 12 Jun 2017 20:09:53 GMT):
https://gerrit.hyperledger.org/r/#/c/6991/
rahulhegde (Mon, 12 Jun 2017 20:09:55 GMT):
At this point of time - we are using CLI for bootstrapping the fabric network.
jimthematrix (Mon, 12 Jun 2017 20:10:12 GMT):
so that includes using the CLI to install the chaincode right?
rahulhegde (Mon, 12 Jun 2017 20:10:36 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=eMgK8sfWSQNg562Nk) @jimthematrix
Right.
jimthematrix (Mon, 12 Jun 2017 20:10:38 GMT):
see the CR above that changes how the CLI packages up the chaincode during install
jimthematrix (Mon, 12 Jun 2017 20:11:42 GMT):
that's the change related to this area, but supposedly it should've discovered all the dependencies and include them in the chaincode package during install
jimthematrix (Mon, 12 Jun 2017 20:12:01 GMT):
@greg.haskins ^^^
jimthematrix (Mon, 12 Jun 2017 20:12:25 GMT):
btw this would be better asked in the #fabric-peer-endorser-committer channel
jimthematrix (Mon, 12 Jun 2017 20:14:25 GMT):
and you have re-built the CLI peer binary that does the install right?
rahulhegde (Mon, 12 Jun 2017 20:15:28 GMT):
In our chaincode we use util package (homegrown) and than chaincode in a separate main package. We face the same above issue while instantiating the chaincode on Beta Images (previous Alpha-19th May worked!)
I have just modified the chaincode (example02) so I show u the error w/o concealing the path/our information here.
jimthematrix (Mon, 12 Jun 2017 20:15:44 GMT):
i wonder if this is the case where the external dependency only exists in your vendor folder, but not in the $GOPATH
jimthematrix (Mon, 12 Jun 2017 20:15:58 GMT):
and as such it's missed by the peer CLI
jimthematrix (Mon, 12 Jun 2017 20:17:30 GMT):
seems like @greg.haskins is offline at the moment, he should know for sure
jimthematrix (Mon, 12 Jun 2017 20:18:23 GMT):
in the meanwhile, you can try this: move your external dependencies out of the vendor folder and put them in the system $GOPATH along with the chaincode itself
jimthematrix (Mon, 12 Jun 2017 20:18:40 GMT):
and re-install the chaincode
jimthematrix (Mon, 12 Jun 2017 20:18:40 GMT):
and re-install the chaincode using the CLI
rahulhegde (Mon, 12 Jun 2017 20:19:09 GMT):
I have volume mounted the package (util) to the Peer CLI but this didn't help.
rahulhegde (Mon, 12 Jun 2017 20:26:48 GMT):
Like for the above example
```
- ../../../../shopspring/decimal/:/opt/gopath/src/github.com/shopspring/decimal/
- ../chaincode/go/:/opt/gopath/src/github.com/hyperledger/fabric/examples/chaincode/go
```
rahulhegde (Mon, 12 Jun 2017 20:28:14 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=4zLqJQLGaCa6Eszu8) @jimthematrix - I have done that.
kostas (Mon, 12 Jun 2017 20:59:14 GMT):
Instead of doing `reverify` and restarting all jobs, is there a way to just call for one specific build to run again?
rameshthoomu (Mon, 12 Jun 2017 21:29:20 GMT):
@kostas I can help you on that..
kostas (Mon, 12 Jun 2017 21:29:43 GMT):
I mean is there a command that we can type as a comment in Gerrit to do that?
kostas (Mon, 12 Jun 2017 21:29:57 GMT):
I don't want to be bugging Ramesh all the time.
rameshthoomu (Mon, 12 Jun 2017 21:30:33 GMT):
No I don't see any such option to do that
kostas (Mon, 12 Jun 2017 21:30:54 GMT):
Would be nice to have, wouldn't it?
kostas (Mon, 12 Jun 2017 21:31:04 GMT):
(Not sure how easy it is though to implement.)
rameshthoomu (Mon, 12 Jun 2017 21:34:03 GMT):
Yes it's nice to have.will check and let you knwo
jyellick (Mon, 12 Jun 2017 21:36:56 GMT):
How about instead we simply say `reverify` only restarts failed jobs. And allow a second target like `reverify_all` to retrigger the successful ones
kostas (Mon, 12 Jun 2017 21:37:28 GMT):
^^ I like this idea much better.
rahulhegde (Mon, 12 Jun 2017 22:25:07 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=JFhHFnuTksDbXciXS) @jimthematrix @greg.haskins
It looks like the Install doesn't pack the dependencies (copied logs - http://notes.io/dy1b) i.e. shopstring/decimal
rahulhegde (Mon, 12 Jun 2017 22:25:07 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=JFhHFnuTksDbXciXS) @jimthematrix @greg.haskins
It looks like the Install doesn't pack the first-level dependencies (copied logs - http://notes.io/dy1b) i.e. shopstring/decimal
rahulhegde (Mon, 12 Jun 2017 23:45:07 GMT):
```
developer@rahul-Inspiron-3442:~/workspace/playtime/go-workspace/src/github.com/hyperledger/fabric$ git diff core/chaincode/platforms/golang/platform.go
diff --git a/core/chaincode/platforms/golang/platform.go b/core/chaincode/platforms/golang/platform.go
index cbe905f..eb2107e 100644
--- a/core/chaincode/platforms/golang/platform.go
+++ b/core/chaincode/platforms/golang/platform.go
@@ -244,6 +244,8 @@ func (goPlatform *Platform) GetDeploymentPayload(spec *pb.ChaincodeSpec) ([]byte
deps := make(map[string]bool)
for _, pkg := range imports {
+ deps[pkg] = true
+
_deps, err := listDeps(env, pkg)
if err != nil {
return nil, fmt.Errorf("Error obtaining dependencies for %s: %s", pkg, err)
```
Is this the fix that needs to be added for resolving this issue, I tried and it works for me.
rahulhegde (Mon, 12 Jun 2017 23:45:07 GMT):
```
developer@rahul-Inspiron-3442:~/workspace/playtime/go-workspace/src/github.com/hyperledger/fabric$ git diff core/chaincode/platforms/golang/platform.go
diff --git a/core/chaincode/platforms/golang/platform.go b/core/chaincode/platforms/golang/platform.go
index cbe905f..eb2107e 100644
--- a/core/chaincode/platforms/golang/platform.go
+++ b/core/chaincode/platforms/golang/platform.go
@@ -244,6 +244,8 @@ func (goPlatform *Platform) GetDeploymentPayload(spec *pb.ChaincodeSpec) ([]byte
deps := make(map[string]bool)
for _, pkg := range imports {
+ deps[pkg] = true
+
_deps, err := listDeps(env, pkg)
if err != nil {
return nil, fmt.Errorf("Error obtaining dependencies for %s: %s", pkg, err)
```
Is this the fix that needs to be added for resolving this issue so we allow the first-level dependency to be added to the Deployment Payload, I tried and it works for me.
rahulhegde (Mon, 12 Jun 2017 23:45:07 GMT):
@greg.haskins @jimthematrix
```
developer@rahul-Inspiron-3442:~/workspace/playtime/go-workspace/src/github.com/hyperledger/fabric$ git diff core/chaincode/platforms/golang/platform.go
diff --git a/core/chaincode/platforms/golang/platform.go b/core/chaincode/platforms/golang/platform.go
index cbe905f..eb2107e 100644
--- a/core/chaincode/platforms/golang/platform.go
+++ b/core/chaincode/platforms/golang/platform.go
@@ -244,6 +244,8 @@ func (goPlatform *Platform) GetDeploymentPayload(spec *pb.ChaincodeSpec) ([]byte
deps := make(map[string]bool)
for _, pkg := range imports {
+ deps[pkg] = true
+
_deps, err := listDeps(env, pkg)
if err != nil {
return nil, fmt.Errorf("Error obtaining dependencies for %s: %s", pkg, err)
```
Is this the fix that needs to be added for resolving this issue so we allow the first-level dependency to be added to the Deployment Payload, I tried and it works for me.
rahulhegde (Mon, 12 Jun 2017 23:45:07 GMT):
@greg.haskins @jimthematrix
```
developer@rahul-Inspiron-3442:~/workspace/playtime/go-workspace/src/github.com/hyperledger/fabric$ git diff core/chaincode/platforms/golang/platform.go
diff --git a/core/chaincode/platforms/golang/platform.go b/core/chaincode/platforms/golang/platform.go
index cbe905f..eb2107e 100644
--- a/core/chaincode/platforms/golang/platform.go
+++ b/core/chaincode/platforms/golang/platform.go
@@ -244,6 +244,8 @@ func (goPlatform *Platform) GetDeploymentPayload(spec *pb.ChaincodeSpec) ([]byte
deps := make(map[string]bool)
for _, pkg := range imports {
+ deps[pkg] = true
+
_deps, err := listDeps(env, pkg)
if err != nil {
return nil, fmt.Errorf("Error obtaining dependencies for %s: %s", pkg, err)
```
Is this the fix that needs to be added for resolving this issue so we allow the first-level dependency to be added to the Deployment Payload, I tried and it works for me.
https://jira.hyperledger.org/browse/FAB-4590
rameshthoomu (Tue, 13 Jun 2017 14:42:12 GMT):
All, Docker Images are being published on below commits. **end-to-end (CLI)**, ** end-to-end (NODE) ** and **end-to-end (JAVA)** tests are working as expected on x86.
`===> FABRIC# - f5dbbaf ===> FABRIC CA# - 1424b33 ===> FABRIC SDK JAVA# - 819afce0 ===> FABRIC SDK NODE# - 503c883`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-rc1-snapshot-1424b33
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-rc1-snapshot-f5dbbaf
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-rc1-snapshot-f5dbbaf
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-rc1-snapshot-f5dbbaf
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-rc1-snapshot-f5dbbaf
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-rc1-snapshot-f5dbbaf
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-rc1-snapshot-f5dbbaf
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-rc1-snapshot-f5dbbaf
rameshthoomu/fabric-tools-x86_64:x86_64-1.0.0-rc1-snapshot-f5dbbaf
```
```
s390x docker images are available on below commits
Fabric# 062a03e
Fabric-ca# 1424b33
```
e2e_cli tests are failing on power node (available in sandbox). Working on it
greg.haskins (Tue, 13 Jun 2017 15:05:04 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=RBxGMq6yGmwFJuHLB) @rahulhegde I dont understand what you mean by first-level
rameshthoomu (Tue, 13 Jun 2017 16:21:57 GMT):
Hi @yacovm I see unit-tests are failed in recent merge jobs.. Here is the build reference.. https://jenkins.hyperledger.org/view/fabric/job/fabric-merge-x86_64/2105/console. Is this new issue or already fixed ?
yacovm (Tue, 13 Jun 2017 16:23:14 GMT):
uh oh.
yacovm (Tue, 13 Jun 2017 16:23:24 GMT):
let me look
rameshthoomu (Tue, 13 Jun 2017 16:23:32 GMT):
sure thanks
yacovm (Tue, 13 Jun 2017 16:25:07 GMT):
nope that's something new
yacovm (Tue, 13 Jun 2017 16:25:27 GMT):
@C0rWin ^
yacovm (Tue, 13 Jun 2017 16:25:37 GMT):
hmm but you know
yacovm (Tue, 13 Jun 2017 16:25:43 GMT):
I think since CI is so slow now
yacovm (Tue, 13 Jun 2017 16:25:57 GMT):
I don't think that says anything
yacovm (Tue, 13 Jun 2017 16:26:05 GMT):
let's give it another few tries
yacovm (Tue, 13 Jun 2017 16:26:57 GMT):
if you see another one that fails with `FAIL: TestDataLeakage`
yacovm (Tue, 13 Jun 2017 16:27:02 GMT):
let us know?
rameshthoomu (Tue, 13 Jun 2017 16:27:30 GMT):
one more recent build is running at the moment .. Will let you know if I see any such errors..
rameshthoomu (Tue, 13 Jun 2017 16:27:31 GMT):
thanks
kostas (Tue, 13 Jun 2017 23:35:45 GMT):
@rameshthoomu: Could you please kick off the verify-z and verify-behave jobs on this one https://gerrit.hyperledger.org/r/#/c/10541/? (/cc @manish-sethi )
kostas (Tue, 13 Jun 2017 23:36:14 GMT):
And the verify-behave job on this one? https://gerrit.hyperledger.org/r/#/c/10535/ (/cc @jyellick)
rameshthoomu (Tue, 13 Jun 2017 23:39:24 GMT):
Done
jyellick (Wed, 14 Jun 2017 18:12:43 GMT):
@rameshthoomu Could you rerun the e2e on this one? https://gerrit.hyperledger.org/r/#/c/10471/
rameshthoomu (Wed, 14 Jun 2017 18:14:33 GMT):
Done
yacovm (Thu, 15 Jun 2017 09:37:21 GMT):
@rameshthoomu I think there is a false negative in CI
https://jenkins.hyperledger.org/job/fabric-verify-x86_64/13489/console
https://jenkins.hyperledger.org/job/fabric-verify-z/9139/console
yacovm (Thu, 15 Jun 2017 09:37:37 GMT):
the unit tests passed but the job marked itself as failed
C0rWin (Thu, 15 Jun 2017 11:08:10 GMT):
There is another false negative in CI: https://jenkins.hyperledger.org/job/fabric-verify-x86_64/13490/console
C0rWin (Thu, 15 Jun 2017 11:08:20 GMT):
@rameshthoomu ^^^
rameshthoomu (Thu, 15 Jun 2017 11:09:50 GMT):
@yacovm @C0rWin I see unit-tests are failing but the Post build action step is failing due to some misconfiguration in CI..
rameshthoomu (Thu, 15 Jun 2017 11:09:50 GMT):
@yacovm @C0rWin I see unit-tests are passing but the Post build action step is failing due to some misconfiguration in CI..
rameshthoomu (Thu, 15 Jun 2017 11:11:02 GMT):
@rjones @jwagantall it seems this patch is causing trouble to the CI.. Could you please check https://github.com/hyperledger/ci-management/commit/646eda8bd87a4863d26ae487d1694aecb1affbcd
C0rWin (Thu, 15 Jun 2017 11:15:16 GMT):
@rameshthoomu well, it looks like UT succeeds, not sure I'm following you
rameshthoomu (Thu, 15 Jun 2017 11:16:01 GMT):
yes unit-tests are passed but post build step is failing.. so overall build is failed..
rameshthoomu (Thu, 15 Jun 2017 11:23:58 GMT):
@rjones I don't see `lf-infra-publish` macro name in macro files.. Is this mapped in the global settings?
cbf (Thu, 15 Jun 2017 11:39:10 GMT):
06:13:20 ---> create-netrc.sh
06:13:20 /tmp/hudson2264011273872495219.sh: line 20: xmlstarlet: command not found
06:13:20 Build step 'Execute a set of scripts' marked build as failure
06:13:20 Archiving artifacts
06:13:24 Recording fingerprints
06:13:25 Finished: FAILURE
cbf (Thu, 15 Jun 2017 11:39:20 GMT):
this seems across the board
cbf (Thu, 15 Jun 2017 11:39:32 GMT):
I am also not finding the logs in nexus, FWIW
cbf (Thu, 15 Jun 2017 11:39:49 GMT):
https://logs.hyperledger.org/jobbuilder/vex-yul-hyp-jenkins-1/fabric-merge-z/1645
cbf (Thu, 15 Jun 2017 11:42:21 GMT):
I would also note that the merge CI for this CR failed https://gerrit.hyperledger.org/r/#/c/10543/
cbf (Thu, 15 Jun 2017 11:42:26 GMT):
and the logs are missing
chrism28 (Thu, 15 Jun 2017 12:02:39 GMT):
Has joined the channel.
jwagantall (Thu, 15 Jun 2017 13:45:26 GMT):
@cbf @rameshthoomu we are working on fixing that failure and installing those packages....the job should be just failing the logs part....but everything before that should be fine...
jwagantall (Thu, 15 Jun 2017 13:46:13 GMT):
Im working on it....
rameshthoomu (Thu, 15 Jun 2017 13:48:44 GMT):
@jwagantall thanks.. Could you please update this bug once done https://jira.hyperledger.org/browse/FAB-4746
rameshthoomu (Thu, 15 Jun 2017 13:50:37 GMT):
Once the issue is fixed we have to re-trigger all the effected builds.. Ry did this earlier.. pls check with him..
cbf (Thu, 15 Jun 2017 14:00:46 GMT):
@rameshthoomu @jwagantall thanks
rjones (Thu, 15 Jun 2017 14:30:10 GMT):
@rameshthoomu I'll retrigger the builds once the new packer image is up
rameshthoomu (Thu, 15 Jun 2017 14:30:27 GMT):
Thanks @rjones
C0rWin (Thu, 15 Jun 2017 14:36:09 GMT):
now, there is no CI feedback on gerrit CR's (re: https://gerrit.hyperledger.org/r/#/c/10635)
rjones (Thu, 15 Jun 2017 14:37:05 GMT):
@C0rWin: incorrect. Patch 2's CI has not completed.
rjones (Thu, 15 Jun 2017 14:37:05 GMT):
@C0rWin: incorrect. Patch 2
C0rWin (Thu, 15 Jun 2017 14:38:05 GMT):
@rjones my bad, missed it
C0rWin (Thu, 15 Jun 2017 14:38:38 GMT):
will wait until it's done
rameshthoomu (Thu, 15 Jun 2017 14:47:24 GMT):
@jwagantall see this also
```
00:13:30.023 cp: cannot stat '/var/log/sysstat/*': No such file or directory
00:13:30.042 provisioning config files...
```
jwagantall (Thu, 15 Jun 2017 14:47:52 GMT):
can you link me the job?
rameshthoomu (Thu, 15 Jun 2017 14:50:45 GMT):
all jobs https://jenkins.hyperledger.org/view/fabric/job/fabric-verify-x86_64/13499/console
jwagantall (Thu, 15 Jun 2017 15:11:11 GMT):
i wonder if that is a problem with also the logs not being generated properly.. we just have installed the packages we need.. @rjones is helping me testing it
rjones (Thu, 15 Jun 2017 15:11:27 GMT):
zomm zoom
firas.qutishat (Thu, 15 Jun 2017 15:28:51 GMT):
Has joined the channel.
kostas (Thu, 15 Jun 2017 15:37:40 GMT):
Getting failures on all jobs: https://gerrit.hyperledger.org/r/#/c/10609/
rameshthoomu (Thu, 15 Jun 2017 15:38:53 GMT):
@kostas We are working on it. Will give you an update soon
rameshthoomu (Thu, 15 Jun 2017 15:40:46 GMT):
@jwagantall We have installed `xmlstarlet facter` in all z nodes.. @harrijk installed sysstat package and triggered build.
jwagantall (Thu, 15 Jun 2017 15:41:08 GMT):
yea.., we are still seeing an issue.. Ry and I are looking into it..
jimthematrix (Thu, 15 Jun 2017 15:46:12 GMT):
same for node SDK verify: https://jenkins.hyperledger.org/job/fabric-sdk-node-verify-x86_64/1183/consoleFull
jwagantall (Thu, 15 Jun 2017 16:09:04 GMT):
looks like this should be fixed... let me re-try few jobs
jwagantall (Thu, 15 Jun 2017 16:10:00 GMT):
ci management passed.. trying fabric
jwagantall (Thu, 15 Jun 2017 16:10:01 GMT):
https://jenkins.hyperledger.org/view/fabric-sdk-node/job/fabric-sdk-node-verify-x86_64/1184/
jwagantall (Thu, 15 Jun 2017 16:26:00 GMT):
i think we are good to go now..
jwagantall (Thu, 15 Jun 2017 16:26:18 GMT):
ill retrigger any jobs i can find
rjones (Thu, 15 Jun 2017 16:27:21 GMT):
@jwagantall I can retrigger them if you like
jwagantall (Thu, 15 Jun 2017 16:27:42 GMT):
oh.. thanks so much Ry!.. sure please... i need to switch gears to another task now..
kostas (Thu, 15 Jun 2017 19:36:29 GMT):
Newbie question: Am I supposed to remove "Hyperledger Jobbuilder" from the list of reviewers every time I upload a new patchset, or is there a way to permanently let them know that they're not welcome in this changeset?
kostas (Thu, 15 Jun 2017 19:36:29 GMT):
Basic question: Am I supposed to remove "Hyperledger Jobbuilder" from the list of reviewers every time I upload a new patchset, or is there a way to permanently let them know that they're not welcome in this changeset?
rjones (Thu, 15 Jun 2017 20:35:32 GMT):
@kostas they will add themselves every new patch. What is the issue you're trying to solve?
kostas (Thu, 15 Jun 2017 20:35:52 GMT):
I'm revising a doc, CI is not needed.
kostas (Thu, 15 Jun 2017 20:36:03 GMT):
So I have to remove it manually every time.
rjones (Thu, 15 Jun 2017 20:36:07 GMT):
So ignore it
rjones (Thu, 15 Jun 2017 20:36:23 GMT):
You don't have to do anything
kostas (Thu, 15 Jun 2017 20:36:41 GMT):
I guess I could do that as well, you're right.
rjones (Thu, 15 Jun 2017 20:37:17 GMT):
We used to use a ci skip plugin, but it was causing problems
jyellick (Fri, 16 Jun 2017 02:43:00 GMT):
@rameshthoomu Could you please re-run Z on https://gerrit.hyperledger.org/r/#/c/10639/ ?
rameshthoomu (Fri, 16 Jun 2017 02:44:34 GMT):
Done
rameshthoomu (Fri, 16 Jun 2017 13:21:40 GMT):
All, Docker Images are being published on below commits. **end-to-end (CLI)**, ** end-to-end (NODE) ** and **end-to-end (JAVA)** tests are working as expected on x86 and s390x.
`===> FABRIC# - 04ff59b ===> FABRIC CA# - 5180ce7 ===> FABRIC SDK JAVA# - ff99ffa ===> FABRIC SDK NODE# - 8fb2968`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-rc1-snapshot-5180ce7
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-rc1-snapshot-04ff59b
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-rc1-snapshot-04ff59b
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-rc1-snapshot-04ff59b
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-rc1-snapshot-04ff59b
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-rc1-snapshot-04ff59b
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-rc1-snapshot-04ff59b
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-rc1-snapshot-04ff59b
rameshthoomu/fabric-tools-x86_64:x86_64-1.0.0-rc1-snapshot-04ff59b
```
Docker images for "System z " are also available by modifying the last component in the repository based on the desired architecture.
```
System z = s390x
```
e2e_cli tests are failing on power node (available in sandbox). https://gerrit.hyperledger.org/r/#/c/10573/
rameshthoomu (Fri, 16 Jun 2017 19:56:47 GMT):
@harsha Could you please rebase this patch https://gerrit.hyperledger.org/r/#/c/10573/ It seems these failures are fixed in recent patches..
harsha (Sat, 17 Jun 2017 03:37:56 GMT):
@rameshthoomu Rebased https://gerrit.hyperledger.org/r/#/c/10573/ now.
sfukazu (Mon, 19 Jun 2017 06:33:27 GMT):
Has joined the channel.
rameshthoomu (Mon, 19 Jun 2017 13:21:43 GMT):
All, Docker Images are being published on below commits. **end-to-end (CLI)**, ** end-to-end (NODE) ** and **end-to-end (JAVA)** tests are working as expected on x86 and s390x.
`===> FABRIC# - f20846c ===> FABRIC CA# - 20b6552 ===> FABRIC SDK JAVA# - 7c87f20 ===> FABRIC SDK NODE# - 9f9659f`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-rc1-snapshot-20b6552
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-rc1-snapshot-f20846c
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-rc1-snapshot-f20846c
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-rc1-snapshot-f20846c
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-rc1-snapshot-f20846c
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-rc1-snapshot-f20846c
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-rc1-snapshot-f20846c
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-rc1-snapshot-f20846c
rameshthoomu/fabric-tools-x86_64:x86_64-1.0.0-rc1-snapshot-f20846c
```
Docker images for "System z " are also available by modifying the last component in the repository based on the desired architecture.
```
System z = s390x
```
e2e_cli tests are failing on power node (available in sandbox). https://gerrit.hyperledger.org/r/#/c/10573/
rameshthoomu (Mon, 19 Jun 2017 13:21:43 GMT):
All, Docker Images are being published on below commits. **end-to-end (CLI)**, ** end-to-end (NODE) ** and **end-to-end (JAVA)** tests are working as expected on x86, s390x and ppc64le
`===> FABRIC# - f20846c ===> FABRIC CA# - 20b6552 ===> FABRIC SDK JAVA# - 7c87f20 ===> FABRIC SDK NODE# - 9f9659f`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-rc1-snapshot-20b6552
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-rc1-snapshot-f20846c
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-rc1-snapshot-f20846c
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-rc1-snapshot-f20846c
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-rc1-snapshot-f20846c
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-rc1-snapshot-f20846c
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-rc1-snapshot-f20846c
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-rc1-snapshot-f20846c
rameshthoomu/fabric-tools-x86_64:x86_64-1.0.0-rc1-snapshot-f20846c
```
Docker images for "System z " are also available by modifying the last component in the repository based on the desired architecture.
```
System z = s390x
Power = ppc64le
```
rameshthoomu (Mon, 19 Jun 2017 13:21:43 GMT):
All, Docker Images are being published on below commits. **end-to-end (CLI)**, ** end-to-end (NODE) ** and **end-to-end (JAVA)** tests are working as expected on x86 and s390x.
`===> FABRIC# - f20846c ===> FABRIC CA# - 20b6552 ===> FABRIC SDK JAVA# - 7c87f20 ===> FABRIC SDK NODE# - 9f9659f`
```zz
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-rc1-snapshot-20b6552
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-rc1-snapshot-f20846c
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-rc1-snapshot-f20846c
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-rc1-snapshot-f20846c
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-rc1-snapshot-f20846c
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-rc1-snapshot-f20846c
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-rc1-snapshot-f20846c
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-rc1-snapshot-f20846c
rameshthoomu/fabric-tools-x86_64:x86_64-1.0.0-rc1-snapshot-f20846c
```
Docker images for "System z " are also available by modifying the last component in the repository based on the desired architecture.
```
System z = s390x
```
e2e_cli tests are failing on power node (available in sandbox). https://gerrit.hyperledger.org/r/#/c/10573/
kostas (Tue, 20 Jun 2017 04:11:38 GMT):
If you spot any CI failures related to `kafka` unit tests can you please let us know? (These should be taken care of now thanks to FAB-4537 and @sanchezl's work.) /cc @jyellick @yacovm @C0rWin
kostas (Tue, 20 Jun 2017 04:11:38 GMT):
If you spot any new CI failures related to `kafka` unit tests can you please let us know? (These should be taken care of now thanks to FAB-4537 and @sanchezl's work.) /cc @jyellick @yacovm @C0rWin
dongqi (Tue, 20 Jun 2017 08:34:12 GMT):
Has joined the channel.
rameshthoomu (Tue, 20 Jun 2017 13:43:11 GMT):
All, Docker Images are being published on below commits. **end-to-end (CLI)**, ** end-to-end (NODE) ** and **end-to-end (JAVA)** tests are working as expected on x86, s390x and ppc64le
`===> FABRIC# - 735be85 ===> FABRIC CA# - 82fad13 ===> FABRIC SDK JAVA# - fc1d7ce ===> FABRIC SDK NODE# - 9b8c6a0`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-rc1-snapshot-82fad13
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-rc1-snapshot-735be85
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-rc1-snapshot-735be85
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-rc1-snapshot-735be85
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-rc1-snapshot-735be85
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-rc1-snapshot-735be85
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-rc1-snapshot-735be85
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-rc1-snapshot-735be85
rameshthoomu/fabric-tools-x86_64:x86_64-1.0.0-rc1-snapshot-735be85
```
Docker images for "System z & Power" are also available by modifying the last component in the repository based on the desired architecture.
```
System z = s390x
Power = ppc64le
```
e2e_cli tests are failing on power node (available in sandbox). https://gerrit.hyperledger.org/r/#/c/10573/
rameshthoomu (Tue, 20 Jun 2017 13:43:11 GMT):
All, Docker Images are being published on below commits. **end-to-end (CLI)**, ** end-to-end (NODE) ** and **end-to-end (JAVA)** tests are working as expected on x86, s390x and ppc64le
`===> FABRIC# - 735be85 ===> FABRIC CA# - 82fad13 ===> FABRIC SDK JAVA# - fc1d7ce ===> FABRIC SDK NODE# - 9b8c6a0`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-rc1-snapshot-82fad13
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-rc1-snapshot-735be85
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-rc1-snapshot-735be85
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-rc1-snapshot-735be85
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-rc1-snapshot-735be85
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-rc1-snapshot-735be85
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-rc1-snapshot-735be85
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-rc1-snapshot-735be85
rameshthoomu/fabric-tools-x86_64:x86_64-1.0.0-rc1-snapshot-735be85
```
Docker images for "System z & Power" are also available by modifying the last component in the repository based on the desired architecture.
```
System z = s390x
Power = ppc64le
```
bsmita (Tue, 20 Jun 2017 14:43:20 GMT):
@rameshthoomu - The above comment, images are published, but e2e_cli tests failed ? I thought images would be published once e2e_cli tests pass?
rameshthoomu (Tue, 20 Jun 2017 14:43:48 GMT):
updated message..
bsmita (Tue, 20 Jun 2017 14:43:53 GMT):
Thank you!
rameshthoomu (Tue, 20 Jun 2017 14:45:32 GMT):
today it passed.. but observed e2e_cli tests are failing intermittently.. This patch https://gerrit.hyperledger.org/r/#/c/10573/ should fix these intermittent failures..
bsmita (Tue, 20 Jun 2017 14:46:49 GMT):
We are still working on the patch...hope it will be integrated soon
rameshthoomu (Wed, 21 Jun 2017 13:28:30 GMT):
All, Docker Images are being published on below commits. **end-to-end (CLI)**, ** end-to-end (NODE) ** and **end-to-end (JAVA)** tests are working as expected on x86, s390x and ppc64le
`===> FABRIC# - 3bc937e ===> FABRIC CA# - ba9c7a8 ===> FABRIC SDK JAVA# - 6382c27 ===> FABRIC SDK NODE# - 7cf6176`
```
rameshthoomu/fabric-ca-x86_64:x86_64-1.0.0-rc1-snapshot-ba9c7a8
rameshthoomu/fabric-couchdb-x86_64:x86_64-1.0.0-rc1-snapshot-3bc937e
rameshthoomu/fabric-kafka-x86_64:x86_64-1.0.0-rc1-snapshot-3bc937e
rameshthoomu/fabric-zookeeper-x86_64:x86_64-1.0.0-rc1-snapshot-3bc937e
rameshthoomu/fabric-orderer-x86_64:x86_64-1.0.0-rc1-snapshot-3bc937e
rameshthoomu/fabric-peer-x86_64:x86_64-1.0.0-rc1-snapshot-3bc937e
rameshthoomu/fabric-javaenv-x86_64:x86_64-1.0.0-rc1-snapshot-3bc937e
rameshthoomu/fabric-ccenv-x86_64:x86_64-1.0.0-rc1-snapshot-3bc937e
rameshthoomu/fabric-tools-x86_64:x86_64-1.0.0-rc1-snapshot-3bc937e
```
Docker images for "System z & Power" are also available by modifying the last component in the repository based on the desired architecture.
```
System z = s390x
Power = ppc64le
```
hcw (Wed, 21 Jun 2017 17:41:42 GMT):
Has joined the channel.
rameshthoomu (Thu, 22 Jun 2017 13:32:04 GMT):
e2e CI jobs are not triggered in sandbox.. Working on it..
rameshthoomu (Thu, 22 Jun 2017 13:32:13 GMT):
Will update the status once done
rameshthoomu (Fri, 23 Jun 2017 13:41:34 GMT):
All, Docker Images are being published on below commits. *end-to-end (CLI)*, * end-to-end (NODE) * and *end-to-end (JAVA)* tests are working as expected on x86 and s390x
`===> FABRIC# - 2929aee ===> FABRIC CA# - b0bc2c0 ===> FABRIC SDK JAVA# - 6f75a13===> FABRIC SDK NODE# - e90ba1e`
Re-triggered e2e power job..
Unable to push docker images Credentials are removed from sandbox environment. Working on this now.
rameshthoomu (Fri, 23 Jun 2017 13:41:34 GMT):
All, Docker Images are being published on below commits. *end-to-end (CLI)*, * end-to-end (NODE) * and *end-to-end (JAVA)* tests are working as expected on x86 and s390x
`===> FABRIC# - 2929aee ===> FABRIC CA# - b0bc2c0 ===> FABRIC SDK JAVA# - 6f75a13===> FABRIC SDK NODE# - e90ba1e`
Re-triggered e2e power job..
Unable to push docker images as the Credentials are removed from sandbox environment. Working on this now.
ThePleasurable (Sat, 24 Jun 2017 12:27:20 GMT):
Has joined the channel.
jun (Tue, 27 Jun 2017 00:41:49 GMT):
Has joined the channel.
rezamt (Wed, 28 Jun 2017 07:08:02 GMT):
Has joined the channel.
pvrbharg (Mon, 03 Jul 2017 14:11:45 GMT):
Has joined the channel.
JonathanLevi (Wed, 05 Jul 2017 10:24:43 GMT):
@rameshthoomu Thank you.
rameshthoomu (Wed, 05 Jul 2017 19:02:10 GMT):
@jtclark created Jira for goAST security tests are failed https://jira.hyperledger.org/browse/FAB-5187
rameshthoomu (Wed, 05 Jul 2017 19:02:10 GMT):
@jtclark I have created Bug in Jira for goAST security test failures.https://jira.hyperledger.org/browse/FAB-5187
rameshthoomu (Wed, 05 Jul 2017 19:02:10 GMT):
@jtclark I have created Bug in Jira for goAST security test failures. https://jira.hyperledger.org/browse/FAB-5187
rameshthoomu (Wed, 05 Jul 2017 19:02:10 GMT):
@jtclark @ashutosh_kumar I have created Bug in Jira for goAST security test failures. https://jira.hyperledger.org/browse/FAB-5187
bobbiejc (Fri, 07 Jul 2017 15:06:20 GMT):
Has joined the channel.
bobbiejc (Fri, 07 Jul 2017 15:15:59 GMT):
wondering if anyone has thought for CI of chaincode, when you change chaincode, how do you know where to reinstall / reinstantiate the chaincode
rjones (Fri, 07 Jul 2017 17:13:44 GMT):
@bobbiejc that sounds like an excellent idea! nobody I know of is working on that
bobbiejc (Fri, 07 Jul 2017 17:14:14 GMT):
i was looking through this: http://hyperledger-fabric.readthedocs.io/en/latest/chaincode4noah.html
bobbiejc (Fri, 07 Jul 2017 17:14:49 GMT):
it seems to start to address some of topics, but not for CI/CD
bobbiejc (Fri, 07 Jul 2017 17:15:59 GMT):
@rjones can you point me to fabric devs who might shed insight into best practices?
rjones (Fri, 07 Jul 2017 17:17:18 GMT):
@bobbiejc you might ask in #fabric ? you could also look at the ci-management repo /jjb/ to see how to add to the CI system if you really wanted
bobbiejc (Fri, 07 Jul 2017 17:18:24 GMT):
so saw that, but this would be outside of standing up and developing fabric
bobbiejc (Fri, 07 Jul 2017 17:18:38 GMT):
this is for a consumer of fabric, who may never touch the base...
rjones (Fri, 07 Jul 2017 17:55:34 GMT):
sure, what I'm saying is if you're trying to find fabric consumers, that might be the place to look? Another option would be to send mail to one of the mailing lists.
rameshthoomu (Mon, 10 Jul 2017 20:48:35 GMT):
@ashutosh_kumar Could you please add your comments in JIRA# 5187
ashutosh_kumar (Mon, 10 Jul 2017 20:48:35 GMT):
Has joined the channel.
ashutosh_kumar (Mon, 10 Jul 2017 20:49:06 GMT):
ok.
guoger (Tue, 11 Jul 2017 12:19:30 GMT):
are tests run as root in CI? thx
rameshthoomu (Tue, 11 Jul 2017 12:20:54 GMT):
@guoger as jenkins user
rameshthoomu (Tue, 11 Jul 2017 12:21:02 GMT):
did you see any issue?
guoger (Tue, 11 Jul 2017 12:22:55 GMT):
I'm trying the test flow:
1. chmod a temp file to 0200
2. attempt to read the file
3. see it fails
However the file is still read without error.
guoger (Tue, 11 Jul 2017 12:22:59 GMT):
@rameshthoomu ^^
guoger (Tue, 11 Jul 2017 12:24:05 GMT):
basically I'm trying to debug this test: https://github.com/hyperledger/fabric/blob/master/orderer/ledger/json/factory_test.go#L51-L62
rameshthoomu (Tue, 11 Jul 2017 12:27:20 GMT):
Ok will check
guoger (Tue, 11 Jul 2017 12:30:00 GMT):
great, thx!
Andy Zhang (Thu, 13 Jul 2017 05:12:10 GMT):
Has joined the channel.
guoger (Thu, 13 Jul 2017 13:16:35 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=dCfRvmkvMmdb4wtyS) @rameshthoomu hi, do you have some time to take a look at this? thanks a lot!
ashutosh_kumar (Thu, 13 Jul 2017 15:10:52 GMT):
@rameshthoomu , I updated my comments on 5187.
rameshthoomu (Thu, 13 Jul 2017 15:13:15 GMT):
ok
rameshthoomu (Thu, 13 Jul 2017 15:13:19 GMT):
Thank you
jyellick (Thu, 13 Jul 2017 18:17:20 GMT):
@rjones @rameshthoomu Not sure this is the right place to report it, but both JIRA and Gerrit seem to be down to me, do we know if is this being worked on?
rameshthoomu (Thu, 13 Jul 2017 18:18:02 GMT):
@jyellick this could be the reason https://status.linuxfoundation.org/incidents/tpp1f2f3dyxw
jyellick (Thu, 13 Jul 2017 18:18:35 GMT):
Ah, thanks @rameshthoomu !
rameshthoomu (Thu, 13 Jul 2017 19:35:08 GMT):
@guoger tested your patch in sandbox (CI) and it worked as expected.
rameshthoomu (Thu, 13 Jul 2017 19:35:09 GMT):
https://jenkins.hyperledger.org/sandbox/job/chmodtest/4/console
rameshthoomu (Thu, 13 Jul 2017 19:35:09 GMT):
https://jenkins.hyperledger.org/sandbox/job/chmodtest/4/console (x86)
https://jenkins.hyperledger.org/sandbox/job/chmodtest/3/console (s390x)
rameshthoomu (Thu, 13 Jul 2017 19:36:39 GMT):
I have executed these commands
```
make peer
cd $GOPATH/src/github.com/hyperledger/fabric/orderer/ledger/json
go test -ldflags "-X github.com/hyperledger/fabric/common/metadata.Version=1.0.1-snapshot-e50ca0c -X github.com/hyperledger/fabric/common/metadata.BaseVersion=0.3.1 -X github.com/hyperledger/fabric/common/metadata.BaseDockerLabel=org.hyperledger.fabric -X github.com/hyperledger/fabric/common/metadata.DockerNamespace=hyperledger -X github.com/hyperledger/fabric/common/metadata.BaseDockerNamespace=hyperledger"
```
guoger (Fri, 14 Jul 2017 02:26:43 GMT):
@rameshthoomu I see, but production CI still fails? should I trigger another reverify? do you consider it a bug in CI?
guoger (Fri, 14 Jul 2017 02:26:57 GMT):
and thanks for you effort
rameshthoomu (Fri, 14 Jul 2017 02:27:33 GMT):
Could you pls rebase your patch ?
rameshthoomu (Fri, 14 Jul 2017 02:27:47 GMT):
Will see.. both environments are same..
rameshthoomu (Fri, 14 Jul 2017 02:28:52 GMT):
But the way I ran is different.. sandbox I have tested your patch on native machone
rameshthoomu (Fri, 14 Jul 2017 02:29:36 GMT):
Where as in production CI, we run these tests in a docker container
IvanPopkov (Fri, 14 Jul 2017 10:21:47 GMT):
Has joined the channel.
jyellick (Fri, 14 Jul 2017 13:40:04 GMT):
@rameshthoomu Some time ago, @kostas had asked you about the possibility of allowing reverify to specify a particular job to re-run (or better yet, automatically only re-run failed jobs) and you had said you would look into it. Maybe I just missed the reply, but was wondering if you had had a chance to do this? [ ](https://chat.hyperledger.org/channel/fabric-ci?msg=CDeSm7gFMdHMqDg9H)
rameshthoomu (Fri, 14 Jul 2017 13:46:36 GMT):
no @jyellick.. Will check and give you an update here next week
rjones (Fri, 14 Jul 2017 15:18:44 GMT):
@jyellick @rameshthoomu AFAIK there is no version of the Jenkins Gerrit plugin that does partial triggers.
rjones (Fri, 14 Jul 2017 15:18:44 GMT):
@jyellick @rameshthoomu AFAIK there is no version of the Gerrit `recheck` plugin that does partial triggers
rjones (Fri, 14 Jul 2017 15:24:24 GMT):
@jyellick @rameshthoomu here is the plugin: https://plugins.jenkins.io/gerrit-trigger
jyellick (Fri, 14 Jul 2017 15:33:15 GMT):
Thanks @rjones not sure if we think this is worth opening an enhancement request for? (or what the likelihood of someone implementing it would be). Obviously the 'right' answer is to make our assorted jobs more stable, but especially as the number of jobs has grown, the false positive problem has gotten worse
rjones (Fri, 14 Jul 2017 15:34:34 GMT):
@jyellick no argument from me. I am personally of the opinion that flaky tests get disabled and a bug filed
guoger (Sat, 15 Jul 2017 10:00:40 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=bfjJmcav2SKA5Pe9C) @rameshthoomu Is the container run as user other than uid 0?
rameshthoomu (Sat, 15 Jul 2017 11:32:31 GMT):
I am getting the same error in my local machine when I run "make unittests"
rameshthoomu (Sat, 15 Jul 2017 11:32:53 GMT):
It's not an issue with CI
pvrbharg (Mon, 17 Jul 2017 01:21:47 GMT):
@dongming Hello, can you please point me to recent (RC1) run reports of benchmark or performance/regression/stress test long run reports? I am an ibmer looking for some understanding of these run reports for my engagement/customer. My ibm email is bvperepa@us.ibm.com. Thanks.
jtrayfield (Mon, 17 Jul 2017 14:32:36 GMT):
I'm having trouble with the v1.0 version of fabric:
2017-07-17 14:18:01.374 UTC [main] main -> ERRO 001 Cannot run peer because error when setting up MSP from directory /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/peerOrganizations/oats.ibm.com/users/Admin@oats.ibm.com/msp: err admin 0 is invalid, validation error Could not obtain certification chain, err A CA certificate cannot be used directly by this MSP
scottz (Mon, 17 Jul 2017 16:00:25 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=4sHbYj7gYCDxBM2XP) @pvrbharg Refer to https://wiki.hyperledger.org/projects/fabric/quality_assurance?&#resources . (Similar questions in future may get quicker and better responses if submitted to fabric-quality)
greg.haskins (Mon, 17 Jul 2017 19:34:31 GMT):
@rameshthoomu do we now have a nexus infra suitable for hosting arbitrary downloads that are permanently stable?
rameshthoomu (Mon, 17 Jul 2017 19:35:29 GMT):
yes @greg.haskins.. We are using nexus to download fabric-binaries and jar jar files..
greg.haskins (Mon, 17 Jul 2017 19:35:30 GMT):
I need to make the "v1.0.0" release of chaintool..we have historically used GH releases (https://github.com/hyperledger/fabric-chaintool/releases)
greg.haskins (Mon, 17 Jul 2017 19:35:42 GMT):
but if nexus is available, we could use that going forward
greg.haskins (Mon, 17 Jul 2017 19:36:20 GMT):
I would need your help coming up with the "-release" job for chaintool which could respond to the push of a new tag, build the artifact, and push it to nexus
rameshthoomu (Mon, 17 Jul 2017 19:37:07 GMT):
sure.. Will do. What type (jar/binary) of artificat it is?
greg.haskins (Mon, 17 Jul 2017 19:37:30 GMT):
you can think of it as an opaque binary
rameshthoomu (Mon, 17 Jul 2017 19:37:30 GMT):
do you want me to check the fabric-chaintools repository for the steps to generate?
greg.haskins (Mon, 17 Jul 2017 19:37:42 GMT):
i can give you a run down
greg.haskins (Mon, 17 Jul 2017 19:37:47 GMT):
ill switch to PM
rameshthoomu (Mon, 17 Jul 2017 19:37:53 GMT):
ok
pvrbharg (Tue, 18 Jul 2017 00:23:32 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=L5hbqiuAKo6ESzxbp) @scottz Thank you Scott for your reply providing me answer and guidance for future. I would get on fabric-quality. Thanks.
kostas (Fri, 21 Jul 2017 13:24:33 GMT):
Hi @rameshthoomu, any updates on this one: https://chat.hyperledger.org/channel/fabric-ci?msg=vMneb9jS2ZXYEdSTu
rameshthoomu (Fri, 21 Jul 2017 13:26:28 GMT):
@kostas still working on it..
rameshthoomu (Fri, 21 Jul 2017 13:28:47 GMT):
I don't see any options as such to trigger partially in gerrit trigger plugin..
rameshthoomu (Fri, 21 Jul 2017 13:29:21 GMT):
Will let you know the update
rjones (Fri, 21 Jul 2017 14:38:05 GMT):
@kostas you would need a change in the gerrit plugin. I don't see an open issue in the gerrit issue tracker for it
lehors (Fri, 21 Jul 2017 23:36:39 GMT):
@rameshthoomu I'm at a loss as to understand why all my verification builds fail
lehors (Fri, 21 Jul 2017 23:36:52 GMT):
even a simple change to the doc fails the verification process: https://jenkins.hyperledger.org/job/fabric-verify-x86_64/14337/console
lehors (Fri, 21 Jul 2017 23:37:53 GMT):
this is for: https://gerrit.hyperledger.org/r/#/c/11821/
lehors (Mon, 24 Jul 2017 17:49:02 GMT):
@here any updates on the fabric-ca builds?
lehors (Mon, 24 Jul 2017 17:49:38 GMT):
after desperately trying to reverify a couple of my changes this weekend I eventually realized this was silly because the builds weren't working for anyone
lehors (Mon, 24 Jul 2017 17:50:07 GMT):
I saw @rameshthoomu reported during the scrum that this is being worked on
rameshthoomu (Mon, 24 Jul 2017 17:52:38 GMT):
@lehors I have re-triggered your jobs over weekend and it worked as expected,,, These builds are from fabric repository...
lehors (Mon, 24 Jul 2017 17:53:09 GMT):
ok, I have some on fabric-ca, and from what I can tell the build now works?
lehors (Mon, 24 Jul 2017 17:53:14 GMT):
I just restarted one to see
rameshthoomu (Mon, 24 Jul 2017 17:53:27 GMT):
@rennman asked @rjones in #ci-pipeline channel about ssh access to x86_64 build machines..
rennman (Mon, 24 Jul 2017 17:53:27 GMT):
Has joined the channel.
rameshthoomu (Mon, 24 Jul 2017 17:54:07 GMT):
Could you please provide your PS.. Will check if the builds are failing with mysql access
rameshthoomu (Mon, 24 Jul 2017 17:54:07 GMT):
Could you please provide your fabric-ca PS.. Will check if the builds are failing with mysql access
lehors (Mon, 24 Jul 2017 18:03:27 GMT):
let me see how the build I restarted goes
lehors (Mon, 24 Jul 2017 18:03:42 GMT):
I'll let you know if there is a problem, no need to worry about it for now
lehors (Mon, 24 Jul 2017 18:03:50 GMT):
thanks
rameshthoomu (Mon, 24 Jul 2017 18:09:26 GMT):
Sure @lehors thanks
simsc (Tue, 25 Jul 2017 12:17:25 GMT):
hi
simsc (Tue, 25 Jul 2017 12:17:28 GMT):
you there
simsc (Tue, 25 Jul 2017 13:24:10 GMT):
oops wrong window
jtclark (Tue, 25 Jul 2017 18:07:20 GMT):
hi all
jtclark (Tue, 25 Jul 2017 18:07:55 GMT):
can either of you @here give a review to https://gerrit.hyperledger.org/r/#/c/11687/ ?
jtclark (Tue, 25 Jul 2017 18:08:27 GMT):
As asked, I've testing this locally, as well as in the Jenkins sandbox per @rameshthoomu
jtclark (Tue, 25 Jul 2017 18:08:27 GMT):
As asked, I've tested this locally, as well as in the Jenkins sandbox per @rameshthoomu
jtclark (Tue, 25 Jul 2017 18:09:11 GMT):
the output from running the FVT tests as part of the fabric-ca-verify-s390x job looks correct.
rjones (Tue, 25 Jul 2017 18:13:00 GMT):
are you asking me for a review, or someone else? the at here is a little broad :)
jtclark (Tue, 25 Jul 2017 18:17:12 GMT):
anyone who would like to review can review.
jtclark (Tue, 25 Jul 2017 18:17:32 GMT):
so, I guess I am asking you :-)
jtclark (Tue, 25 Jul 2017 18:19:53 GMT):
@lehors just noticed that the FVT tests for fabric-ca are specific to the 390x platform?
jtclark (Tue, 25 Jul 2017 18:20:22 GMT):
now that I think about it, I assume it's for testing purposes
jtclark (Tue, 25 Jul 2017 18:20:49 GMT):
once the patch is merged, it would be available across all the platforms.
rameshthoomu (Tue, 25 Jul 2017 18:36:22 GMT):
@jtclark rebase your patch please.. I see mysql server errors
jtclark (Tue, 25 Jul 2017 19:23:44 GMT):
@rameshthoomu +1
jtclark (Tue, 25 Jul 2017 19:27:53 GMT):
test is running again
jtclark (Tue, 25 Jul 2017 20:25:34 GMT):
@rameshthoomu take a look at the test results. look clean?
jtclark (Tue, 25 Jul 2017 21:11:36 GMT):
ok I've another issue. working on the PTE patch, @rameshthoomu. I'm seeing this when I run the `make docker` step for setting up PTE locally:
jtclark (Tue, 25 Jul 2017 21:11:40 GMT):
```
jtclark (Tue, 25 Jul 2017 21:11:46 GMT):
```jasonclark INSPECTAH ~ go … github.com hyperledger fabric release $ make docker
find: /src/github.com/hyperledger/fabric/core/chaincode/shim: No such file or directory
Building build/docker/bin/peer
(cd sampleconfig && tar -jc *) > build/sampleconfig.tar.bz2
mkdir -p build/image/peer/payload
cp build/docker/bin/peer build/sampleconfig.tar.bz2 build/image/peer/payload
make[1]: Entering directory '/opt/gopath/src/github.com/hyperledger/fabric/gotools'
Building github.com/golang/lint/golint -> golint
make[1]: Leaving directory '/opt/gopath/src/github.com/hyperledger/fabric/gotools'
make[1]: Entering directory '/opt/gopath/src/github.com/hyperledger/fabric/gotools'
Building github.com/kardianos/govendor -> govendor
make[1]: Leaving directory '/opt/gopath/src/github.com/hyperledger/fabric/gotools'
make[1]: Entering directory '/opt/gopath/src/github.com/hyperledger/fabric/gotools'
Building golang.org/x/tools/cmd/goimports -> goimports
make[1]: Leaving directory '/opt/gopath/src/github.com/hyperledger/fabric/gotools'
make[1]: Entering directory '/opt/gopath/src/github.com/hyperledger/fabric/gotools'
Building github.com/golang/protobuf/protoc-gen-go -> protoc-gen-go
make[1]: Leaving directory '/opt/gopath/src/github.com/hyperledger/fabric/gotools'
make[1]: Entering directory '/opt/gopath/src/github.com/hyperledger/fabric/gotools'
Building github.com/onsi/ginkgo/ginkgo -> ginkgo
make[1]: Leaving directory '/opt/gopath/src/github.com/hyperledger/fabric/gotools'
make[1]: Entering directory '/opt/gopath/src/github.com/hyperledger/fabric/gotools'
Building github.com/axw/gocov/... -> gocov
make[1]: Leaving directory '/opt/gopath/src/github.com/hyperledger/fabric/gotools'
make[1]: Entering directory '/opt/gopath/src/github.com/hyperledger/fabric/gotools'
Building github.com/AlekSi/gocov-xml -> gocov-xml
make[1]: Leaving directory '/opt/gopath/src/github.com/hyperledger/fabric/gotools'
make[1]: Entering directory '/opt/gopath/src/github.com/hyperledger/fabric/gotools'
Building github.com/client9/misspell/cmd/misspell -> misspell
make[1]: Leaving directory '/opt/gopath/src/github.com/hyperledger/fabric/gotools'
cp /opt/gotools/obj/gopath/bin/golint /opt/gotools/obj/gopath/bin/govendor /opt/gotools/obj/gopath/bin/goimports /opt/gotools/obj/gopath/bin/protoc-gen-go /opt/gotools/obj/gopath/bin/ginkgo /opt/gotools/obj/gopath/bin/gocov /opt/gotools/obj/gopath/bin/gocov-xml /opt/gotools/obj/gopath/bin/misspell /opt/gotools/bin
Installing chaintool
curl -L https://github.com/hyperledger/fabric-chaintool/releases/download/v0.10.3/chaintool > build/bin/chaintool
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 599 0 599 0 0 2262 0 --:--:-- --:--:-- --:--:-- 2268
100 14.6M 100 14.6M 0 0 2966k 0 0:00:05 0:00:05 --:--:-- 3495k
chmod +x build/bin/chaintool
find: /src/github.com/hyperledger/fabric/core/chaincode/shim: No such file or directory
Creating build/goshim.tar.bz2
tar: no files or directories specified
make: *** [build/goshim.tar.bz2] Error 1
jtclark (Tue, 25 Jul 2017 21:12:34 GMT):
chaincode/shim?
jtclark (Tue, 25 Jul 2017 21:13:09 GMT):
@rjones, @jwagantall thoughts?
jwagantall (Tue, 25 Jul 2017 21:15:07 GMT):
i wonder if that find is looking in the correct directory .. is that were is expected to be? is any env variable missing?
jtclark (Tue, 25 Jul 2017 21:17:10 GMT):
maybe not....
jtclark (Tue, 25 Jul 2017 21:17:13 GMT):
it's there
jtclark (Tue, 25 Jul 2017 21:17:21 GMT):
just not being picked up by the find....
jtclark (Tue, 25 Jul 2017 21:17:23 GMT):
_checks_
jwagantall (Tue, 25 Jul 2017 21:23:37 GMT):
are you able to find it manually.. is this on your personal machine? or jenkins?
jtclark (Tue, 25 Jul 2017 21:23:46 GMT):
personal machine
jtclark (Tue, 25 Jul 2017 21:23:53 GMT):
starting there
jtclark (Tue, 25 Jul 2017 21:24:19 GMT):
the directory is there locally
jwagantall (Tue, 25 Jul 2017 21:24:34 GMT):
because jenkins has several env variables.. tha'ts what i think it might be missing..
jwagantall (Tue, 25 Jul 2017 21:24:47 GMT):
did you defined WORKSPACE and those basic ones?
jwagantall (Tue, 25 Jul 2017 21:24:57 GMT):
im not sure if you will need GOPATH
jtclark (Tue, 25 Jul 2017 21:25:24 GMT):
```GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/jasonclark/go"
GORACE=""
GOROOT="/usr/local/go"
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/76/6kxcb4zj5d32st7y80935pgw0000gn/T/go-build269432261=/tmp/go-build -gno-record-gcc-switches -fno-common"
CXX="clang++"
CGO_ENABLED="1"
PKG_CONFIG="pkg-config"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"```
jtclark (Tue, 25 Jul 2017 21:28:27 GMT):
Perhaps I will just try creating a JJB file for this
jtclark (Tue, 25 Jul 2017 21:28:31 GMT):
and test it on the sandbox.
jtclark (Tue, 25 Jul 2017 21:28:43 GMT):
that way, I don't have to wait for my env to be perfect
jyellick (Wed, 26 Jul 2017 02:28:28 GMT):
@rameshthoomu Could you rerun the fabric-verify-x86_64 for https://gerrit.hyperledger.org/r/#/c/11921/
rameshthoomu (Wed, 26 Jul 2017 02:30:16 GMT):
Done
jyellick (Wed, 26 Jul 2017 02:34:45 GMT):
Thanks
Ratnakar (Wed, 26 Jul 2017 18:12:10 GMT):
Unable to access the jenkin console logs page directly from the Gerrit page
https://logs.hyperledger.org/jobbuilder/vex-yul-hyp-jenkins-1/fabric-verify-x86_64/14564
rjones (Wed, 26 Jul 2017 18:18:44 GMT):
@Ratnakar https://logs.hyperledger.org/production/vex-yul-hyp-jenkins-1/fabric-verify-x86_64/14564/
Ratnakar (Wed, 26 Jul 2017 18:19:38 GMT):
@rjones Thankyou
rjones (Wed, 26 Jul 2017 18:20:04 GMT):
@Ratnakar thank _you_ for pointing out I need to fix the plugin
rjones (Wed, 26 Jul 2017 18:24:01 GMT):
@Ratnakar I made that change on 16-JUN and you're the first person to notice the error - tells me how much people use the logs :)
lehors (Thu, 27 Jul 2017 00:15:13 GMT):
@rjones for what it's worth I did notice there were broken links
lehors (Thu, 27 Jul 2017 00:15:13 GMT):
@rjones for what it's worth I did notice there were borken links
lehors (Thu, 27 Jul 2017 00:15:33 GMT):
I assumed it was a known issue
lehors (Thu, 27 Jul 2017 00:15:45 GMT):
which I realize was the stupid assumption
lehors (Thu, 27 Jul 2017 00:15:45 GMT):
which I realize was a stupid assumption
rjones (Thu, 27 Jul 2017 00:15:59 GMT):
@lehors if you `s/jobbuilder/production/` in the url it works
lehors (Thu, 27 Jul 2017 00:16:09 GMT):
ok, good to know
rjones (Thu, 27 Jul 2017 00:17:21 GMT):
what is your position on log retention? my position is keep the logs forever, basically, but unless something is ingesting them for analysis it's probably a waste
rjones (Thu, 27 Jul 2017 00:18:11 GMT):
[ ](https://chat.hyperledger.org/channel/ci-pipeline?msg=ceWTmCDbxTGG9CeDa) @cbf 's position
lehors (Thu, 27 Jul 2017 00:18:14 GMT):
for the logs, I've been using the link to the Console output which worked
lehors (Thu, 27 Jul 2017 00:18:40 GMT):
I would agree we don't need to keep them forever
lehors (Thu, 27 Jul 2017 00:19:35 GMT):
at the same time they are probably not the most expensive things to keep
rjones (Thu, 27 Jul 2017 00:19:47 GMT):
iirc the console output logs are only kept at most a week, once we moved to logshipping I cut retention down quite a bit. the next step (now that the links in gerrit work) is to set retention to a day
lehors (Thu, 27 Jul 2017 00:20:04 GMT):
you could mitigate this simply by having a long retention policy but delete eventually
lehors (Thu, 27 Jul 2017 00:20:22 GMT):
say a year or maybe 6 months, that would seem to be plenty
rjones (Thu, 27 Jul 2017 00:20:36 GMT):
space on the Jenkins server is at a premium, which is where the console logs are kept. Space on nexus, not so much
lehors (Thu, 27 Jul 2017 00:20:44 GMT):
I see
rjones (Thu, 27 Jul 2017 00:20:44 GMT):
I could see six months
lehors (Thu, 27 Jul 2017 00:20:49 GMT):
that makes sense
rjones (Thu, 27 Jul 2017 00:21:35 GMT):
there are design decisions in jenkins that make some operations fraught. Most operations are single threaded. For instance, multiple people having the web UI open slows the service down.
lehors (Thu, 27 Jul 2017 00:22:11 GMT):
oh
rjones (Thu, 27 Jul 2017 00:23:21 GMT):
copying artifacts (logs) back to the server from a minion, or copying them from the server to a web view, is blocking
lehors (Thu, 27 Jul 2017 00:23:52 GMT):
what about having it open multiple times? :-/
rjones (Thu, 27 Jul 2017 00:24:19 GMT):
it takes a lot of people to drag the server down! I'm not saying don't do it, just that it isn't free
lehors (Thu, 27 Jul 2017 00:24:28 GMT):
ok
lehors (Thu, 27 Jul 2017 00:25:09 GMT):
as I told @jtclark the other day (yesterday?) there is room for optimization on the CI front
rjones (Thu, 27 Jul 2017 00:25:24 GMT):
yes very much so
lehors (Thu, 27 Jul 2017 00:25:38 GMT):
for one thing if I push a new patch-set and it starts a new build it should stop any previous builds running
lehors (Thu, 27 Jul 2017 00:25:53 GMT):
short of doing it automatically it would be nice to be able to stop it manually
lehors (Thu, 27 Jul 2017 00:26:40 GMT):
my simple use case is: I push a change, realize I screwed something up, I push a second change
lehors (Thu, 27 Jul 2017 00:26:51 GMT):
we end up with 2 builds running
rjones (Thu, 27 Jul 2017 00:27:01 GMT):
We could open up the ability to kill builds, but there isn't a knob that limits it to 'kill your builds'
rjones (Thu, 27 Jul 2017 00:28:20 GMT):
outside of periods of high use on the Z platform, our builds are limited to 35 or 40 x86 minions. are we running out a lot?
lehors (Thu, 27 Jul 2017 00:28:21 GMT):
I feel bad because I screwed up and the fact that I'm wasting resources running a useless build only makes it worse :)
lehors (Thu, 27 Jul 2017 00:29:06 GMT):
I thought that's something you would tell me! :)
rjones (Thu, 27 Jul 2017 00:29:38 GMT):
:)
rjones (Thu, 27 Jul 2017 00:31:44 GMT):
I guess I treat CI as more fire-and-forget. I clearly have an impedance mismatch
rjones (Thu, 27 Jul 2017 00:35:05 GMT):
If you want to see something scary, when Jenkins is busy, look at this page in your browser's debugger: https://jenkins.hyperledger.org/ with the `build executor status` window collapsed and open. look at the amount of JSON flying around to keep those build progress bars updated
lehors (Thu, 27 Jul 2017 00:37:56 GMT):
ok, I will check :)
jyellick (Thu, 27 Jul 2017 14:27:03 GMT):
@rameshthoomu Could you check the health of CI? https://jenkins.hyperledger.org/job/fabric-verify-x86_64/ Looks to me like no build has run in a couple hours, and I have a few CRs which I've run "reveriify" on (such as https://gerrit.hyperledger.org/r/#/c/11501/ ) which are just sitting there
rameshthoomu (Thu, 27 Jul 2017 14:29:20 GMT):
yes.. Trigger events are not working.
rameshthoomu (Thu, 27 Jul 2017 14:29:20 GMT):
yes.. Gerrit Trigger events are not working.
rameshthoomu (Thu, 27 Jul 2017 14:37:13 GMT):
informed LF team..
mastersingh24 (Thu, 27 Jul 2017 15:03:21 GMT):
gracias
rjones (Thu, 27 Jul 2017 16:22:51 GMT):
@jyellick @mastersingh24 I have manually triggered some of the builds
jyellick (Thu, 27 Jul 2017 19:22:54 GMT):
@rjones @rameshthoomu Any updates on the trigger outage? Any place we can watch for status?
rjones (Thu, 27 Jul 2017 19:23:36 GMT):
I need to restart Jenkins. There is a long-running job - it's been running for over 8 hours! - blocking the restart
rjones (Thu, 27 Jul 2017 19:24:03 GMT):
@jyellick https://jenkins.hyperledger.org/job/fabric-daily-tests-x86_64/buildTimeTrend almost 9 hours
rjones (Thu, 27 Jul 2017 19:26:05 GMT):
@rameshthoomu when the last `-verify` job completes, may I kill this `daily-tests` job and let it re-run Friday?
rameshthoomu (Thu, 27 Jul 2017 19:26:19 GMT):
yes
rjones (Thu, 27 Jul 2017 19:26:41 GMT):
OK. I hope it finishes first, but if it doesn't, I'll kill it
rameshthoomu (Thu, 27 Jul 2017 19:28:48 GMT):
@rjones kill that job.. I will trigger it later or will let it run on friday..
rjones (Thu, 27 Jul 2017 19:29:04 GMT):
@rameshthoomu I want to wait for the other job to complete.
rjones (Thu, 27 Jul 2017 19:29:30 GMT):
(which it is doing now)
rameshthoomu (Thu, 27 Jul 2017 19:29:33 GMT):
ok..
rjones (Thu, 27 Jul 2017 19:31:18 GMT):
builds won't start right away. I need to test the trigger.
rjones (Thu, 27 Jul 2017 19:34:07 GMT):
OK. Builds released. I just tested the trigger on @jyellick 's most recent change, and it worked
rjones (Thu, 27 Jul 2017 19:35:26 GMT):
I'll go back and retrigger anything that hasn't moved today
rjones (Thu, 27 Jul 2017 19:58:20 GMT):
OK. @rameshthoomu I've retriggered the very long running job
rjones (Thu, 27 Jul 2017 20:30:11 GMT):
@jyellick @rameshthoomu one more jenkins restart coming
mastersingh24 (Fri, 28 Jul 2017 16:42:53 GMT):
How are we looking on CI these days?
mastersingh24 (Fri, 28 Jul 2017 16:43:12 GMT):
If still manually triggering, this guy could use some help: https://gerrit.hyperledger.org/r/#/c/12019/
rjones (Fri, 28 Jul 2017 16:46:15 GMT):
it shouldn't be manual, but I see that change didn't trigger a build.
rjones (Fri, 28 Jul 2017 16:49:17 GMT):
I've manually triggered several builds.
rjones (Fri, 28 Jul 2017 18:59:28 GMT):
please don't `reverify` anything right now.
jyellick (Sat, 29 Jul 2017 16:46:21 GMT):
Any status updates on CI? Anywhere we can see what the current state is, if we should be submitting new patches, reverifies, etc.?
rjones (Sat, 29 Jul 2017 16:49:03 GMT):
we're taking a 90 minute outage in 14 minutes. you're welcome to submit patches to gerrit.
jyellick (Sat, 29 Jul 2017 16:51:40 GMT):
Is there a status page like https://status.linuxfoundation.org/history but for our CI?
rjones (Sat, 29 Jul 2017 17:04:52 GMT):
@jyellick I now know I can't update that page directly, so I've asked for access to do so.
rjones (Sat, 29 Jul 2017 19:48:22 GMT):
@jyellick the outage is over. I'm keeping an eye on Jenkins waiting for the issue to repro. You're welcome to upload patches, etc, reverify
rjones (Sat, 29 Jul 2017 19:48:43 GMT):
@jyellick if the gerrit plugin falls over again I'll have more to go on
jyellick (Sat, 29 Jul 2017 19:55:33 GMT):
Great, thanks for the update @rjones
mastersingh24 (Sun, 30 Jul 2017 16:50:27 GMT):
Does not seem like the trigger is working?
mastersingh24 (Sun, 30 Jul 2017 18:27:28 GMT):
But the @rjones trigger seems to be. sorry Ry
rjones (Sun, 30 Jul 2017 18:27:46 GMT):
not your fault Jenkins is astable
mastersingh24 (Mon, 31 Jul 2017 11:02:52 GMT):
Good news is that builds are being triggered. Bad news is that I'm seeing the same error as in this log:
https://jenkins.hyperledger.org/job/fabric-verify-x86_64/14758/console
(I have not tried submitting against master - these are all against the release branch in case that makes a difference)
rameshthoomu (Mon, 31 Jul 2017 13:03:22 GMT):
@rjones @jwagantall seems plugin compatibility is causing this error.. java.lang.NoSuchMethodError: org.eclipse.jgit.revwalk.RevWalk.release
rameshthoomu (Mon, 31 Jul 2017 13:35:53 GMT):
@rjones I have created https://jira.hyperledger.org/browse/FAB-5541 to track the status of above issue..
rjones (Mon, 31 Jul 2017 18:23:29 GMT):
I've replaced the plugin but I'm no closer to seeing why the other failure is happening
lasantha (Tue, 01 Aug 2017 03:13:35 GMT):
Has joined the channel.
tongli (Tue, 01 Aug 2017 14:50:58 GMT):
@rjones, Ry, thanks for the comments for my patch set. can you tell me what white space checking tool we use at the gate? I would like to have the same thing installed to check the problems before I submit another patch set.
jimthematrix (Tue, 01 Aug 2017 15:40:18 GMT):
@rjones @jwagantall can I request for a new repository `fabric-shim-node` to be created? has been discussed with @cbf and @mastersingh24 in the context of https://jira.hyperledger.org/browse/FAB-2331, which I've sent an announce email for to the mailing list last week
jimthematrix (Tue, 01 Aug 2017 15:40:18 GMT):
@rjones @jwagantall can I request for a new repository `fabric-shim-node` to be created? has been discussed with @cbf and @mastersingh24 in the context of https://jira.hyperledger.org/browse/FAB-2331, which I've sent an announce email to the mailing list last week
jimthematrix (Tue, 01 Aug 2017 15:45:02 GMT):
initial maintainers should be
```Jim Zhang, jzhang@us.ibm.com
David Kelsay, d_kelsey@uk.ibm.com
Bret Harrison
jimthematrix (Tue, 01 Aug 2017 15:45:02 GMT):
initial maintainers should be
```Jim Zhang, jzhang@us.ibm.com
David Kelsey, d_kelsey@uk.ibm.com
Bret Harrison
cbf (Tue, 01 Aug 2017 15:58:14 GMT):
@jimthematrix @rjones https://jira.hyperledger.org/browse/FAB-2331 has the requisite votes to proceed
cbf (Tue, 01 Aug 2017 15:58:52 GMT):
@jimthematrix is that the best name? Wouldn't it be fabric-javascript-cc?
jimthematrix (Tue, 01 Aug 2017 15:59:29 GMT):
I think "shim" should be part of the name, since that's essentially what's being peeled off
jwagantall (Tue, 01 Aug 2017 15:59:51 GMT):
I can help with this request .
jimthematrix (Tue, 01 Aug 2017 15:59:52 GMT):
the rest is integration glue code is still in GO in fabric repo
jimthematrix (Tue, 01 Aug 2017 16:00:09 GMT):
let me validate that with Luis
cbf (Tue, 01 Aug 2017 16:00:13 GMT):
ok - just re-examined what's under core/chaincode and yea
jimthematrix (Tue, 01 Aug 2017 16:00:28 GMT):
likely the java one should be "fabric-shim-java"
cbf (Tue, 01 Aug 2017 16:00:33 GMT):
but is node the right language qualifier?
cbf (Tue, 01 Aug 2017 16:00:38 GMT):
or js
jimthematrix (Tue, 01 Aug 2017 16:01:03 GMT):
should be more specific than JS since these are meant to run under the node.js engine
cbf (Tue, 01 Aug 2017 16:01:10 GMT):
could we possibly have a js shim that then supported various frameworks?
cbf (Tue, 01 Aug 2017 16:01:19 GMT):
ok fair enough
jimthematrix (Tue, 01 Aug 2017 16:01:27 GMT):
they are written as CommonJS modules that other engines like those in browsers won't understand
jimthematrix (Tue, 01 Aug 2017 16:04:54 GMT):
discussed with Luiz, let's use the naming convention "fabric-chaincode-
jimthematrix (Tue, 01 Aug 2017 16:04:54 GMT):
discussed with @sanchezl , let's use the naming convention "fabric-chaincode-
jimthematrix (Tue, 01 Aug 2017 16:05:12 GMT):
for java and node chaincode support, at the moment it'll just be the shim to be peeled off
jimthematrix (Tue, 01 Aug 2017 16:05:23 GMT):
but in the future there could be others like tools, etc.
jimthematrix (Tue, 01 Aug 2017 16:05:57 GMT):
so "chaincode" is a better term and more generic to accommodate future expansion of the repo's intended content
jimthematrix (Tue, 01 Aug 2017 16:06:08 GMT):
@cbf @jwagantall ^^^
cbf (Tue, 01 Aug 2017 16:06:49 GMT):
ok by me
cbf (Tue, 01 Aug 2017 16:07:08 GMT):
can we set up both node and java then?
cbf (Tue, 01 Aug 2017 16:07:15 GMT):
might as well
jwagantall (Tue, 01 Aug 2017 16:08:04 GMT):
so .. 2 gerrit repos ... fabric-chaincode-node and fabric-chaincode-java ? will they be sharing the same group of committers?
sanchezl (Tue, 01 Aug 2017 16:12:15 GMT):
For fabric-chaincode-java, I suggest @muralisr & @sanchezl
jimthematrix (Tue, 01 Aug 2017 16:14:28 GMT):
@sanchezl agreed, and I think you will need to provide emails each committer used for gerrit
jimthematrix (Tue, 01 Aug 2017 16:14:28 GMT):
@sanchezl I think you will need to provide emails each committer used for gerrit
sanchezl (Tue, 01 Aug 2017 16:16:10 GMT):
Srinivasan Muralidharan
jwagantall (Tue, 01 Aug 2017 16:24:41 GMT):
Can we please add the final details in the jira too please? Including list of committers... that way we can have a record
jimthematrix (Tue, 01 Aug 2017 17:02:17 GMT):
@jwagantall for fabric-chaincode-node: https://jira.hyperledger.org/browse/FAB-5572, thanks!
jimthematrix (Tue, 01 Aug 2017 17:03:07 GMT):
Luis will create one for fabric-chaincode-java separately
jwagantall (Tue, 01 Aug 2017 17:29:25 GMT):
thank you ..
sanchezl (Tue, 01 Aug 2017 18:03:02 GMT):
@jwagantall for fabric-chaincode-java: https://jira.hyperledger.org/browse/FAB-5573
rjones (Tue, 01 Aug 2017 18:11:21 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=2btp7Rsqd8Dg3e62j) @tongli it is in the build logs - I don't know off the top of my head
tongli (Tue, 01 Aug 2017 18:12:05 GMT):
@rjones,I will take a look at the log file. thanks.
tongli (Tue, 01 Aug 2017 18:24:13 GMT):
@rjones, looked at the project, it seems to me it uses tox.
jwagantall (Tue, 01 Aug 2017 19:07:54 GMT):
@jimthematrix @sanchezl the repos are created now... do you guys need me to set them up in Jenkins and Nexus to push in future there? or not needed?
jimthematrix (Tue, 01 Aug 2017 20:12:46 GMT):
thanks Jessica, would need Jenkins integration for sure, for nexus fabric-chaincode-node for the moment does not publish binaries (it published directly to npm), but I'm pretty sure fabric-chaincode-java would need to
jimthematrix (Tue, 01 Aug 2017 20:12:58 GMT):
@jwagantall ^^^
jwagantall (Tue, 01 Aug 2017 20:13:28 GMT):
awesome.. will set that up
jwagantall (Tue, 01 Aug 2017 20:13:31 GMT):
thanks!
jimthematrix (Tue, 01 Aug 2017 20:13:55 GMT):
thank you!
amod (Wed, 02 Aug 2017 15:01:48 GMT):
Has joined the channel.
rjones (Fri, 04 Aug 2017 17:22:40 GMT):
fabric ci performance on x86 in our infra is getting a lot of attention in #ci-pipeline if any interested party is not already watching.
eacoeytaux (Fri, 04 Aug 2017 19:52:42 GMT):
Has joined the channel.
yacovm (Sun, 06 Aug 2017 18:53:33 GMT):
@rjones to my knowledge, crypto computations have a very big role in the system performance as a whole but I'm not sure how much they affect unit tests.
rjones (Sun, 06 Aug 2017 19:11:29 GMT):
@yacovm the difference between AES passthrough and native floating point is an order of magnitude
yacovm (Sun, 06 Aug 2017 19:15:23 GMT):
well yeah I understand but only a minority of UTs use crypto from what I know
yacovm (Sun, 06 Aug 2017 19:17:12 GMT):
btw can you please retrigger https://jenkins.hyperledger.org/job/fabric-verify-x86_64/15046/console and the failed jobs in https://gerrit.hyperledger.org/r/#/c/12193/ ?
yacovm (Sun, 06 Aug 2017 19:18:09 GMT):
Also I'll give you an example- there was 1 time where gossip UTs were very slow on PPC and they were fast on x86, and I disabled TLS and they were still slow...
rjones (Sun, 06 Aug 2017 19:23:12 GMT):
done
rjones (Mon, 07 Aug 2017 01:08:28 GMT):
@yacovm based on the profiling done in #ci-pipeline the call graph is dominated by crypto when not accelerated
jyellick (Mon, 07 Aug 2017 04:43:58 GMT):
Looks like there are a number of hung x86 builds https://jenkins.hyperledger.org/job/fabric-verify-x86_64/
jyellick (Mon, 07 Aug 2017 04:44:27 GMT):
@rameshthoomu @rjones ^
rjones (Mon, 07 Aug 2017 04:45:02 GMT):
I noticed they're taking a long time tonight and some are timing out
rjones (Mon, 07 Aug 2017 04:45:37 GMT):
if you look here it's pretty gross: https://jenkins.hyperledger.org/job/fabric-verify-x86_64/buildTimeTrend
jyellick (Mon, 07 Aug 2017 05:11:29 GMT):
Indeed... glad to hear you are tracking it, just thought I'd report it in case no one had noticed yet
rjones (Mon, 07 Aug 2017 05:19:07 GMT):
I'm keeping my good eye on it, but I suspect it's a change in the merged code
jyellick (Mon, 07 Aug 2017 05:35:38 GMT):
Any chance that the x86 machines are just running slow? I am seeing lots of x86 failures across the board, while Z seems to be quite happy with the same commit
mastersingh24 (Mon, 07 Aug 2017 11:43:56 GMT):
Something odd going on with CI - not sure if there's something wrong with the CRs or CI. Hard to say
dave.enyeart (Mon, 07 Aug 2017 12:49:22 GMT):
yes, CI has been very unreliable recently. 1.1 work items are blocked. @rjones @rameshthoomu and all, appreciate if you could dedicate time to this today
dave.enyeart (Mon, 07 Aug 2017 12:49:55 GMT):
@yacovm Also there have been intermittent gossip CI failures
rameshthoomu (Mon, 07 Aug 2017 12:50:03 GMT):
@dave.enyeart @mastersingh24 I have created FAB https://jira.hyperledger.org/browse/FAB-5643
rameshthoomu (Mon, 07 Aug 2017 12:51:05 GMT):
I think this patch https://gerrit.hyperledger.org/r/#/c/12141/ is causing longer builds
mastersingh24 (Mon, 07 Aug 2017 12:53:37 GMT):
Not sure how that is possible
dave.enyeart (Mon, 07 Aug 2017 12:53:50 GMT):
@scottz Also behave and end-to-end CI verifications are failing. Who could take a look at these? Various examples of these failures in the reverifies for https://gerrit.hyperledger.org/r/#/c/12177/ and https://gerrit.hyperledger.org/r/#/c/12161/
mastersingh24 (Mon, 07 Aug 2017 12:54:18 GMT):
I'm pretty sure there's somthing wrong with the CI machines
rameshthoomu (Mon, 07 Aug 2017 13:14:56 GMT):
yes @mastersingh24 I have verified all x86 builds (behave, end-to-end and unit-tests) taking longer time..
rameshthoomu (Mon, 07 Aug 2017 13:16:47 GMT):
all tests are failing (behave and java end-to-end) because x86_64 build nodes are processing requests with huge delay.. @rjones @jwagantall could you please check this
rameshthoomu (Mon, 07 Aug 2017 13:17:19 GMT):
observed same unit-tests are working as expected in `z` platform..
dave.enyeart (Mon, 07 Aug 2017 16:14:15 GMT):
@rameshthoomu @rjones It looks like some verifications are succeeding now. Did something change for the better?
rjones (Mon, 07 Aug 2017 16:17:19 GMT):
@dave.enyeart something changed, yes
rjones (Mon, 07 Aug 2017 16:17:43 GMT):
I don't mean to be opaque but I don't know exactly what was changed
dave.enyeart (Mon, 07 Aug 2017 16:18:36 GMT):
ok, did the environments get restarted or something? i mean, if the problem resurfaces, what is the corrective action?
rjones (Mon, 07 Aug 2017 16:21:05 GMT):
You're asking reasonable questions I can't answer yet
cbf (Mon, 07 Aug 2017 18:36:17 GMT):
@dave.enyeart @mastersingh24 there was a bunch of discussion over the weekend on #ci-pipeline where (I presume) some of the LF infrastructure support team were examining the configuration and trying to debug the problems we've been seeing (slow builds etc). @rjones is basically telling us that he isn't aware of the specific things that they are tweaking in an effort to resolve our problems.
cbf (Mon, 07 Aug 2017 18:36:37 GMT):
I am encouraged that there is some energy behind this
rjones (Mon, 07 Aug 2017 18:52:33 GMT):
@cbf: mnaser owns the service provider, mricon is one of the engineering leads for LF.
cbf (Mon, 07 Aug 2017 19:18:30 GMT):
@rjones thanks
dave.enyeart (Mon, 07 Aug 2017 22:09:01 GMT):
@rameshthoomu @rjones Tonight we have the opposite CI problem... the x86 tests are all succeeding but the z tests are failing, happened twice in a row in https://gerrit.hyperledger.org/r/#/c/12163/
rjones (Mon, 07 Aug 2017 22:13:11 GMT):
@dave.enyeart Z is a bit of a black box to me. I do see a specific unit test is failing though:
rjones (Mon, 07 Aug 2017 22:13:14 GMT):
```unit-tests_1 | --- FAIL: TestLeaderYield (45.00s)
unit-tests_1 | integration_test.go:134: p0 started its delivery service
unit-tests_1 | assertions.go:225:
Error Trace: integration_test.go:120
unit-tests_1 |
integration_test.go:136
unit-tests_1 |
Error: Should be false
unit-tests_1 |
unit-tests_1 | integration_test.go:139: p0 stopped its delivery service
unit-tests_1 | integration_test.go:144: p1 started its delivery service
unit-tests_1 | assertions.go:225:
Error Trace: integration_test.go:146
unit-tests_1 |
Error: Not equal: 1 (expected)
unit-tests_1 | != -1 (actual)
unit-tests_1 |
```
rjones (Mon, 07 Aug 2017 22:14:10 GMT):
@harrijk any turbulence on Z lately?
harrijk (Mon, 07 Aug 2017 22:15:26 GMT):
hmm. This is the first that I've seen these issues. I
harrijk (Mon, 07 Aug 2017 22:15:26 GMT):
hmm. This is the first that I've seen these issues. I guess I'd have to track it back to any recent changes
dave.enyeart (Mon, 07 Aug 2017 22:15:41 GMT):
ok, that specific test has caused problems and is being removed in https://gerrit.hyperledger.org/r/#/c/12237/
dave.enyeart (Mon, 07 Aug 2017 22:15:45 GMT):
I will merge that one
harrijk (Mon, 07 Aug 2017 22:15:50 GMT):
OK
dave.enyeart (Mon, 07 Aug 2017 22:15:54 GMT):
and then reverify the other
rjones (Mon, 07 Aug 2017 22:24:19 GMT):
you'll need to rebase as well
mavstronaut (Tue, 08 Aug 2017 04:04:25 GMT):
Has joined the channel.
rjones (Tue, 08 Aug 2017 22:05:53 GMT):
@rameshthoomu @rickr if I understand https://gerrit.hyperledger.org/r/#/c/12097/ you want to wait until 1.0.1 docker images are pushed to merge, correct?
rameshthoomu (Wed, 09 Aug 2017 00:13:13 GMT):
yes @rjones
medhak19 (Wed, 09 Aug 2017 07:13:02 GMT):
Has joined the channel.
rjones (Wed, 09 Aug 2017 21:59:58 GMT):
there will be a short Jenkins outage to upgrade RAM when the current jobs finish. It will be a couple of minutes.
rjones (Wed, 09 Aug 2017 23:15:29 GMT):
outage is over, Jenkins VM is rebooted and has 2x the RAM it had
jimthematrix (Thu, 10 Aug 2017 13:57:23 GMT):
hi @rameshthoomu the merge CI for https://gerrit.hyperledger.org/r/#/c/12301/ hasn't started after almost 2 hours
rameshthoomu (Thu, 10 Aug 2017 13:57:51 GMT):
checking
rameshthoomu (Thu, 10 Aug 2017 14:02:43 GMT):
@jimthematrix this job was triggered on `z` and `x86` but failed on x86 https://jenkins.hyperledger.org/view/fabric-sdk-node/job/fabric-sdk-node-merge-x86_64/413/console
jimthematrix (Thu, 10 Aug 2017 14:06:48 GMT):
can you trigger that manually? from what I can tell it's not a code issue:
```12:25:06 [12:25:06] Finished 'pre-test' after 8.9 s
12:25:06 [12:25:06] Finished 'ca' after 8.95 s
12:25:08 [12:25:08] Finished 'lint' after 11 s
12:25:08 + '[' 1 == 0 ']'
12:25:08 + cp /tmp/hfc/test-log/debug.log /w/workspace/fabric-sdk-node-merge-x86_64
12:25:08 + exit 1
12:25:08 Build step 'Execute shell' marked build as failure
rameshthoomu (Thu, 10 Aug 2017 14:15:16 GMT):
Triggered manually
rameshthoomu (Thu, 10 Aug 2017 14:15:23 GMT):
but I see this
```
00:09:02.648 Creating network "fixtures_default" with the default driver
00:09:02.950 Pulling couchdb (hyperledger/fabric-couchdb:latest)...
00:09:03.352 [12:25:01] gulp-debug: fabric-client/lib/hash.js
00:09:03.434 manifest for hyperledger/fabric-couchdb:latest not found
00:09:03.982 [12:25:02] 'docker-ready' errored after 1.84 s
00:09:03.982 [12:25:02] Error in plugin 'gulp-shell'
```
rameshthoomu (Thu, 10 Aug 2017 14:15:51 GMT):
unable to find couchdb image..
jimthematrix (Thu, 10 Aug 2017 14:26:58 GMT):
@rameshthoomu shouldn't that have been made available by the fabric build?
jimthematrix (Thu, 10 Aug 2017 14:26:58 GMT):
@rameshthoomu shouldn't that have been made available by the fabric build that happens in the beginning of the CI job?
jimthematrix (Thu, 10 Aug 2017 14:27:10 GMT):
it's always been like that
rameshthoomu (Thu, 10 Aug 2017 14:28:59 GMT):
yes it should be available but for some reason it missed in this case.. checking why it is unavailable..
rameshthoomu (Thu, 10 Aug 2017 15:18:49 GMT):
Done/. It worked this time and published 1.0.1 npm modules successfully
jyellick (Fri, 11 Aug 2017 02:14:11 GMT):
@rameshthoomu I see your name attached to the commit which set this line:
```
1e9a087903 unit-test/run.sh (rameshthoomu 2017-06-06 07:50:05 -0400 79) gocov test -ldflags "$GO_LDFLAGS" $PKGS -p 1 -timeout=20m | gocov-xml > report.xml
```
in the `unit-test/run.sh` file. Whenever I am forced to run `make unit-test` locally, I am amazed at how slowly it runs, so almost always do `go test ./component/...` myself as it is usually multiple orders of magnitude faster. I just did a quick check, replacing that line with:
```
go test -p 1 -ldflags "$GO_LDFLAGS" $PKGS -timeout=20m
```
The time for testing the same set of packages drops from 8 minutes, to 1.5 minutes. So it appears that using `gocov` is occupying about 80% of the time when the unit tests are actually running. Seems like we could significantly speed up CI if we could simply run the code coverage stats when needed. Maybe only on packages with changed files? Or, maybe only in a once a week job or something?
acosta_rodrigo (Sat, 12 Aug 2017 17:03:44 GMT):
Has joined the channel.
rameshthoomu (Mon, 14 Aug 2017 18:15:07 GMT):
@rickr @jimthematrix published 1.0.1 fabric-sdk-java release to maven.. http://repo1.maven.org/maven2/org/hyperledger/fabric-sdk-java/fabric-sdk-java/
rameshthoomu (Mon, 14 Aug 2017 18:15:54 GMT):
I also performed release to maven.. this will take 24 hrs to publish here https://mvnrepository.com/artifact/org.hyperledger.fabric-sdk-java/fabric-sdk-java
aleksandar.likic (Mon, 14 Aug 2017 19:01:02 GMT):
Has joined the channel.
sudeshrshetty (Mon, 14 Aug 2017 19:18:35 GMT):
Has joined the channel.
sudeshrshetty (Mon, 14 Aug 2017 19:31:51 GMT):
Hi Guys, Needed your help.
As per new story FAB-5460, we are implementing new kind of chaincodes, i.e precompiled binary user chaincodes.
We pushed the changes just now but verification build "https://jenkins.hyperledger.org/job/fabric-verify-behave-x86_64/9629/ " just failed due to failure in bddtests.
Cause: There is a new target added to makefile called 'sample-binarycc-files', which has to be run before running bddtests just like existing make peer and make docker targets.
Since this verification build is not using 'make behave' to run bddtests and we have limited access to jenkins job "https://jenkins.hyperledger.org/view/fabric/job/fabric-verify-behave-x86_64/", the verification build is failing.
Can anyone add make sample-binarycc-files to below execute shell of this job only for this code push. .
.
.
# Build Peer and images
make peer && make docker && make sample-binarycc-files
.
.
.
Here is the gerrit link for code push
https://gerrit.hyperledger.org/r/#/c/12435/
Any help would be appreciated
sudeshrshetty (Mon, 14 Aug 2017 20:05:28 GMT):
This new target 'make sample-binarycc-files' generates sample binary chaincode files which will be used by bddtests.
I guess, changing jenkins job in advance for new target before this code is getting merged may fail the build for others who of course doesn't have this target.
I have a work around for time being where I can add this new target 'make sample-binarycc-files' as dependency for 'make peer'(which is already being used by this jenkins job), so that verification build will be successful. Once the code is merged then jenkins execute shell can be changed to include this new target and I will revert this work around later.Let me know what you think about this.
rameshthoomu (Mon, 14 Aug 2017 20:15:39 GMT):
@sudeshrshetty checking this
sudeshrshetty (Mon, 14 Aug 2017 20:30:25 GMT):
Thanks ramesh
rameshthoomu (Mon, 14 Aug 2017 21:18:40 GMT):
@sudeshrshetty I have tested your patch with `make sample-binarycc-files` and it worked as expected in jenkins sandbox
rameshthoomu (Mon, 14 Aug 2017 21:18:48 GMT):
https://jenkins.hyperledger.org/sandbox/job/fabric-verify-behave-x86_64/2/consoleFull
rameshthoomu (Mon, 14 Aug 2017 21:19:29 GMT):
But I can not add make target in CI till your patch is merged in fabric..
sudeshrshetty (Mon, 14 Aug 2017 22:24:11 GMT):
Thanks Ramesh, I will push it as a dependency on make peer as of now and Will create a JIRA to revert it back once my code is merged and you make changes in jenkins.
Does it took fine for you?
sudeshrshetty (Mon, 14 Aug 2017 22:25:14 GMT):
or can we ignore this verification fail for this build
rameshthoomu (Tue, 15 Aug 2017 13:12:47 GMT):
@sudeshrshetty it's better to ignore this verification result.. Once your patch is merged, will include new make target in CI script..
sudeshrshetty (Tue, 15 Aug 2017 13:35:56 GMT):
Thanks a lot Ramesh
jyellick (Fri, 18 Aug 2017 16:36:47 GMT):
@rameshthoomu @rjones The x86-64 fabric unit test builds seem to be especially slow today
jyellick (Fri, 18 Aug 2017 16:37:01 GMT):
https://jenkins.hyperledger.org/job/fabric-verify-x86_64/15829/console for instance has been running for almost 2 hours (with no failures yet)
rameshthoomu (Fri, 18 Aug 2017 16:45:25 GMT):
@jyellick I see only that build took that long. https://jenkins.hyperledger.org/job/fabric-verify-x86_64/buildTimeTrend.. Will check why that took so long..
rjones (Sat, 19 Aug 2017 04:28:05 GMT):
*there is an outage at Vexxhost which is impacting our CI* more updates as they become available
rjones (Sat, 19 Aug 2017 04:56:20 GMT):
https://status.linuxfoundation.org/incidents/kxhh640z07th
rjones (Sat, 19 Aug 2017 05:24:07 GMT):
*outage resolved*
jimthematrix (Tue, 22 Aug 2017 14:50:32 GMT):
@rameshthoomu @greg.haskins I pushed a CR to fabric-baseimage, but the build is stuck due to the ppc64 build not triggering: https://jenkins.hyperledger.org/job/fabric-baseimage-verify-docker-x86_64/97/
jimthematrix (Tue, 22 Aug 2017 14:50:50 GMT):
do we need the ppc64 build for this?
rjones (Tue, 22 Aug 2017 17:46:36 GMT):
@jimthematrix I disabled that job - we're testing all of the PPC minions in sandbox
rjones (Tue, 22 Aug 2017 17:47:01 GMT):
@jimthematrix I _think_ it is OK to not wait for that job? it hasn't succeeded in forever
rjones (Tue, 22 Aug 2017 17:47:34 GMT):
since 12-June: https://jenkins.hyperledger.org/job/fabric-baseimage-verify-docker-ppc64le/
bsmita (Tue, 22 Aug 2017 18:03:21 GMT):
@rjones I see this error for the failed builds on ppc64le: /tmp/hudson4626619725428175573.sh: line 17: virtualenv: command not found
bsmita (Tue, 22 Aug 2017 18:03:39 GMT):
Looks like this error is new, we are trying a build separately
rjones (Tue, 22 Aug 2017 18:18:10 GMT):
@bsmita OK, I guess we've taken a dependency on `virtualenv` somewhat recently?
bsmita (Tue, 22 Aug 2017 18:19:09 GMT):
We are running a build on our local VM, and looking at the error on the previous community build logs...
bsmita (Tue, 22 Aug 2017 18:19:59 GMT):
The code is going to fabric-baseimage, so that should be ok
jimthematrix (Tue, 22 Aug 2017 18:55:31 GMT):
thanks @rjones for handling that, I'm ok with not having that for now. will discuss with the maintainers on how to push to docker hub (for which we might need the ppc64le build to have parity with previous versions)
bsmita (Tue, 22 Aug 2017 18:55:31 GMT):
Local build passed, testing it on the node that was being used in the community
rjones (Tue, 22 Aug 2017 18:56:13 GMT):
there is no community node in Jenkins right now
rjones (Tue, 22 Aug 2017 18:56:23 GMT):
all of the power nodes are on /sandbox/
bsmita (Tue, 22 Aug 2017 18:56:41 GMT):
Is it possible to trigger the same build in sandbox? on one node?
rjones (Tue, 22 Aug 2017 18:56:53 GMT):
not and publish from sandbox, no
bsmita (Tue, 22 Aug 2017 18:58:02 GMT):
Not the publishing part but just the fabric-baseimage build
bsmita (Tue, 22 Aug 2017 19:53:50 GMT):
@rjones - 2 local VM builds and one sandbox node build on baseimage passed
rjones (Tue, 22 Aug 2017 20:00:50 GMT):
@bsmita OK, what do you want me to do? have you updated all of the VMs so they have the virtualenv (and whatever else) dependencies installed?
bsmita (Tue, 22 Aug 2017 20:02:08 GMT):
On the nodes we tried, it didn't need updates, so that's why I was checking to see if running a baseimage build in sandbox is an option
bsmita (Tue, 22 Aug 2017 20:02:08 GMT):
On the nodes we tried, it didn't need updates, so that's why I was checking to see if running a baseimage build in sandbox is an option, any way I am checking all the nodes and updating
jimthematrix (Wed, 23 Aug 2017 02:31:04 GMT):
@rameshthoomu I just submitted https://jira.hyperledger.org/browse/FAB-5881, which is tangentially related to the node.js chaincode work, please let me know if you have any questions. thanks
Hai-XuCheng (Wed, 23 Aug 2017 08:42:05 GMT):
Has joined the channel.
sudeshrshetty (Wed, 23 Aug 2017 15:45:48 GMT):
@rameshthoomu the code push we discussed eariler where verification build failed due to missing new target 'make sample-binarycc-files' is not being reviewed by anyone due to failure in verification.
I have suggestion which will fix this verification build and also it will not impact anyone else’s code push.
If you look at execute shell in https://jenkins.hyperledger.org/job/fabric-verify-behave-x86_64/configure-readonly/
.
.
.
.
# Build Peer and images
make peer && make docker
docker images | grep hyperledger
cd bddtests
behave -k -D logs=force -D cache-deployment-spec
#behave -k -D cache-deployment-spec features/bootstrap.feature
# Deactivate vitrualenv after behave test
Deactivate
.
.
.
.
If you replace ‘make peer && make docker’ with already existing target for running behave dependencies called ‘ make behave-deps’ which does the same job, will fix my code push as well as it won’t impact others.
Thanks for any help.
sudeshrshetty (Wed, 23 Aug 2017 16:26:03 GMT):
I have also created a ticket https://jira.hyperledger.org/browse/FAB-5891 for permanent fix for such issues
sudeshrshetty (Wed, 23 Aug 2017 16:26:12 GMT):
Please have a look
rameshthoomu (Wed, 23 Aug 2017 17:09:04 GMT):
looking into this.. WIll test this in sandbox let you know the update
sudeshrshetty (Wed, 23 Aug 2017 18:33:24 GMT):
Thanks Ramesh
aleksandar.likic (Wed, 23 Aug 2017 20:58:52 GMT):
Hi all, I went through fabric Makefile, and it seems the only static code analysis is performed using 'go vet'. Is there any other static code analysis performed on fabric beyond 'go vet'? Thanks.
rameshthoomu (Thu, 24 Aug 2017 02:43:50 GMT):
@sudeshrshetty it's done now.. git +1 from CI on your patch.
sudeshrshetty (Thu, 24 Aug 2017 02:44:20 GMT):
@rameshthoomu thanks a lot for the help.
rameshthoomu (Thu, 24 Aug 2017 02:44:29 GMT):
Now every behave job executes make behave-deps
sudeshrshetty (Thu, 24 Aug 2017 02:44:40 GMT):
verification build is SUCCESS now
rameshthoomu (Thu, 24 Aug 2017 02:45:00 GMT):
Yes..
ysadek (Thu, 24 Aug 2017 14:45:39 GMT):
Has joined the channel.
sanchezl (Thu, 24 Aug 2017 17:51:01 GMT):
Does fabric (or hyperledger) have a repository (e.g. Artifactory) for publishing artifacts (e.g. jars, docker images, etc...) during development?
harsha (Thu, 24 Aug 2017 18:41:50 GMT):
I see UT failures across x and z at `github.com/hyperledger/fabric/core/chaincode`
rameshthoomu (Thu, 24 Aug 2017 18:50:10 GMT):
@sanchezl CI publish to dockerhub and maven repositories after every release but not during development..
rameshthoomu (Thu, 24 Aug 2017 18:51:41 GMT):
@harsha yes.. I see the that last merge successfully executed and after that every verify build is failing..
rameshthoomu (Thu, 24 Aug 2017 18:52:09 GMT):
that's strange..
harsha (Thu, 24 Aug 2017 18:53:33 GMT):
@rameshthoomu :- Wasn't it flagged as failure during verify/merge ?
rameshthoomu (Thu, 24 Aug 2017 19:02:53 GMT):
@harsha last patch set was passed https://jenkins.hyperledger.org/view/fabric/job/fabric-merge-x86_64/2439/console
harsha (Thu, 24 Aug 2017 19:08:37 GMT):
Ok verify is failing but merge is passing.
I see a patch in https://gerrit.hyperledger.org/r/#/c/12763/
thanks @muralisr
mastersingh24 (Sat, 26 Aug 2017 20:00:14 GMT):
@rameshthoomu - Is there something wrong with the fabric-verify-end-2-end-x86_64 job? I've seen the following:
```
18:49:00 /tmp/hudson4666462160448451997.sh: line 19: npm: command not found
18:49:00 Build step 'Execute shell' marked build as failure
```
rameshthoomu (Sat, 26 Aug 2017 20:17:04 GMT):
@mastersingh24 yesterday we tried to upgrade node js version and @rjones and @jwagantall updated CI image..
rjones (Sat, 26 Aug 2017 20:18:01 GMT):
but that image shouldn't be in production
rjones (Sat, 26 Aug 2017 20:18:16 GMT):
only sandbox
rameshthoomu (Sat, 26 Aug 2017 20:19:09 GMT):
yes
rjones (Sat, 26 Aug 2017 20:19:40 GMT):
@rameshthoomu I have rolled back to the previous image, I don't know how the packer image got updated - @jwagantall did you update Jenkins?
rjones (Sat, 26 Aug 2017 20:20:34 GMT):
@mastersingh24 I retriggered the one failed build that I see
rameshthoomu (Sat, 26 Aug 2017 20:28:48 GMT):
I see below error in many builds
``
00:23:05.792 Caused by: java.net.ConnectException: Connection refused
```
https://jenkins.hyperledger.org/view/fabric/job/fabric-verify-end-2-end-x86_64/7659/console
rameshthoomu (Sat, 26 Aug 2017 20:28:48 GMT):
I see below error in many builds
```
00:23:05.792 Caused by: java.net.ConnectException: Connection refused
```
https://jenkins.hyperledger.org/view/fabric/job/fabric-verify-end-2-end-x86_64/7659/console
rjones (Sat, 26 Aug 2017 20:29:30 GMT):
but there is only one failed build today? when were these failures?
rameshthoomu (Sat, 26 Aug 2017 20:30:58 GMT):
I see this error in these builds.. 7653, 7656,7657,7559
rjones (Sat, 26 Aug 2017 23:47:18 GMT):
@rameshthoomu that sounds like a temporary network turbulence - if it was every build I could debug it, four builds out of ca 100 is not that interesting
jimthematrix (Mon, 28 Aug 2017 01:46:09 GMT):
@rjones @jwagantall any news on installing nvm to manage node 6/7/8? Ramesh told me there were errors when trying to use nvm after the install...
rameshthoomu (Mon, 28 Aug 2017 04:46:51 GMT):
finally this is worked with the below commands.. I have used below commands while running job..
```
wget -qO- https://raw.githubusercontent.com/creationix/nvm/v0.33.2/install.sh | bash
export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh" # This loads nvm
[ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion" # This loads nvm bash_completion
nvm install 8.4.0 || true
nvm use 8.4.0
npm install
npm config set prefix ~/npm && npm install -g gulp
# Execute Integration test
npm test
```
https://jenkins.hyperledger.org/sandbox/job/fabric-chaincode-node-verify-x86_64/10/consoleFull
Tested this patch https://gerrit.hyperledger.org/r/#/c/12717/ in sandbox..
rameshthoomu (Mon, 28 Aug 2017 04:58:17 GMT):
@jimthematrix please see the log output and confirm the test result
rameshthoomu (Mon, 28 Aug 2017 04:58:48 GMT):
testing with 7.4.0 on fabric-sdk-node builds with above commands... Will give you the update by tomorrow morning..
mastersingh24 (Mon, 28 Aug 2017 09:00:34 GMT):
@rameshthoomu - did you mean 7.4.0 or 8.4.0 ? There's no reason to do anything with 7.4.0 ;)
mastersingh24 (Mon, 28 Aug 2017 11:15:56 GMT):
Given there's been a number of updates to the CI for fabric, just though I'd give you a heads up on these: https://jira.hyperledger.org/issues/?jql=text%20~%20%2217.06%22
(basically moving CI to Docker 17.06+)
mastersingh24 (Mon, 28 Aug 2017 11:17:00 GMT):
I slated this for 1.2, but it won't hurt anything to have it as soon as possible. I'm particularly interested in simplifying some of our builds by using the multi-stage build feature of 17.06
rameshthoomu (Mon, 28 Aug 2017 12:36:23 GMT):
@mastersingh24, Jim wants to test on fabric-sdk-node on different node versions (7.4.0 and 8.4.0)..
jimthematrix (Mon, 28 Aug 2017 13:02:27 GMT):
@mastersingh24 our official supported version for node SDK is >= 6.9 < 7.0.0, which is the current LTS. planning to upgrade to 8 once it enters LTS. so until that happens, we should have CIs run jobs under 6 and 8 at the same time
jimthematrix (Mon, 28 Aug 2017 13:05:57 GMT):
@rameshthoomu I didn't know our CI has been running with node 7.4, please install the latest 6.9.x instead, so we'll have jobs covering the two LTS versions 6 (current) and 8 (next). node 7 is not LTS so we never planned to support that
rameshthoomu (Mon, 28 Aug 2017 13:16:42 GMT):
ok testing on 6.9.5 and 8.4.0..
rjones (Tue, 29 Aug 2017 04:21:07 GMT):
I want to show you something. If you look here: https://jenkins.hyperledger.org/view/fabric/job/fabric-merge-x86_64/buildTimeTrend you'll notice the builds on the ubuntu1604-x86_64-2c-8g (older, slower, but with dedicated resources) are more regular than the builds on type ubuntu1604-x86_64-4c-4g (newer CPUs).
rjones (Tue, 29 Aug 2017 04:22:01 GMT):
I've rolled this change out for a short while to several fabric build types. The downside is there will be a price differential if we decide to go with having some of these dedicated minion types around. The number for that is not known.
rameshthoomu (Tue, 29 Aug 2017 12:41:56 GMT):
@jimthematrix CI jobs are configured for both 6.9.5 and 8.4.0 node versions.. I have triggered them manually yesterday and both are passed.. https://jenkins.hyperledger.org/view/fabric-sdk-node/
anishman (Wed, 30 Aug 2017 15:01:27 GMT):
Has joined the channel.
greg.haskins (Wed, 30 Aug 2017 20:14:00 GMT):
Has left the channel.
rjones (Mon, 04 Sep 2017 05:47:51 GMT):
There is an outage for Jenkins. I am diagnosing it right now.
rjones (Mon, 04 Sep 2017 06:11:53 GMT):
Workaround in place. Build queue is clearing.
sudeshrshetty (Tue, 05 Sep 2017 16:32:40 GMT):
Hi, fabric-verify-z verification build is failing for everyone due to error while doing
git fetch --tags --progress ssh://hyperledger-jobbuilder@gerrit.hyperledger.org:29418/fabric +refs/heads/*:refs/remotes/origin/*
with error,
15:39:17 hudson.plugins.git.GitException: Command "git fetch --tags --progress ssh://hyperledger-jobbuilder@gerrit.hyperledger.org:29418/fabric +refs/heads/*:refs/remotes/origin/*" returned status code 128:
sudeshrshetty (Tue, 05 Sep 2017 16:32:50 GMT):
Can someone look into this?
sudeshrshetty (Tue, 05 Sep 2017 16:39:45 GMT):
https://jenkins.hyperledger.org/job/fabric-verify-z/
rjones (Tue, 05 Sep 2017 17:34:35 GMT):
@sudeshrshetty I've asked @harrijk if there is a problem with the `z` nodes
sudeshrshetty (Tue, 05 Sep 2017 17:40:46 GMT):
Thanks @rjones
harrijk (Tue, 05 Sep 2017 17:50:13 GMT):
@sudeshrshetty I'm checking the systems now. I don't see anything that pops out as an issue, but I'll continue to look.
harrijk (Tue, 05 Sep 2017 18:12:10 GMT):
@sudeshrshetty It appears to be a network issue on the s390x end. I will work with our support team to resolve the issue.
sudeshrshetty (Tue, 05 Sep 2017 18:12:34 GMT):
Thanks a lot @harrijk , thanks for your time
harrijk (Tue, 05 Sep 2017 18:12:40 GMT):
anytime
jimthematrix (Wed, 06 Sep 2017 14:35:36 GMT):
@rjones @jwagantall Ry, Jessica, can I ask for a favor? when pushing the v1.0.2 tag for fabric-sdk-node, I accidentally created a v1.0.2 branch as a side effect. ```git push origin v1.0.2 HEAD:refs/heads/v1.0.2``` I've tried to removed them from gerrit and as far as I can tell they are gone, but the github mirror still displays the branch
jimthematrix (Wed, 06 Sep 2017 14:35:58 GMT):
can I ask you to help with deleting the branch v1.0.2 from github? thanks
jimthematrix (Wed, 06 Sep 2017 14:35:58 GMT):
can I ask for your help with deleting the branch v1.0.2 from github? thanks
jwagantall (Wed, 06 Sep 2017 17:21:29 GMT):
sure.l i can take care of that
kkado (Thu, 07 Sep 2017 08:45:05 GMT):
Has joined the channel.
jimthematrix (Thu, 07 Sep 2017 17:24:15 GMT):
thanks @jwagantall !
mastersingh24 (Sun, 10 Sep 2017 14:46:58 GMT):
@rameshthoomu - When you get a chance, can you check to see why fabric-baseimage 0.4.0 was not published for Z and P?
rameshthoomu (Sun, 10 Sep 2017 15:36:33 GMT):
Yesterday we had issues with docker login on 17.06 version.. I have submitted fix as per ry and Greg.. Greg has to create new release tag to publish 0.4.1
rameshthoomu (Sun, 10 Sep 2017 15:37:53 GMT):
Z and P build nodes are pointing to docker version 17.06..
mastersingh24 (Mon, 11 Sep 2017 16:40:40 GMT):
@rameshthoomu - merged and tagged 0.4.1 - I see the x86_64 image pushed but still nothing for Z and P
rameshthoomu (Mon, 11 Sep 2017 16:44:48 GMT):
I see the same error on z and p (docker 17.06.02-ce version) and x86_64 on 17.05.0-ce..
rameshthoomu (Mon, 11 Sep 2017 16:45:08 GMT):
checking why the script is still taking --email flag
rameshthoomu (Mon, 11 Sep 2017 16:47:45 GMT):
@mastersingh24 this patch https://gerrit.hyperledger.org/r/#/c/13289/ was not rebased before merge..
rameshthoomu (Mon, 11 Sep 2017 16:48:22 GMT):
I see --email flag is still exists in 0.4.1 tag..
mastersingh24 (Mon, 11 Sep 2017 17:12:37 GMT):
OK - I fixed it ;)
jimthematrix (Thu, 14 Sep 2017 12:20:03 GMT):
@jeffgarratt are you aware of the behave tests failure in the recent couple of CRs with this error:
```12:00:19 Exception ImportError: cannot import name rand
12:00:19 Traceback (most recent call last):
12:00:19 File "/w/workspace/fabric-verify-behave-x86_64/gopath/src/github.com/hyperledger/fabric/venv/bin/behave", line 11, in
jimthematrix (Thu, 14 Sep 2017 12:21:00 GMT):
for instance
https://gerrit.hyperledger.org/r/#/c/9711/
https://gerrit.hyperledger.org/r/#/c/13451/
jimthematrix (Thu, 14 Sep 2017 12:21:00 GMT):
for instance
https://gerrit.hyperledger.org/r/#/c/9711/
https://gerrit.hyperledger.org/r/#/c/13451/
https://gerrit.hyperledger.org/r/#/c/13447/
jeffgarratt (Thu, 14 Sep 2017 13:37:55 GMT):
this seems like an env issue... did the CI env chang recently?
jeffgarratt (Thu, 14 Sep 2017 13:37:55 GMT):
@jimthematrix this seems like an env issue... did the CI env chang recently?
jimthematrix (Thu, 14 Sep 2017 13:42:10 GMT):
@rameshthoomu do you know the answer to Jeff's question above?
rameshthoomu (Thu, 14 Sep 2017 13:43:00 GMT):
We have updated packer image but not related to this change.. and I see few builds succeeded on the new image..
rameshthoomu (Thu, 14 Sep 2017 13:43:19 GMT):
checking.. Will update here
rameshthoomu (Thu, 14 Sep 2017 14:40:21 GMT):
@jimthematrix @jeffgarratt submitted patch https://gerrit.hyperledger.org/r/#/c/13463/
rameshthoomu (Thu, 14 Sep 2017 14:40:29 GMT):
Will let you know once this is merged..
jimthematrix (Thu, 14 Sep 2017 15:53:35 GMT):
just got merged
rameshthoomu (Thu, 14 Sep 2017 16:17:02 GMT):
behave tests are working now..
jimthematrix (Thu, 14 Sep 2017 16:19:13 GMT):
can you take a look at this one: https://jenkins.hyperledger.org/job/fabric-verify-behave-x86_64/10779/?
jimthematrix (Thu, 14 Sep 2017 16:19:32 GMT):
@rameshthoomu I kicked it off after the above was merged
rameshthoomu (Thu, 14 Sep 2017 16:20:31 GMT):
re-triggered again..
rameshthoomu (Thu, 14 Sep 2017 16:21:12 GMT):
after merge, we have to wait for the result of the ci-merge job.. some times it takes time to CI configurations..
rameshthoomu (Thu, 14 Sep 2017 16:21:48 GMT):
will monitor this job
rameshthoomu (Thu, 14 Sep 2017 16:38:33 GMT):
done now.. It's passed..
SethiSaab (Thu, 14 Sep 2017 21:34:44 GMT):
Has joined the channel.
jimthematrix (Fri, 15 Sep 2017 14:44:28 GMT):
@rameshthoomu node.js chaincode builds still need cubertura reports to be added (the test generates that already), please let me know if there's still anything you need from the test code side
jimthematrix (Fri, 15 Sep 2017 14:45:45 GMT):
also, should add s390 builds at some point
rameshthoomu (Fri, 15 Sep 2017 15:31:18 GMT):
Yes Jim.. Working on this..
rameshthoomu (Fri, 15 Sep 2017 16:48:39 GMT):
@jimthematrix coverage report for fabric-chaincode-node is missed in verify job..
rameshthoomu (Fri, 15 Sep 2017 16:49:05 GMT):
it's implemented in merge job.. https://jenkins.hyperledger.org/view/fabric-chaincode-node/job/fabric-chaincode-node-merge-x86_64/19/cobertura/
rameshthoomu (Fri, 15 Sep 2017 16:49:18 GMT):
will submit patch now to include the same in verify job
rameshthoomu (Fri, 15 Sep 2017 17:06:55 GMT):
Will add s390x chaincode-node jobs..
rameshthoomu (Fri, 15 Sep 2017 17:07:48 GMT):
@rjones @jwagantall @harrijk `hyp-z-linuxone-24` is offline in sandbox.. Could you please make it active.. Have to run few builds on z node..
harrijk (Fri, 15 Sep 2017 17:12:18 GMT):
I don't see any jenkins java process running on -24
rameshthoomu (Fri, 15 Sep 2017 18:58:57 GMT):
@harrijk z node in sandbox is up now.
harrijk (Fri, 15 Sep 2017 20:43:02 GMT):
Thanks for the update. Have a great weekend!
yuanlv (Fri, 15 Sep 2017 21:44:20 GMT):
Has joined the channel.
mastersingh24 (Sun, 17 Sep 2017 08:31:54 GMT):
So unfortunately I missed this as part of the move to Go 1.9 for the master branch: https://jira.hyperledger.org/browse/FAB-6191
Looks like the e2e and behave both use the version of Go installed on the host to build some of the binaries for testing.
SethiSaab (Sun, 17 Sep 2017 19:04:19 GMT):
@mastersingh24 Hi
mastersingh24 (Mon, 18 Sep 2017 15:03:43 GMT):
FYI - I'm looking into this
(https://chat.hyperledger.org/channel/fabric-ci?msg=MkQBbxYTAkXobJbzg) @mastersingh24
bsmita (Tue, 19 Sep 2017 15:44:37 GMT):
Oh! ok
bsmita (Tue, 19 Sep 2017 15:45:28 GMT):
I am still looking into fabric-ca-client error, even with go 1.8.3, the testcase is failing
bsmita (Tue, 19 Sep 2017 15:45:37 GMT):
on Power
rameshthoomu (Tue, 19 Sep 2017 15:45:46 GMT):
oh ok,..
rameshthoomu (Tue, 19 Sep 2017 15:45:59 GMT):
I will check @mastersingh24 today regarding installing go 1.9 on hosts..
rameshthoomu (Tue, 19 Sep 2017 15:45:59 GMT):
I will check with @mastersingh24 today regarding installing go 1.9 on hosts..
rameshthoomu (Tue, 19 Sep 2017 15:46:22 GMT):
if say yes then we can work on enabling power nodes
bsmita (Tue, 19 Sep 2017 15:46:34 GMT):
ok...thank you
rohitadivi (Tue, 19 Sep 2017 15:57:01 GMT):
Has joined the channel.
sambhavdutt (Tue, 19 Sep 2017 16:14:14 GMT):
Has joined the channel.
mastersingh24 (Wed, 20 Sep 2017 00:19:03 GMT):
If you pull down the latest from the master branch of fabric-ca, it will now compile under Go 1.9 ( https://gerrit.hyperledger.org/r/#/c/13407/ ) (https://chat.hyperledger.org/channel/fabric-ci?msg=wcqTsi2hPM8KLSSnJ) @bsmita
rameshthoomu (Wed, 20 Sep 2017 00:35:39 GMT):
@mastersingh24 do you want me to install go 1.9 on all three platforms (x,z and p) ?
rameshthoomu (Wed, 20 Sep 2017 00:35:39 GMT):
@mastersingh24 do you want me to install go 1.9 on all three platform CI nodes (x,z and p) ?
Jacky_Sheng (Wed, 20 Sep 2017 03:20:19 GMT):
Has joined the channel.
mastersingh24 (Wed, 20 Sep 2017 09:13:19 GMT):
@rameshthoomu - It's a bit more complicated than that. We actually need both Go 1.9 and Go 1.7.5 installed since v1.0.x (current release branch) won't compile with Go 1.9.
jtclark (Wed, 20 Sep 2017 13:14:45 GMT):
Good morning
mastersingh24 (Wed, 20 Sep 2017 13:28:46 GMT):
morning ;)
troyronda (Wed, 20 Sep 2017 13:50:14 GMT):
Ah - I was about to also ask about Go 1.9 on the CI :)
troyronda (Wed, 20 Sep 2017 13:50:57 GMT):
(for Go SDK)
yacovm (Sat, 23 Sep 2017 22:57:30 GMT):
@rameshthoomu what is `fabric-verify-two-staged-ci-check-x86_64` ?
rameshthoomu (Sat, 23 Sep 2017 23:00:02 GMT):
It's a test job planning to run unit tests based on changes submitted in the oatch
rameshthoomu (Sat, 23 Sep 2017 23:00:46 GMT):
We skip result of this job and ignore voting on gerrit patch set..
SethiSaab (Sun, 24 Sep 2017 14:15:30 GMT):
Hi Team i am getting error while registering a user .....when i run this command fabric-ca-client register --id.name admin2 --id.affiliation org1.department1 --id.attrs 'hf.Revoker=true,admin=true:ecert' i get the following error ..............7/09/24 07:12:46 [DEBUG] Directing traffic to default CA
2017/09/24 07:12:46 [DEBUG] Checking for revocation/expiration of certificate owned by 'admin'
2017/09/24 07:12:46 [DEBUG] DB: Get certificate by serial (8247494153b0aec633674b90a34d97e066ba3bb) and aki (1e94125663d537fb926ba373a2ab9ba321c2ec34)
2017/09/24 07:12:46 [ERROR] No certificates found for provided serial and aki
jimthematrix (Mon, 25 Sep 2017 00:52:06 GMT):
@rameshthoomu https://gerrit.hyperledger.org/r/#/c/13721/ didn't get published to docker hub despite `IS_RELEASE=true`?
rameshthoomu (Mon, 25 Sep 2017 01:16:16 GMT):
Some one has to create a release tag to publish images to docker hub..
jimthematrix (Mon, 25 Sep 2017 01:55:53 GMT):
ok thanks, just pushed v0.4.2
rameshthoomu (Mon, 25 Sep 2017 02:42:30 GMT):
@jimthematrix it's done now.. https://hub.docker.com/r/hyperledger/fabric-baseimage/tags/
GiorgiBlockchain (Tue, 26 Sep 2017 06:06:21 GMT):
Has joined the channel.
GiorgiBlockchain (Tue, 26 Sep 2017 06:16:20 GMT):
Hello everyone, I have some issue while interacting with fabric. Not sure if it's the right chat to ask this question if not my apologize and ignore my message. So I'm testing the balance-transfer example on ubuntu machine. I docerized node.js API in order to interact with fabric from remote app. Then I have exposed port 4000 on node.js and made a bridge with outside port to access the server. Yesterday I could execute sample REST API requests (https://github.com/hyperledger/fabric-samples/tree/master/balance-transfer#sample-rest-apis-requests) locally from command line. For example I could register/enroll user in the network, create a channel, etc. However with the Postman tool I was getting errors like: Error: Enrollment failed; ECONNREFUSED localhost:8054, ECONNREFUSED localhost:7054, port number depends on what user token I was using for the request. "Error: This client instance must be assigned a user context." That is my first problem.
The second problem came today. Node.js uses JWS tokens for secure authentication and jwt token was expired after 10 hours and it is normal since it is configured that way (https://github.com/hyperledger/fabric-samples/blob/master/balance-transfer/config.json). But what I couldn't understand is that I even can not authenticate a new user from localhost with cli. For instance, this login request doesn't return anything, it's not executing: curl -s -X POST http://localhost:4000/users -H "content-type: application/x-www-form-urlencoded" -d 'username=Jim&orgName=org1'
If any of you already faced the same issue please guide me. Thank you in advance!
kostas (Tue, 26 Sep 2017 13:40:09 GMT):
@GiorgiBlockchain: This is not the right forum. Try #fabric-sdk-node ?
kostas (Tue, 26 Sep 2017 13:49:48 GMT):
Does my memory serve me wrong, or did we use to have the Hyperledger Jobbuilder post links to the CI merge jobs on every changeset after it was merged?
kostas (Tue, 26 Sep 2017 13:52:26 GMT):
On a related note, what's the quickest way to check the status of the CI merge tasks for a given changeset? (Browse manually via this page https://jenkins.hyperledger.org/view/fabric/ is how I do it, but I'm sure I'm missing a more obvious way to do this.)
rameshthoomu (Tue, 26 Sep 2017 14:23:31 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=ueKb8Strkn5BJAW8Y) @kostas :: see this.. [ ](https://chat.hyperledger.org/channel/ci-pipeline?msg=dBqRrmsnjaWZ5sqa5) @rjones
GiorgiBlockchain (Wed, 27 Sep 2017 00:34:32 GMT):
@kostas Alright will try. Thanks!
tiennv (Wed, 27 Sep 2017 12:43:40 GMT):
Has joined the channel.
troyronda (Wed, 27 Sep 2017 13:31:40 GMT):
@rameshthoomu @mastersingh24 hey guys - just checking in on the status of Go 1.9 for CI
mastersingh24 (Wed, 27 Sep 2017 13:32:45 GMT):
@troyronda - it's complicated for the e2e and behave
mastersingh24 (Wed, 27 Sep 2017 13:32:53 GMT):
I'm working on a couple of options
mastersingh24 (Wed, 27 Sep 2017 13:33:05 GMT):
For the verify on Z and x86, we are good to go
troyronda (Wed, 27 Sep 2017 13:35:52 GMT):
Nice - do you know how I would adjust the Go SDK build to switch over to 1.9?
mastersingh24 (Wed, 27 Sep 2017 13:47:23 GMT):
I'll try to take a look at the CI jobs for the Go SDK
mastersingh24 (Wed, 27 Sep 2017 13:47:38 GMT):
If using Docker for the testenv, then it's a no brainer
mastersingh24 (Wed, 27 Sep 2017 13:48:00 GMT):
But if using the Go version installed on the CI hosts, therein lies the rub
mastersingh24 (Wed, 27 Sep 2017 13:48:02 GMT):
;)
mastersingh24 (Wed, 27 Sep 2017 13:48:26 GMT):
Although I think we can more easily deal with the GO SDK since I assume you no longer care about Go 1.7.5?
mastersingh24 (Wed, 27 Sep 2017 13:48:36 GMT):
Whereas for Fabric 1.0.x we still need 1.7.5
troyronda (Wed, 27 Sep 2017 13:52:33 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=3Lh48Sf5Muaxek7Hz) yup - don't care about 1.7.5
mastersingh24 (Wed, 27 Sep 2017 13:52:43 GMT):
Lucky dog
mastersingh24 (Wed, 27 Sep 2017 13:52:46 GMT):
;)
troyronda (Wed, 27 Sep 2017 13:52:51 GMT):
ha.
mastersingh24 (Wed, 27 Sep 2017 13:53:13 GMT):
OK - I think I can likely push an initial CR to CI that can help
troyronda (Wed, 27 Sep 2017 13:53:27 GMT):
(My belief is that 1.7.x is old enough that it's not relevant for an SDK)
mastersingh24 (Wed, 27 Sep 2017 13:53:52 GMT):
Fine by me
troyronda (Wed, 27 Sep 2017 13:55:12 GMT):
Will probably have to write up some policy in the README about supporting current-X versions of Go...
troyronda (Wed, 27 Sep 2017 14:00:29 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=BWoshF9PcAjKJQ33z) Awesome thanks (if you don't have cycles, then any hints/pointers would help too).
mastersingh24 (Wed, 27 Sep 2017 14:01:14 GMT):
I pretty much did what you need (I think) - need to go look at my local changeset
rjones (Wed, 27 Sep 2017 17:20:42 GMT):
There will be a short Hyperledger hosted services outage this weekend to apply OS updates. https://lists.hyperledger.org/pipermail/hyperledger-tsc/2017-September/001125.html
jimthematrix (Mon, 02 Oct 2017 18:22:05 GMT):
@rameshthoomu s390 build for node.js chaincode failed https://logs.hyperledger.org/production/vex-yul-hyp-jenkins-1/fabric-chaincode-node-verify-s390x/4/console-timestamp.log.gz with the following error:
```18:53:05 [14:52:55] Starting 'clean-up'...
18:53:05 [14:52:55] 'clean-up' errored after 540 ��s
18:53:05 [14:52:55] Error: EACCES: permission denied, rmdir '/tmp/fabric-shim/chaincode/hyperledger/fabric'
18:53:05 at Object.fs.rmdirSync (fs.js:852:18)
18:53:05 at rmdirSync (/w/workspace/fabric-chaincode-node-verify-s390x/gopath/src/github.com/hyperledger/fabric-chaincode-node/node_modules/fs-extra/lib/remove/rimraf.js:276:13)
18:53:05 at rimrafSync (/w/workspace/fabric-chaincode-node-verify-s390x/gopath/src/github.com/hyperledger/fabric-chaincode-node/node_modules/fs-extra/lib/remove/rimraf.js:252:7)
18:53:05 at options.readdirSync.forEach.f (/w/workspace/fabric-chaincode-node-verify-s390x/gopath/src/github.com/hyperledger/fabric-chaincode-node/node_modules/fs-extra/lib/remove/rimraf.js:291:39)
18:53:05 at Array.forEach (
jimthematrix (Mon, 02 Oct 2017 18:22:05 GMT):
@rameshthoomu @harrijk s390 build for node.js chaincode failed https://logs.hyperledger.org/production/vex-yul-hyp-jenkins-1/fabric-chaincode-node-verify-s390x/4/console-timestamp.log.gz with the following error:
```18:53:05 [14:52:55] Starting 'clean-up'...
18:53:05 [14:52:55] 'clean-up' errored after 540 ��s
18:53:05 [14:52:55] Error: EACCES: permission denied, rmdir '/tmp/fabric-shim/chaincode/hyperledger/fabric'
18:53:05 at Object.fs.rmdirSync (fs.js:852:18)
18:53:05 at rmdirSync (/w/workspace/fabric-chaincode-node-verify-s390x/gopath/src/github.com/hyperledger/fabric-chaincode-node/node_modules/fs-extra/lib/remove/rimraf.js:276:13)
18:53:05 at rimrafSync (/w/workspace/fabric-chaincode-node-verify-s390x/gopath/src/github.com/hyperledger/fabric-chaincode-node/node_modules/fs-extra/lib/remove/rimraf.js:252:7)
18:53:05 at options.readdirSync.forEach.f (/w/workspace/fabric-chaincode-node-verify-s390x/gopath/src/github.com/hyperledger/fabric-chaincode-node/node_modules/fs-extra/lib/remove/rimraf.js:291:39)
18:53:05 at Array.forEach (
jimthematrix (Mon, 02 Oct 2017 18:22:48 GMT):
can you advise what seems to be the issue?
rameshthoomu (Mon, 02 Oct 2017 18:24:56 GMT):
@harrijk fixed this issue last friday
harrijk (Mon, 02 Oct 2017 18:26:12 GMT):
@rameshthoomu @jimthematrix let me ensure that the cleanup script is indeed removing the /tmp/fabric-shim/* dirs
harrijk (Mon, 02 Oct 2017 18:32:32 GMT):
It looks like after I updated the script last Fri. the job listed above was re-run without error. https://logs.hyperledger.org/production/vex-yul-hyp-jenkins-1/fabric-chaincode-node-verify-s390x/5/console-timestamp.log.gz
mastersingh24 (Tue, 03 Oct 2017 11:37:48 GMT):
@rameshthoomu - https://gerrit.hyperledger.org/r/#/c/14145/
mastersingh24 (Tue, 03 Oct 2017 14:37:51 GMT):
@rameshthoomu - https://jenkins.hyperledger.org/view/fabric-app/job/fabric-app-image-release-docker-x86_64/lastBuild/console
For some reason, pushing the x86_64 images fails due to `denied: requested access to the resource is denied`
But the ppc64le and s390x push just fine
rameshthoomu (Tue, 03 Oct 2017 14:38:07 GMT):
checking
mastersingh24 (Tue, 03 Oct 2017 14:38:33 GMT):
thx
rjones (Tue, 03 Oct 2017 15:03:59 GMT):
@rameshthoomu is https://gerrit.hyperledger.org/r/#/c/14153/ ready to merge?
rameshthoomu (Tue, 03 Oct 2017 15:04:26 GMT):
yes.. @rjones
rameshthoomu (Tue, 03 Oct 2017 15:05:21 GMT):
While pushing images from release jobs, seeing this error on x86_64 nodes..
`denied: requested access to the resource is denied`
rjones (Tue, 03 Oct 2017 15:05:38 GMT):
I assume this fixes it?
rjones (Tue, 03 Oct 2017 15:06:26 GMT):
I mean, they're all using the same credentials, if it was a credential issue, they should all fail
rameshthoomu (Tue, 03 Oct 2017 15:06:50 GMT):
yes
rameshthoomu (Tue, 03 Oct 2017 15:07:17 GMT):
will re-run after merge #14153 patch.
rjones (Tue, 03 Oct 2017 15:10:11 GMT):
merge failed due to gateway timeout, re-merging 153
rameshthoomu (Tue, 03 Oct 2017 15:14:53 GMT):
ok
rjones (Tue, 03 Oct 2017 15:15:39 GMT):
the next build made it. the logs haven't published yet, but the jobs are re-jiggered. which job do I need to retrigger (or are you retriggering it?)
rameshthoomu (Tue, 03 Oct 2017 15:17:16 GMT):
I re-triggered x86_64 release job
rameshthoomu (Tue, 03 Oct 2017 15:32:11 GMT):
@mastersingh24 - x86_64 images are now pushed to docker hub..
rameshthoomu (Tue, 03 Oct 2017 15:32:15 GMT):
https://hub.docker.com/r/hyperledger/fabric-peer/tags/
jyellick (Tue, 03 Oct 2017 16:00:40 GMT):
@rameshthoomu @rjones I'm seeing odd new aborted jobs in many of my CRs, like:
> https://jenkins.hyperledger.org/job/fabric-verify-two-staged-ci-check-x86_64/300/ : ABORTED
> No problems were identified. If you know why this problem occurred, please add a suitable Cause for it. ( https://jenkins.hyperledger.org/job/fabric-verify-two-staged-ci-check-x86_64/300/ )
> https://jenkins.hyperledger.org/job/fabric-verify-behave-x86_64/11539/ : ABORTED
> No problems were identified. If you know why this problem occurred, please add a suitable Cause for it. ( https://jenkins.hyperledger.org/job/fabric-verify-behave-x86_64/11539/ )
Any idea what that's about?
rameshthoomu (Tue, 03 Oct 2017 16:01:38 GMT):
@jyellick checking this
rjones (Tue, 03 Oct 2017 16:03:39 GMT):
@jyellick did you upload a new patch? that will abort in-progress jobs
jyellick (Tue, 03 Oct 2017 16:04:41 GMT):
I did, but for instance `fabric-verify-two-staged-ci-check` is a job I have not seen before, maybe this was just added and I did not notice?
jyellick (Tue, 03 Oct 2017 16:05:05 GMT):
(And the other jobs are returning `SUCCESS` )
rjones (Tue, 03 Oct 2017 16:05:56 GMT):
it was just added. If your other jobs completed before the new patch, they will return SUCCESS and the ones in progress will (should) return ABORT
rjones (Tue, 03 Oct 2017 16:06:08 GMT):
(SUCCESS or FAIL as appropriate)
rjones (Tue, 03 Oct 2017 16:08:10 GMT):
@rameshthoomu @jyellick I retriggered that specific job. Not sure why it aborted
jyellick (Tue, 03 Oct 2017 16:09:13 GMT):
What is the new 'rebuild' command for this new CI job?
rjones (Tue, 03 Oct 2017 16:11:56 GMT):
for e2e? there might not be one, I didn't add it
rameshthoomu (Tue, 03 Oct 2017 16:12:14 GMT):
@jyellick we are skipping the result of this new job.. I don't see an option to skip the abort failure..
rjones (Tue, 03 Oct 2017 16:13:06 GMT):
we have other jobs without voting rights, I'd take a look at how they work. I know the -p verify jobs had no voting rights for a while, for instance
sudheesh001 (Wed, 04 Oct 2017 06:39:06 GMT):
Has joined the channel.
jamesgua (Wed, 04 Oct 2017 15:19:35 GMT):
Has joined the channel.
Menniti (Thu, 05 Oct 2017 12:31:30 GMT):
Has joined the channel.
jimthematrix (Thu, 05 Oct 2017 16:02:37 GMT):
@rameshthoomu hi Ramesh, I re-opened https://jira.hyperledger.org/browse/FAB-5444 for the last piece of the CI work on publishing the API Reference web site generated from `gulp docs` (once https://gerrit.hyperledger.org/r/#/c/14231/ is merged), please let me know if you have any questions
jimthematrix (Thu, 05 Oct 2017 16:02:40 GMT):
thanks!
jimthematrix (Thu, 05 Oct 2017 20:25:08 GMT):
https://gerrit.hyperledger.org/r/#/c/14231/ has been merged
jimthematrix (Thu, 05 Oct 2017 20:25:15 GMT):
@rameshthoomu ^^^
rameshthoomu (Thu, 05 Oct 2017 20:25:42 GMT):
ok.. I have created fabric-shim.github.io..
rameshthoomu (Thu, 05 Oct 2017 20:26:04 GMT):
Will update merge job
rameshthoomu (Thu, 05 Oct 2017 20:26:04 GMT):
Will update merge job and push for every merge job..
rameshthoomu (Fri, 06 Oct 2017 01:57:08 GMT):
Hi @jimthematrix we have incorporated above changes in CI.. We see merge job is failing while triggering `gulp doc` from chaincode-node directory
```
00:27:06.827 [00:12:14] Using gulpfile /w/workspace/fabric-chaincode-node-merge-x86_64/gopath/src/github.com/hyperledger/fabric-chaincode-node/gulpfile.js
00:27:06.828 [00:12:14] Task 'doc' is not in your gulpfile
00:27:06.829 [00:12:14] Please check the documentation for proper gulpfile formatting
00:27:06.840 Build step 'Execute shell' marked build as failure
```
rameshthoomu (Fri, 06 Oct 2017 01:57:21 GMT):
do we have gulp doc task available in .js file?
rameshthoomu (Fri, 06 Oct 2017 01:57:39 GMT):
or am I referring wrong directory to trigger the `gulp doc`
rameshthoomu (Fri, 06 Oct 2017 02:01:54 GMT):
oops.. Missed configured job with `gulp doc` instead of `gulp docs`
rameshthoomu (Fri, 06 Oct 2017 02:01:54 GMT):
oops.. Miss configured job with `gulp doc` instead of `gulp docs`
dave.enyeart (Mon, 09 Oct 2017 15:26:21 GMT):
@rameshthoomu any ideas why this one keeps failing CI? https://gerrit.hyperledger.org/r/#/c/12913/
rameshthoomu (Mon, 09 Oct 2017 15:28:41 GMT):
@dave.enyeart rebase should work
rameshthoomu (Mon, 09 Oct 2017 15:29:45 GMT):
a week back ci.properties file change merged in master branch.. Seems this patch is missing this change..
dave.enyeart (Mon, 09 Oct 2017 15:38:04 GMT):
thanks @rameshthoomu , will do
rameshthoomu (Mon, 09 Oct 2017 19:51:28 GMT):
@MartinC made couple of changes to fabric-sdk-rest CI jobs.. your patch is now good go https://gerrit.hyperledger.org/r/#/c/14111/
MartinC (Mon, 09 Oct 2017 19:51:28 GMT):
Has joined the channel.
jimthematrix (Wed, 11 Oct 2017 03:26:27 GMT):
@jwagantall @rjones can I ask for a quick favor, I'm trying to find who are the maintainers of the fabric-chaincode-java project, I know @sanchezl is one, who else?
sanchezl (Wed, 11 Oct 2017 03:26:50 GMT):
@muralisr
jimthematrix (Wed, 11 Oct 2017 03:28:26 GMT):
I think we need at least one more maintainer, otherwise merging CRs could take a long time if Murali is the only other maintainer
jimthematrix (Wed, 11 Oct 2017 03:28:26 GMT):
I think we need at least one more maintainer, otherwise merging your CRs could take a long time if Murali is the only other maintainer
jimthematrix (Wed, 11 Oct 2017 03:28:43 GMT):
can you nominate someone please?
sanchezl (Wed, 11 Oct 2017 03:29:24 GMT):
Sure, what's the appropriate forum for that?
rjones (Wed, 11 Oct 2017 03:30:39 GMT):
Message Attachments
jimthematrix (Wed, 11 Oct 2017 03:31:55 GMT):
@rjones thanks, wow I didn't know ;-) can I ask you to replace "jimthematrix@gmail.com" with "jim_the_matrix@hotmail.com"?
jimthematrix (Wed, 11 Oct 2017 03:32:27 GMT):
(btw I had to ask Jessica to do that same change for fabric-chaincode-node project, sorry about my mistake giving you guys the wrong username)
rjones (Wed, 11 Oct 2017 03:32:57 GMT):
usually there would be something in here: https://github.com/hyperledger/fabric-chaincode-java that had a MAINTAINERS.md file, which people would then modify and have the other maintainers vote on
sanchezl (Wed, 11 Oct 2017 03:33:35 GMT):
Jim, i can create the file, and you an Murali can vote on it ?
rjones (Wed, 11 Oct 2017 03:33:54 GMT):
slow down a second
rjones (Wed, 11 Oct 2017 03:34:05 GMT):
I want to steer you the right way
jimthematrix (Wed, 11 Oct 2017 03:34:32 GMT):
yes please Ry
rjones (Wed, 11 Oct 2017 03:36:25 GMT):
@jimthematrix your invite was just sent, please accept it (should be in your email)
rjones (Wed, 11 Oct 2017 03:37:03 GMT):
I just removed your gmail account from the group
jimthematrix (Wed, 11 Oct 2017 03:43:07 GMT):
thanks, but I have to ask you to send the invite again, I accepted your earlier one but signed in with the wrong account (I'm so embarrassed :pensive: )
rjones (Wed, 11 Oct 2017 03:43:33 GMT):
should I disable the other account or do you use it for something?
jimthematrix (Wed, 11 Oct 2017 03:43:54 GMT):
yes please, that'll make things so much better
rjones (Wed, 11 Oct 2017 03:44:15 GMT):
invite sent
jimthematrix (Wed, 11 Oct 2017 03:44:21 GMT):
(yes please disable jimthematrix@gmail.com)
jimthematrix (Wed, 11 Oct 2017 03:44:27 GMT):
cool
jimthematrix (Wed, 11 Oct 2017 03:45:54 GMT):
I'm all set! thanks Ry!
rjones (Wed, 11 Oct 2017 03:46:40 GMT):
@sanchezl what is your github alias and public email
rjones (Wed, 11 Oct 2017 03:47:15 GMT):
should I use your IBM address? I have `sanchezl@us.ibm.com`
rjones (Wed, 11 Oct 2017 03:48:26 GMT):
looks like `sanchezl` is your GitHub alias
sanchezl (Wed, 11 Oct 2017 03:48:36 GMT):
Correct on both counts.
sanchezl (Wed, 11 Oct 2017 03:48:36 GMT):
Correct/yes on both counts.
rjones (Wed, 11 Oct 2017 03:50:35 GMT):
https://gerrit.hyperledger.org/r/#/c/14401/ for your approval
rjones (Wed, 11 Oct 2017 03:51:04 GMT):
merge that, then propose changes as you wish. I stole that file from fabric/docs/source/...
rjones (Wed, 11 Oct 2017 03:51:19 GMT):
(merge that if it is correct)
rjones (Wed, 11 Oct 2017 03:52:41 GMT):
Once your team votes in new members, please tell @jwagantall and me (or add us to the code reviews for this file) and we'll update LDAP after the merge
rjones (Wed, 11 Oct 2017 03:56:19 GMT):
@jimthematrix I have disabled the gmail account and removed it from the two groups it was in
rjones (Wed, 11 Oct 2017 04:20:10 GMT):
thank you for humoring me, @sanchezl
rjones (Wed, 11 Oct 2017 04:20:41 GMT):
I submitted https://gerrit.hyperledger.org/r/#/c/14403/ as well
sanchezl (Wed, 11 Oct 2017 04:22:14 GMT):
Thanks @rjones
rjones (Wed, 11 Oct 2017 04:25:40 GMT):
thank you, @sanchezl
rjones (Wed, 11 Oct 2017 04:25:43 GMT):
also: https://github.com/hyperledger/fabric-chaincode-java/blob/master/MAINTAINERS.rst
rjones (Wed, 11 Oct 2017 04:26:13 GMT):
(I just like the way GitHub renders that for free)
jyellick (Wed, 11 Oct 2017 04:29:08 GMT):
@rameshthoomu Looks like the fabric-e2e builds are having problems, anyone https://jenkins.hyperledger.org/job/fabric-verify-end-2-end-x86_64/buildTimeTrend
jyellick (Wed, 11 Oct 2017 04:29:08 GMT):
@rameshthoomu (or anyone) Looks like the fabric-e2e builds are having problems, https://jenkins.hyperledger.org/job/fabric-verify-end-2-end-x86_64/buildTimeTrend
rameshthoomu (Wed, 11 Oct 2017 09:35:43 GMT):
Yes I see consistent Java Test failures.. @rickr could you pls verify
rameshthoomu (Wed, 11 Oct 2017 10:23:08 GMT):
@rickr FAB-6575
rameshthoomu (Wed, 11 Oct 2017 12:11:20 GMT):
@mastersingh24 @rickr @jyellick master is broken. I see all builds are failing with FAB-6575
boliang (Wed, 11 Oct 2017 13:05:12 GMT):
Has joined the channel.
boliang (Wed, 11 Oct 2017 13:05:39 GMT):
Hey, there are some wear problems in jenkins servers. The console log says "Makefile:79: *** "No go in PATH: Check dependencies". Stop.". It seems that the environment is not properly set up. Details refer to: https://logs.hyperledger.org/production/vex-yul-hyp-jenkins-1/fabric-verify-end-2-end-x86_64/9451/console.log.gz
rameshthoomu (Wed, 11 Oct 2017 13:09:00 GMT):
@boliang you have to rebase your patch..
rameshthoomu (Wed, 11 Oct 2017 13:09:29 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=e6t2Mm6HvpKKbHeKT) @rameshthoomu
boliang (Wed, 11 Oct 2017 13:10:17 GMT):
OK~ Will try it
jimthematrix (Wed, 11 Oct 2017 23:56:41 GMT):
@rameshthoomu fabric-chaincode-node verify s390 builds are failing with the following error:
```Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-dbKBkJ/cryptography/
jimthematrix (Wed, 11 Oct 2017 23:56:54 GMT):
https://jenkins.hyperledger.org/job/fabric-chaincode-node-verify-s390x/14/
rameshthoomu (Thu, 12 Oct 2017 00:10:30 GMT):
Yes.. we are aware of this issue.. we have been discussing about this in #ci-pipeline
mastersingh24 (Thu, 12 Oct 2017 11:45:47 GMT):
e2e is broken now with the re-ordering of the tests
mastersingh24 (Thu, 12 Oct 2017 11:46:03 GMT):
The Node tests are not properly shutting down / deleting the containers
rameshthoomu (Thu, 12 Oct 2017 12:59:32 GMT):
@mastersingh24 can you please give me the build reference..
mastersingh24 (Thu, 12 Oct 2017 13:00:01 GMT):
look at any of the latest - they are all failing for the same reason
mastersingh24 (Thu, 12 Oct 2017 13:00:44 GMT):
https://jenkins.hyperledger.org/job/fabric-verify-end-2-end-x86_64/9492/
rameshthoomu (Thu, 12 Oct 2017 14:02:29 GMT):
@mastersingh24 this has been fixed and tested in sandbox.. Waiting for merge
mastersingh24 (Thu, 12 Oct 2017 14:04:46 GMT):
;)
mastersingh24 (Thu, 12 Oct 2017 14:05:38 GMT):
You are a machine @rameshthoomu and thanks @rjones for the quick merge ;)
kostas (Thu, 12 Oct 2017 14:32:26 GMT):
From DigitalOcean's [write-up on their monorepo structure](https://blog.digitalocean.com/cthulhu-organizing-go-code-in-a-scalable-repo/) yesterday, something to keep an eye out on in order to speed up our CI process:
kostas (Thu, 12 Oct 2017 14:32:31 GMT):
> `gta` inspects the git history to determine which files changed between master and a feature branch, and uses this information to determine which packages must be tested for a given build (including packages that import the changed package).
kostas (Thu, 12 Oct 2017 14:32:34 GMT):
Apparently, the tool is not open-sourced yet, but [it might be soon](https://www.reddit.com/r/golang/comments/75pm12/cthulhu_organizing_go_code_in_a_scalable_repo/do80hp3/).
rameshthoomu (Thu, 12 Oct 2017 19:03:12 GMT):
@harsha @bsmita I see below unit-test is failing on power (ppc64le) build nodes (testing in sandbox)
```
unit-tests_1 | --- FAIL: TestLoadAuthPlugin (0.05s)
Error Trace: registry_plugin_test.go:41
unit-tesError:| Received unexpected error "exit status 1"
unit-tesMessages: Could not build plugin: -buildmode=plugin not supported on linux/ppc64le
```
rameshthoomu (Thu, 12 Oct 2017 19:03:53 GMT):
Did you see the same error on local machine? if yes, will ask @divyank to look into this..
harsha (Thu, 12 Oct 2017 19:05:55 GMT):
@rameshthoomu I tried reproducing the above on my local machine and looks like this is coming from
https://github.com/hyperledger/fabric/blob/master/core/handlers/library/registry_plugin_test.go#L61 & #L38
rameshthoomu (Thu, 12 Oct 2017 19:07:51 GMT):
yes I see the same file. this change was submitted by @divyank.. Seems this plugin build mode is not supported on power arch..
rameshthoomu (Thu, 12 Oct 2017 19:08:13 GMT):
we need his inputs on this..
bsmita (Thu, 12 Oct 2017 19:56:12 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=EAPLuyyHsGyHG7bCj) @rameshthoomu Yes I saw the same error when I tried today
divyank (Fri, 13 Oct 2017 00:43:40 GMT):
Hi @rameshthoomu, I'm looking into this. Will add build flags to exclude the test on ppc64le if required.
divyank (Fri, 13 Oct 2017 01:07:24 GMT):
ppc64le - Go plugin support isn't coming until 1.10: https://github.com/golang/go/issues/20756
I'll add the build flags
divyank (Fri, 13 Oct 2017 01:36:30 GMT):
Please retest with https://gerrit.hyperledger.org/r/c/14491/
boliang (Fri, 13 Oct 2017 01:38:48 GMT):
Anyone knows these failures in fabric-verify-end-2-end-x86_64?
`Failed tests:
End2endAndBackAgainIT.setup:183 UserContext for user peerOrg1Admin has no enrollment set.
End2endIT.setup:231 Url:https://localhost:7054, Failed to get info
UpdateChannelIT.setup:219 UserContext for user peerOrg1Admin has no enrollment set.`
boliang (Fri, 13 Oct 2017 01:38:48 GMT):
Anyone knows these failures in fabric-verify-end-2-end-x86_64?
```
Failed tests:
End2endAndBackAgainIT.setup:183 UserContext for user peerOrg1Admin has no enrollment set.
End2endIT.setup:231 Url:https://localhost:7054, Failed to get info
UpdateChannelIT.setup:219 UserContext for user peerOrg1Admin has no enrollment set.
```
boliang (Fri, 13 Oct 2017 01:38:48 GMT):
Anyone knows these failures in fabric-verify-end-2-end-x86_64? Details refer to https://logs.hyperledger.org/production/vex-yul-hyp-jenkins-1/fabric-verify-end-2-end-x86_64/9513/console.log.gz
```Failed tests:
End2endAndBackAgainIT.setup:183 UserContext for user peerOrg1Admin has no enrollment set.
End2endIT.setup:231 Url:https://localhost:7054, Failed to get info
UpdateChannelIT.setup:219 UserContext for user peerOrg1Admin has no enrollment set.
```
rameshthoomu (Fri, 13 Oct 2017 01:46:08 GMT):
@boliang please re-trigger now..This has been fixed today after noon..
boliang (Fri, 13 Oct 2017 01:47:38 GMT):
@rameshthoomu Sure. A lot of failures last day frustrated me.
rameshthoomu (Fri, 13 Oct 2017 01:48:47 GMT):
yes.. builds are stable now.. Please report here if you see any error..
boliang (Fri, 13 Oct 2017 01:48:52 GMT):
BTW, do you know how to trigger the testing without submitting new code patch?
rameshthoomu (Fri, 13 Oct 2017 01:49:04 GMT):
`rebuild-e2e`
rameshthoomu (Fri, 13 Oct 2017 01:49:44 GMT):
like murali did today morning on your patch..
boliang (Fri, 13 Oct 2017 01:51:06 GMT):
where should I input this command?
rameshthoomu (Fri, 13 Oct 2017 01:52:32 GMT):
click on `reply` and add `rebuild-e2e` then `post`
rameshthoomu (Fri, 13 Oct 2017 01:52:52 GMT):
like adding a comment to the patch...
boliang (Fri, 13 Oct 2017 01:53:08 GMT):
I see! Thanks a lot!
rameshthoomu (Fri, 13 Oct 2017 01:53:58 GMT):
that's it.. it's triggered now..
rameshthoomu (Fri, 13 Oct 2017 01:54:28 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=Q3bANjPRg8sZw2kPh) @divyank sure will test this and let you know..
rameshthoomu (Fri, 13 Oct 2017 01:54:34 GMT):
thanks for the quick fix..
rameshthoomu (Fri, 13 Oct 2017 03:14:37 GMT):
@divyank @bsmita @harsha unit-tests are working as expected on power node with this fix https://gerrit.hyperledger.org/r/c/14491
rameshthoomu (Fri, 13 Oct 2017 03:14:42 GMT):
https://jenkins.hyperledger.org/sandbox/job/fabric-verify-power-ppc64le/24/consoleFull
bsmita (Fri, 13 Oct 2017 03:15:20 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=mRhqCXmFC2PrFfsKn) @rameshthoomu and @divyank - thank you for the quick fix
rameshthoomu (Fri, 13 Oct 2017 03:15:35 GMT):
overall build time I see is 57 mins..
rameshthoomu (Fri, 13 Oct 2017 03:15:55 GMT):
this is a great improvement.. could be with go1.9
rameshthoomu (Fri, 13 Oct 2017 03:15:55 GMT):
this is a great improvement.. could be with go1.9 and optimized power nodes
bsmita (Fri, 13 Oct 2017 03:16:45 GMT):
Yes with go 1.9 we see good build times
rameshthoomu (Fri, 13 Oct 2017 03:18:08 GMT):
@bsmita once above patch is merged, will run unit-tests all power nodes couple of more times and will initiate discussion with Maintainers on bringing power nodes back into action
bsmita (Fri, 13 Oct 2017 03:18:48 GMT):
Sounds good, please let me know when you are ready to test, I will make sure the go 1.9 paths are set correctly
rameshthoomu (Fri, 13 Oct 2017 03:19:23 GMT):
sure.. when ever you have time update go1.9 on all power nodes.. same like 06 node..
rameshthoomu (Fri, 13 Oct 2017 03:19:27 GMT):
in sandbox
bsmita (Fri, 13 Oct 2017 03:19:36 GMT):
OK, will do it tomorrow morning
rameshthoomu (Fri, 13 Oct 2017 03:20:22 GMT):
sure.. thank you
rameshthoomu (Fri, 13 Oct 2017 05:05:28 GMT):
@sanchezl Testsummary report is now available in fabric-chaincode-java verify and merge jobs..
rameshthoomu (Fri, 13 Oct 2017 05:05:31 GMT):
https://jenkins.hyperledger.org/view/fabric-chaincode-java/job/fabric-chaincode-java-verify-x86_64/
bsmita (Fri, 13 Oct 2017 14:32:57 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=gPZwsT7aPfswkERCa) @rameshthoomu Harsha updated the go 1.9 paths on all Power nodes, please kick off builds when you have time
rameshthoomu (Fri, 13 Oct 2017 14:33:39 GMT):
sure thanks
dave.enyeart (Sat, 14 Oct 2017 14:40:08 GMT):
@rameshthoomu A lot of CI failures today, only z is passing. For example look at https://gerrit.hyperledger.org/r/#/c/14195/
dave.enyeart (Sat, 14 Oct 2017 14:40:08 GMT):
@rameshthoomu @rjones A lot of CI failures today, only z is passing. For example look at https://gerrit.hyperledger.org/r/#/c/14195/
rjones (Sat, 14 Oct 2017 14:47:43 GMT):
@dave.enyeart looks like timeouts reaching dockerhub
rjones (Sat, 14 Oct 2017 14:56:02 GMT):
@dave.enyeart our service provider had trouble with the service provider they buy bandwidth from, it's fixed now, I'll retrigger builds
yacovm (Sat, 14 Oct 2017 19:04:58 GMT):
@rjones can you perhaps retrigger again? it still fails... the verify column in gerrit is a sea of red :)
rjones (Sat, 14 Oct 2017 19:06:52 GMT):
on it
rjones (Sat, 14 Oct 2017 19:08:19 GMT):
what's interesting is not every build is failing
rjones (Sat, 14 Oct 2017 19:10:34 GMT):
@yacovm the failures here appear to be legit unit test failures: https://gerrit.hyperledger.org/r/#/c/14513/ for instance
rjones (Sat, 14 Oct 2017 19:12:49 GMT):
I will go through and restart builds that look like network issues caused to fail, but the ones that fail unit tests should be fixed
yacovm (Sat, 14 Oct 2017 19:16:08 GMT):
oh that one isn't mine...
> I will go through and restart builds that look like network issues caused to fail, but the ones that fail unit tests should be fixed
Thanks!
But, I did so today after you said it was resolved and it failed again...
rjones (Sat, 14 Oct 2017 19:21:35 GMT):
There were two issues. one was resolved. the other one is apparently not
rjones (Sat, 14 Oct 2017 19:33:49 GMT):
so far, so good. All re-queued builds have taken multiple minutes instead of ending in 14 seconds or whatever
rjones (Sat, 14 Oct 2017 20:01:19 GMT):
I've marked several changes as failing due to unit tests
rjones (Sat, 14 Oct 2017 21:02:35 GMT):
@yacovm I marked everything that failed due to unit tests as such, everything else has worked out
yacovm (Sat, 14 Oct 2017 21:08:24 GMT):
thanks @rjones !
yacovm (Sat, 14 Oct 2017 22:36:09 GMT):
All is good now, you can remove the `-1` from https://gerrit.hyperledger.org/r/#/c/14291/ and https://gerrit.hyperledger.org/r/#/c/14309/ :)
yacovm (Sat, 14 Oct 2017 22:36:09 GMT):
All is good now, @rjones can you remove the `-1` from https://gerrit.hyperledger.org/r/#/c/14291/ and https://gerrit.hyperledger.org/r/#/c/14309/ and https://gerrit.hyperledger.org/r/#/c/14195/ ? :)
yacovm (Sat, 14 Oct 2017 22:36:09 GMT):
All is good now, @rjones can you remove the `-1` from https://gerrit.hyperledger.org/r/#/c/14291/ and https://gerrit.hyperledger.org/r/#/c/14309/ ? :)
rjones (Sat, 14 Oct 2017 23:21:33 GMT):
@yacovm you can delete my votes I’m on the road
rjones (Sat, 14 Oct 2017 23:21:52 GMT):
Click the X by my name in gerrit
yacovm (Sat, 14 Oct 2017 23:22:28 GMT):
sure will do
yacovm (Sat, 14 Oct 2017 23:22:33 GMT):
thanks
NabeelSheikh (Sun, 15 Oct 2017 15:19:04 GMT):
Has joined the channel.
NabeelSheikh (Sun, 15 Oct 2017 15:19:11 GMT):
Running peer channel create -o orderer.example.com:7050 -c $CHANNEL_NAME -f ./channel-artifacts/channel.tx --tls $CORE_PEER_TLS_ENABLED --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem gave me an error Peer command not find. I have re-run the cli container but still same error
rjones (Mon, 16 Oct 2017 20:49:11 GMT):
@rameshthoomu global-jjb is updated https://gerrit.hyperledger.org/r/#/c/14549/ , if you want to try the old versions of `-z` jobs in sandbox let me know if it works now
rjones (Mon, 16 Oct 2017 20:49:30 GMT):
(the ones that log ship)
rameshthoomu (Mon, 16 Oct 2017 20:49:57 GMT):
sure.. will let you know the update
rameshthoomu (Mon, 16 Oct 2017 20:55:10 GMT):
@rjones seems -24 (z) is offiline in sandbox.. If possible could you please make it online.
rjones (Mon, 16 Oct 2017 20:56:05 GMT):
@harrijk this is the error I get: ```
[10/16/17 20:55:33] [SSH] Authentication successful.
SSH connection reports a garbage before a command execution.
Check your .bashrc, .profile, and so on to make sure it is quiet.
The received junk text is as follows:
nvm is not compatible with the npm config "prefix" option: currently set to "/home/jenkins/npm"
Run `nvm use --delete-prefix v8.4.0 --silent` to unset it.
null
[10/16/17 20:55:34] Launch failed - cleaning up connection
[10/16/17 20:55:34] [SSH] Connection closed.
```
rjones (Mon, 16 Oct 2017 20:56:05 GMT):
@harrijk this is the error I get: ```[10/16/17 20:55:33] [SSH] Opening SSH connection to 129.34.32.79:22.
[10/16/17 20:55:33] [SSH] WARNING: SSH Host Keys are not being verified. Man-in-the-middle attacks may be possible against this connection.
[10/16/17 20:55:33] [SSH] Authentication successful.
SSH connection reports a garbage before a command execution.
Check your .bashrc, .profile, and so on to make sure it is quiet.
The received junk text is as follows:
nvm is not compatible with the npm config "prefix" option: currently set to "/home/jenkins/npm"
Run `nvm use --delete-prefix v8.4.0 --silent` to unset it.
null
[10/16/17 20:55:34] Launch failed - cleaning up connection
[10/16/17 20:55:34] [SSH] Connection closed.
```
harrijk (Mon, 16 Oct 2017 20:57:05 GMT):
for all z minions?
rjones (Mon, 16 Oct 2017 20:57:56 GMT):
I only tested the sandbox one
harrijk (Mon, 16 Oct 2017 20:57:57 GMT):
hmm. this looks familiar. @rameshthoomu is this a new one?
harrijk (Mon, 16 Oct 2017 20:58:06 GMT):
OK
rjones (Mon, 16 Oct 2017 20:58:29 GMT):
it looks like all the production `-z` minions are online
harrijk (Mon, 16 Oct 2017 21:01:38 GMT):
Assuming this is the same issue, @rameshthoomu added ...
```
rm -rf $NVM_DIR ~/.npm ~/.bower
```
to the job that had the failure. I assume the line was placed just before the actual build/test began.
rjones (Mon, 16 Oct 2017 21:09:40 GMT):
I guess that needs to be run on the node itself?
rjones (Mon, 16 Oct 2017 21:09:47 GMT):
as in, I need the pump primed
rameshthoomu (Mon, 16 Oct 2017 21:12:59 GMT):
@harrijk `rm -rf $NVM_DIR ~/.npm ~/.bower` we run this command only in fabric-sdk-node builds..
harrijk (Mon, 16 Oct 2017 21:13:42 GMT):
Yeah, pump priming required
harrijk (Mon, 16 Oct 2017 21:13:52 GMT):
;)
rameshthoomu (Mon, 16 Oct 2017 21:14:19 GMT):
:)
rjones (Mon, 16 Oct 2017 21:24:49 GMT):
instead of being coy - I need someone to log on to the machine and do that, I think
mastersingh24 (Tue, 17 Oct 2017 10:28:30 GMT):
@rameshthoomu @rjones https://gerrit.hyperledger.org/r/14585 (support ci.properties for fabric-ca jobs similar to what we did for fabric jobs)
NabeelSheikh (Tue, 17 Oct 2017 10:53:34 GMT):
Running peer channel create -o orderer.example.com:7050 -c $CHANNEL_NAME -f ./channel-artifacts/channel.tx --tls $CORE_PEER_TLS_ENABLED --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem gave me an error Peer command not find. I have re-run the cli container but still same error
NabeelSheikh (Tue, 17 Oct 2017 11:30:21 GMT):
i ran docker exec -it cli bash but getting response " Error daemon container is not running"
rjones (Tue, 17 Oct 2017 14:09:59 GMT):
@harrijk @rameshthoomu I still can't launch the `-z` minion in sandbox due to: ```[10/17/17 14:09:19] [SSH] Authentication successful.
SSH connection reports a garbage before a command execution.
Check your .bashrc, .profile, and so on to make sure it is quiet.
The received junk text is as follows:
nvm is not compatible with the npm config "prefix" option: currently set to "/home/jenkins/npm"
Run `nvm use --delete-prefix v8.4.0 --silent` to unset it.
null
[10/17/17 14:09:20] Launch failed - cleaning up connection
[```
harrijk (Tue, 17 Oct 2017 14:10:53 GMT):
@rjones what is the job that you're running?
harrijk (Tue, 17 Oct 2017 14:11:05 GMT):
I first want to see what this job does
rjones (Tue, 17 Oct 2017 14:11:10 GMT):
I'm not running a job, I'm connecting to the minion
rjones (Tue, 17 Oct 2017 14:12:00 GMT):
something in the `.bashrc` or whatever is emitting that error, so it probably needs the same cleanup you stated above but it needs to be run manually
harrijk (Tue, 17 Oct 2017 14:12:30 GMT):
I see. So you're just running a command using ssh (as user jenkins)
harrijk (Tue, 17 Oct 2017 14:12:48 GMT):
I'll take a look at .bashrc
harrijk (Tue, 17 Oct 2017 14:13:55 GMT):
```
export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh" # This loads nvm
[ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion" # This loads nvm bash_completion```
harrijk (Tue, 17 Oct 2017 14:14:33 GMT):
@rameshthoomu What job needed the above statements to be added to jenkins' .bashrc?
harrijk (Tue, 17 Oct 2017 14:14:55 GMT):
For now, I'll comment out those statements to let @rjones perform his testing.
harrijk (Tue, 17 Oct 2017 14:15:42 GMT):
@rjones can you try again?
rjones (Tue, 17 Oct 2017 14:16:06 GMT):
@harrijk it's online now, thank you. https://jenkins.hyperledger.org/sandbox/computer/hyp-z-linuxone-24/
harrijk (Tue, 17 Oct 2017 14:16:15 GMT):
phew
rjones (Tue, 17 Oct 2017 14:16:29 GMT):
@rameshthoomu could you test the older versions of the `-z` jobs and see that log shipping works?
rjones (Tue, 17 Oct 2017 14:16:36 GMT):
if not we have deeper problems
rameshthoomu (Tue, 17 Oct 2017 14:35:24 GMT):
-z is available now.. will test and update you..
kostas (Tue, 17 Oct 2017 14:46:27 GMT):
I need to be a bit less eager to jump on the `rebuild-foo` bandwagon, which means I need to understand CI logs a bit better. That said, let's have a look at this one: https://jenkins.hyperledger.org/job/fabric-verify-x86_64/18150/consoleText
kostas (Tue, 17 Oct 2017 14:48:58 GMT):
Is the linter failure (on a file that wasn't touched in this changeset BTW) the reason for failure, or is it something else? Is this expected?
rameshthoomu (Tue, 17 Oct 2017 14:50:20 GMT):
yes it's the linter failure
```
msp/mspimplvalidate.go:197: result of fmt.Errorf call not used
exit status 1
Makefile:190: recipe for target 'linter' failed
```
kostas (Tue, 17 Oct 2017 14:50:39 GMT):
I always figure it out after I post here, damn it. I see what's going on.
kostas (Tue, 17 Oct 2017 14:51:02 GMT):
This changeset is stacked against one that does touch `mspimplvalidate.go`.
kostas (Tue, 17 Oct 2017 14:51:11 GMT):
Thanks @rameshthoomu.
kostas (Tue, 17 Oct 2017 14:51:11 GMT):
Thanks @rameshthoomu
rameshthoomu (Tue, 17 Oct 2017 14:51:27 GMT):
sure @kostas
mastersingh24 (Wed, 18 Oct 2017 14:16:15 GMT):
@rameshthoomu - Can you take a look at https://gerrit.hyperledger.org/r/14625 ? I think the change is needed for things to work. Looks like PATH was not properly being set even though it was picking up the GO_VER correctly ( https://jenkins.hyperledger.org/job/fabric-ca-verify-x86_64/2061/parameters/ )
rameshthoomu (Wed, 18 Oct 2017 14:17:10 GMT):
sure.. checking now..
rameshthoomu (Wed, 18 Oct 2017 14:51:08 GMT):
@rjones @jwagantall could you please review and merge this patch https://gerrit.hyperledger.org/r/#/c/14625/
rameshthoomu (Wed, 18 Oct 2017 14:51:59 GMT):
tested this change in sandbox and it's working..
rjones (Wed, 18 Oct 2017 15:14:24 GMT):
@rameshthoomu merged
rameshthoomu (Wed, 18 Oct 2017 15:14:33 GMT):
thanks @rjones
rameshthoomu (Wed, 18 Oct 2017 18:15:10 GMT):
@harsha @bsmita I see this error while running fabric-ca tests on power nodes https://jenkins.hyperledger.org/sandbox/job/fabric-ca-verify-ppc64le/6/console
rameshthoomu (Wed, 18 Oct 2017 18:15:30 GMT):
did you see the same error on fabric-ca tests.. ?
harsha (Wed, 18 Oct 2017 18:21:09 GMT):
@rameshthoomu I do see these errors with go1.9 + fabric-ca.
harsha (Wed, 18 Oct 2017 18:21:09 GMT):
@rameshthoomu I do see these errors with go1.9 + fabric-ca, on my local nodes
rameshthoomu (Wed, 18 Oct 2017 18:21:46 GMT):
ok then it's only on power.. I don't see these failures on z and p
rameshthoomu (Wed, 18 Oct 2017 18:21:46 GMT):
ok then it's only on power.. I don't see these failures on z and x86
bsmita (Wed, 18 Oct 2017 18:22:34 GMT):
@rameshthoomu looks like it's failing to insert entries into database?
rameshthoomu (Wed, 18 Oct 2017 18:25:11 GMT):
@rennman we are seeing fabric-ca test failures in power nodes with go1.9 https://jenkins.hyperledger.org/sandbox/job/fabric-ca-verify-ppc64le/6/consoleFull
rameshthoomu (Wed, 18 Oct 2017 18:25:29 GMT):
could you please check
rennman (Wed, 18 Oct 2017 20:53:40 GMT):
to start, looks like at least one issue is a permission problem ... why are we not able to write to /tmp?
rennman (Wed, 18 Oct 2017 20:54:06 GMT):
6:33:40 main_test.go:527: Unable to create json config file: open /tmp/client-config.json: permission denied
rennman (Wed, 18 Oct 2017 20:54:38 GMT):
if that's the case, we should start there
rennman (Wed, 18 Oct 2017 20:55:07 GMT):
even when the UT starts, we can't even open the results file for writing:
16:32:49 tee: /tmp/test.results: Permission denied
rameshthoomu (Wed, 18 Oct 2017 20:56:38 GMT):
Thanks @rennman .. @bsmita Could you please check this and update in one of the power node in sandbox..
bsmita (Thu, 19 Oct 2017 02:11:44 GMT):
@rameshthoomu for some reason on node-13, the files /tmp/test.results and /tmp/client-config.json that were created a while back were not letting jenkins to overwrite. I deleted them as root and manually created those files as jenkins user and now I can touch those files. Please kick off the run again
rameshthoomu (Thu, 19 Oct 2017 02:19:48 GMT):
Triggered now.. Will let you know the udpate
bsmita (Thu, 19 Oct 2017 13:56:19 GMT):
https://jenkins.hyperledger.org/sandbox/job/fabric-ca-verify-ppc64le/10/ looks like this build passed @rameshthoomu ?
rameshthoomu (Thu, 19 Oct 2017 13:58:00 GMT):
Yes.. it's passed on 16 node..
rameshthoomu (Thu, 19 Oct 2017 13:58:34 GMT):
Will trigger on all nodes now and see the result..
rameshthoomu (Thu, 19 Oct 2017 13:59:43 GMT):
ok done triggered on all nodes now.. will let you know the update..
jtclark (Thu, 19 Oct 2017 14:54:10 GMT):
https://gerrit.hyperledger.org/r/#/c/14655/
jtclark (Thu, 19 Oct 2017 14:54:29 GMT):
can you guys give a quick review to this one? it's very, very, simple.
rameshthoomu (Thu, 19 Oct 2017 14:58:45 GMT):
@jtclark please post in #fabric-pr-review
jtclark (Thu, 19 Oct 2017 15:16:32 GMT):
@rameshthoomu sure, I can post in there again.
jimthematrix (Thu, 19 Oct 2017 16:16:52 GMT):
hi @rameshthoomu @gujingxiao has added jacoco coverage for fabric-chaincode-java, can you work on adding the jenkins plugin to display that when you get a chance? thanks!
jimthematrix (Thu, 19 Oct 2017 16:16:52 GMT):
hi @rameshthoomu, @gujingxiao has added jacoco coverage for fabric-chaincode-java, can you work on adding the jenkins plugin to display that when you get a chance? thanks!
jimthematrix (Thu, 19 Oct 2017 16:16:52 GMT):
hi @rameshthoomu, @gujingxiao has added jacoco coverage for fabric-chaincode-java (https://gerrit.hyperledger.org/r/#/c/14677/), can you work on adding the jenkins plugin to display that when you get a chance? thanks!
gujingxiao (Thu, 19 Oct 2017 16:16:52 GMT):
Has joined the channel.
rameshthoomu (Thu, 19 Oct 2017 16:17:37 GMT):
sure.. If possible could you please JIRA and assign it me..
rameshthoomu (Thu, 19 Oct 2017 16:17:50 GMT):
I will work on this today
rameshthoomu (Thu, 19 Oct 2017 20:18:27 GMT):
@jimthematrix @gujingxiao https://gerrit.hyperledger.org/r/#/c/14713/
rameshthoomu (Thu, 19 Oct 2017 20:19:06 GMT):
Please see the sandbox result link and address the comment I have added in the above patch.
rameshthoomu (Thu, 19 Oct 2017 20:27:29 GMT):
@bsmita triggered multiple times.. I could see 50% of the builds are passed and rest failed.. https://jenkins.hyperledger.org/sandbox/job/fabric-ca-tests-power/
rameshthoomu (Thu, 19 Oct 2017 20:28:22 GMT):
Could you please check the IOWAIT error..
rameshthoomu (Thu, 19 Oct 2017 20:28:22 GMT):
Could you please check the IO wait error..
rjones (Thu, 19 Oct 2017 21:17:26 GMT):
@rameshthoomu let me know when you need 14713 merged, I am out of the house for the next hour or so but I will get to it
rameshthoomu (Thu, 19 Oct 2017 21:18:16 GMT):
sure will do that..
bsmita (Fri, 20 Oct 2017 13:26:33 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=YJm9Ph9gjnoy9PX9G) @rameshthoomu Will check these errors
rameshthoomu (Fri, 20 Oct 2017 13:48:54 GMT):
@rjones this is good to go https://gerrit.hyperledger.org/r/#/c/14713/
tongli (Fri, 20 Oct 2017 15:00:16 GMT):
@rjones want to continue here.
rjones (Fri, 20 Oct 2017 15:00:16 GMT):
@rameshthoomu merged
rjones (Fri, 20 Oct 2017 15:00:38 GMT):
@jwagantall ^^^
tongli (Fri, 20 Oct 2017 15:01:02 GMT):
so you are working on providing a credential that will be able to provision against the cloud for up to 5 machines.
rjones (Fri, 20 Oct 2017 15:01:08 GMT):
@tongli the jenkins server will create these new VMs and have access to them, yes
rjones (Fri, 20 Oct 2017 15:01:45 GMT):
it will be able to provision some number less than 45, which is the amount set aside for the CI silo entirely
tongli (Fri, 20 Oct 2017 15:01:54 GMT):
it will be my ansible script responsibility to provision the machines or you prefer these machines to be there already.
rjones (Fri, 20 Oct 2017 15:02:57 GMT):
there is a new openstack that we aren't using yet, that will replace the current one, that will have up to 45 VMs.
rjones (Fri, 20 Oct 2017 15:03:32 GMT):
previously, you wanted ansible, which I can do, but just now you were talking about doing it some other way and being able to ssh to the machines. I can't provide ssh access to them
tongli (Fri, 20 Oct 2017 15:03:43 GMT):
?
tongli (Fri, 20 Oct 2017 15:04:13 GMT):
it has been ansible all alone,
rjones (Fri, 20 Oct 2017 15:04:16 GMT):
you said: `do I have direct access to 5 machines?`
rjones (Fri, 20 Oct 2017 15:04:30 GMT):
which to me, means, can I ssh to them? the answer is no
tongli (Fri, 20 Oct 2017 15:04:45 GMT):
so how the ansible can access them?
rjones (Fri, 20 Oct 2017 15:05:08 GMT):
previously we had discussed (and I added in Sandbox) the ansible plugin
rjones (Fri, 20 Oct 2017 15:06:08 GMT):
from the jenkins server, I can ssh to the minions, and I assume the ansible plugin will use that to handle orchestration? how are you planning to do this?
rjones (Fri, 20 Oct 2017 15:07:05 GMT):
I didn't enable the ansible plugin in sandbox because of the credential issue, which is now mostly solved. right now it is useless because there are no images in that openstack to instantiate
tongli (Fri, 20 Oct 2017 15:07:21 GMT):
jenkins machine runs ansible script, it can either use OpenStack cloud module provision against the OpenStack endpoint or if these machines have already been created, then the ansible script can simply use them but need to access them via ssh-agent and key pairs.
tongli (Fri, 20 Oct 2017 15:08:20 GMT):
seems you prefer my ansible script not to provision the machines?
rjones (Fri, 20 Oct 2017 15:08:55 GMT):
I don't care how you want to implement it, previously you were wanting ansible, now you're talking about doing some other thing
rjones (Fri, 20 Oct 2017 15:09:06 GMT):
I need requirements that aren't changing
tongli (Fri, 20 Oct 2017 15:09:30 GMT):
what are you talking about? It has always been using ansible script, that never changed.
tongli (Fri, 20 Oct 2017 15:10:15 GMT):
what I am asking is do you prefer I use ansible script running on jenkins to provision new machines or you prefer these new machines get created by you, my ansible script running on jenkins simply use them.
rjones (Fri, 20 Oct 2017 15:10:39 GMT):
I don't care. Your ansible script can provision them
tongli (Fri, 20 Oct 2017 15:10:40 GMT):
the ansible script can do either.
tongli (Fri, 20 Oct 2017 15:11:36 GMT):
ok, in that case, the jenkins job will need a credential which can provision VMs against the openstack cloud, so I will need the openstack endpoint (url) and a credential.
rjones (Fri, 20 Oct 2017 15:12:10 GMT):
right, which as I said isn't quite ready because there aren't any images to provision there.
tongli (Fri, 20 Oct 2017 15:12:11 GMT):
that credential will be a userid/password on the openstack cloud.
rjones (Fri, 20 Oct 2017 15:12:31 GMT):
the new openstack exists and is ready to use, probably, but there are no images to instantiate yet.
tongli (Fri, 20 Oct 2017 15:12:32 GMT):
ok, that is fine, you have entire next week to get that working.
rjones (Fri, 20 Oct 2017 15:13:03 GMT):
is there a place you can put this script so I can test it when you're on the road?
tongli (Fri, 20 Oct 2017 15:13:22 GMT):
cello/src/agent/ansible
tongli (Fri, 20 Oct 2017 15:13:33 GMT):
contains every pieces of the code needed.
tongli (Fri, 20 Oct 2017 15:13:53 GMT):
we have also developed jenkins pipeline to start using it.
tongli (Fri, 20 Oct 2017 15:14:20 GMT):
@suryalanka @rameshthoomu can both help while I am away.
rjones (Fri, 20 Oct 2017 15:17:06 GMT):
are you using pipelines internally? so your team has a lot of experience with Jenkins pipeline jobs?
tongli (Fri, 20 Oct 2017 15:17:55 GMT):
yes, all the jenkins jobs we created are pipelines which we run on our own jenkins server.
rjones (Fri, 20 Oct 2017 15:18:10 GMT):
excellent. are you using JJB internally?
tongli (Fri, 20 Oct 2017 15:18:49 GMT):
a lot easier to manage, no, I am not using JJB, I think @rameshthoomu use it.
tongli (Fri, 20 Oct 2017 15:19:14 GMT):
what kind of images are you planning to upload to OpenStack cloud?
rameshthoomu (Fri, 20 Oct 2017 15:20:16 GMT):
@rjones I have to work on creating one.. @tongli right now, we don't have JJB with pipeline..
rameshthoomu (Fri, 20 Oct 2017 15:20:50 GMT):
will create a one in sandbox and let you know how this goes..
rjones (Fri, 20 Oct 2017 15:21:51 GMT):
@tongli they will be the same images we use in the current openstack cloud - Ubuntu 16.04 IIRC
tongli (Fri, 20 Oct 2017 15:22:00 GMT):
@rameshthoomu I do not think @rjones was asking if we are combining JJB and pipeline. I wish that we do not do that.
rjones (Fri, 20 Oct 2017 15:22:21 GMT):
@tongli that is the only way forward, though
tongli (Fri, 20 Oct 2017 15:22:25 GMT):
@rjones, ok that is fine, I do not like to have images with extra stuff on.
jeremyphelps (Fri, 20 Oct 2017 15:22:40 GMT):
Has joined the channel.
tongli (Fri, 20 Oct 2017 15:22:47 GMT):
@rjones JJB to include pipeline?
rjones (Fri, 20 Oct 2017 15:23:39 GMT):
@tongli yes, we use JJB for everything, so for pipeline we will need JJB
tongli (Fri, 20 Oct 2017 15:23:48 GMT):
@rjones, are you saying developing JJB which actually produce a pipeline (or point to a pipeline jenkins project)?
rjones (Fri, 20 Oct 2017 15:24:18 GMT):
I'm not quite sure what you're asking.
jeremyphelps (Fri, 20 Oct 2017 15:24:44 GMT):
@tongli use JJB to instrument a pipeline
tongli (Fri, 20 Oct 2017 15:24:47 GMT):
JJB import into jenkins, but in our case, produce a pipeline jenkins project,
tongli (Fri, 20 Oct 2017 15:25:03 GMT):
I think I understand what you are saying.
tongli (Fri, 20 Oct 2017 15:25:28 GMT):
will be still a JJB but after put into jenkins, it becomes a pipeline project.
jeremyphelps (Fri, 20 Oct 2017 15:25:35 GMT):
yes
jeremyphelps (Fri, 20 Oct 2017 15:25:42 GMT):
JJB can be used to create a pipeline
tongli (Fri, 20 Oct 2017 15:25:49 GMT):
vs some other kind of job in jenkins,
tongli (Fri, 20 Oct 2017 15:25:55 GMT):
that is fine.
rameshthoomu (Fri, 20 Oct 2017 15:25:56 GMT):
yes
tongli (Fri, 20 Oct 2017 15:26:19 GMT):
if this is for automation, then yeah, we can go for that.
tongli (Fri, 20 Oct 2017 15:26:28 GMT):
no issue there.
tongli (Fri, 20 Oct 2017 15:27:20 GMT):
I think we are good for now, thanks to @rjones @rameshthoomu @suryalanka .
tongli (Fri, 20 Oct 2017 15:27:58 GMT):
also @jeremyphelps , sorry.
jeremyphelps (Fri, 20 Oct 2017 15:28:01 GMT):
There are several things to work out before this happens, it's not a for sure thing.
jeremyphelps (Fri, 20 Oct 2017 15:28:08 GMT):
not a problem @tongli
tongli (Fri, 20 Oct 2017 15:28:45 GMT):
@jeremyphelps that is fine, let me know if I can help in any way, I know OpenStack very well.
jimthematrix (Tue, 24 Oct 2017 16:11:23 GMT):
@rameshthoomu the Composer team are noticing the node SDK merge jobs sometimes fail to publish to npm "unstable" tags, can you check on that please?
rameshthoomu (Tue, 24 Oct 2017 16:12:48 GMT):
will check.. but if the merge job is failed for some reason. it won't publish npm modules..
Menniti (Tue, 24 Oct 2017 16:20:33 GMT):
Hey guys,
Maybe someone is interested
Hyperledger Course in EdX
https://www.edx.org/course/blockchain-business-introduction-linuxfoundationx-lfs171x
jyellick (Wed, 25 Oct 2017 03:10:52 GMT):
@Menniti You've posted this several times in multiple channels, please don't spam.
wlahti (Wed, 25 Oct 2017 12:11:51 GMT):
Anybody seen CI failures like this before?
```--- FAIL: TestQueries (3.07s)
exectransaction_test.go:1121: Error initializing chaincode tmap(Error deploying chaincode(2): error starting container: Failed to generate platform-specific docker build: Failed to pull hyperledger/fabric-ccenv:x86_64-1.0.0-snapshot-4342105: API error (404): {"message":"manifest for hyperledger/fabric-ccenv:x86_64-1.0.0-snapshot-4342105 not found"}
)```
wlahti (Wed, 25 Oct 2017 12:11:51 GMT):
Anybody seen CI failures like this before?
```--- FAIL: TestQueries (3.07s)
exectransaction_test.go:1121: Error initializing chaincode tmap(Error deploying chaincode(2): error starting container: Failed to generate platform-specific docker build: Failed to pull hyperledger/fabric-ccenv:x86_64-1.0.0-snapshot-4342105: API error (404): {"message":"manifest for hyperledger/fabric-ccenv:x86_64-1.0.0-snapshot-4342105 not found"}
)```
wlahti (Wed, 25 Oct 2017 12:11:51 GMT):
Anybody seen CI failures like this before? One of my CRs keeps failing with this error even though it's (seemingly) unrelated.
```--- FAIL: TestQueries (3.07s)
exectransaction_test.go:1121: Error initializing chaincode tmap(Error deploying chaincode(2): error starting container: Failed to generate platform-specific docker build: Failed to pull hyperledger/fabric-ccenv:x86_64-1.0.0-snapshot-4342105: API error (404): {"message":"manifest for hyperledger/fabric-ccenv:x86_64-1.0.0-snapshot-4342105 not found"}
)```
wlahti (Wed, 25 Oct 2017 12:11:51 GMT):
Has anybody seen CI failures like this before? One of my CRs keeps failing with this error even though it's (seemingly) unrelated.
```--- FAIL: TestQueries (3.07s)
exectransaction_test.go:1121: Error initializing chaincode tmap(Error deploying chaincode(2): error starting container: Failed to generate platform-specific docker build: Failed to pull hyperledger/fabric-ccenv:x86_64-1.0.0-snapshot-4342105: API error (404): {"message":"manifest for hyperledger/fabric-ccenv:x86_64-1.0.0-snapshot-4342105 not found"}
)```
rameshthoomu (Wed, 25 Oct 2017 13:34:19 GMT):
No.. Could you please refer the build number..
wlahti (Wed, 25 Oct 2017 14:34:41 GMT):
https://jenkins.hyperledger.org/job/fabric-verify-x86_64/18398/consoleFull
rameshthoomu (Wed, 25 Oct 2017 15:13:42 GMT):
@wlahti I see timeout expired error messages in the recent failures.. If possible could you please check ```Invalid execute timeout value 0s (should be at least 1s); defaulting to 30s```
srongzhe (Sun, 29 Oct 2017 13:25:48 GMT):
Has joined the channel.
jyellick (Thu, 02 Nov 2017 17:02:10 GMT):
@rameshthoomu https://jenkins.hyperledger.org/job/fabric-verify-x86_64/18704/console
```
13:58:27 curl: (22) The requested URL returned error: 504 Gateway Time-out
13:58:27 Makefile:194: recipe for target 'build/bin/chaintool' failed
```
jyellick (Thu, 02 Nov 2017 17:02:44 GMT):
I'm seeing this across many builds
rameshthoomu (Thu, 02 Nov 2017 17:02:52 GMT):
Yes we are seeing this too frequently today
rameshthoomu (Thu, 02 Nov 2017 17:03:35 GMT):
Checking for the mirror link .. for now pls re-trigger
jyellick (Thu, 02 Nov 2017 17:03:42 GMT):
Great, thanks
mastersingh24 (Fri, 03 Nov 2017 19:31:38 GMT):
@rameshthoomu - so what exactly is https://jenkins.hyperledger.org/job/fabric-sdk-node-vulnerable-tests-x86_64/74/ and what happened to the other standard fabric-sdk-node tests?
rameshthoomu (Fri, 03 Nov 2017 19:32:12 GMT):
:(
rameshthoomu (Fri, 03 Nov 2017 19:32:21 GMT):
I didn't see this.. let me check
rameshthoomu (Fri, 03 Nov 2017 19:34:44 GMT):
seems gerrit trigger causing this issue..
mastersingh24 (Fri, 03 Nov 2017 19:58:13 GMT):
seems like it's been happening for at least 1 day
mastersingh24 (Fri, 03 Nov 2017 19:59:50 GMT):
actually 3 days ago is the last time the standard tests ran
rameshthoomu (Fri, 03 Nov 2017 20:22:56 GMT):
@mastersingh24 - issue is fixed and now all the jobs are triggered.. Will add `rebuild-node6-x` etc.. build phrases are reverted.. I am actually optimizing these triggers.
rameshthoomu (Fri, 03 Nov 2017 20:23:08 GMT):
will work on this..
mastersingh24 (Fri, 03 Nov 2017 20:40:53 GMT):
thanks @rameshthoomu
rickr (Mon, 06 Nov 2017 13:31:14 GMT):
https://gerrit.hyperledger.org/r/#/c/14339/
reverify not kicking off ... yes it's been merged but running merged already passed CRs can be very useful and this used to work for me.
rickr (Mon, 06 Nov 2017 13:50:50 GMT):
odd the build happened but there was no message indicating it started
rameshthoomu (Mon, 06 Nov 2017 14:00:39 GMT):
@rickr After the patch is merged, `reverify` trigger the verify jobs not the merge jobs.. do `remerge` to trigger the merge jobs..
rickr (Mon, 06 Nov 2017 14:01:27 GMT):
@rameshthoomu The build was retriggered
rickr (Mon, 06 Nov 2017 14:01:38 GMT):
It just didn't report it started
rameshthoomu (Mon, 06 Nov 2017 14:01:50 GMT):
yes it will trigger the verify jobs..
rameshthoomu (Mon, 06 Nov 2017 14:02:10 GMT):
yes once the patch is merged, Jenkins is not reporting any status back to gerrit..
rickr (Mon, 06 Nov 2017 14:02:24 GMT):
so what's the diff between reverfiy and remerge ?
rameshthoomu (Mon, 06 Nov 2017 14:02:26 GMT):
we are waiting for the fix.
rameshthoomu (Mon, 06 Nov 2017 14:02:49 GMT):
both does the same thing here..
rickr (Mon, 06 Nov 2017 14:03:06 GMT):
ok so ignore your advice on remerge :)
rameshthoomu (Mon, 06 Nov 2017 14:03:26 GMT):
so it's ok to trigger either reverify or remerge.. But the status is not reporting back to gerrit..
rameshthoomu (Mon, 06 Nov 2017 14:03:35 GMT):
Will let you know once this is fixed..
rickr (Mon, 06 Nov 2017 14:06:10 GMT):
np -- not so urgent -- The main thing is after the a while the output is lost and sometimes for the last merge it good to get that back to compare.
IMO It would be great if the last merged output was never lost till ofcourse the merge but that _icing on the cake_
rickr (Mon, 06 Nov 2017 14:06:10 GMT):
np -- not so urgent -- The main thing is after the a while the output is lost and sometimes for the last merge it good to get that back to compare.
IMO It would be great if the last merged output was never lost till ofcourse the next merge but that _icing on the cake_
zdmob (Tue, 07 Nov 2017 01:51:45 GMT):
Has joined the channel.
jimthematrix (Tue, 07 Nov 2017 16:43:59 GMT):
@rameshthoomu just opened FAB-6909 to upgrade node.js engine to 8.9.0 (new LTS), thanks!
jimthematrix (Tue, 07 Nov 2017 16:43:59 GMT):
@rameshthoomu just opened FAB-6910 to upgrade node.js engine to 8.9.0 (new LTS), thanks!
rameshthoomu (Tue, 07 Nov 2017 16:45:21 GMT):
Ok will update CI build nodes and let you know
rameshthoomu (Tue, 07 Nov 2017 17:23:53 GMT):
@jimthematrix Do you want me to update on fabric-chaincode-node jobs as well..
jimthematrix (Tue, 07 Nov 2017 17:24:16 GMT):
yes please
rameshthoomu (Tue, 07 Nov 2017 17:24:26 GMT):
ok
guoger (Wed, 08 Nov 2017 04:37:41 GMT):
e2e test for my [patch](https://gerrit.hyperledger.org/r/#/c/15249/) failed with following error:
```
Pulling zookeeper0 (hyperledger/fabric-zookeeper:latest)...
manifest for hyperledger/fabric-zookeeper:latest not found
ERROR !!!! Unable to pull the images
```
https://logs.hyperledger.org/production/vex-yul-hyp-jenkins-3/fabric-verify-end-2-end-x86_64/10503/console.log.gz
Supposedly that image ought to be built from dockerfile instead of pulled, correct?
guoger (Wed, 08 Nov 2017 06:13:25 GMT):
NVMD, `rebuild-e2e` solves the problem.
dave.enyeart (Thu, 09 Nov 2017 00:55:38 GMT):
@rjones @rameshthoomu looks like CI is failing in e2e and behave for all builds this afternoon, due to errors getting zookeeper
dave.enyeart (Thu, 09 Nov 2017 00:55:46 GMT):
For example look at https://gerrit.hyperledger.org/r/#/c/15323/
rjones (Thu, 09 Nov 2017 01:24:29 GMT):
@dave.enyeart rebase
rjones (Thu, 09 Nov 2017 01:24:40 GMT):
Fix was merged today
dave.enyeart (Thu, 09 Nov 2017 01:32:40 GMT):
@rjones thanks, just rebased a bunch of them
rjones (Thu, 09 Nov 2017 01:51:01 GMT):
@dave.enyeart thank you
dave.enyeart (Thu, 09 Nov 2017 03:19:57 GMT):
@rjones the rebase worked, but as usual one or two of the CIs still fail intermittently in each CR. remind me what the rebuild-{} command is for fabric-verify-s390x?
rjones (Thu, 09 Nov 2017 03:20:26 GMT):
I think rebuild-z? let me look
dave.enyeart (Thu, 09 Nov 2017 03:20:28 GMT):
or better yet show me where to look this up
dave.enyeart (Thu, 09 Nov 2017 03:20:57 GMT):
rebuild-z was the name when the verify job was called 'z'... just curious if it changed due to the s390 rename.
rjones (Thu, 09 Nov 2017 03:21:55 GMT):
https://github.com/hyperledger/ci-management/blob/master/jjb/global-macros.yaml
rjones (Thu, 09 Nov 2017 03:22:20 GMT):
https://github.com/hyperledger/ci-management/blob/master/jjb/global-macros.yaml#L242
rjones (Thu, 09 Nov 2017 03:22:43 GMT):
I forgot to add one for s390x, I probably won't since we already use rebuild-x
rjones (Thu, 09 Nov 2017 03:23:35 GMT):
@dave.enyeart if you like I can add a verb for rebuild-s390x
dave.enyeart (Thu, 09 Nov 2017 03:23:45 GMT):
yes please!
rjones (Thu, 09 Nov 2017 03:25:53 GMT):
https://gerrit.hyperledger.org/r/#/c/15337/
dave.enyeart (Thu, 09 Nov 2017 03:26:41 GMT):
thx
jimthematrix (Thu, 09 Nov 2017 15:19:58 GMT):
@rameshthoomu latest fabric-chaincode-node merge CI on x86 failed:
```17:42:25 [fabric-chaincode-node-merge-x86_64] $ /bin/bash -eu /tmp/jenkins4898242766787313616.sh
17:42:25 /tmp/jenkins4898242766787313616.sh: line 63: npm: command not found
jimthematrix (Thu, 09 Nov 2017 15:20:05 GMT):
https://jenkins.hyperledger.org/view/fabric-chaincode-node/job/fabric-chaincode-node-merge-x86_64/46/console
rameshthoomu (Thu, 09 Nov 2017 15:20:30 GMT):
checking
jimthematrix (Thu, 09 Nov 2017 15:20:44 GMT):
thanks
rameshthoomu (Thu, 09 Nov 2017 15:22:49 GMT):
seems 8.9.0 is missing in the PATH.. I re-triggered the job now..
rameshthoomu (Thu, 09 Nov 2017 15:24:40 GMT):
I see now 8.9.0 version is set in the PATH.. Will check more if it fail again..
rameshthoomu (Thu, 09 Nov 2017 15:45:55 GMT):
@jimthematrix worked now https://jenkins.hyperledger.org/view/fabric-chaincode-node/job/fabric-chaincode-node-merge-x86_64/47/consoleFull
jimthematrix (Thu, 09 Nov 2017 15:48:22 GMT):
thanks Ramesh!
nnao (Fri, 10 Nov 2017 00:41:08 GMT):
Has joined the channel.
mastersingh24 (Fri, 10 Nov 2017 19:14:21 GMT):
@rameshthoomu - no rush - but can you take a look at https://jenkins.hyperledger.org/job/fabric-sdk-node6-verify-x86_64/204/consoleFull ?
mastersingh24 (Fri, 10 Nov 2017 19:14:38 GMT):
Seems like there may be some inconsistencies on the build machines?
rameshthoomu (Fri, 10 Nov 2017 19:16:31 GMT):
yes.. submitting fix for this..We are seeing this issue, If a patch set is triggered on a non-destroyed VM
rjones (Fri, 10 Nov 2017 19:23:31 GMT):
@rameshthoomu I have noticed today we are re-running jobs on VMs sometimes
rjones (Fri, 10 Nov 2017 19:23:49 GMT):
I'm not sure what is going on
rameshthoomu (Fri, 10 Nov 2017 19:26:05 GMT):
we are seeing below issue
```
00:11:14.767 + nvm_err 'Run `nvm use --delete-prefix v6.9.5` to unset it.'
00:11:14.768 + nvm_echo 'Run `nvm use --delete-prefix v6.9.5` to unset it.'
00:11:14.768 + command printf '%s\n' 'Run `nvm use --delete-prefix v6.9.5` to unset it.'
00:11:14.768 Run `nvm use --delete-prefix v6.9.5` to unset it
``` if the node sdk patch set is running on non-destroyed VM..
rameshthoomu (Fri, 10 Nov 2017 19:26:17 GMT):
I am testing this fix in sandbox and seems it's working..
rjones (Fri, 10 Nov 2017 19:34:05 GMT):
ok
thiago-moreira (Sun, 12 Nov 2017 01:25:29 GMT):
Has joined the channel.
mastersingh24 (Sun, 12 Nov 2017 13:32:43 GMT):
FYI - I believe that https://jira.hyperledger.org/browse/FAB-6969 is the reason CI for fabric is failing
mastersingh24 (Sun, 12 Nov 2017 13:33:03 GMT):
I'm working on it now
yacovm (Mon, 13 Nov 2017 12:14:03 GMT):
@mastersingh24 any idea why the java SDK fails in your change sets? @rickr FYI
yacovm (Mon, 13 Nov 2017 12:14:03 GMT):
@mastersingh24 any idea why the java SDK e2e fails in your change sets? @rickr FYI
mastersingh24 (Mon, 13 Nov 2017 12:53:40 GMT):
@yacovm - sadly yes - https://gerrit.hyperledger.org/r/15429 - figured it out last night but opted for sleep rather than fixing it ;)
rickr (Mon, 13 Nov 2017 14:06:42 GMT):
@mastersingh24 did you fix it in your sleep ?
dave.enyeart (Mon, 13 Nov 2017 14:30:28 GMT):
@mastersingh24 @yacovm I see it is merged now. So a rebuild-e2e on https://gerrit.hyperledger.org/r/#/c/15411/ should work now?
yacovm (Mon, 13 Nov 2017 14:35:44 GMT):
it should
yacovm (Mon, 13 Nov 2017 14:35:47 GMT):
@dave.enyeart
dave.enyeart (Mon, 13 Nov 2017 14:37:24 GMT):
ok just attempted it
mastersingh24 (Mon, 13 Nov 2017 15:00:39 GMT):
That's the dream @dave.enyeart ;)
mastersingh24 (Mon, 13 Nov 2017 15:48:49 GMT):
Should be good to go now!
mastersingh24 (Mon, 13 Nov 2017 16:04:52 GMT):
@rameshthoomu - can you figure out what's going on with https://jenkins.hyperledger.org/job/fabric-verify-end-2-end-x86_64/10633/console ?
mastersingh24 (Mon, 13 Nov 2017 16:05:14 GMT):
This is for the release branch of fabric and seems to be confused with Docker images
rameshthoomu (Mon, 13 Nov 2017 16:06:02 GMT):
it seems this patch has to rebase.. I see this error while building zookeeper image
```
00:05:06.089 + curl -fsSL http://www.apache.org/dist/zookeeper/zookeeper-3.4.9/zookeeper-3.4.9.tar.gz
00:05:06.269 curl: (22) The requested URL returned error: 404 Not Found
00:05:06.270
```
rameshthoomu (Mon, 13 Nov 2017 16:07:18 GMT):
I have to submit this patch in `release branch` https://gerrit.hyperledger.org/r/#/c/15319/
rameshthoomu (Mon, 13 Nov 2017 16:37:30 GMT):
@mastersingh24 https://gerrit.hyperledger.org/r/#/c/15433/
mastersingh24 (Mon, 13 Nov 2017 16:46:22 GMT):
cool. thx
rameshthoomu (Mon, 13 Nov 2017 20:09:47 GMT):
@mastersingh24 fabric unit-tests jobs is failing consistently (unit-test containers is not launching) FAB-6977
rameshthoomu (Mon, 13 Nov 2017 20:10:34 GMT):
I see the similar error in my machine.. not sure what's causing this error..
rameshthoomu (Tue, 14 Nov 2017 16:31:28 GMT):
Referring @AdnanC post in #ci-pipeline [ ](https://chat.hyperledger.org/channel/ci-pipeline?msg=KQGSQt2P8vLaqkcPW) @AdnanC
rameshthoomu (Tue, 14 Nov 2017 16:33:29 GMT):
@rjones @jwagantall I see many builds are failing with curl (18) error
I see `curl` command is failed to fetch `maven` version from third party site..
```
00:06:27.353 Step 7/15 : RUN mkdir -p /usr/share/maven /usr/share/maven/ref && curl -fsSL http://www-us.apache.org/dist/maven/maven-3/$MAVEN_VERSION/binaries/apache-maven-$MAVEN_VERSION-bin.tar.gz | tar -xzC /usr/share/maven --strip-components=1 && ln -s /usr/share/maven/bin/mvn /usr/bin/mvn
00:06:27.475 ---> Running in a8a923221233
00:06:30.362 curl: (18) transfer closed with 8373958 bytes remaining to read
```
Is this network latency error ?
rameshthoomu (Tue, 14 Nov 2017 16:33:29 GMT):
@rjones @jwagantall I see many builds are failing with curl (18) error
```
I see `curl` command is failed to fetch `maven` version from third party site..
```
00:06:27.353 Step 7/15 : RUN mkdir -p /usr/share/maven /usr/share/maven/ref && curl -fsSL http://www-us.apache.org/dist/maven/maven-3/$MAVEN_VERSION/binaries/apache-maven-$MAVEN_VERSION-bin.tar.gz | tar -xzC /usr/share/maven --strip-components=1 && ln -s /usr/share/maven/bin/mvn /usr/bin/mvn
00:06:27.475 ---> Running in a8a923221233
00:06:30.362 curl: (18) transfer closed with 8373958 bytes remaining to read
```
Is this network latency error ?
jwagantall (Tue, 14 Nov 2017 16:53:09 GMT):
i need to see... could be since no other change seems related..ill take a peek
rameshthoomu (Tue, 14 Nov 2017 16:55:30 GMT):
Observed this error while doing curl on `zookeeper, maven, couchdb and kafka`
jwagantall (Tue, 14 Nov 2017 16:56:57 GMT):
I know that curl is pretty buggy inside docker... did you guys recently changed the MTU for docker? @rjones?
rameshthoomu (Tue, 14 Nov 2017 17:06:22 GMT):
I am working on FAB-6941. may this will simplify build process and avoids these errors
rameshthoomu (Tue, 14 Nov 2017 17:06:22 GMT):
FYI I am working on FAB-6941. may this will simplify build process and avoids these errors
rameshthoomu (Tue, 14 Nov 2017 17:06:29 GMT):
https://jira.hyperledger.org/browse/FAB-6941
rjones (Tue, 14 Nov 2017 17:37:00 GMT):
@jwagantall I haven’t changed anything, however, we did need to change the MTU inside docket a long time ago for one of @greg.haskins projects
greg.haskins (Tue, 14 Nov 2017 17:37:00 GMT):
Has joined the channel.
rjones (Tue, 14 Nov 2017 17:38:48 GMT):
@rameshthoomu the issue is docker no longer calculates the MTU correctly as of some version about a year ago
jwagantall (Tue, 14 Nov 2017 17:40:43 GMT):
thanks @rjones was this issue seen after upgrading docker (to 1.10 i think) .. we saw the same issues in ONAP.. but in ONAP's case curl wont work at all..
rjones (Tue, 14 Nov 2017 17:41:20 GMT):
Even with the smaller MTU?
jwagantall (Tue, 14 Nov 2017 17:44:03 GMT):
not sure what is the default MTU.. but after doing some online investigation we found 1454 did the trick for us
rjones (Tue, 14 Nov 2017 17:44:05 GMT):
@jwagantall sorry I misread what you said.
rjones (Tue, 14 Nov 2017 17:53:10 GMT):
@rameshthoomu @jwagantall here is where we fixed it a long time ago: https://github.com/hyperledger/ci-management/blame/f2beb20e6b86798ac82a0ca9f607b67a47a61663/packer/provision/docker.sh#L66
rjones (Tue, 14 Nov 2017 17:53:33 GMT):
we discovered 1392 experimentally
rjones (Tue, 14 Nov 2017 17:54:27 GMT):
@rameshthoomu are these builds that have worked with exactly these changes before? It's possible our upstream changed MTUs and I need to adjust MTU again
rameshthoomu (Tue, 14 Nov 2017 18:54:40 GMT):
@rjones yes these builds worked earlier and it's working now also but it's very inconsistent..
flyq (Wed, 15 Nov 2017 04:41:31 GMT):
Has joined the channel.
flyq (Wed, 15 Nov 2017 04:42:58 GMT):
Has left the channel.
chrispoole (Wed, 15 Nov 2017 14:51:41 GMT):
Has joined the channel.
chrispoole (Wed, 15 Nov 2017 14:52:11 GMT):
Hey folks... could someone help with the verify job for `fabric-sdk-rest` please?
Example failure just now: https://logs.hyperledger.org/production/vex-yul-hyp-jenkins-3/fabric-sdk-rest-verify-x86_64/73/console.log.gz
```
```
> pkcs11js@1.0.10 install /w/workspace/fabric-sdk-rest-verify-x86_64/gopath/src/github.com/hyperledger/fabric-sdk-rest/node_modules/pkcs11js
> node-gyp rebuild
make: Entering directory '/w/workspace/fabric-sdk-rest-verify-x86_64/gopath/src/github.com/hyperledger/fabric-sdk-rest/node_modules/pkcs11js/build'
CXX(target) Release/obj.target/pkcs11/src/main.o
CXX(target) Release/obj.target/pkcs11/src/dl.o
CXX(target) Release/obj.target/pkcs11/src/const.o
In file included from ../src/const.cpp:1:0:
../src/const.cpp: In function ‘void declare_attributes(v8::Local
chrispoole (Wed, 15 Nov 2017 14:52:11 GMT):
Hey folks... could someone help with the verify job for `fabric-sdk-rest` please?
Example failure just now: https://logs.hyperledger.org/production/vex-yul-hyp-jenkins-3/fabric-sdk-rest-verify-x86_64/73/console.log.gz
```
> pkcs11js@1.0.10 install /w/workspace/fabric-sdk-rest-verify-x86_64/gopath/src/github.com/hyperledger/fabric-sdk-rest/node_modules/pkcs11js
> node-gyp rebuild
make: Entering directory '/w/workspace/fabric-sdk-rest-verify-x86_64/gopath/src/github.com/hyperledger/fabric-sdk-rest/node_modules/pkcs11js/build'
CXX(target) Release/obj.target/pkcs11/src/main.o
CXX(target) Release/obj.target/pkcs11/src/dl.o
CXX(target) Release/obj.target/pkcs11/src/const.o
In file included from ../src/const.cpp:1:0:
../src/const.cpp: In function ‘void declare_attributes(v8::Local
rameshthoomu (Wed, 15 Nov 2017 14:53:14 GMT):
Seems it' failed to connect to the server
```
00:04:54.144 Browse your REST API at http://0.0.0.0:3000/explorer
00:05:20.710 Unhandled error for request POST /auth/ldap: Error: connect ECONNREFUSED 0.0.0.0:1389
00:05:20.710 at Object.exports._errnoException (util.js:1022:11)
00:05:20.710 at exports._exceptionWithHostPort (util.js:1045:20)
00:05:20.710 at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1087:14)
00:05:20.723 Error: connect ECONNREFUSED 0.0.0.0:1389
00:05:20.723 at Object.exports._errnoException (util.js:1022:11)
00:05:20.723 at exports._exceptionWithHostPort (util.js:1045:20)
00:05:20.723 at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1087:14)
00:05:20.751 Treating unknown remoting type "args" as "any"
00:05:20.764 Unhandled error for request POST /api/fabric/1_0/channels/mychannel/ledger?chaincodeId=fabcar: Error: Authorization Required
```
rameshthoomu (Wed, 15 Nov 2017 14:53:21 GMT):
Let me re-trigger this
chrispoole (Wed, 15 Nov 2017 14:53:52 GMT):
Ahhhh... not yey
chrispoole (Wed, 15 Nov 2017 14:53:54 GMT):
yet
chrispoole (Wed, 15 Nov 2017 14:54:13 GMT):
Didn't spot that; I've updated the tests so will need to update the script that Jenkins runs
rameshthoomu (Wed, 15 Nov 2017 14:54:48 GMT):
cool..
rameshthoomu (Wed, 15 Nov 2017 14:55:25 GMT):
ping me if you have any script/commands to incorporate in CI script..
chrispoole (Wed, 15 Nov 2017 14:55:51 GMT):
Where did you see that output, btw?
chrispoole (Wed, 15 Nov 2017 14:55:59 GMT):
Is this in run 73?
rameshthoomu (Wed, 15 Nov 2017 15:04:04 GMT):
yes in 73 run
rameshthoomu (Wed, 15 Nov 2017 15:04:11 GMT):
search with `Hyperledger Fabric SDK REST`
rameshthoomu (Wed, 15 Nov 2017 15:04:39 GMT):
or with `Unhandled error`
boliang (Thu, 16 Nov 2017 14:43:58 GMT):
Hi, anyone sees these errors?
```
Creating network "e2ecli_default" with the default driver
Pulling zookeeper0 (hyperledger/fabric-zookeeper:latest)...
manifest for hyperledger/fabric-zookeeper:latest not found
ERROR !!!! Unable to pull the images
Build step 'Execute shell' marked build as failure
```
Details refer to https://logs.hyperledger.org/production/vex-yul-hyp-jenkins-3/fabric-verify-end-2-end-x86_64/10690/console.log.gz
boliang (Thu, 16 Nov 2017 14:43:58 GMT):
Hi, anyone sees these errors?
```Creating network "e2ecli_default" with the default driver
Pulling zookeeper0 (hyperledger/fabric-zookeeper:latest)...
manifest for hyperledger/fabric-zookeeper:latest not found
ERROR !!!! Unable to pull the images
Build step 'Execute shell' marked build as failure
```
Details refer to https://logs.hyperledger.org/production/vex-yul-hyp-jenkins-3/fabric-verify-end-2-end-x86_64/10690/console.log.gz
rameshthoomu (Thu, 16 Nov 2017 14:44:55 GMT):
@boliang checking
rameshthoomu (Thu, 16 Nov 2017 14:46:01 GMT):
@boliang I see zookeeper image is failed to build.. Got curl (18) error
```
Removing intermediate container f3f5c62cb307
Step 7/15 : RUN set -x && cd / && curl -fsSL "http://www.apache.org/dist/zookeeper/$DISTRO_NAME/$DISTRO_NAME.tar.gz" | tar -xz && mv "$DISTRO_NAME/conf/"* "$ZOO_CONF_DIR"
---> Running in 423d6055dd9c
+ cd /
+ curl -fsSL http://www.apache.org/dist/zookeeper/zookeeper-3.4.10/zookeeper-3.4.10.tar.gz
+ tar -xz
curl: (18) transfer closed with 32761179 bytes remaining to read
```
rameshthoomu (Thu, 16 Nov 2017 14:46:01 GMT):
@boliang I see zookeeper image is failed to build.. Got curl (18) error
```
+ cd /
+ curl -fsSL http://www.apache.org/dist/zookeeper/zookeeper-3.4.10/zookeeper-3.4.10.tar.gz
+ tar -xz
curl: (18) transfer closed with 32761179 bytes remaining to read
```
boliang (Thu, 16 Nov 2017 14:46:26 GMT):
Yep
boliang (Thu, 16 Nov 2017 14:46:42 GMT):
Connection issue in server?
boliang (Thu, 16 Nov 2017 14:47:01 GMT):
Met this error twice today
rameshthoomu (Thu, 16 Nov 2017 14:47:10 GMT):
Seems behave test job also failed with the same error but it;s with Kafka
```
/opt/kafka && rm kafka_"$SCALA_VERSION"-"$KAFKA_VERSION".tgz
00:10:29.392 ---> Running in 239a84175fca
00:10:33.101 curl: (18) transfer closed with 35119182 bytes remaining to read
```
rameshthoomu (Thu, 16 Nov 2017 14:47:41 GMT):
Yes we are seeing these issues intermittently.. Could be network issue..
rameshthoomu (Thu, 16 Nov 2017 14:47:56 GMT):
@rjones and @jwagantall looking into this..
boliang (Thu, 16 Nov 2017 14:49:15 GMT):
Thanks. Let me retry the testing. BTW, what's the command of rebuild everything?
rameshthoomu (Thu, 16 Nov 2017 14:49:27 GMT):
`rebuild-e2e, rebuild-behave`
boliang (Thu, 16 Nov 2017 14:49:57 GMT):
thx
rameshthoomu (Thu, 16 Nov 2017 14:50:09 GMT):
this triggers those two failed jobs.. If you want to trigger the success jobs (all), just do `reverify`
harsha (Thu, 16 Nov 2017 16:36:25 GMT):
`make` breaks on `fabric-ca` when I'm at commit level `52fc1f6be7199ba1f8b1f7dc1d9af766a42b6643` which is pretty latest.
^^^@rameshthoomu @rennman
rameshthoomu (Thu, 16 Nov 2017 16:39:05 GMT):
I see the merge job passed 4 hr ago.. let me check
rameshthoomu (Thu, 16 Nov 2017 16:43:16 GMT):
I just re-triggered fabric-ca job on latest commit and observed the same error.. https://jenkins.hyperledger.org/view/fabric-ca/job/fabric-ca-verify-s390x/2306/console
rameshthoomu (Thu, 16 Nov 2017 16:44:13 GMT):
@harsha pls post in #fabric-ca channel
skarim (Thu, 16 Nov 2017 19:38:15 GMT):
Has joined the channel.
boliang (Mon, 20 Nov 2017 13:56:20 GMT):
```Creating network "e2ecli_default" with the default driver
Pulling kafka3 (hyperledger/fabric-kafka:latest)...
manifest for hyperledger/fabric-kafka:latest not found
ERROR !!!! Unable to pull the images
Build step 'Execute shell' marked build as failure
``` See these errors. https://logs.hyperledger.org/production/vex-yul-hyp-jenkins-3/fabric-verify-end-2-end-x86_64/10734/console.log.gz Connections issues?
rameshthoomu (Mon, 20 Nov 2017 14:06:15 GMT):
@boliang curl failed to download thirdparty kafka reference.
```
curl: (22) The requested URL returned error: 404 Not Found
```
rameshthoomu (Mon, 20 Nov 2017 14:06:22 GMT):
Pls re-trigger..
boliang (Mon, 20 Nov 2017 14:10:38 GMT):
Yep. Failed twice today. Wondering whether the server is not stable. Have re triggered
rameshthoomu (Mon, 20 Nov 2017 14:11:44 GMT):
let me check
boliang (Mon, 20 Nov 2017 14:14:45 GMT):
Thanks~
rameshthoomu (Mon, 20 Nov 2017 14:15:43 GMT):
it seems kafka `10.10.2.0` version has been archived .. http://www-us.apache.org/dist/kafka/
rameshthoomu (Mon, 20 Nov 2017 14:17:03 GMT):
Can you please create JIRA bug for this.. I will fix this now
boliang (Mon, 20 Nov 2017 14:23:59 GMT):
Sure
rameshthoomu (Mon, 20 Nov 2017 14:51:11 GMT):
@boliang https://gerrit.hyperledger.org/r/#/c/15593/
rameshthoomu (Mon, 20 Nov 2017 18:53:18 GMT):
@boliang please rebase your patch.. Kafka version issue has been fixed..
boliang (Tue, 21 Nov 2017 01:55:45 GMT):
@rameshthoomu Thanks. It works.
philviana (Tue, 21 Nov 2017 02:42:41 GMT):
Has joined the channel.
philviana (Tue, 21 Nov 2017 02:53:12 GMT):
@rameshthoomu I can't compile the `release` version of the code due to what seems to be the same problem (only difference is version):
```Step 2/10 : ENV SCALA_VERSION 2.11 KAFKA_VERSION 0.9.0.1 KAFKA_DOWNLOAD_SHA1 FC9ED9B663DD608486A1E56197D318C41813D326
---> Using cache
---> f2dc24a8d9e6
Step 3/10 : RUN curl -fSL "http://www-us.apache.org/dist/kafka/0.9.0.1/kafka_${SCALA_VERSION}-${KAFKA_VERSION}.tgz" -o kafka_${SCALA_VERSION}-${KAFKA_VERSION}.tgz && echo "${KAFKA_DOWNLOAD_SHA1} kafka_${SCALA_VERSION}-${KAFKA_VERSION}.tgz" | sha1sum -c - && tar xfz kafka_"$SCALA_VERSION"-"$KAFKA_VERSION".tgz -C /opt && mv /opt/kafka_"$SCALA_VERSION"-"$KAFKA_VERSION" /opt/kafka && rm kafka_"$SCALA_VERSION"-"$KAFKA_VERSION".tgz
---> Running in 3b839369abb4
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (22) The requested URL returned error: 404 Not Found
```
philviana (Tue, 21 Nov 2017 02:53:24 GMT):
v0.9.0.1 is no longer available.
philviana (Tue, 21 Nov 2017 02:53:36 GMT):
as we can see here: http://www-us.apache.org/dist/kafka/
philviana (Tue, 21 Nov 2017 03:00:52 GMT):
I will add the info to FAB-7054
rameshthoomu (Tue, 21 Nov 2017 03:04:40 GMT):
@philviana this patch is waiting for merge. https://gerrit.hyperledger.org/r/#/c/15599/
rameshthoomu (Tue, 21 Nov 2017 03:04:48 GMT):
Will let you know once done..
philviana (Tue, 21 Nov 2017 03:48:12 GMT):
@rameshthoomu thanks. So `master` is merged into `release`? Is the branching model documented somewhere?
rameshthoomu (Tue, 21 Nov 2017 03:50:06 GMT):
not today..
rameshthoomu (Tue, 21 Nov 2017 03:50:19 GMT):
let me see if I can find any documentation on branching stuff.
rameshthoomu (Tue, 21 Nov 2017 14:31:59 GMT):
@philviana found this https://wiki.hyperledger.org/community/release_taxonomy
cbf (Tue, 21 Nov 2017 14:48:48 GMT):
hi @rjones could you please create a repo for the fabric-evm chaincode per https://jira.hyperledger.org/browse/FAB-6590
harsha (Tue, 21 Nov 2017 14:49:32 GMT):
Hi @rameshthoomu request you to share your observation on fabric-ca|fabric UT for ppc64le.
rameshthoomu (Tue, 21 Nov 2017 15:02:42 GMT):
Hi @harsha .. I have been working on this in sandbox.. After couple of fixes, it's seems fabric-ca and fabric unit-tests are working as expected on power nodes..
rameshthoomu (Tue, 21 Nov 2017 15:03:32 GMT):
I will update average build time on power nodes and results in https://jira.hyperledger.org/browse/FAB-5463
harsha (Tue, 21 Nov 2017 15:09:55 GMT):
Thanks @rameshthoomu
rjones (Tue, 21 Nov 2017 19:12:06 GMT):
@cbf I asked a question WRT repo name in FAB-6590
rjones (Tue, 21 Nov 2017 19:12:06 GMT):
@cbf I asked a question WRT repo name in FAB-6509
cbf (Tue, 21 Nov 2017 22:07:37 GMT):
fabric-chaincode-evm
rjones (Tue, 21 Nov 2017 23:30:34 GMT):
@cbf done
cbf (Wed, 22 Nov 2017 14:06:32 GMT):
@rjones thanks!
jackeyliliang (Fri, 24 Nov 2017 02:57:32 GMT):
Has joined the channel.
MohitYadav2317 (Fri, 24 Nov 2017 07:10:42 GMT):
Has joined the channel.
jimthematrix (Fri, 24 Nov 2017 14:40:21 GMT):
@rjones, @jwagantall the Fabric maintainers have voted for fabric-sdk-node repo using its own list of maintainers: https://gerrit.hyperledger.org/r/#/c/15647/, can the ACL changes be made accordingly? thanks!
rjones (Fri, 24 Nov 2017 18:15:27 GMT):
@jimthematrix please send email to helpdesk@hyperledger.org and I’ll knock it out
rjones (Fri, 24 Nov 2017 21:09:12 GMT):
@jimthematrix is this in addition to the fabric committers, or does this replace the fabric committers? is it a superset, or a distinct set? thank you
rjones (Fri, 24 Nov 2017 21:09:12 GMT):
@jimthematrix is this in addition to the fabric committers, or does this replace the fabric committers? is it a superset, or a distinct set? thank yoy
jimthematrix (Fri, 24 Nov 2017 23:57:50 GMT):
@rjones the new list is a replacement, so it’s a distinct set, thanks!
baoyangc (Sun, 26 Nov 2017 16:43:14 GMT):
Has joined the channel.
himani.arora (Mon, 27 Nov 2017 11:39:21 GMT):
Has joined the channel.
jimthematrix (Mon, 27 Nov 2017 14:41:48 GMT):
@rjones just sent an email to helpdesk@hyperledger.org requesting the ACL changes, thanks!
rjones (Mon, 27 Nov 2017 21:50:24 GMT):
@jimthematrix done - the new committers should have access
jimthematrix (Mon, 27 Nov 2017 21:51:19 GMT):
just checked quickly, I'm now part of this new group `ldap/hyperledger-gerrit-fabric-sdk-node-committers`
jimthematrix (Mon, 27 Nov 2017 21:51:26 GMT):
thanks @rjones !
rjones (Mon, 27 Nov 2017 21:51:42 GMT):
yup, you all should be
jimthematrix (Mon, 27 Nov 2017 21:53:49 GMT):
@bretharrison @zhaochy @JonathanLevi @smithbk welcome to the node SDK maintainer group! @cbf @mastersingh24 welcome back ;-) ^^^
smithbk (Mon, 27 Nov 2017 21:53:49 GMT):
Has joined the channel.
zhaochy (Mon, 27 Nov 2017 21:53:49 GMT):
Has joined the channel.
bretharrison (Mon, 27 Nov 2017 21:53:50 GMT):
Has joined the channel.
cbf (Mon, 27 Nov 2017 23:09:02 GMT):
;-)
prabhat.kashyap (Tue, 28 Nov 2017 05:57:23 GMT):
Has joined the channel.
lehors (Wed, 29 Nov 2017 20:55:13 GMT):
hi there, it looks like there is a problem with the builds
lehors (Wed, 29 Nov 2017 20:55:33 GMT):
I've a couple of CRs that are failing for "unknown reasons"
lehors (Wed, 29 Nov 2017 20:55:43 GMT):
looking into the log (https://jenkins.hyperledger.org/job/fabric-verify-end-2-end-x86_64/10958/console) I see:
lehors (Wed, 29 Nov 2017 20:56:27 GMT):
17:55:13 ERROR !!!! Unable to pull the images
17:55:13 Build step 'Execute shell' marked build as failure
rjones (Wed, 29 Nov 2017 21:02:06 GMT):
there was a fire drill earlier this week, are the CRs on the tip of whatever branch?
rameshthoomu (Wed, 29 Nov 2017 21:04:52 GMT):
@lehors could be a network glitch..
```
00:23:49.456 An HTTP request took too long to complete. Retry with --verbose to obtain debug information.
00:23:49.456 If you encounter this issue regularly because of slow network conditions, consider setting COMPOSE_HTTP_TIMEOUT to a higher value (current value: 60).
```
lehors (Thu, 30 Nov 2017 15:11:18 GMT):
well, I've tried several times but it seems to fail every time even though I can't see how my change - only to the doc! - has anything to do with the failure
lehors (Thu, 30 Nov 2017 15:11:24 GMT):
https://gerrit.hyperledger.org/r/#/c/15727/
rameshthoomu (Thu, 30 Nov 2017 15:28:14 GMT):
@lehors as per the behave logs, peers are not connecting https://jenkins.hyperledger.org/job/fabric-verify-behave-x86_64/13338/
rameshthoomu (Thu, 30 Nov 2017 15:29:10 GMT):
@jeffgarratt could you please look into this issue.. It seems inconsistently this test case is failing
jeffgarratt (Thu, 30 Nov 2017 15:29:21 GMT):
will take a look asap
rameshthoomu (Thu, 30 Nov 2017 15:29:57 GMT):
thanks
jeffgarratt (Thu, 30 Nov 2017 18:39:33 GMT):
@rameshthoomu @lehors from what I can see it is taking longer than 2 seconds to create the channel through the orderer
jeffgarratt (Thu, 30 Nov 2017 18:40:29 GMT):
```36m2017-11-30 14:56:05.411 UTC [orderer/common/broadcast] Handle -> DEBU 293[0m [channel: com.acme.blockchain.jdoe.channel1] Broadcast is processing config update message from 172.18.0.1:49116
jeffgarratt (Thu, 30 Nov 2017 18:40:29 GMT):
```2017-11-30 14:56:05.411 UTC [orderer/common/broadcast] Handle -> DEBU 293[0m [channel: com.acme.blockchain.jdoe.channel1] Broadcast is processing config update message from 172.18.0.1:49116
jeffgarratt (Thu, 30 Nov 2017 18:40:34 GMT):
that is the start of attempt
jeffgarratt (Thu, 30 Nov 2017 18:41:18 GMT):
```2017-11-30 14:56:08.155 UTC [orderer/commmon/multichannel] newChain -> INFO 545[0m Created and starting new chain com.acme.blockchain.jdoe.channel1
jeffgarratt (Thu, 30 Nov 2017 18:41:42 GMT):
that is the channel ready notice... appears to be 2.8 seconds (over the 2s wait indicated in BDD)
jeffgarratt (Thu, 30 Nov 2017 18:42:00 GMT):
that seems like in inordinate amount of time to me
jeffgarratt (Thu, 30 Nov 2017 18:42:21 GMT):
I would say either the CI env is sloooooowwwww
jeffgarratt (Thu, 30 Nov 2017 18:42:21 GMT):
I would say the CI env is sloooooowwwww for some reason on this run
jeffgarratt (Thu, 30 Nov 2017 18:43:07 GMT):
i.e. if CI is taking over 2 secs on this, it will fail as prescribed.
jeffgarratt (Thu, 30 Nov 2017 18:45:00 GMT):
from the BDD...
jeffgarratt (Thu, 30 Nov 2017 18:45:01 GMT):
``` And I wait "
jeffgarratt (Thu, 30 Nov 2017 18:45:09 GMT):
that is currently set to 2s I believe
rameshthoomu (Thu, 30 Nov 2017 18:58:32 GMT):
Thanks @jeffgarratt
jeffgarratt (Thu, 30 Nov 2017 18:58:50 GMT):
your most welcome @rameshthoomu :)
lehors (Thu, 30 Nov 2017 19:26:21 GMT):
That's actually what I thought: is slow. So, the question is why.
lehors (Thu, 30 Nov 2017 19:27:02 GMT):
Thanks @jeffgarratt
jeffgarratt (Thu, 30 Nov 2017 19:27:41 GMT):
exactly... not sure.. though I asssume CI hiccups every now and then
rameshthoomu (Thu, 30 Nov 2017 19:38:25 GMT):
@rjones @jwagantall any inputs on CI env slowness..
rameshthoomu (Thu, 30 Nov 2017 19:38:25 GMT):
@rjones @jwagantall any inputs on CI env is slowness..
jwagantall (Thu, 30 Nov 2017 19:39:40 GMT):
noting has change internally.. i wonder if this is an issue with the provider rather than actual Jenkins
jwagantall (Thu, 30 Nov 2017 19:39:45 GMT):
ill take a peek
rjones (Thu, 30 Nov 2017 19:48:33 GMT):
Something has changed @jwagantall
rjones (Thu, 30 Nov 2017 19:48:45 GMT):
We’re on cattle cloud not pets
jwagantall (Thu, 30 Nov 2017 19:49:47 GMT):
oh .. thanks Ry,, when did you guys started seeing the slowdowns?
rameshthoomu (Thu, 30 Nov 2017 20:08:19 GMT):
@jwagantall intermittently but I see build time out is increased since yesterday or a day before.. Not exact dates.. see the trend here https://jenkins.hyperledger.org/view/fabric/job/fabric-verify-end-2-end-x86_64/buildTimeTrend
rameshthoomu (Thu, 30 Nov 2017 20:08:19 GMT):
@jwagantall intermittently but I see build time is increased since yesterday or a day before.. Not exact date.. see the trend here https://jenkins.hyperledger.org/view/fabric/job/fabric-verify-end-2-end-x86_64/buildTimeTrend
iamprem (Thu, 30 Nov 2017 21:56:29 GMT):
Has joined the channel.
bizhenchao1201 (Sun, 03 Dec 2017 09:34:45 GMT):
Has joined the channel.
yacovm (Mon, 04 Dec 2017 22:21:11 GMT):
@rameshthoomu why are we doing:
> FAB-7301 disable fabric-verify-s390x job
?
rjones (Tue, 05 Dec 2017 17:23:01 GMT):
@yacovm read the commentary on 7301. I had the same question.
yacovm (Tue, 05 Dec 2017 18:32:10 GMT):
@cbf ?
yacovm (Tue, 05 Dec 2017 18:33:45 GMT):
I dont think thats a good idea... Maintainers check CI jobs anyway. We know roughly what UTs are brittle and what are not. Disabling z ci makes no sense IMO especially since it runs faster than the x86 one
yacovm (Tue, 05 Dec 2017 18:33:45 GMT):
I dont think thats a good idea... Maintainers check CI jobs anyway. We know roughly what UTs are brittle and what are not. Disabling *especially* z ci makes no sense IMO especially since it runs faster than the x86 one
yacovm (Tue, 05 Dec 2017 18:33:45 GMT):
I dont think thats a good idea... Maintainers check CI jobs anyway. We know roughly what UTs are brittle and what are not. Disabling *especially* z ci makes no sense IMO since it runs faster than the x86 one
yacovm (Tue, 05 Dec 2017 18:34:48 GMT):
It doesnt really shorten the overall ci round
cbf (Wed, 06 Dec 2017 11:03:24 GMT):
@yacovm as for disabling Z verify... basically, the thinking is that we would only run it daily and just run the x86 verify on each CR
cbf (Wed, 06 Dec 2017 11:03:46 GMT):
there are few times when the change is actually going to be problematic only for Z
cbf (Wed, 06 Dec 2017 11:03:49 GMT):
(or P)
yacovm (Wed, 06 Dec 2017 11:03:52 GMT):
what do you get out of it besides saving electricity?
cbf (Wed, 06 Dec 2017 11:04:06 GMT):
but the motivation is basically to put CI on aa diet
cbf (Wed, 06 Dec 2017 11:04:06 GMT):
but the motivation is basically to put CI on a diet
yacovm (Wed, 06 Dec 2017 11:04:14 GMT):
hmm, why not do the opposite then?
yacovm (Wed, 06 Dec 2017 11:04:18 GMT):
run z and not x?
yacovm (Wed, 06 Dec 2017 11:04:21 GMT):
z is faster
yacovm (Wed, 06 Dec 2017 11:04:29 GMT):
x is always the "long tail"
troyronda (Thu, 07 Dec 2017 17:41:24 GMT):
Hi all - are there any plans to post 1.1 snapshot docker images to a registry? I'm trying to figure out a better way to enable earlier SDK development of features (including CI) that have been merged into fabric but not yet tagged.
troyronda (Thu, 07 Dec 2017 17:41:24 GMT):
Hi all - are there any plans to post snapshot docker images to a registry? I'm trying to figure out a better way to enable earlier SDK development of features (including CI) that have been merged into fabric but not yet tagged.
troyronda (Thu, 07 Dec 2017 17:41:48 GMT):
(e.g., mutual TLS)
rameshthoomu (Thu, 07 Dec 2017 18:12:41 GMT):
@troyronda yes as part of daily build we publish DEV_STABLE tagged images nexus docker registry https://nexus3.hyperledger.org/#browse/browse/components:docker.snapshot
rameshthoomu (Thu, 07 Dec 2017 18:12:41 GMT):
@troyronda yes as part of daily build we publish DEV_STABLE tagged images to nexus docker registry https://nexus3.hyperledger.org/#browse/browse/components:docker.snapshot
alvaradojl (Fri, 08 Dec 2017 14:03:52 GMT):
Has joined the channel.
nehirakdag (Sun, 10 Dec 2017 04:55:54 GMT):
Has joined the channel.
guolidong (Tue, 12 Dec 2017 06:02:27 GMT):
Has joined the channel.
Norberthu (Wed, 13 Dec 2017 09:56:03 GMT):
Has joined the channel.
rickr (Sat, 16 Dec 2017 00:41:41 GMT):
anyone seeing any issues with Hyperledger builders ? running real slow ?
rameshthoomu (Sat, 16 Dec 2017 00:47:53 GMT):
any build references ?
rickr (Sat, 16 Dec 2017 00:50:18 GMT):
https://jenkins.hyperledger.org/job/fabric-sdk-java-verify-x86_64/1422/consoleFull
rameshthoomu (Sat, 16 Dec 2017 00:52:51 GMT):
can you check this line
```
00:32:24.749 2017-12-16 00:31:50,160 pool-16-thread-1 DEBUG Channel:3469 - Force removing transaction listener after 1200000 ms for transaction 19cbee6673f1d6ba8f798a9f91b6a069d8a0e2bef07a8fb8521d7292a47311e9. Non reporting event hubs:. Non reporting peers: peer0.org1.example.com,peer1.org1.example.com. sweep timeout: true, fired: false, future done:false
```
rickr (Sat, 16 Dec 2017 00:53:10 GMT):
y
rickr (Sat, 16 Dec 2017 00:53:14 GMT):
but y?
rickr (Sat, 16 Dec 2017 00:53:18 GMT):
:)
rickr (Sat, 16 Dec 2017 00:53:30 GMT):
Not seeing it locally
rameshthoomu (Sat, 16 Dec 2017 00:54:12 GMT):
ok.
rameshthoomu (Sat, 16 Dec 2017 00:56:10 GMT):
@rickr is this consistently happening.. I don't see any issues with build latency issues..
rameshthoomu (Sat, 16 Dec 2017 00:56:20 GMT):
re-trigger the job and see
rickr (Sat, 16 Dec 2017 03:39:17 GMT):
figured out timing problem in code.
rickr (Sat, 16 Dec 2017 03:39:17 GMT):
figured it out timing problem in code.
iyerrama25 (Sun, 17 Dec 2017 17:33:53 GMT):
Has joined the channel.
zhishui (Tue, 19 Dec 2017 08:09:24 GMT):
Has joined the channel.
lehors (Thu, 21 Dec 2017 10:53:50 GMT):
hi there, I know the CI supports a bunch of commands through comments, such as reverify, rebuild-behave, etc. Are these commands documented somewhere?
lehors (Thu, 21 Dec 2017 11:12:17 GMT):
ok, found the answer: the code :-)
lehors (Thu, 21 Dec 2017 11:13:57 GMT):
seriously though, the ci-management doc could use a bit of love
lehors (Thu, 21 Dec 2017 11:14:11 GMT):
it still refers to ci-skip!
lehors (Thu, 21 Dec 2017 11:14:27 GMT):
which was removed back in April...
lehors (Thu, 21 Dec 2017 18:13:08 GMT):
patch submitted and already merged - thanks @rjones!
rjones (Thu, 21 Dec 2017 18:25:44 GMT):
@lehors I'm willing to try adding the `ci-skip` plugin again, if you think it's worth it. I feel it was probably unrightly maligned previously
lehors (Thu, 21 Dec 2017 18:26:21 GMT):
oh, I would like that
lehors (Thu, 21 Dec 2017 18:27:02 GMT):
I "often" patch the doc and find very silly to see the build kicking in when it is totally irrelevant
lehors (Thu, 21 Dec 2017 18:27:40 GMT):
it takes away resources that would be better use for other builds that really matter
rjones (Thu, 21 Dec 2017 18:30:17 GMT):
OK, installed. Let's see how it goes
rjones (Thu, 21 Dec 2017 18:31:17 GMT):
At the end of the day, though, your final commit would not have that in the commit message, right? I _feel_ having the commit log littered with `[ci skip]` messages would be ugly
lehors (Thu, 21 Dec 2017 22:22:59 GMT):
that is an interesting point
lehors (Thu, 21 Dec 2017 22:23:28 GMT):
at the same time maybe it is a good thing to have it in the log
lehors (Thu, 21 Dec 2017 22:23:54 GMT):
this can serve as a reminder that the commit wasn't checked against CI
lehors (Thu, 21 Dec 2017 22:24:44 GMT):
it seems that in case of problems down the line this might be help an investigation
lehors (Thu, 21 Dec 2017 22:29:01 GMT):
hmm, it doesn't seem to work, see https://gerrit.hyperledger.org/r/#/c/16407/
lehors (Thu, 21 Dec 2017 22:29:26 GMT):
what am I doing wrong?
rjones (Thu, 21 Dec 2017 22:29:33 GMT):
I might need to restart Jenkins
lehors (Thu, 21 Dec 2017 22:29:45 GMT):
ah...
lehors (Thu, 21 Dec 2017 22:29:48 GMT):
oh well
lehors (Thu, 21 Dec 2017 22:30:06 GMT):
it's ok, this can wait
lehors (Thu, 21 Dec 2017 22:30:29 GMT):
I'm done for now
lehors (Thu, 21 Dec 2017 22:30:32 GMT):
ttyl
rjones (Thu, 21 Dec 2017 22:30:33 GMT):
ok
rjones (Thu, 21 Dec 2017 22:33:36 GMT):
@lehors here is the source: https://github.com/jenkinsci/ci-skip-plugin
rjones (Thu, 21 Dec 2017 22:33:44 GMT):
last release was 4 years ago
rjones (Thu, 21 Dec 2017 22:34:26 GMT):
https://github.com/jenkinsci/ci-skip-plugin/blob/master/lib/ci_skip/matcher.rb#L8
rjones (Thu, 21 Dec 2017 22:34:26 GMT):
https://github.com/jenkinsci/ci-skip-plugin/blob/master/lib/ci_skip/matcher.rb
keerthiGiridhari (Fri, 22 Dec 2017 07:50:03 GMT):
Has joined the channel.
Roger (Wed, 27 Dec 2017 03:28:45 GMT):
Has joined the channel.
elias_p (Sat, 30 Dec 2017 10:32:41 GMT):
Has joined the channel.
allonblocks21 (Thu, 04 Jan 2018 11:05:25 GMT):
Has joined the channel.
tongli (Thu, 04 Jan 2018 13:57:31 GMT):
@rjones, good morning, got a question for you. On our jenkins system, conditional step can have builders such as Trigger/call builds on other projects
tongli (Thu, 04 Jan 2018 13:57:45 GMT):
@rjones, see this picture.
tongli (Thu, 04 Jan 2018 13:57:58 GMT):
Screen Shot 2018-01-04 at 8.56.50 AM.png
tongli (Thu, 04 Jan 2018 13:58:16 GMT):
please see the bottom of the picture.
tongli (Thu, 04 Jan 2018 13:58:59 GMT):
On my own jenkins system, I do not see as many builders , I must have missed something plugins or settings, can you shed a bit light on that? Thanks.
mastersingh24 (Thu, 04 Jan 2018 15:27:10 GMT):
what is this test: https://jenkins.hyperledger.org/job/fabric-verify-behave-tests-x86_64/234/ ?
mastersingh24 (Thu, 04 Jan 2018 15:28:28 GMT):
CR https://gerrit.hyperledger.org/r/16555 - behave failed originally and "rebuild-behave" triggered two tests
mastersingh24 (Thu, 04 Jan 2018 15:28:41 GMT):
@rameshthoomu - any ideas here? ^^^^^^
rameshthoomu (Thu, 04 Jan 2018 15:29:04 GMT):
let me check
rameshthoomu (Thu, 04 Jan 2018 15:30:22 GMT):
will fix this.. Yesterday I have added this comment based trigger condition in the above job..
rameshthoomu (Thu, 04 Jan 2018 15:31:01 GMT):
same comment added in another job also..
jtclark (Thu, 04 Jan 2018 16:15:55 GMT):
User User_1 added by jtclark.
rjones (Thu, 04 Jan 2018 17:25:33 GMT):
So everyone is aware: mitigations for the recent security bugs will slow our CI processes across the board on x86 builds
tongli (Fri, 05 Jan 2018 00:05:20 GMT):
@rjones, good evening, wonder if you see my earlier question on jenkins?
rjones (Fri, 05 Jan 2018 00:15:50 GMT):
@tongli I did, I don't understand your question.
rjones (Fri, 05 Jan 2018 00:16:15 GMT):
are you asking for a list of plugins that I have installed?
tongli (Fri, 05 Jan 2018 00:16:47 GMT):
@rjones, oh, ok. The picture I uploaded shows builders available when you use conditional step plugin .
rjones (Fri, 05 Jan 2018 00:17:02 GMT):
in what context?
tongli (Fri, 05 Jan 2018 00:17:23 GMT):
but the list on my own test jenkins only show smaller number of builders, which does not include Trigger/call builds on other projects.
tongli (Fri, 05 Jan 2018 00:17:59 GMT):
@rjones, any job which uses conditional step plugin.
tongli (Fri, 05 Jan 2018 00:19:36 GMT):
if you have a list of plugins that you installed onto sandbox jenkins, I can compare with mine to see what I might have missed.
rjones (Fri, 05 Jan 2018 00:19:57 GMT):
when I search for that exact string, and click a couple times, I end up here: https://plugins.jenkins.io/parameterized-trigger
rjones (Fri, 05 Jan 2018 00:20:29 GMT):
I have not grabbed the source for it to see if that string is in there, but when I run into problems like this, I find searching on exact strings to be useful
tongli (Fri, 05 Jan 2018 00:20:51 GMT):
@rjones, hmmm, I do not think it related to that.
tongli (Fri, 05 Jan 2018 00:21:25 GMT):
Here is how you see the list.
rjones (Fri, 05 Jan 2018 00:21:42 GMT):
yeah I have about a million plugins.
rjones (Fri, 05 Jan 2018 00:21:48 GMT):
I'm not copy pasting all this spew.
tongli (Fri, 05 Jan 2018 00:22:01 GMT):
from any job which uses conditional step plugin,
tongli (Fri, 05 Jan 2018 00:24:11 GMT):
after Run? you will see Builder which shows a dropdown box.
rjones (Fri, 05 Jan 2018 00:24:18 GMT):
```parameterized-trigger-plugin ry$ grep -R "call builds" *
src/main/java/hudson/plugins/parameterizedtrigger/TriggerBuilder.java: return "Trigger/call builds on other projects";
```
rjones (Fri, 05 Jan 2018 00:24:38 GMT):
so that string is in the plugin I pointed you to. I have that plugin installed.
tongli (Fri, 05 Jan 2018 00:25:20 GMT):
oh, ok, let me verify that if I have it installed. will confirm. thanks.
tongli (Fri, 05 Jan 2018 00:33:00 GMT):
@rjones, confirmed. That is the plugin, I installed that, and the option appears in the builder list. Thanks.
rjones (Fri, 05 Jan 2018 00:33:12 GMT):
you're welcome!
SanketPanchamia (Tue, 09 Jan 2018 11:55:01 GMT):
Has joined the channel.
kostas (Tue, 09 Jan 2018 15:28:01 GMT):
Is there a verb/command to allow me to re-trigger only a `fabric-verify-s390x` job?
rameshthoomu (Tue, 09 Jan 2018 15:32:07 GMT):
`rebuild-s390x`
kostas (Tue, 09 Jan 2018 15:35:53 GMT):
Ah, makes sense. Thanks Ramesh.
rameshthoomu (Wed, 10 Jan 2018 15:36:57 GMT):
@jeffgarratt please check this when you get some time FAB-7683
jeffgarratt (Wed, 10 Jan 2018 15:37:07 GMT):
will do
jeffgarratt (Wed, 10 Jan 2018 15:53:32 GMT):
@rameshthoomu is logs forced == TRUE?
jeffgarratt (Wed, 10 Jan 2018 15:54:06 GMT):
I would assume so, in which case you are hitting a bad output message, but there was no failure.
rameshthoomu (Wed, 10 Jan 2018 15:54:52 GMT):
yes it is set to force..
jeffgarratt (Wed, 10 Jan 2018 15:54:59 GMT):
see https://github.com/hyperledger/fabric/blob/master/bddtests/environment.py#L47-L48
jeffgarratt (Wed, 10 Jan 2018 15:55:11 GMT):
so the test passed, but the output message is poor, but your good to go
rameshthoomu (Wed, 10 Jan 2018 15:55:22 GMT):
I don't see a test failure but the message is confusing..
jeffgarratt (Wed, 10 Jan 2018 15:55:27 GMT):
exactly
rameshthoomu (Wed, 10 Jan 2018 15:55:27 GMT):
yes got it.
jeffgarratt (Wed, 10 Jan 2018 15:55:31 GMT):
poorly state message
rameshthoomu (Wed, 10 Jan 2018 15:55:40 GMT):
nope..
tongli (Wed, 10 Jan 2018 20:29:32 GMT):
@rjones, we are splitting the big job 0f fabric build,testing into smaller ones, one issue we have is that all these jobs use same gerrit trigger, the verification comes from same user. Is it possible we create multiple gerrit servers which use different credentials? If we can do that, then each patch set will post different verification votes.
rjones (Thu, 11 Jan 2018 00:48:31 GMT):
@tongli I'm out for the next few weeks, but what @jwagantall and @jeremyphelps could investigate would be adding a custom vote class - additional columns to the gerrit UI, with distinct jobs voting on different states.
tongli (Thu, 11 Jan 2018 01:06:27 GMT):
@rjones, thanks for the info, I will talk to them. thanks.
C0rWin (Thu, 11 Jan 2018 09:51:46 GMT):
@rameshthoomu https://jira.hyperledger.org/browse/FAB-7694
C0rWin (Thu, 11 Jan 2018 09:52:24 GMT):
@rameshthoomu per our conversation I've opened a JIRA item to reflect the need to temporarily disable SDK related e2e test to make it possible to bring new changes
C0rWin (Thu, 11 Jan 2018 09:52:44 GMT):
once SDK will update required API tests could be re-enabled
C0rWin (Thu, 11 Jan 2018 09:53:10 GMT):
@rameshthoomu could you please ping me once tests will be disabled so I will trigger rebuild for my CR?
manu (Thu, 11 Jan 2018 15:35:51 GMT):
Has joined the channel.
Maria (Thu, 11 Jan 2018 16:03:41 GMT):
Has joined the channel.
rameshthoomu (Thu, 11 Jan 2018 16:35:20 GMT):
@C0rWin disabled Node SDK & Java SDK e2e temporarily.. Will trigger your job now
C0rWin (Thu, 11 Jan 2018 16:35:44 GMT):
Thanks
tongli (Thu, 11 Jan 2018 18:51:45 GMT):
@jwagantall @JeremyMet hi, we have split the big build/test job into smaller jobs, but we are using same gerrit user for posting job results. I would like to know if it is possible to create few more gerrit users so that different job will be using different gerrit users to post build results against a patch set?
JeremyMet (Thu, 11 Jan 2018 18:51:46 GMT):
Has joined the channel.
tongli (Thu, 11 Jan 2018 18:56:35 GMT):
@jwagantall @JeremyMet or at least customized Gerrit Trigger which use different labels.
jwagantall (Thu, 11 Jan 2018 18:57:58 GMT):
@tongli i think the different users might be a little bit of a hassle.. do you want to use different gerrit triggers depending on the job? for example "remerge-fabric" ?
tongli (Thu, 11 Jan 2018 18:58:43 GMT):
@jwagantall yeah. I think too many users may not be a good idea. probably multiple gerrit trigger server with customized label?
tongli (Thu, 11 Jan 2018 18:59:34 GMT):
each job uses a different gerrit trigger server which uses customized label. so that the vote will not over write each other?
jwagantall (Thu, 11 Jan 2018 19:06:26 GMT):
@tongli can you give me an example? is this getting overwritten now becuase we have the different architectures using the same trigger? would it be better to add a trigger like "recheck-
tongli (Thu, 11 Jan 2018 19:08:21 GMT):
@jwagantall I am not sure. currently when we use same user (same gerrit trigger) on multiple jobs, the vote from different jobs overwrite each other's verify vote.
tongli (Thu, 11 Jan 2018 19:08:26 GMT):
see the picture
tongli (Thu, 11 Jan 2018 19:08:40 GMT):
Screen Shot 2018-01-11 at 2.07.49 PM.png
tongli (Thu, 11 Jan 2018 19:09:03 GMT):
ideally, different jobs against same patch set have different verified votes.
tongli (Thu, 11 Jan 2018 19:09:32 GMT):
that is the goal. I am not sure which way is the best. I am sure if we use different users, then it will work. but that is probably too much.
tongli (Thu, 11 Jan 2018 19:10:39 GMT):
either it is Verified label be different or the user be different, that is fine, as long as different jobs do not overwrite each other's vote, then we are good.
tongli (Thu, 11 Jan 2018 19:19:24 GMT):
@jwagantall what do you think?
tongli (Thu, 11 Jan 2018 21:59:52 GMT):
@jwagantall please let me know what you think.
jwagantall (Thu, 11 Jan 2018 22:01:03 GMT):
@tongli I need to check if we can do something similar without the need of different users... not sure if its possible with the different users... let me investigate more on it.. in the meantime is there any RT ticket for tracking this task?
tongli (Thu, 11 Jan 2018 22:01:46 GMT):
@jwagantall there is none. where should I go to create one?
jwagantall (Thu, 11 Jan 2018 22:03:10 GMT):
yes pls... i will asign it to myself
tongli (Thu, 11 Jan 2018 22:03:26 GMT):
jira or somewhere else?
rjones (Thu, 11 Jan 2018 22:06:07 GMT):
@tongli @jwagantall use custom labels https://gerrit-review.googlesource.com/Documentation/config-labels.html#label_custom
jwagantall (Thu, 11 Jan 2018 22:06:34 GMT):
yea.. that's what @tongli also suggested
rjones (Thu, 11 Jan 2018 22:06:42 GMT):
Just create a label per test tranche
rjones (Thu, 11 Jan 2018 22:07:26 GMT):
I keep seeing the multiple user thing coming up
tongli (Thu, 11 Jan 2018 22:08:15 GMT):
@rjones, so we just need to propose one label per build, and create a gerrit trigger server per label, in the customize gerrit review command field adding the label, is that what you suggest?
rjones (Thu, 11 Jan 2018 22:09:24 GMT):
How many builds fire at once? Each slice of builds should be a label
tongli (Thu, 11 Jan 2018 22:10:04 GMT):
for fabric, we are thinking about 4 builds, they do not fire up at the same time.
tongli (Thu, 11 Jan 2018 22:10:19 GMT):
new patch set only triggers one build job.
tongli (Thu, 11 Jan 2018 22:10:56 GMT):
based on that build results, other jobs get triggered. if the first job fails, no other jobs get triggered.
rjones (Thu, 11 Jan 2018 22:11:21 GMT):
This is something to mess with in the sandbox project
rjones (Thu, 11 Jan 2018 22:11:36 GMT):
Since rule errors the affect nobody
tongli (Thu, 11 Jan 2018 22:11:41 GMT):
but if when all the jobs finish, each job should vote on its own label.
tongli (Thu, 11 Jan 2018 22:11:50 GMT):
so that we do not overwrite each other.
tongli (Thu, 11 Jan 2018 22:12:38 GMT):
@rjones, adding custome label requires changes to gerrit project, I do not think we can do that on sandbox.
rjones (Thu, 11 Jan 2018 22:16:18 GMT):
That isn't what I'm saying. Please outline exactly what labels you want-name, ID, in an email to helpdesk@hyper... And it will be before the right people
tongli (Thu, 11 Jan 2018 22:16:41 GMT):
oh. i c.
tongli (Thu, 11 Jan 2018 22:17:13 GMT):
so we are taking the custom label route, can you confirm that?
rjones (Thu, 11 Jan 2018 22:17:41 GMT):
No I can't confirm that.
rjones (Thu, 11 Jan 2018 22:17:53 GMT):
There may be another solution.
rjones (Thu, 11 Jan 2018 22:18:15 GMT):
Opening the ticket will start the conversation with a wider audience
rjones (Thu, 11 Jan 2018 22:18:15 GMT):
Opening the ticket will start the conversation with a roofer siding
tongli (Thu, 11 Jan 2018 22:18:38 GMT):
all right, I will open a ticket and put the requirement in.
rjones (Thu, 11 Jan 2018 22:18:46 GMT):
Thank you
tongli (Thu, 11 Jan 2018 22:18:46 GMT):
thanks very much.
hightall (Fri, 12 Jan 2018 06:43:39 GMT):
Has joined the channel.
hightall (Fri, 12 Jan 2018 06:44:35 GMT):
hi, I have a question, I make check in local machine is passed, but in jenkins return failed with message grep: /etc/default/sysstat: No such file or directory
hightall (Fri, 12 Jan 2018 06:44:44 GMT):
anybody can help me?
rameshthoomu (Fri, 12 Jan 2018 12:14:46 GMT):
Ignore that error.. above log is coming from postbuild action and we ignore that error. The exact failure might be some other. Could you pls give me the build number or the patch set
latitiah (Tue, 16 Jan 2018 20:57:08 GMT):
@rjones @cbf : who do I need to talk to about adding a "Test" state to the Jira workflow with Pass, Fail, and Not Applicable statuses?
cbf (Tue, 16 Jan 2018 21:31:12 GMT):
@latitiah we will be reorganizing JIRA soon as LF provides us with an expert and we can adapt the flow as needed
javrevasandeep (Wed, 17 Jan 2018 08:16:14 GMT):
Has joined the channel.
Ammu (Thu, 18 Jan 2018 13:35:44 GMT):
Has joined the channel.
grapebaba (Thu, 18 Jan 2018 15:34:12 GMT):
@rjones can you help https://jenkins.hyperledger.org/job/fabric-sdk-py-verify-x86_64/299/
grapebaba (Thu, 18 Jan 2018 15:34:23 GMT):
it works fine in my local
rjones (Thu, 18 Jan 2018 17:43:12 GMT):
@jwagantall @jeremyphelps ^^^
jwagantall (Thu, 18 Jan 2018 17:43:21 GMT):
on it
rjones (Thu, 18 Jan 2018 17:43:22 GMT):
@grapebaba I'm out of the office for a while more
jwagantall (Thu, 18 Jan 2018 17:54:21 GMT):
@grapebaba I am not getting too much information from the logs:
15:29:30 test/integration/ca_test.py ... [ 5%]
15:29:48 test/integration/chaincode_install_test.py ERROR: InvocationError: '/w/workspace/fabric-sdk-py-verify-x86_64/.tox/pylint/bin/py.test --cov=hfc test'
I am checking if this is a problem on the current tip..
jwagantall (Thu, 18 Jan 2018 18:14:43 GMT):
@rameshthoomu are you familiar with this failure? https://jenkins.hyperledger.org/job/fabric-sdk-py-verify-x86_64/300/ looks like it is on the current tip..
rameshthoomu (Thu, 18 Jan 2018 18:17:13 GMT):
checked it already but not sure what is causing
jtclark (Fri, 19 Jan 2018 15:15:42 GMT):
GM all
jtclark (Fri, 19 Jan 2018 15:17:14 GMT):
Just wanted you guys to know that I reviewed the "Getting Started with Fabric CI" documentation with cbf- he was impressed with what he saw, and wants to know if we can "publicize" this documentation here on the #fabric-ci channel as well as the #ci-pipeline channel. Perhaps updating the channel topic in each?
jtclark (Fri, 19 Jan 2018 15:17:44 GMT):
@rameshthoomu, @jwagantall ^
jtclark (Fri, 19 Jan 2018 15:18:49 GMT):
or adding a channel announcement
rameshthoomu (Fri, 19 Jan 2018 15:19:33 GMT):
sounds good.... Could you please share the document here.. Will review and see If I can add few more points or Q&A
jtclark (Fri, 19 Jan 2018 16:04:32 GMT):
sure
jtclark (Fri, 19 Jan 2018 16:07:46 GMT):
https://wiki.hyperledger.org/projects/fabric/fabric_ci_documentation
rameshthoomu (Fri, 19 Jan 2018 16:10:53 GMT):
looks good to me..
rameshthoomu (Fri, 19 Jan 2018 16:11:33 GMT):
I would like to add few questions & answers and update the jobs we run on every patch set
rameshthoomu (Fri, 19 Jan 2018 16:11:53 GMT):
Also, we have to update the reference documents in ci-management repository
rameshthoomu (Fri, 19 Jan 2018 16:12:15 GMT):
I will update this document over this weekend and let you know the update
tongli (Fri, 19 Jan 2018 18:56:18 GMT):
@jwagantall Jessica, any update on the event triggering issue fabric build has?
rameshthoomu (Fri, 19 Jan 2018 18:58:43 GMT):
@tongli initiate this discussion in #ci-pipeline
rameshthoomu (Fri, 19 Jan 2018 19:04:33 GMT):
@ashutosh_kumar looking your comment in FAB-7011, it seems --exclude is for specific rules
rameshthoomu (Fri, 19 Jan 2018 19:07:11 GMT):
but as you know we have to skip few directories from fabric
ashutosh_kumar (Fri, 19 Jan 2018 19:10:17 GMT):
exclude works for directories also , I think. Have you given a try ?
rameshthoomu (Fri, 19 Jan 2018 19:11:16 GMT):
yes I have tried that https://jenkins.hyperledger.org/sandbox/job/fabric-goast-daily-x86_64/11/console
rameshthoomu (Fri, 19 Jan 2018 19:11:39 GMT):
let me check this in detail..
ashutosh_kumar (Fri, 19 Jan 2018 19:19:21 GMT):
ok.
rameshthoomu (Fri, 19 Jan 2018 19:22:16 GMT):
@jyellick I see e2e tests are failing with below error
```
00:10:52.689 2018-01-19 19:12:37.819 UTC [channelCmd] readBlock -> DEBU 00a Got status: &{SERVICE_UNAVAILABLE}
00:10:52.689 Error: proto: Marshal called with nil
```
any help here?
jyellick (Fri, 19 Jan 2018 19:22:49 GMT):
I have a strong suspicion yes
jyellick (Fri, 19 Jan 2018 19:23:24 GMT):
Can you check the version of Kafka in the kafka container?
rameshthoomu (Fri, 19 Jan 2018 19:24:01 GMT):
ok
jyellick (Fri, 19 Jan 2018 19:24:31 GMT):
https://stackoverflow.com/questions/27606065/how-to-find-the-kafka-version-in-linux
jyellick (Fri, 19 Jan 2018 19:25:40 GMT):
I suspect you will find that the Kafka version is v0.9.0.1
rameshthoomu (Fri, 19 Jan 2018 19:25:45 GMT):
ok will check and let you know..
rameshthoomu (Fri, 19 Jan 2018 19:25:56 GMT):
yes it should be https://github.com/hyperledger/fabric-baseimage/blob/master/images/kafka/Dockerfile.in#L8
rameshthoomu (Fri, 19 Jan 2018 19:26:16 GMT):
will confirm
jyellick (Fri, 19 Jan 2018 19:26:23 GMT):
But I know the CI has been running with v0.10.2.0 for the past several weeks
jyellick (Fri, 19 Jan 2018 19:26:36 GMT):
Because it was pulling the fabric v1.0.0-preview docker image
jyellick (Fri, 19 Jan 2018 19:27:54 GMT):
The `orderer.yaml` in master depends on v0.10.2.0 or newer: https://github.com/hyperledger/fabric/blob/master/sampleconfig/orderer.yaml#L249
rameshthoomu (Fri, 19 Jan 2018 19:28:26 GMT):
oh that;s the issue..
jyellick (Fri, 19 Jan 2018 19:29:01 GMT):
Well, whether the baseimage should be updated to v0.10.2.0 or `orderer.yaml` should be reverted back to v0.9.0.1 I don't have a strong opinion, but there is a mismatch
rameshthoomu (Fri, 19 Jan 2018 19:29:02 GMT):
we have released baseimage and thirdparty images (couchdb, kafka and zookeeper) wih 0.4.4
rameshthoomu (Fri, 19 Jan 2018 19:29:16 GMT):
So my patch https://gerrit.hyperledger.org/r/#/c/17001/ is pulling 0.4.4 docker images..
jyellick (Fri, 19 Jan 2018 19:29:34 GMT):
Yes, that would do it
rameshthoomu (Fri, 19 Jan 2018 20:12:06 GMT):
@jyellick created bug here FAB-7825
Brucepark (Sat, 20 Jan 2018 06:13:58 GMT):
Has joined the channel.
silasdavis (Sun, 21 Jan 2018 11:54:36 GMT):
Has left the channel.
rameshthoomu (Mon, 22 Jan 2018 14:00:51 GMT):
Hi @sykesm I have created FAB-7842
sykesm (Mon, 22 Jan 2018 14:00:51 GMT):
Has joined the channel.
rameshthoomu (Mon, 22 Jan 2018 14:02:29 GMT):
suspecting on this patch https://gerrit.hyperledger.org/r/#/c/16661/
rameshthoomu (Mon, 22 Jan 2018 20:51:54 GMT):
@harsha I see fabric-baseimage is not published from ppc64le arch.. See this error
```
00:00:38.797 + wget -q -U UA_IBM_JAVA_Docker -O /tmp/ibm-java.bin
00:00:38.800 wget: missing URL
00:00:38.800 Usage: wget [OPTION]... [URL]...
00:00:38.800
00:00:38.800 Try `wget --help' for more options.
00:00:38.800 The command '/bin/sh -c cd /tmp/scripts && common/jvm.sh && common/cleanup.sh && rm -rf /tmp/scripts' returned a non-zero code: 1
00:00:38.802 Makefile:68: recipe for target 'build/docker/basejvm/.
```
harsha (Tue, 23 Jan 2018 01:33:09 GMT):
@rameshthoomu Looks like missing java URL, which is updated in the latest master code of fabric-baseimage.
rameshthoomu (Tue, 23 Jan 2018 01:36:11 GMT):
ok.. I think this will fix in next release 0.4.5
harsha (Tue, 23 Jan 2018 01:38:10 GMT):
Ok, any ETA when we are expecting to release 0.4.5 ?
rameshthoomu (Tue, 23 Jan 2018 02:41:55 GMT):
patch has been submitted here.. https://gerrit.hyperledger.org/r/c/17079/
rameshthoomu (Tue, 23 Jan 2018 02:42:12 GMT):
some one has to merge and create a tag in baseimage
rameshthoomu (Tue, 23 Jan 2018 02:42:12 GMT):
some one has to merge and create a release tag
zhaochy (Tue, 23 Jan 2018 08:20:51 GMT):
hi, team, how can i re-verify a jenkins job?
rameshthoomu (Tue, 23 Jan 2018 11:22:49 GMT):
You can type reverify in the gerrit comment
rameshthoomu (Tue, 23 Jan 2018 11:22:49 GMT):
You can type `reverify` in the gerrit comment
rameshthoomu (Tue, 23 Jan 2018 11:22:49 GMT):
You can type `reverify` in the gerrit patch set as a comment
rameshthoomu (Tue, 23 Jan 2018 13:43:14 GMT):
@simsc I have submitted patch to create a new CI job to unit-tests and generate code coverage report.. https://gerrit.hyperledger.org/r/#/c/17091/
rameshthoomu (Tue, 23 Jan 2018 13:43:14 GMT):
@simsc I have submitted patch to create a new CI job to unit-tests and generate code coverage report daily once. This is a cron job which runs daily at 5;00 AM EST.. https://gerrit.hyperledger.org/r/#/c/17091/
rameshthoomu (Tue, 23 Jan 2018 13:43:48 GMT):
Once this patch is merged, will give you the link to access code coverage report..
rameshthoomu (Tue, 23 Jan 2018 13:46:54 GMT):
Please note, we don't run code coverage report for every patch set like the way we did earlier..
rameshthoomu (Wed, 24 Jan 2018 00:39:58 GMT):
@simsc please check the code coverage report here https://jenkins.hyperledger.org/view/Daily/job/fabric-unit-tests-coverage-daily-x86_64/
jtclark (Wed, 24 Jan 2018 14:50:04 GMT):
good morning
rameshthoomu (Wed, 24 Jan 2018 15:28:07 GMT):
good morning
rameshthoomu (Wed, 24 Jan 2018 15:29:33 GMT):
@jtclark do you know how to override the version published in nexus using `maven deploy-plugin`?
jtclark (Wed, 24 Jan 2018 15:34:47 GMT):
I don't. I'd like to learn
rameshthoomu (Wed, 24 Jan 2018 15:42:24 GMT):
ok then ignore it..
jtclark (Wed, 24 Jan 2018 16:01:20 GMT):
no problem.
rameshthoomu (Fri, 26 Jan 2018 00:00:54 GMT):
@harrijk Need your help in deleting this directory from s390x build nodes
```
00:00:07.732 rm: cannot remove '/tmp/fabric-shim/chaincode/hyperledger/fabric/peer/mychannel.block': Permission denied
00:00:07.733 rm: cannot remove '/tmp/fabric-shim/chaincode/hyperledger/fabric/peer/crypto': Permission denied
```
rameshthoomu (Fri, 26 Jan 2018 00:01:43 GMT):
cleanup script in CI job is deleting this and getting above error
harrijk (Fri, 26 Jan 2018 00:02:56 GMT):
that looks right.
harrijk (Fri, 26 Jan 2018 00:03:28 GMT):
You may be trying to login from a different machine in which case, that public key may not be in the authorized_keys file
rameshthoomu (Fri, 26 Jan 2018 00:03:35 GMT):
I think root user is setting on these files.
harrijk (Fri, 26 Jan 2018 00:06:16 GMT):
I just deleted /tmp/fabric-shim on -18
rameshthoomu (Fri, 26 Jan 2018 00:07:32 GMT):
this worked now..
rameshthoomu (Fri, 26 Jan 2018 00:08:27 GMT):
not sure how to fix this issue.. it seems root user is setting on these files, so jenkins is unable to delete these files..
harrijk (Fri, 26 Jan 2018 00:11:15 GMT):
Are you including those rm statements in your job?
harrijk (Fri, 26 Jan 2018 00:11:44 GMT):
My script is constantly checking for /tmp/fabric-shim and will remove/delete the directory if it isn't in use
harrijk (Fri, 26 Jan 2018 00:12:19 GMT):
I would leave it to my cleanup script to delete those temp directories
harrijk (Fri, 26 Jan 2018 00:12:43 GMT):
Also... can you paste in your public key? I'd like to see if it's in the authorized_keys file
rameshthoomu (Fri, 26 Jan 2018 00:30:13 GMT):
Thanks @harrijk I have access to all the z build nodes..
rameshthoomu (Fri, 26 Jan 2018 02:39:13 GMT):
@cbf goreport card issue has been fixed with this https://github.com/gojp/goreportcard/issues/239
rameshthoomu (Fri, 26 Jan 2018 02:40:37 GMT):
earlier goreport was showing F grade now it got updated to A+ after the fix
cbf (Fri, 26 Jan 2018 14:49:18 GMT):
thx!
rameshthoomu (Mon, 29 Jan 2018 14:02:30 GMT):
there will be rolling outages to infra Monday. Please see: https://lists.hyperledger.org/pipermail/hyperledger-tsc/2018-January/001360.html this means Jenkins will be in shutdown mode until the queue is drained
jtclark (Mon, 29 Jan 2018 14:34:35 GMT):
@rameshthoomu qq for you
jtclark (Mon, 29 Jan 2018 14:37:29 GMT):
the output from the safesql_test.sh file as mentioned in FAB-1446 is being "surpressed" now. I'll re-upload the fabric-ca-verify-x86_64 job again to show you, but, basically it just says "passed". Do you guys have a way that you "bubble up" the script output results to the fvt test that gets triggered?
jtclark (Mon, 29 Jan 2018 14:38:55 GMT):
@rameshthoomu I'm trying to get back to where I was able to see this output:
```
15:01:39 Found 14 potentially unsafe SQL statements:
15:01:39 - /opt/gopath/src/github.com/hyperledger/fabric-ca/vendor/github.com/jmoiron/sqlx/sqlx.go:618:21
15:01:39 - /opt/gopath/src/github.com/hyperledger/fabric-ca/vendor/github.com/jmoiron/sqlx/sqlx.go:673:20
15:01:39 - /opt/gopath/src/github.com/hyperledger/fabric-ca/lib/dbaccessor.go:404:23
15:01:39 - /opt/gopath/src/github.com/hyperledger/fabric-ca/vendor/github.com/jmoiron/sqlx/named.go:335:15
15:01:39 - /opt/gopath/src/github.com/hyperledger/fabric-ca/lib/dbaccessor.go:281:20
15:01:39 - /opt/gopath/src/github.com/hyperledger/fabric-ca/lib/dbutil/dbutil.go:178:19
15:01:39 - /opt/gopath/src/github.com/hyperledger/fabric-ca/lib/dbutil/dbutil.go:268:19
15:01:39 - /opt/gopath/src/github.com/hyperledger/fabric-ca/vendor/github.com/jmoiron/sqlx/sqlx.go:341:26
15:01:39 - /opt/gopath/src/github.com/hyperledger/fabric-ca/vendor/github.com/jmoiron/sqlx/sqlx.go:332:23
15:01:39 - /opt/gopath/src/github.com/hyperledger/fabric-ca/vendor/github.com/jmoiron/sqlx/sqlx.go:618:21
15:01:39 - /opt/gopath/src/github.com/hyperledger/fabric-ca/vendor/github.com/jmoiron/sqlx/named.go:335:15
15:01:39 - /opt/gopath/src/github.com/hyperledger/fabric-ca/vendor/github.com/jmoiron/sqlx/sqlx.go:673:20
15:01:39 - /opt/gopath/src/github.com/hyperledger/fabric-ca/vendor/github.com/jmoiron/sqlx/sqlx.go:415:26
15:01:39 - /opt/gopath/src/github.com/hyperledger/fabric-ca/vendor/github.com/jmoiron/sqlx/sqlx.go:406:23
```
rameshthoomu (Mon, 29 Jan 2018 14:40:04 GMT):
Seems these errors are not from our code base..
rameshthoomu (Mon, 29 Jan 2018 14:40:19 GMT):
I think it's better to ignore vendor module..
jtclark (Mon, 29 Jan 2018 14:40:53 GMT):
according to keith smith:
jtclark (Mon, 29 Jan 2018 14:40:59 GMT):
```
It seems to me that we need to evaluate each of the "14 potentially unsafe SQL statements" above to see which pose real threats.
For all that pose a real threat, we need to fix them whether they are in vendor packages or not.
```
rameshthoomu (Mon, 29 Jan 2018 14:41:38 GMT):
ok
jtclark (Mon, 29 Jan 2018 14:41:43 GMT):
even if we don't do anything about them, I'd like to at least see them
jtclark (Mon, 29 Jan 2018 14:42:11 GMT):
because now when the job runs, it doesn't show this output, it just says passed, which basically means that the script successfully ran.
rameshthoomu (Mon, 29 Jan 2018 14:43:19 GMT):
try to fail the job if we have errors
jtclark (Mon, 29 Jan 2018 14:43:33 GMT):
I think I can figure out a way to alter the return code, based on what we get as output from the script running, but I'm wondering how you "throw" this output up to the fvt script that's running all of the others.....
jtclark (Mon, 29 Jan 2018 14:44:04 GMT):
right, ok.
jtclark (Mon, 29 Jan 2018 14:44:41 GMT):
yeah, maybe I can handle that in the safesql_test.sh script itself. I'll try that.
Ammu (Wed, 31 Jan 2018 07:32:22 GMT):
where our data's will store in couchdb?
lehors (Wed, 31 Jan 2018 15:18:23 GMT):
any known problem with our CI right now?
lehors (Wed, 31 Jan 2018 15:18:54 GMT):
I merely changed the content of a string in an error message and the build fails
lehors (Wed, 31 Jan 2018 15:19:04 GMT):
reverify failed too
lehors (Wed, 31 Jan 2018 15:19:23 GMT):
https://gerrit.hyperledger.org/r/#/c/17333/
rameshthoomu (Wed, 31 Jan 2018 15:29:28 GMT):
@lehors checking
rameshthoomu (Wed, 31 Jan 2018 15:49:02 GMT):
@lehors I see s390x is not loading thirdparty packages successfully..
rameshthoomu (Wed, 31 Jan 2018 15:51:00 GMT):
@harrijk ^^
harrijk (Wed, 31 Jan 2018 15:52:12 GMT):
hmm. Let take a look at 17333
rameshthoomu (Wed, 31 Jan 2018 15:55:18 GMT):
it's happening in fabric-sdk-go projects also..
rameshthoomu (Wed, 31 Jan 2018 15:55:44 GMT):
I triggered one build from fabric on 23 node and it's working
harrijk (Wed, 31 Jan 2018 15:59:41 GMT):
Which build is working? the fabric-ca-verify or fabric-sdk-go?
harrijk (Wed, 31 Jan 2018 15:59:55 GMT):
I see all of the failed builds are running on -16.
harrijk (Wed, 31 Jan 2018 16:00:10 GMT):
Can you force the fabric-ca-verify build to run on another minion?
harrijk (Wed, 31 Jan 2018 16:00:33 GMT):
I'm logging into -16 and will try and clean things up, where needed.
rameshthoomu (Wed, 31 Jan 2018 16:00:44 GMT):
sure..
rameshthoomu (Wed, 31 Jan 2018 16:00:58 GMT):
let me check where fabric-sdk-go builds are running
harrijk (Wed, 31 Jan 2018 16:01:03 GMT):
OK
rameshthoomu (Wed, 31 Jan 2018 16:02:17 GMT):
21,17 also
rameshthoomu (Wed, 31 Jan 2018 16:02:39 GMT):
23 is good
jtclark (Wed, 31 Jan 2018 16:38:27 GMT):
GM :sunny:
rameshthoomu (Wed, 31 Jan 2018 16:39:33 GMT):
GM
jtclark (Wed, 31 Jan 2018 16:39:42 GMT):
question: looking around for an example of where the script output is written to a tmp file
jtclark (Wed, 31 Jan 2018 16:40:09 GMT):
I want to parse that file so that I can fail the test if there's error output
rameshthoomu (Wed, 31 Jan 2018 16:41:09 GMT):
@harrijk please let me know once you cleanup workspace in all z nodes.. Will re-trigger all the failed builds
jtclark (Wed, 31 Jan 2018 16:41:11 GMT):
I see CA_CFG_PATH in several of the the FVT tests
harrijk (Wed, 31 Jan 2018 16:41:35 GMT):
@rameshthoomu Will do... waiting on -18 to complete
jtclark (Wed, 31 Jan 2018 16:41:38 GMT):
is that a tmp dir that I can write my script output to?
jtclark (Wed, 31 Jan 2018 16:41:59 GMT):
ok well, maybe not that path, but the /tmp dir....
rameshthoomu (Wed, 31 Jan 2018 16:42:34 GMT):
@jtclark which job you are referring? is it from CI job configuration or fabric-ca test configuration?
jtclark (Wed, 31 Jan 2018 16:42:57 GMT):
fabric-ca-verify
jtclark (Wed, 31 Jan 2018 16:43:30 GMT):
which runs the fvt-tests make
rameshthoomu (Wed, 31 Jan 2018 16:43:51 GMT):
check with @rennman
jtclark (Wed, 31 Jan 2018 16:44:05 GMT):
ok
jtclark (Wed, 31 Jan 2018 16:44:31 GMT):
right now, when I run my version of the test that includes the safesql script
harrijk (Wed, 31 Jan 2018 16:44:36 GMT):
@rameshthoomu -18 has been cleaned up. All minions have been cleaned.
rameshthoomu (Wed, 31 Jan 2018 16:44:47 GMT):
thanks @harrijk
jtclark (Wed, 31 Jan 2018 16:45:02 GMT):
it suppresses the output, so I need to fail that job if we see warnings in the output, and I'm thinking to write the output to a file, then parse the file before exiting
jtclark (Wed, 31 Jan 2018 16:45:36 GMT):
but I need to know where I can write the file (temporarily)
rameshthoomu (Wed, 31 Jan 2018 16:46:24 GMT):
you can write it any where outside of $WORKSPACE
rameshthoomu (Wed, 31 Jan 2018 16:47:25 GMT):
so that the you can take this as build artifact in Jenkins.. Otherwise, write it in /tmp and mv this to $WORKSPACE
rennman (Wed, 31 Jan 2018 16:47:27 GMT):
@jtclark in an effort to reduce the amount of log storage, the test will print a log only if the test fails ... if you insert a bogus exit # (not 0) the test will have presumed to have failed and print the log in the console log
jtclark (Wed, 31 Jan 2018 16:47:59 GMT):
FAB-1446
rennman (Wed, 31 Jan 2018 16:48:02 GMT):
otherwise, if you have access to the VM that runs the test, all of the logs are stored in /tmp, under the specific testcase name
jtclark (Wed, 31 Jan 2018 16:49:20 GMT):
if you look at that, you'll see that the script runs. we see 'potentially unsafe SQL statements' and as Keith Smith mentioned, we should get the opportunity to evaluate those.
jtclark (Wed, 31 Jan 2018 16:50:41 GMT):
even though the exit code is '0' (which says that the script ran successfully) we still need to fail the test because of these 'potentially unsafe' queries in the code.
jtclark (Wed, 31 Jan 2018 16:51:40 GMT):
@rennman you're saying that my script output is stored in temp under the test case name, and I can parse the output from there prior to exiting?
rennman (Wed, 31 Jan 2018 16:52:13 GMT):
yes
jtclark (Wed, 31 Jan 2018 16:52:33 GMT):
thanks. I'll see if I can modify my script to then read the file there.
rennman (Wed, 31 Jan 2018 16:58:28 GMT):
all of the individual script output to STDOUT is stored in /tmp/fvt-test.results
however, most of the tests in /fvt create their own output logs in their own directory that exploits the feature of fabric-ca_setup.sh which uses CA_CFG_PATH as it's home ... the basic template is to
set CA_CFG_PATH=
jtclark (Wed, 31 Jan 2018 16:59:21 GMT):
ok
jtclark (Wed, 31 Jan 2018 16:59:35 GMT):
so I should export that env var too
jtclark (Wed, 31 Jan 2018 16:59:38 GMT):
in my test
jtclark (Wed, 31 Jan 2018 17:00:15 GMT):
(sounds like)
jtclark (Wed, 31 Jan 2018 17:00:58 GMT):
@rennman ^
rennman (Wed, 31 Jan 2018 17:01:03 GMT):
however, it is still the script's responsibility to redirect '>' any log files you explicitly generate to that directory
jtclark (Wed, 31 Jan 2018 17:01:15 GMT):
ok
rennman (Wed, 31 Jan 2018 17:01:29 GMT):
but anything written to STDOUT will show up in /tmp/fvt-test.results
jtclark (Wed, 31 Jan 2018 17:01:55 GMT):
well, sounds like I should redirect, just so that I'm not looking through ALL of fvt-test.results
rennman (Wed, 31 Jan 2018 17:02:05 GMT):
good plan ;-)
jtclark (Wed, 31 Jan 2018 17:02:15 GMT):
cool.
dave.enyeart (Wed, 31 Jan 2018 17:52:50 GMT):
@rameshthoomu I've seen e2e fail CI a few times in a row, e.g.: https://gerrit.hyperledger.org/r/#/c/17373/
dave.enyeart (Wed, 31 Jan 2018 17:53:45 GMT):
Also, in that one, fabric-rtd-verify-master failed. That one is new to me... what does it do and why the failure?
dave.enyeart (Wed, 31 Jan 2018 17:54:07 GMT):
@joe-alewine @AdnanC FYI ^^^^^
joe-alewine (Wed, 31 Jan 2018 17:54:07 GMT):
Has joined the channel.
rameshthoomu (Wed, 31 Jan 2018 17:54:30 GMT):
checking .. rtd-verify is a recent job.. will check this one..
rameshthoomu (Wed, 31 Jan 2018 17:54:54 GMT):
I see latest e2e tests failed with 00:14:27.274 Error: timeout waiting for channel creation
dave.enyeart (Wed, 31 Jan 2018 17:55:43 GMT):
yeah, i've seen that twice today
rameshthoomu (Wed, 31 Jan 2018 17:57:08 GMT):
to pass rtd-verify, we need this patch to be merged https://gerrit.hyperledger.org/r/#/c/17275/
dave.enyeart (Wed, 31 Jan 2018 17:58:57 GMT):
@rameshthoomu shall I go ahead and +2 https://gerrit.hyperledger.org/r/#/c/17275 ? I assume you wanted both of those .gitignores in there?
rameshthoomu (Wed, 31 Jan 2018 17:59:23 GMT):
yes
rameshthoomu (Wed, 31 Jan 2018 17:59:40 GMT):
I don't see FAB in the commit
rameshthoomu (Wed, 31 Jan 2018 18:01:02 GMT):
Shall I create one and upload new change?
dave.enyeart (Wed, 31 Jan 2018 18:02:02 GMT):
i'm ok +2ing without the FAB number in this case since we'd like to unblock CI failures
rameshthoomu (Wed, 31 Jan 2018 18:04:35 GMT):
ok.. This only triggers on documentation change not on every patch set
joe-alewine (Wed, 31 Jan 2018 18:15:57 GMT):
@dave.enyeart It seems to do it often. I have no idea why. But "reverify" usually takes care of it.
Although Adnan should have put [ci-skip] under his commit message. That does seem to help (although I've had it fail to verify when using it).
joe-alewine (Wed, 31 Jan 2018 18:15:57 GMT):
@dave.enyeart It seems to do it often. I have no idea why. But "reverify" usually takes care of it.
Although Adnan should have put [ci-skip] under his commit message. That does seem to help (although I've had it fail to verify when using it).
dave.enyeart (Wed, 31 Jan 2018 18:17:18 GMT):
Do we know what the new job rtd-verify does?
dave.enyeart (Wed, 31 Jan 2018 18:17:50 GMT):
and will it still be executed for doc changes when we add [ci-skip] ?
rameshthoomu (Wed, 31 Jan 2018 18:19:55 GMT):
ci-skip won't work in our jenkins jobs.. seems some security issues with the plugin..
rameshthoomu (Wed, 31 Jan 2018 18:20:13 GMT):
so no matter whether you use or not, we trigger the build
rameshthoomu (Wed, 31 Jan 2018 18:20:46 GMT):
regarding rtd-verify job, this is a new job added which triggers when a patch set submitted with .rst or .md changes
rameshthoomu (Wed, 31 Jan 2018 18:24:57 GMT):
access the build logs to see the documentation output..
rameshthoomu (Wed, 31 Jan 2018 18:26:34 GMT):
Capture.PNG
eugenluft (Wed, 31 Jan 2018 20:36:49 GMT):
Has joined the channel.
eugenluft (Wed, 31 Jan 2018 20:44:40 GMT):
I´m really looking forward to use TS/Node.js to implement CC ;) :champagne: Would there be a possibility to enable the node.js remote-debugger to debug the code on a running ledger? Are there any objections?
rameshthoomu (Wed, 31 Jan 2018 20:50:05 GMT):
@eugenluft seems the question is not related to CI, better post in #fabric-sdk-node
eugenluft (Wed, 31 Jan 2018 20:53:26 GMT):
@rameshthoomu Sorry if i´m wrong, but i saw some discussions about node cc here and i´m not really speaking about the node sdk. So difficult to find the right place :-(
lehors (Thu, 01 Feb 2018 08:05:21 GMT):
@eugenluft as you probably know the node.js cc is new and I guess we don't have a dedicated channel for it but you'd still be better off taking your question to the sdk channel than this channel which really has nothing to do with it
lehors (Thu, 01 Feb 2018 08:06:16 GMT):
@rameshthoomu I see the build on https://gerrit.hyperledger.org/r/#/c/17333/ was restarted and succeeded - thank you
lehors (Thu, 01 Feb 2018 08:06:45 GMT):
however, the vote didn't seem to register and it still says -1
lehors (Thu, 01 Feb 2018 11:16:32 GMT):
well, @smithbk restarted the build so that will take care of it hopefully
smithbk (Thu, 01 Feb 2018 11:18:28 GMT):
yes, it was weird ... never seen the build succeed but not register
dave.enyeart (Thu, 01 Feb 2018 12:02:07 GMT):
@rameshthoomu In addition to rtd-verify, I see another new one byfn-verify that is failing in https://gerrit.hyperledger.org/r/#/c/16719/ . Could you announce on this channel when major CI job changes are done and what the job does at high level? I still don't understand whether these should be ignored or not.
lehors (Thu, 01 Feb 2018 12:04:04 GMT):
@smithbk the build was restarted by hand and I can only guess that this process didn't involve the voting registration
rameshthoomu (Thu, 01 Feb 2018 13:19:02 GMT):
@dave.enyeart rtd-verify was added in fabric builds, triggers on .rst or .md changes. But the `byfn-verify` is part of the `fabric-samples` repository and it's not a new job..
rameshthoomu (Thu, 01 Feb 2018 13:19:56 GMT):
sure will announce here, if I add new jobs..
rameshthoomu (Thu, 01 Feb 2018 13:22:53 GMT):
@smithbk @lehors re-triggered build again.. I see the workspace directory is deleted in s390x job before build complete
rameshthoomu (Thu, 01 Feb 2018 13:23:42 GMT):
@harrijk ping me once you are in.. Will check this https://jenkins.hyperledger.org/job/fabric-ca-verify-s390x/2634/console
jtclark (Thu, 01 Feb 2018 13:45:59 GMT):
GM
jtclark (Thu, 01 Feb 2018 13:47:40 GMT):
need to review the test result log file on the build system.. is there a way to get access to the VM that runs the test?
rameshthoomu (Thu, 01 Feb 2018 13:49:12 GMT):
use artifacts in job to see the log file..
jtclark (Thu, 01 Feb 2018 13:57:31 GMT):
ok
jtclark (Thu, 01 Feb 2018 14:34:08 GMT):
@rameshthoomu https://logs.hyperledger.org/sandbox/vex-yul-hyp-jenkins-2/fabric-ca-verify-x86_64/12/ ?
jtclark (Thu, 01 Feb 2018 14:34:41 GMT):
I'm looking through there, but I don't see where the test result files are.... does it explicitly have to be added to the job?
rameshthoomu (Thu, 01 Feb 2018 14:37:57 GMT):
yes if not there..
rameshthoomu (Thu, 01 Feb 2018 14:37:57 GMT):
yes if not there.. you can the same in post build action.. If you don't find any archive the artifacts, then pls add the correct path of the log
rameshthoomu (Thu, 01 Feb 2018 14:37:57 GMT):
yes if it is not there.. check the same in post build action.. There is a Archive artifact plugin in Jenkins to archive the artifacts.. Please configure that in your job
jtclark (Thu, 01 Feb 2018 14:42:34 GMT):
hmm
jtclark (Thu, 01 Feb 2018 15:22:41 GMT):
@rameshthoomu I found this in a JJB:
jtclark (Thu, 01 Feb 2018 15:22:47 GMT):
```
- archive:
artifacts: 'gopath/src/github.com/hyperledger/fabric/bddtests/*.log'
fingerprint: true
default-excludes: false
allow-empty: true
```
rameshthoomu (Thu, 01 Feb 2018 15:23:02 GMT):
yes
jtclark (Thu, 01 Feb 2018 15:23:03 GMT):
is this what needs to be explicitly defined
jtclark (Thu, 01 Feb 2018 15:23:05 GMT):
?
jtclark (Thu, 01 Feb 2018 15:23:11 GMT):
for fabric-ca
jtclark (Thu, 01 Feb 2018 15:23:11 GMT):
?
rameshthoomu (Thu, 01 Feb 2018 15:23:20 GMT):
yes that's right.
jtclark (Thu, 01 Feb 2018 15:23:27 GMT):
ok
rameshthoomu (Thu, 01 Feb 2018 15:24:12 GMT):
pls note.. You have to provide the correct artifacts path..
jtclark (Thu, 01 Feb 2018 15:34:46 GMT):
@rameshthoomu sure. that was an example that I saw
jtclark (Thu, 01 Feb 2018 15:35:04 GMT):
but, I'm trying to determine what the correct path is....
rameshthoomu (Thu, 01 Feb 2018 15:35:23 GMT):
just give `**/*.log`
jtclark (Thu, 01 Feb 2018 15:35:35 GMT):
oh ok
jtclark (Thu, 01 Feb 2018 15:35:43 GMT):
I'll try that now.
rameshthoomu (Thu, 01 Feb 2018 15:36:12 GMT):
make sure your log file is placed outside WORKSPACE directory..
jtclark (Thu, 01 Feb 2018 15:36:33 GMT):
I'm writing it like this:
jtclark (Thu, 01 Feb 2018 15:37:21 GMT):
`safesql -v ../cmd/fabric-ca-client ../cmd/fabric-ca-server | tee $CA_CFG_PATH/safesql_tests.log`
jtclark (Thu, 01 Feb 2018 15:37:51 GMT):
and that env variable is defined as `export CA_CFG_PATH="/tmp/safesql"`
jtclark (Thu, 01 Feb 2018 15:38:37 GMT):
by adding **/*.log I should be able to see the log file in the build artifacts?
jtclark (Thu, 01 Feb 2018 15:38:37 GMT):
by adding `**/*.log` I should be able to see the log file in the build artifacts?
rameshthoomu (Thu, 01 Feb 2018 15:38:58 GMT):
ok.. That won;t work. you have to move .log file from /tmp to WORKSPACE
jtclark (Thu, 01 Feb 2018 15:39:13 GMT):
ok
jtclark (Thu, 01 Feb 2018 15:40:21 GMT):
I don't seed to use that $CA_CFG_PATH env var at all then it sounds like...
jtclark (Thu, 01 Feb 2018 15:43:38 GMT):
@rameshthoomu so this in my script now:
jtclark (Thu, 01 Feb 2018 15:43:43 GMT):
```
safesql -v ../cmd/fabric-ca-client ../cmd/fabric-ca-server | tee $WORKSPACE/safesql_tests.log
```
jtclark (Thu, 01 Feb 2018 15:44:52 GMT):
and then in the fabric-ca-verify job, I added:
```
- archive:
artifacts: '**/*.log'
fingerprint: true
default-excludes: false
allow-empty: true
```
jtclark (Thu, 01 Feb 2018 15:45:13 GMT):
under `builders:` is this correct ?
rameshthoomu (Thu, 01 Feb 2018 15:46:16 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=YmX8swjf8pCcN3JJz) @jtclark ??
jtclark (Thu, 01 Feb 2018 15:47:37 GMT):
@rameshthoomu .... ok... where is the correct place to add the `archive` entry?
jtclark (Thu, 01 Feb 2018 15:48:22 GMT):
```
builders:
- verify-commit-message
- clean-environment
- 'ca-golang-environment-{arch}'
- output-environment
- ca-unit-tests
```
jtclark (Thu, 01 Feb 2018 15:48:47 GMT):
would it be underneath builders? or publishers? or somewhere else?
rameshthoomu (Thu, 01 Feb 2018 15:49:50 GMT):
which one your command or Artifacts?
jtclark (Thu, 01 Feb 2018 15:50:01 GMT):
the artifacts entry above
jtclark (Thu, 01 Feb 2018 15:50:03 GMT):
not my script.
jtclark (Thu, 01 Feb 2018 15:50:10 GMT):
my script goes in fabric-ca.
rameshthoomu (Thu, 01 Feb 2018 15:50:22 GMT):
As I said, it should be in Postbuild actions.. so should be in Publishers
jtclark (Thu, 01 Feb 2018 15:51:08 GMT):
awesome, thx
jtclark (Thu, 01 Feb 2018 15:59:52 GMT):
I'm updated the job, and the script. testing it now on the sandbox.
jtclark (Thu, 01 Feb 2018 15:59:52 GMT):
I've updated the job, and the script. testing it now on the sandbox.
jtclark (Thu, 01 Feb 2018 17:06:49 GMT):
@rameshthoomu the build finished - took 54mins - don't see the artifacts though....
rameshthoomu (Thu, 01 Feb 2018 17:08:37 GMT):
ok can you show me the build
jtclark (Thu, 01 Feb 2018 17:09:14 GMT):
sure
jtclark (Thu, 01 Feb 2018 17:09:24 GMT):
https://jenkins.hyperledger.org/sandbox/job/fabric-ca-verify-x86_64/lastBuild/
rameshthoomu (Thu, 01 Feb 2018 17:10:38 GMT):
I don't see archive-artifacts section in post build action
rameshthoomu (Thu, 01 Feb 2018 17:10:45 GMT):
do you want me to add?
jtclark (Thu, 01 Feb 2018 17:13:25 GMT):
@rameshthoomu that's strange.
jtclark (Thu, 01 Feb 2018 17:13:33 GMT):
I added this under publishers
jtclark (Thu, 01 Feb 2018 17:13:40 GMT):
```
publishers:
- lf-infra-publish
- ca-code-coverage-report
- archive:
artifacts: '**/*.log'
fingerprint: true
default-excludes: false
allow-empty: true
```
jtclark (Thu, 01 Feb 2018 17:13:54 GMT):
then re-updated the jjb
jtclark (Thu, 01 Feb 2018 17:14:00 GMT):
unless that's not correct....
rameshthoomu (Thu, 01 Feb 2018 17:15:17 GMT):
that's not correct
jtclark (Thu, 01 Feb 2018 17:15:41 GMT):
how should this look?
rameshthoomu (Thu, 01 Feb 2018 17:17:00 GMT):
do like this
```
publishers:
- lf-infra-publish
- ca-code-coverage-report
- dockerlog
```
jtclark (Thu, 01 Feb 2018 17:17:12 GMT):
ah
jtclark (Thu, 01 Feb 2018 17:17:15 GMT):
use that macro basically
jtclark (Thu, 01 Feb 2018 17:17:47 GMT):
I'll try it
jtclark (Thu, 01 Feb 2018 18:45:02 GMT):
@rameshthoomu failed this time: https://jenkins.hyperledger.org/sandbox/job/fabric-ca-verify-x86_64/lastBuild/console
rameshthoomu (Thu, 01 Feb 2018 19:07:47 GMT):
did you move your log file from /tmp to workspace?
jtclark (Thu, 01 Feb 2018 19:15:24 GMT):
I think I see what I did in the list attempt - the job wasn't updated to point to my github repo
jtclark (Thu, 01 Feb 2018 19:15:24 GMT):
I think I see what I did in the last attempt - the job wasn't updated to point to my github repo
jtclark (Thu, 01 Feb 2018 19:16:01 GMT):
after I updated the job with the - dockerlog entry
jtclark (Thu, 01 Feb 2018 19:16:12 GMT):
I should've went back in and changed the repo.
jtclark (Thu, 01 Feb 2018 19:16:27 GMT):
I'll just stop the build and update that
skarim (Thu, 01 Feb 2018 20:50:49 GMT):
reverify
jtclark (Fri, 02 Feb 2018 15:44:51 GMT):
:sunrise:
jtclark (Fri, 02 Feb 2018 15:49:10 GMT):
Hi @rameshthoomu - picking up where I left off yesterday on getting the script output logged and accessible as an archive artifact.... the job provide the archive, but it's empty.
rameshthoomu (Fri, 02 Feb 2018 15:53:54 GMT):
try the same in your local machine..
jtclark (Fri, 02 Feb 2018 16:06:06 GMT):
ok.
jtclark (Fri, 02 Feb 2018 16:06:20 GMT):
while I have you
jtclark (Fri, 02 Feb 2018 16:06:36 GMT):
I talked to @tongli a little bit about ansible/cello tasks
jtclark (Fri, 02 Feb 2018 16:06:43 GMT):
he told me to ask you about build automation?
jtclark (Fri, 02 Feb 2018 16:31:21 GMT):
@rameshthoomu ^^^
rameshthoomu (Fri, 02 Feb 2018 16:34:05 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=h5yL6FofGFETjTKNB) @jtclark you mean CI tasks ? I didn't get you on build automation
jtclark (Fri, 02 Feb 2018 16:35:05 GMT):
@rameshthoomu yes, I assume that's what he means
rameshthoomu (Fri, 02 Feb 2018 16:35:33 GMT):
ok
rameshthoomu (Fri, 02 Feb 2018 16:37:18 GMT):
I think we have JIRA tasks assigned.. let;s focus on completing them..
rameshthoomu (Fri, 02 Feb 2018 16:37:47 GMT):
feel free to create jira tasks..
rameshthoomu (Fri, 02 Feb 2018 16:38:29 GMT):
we have fabric-ci & fabric-build components in JIRA to track all ci tasks/issues
rameshthoomu (Fri, 02 Feb 2018 16:44:42 GMT):
@jtclark are you ok with the plan?
jtclark (Fri, 02 Feb 2018 16:45:14 GMT):
that's fine.
jtclark (Fri, 02 Feb 2018 16:45:15 GMT):
I
jtclark (Fri, 02 Feb 2018 16:45:15 GMT):
I'll revisit the cello stuff after I've got these other tasks out of the way
rameshthoomu (Fri, 02 Feb 2018 16:51:13 GMT):
ok @scottz was asking about the update on PTE integration in CI
rameshthoomu (Fri, 02 Feb 2018 16:51:18 GMT):
any update on that?
jtclark (Fri, 02 Feb 2018 16:55:36 GMT):
I'm working on added the tests to systest_pte.py
jtclark (Fri, 02 Feb 2018 16:55:36 GMT):
I'm working on adding the tests to systest_pte.py
jtclark (Fri, 02 Feb 2018 16:56:23 GMT):
basically, I'm trying to follow this:
jtclark (Fri, 02 Feb 2018 16:56:28 GMT):
```
CI test:
#### FAB-3833-2i: 2 invokes, couchDB
./test_driver.sh -n -m FAB-3810-2q -p -c samplecc -t FAB-3810-2q
./test_driver.sh -t FAB-3833-2i
#### execute testcase
#### FAB-3810-2q: 2 queries, couchDB
./test_driver.sh -t FAB-3810-2q
#### tear down network
#### Lauch network and execute testcase
#### FAB-3832-4i: 4 invokes, couchDB
./test_driver.sh -n -m FAB-3834-4q -p -c samplecc -t FAB-3834-4q
./test_driver.sh -t FAB-3832-4i
#### execute testcase
#### FAB-3834-4q: 4 queries, couchDB:
./test_driver.sh -t FAB-3834-4q
#### golevelDB ####
#### Lauch network and execute testcase
#### FAB-3808-2i: 2 invokes, golevelDB
./test_driver.sh -n -m FAB-3811-2q -p -c samplecc -t FAB-3811-2q
./test_driver.sh -t FAB-3808-2i
#### execute testcase
#### FAB-3811-2q: 2 queries, golevelDB
./test_driver.sh -t FAB-3811-2q
```
jtclark (Fri, 02 Feb 2018 16:57:09 GMT):
I'm about to test adding the execute testcase for couchDB
jtclark (Fri, 02 Feb 2018 16:57:20 GMT):
so, trying to get it to work
scottz (Fri, 02 Feb 2018 17:36:57 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=G8FpfTWbtqecjB8zP) @jtclark There are already some tests defined in fabric-test/regression/daily/systest_pte.py. If you look in fabric-test/regression/daily/runDailyTestSuite.sh, you will see a line commented out. I think you just need to start by uncommenting that line, run it on your environment, and then try it in a sandbox from a jenkins process and submit it. If I remember correclty, the problem is that it was failing when it was run by the CI. `#py.test -v --junitxml results_systest_pte.xml systest_pte.py
`
dave.enyeart (Sun, 04 Feb 2018 13:23:45 GMT):
@rameshthoomu RTD CRs are still failing due to fabric-rtd-verify-master. https://gerrit.hyperledger.org/r/#/c/17481/ What needs to be done? Do we simply need to merge https://gerrit.hyperledger.org/r/#/c/17275/ ? I suspect it is not getting merged because maintainers don't understand what is going on with the RTD build and CI and how tox.ini fits in. Can you elaborate here?
rameshthoomu (Sun, 04 Feb 2018 22:40:51 GMT):
@dave.enyeart tox.ini is the configuration file to build documentation in RTD format. `rtd-verify` CI job looks for the documentation changes in the patchset and triggers the build. Once the build is triggered, it looks for the tox.ini file and build documentation.
dave.enyeart (Mon, 05 Feb 2018 03:52:39 GMT):
@rameshthoomu so what needs to be done to fix the failures? Simply merge 17275?
rameshthoomu (Mon, 05 Feb 2018 03:53:04 GMT):
Yes
rameshthoomu (Mon, 05 Feb 2018 22:17:29 GMT):
@nfrunza submitted patchset to create CI jobs for blockchain explorer..Tested this in sandbox and it worked as expected..
nfrunza (Mon, 05 Feb 2018 22:17:30 GMT):
Has joined the channel.
rameshthoomu (Mon, 05 Feb 2018 22:17:34 GMT):
https://gerrit.hyperledger.org/r/#/c/17559/
rameshthoomu (Mon, 05 Feb 2018 22:18:23 GMT):
I don't see many tests in the repo.. Please feel free to create JIRA tasks under 'fabric-ci' component to enhance or add more features to these Jobs..
rameshthoomu (Mon, 05 Feb 2018 22:18:23 GMT):
I don't see many tests in the repo. Will add code coverage report later. Please feel free to create JIRA tasks under 'fabric-ci' component to enhance or add more features to these Jobs..
rameshthoomu (Mon, 05 Feb 2018 22:30:35 GMT):
Hi @jtclark any progress on FAB-1446 & PTE integration..
jtclark (Mon, 05 Feb 2018 22:34:42 GMT):
I’m OOTO today.
jtclark (Mon, 05 Feb 2018 22:34:51 GMT):
Still working on both.
jtclark (Mon, 05 Feb 2018 22:44:46 GMT):
I’m trying to test the PTE integration locally
jtclark (Mon, 05 Feb 2018 22:45:28 GMT):
As suggested. Seeing what fails after I uncomment the tests
rameshthoomu (Mon, 05 Feb 2018 22:46:22 GMT):
ok thanks for the update.. let me know if you need any help on these..
rameshthoomu (Mon, 05 Feb 2018 22:46:26 GMT):
take care
jtclark (Mon, 05 Feb 2018 22:47:58 GMT):
@rameshthoomu the main thing on 1446 is getting the output of the script right.
jtclark (Mon, 05 Feb 2018 22:48:22 GMT):
I guess I'll try to test that locally tomorrow as well, b/c with the sandbox
jtclark (Mon, 05 Feb 2018 22:48:46 GMT):
I can't get the log file to "show up" as an artifact.
jtclark (Mon, 05 Feb 2018 22:49:21 GMT):
once I get that part working, I think it should be pretty easy to say pass on "no SQL threats" and fail on anything else.
jtclark (Mon, 05 Feb 2018 22:49:39 GMT):
that's the plan on that one.
suhotskyi (Tue, 06 Feb 2018 11:07:33 GMT):
Has joined the channel.
jtclark (Tue, 06 Feb 2018 14:11:45 GMT):
GM :sunny:
jtclark (Tue, 06 Feb 2018 14:12:20 GMT):
@rameshthoomu so, I'm working on 1446 again this morning. I want to make sure that I am sending the output to the correct location
jtclark (Tue, 06 Feb 2018 14:12:28 GMT):
so that it can be picked up
jtclark (Tue, 06 Feb 2018 14:12:44 GMT):
```
safesql -v ../cmd/fabric-ca-client ../cmd/fabric-ca-server &> $WORKSPACE/safesql_tests.log
```
jtclark (Tue, 06 Feb 2018 14:13:23 GMT):
right now, this is what's inside my version of the safesql_test.sh
rameshthoomu (Tue, 06 Feb 2018 14:13:28 GMT):
Better test this in local machine and implement the same in Jenkins..
jtclark (Tue, 06 Feb 2018 14:13:48 GMT):
ok.
rameshthoomu (Tue, 06 Feb 2018 14:14:26 GMT):
seems you are adding these tests in fabric-ca regular builds..
jtclark (Tue, 06 Feb 2018 14:15:43 GMT):
that sounds like what I'm doing, yes.
rameshthoomu (Tue, 06 Feb 2018 14:15:45 GMT):
please inform the same in #fabric-ca channel.. Please make sure fabric-ca contributors are aware of this change..
jtclark (Tue, 06 Feb 2018 14:16:01 GMT):
ok.
rameshthoomu (Tue, 06 Feb 2018 14:16:26 GMT):
qq: are these tests working now?
jtclark (Tue, 06 Feb 2018 14:16:33 GMT):
it's sitting alongside the other fvt scripts inside scripts/fvt
jtclark (Tue, 06 Feb 2018 14:16:47 GMT):
yes, the test is working. the only problem is determining how to pass/fal
jtclark (Tue, 06 Feb 2018 14:16:47 GMT):
yes, the test is working. the only problem is determining how to pass/fail
jtclark (Tue, 06 Feb 2018 14:17:23 GMT):
right now, it warns about potential issues with a 3rd party package
rameshthoomu (Tue, 06 Feb 2018 14:17:27 GMT):
ok.. see what allen is doing in his fvt tests..
rameshthoomu (Tue, 06 Feb 2018 14:17:37 GMT):
or take his help..
jtclark (Tue, 06 Feb 2018 14:17:41 GMT):
and we dont catch that warning, it just passes
jtclark (Tue, 06 Feb 2018 14:18:03 GMT):
ok
jtclark (Tue, 06 Feb 2018 14:18:36 GMT):
@rameshthoomu allen is aambati ?
rameshthoomu (Tue, 06 Feb 2018 14:19:17 GMT):
Allen Bailey
zhaochy (Wed, 07 Feb 2018 02:25:29 GMT):
hello, it seems something wrong with the jenkins. I can't open https://jenkins.hyperledger.org/job/fabric-sdk-node8-verify-x86_64/349/
rjones (Wed, 07 Feb 2018 02:25:43 GMT):
https://lists.hyperledger.org/pipermail/hyperledger-tsc/2018-February/001370.html
zhaochy (Wed, 07 Feb 2018 02:31:33 GMT):
thanks
sreedharn (Wed, 07 Feb 2018 20:30:38 GMT):
Has joined the channel.
jtclark (Wed, 07 Feb 2018 21:22:56 GMT):
@rameshthoomu I think we *finally* have 1446 in a workable state:
jtclark (Wed, 07 Feb 2018 21:22:57 GMT):
https://jenkins.hyperledger.org/sandbox/job/fabric-ca-verify-x86_64/2/console
jtclark (Wed, 07 Feb 2018 21:23:17 GMT):
you can see that the test fails (as expected) and the output is given in the console output of the job.
jtclark (Wed, 07 Feb 2018 21:23:46 GMT):
I'll go ahead and update the patch
jtclark (Wed, 07 Feb 2018 21:23:58 GMT):
and if you guys can review, that'd be awesome. :-)
rameshthoomu (Wed, 07 Feb 2018 21:25:20 GMT):
before we enable this in production jenkins please check with @smithbk @rennman
rameshthoomu (Wed, 07 Feb 2018 21:26:12 GMT):
I see the test is failed in sandbox, if we enable the same this will fail all the builds.. right ?
jtclark (Wed, 07 Feb 2018 21:26:55 GMT):
yes.
jtclark (Wed, 07 Feb 2018 21:27:00 GMT):
I think what we will probably want
jtclark (Wed, 07 Feb 2018 21:27:09 GMT):
to add... is a skip option eventually
jtclark (Wed, 07 Feb 2018 21:27:19 GMT):
@rennman feel free to chime in
rennman (Wed, 07 Feb 2018 21:28:08 GMT):
yep ... I think Keith will have to weigh in ... in the jira he alluded to the fact that not all of them may be worth fixing, so someone from DEV will have o do some analysis of the results before we proceed
jtclark (Wed, 07 Feb 2018 21:28:18 GMT):
+1
jtclark (Wed, 07 Feb 2018 21:28:37 GMT):
and I think if the deem the "failures" to be false positives
jtclark (Wed, 07 Feb 2018 21:28:37 GMT):
and I think if they deem the "failures" to be false positives
jtclark (Wed, 07 Feb 2018 21:28:52 GMT):
we should probably add some sort of skip in a recheck (or something)
jtclark (Wed, 07 Feb 2018 21:29:37 GMT):
but I'd like Keith to weigh in as @rennman suggests....
rennman (Wed, 07 Feb 2018 21:29:44 GMT):
once the 'baseline' is set we need to fasttrack it before someone injects more errors. I always find myself chasing my tail trying to get the test in before someone pr-emptively breaks it
rameshthoomu (Wed, 07 Feb 2018 21:30:17 GMT):
or I would say, create a bug and ask developer to fix those issues before we enable them.. meanwhile run this job daily if it;s ok to everyone..
rennman (Wed, 07 Feb 2018 21:30:32 GMT):
that's a good idea
jtclark (Wed, 07 Feb 2018 21:30:56 GMT):
before we "enable them" <-- you mean add the test as is
jtclark (Wed, 07 Feb 2018 21:31:06 GMT):
and then ask them to fix before they end up in a release?
rennman (Wed, 07 Feb 2018 21:31:21 GMT):
yes ... link the bug it to the existing jira item and put the ball in DEV court
jtclark (Wed, 07 Feb 2018 21:31:37 GMT):
agreed. I think that's in concert w/ what Keith was saying
rennman (Wed, 07 Feb 2018 21:31:54 GMT):
they can prioritize as they see fit
jtclark (Wed, 07 Feb 2018 21:31:55 GMT):
we should see the failures and have them addressed by the dev team
jtclark (Wed, 07 Feb 2018 21:32:23 GMT):
still it might be good to offer a --skip option b/c they *could* potentially identify something as a false positive
jtclark (Wed, 07 Feb 2018 21:32:34 GMT):
(or false negative?) :-)
jtclark (Wed, 07 Feb 2018 21:33:06 GMT):
for now, I'll submit my patch and let them review.
rameshthoomu (Wed, 07 Feb 2018 22:00:36 GMT):
updated existing **comment phrases** to trigger specific failed builds in the below project gerrit patch sets
**fabric-ca**, **fabric-chaincode-node**,
(Triggers verify jobs on x and z platforms)
`reverify-x`
`reverify-z`
Use `reverify` to trigger all the failed jobs
**fabric-sdk-node**:
(Triggers node8 jobs on x and z platforms)
`reverify-node8x`
`reverify-node8z`
(Triggers node6 jobs on x and z platforms)
`reverify-node6x`
`reverify-node6z`
Use `reverify` to trigger all the failed jobs
**fabric**:
`reverify-x`
`reverify-e2e`
Use `reverify` to trigger all the failed jobs
**fabric-sdk-java**:
`reverify-x`
`reverify-1.0.0`
Use `reverify` to trigger all the failed jobs
**fabric-chaincode-node**:
`reverify-x`
`reverify-z`
Use `reverify` to trigger all the failed job
All other repositories use any of the below comment phrases
`reverify-x` or `reverify`
rameshthoomu (Wed, 07 Feb 2018 22:00:36 GMT):
updated existing **comment phrases** to trigger specific failed builds in the below project gerrit patch sets
**fabric-ca**, **fabric-chaincode-node**,
(Triggers verify jobs on x and z platforms)
`reverify-x`
`reverify-z`
Use `reverify` to trigger all the failed jobs
**fabric-sdk-node**:
(Triggers node8 jobs on x and z platforms)
`reverify-node8x`
`reverify-node8z`
(Triggers node6 jobs on x and z platforms)
`reverify-node6x`
`reverify-node6z`
Use `reverify` to trigger all the failed jobs
**fabric**:
`reverify-x` -- triggers unit-tests job on x86_64
`reverify-e2e` -- triggers e2e job
Use `reverify` to trigger all the failed jobs
**fabric-sdk-java**:
`reverify-x`. -- triggers java tests on latest fabric commits
`reverify-1.0.0` -- triggers java e2e tests on fabric 1.0.0 with latest sdk
Use `reverify` to trigger all the failed jobs
**fabric-chaincode-node**:
`reverify-x` -- triggers verify job on x86_64
`reverify-z` -- triggers verify job on s390x
Use `reverify` to trigger all the failed job
All other repositories use any of the below comment phrases
`reverify-x` or `reverify`. -- Triggers job on x86_64 build node
rameshthoomu (Wed, 07 Feb 2018 22:00:36 GMT):
updated existing **comment phrases** to trigger specific failed builds in the below project gerrit patch sets
**fabric-ca**, **fabric-chaincode-node**,
(Triggers verify jobs on x and z platforms)
`reverify-x`
`reverify-z`
Use `reverify` to trigger all the failed jobs
**fabric-sdk-node**:
(Triggers node8 jobs on x and z platforms)
`reverify-node8x`
`reverify-node8z`
(Triggers node6 jobs on x and z platforms)
`reverify-node6x`
`reverify-node6z`
Use `reverify` to trigger all the failed jobs
**fabric**:
`reverify-x` -- triggers unit-tests job on x86_64
`reverify-e2e` -- triggers e2e job
Use `reverify` to trigger all the failed jobs
**fabric-sdk-java**:
`reverify-x`. -- triggers java tests on latest fabric commits
`reverify-1.0.0` -- triggers java e2e tests on fabric 1.0.0 with latest sdk
Use `reverify` to trigger all the failed jobs
**fabric-chaincode-node**:
`reverify-x` -- triggers verify job on x86_64
`reverify-z` -- triggers verify job on s390x
Use `reverify` to trigger all the failed job
All other repositories use any of the below comment phrases
`reverify-x` or `reverify`. -- Triggers job on x86_64 build node
rameshthoomu (Wed, 07 Feb 2018 22:00:36 GMT):
updated existing **comment phrases** to trigger specific failed builds in the below project gerrit patch sets
**fabric-ca**, **fabric-chaincode-node**,
(Triggers verify jobs on x and z platforms)
`reverify-x`
`reverify-z`
Use `reverify` to trigger all the failed jobs
**fabric-sdk-node**:
(Triggers node8 jobs on x and z platforms)
`reverify-node8x`
`reverify-node8z`
(Triggers node6 jobs on x and z platforms)
`reverify-node6x`
`reverify-node6z`
Use `reverify` to trigger all the failed jobs
**fabric**:
`reverify-x` -- triggers unit-tests job on x86_64
`reverify-e2e` -- triggers e2e job
Use `reverify` to trigger all the failed jobs
**fabric-sdk-java**:
`reverify-x`. -- triggers java tests on latest fabric commits
`reverify-1.0.0` -- triggers java e2e tests on fabric 1.0.0 with latest sdk
Use `reverify` to trigger all the failed jobs
**fabric-chaincode-node**:
`reverify-x` -- triggers verify job on x86_64
`reverify-z` -- triggers verify job on s390x
Use `reverify` to trigger all the failed job
All other repositories use any of the below comment phrases
`reverify-x` or `reverify`. -- Triggers job on x86_64 build node
jtclark (Wed, 07 Feb 2018 22:09:43 GMT):
patch submitted: https://gerrit.hyperledger.org/r/#/c/17649/
rjones (Fri, 09 Feb 2018 00:47:11 GMT):
There will be a 30 minute Jenkins/Nexus outage starting at 1700 Pacific, tonight.
pravindia (Sun, 11 Feb 2018 04:45:39 GMT):
Has joined the channel.
dave.enyeart (Tue, 13 Feb 2018 17:43:10 GMT):
@rameshthoomu Any idea why rebuild-e2e didn't work on https://gerrit.hyperledger.org/r/#/c/13023/ ?
rameshthoomu (Tue, 13 Feb 2018 18:11:30 GMT):
try reverify-e2e
davidkhala (Wed, 14 Feb 2018 02:23:53 GMT):
Has joined the channel.
rjones (Wed, 14 Feb 2018 18:59:58 GMT):
There will be an emergency Jenkins outage today for both sandbox and production. More on timing soon.
susmita (Wed, 14 Feb 2018 19:09:58 GMT):
Has joined the channel.
rameshthoomu (Wed, 14 Feb 2018 19:40:50 GMT):
@nfrunza see this https://jenkins.hyperledger.org/sandbox/job/blockchain-explorer-node6-verify-x86_64/HTML_Report/
nfrunza (Wed, 14 Feb 2018 19:42:29 GMT):
nice, will the link we available for every job number?
rameshthoomu (Wed, 14 Feb 2018 19:42:47 GMT):
yes
rameshthoomu (Wed, 14 Feb 2018 19:43:07 GMT):
see one here https://jenkins.hyperledger.org/sandbox/job/blockchain-explorer-node6-verify-x86_64/
rjones (Wed, 14 Feb 2018 23:03:08 GMT):
This will impact us: https://status.linuxfoundation.org/incidents/v0bs1g958b6g outages this Saturday
rjones (Wed, 14 Feb 2018 23:03:08 GMT):
This will impact us: https://status.linuxfoundation.org/incidents/v0bs1g958b6g outages this Friday
rjones (Wed, 14 Feb 2018 23:26:09 GMT):
all three jenkins instance are up-to-date on security patches.
nfrunza (Thu, 15 Feb 2018 22:22:30 GMT):
Hi
nfrunza (Thu, 15 Feb 2018 22:23:20 GMT):
i have a question, a new user in order to commit into gerrit id is required permission ?
jwagantall (Thu, 15 Feb 2018 23:13:17 GMT):
Hi team, there will be a Gerrit-Jenkins outage today at 16:30 Pacific to upgrade Gerrit to v2.14.6. This should just take about 30 min or less.
jwagantall (Thu, 15 Feb 2018 23:15:29 GMT):
@nfrunza you dont need additional permissions, just as long as you are a registered user you should be able to push a change into Gerrit
nfrunza (Thu, 15 Feb 2018 23:20:49 GMT):
thank you
rjones (Thu, 15 Feb 2018 23:22:07 GMT):
@nfrunza you can experiment in the sandbox project if you like
rjones (Thu, 15 Feb 2018 23:22:43 GMT):
https://gerrit.hyperledger.org/r/#/admin/projects/lf-sandbox
nfrunza (Thu, 15 Feb 2018 23:22:50 GMT):
@rjones another team member was facing issues
rjones (Thu, 15 Feb 2018 23:23:25 GMT):
I wonder if they were pushing to the branch directly, instead of `refs/for/branch` ?
nfrunza (Thu, 15 Feb 2018 23:24:19 GMT):
yes
nfrunza (Thu, 15 Feb 2018 23:24:33 GMT):
using refs
nfrunza (Thu, 15 Feb 2018 23:25:20 GMT):
this is the push command git push ssh://userid@gerrit.hyperledger.org:29418/blockchain-explorer HEAD:refs/for/release-3
rjones (Thu, 15 Feb 2018 23:25:57 GMT):
could you have them join chat, and ask them to ask in #infra-support maybe?
rjones (Thu, 15 Feb 2018 23:26:05 GMT):
since we're off topic
nfrunza (Thu, 15 Feb 2018 23:26:40 GMT):
sure, they are done for today i'll let them know thank you
rjones (Thu, 15 Feb 2018 23:26:59 GMT):
There is an upcoming chat outage to upgrade. More on timing when I know timing.
nfrunza (Thu, 15 Feb 2018 23:27:33 GMT):
thank you
jwagantall (Fri, 16 Feb 2018 00:47:31 GMT):
Team, Gerrit is now v2.14.6.. services are back! .. thanks!
rameshthoomu (Fri, 16 Feb 2018 15:32:04 GMT):
`z` build nodes went offline.. Hardware support team is actively looking at the issue.
gospodin.bodurov (Mon, 19 Feb 2018 08:21:13 GMT):
Has joined the channel.
vitiko (Mon, 19 Feb 2018 11:42:14 GMT):
Has joined the channel.
mastersingh24 (Mon, 19 Feb 2018 22:55:26 GMT):
@rameshthoomu - I just tagged v1.0.6 and looks like the x86 and z publish jobs ran fine. The ppe64le job failed
mastersingh24 (Mon, 19 Feb 2018 22:55:26 GMT):
@rameshthoomu - I just tagged v1.0.6 and looks like the x86 and z publish jobs ran fine. The ppc64le job failed
mastersingh24 (Mon, 19 Feb 2018 22:55:26 GMT):
@rameshthoomu - I just tagged v1.0.6 and looks like the x86 and z publish jobs ran fine. The ppc64le job failed
https://jenkins.hyperledger.org/view/fabric-app/job/fabric-app-image-release-docker-ppc64le/lastFailedBuild/
rameshthoomu (Mon, 19 Feb 2018 23:27:51 GMT):
re-trigger did the trick..
rameshthoomu (Mon, 19 Feb 2018 23:28:19 GMT):
Published from ppc64le
mastersingh24 (Tue, 20 Feb 2018 00:01:34 GMT):
awesome - thanks @rameshthoomu !
harrijk (Tue, 20 Feb 2018 10:45:40 GMT):
The TestMSPWithIntermediateCAs unit test uses certs from `fabric/msp/intermediate/testdata`
All of those certs expired last night at around 8:00 PM EST. This is causing failures for this test case.
rameshthoomu (Tue, 20 Feb 2018 12:49:09 GMT):
@harrijk pls create Jira
rameshthoomu (Tue, 20 Feb 2018 12:49:09 GMT):
@harrijk pls create Jira Bug
harrijk (Tue, 20 Feb 2018 12:49:21 GMT):
It is not my problem
harrijk (Tue, 20 Feb 2018 12:49:33 GMT):
Please tell Angelo
rameshthoomu (Tue, 20 Feb 2018 12:49:35 GMT):
🤔
harrijk (Tue, 20 Feb 2018 12:49:39 GMT):
It is his issue
harrijk (Tue, 20 Feb 2018 12:49:47 GMT):
He created the certs that have expired
rameshthoomu (Tue, 20 Feb 2018 12:50:16 GMT):
Sure.
harrijk (Tue, 20 Feb 2018 12:51:58 GMT):
Thanks.
rameshthoomu (Tue, 20 Feb 2018 13:16:31 GMT):
@harrijk @adc https://jira.hyperledger.org/browse/FAB-8393
rameshthoomu (Tue, 20 Feb 2018 14:01:46 GMT):
Patch has been submitted https://gerrit.hyperledger.org/r/#/c/18081/
rameshthoomu (Tue, 20 Feb 2018 14:16:21 GMT):
@rjones @jwagantall could you please review this and merge https://gerrit.hyperledger.org/r/#/c/18045/
rameshthoomu (Tue, 20 Feb 2018 14:19:25 GMT):
I will be OOO today but will be available on mobile
rameshthoomu (Wed, 21 Feb 2018 06:33:28 GMT):
FAB-8425
rameshthoomu (Wed, 21 Feb 2018 16:32:24 GMT):
Below are the open issues causing CI failures
FAB-8425 FAB-8430 FAB-8438 FAB-8373
rameshthoomu (Wed, 21 Feb 2018 16:32:24 GMT):
Below are the open issues causing CI failures
FAB-8415 FAB-8430 FAB-8438 FAB-8373
jtclark (Wed, 21 Feb 2018 17:12:13 GMT):
hi all :wave:
jtclark (Wed, 21 Feb 2018 17:12:55 GMT):
have either of you seen this issue when running `make ci-smoke` out of fabric-tests:
jtclark (Wed, 21 Feb 2018 17:13:03 GMT):
```
docker tag hyperledger/fabric-tools hyperledger/fabric-tools:x86_64-1.1.0-beta-snapshot-5b4c925
make[1]: Leaving directory '/home/ibmadmin/Code/go/src/github.com/hyperledger/fabric'
make[1]: Entering directory '/home/ibmadmin/Code/go/src/github.com/hyperledger/fabric'
build/bin/peer
CGO_CFLAGS=" " GOBIN=/home/ibmadmin/Code/go/src/github.com/hyperledger/fabric/build/bin go install -tags "experimental" -ldflags "-X github.com/hyperledger/fabric/common/metadata.Version=1.1.0-beta-snapshot-5b4c925 -X github.com/hyperledger/fabric/common/metadata.BaseVersion=0.4.6 -X github.com/hyperledger/fabric/common/metadata.BaseDockerLabel=org.hyperledger.fabric -X github.com/hyperledger/fabric/common/metadata.DockerNamespace=hyperledger -X github.com/hyperledger/fabric/common/metadata.BaseDockerNamespace=hyperledger -X github.com/hyperledger/fabric/common/metadata.Experimental=true" github.com/hyperledger/fabric/peer
# github.com/hyperledger/fabric/vendor/github.com/miekg/pkcs11
vendor/github.com/miekg/pkcs11/pkcs11.go:26:18: fatal error: ltdl.h: No such file or directory
compilation terminated.
Makefile:258: recipe for target 'build/bin/peer' failed
make[1]: *** [build/bin/peer] Error 2
make[1]: Leaving directory '/home/ibmadmin/Code/go/src/github.com/hyperledger/fabric'
Makefile:57: recipe for target 'docker-images' failed
make: *** [docker-images] Error 2
```
jtclark (Wed, 21 Feb 2018 17:13:55 GMT):
I want to say that this is some sort of PATH problem, but I'm checking here just in case
rameshthoomu (Wed, 21 Feb 2018 17:16:01 GMT):
try this `sudo apt install libltdl-dev`
jtclark (Wed, 21 Feb 2018 17:18:48 GMT):
ok
jtclark (Wed, 21 Feb 2018 18:02:40 GMT):
that worked
jtclark (Wed, 21 Feb 2018 18:02:49 GMT):
I've got another error re: behave
jtclark (Wed, 21 Feb 2018 18:03:08 GMT):
but I got past that the other one
jtclark (Wed, 21 Feb 2018 18:03:08 GMT):
but I got past the other one
jtclark (Wed, 21 Feb 2018 18:03:38 GMT):
@rameshthoomu :point_up_2_tone3:
jtclark (Wed, 21 Feb 2018 18:16:52 GMT):
```
cd /home/ibmadmin/Code/go/src/github.com/hyperledger/fabric-test/regression/smoke && ./runSmokeTestSuite.sh
========== Behave feature and system tests...
./runSmokeTestSuite.sh: line 11: behave: command not found
/home/ibmadmin/Code/go/src/github.com/hyperledger/fabric-test/regression/smoke
========== System Test using PTE and NL tools...
./runSmokeTestSuite.sh: line 15: py.test: command not found
========== Orderer component test using OTE and NL tools...
./runSmokeTestSuite.sh: line 18: py.test: command not found
Makefile:73: recipe for target 'smoke-tests' failed
make: *** [smoke-tests] Error 127
```
rameshthoomu (Wed, 21 Feb 2018 18:23:41 GMT):
try this `$ cd /path/to/fabric-test/feature; ./scripts/install_behave.sh`
rameshthoomu (Wed, 21 Feb 2018 18:24:25 GMT):
you have follow the pre-requisties to run these scripts https://github.com/hyperledger/fabric-test/tree/master/feature
jtclark (Wed, 21 Feb 2018 18:35:39 GMT):
ah
jtclark (Wed, 21 Feb 2018 18:35:39 GMT):
ok
jtclark (Wed, 21 Feb 2018 19:00:26 GMT):
I think this is working now. thanks
jtclark (Wed, 21 Feb 2018 19:36:20 GMT):
@rameshthoomu just so you know where I am with this JIRA ticket: https://jira.hyperledger.org/browse/FAB-5283
rameshthoomu (Wed, 21 Feb 2018 19:38:53 GMT):
Ok I see comments your comments in the JIRA.. Instead of setting up another machine, i would suggest you to use sandbox.
rameshthoomu (Wed, 21 Feb 2018 19:39:15 GMT):
anyway you already setup your local dev environment..
rameshthoomu (Wed, 21 Feb 2018 19:40:18 GMT):
If you see @scottz comments in the JIRA, 5283 is working as expected in local machine but fails the same in Jenkins..
rameshthoomu (Wed, 21 Feb 2018 19:41:03 GMT):
better you use sandbox to integrate PTE tests in daily test suite..
jtclark (Wed, 21 Feb 2018 19:44:32 GMT):
understood
jtclark (Wed, 21 Feb 2018 19:44:43 GMT):
but, if I'm testing new PTE tests
jtclark (Wed, 21 Feb 2018 19:44:50 GMT):
I want to know that what I'm doing is going to work
jtclark (Wed, 21 Feb 2018 19:44:59 GMT):
before I submit patches and such
jtclark (Wed, 21 Feb 2018 19:45:30 GMT):
I figured that setting up my own environment for testing is less resource intensive on the sandbox
jtclark (Wed, 21 Feb 2018 19:45:55 GMT):
when you say, "fails the same in Jenkins"
jtclark (Wed, 21 Feb 2018 19:46:15 GMT):
are you saying that the failures I'm now getting on my sandbox are the same as we're seeing on the sandbox?
jtclark (Wed, 21 Feb 2018 19:46:24 GMT):
@rameshthoomu ^^^^^^^
rameshthoomu (Wed, 21 Feb 2018 19:50:26 GMT):
No.. Jenkins sandbox has that setup already.. all you have to do is just keep these lines in `runDailyTestSuite.sh`
```
echo "========== System Test Performance Stress tests driven by PTE tool..."
cp -r ../../tools/PTE $WORKSPACE/gopath/src/github.com/hyperledger/fabric-test/fabric-sdk-node/test/
cd $WORKSPACE/gopath/src/github.com/hyperledger/fabric-test/fabric-sdk-node
./../pre_setup.sh && npm config set prefix ~/npm && npm install && npm install -g gulp
gulp ca || exit 1
ls
cd ../regression/daily
echo "==========PY Test============"
py.test -v --junitxml results_systest_pte.xml systest_pte.py
```
rameshthoomu (Wed, 21 Feb 2018 19:50:26 GMT):
No.. Jenkins sandbox has that setup already.. all you have to do is just keep these lines in `runDailyTestSuite.sh`
```
echo "========== System Test Performance Stress tests driven by PTE tool..."
cp -r ../../tools/PTE $WORKSPACE/gopath/src/github.com/hyperledger/fabric-test/fabric-sdk-node/test/
cd $WORKSPACE/gopath/src/github.com/hyperledger/fabric-test/fabric-sdk-node
./../pre_setup.sh && npm config set prefix ~/npm && npm install && npm install -g gulp
gulp ca || exit 1
ls
cd ../regression/daily
echo "==========PY Test============"
py.test -v --junitxml results_systest_pte.xml systest_pte.py
```
also add `@git submodule foreach git pull origin master` to `git-update` target in makefile
rameshthoomu (Wed, 21 Feb 2018 19:50:38 GMT):
and `make ci-daily` from sandbox..
rameshthoomu (Wed, 21 Feb 2018 19:50:38 GMT):
and `make ci-daily` from jenkins sandbox..
jtclark (Wed, 21 Feb 2018 21:40:53 GMT):
@rameshthoomu trying to make this work in my local environment.... perhaps I'll take another look at this tmrw.
rameshthoomu (Wed, 21 Feb 2018 21:42:31 GMT):
ok.. we can check this tomorrow in lab..
rickr (Thu, 22 Feb 2018 04:28:00 GMT):
https://gerrit.hyperledger.org/r/#/c/18171/ nothing starting up here
rickr (Thu, 22 Feb 2018 04:31:19 GMT):
Just started f
rickr (Thu, 22 Feb 2018 04:31:19 GMT):
Just started
dbhalgami (Thu, 22 Feb 2018 10:49:00 GMT):
Has joined the channel.
dbhalgami (Thu, 22 Feb 2018 10:49:28 GMT):
Why hyperledger/fabric-ccenv:x86_64-1.1.0-preview docker image is not having "github.com/hyperledger/fabric/core/chaincode/lib/cid" folder???
rickr (Thu, 22 Feb 2018 12:05:46 GMT):
Why not use 1.1.0-alpha ?
jtclark (Thu, 22 Feb 2018 13:56:52 GMT):
GM
jtclark (Thu, 22 Feb 2018 13:57:03 GMT):
@rameshthoomu are you coming into the office today?
rameshthoomu (Thu, 22 Feb 2018 13:57:14 GMT):
in lab
jtclark (Thu, 22 Feb 2018 13:57:27 GMT):
I'm here.
PraveenKumar5 (Fri, 23 Feb 2018 00:47:12 GMT):
Has joined the channel.
mastersingh24 (Sun, 25 Feb 2018 13:51:40 GMT):
@dbhalgami - It is an optional library so we do not include it in the ccenv image
(https://chat.hyperledger.org/channel/fabric-ci?msg=nrcJgWupX682Zo4GG)
phanikumar (Mon, 26 Feb 2018 08:08:15 GMT):
Has joined the channel.
jtclark (Mon, 26 Feb 2018 14:56:27 GMT):
GM all :sunrise:
jtclark (Mon, 26 Feb 2018 14:56:35 GMT):
couple of questions:
jtclark (Mon, 26 Feb 2018 14:57:11 GMT):
1) There are a couple JIRA tasks that are no longer needed. I have them in the UNVERIFIED state, but is there a way to simply remove them? @rjones, @rameshthoomu, @jwagantall
gskerry (Mon, 26 Feb 2018 17:13:37 GMT):
Has joined the channel.
rjones (Mon, 26 Feb 2018 17:58:34 GMT):
@jtclark I saw an alert from you about a JIRA you needed help with but I can't find the message. help?
jtclark (Mon, 26 Feb 2018 17:59:33 GMT):
yeah, I removed it. @rameshthoomu helped me via DM. the question was about removing JIRA tasks that are no longer needed
jtclark (Mon, 26 Feb 2018 17:59:48 GMT):
basically, move them to DONE and add a comment
jtclark (Mon, 26 Feb 2018 18:00:02 GMT):
unless there is actually a procedure for removing them....
rjones (Mon, 26 Feb 2018 18:01:21 GMT):
oh OK. No, they shouldn't be deleted. The only ones I've deleted were from spammers
rjones (Mon, 26 Feb 2018 18:01:25 GMT):
_I think_
jtclark (Mon, 26 Feb 2018 18:01:33 GMT):
sounds good
rjones (Mon, 26 Feb 2018 18:01:33 GMT):
I try not to change history
rjones (Mon, 26 Feb 2018 18:01:52 GMT):
anyway, I am glad you have it worked out
jtclark (Mon, 26 Feb 2018 18:03:20 GMT):
thanks. just low-hanging fruit to get out of the way
rohitadivi (Mon, 26 Feb 2018 20:34:29 GMT):
Has left the channel.
Ammu (Tue, 27 Feb 2018 11:16:21 GMT):
can any1 solve this error?
Ammu (Tue, 27 Feb 2018 11:16:23 GMT):
stsrt.png
rameshthoomu (Tue, 27 Feb 2018 12:05:03 GMT):
@Ammu either you have to build or pull third party docker images.. we don’t publish latest tag
rameshthoomu (Thu, 01 Mar 2018 04:20:45 GMT):
@harrijk I see unit-tests are failing in s390x build consistently https://jira.hyperledger.org/browse/FAB-8598
rameshthoomu (Thu, 01 Mar 2018 04:20:45 GMT):
@harrijk I see fabric unit-tests are failing in s390x build consistently https://jira.hyperledger.org/browse/FAB-8598
harrijk (Thu, 01 Mar 2018 13:51:22 GMT):
@rameshthoomu Please check the updated JIRA https://jira.hyperledger.org/browse/FAB-8598. It appears that this has been resolved. Can you re-trigger another s390x verify?
rameshthoomu (Thu, 01 Mar 2018 14:11:27 GMT):
It’s working now
rameshthoomu (Thu, 01 Mar 2018 14:11:40 GMT):
Will update Jira
rjones (Tue, 06 Mar 2018 17:04:16 GMT):
mastersingh24
jtclark (Wed, 07 Mar 2018 17:52:49 GMT):
Hi @rameshthoomu - quick update on FAB-5283 - I ran the fabric-test-daily-390x job again yesterday with the 'while loop' you suggested that I add in? The job still bombs. :-(
rameshthoomu (Wed, 07 Mar 2018 17:53:44 GMT):
Pls work with Dongming
jtclark (Wed, 07 Mar 2018 17:54:36 GMT):
sure
jtclark (Wed, 07 Mar 2018 17:54:43 GMT):
I pinged him about it
jtclark (Wed, 07 Mar 2018 17:54:53 GMT):
waiting to hear back, just wanted to update you
jtclark (Wed, 07 Mar 2018 17:54:59 GMT):
I talked to him yesterday
rameshthoomu (Wed, 07 Mar 2018 17:55:13 GMT):
Sure ..
jtclark (Wed, 07 Mar 2018 17:55:24 GMT):
and we discovered that the FAB-3833-2i scenario doesn't run the test cases in order
jtclark (Wed, 07 Mar 2018 17:55:58 GMT):
if you remember, we saw the query test run first, instead of invoke
jtclark (Wed, 07 Mar 2018 17:56:13 GMT):
anyway, I'll work with @dongming on it.
rjones (Wed, 07 Mar 2018 20:55:51 GMT):
@tongli @rameshthoomu what I propose to do is to enable you two to be able to use https://jenkins-new.hyperledger.org/ as a sandbox with the provision that you only build jobs that trigger on changes in the `lf-sandbox` repo.
rjones (Wed, 07 Mar 2018 20:56:56 GMT):
@tongli @rameshthoomu you will be able to create manual jobs, and use JJB, as you would in https://jenkins.hyperledger.org/sandbox/, but only against `lf-sandbox` (or a new test repo, if you'd like). I'd prefer to use `lf-sandbox` since it already has a few custom voting options
tongli (Wed, 07 Mar 2018 20:57:01 GMT):
Ok. So these labels have been created?
rjones (Wed, 07 Mar 2018 20:57:26 GMT):
in `lf-sandbox`, we have three additional custom labels.
rjones (Wed, 07 Mar 2018 20:57:55 GMT):
if you can get your workflow working on `lf-sandbox` repo then you can migrate it to real repos without my intervention.
rjones (Wed, 07 Mar 2018 20:58:30 GMT):
@tongli @rameshthoomu what I want to do is enable you to work on this without my being critical path, and to leave the current sandbox for people that can test without the gerrit trigger.
tongli (Wed, 07 Mar 2018 20:58:50 GMT):
So how do we post vote against the label? I was thinking using the gerrit trigger.
rjones (Wed, 07 Mar 2018 20:58:57 GMT):
enabling the gerrit trigger in the /sandbox/ would not work
tongli (Wed, 07 Mar 2018 20:59:08 GMT):
I like that. I think that will be the only question I have at present.
rjones (Wed, 07 Mar 2018 20:59:16 GMT):
in the job configuration, you can choose how it votes. let me show you
tongli (Wed, 07 Mar 2018 20:59:34 GMT):
Ok
rjones (Wed, 07 Mar 2018 21:01:01 GMT):
if you go to https://jenkins-new.hyperledger.org/job/step-0/configure and select gerrit trigger -> advanced, you can see where to put in custom votes. they will look like this answer: https://stackoverflow.com/a/43848896/5453
rjones (Wed, 07 Mar 2018 21:01:11 GMT):
(I still need to add you two to the jenkins ACL give me a second)
rjones (Wed, 07 Mar 2018 21:03:56 GMT):
OK you two should have the same access to jenkins-new as you have for /sandbox/. Do not create jobs with triggers against any project except `lf-sandbox`, OK?
rjones (Wed, 07 Mar 2018 21:04:32 GMT):
@tongli @rameshthoomu I attached a `hyp-p` node for faster turn arounds on shell scripts
tongli (Wed, 07 Mar 2018 21:04:51 GMT):
Ok. Easy enough.
tongli (Wed, 07 Mar 2018 21:04:55 GMT):
Thanks.
rjones (Wed, 07 Mar 2018 21:05:28 GMT):
sure. I hope this unblocks you. I set the rules for `lf-sandbox` to 2+2, I think. If you need a vote on a change let me know.
tongli (Wed, 07 Mar 2018 21:05:40 GMT):
K
tongli (Wed, 07 Mar 2018 21:05:55 GMT):
Custom labels are already created right?
rjones (Wed, 07 Mar 2018 21:06:09 GMT):
this is the command I was using to vote: ```ssh -p 29418 ryjones@gerrit.hyperledger.org gerrit review 18797,2 -l Docs=-1 -l Unit-Tests=1 -l Code-Review=-1
```
rjones (Wed, 07 Mar 2018 21:06:15 GMT):
for instance
rjones (Wed, 07 Mar 2018 21:06:32 GMT):
to vote from my desktop
rjones (Wed, 07 Mar 2018 21:09:12 GMT):
@rameshthoomu @tongli if you look here: https://gerrit.hyperledger.org/r/#/q/project:lf-sandbox you will see custom labels
rameshthoomu (Wed, 07 Mar 2018 21:10:38 GMT):
cool.. Will create a workflow in jenkins-new using lf-sandbox and let you know the update
rjones (Wed, 07 Mar 2018 21:10:56 GMT):
thank you. I will be watching closely. I have great interest in this.
rameshthoomu (Wed, 07 Mar 2018 21:11:18 GMT):
how many x nodes available in jenkins-new?
rjones (Wed, 07 Mar 2018 21:12:14 GMT):
10
rjones (Wed, 07 Mar 2018 21:12:40 GMT):
@rameshthoomu the hyp-x nodes have a 30 minute timeout so you can re-use nodes for faster turn around
rameshthoomu (Wed, 07 Mar 2018 21:13:16 GMT):
ok
rjones (Wed, 07 Mar 2018 21:14:07 GMT):
I suggest using the hyp-p node as much as you can, since it will be there
rjones (Wed, 07 Mar 2018 21:14:13 GMT):
but, do as you will.
rjones (Wed, 07 Mar 2018 21:18:03 GMT):
@rameshthoomu should I delete the three jobs I have there?
rameshthoomu (Wed, 07 Mar 2018 21:18:27 GMT):
you can keep them..
rjones (Wed, 07 Mar 2018 21:19:44 GMT):
@rameshthoomu I deleted my changes in Gerrit, so you will need to push a couple test changes
jtclark (Thu, 08 Mar 2018 15:10:41 GMT):
GM all
jtclark (Thu, 08 Mar 2018 15:11:07 GMT):
re: FAB-5283 - I wrote up the exact way that I've tried to test it thus far
jtclark (Thu, 08 Mar 2018 15:11:29 GMT):
@rameshthoomu and I should get a chance to work on this one today.
rjones (Thu, 08 Mar 2018 15:50:20 GMT):
@rameshthoomu https://jenkins-new.hyperledger.org/job/fabric-byfn-verify-x86_64/ points at the wrong gerrit repo so I disabled it
rameshthoomu (Thu, 08 Mar 2018 15:51:48 GMT):
oh. that supposed to go to sandbox jenkins..
rameshthoomu (Thu, 08 Mar 2018 15:52:20 GMT):
didn;t change my jenkins.ini file.. will delete that job
dave.enyeart (Thu, 08 Mar 2018 22:39:23 GMT):
@rameshthoomu @bretharrison any idea why e2e CI with node sdk keeps failing in release-1.0? https://gerrit.hyperledger.org/r/#/c/18883/
rameshthoomu (Fri, 09 Mar 2018 02:09:52 GMT):
@dave.enyeart I see orderer is exited in the log with error
```
[36morderer.example.com |[0m panic: Error creating configtx manager and handlers: Error deserializing key Capabilities for group /Channel: Unexpected key Capabilities
[36morderer.example.com |[0m
```
rameshthoomu (Fri, 09 Mar 2018 02:10:17 GMT):
looking into it..
dave.enyeart (Fri, 09 Mar 2018 03:06:36 GMT):
@rameshthoomu Capabilities are new in 1.1, there should be nothing related to Capabilities in the release-1.0 CI. Can you tell where it is coming from? @jyellick is the Capabilities expert if you need any help.
rameshthoomu (Fri, 09 Mar 2018 03:07:59 GMT):
CI script is pulling code from fabric-sdk-node master branch..
rameshthoomu (Fri, 09 Mar 2018 03:10:15 GMT):
In my sandbox, I have tested above patch on fabric (release branch), fabric-ca(release branch), fabric-sdk-node (release branch) and fabric-sdk-java (1.0.1 as there is no release branch).. I am not seeing fabric-sdk-node failures but I see fabric-sdk-java e2e tests are failing..
rameshthoomu (Fri, 09 Mar 2018 03:11:27 GMT):
@dave.enyeart do you think above is correct flow on release patchset?
dave.enyeart (Fri, 09 Mar 2018 03:20:01 GMT):
ignore fabric-sdk-java for a moment... previously all the 1.0.x CI should use release branch of every project. recently release was cloned into release-1.0 for fabric and fabric-ca. we will do the same for fabric-sdk-node shortly. at that time, all the 1.0.x CI should use release-1.0 branch of every project.
dave.enyeart (Fri, 09 Mar 2018 03:20:01 GMT):
ignore fabric-sdk-java for a moment... previously all the 1.0.x CI should use release branch of every project. recently release was cloned into release-1.0 for fabric and fabric-ca. we will do the same for fabric-sdk-node shortly. at that time, all the 1.0.x CI should use release-1.0 branch of every project. would it help if we go ahead and create the release-1.0 branch for fabric-sdk-node? then you can align all the 1.0.x CI.
dave.enyeart (Fri, 09 Mar 2018 03:22:08 GMT):
release branch will be sunset once we confirm release-1.0 branches are working properly
dave.enyeart (Fri, 09 Mar 2018 03:22:35 GMT):
@rameshthoomu
rameshthoomu (Fri, 09 Mar 2018 03:24:46 GMT):
yes that helps
rameshthoomu (Fri, 09 Mar 2018 03:25:49 GMT):
so, you want me to disable fabric-sdk-java tests temporarily from fabric-e2e ?
dave.enyeart (Fri, 09 Mar 2018 03:34:29 GMT):
@rameshthoomu can you disable fabric-sdk-java e2e in the 1.0.x CI only?
rameshthoomu (Fri, 09 Mar 2018 03:35:22 GMT):
sure will do that..
dave.enyeart (Fri, 09 Mar 2018 03:35:43 GMT):
thx. and you want us to go ahead and create the release-1.0 branch for fabric-sdk-node?
rameshthoomu (Fri, 09 Mar 2018 03:36:20 GMT):
and till you create 1.0.x for sdk-node, will clone from release branch for all 1.0.x builds
dave.enyeart (Fri, 09 Mar 2018 03:36:42 GMT):
sounds good.
dave.enyeart (Fri, 09 Mar 2018 03:37:21 GMT):
we'll ask @bretharrison to do the `release` to `release-1.0` clone in fabric-sdk-node, since he is lead maintainer on that one
rameshthoomu (Fri, 09 Mar 2018 03:37:59 GMT):
sure..
dave.enyeart (Fri, 09 Mar 2018 03:39:21 GMT):
also we'll ask @bretharrison to create `release-1.1` branch from `master` very soon. @rameshthoomu does anything need to be updated in 1.1 CI when that change is made?
dave.enyeart (Fri, 09 Mar 2018 03:39:54 GMT):
to ensure all the 1.1 CI is aligned at `release-1.1` branch?
dave.enyeart (Fri, 09 Mar 2018 03:39:54 GMT):
to ensure all the 1.1 CI is aligned at `release-1.1` branches?
dave.enyeart (Fri, 09 Mar 2018 03:40:52 GMT):
to be clear - we will publish all 1.1 release artifacts from the new `release-1.1` branches
dave.enyeart (Fri, 09 Mar 2018 03:40:52 GMT):
to be clear - we will publish all 1.1 GA release artifacts from the new `release-1.1` branches
dave.enyeart (Fri, 09 Mar 2018 03:40:52 GMT):
to be clear - we will publish all 1.1 GA release artifacts from the new `release-1.1` branches (expected end of next week)
rameshthoomu (Fri, 09 Mar 2018 03:42:31 GMT):
I have to update the CI configuration to checkout to the specific branch..Once the node is ready with branches, then we are good to go..
dave.enyeart (Fri, 09 Mar 2018 03:42:43 GMT):
ok
dave.enyeart (Fri, 09 Mar 2018 03:43:02 GMT):
now, concerning fabric-sdk-java, let's take that up over in the fabric-sdk-java channel
rameshthoomu (Fri, 09 Mar 2018 03:43:20 GMT):
ok
bretharrison (Fri, 09 Mar 2018 09:37:42 GMT):
@rameshthoomu @dave.enyeart The CI is failing due to
```
[36morderer.example.com |[0m [35m2018-03-08 21:14:25.105 UTC [orderer/multichain] newLedgerResources -> CRIT 068[0m Error creating configtx manager and handlers: Error deserializing key Capabilities for group /Channel: Unexpected key Capabilities
[36morderer.example.com |[0m panic: Error creating configtx manager and handlers: Error deserializing key Capabilities for group /Channel: Unexpected key Capabilities
[36morderer.example.com |[0m
[36morderer.example.com |[0m goroutine 1 [running]:
[36morderer.example.com |[0m panic(0xb44a80, 0xc4203896a0)
[36morderer.example.com |[0m /opt/go/src/runtime/panic.go:500 +0x1a1
[36morderer.example.com |[0m github.com/hyperledger/fabric/vendor/github.com/op/go-logging.(*Logger).Panicf(0xc4201feba0, 0xc860ec, 0x30, 0xc4203895f0, 0x1, 0x1)
[36morderer.example.com |[0m /opt/gopath/src/github.com/hyperledger/fabric/vendor/github.com/op/go-logging/logger.go:194 +0x127
[36morderer.example.com |[0m github.com/hyperledger/fabric/orderer/multichain.(*multiLedger).newLedgerResources(0xc42034a640, 0xc42037b2c0, 0xc42037b2c0)
[36morderer.example.com |[0m /opt/gopath/src/github.com/hyperledger/fabric/orderer/multichain/manager.go:153 +0x393
[36morderer.example.com |[0m github.com/hyperledger/fabric/orderer/multichain.NewManagerImpl(0x1246880, 0xc420394140, 0xc42037ad80, 0x1243480, 0x128b4a8, 0x0, 0x0)
[36morderer.example.com |[0m /opt/gopath/src/github.com/hyperledger/fabric/orderer/multichain/manager.go:103 +0x23b
[36morderer.example.com |[0m main.initializeMultiChainManager(0xc420200d80, 0x1243480, 0x128b4a8, 0xc420204dd0, 0x1)
[36morderer.example.com |[0m /opt/gopath/src/github.com/hyperledger/fabric/orderer/main.go:220 +0x27a
[36morderer.example.com |[0m main.main()
[36morderer.example.com |[0m /opt/gopath/src/github.com/hyperledger/fabric/orderer/main.go:75 +0x392
```
@rameshthoomu @bretharrison any idea why e2e CI with node sdk keeps failing in release-1.0? https://gerrit.hyperledger.org/r/#/c/18883/
bretharrison (Fri, 09 Mar 2018 09:37:42 GMT):
@rameshthoomu @dave.enyeart The CI is failing due to the orderer crashing
```
[36morderer.example.com |[0m [35m2018-03-08 21:14:25.105 UTC [orderer/multichain] newLedgerResources -> CRIT 068[0m Error creating configtx manager and handlers: Error deserializing key Capabilities for group /Channel: Unexpected key Capabilities
[36morderer.example.com |[0m panic: Error creating configtx manager and handlers: Error deserializing key Capabilities for group /Channel: Unexpected key Capabilities
[36morderer.example.com |[0m
[36morderer.example.com |[0m goroutine 1 [running]:
[36morderer.example.com |[0m panic(0xb44a80, 0xc4203896a0)
[36morderer.example.com |[0m /opt/go/src/runtime/panic.go:500 +0x1a1
[36morderer.example.com |[0m github.com/hyperledger/fabric/vendor/github.com/op/go-logging.(*Logger).Panicf(0xc4201feba0, 0xc860ec, 0x30, 0xc4203895f0, 0x1, 0x1)
[36morderer.example.com |[0m /opt/gopath/src/github.com/hyperledger/fabric/vendor/github.com/op/go-logging/logger.go:194 +0x127
[36morderer.example.com |[0m github.com/hyperledger/fabric/orderer/multichain.(*multiLedger).newLedgerResources(0xc42034a640, 0xc42037b2c0, 0xc42037b2c0)
[36morderer.example.com |[0m /opt/gopath/src/github.com/hyperledger/fabric/orderer/multichain/manager.go:153 +0x393
[36morderer.example.com |[0m github.com/hyperledger/fabric/orderer/multichain.NewManagerImpl(0x1246880, 0xc420394140, 0xc42037ad80, 0x1243480, 0x128b4a8, 0x0, 0x0)
[36morderer.example.com |[0m /opt/gopath/src/github.com/hyperledger/fabric/orderer/multichain/manager.go:103 +0x23b
[36morderer.example.com |[0m main.initializeMultiChainManager(0xc420200d80, 0x1243480, 0x128b4a8, 0xc420204dd0, 0x1)
[36morderer.example.com |[0m /opt/gopath/src/github.com/hyperledger/fabric/orderer/main.go:220 +0x27a
[36morderer.example.com |[0m main.main()
[36morderer.example.com |[0m /opt/gopath/src/github.com/hyperledger/fabric/orderer/main.go:75 +0x392
```
@rameshthoomu @bretharrison any idea why e2e CI with node sdk keeps failing in release-1.0? https://gerrit.hyperledger.org/r/#/c/18883/
mastersingh24 (Fri, 09 Mar 2018 14:27:24 GMT):
@rjones @cbf https://jira.hyperledger.org/browse/FAB-8742
rjones (Fri, 09 Mar 2018 14:49:37 GMT):
@mastersingh24 why not just leave them there as artifacts of the past?
rjones (Fri, 09 Mar 2018 14:50:19 GMT):
I don't have strong feelings about it either way. Just wondering
dave.enyeart (Fri, 09 Mar 2018 14:51:17 GMT):
I would prefer to delete the `release` branches, as it is very confusing to see `release` and `release-1.0` and `release-1.1`.
mastersingh24 (Fri, 09 Mar 2018 14:52:39 GMT):
release was created directly from the tip of release-1.0 - so we have the entire history there
mastersingh24 (Fri, 09 Mar 2018 14:52:39 GMT):
release-1.0 was created directly from the tip of release - so we have the entire history there
mastersingh24 (Fri, 09 Mar 2018 14:53:11 GMT):
and agree with @dave.enyeart - basically need to reduce confusion
dave.enyeart (Fri, 09 Mar 2018 14:53:38 GMT):
@mastersingh24 I think you switched the release names in the above post
mastersingh24 (Fri, 09 Mar 2018 14:53:58 GMT):
no I didn;t ;)
mastersingh24 (Fri, 09 Mar 2018 14:53:58 GMT):
no I didn't ;)
mastersingh24 (Fri, 09 Mar 2018 14:54:09 GMT):
haha
rjones (Fri, 09 Mar 2018 15:01:26 GMT):
@mastersingh24 please adjudicate https://github.com/hyperledger/fabric-ca/pull/6
rjones (Fri, 09 Mar 2018 15:01:42 GMT):
I can't delete the `release` branch until you do
rjones (Fri, 09 Mar 2018 15:05:59 GMT):
_closes `6` on further inspection_
mastersingh24 (Fri, 09 Mar 2018 15:08:42 GMT):
done
rjones (Fri, 09 Mar 2018 15:09:10 GMT):
done done done
mastersingh24 (Fri, 09 Mar 2018 15:09:21 GMT):
awesome
rjones (Fri, 09 Mar 2018 15:09:58 GMT):
I miss that from Lab126. Anything you said you were done with, you would get challenged on if it was done, done done, or done done done. In this case... done done done
mastersingh24 (Fri, 09 Mar 2018 15:13:23 GMT):
I used to do that as well?
I'm done?
Are you done, done?
Yes?
Done, done, done?
I'm done with you
mastersingh24 (Fri, 09 Mar 2018 15:13:23 GMT):
I used to do that as well
I'm done
Are you done, done?
Yes
Done, done, done?
I'm done with you
rjones (Fri, 09 Mar 2018 15:26:05 GMT):
Heh
rjones (Fri, 09 Mar 2018 15:26:31 GMT):
Test code documentation
rjones (Fri, 09 Mar 2018 15:27:57 GMT):
The three dones
tongli (Fri, 09 Mar 2018 15:36:59 GMT):
@rjones, using the gerrit review command, I assume you really mean doing that in the gerrit server page, not at the job advanced page, is that correct?
rjones (Fri, 09 Mar 2018 15:37:58 GMT):
@tongli I'm not sure exactly that you mean
tongli (Fri, 09 Mar 2018 15:39:20 GMT):
trying to figure out what you suggested in terms using the customized labels. All I can figure out is using the gerrit server advanced page on jenkins to do that. at each job gerrit trigger, there is no where to add gerrit review command.
rjones (Fri, 09 Mar 2018 15:39:59 GMT):
@tongli if you go here: https://jenkins-new.hyperledger.org/job/fabric-docs-build-x86_64/configure
tongli (Fri, 09 Mar 2018 15:40:47 GMT):
yes. I am there.
rjones (Fri, 09 Mar 2018 15:40:58 GMT):
click `gerrit trigger` tab, then click advanced
tongli (Fri, 09 Mar 2018 15:41:00 GMT):
looking at the gerrit trigger advanced page.
rjones (Fri, 09 Mar 2018 15:41:16 GMT):
yes, that is where you would put it
tongli (Fri, 09 Mar 2018 15:41:32 GMT):
use URL to post field?
tongli (Fri, 09 Mar 2018 15:42:09 GMT):
each job has this field customized, is that what you are saying?
rjones (Fri, 09 Mar 2018 15:42:27 GMT):
no you put in tokenized gerrit commands. I gave you a link to that previously, on stack overflow
rjones (Fri, 09 Mar 2018 15:42:39 GMT):
you'll be customizing the verified stanza
rjones (Fri, 09 Mar 2018 15:42:54 GMT):
what you put in there will look like what I pasted before
tongli (Fri, 09 Mar 2018 15:43:06 GMT):
like this ```ssh -i /path/to/jenkins/.ssh/key -p 29418 user@gerrit-host gerrit review ${change},${patch} --label=customLabel=${result} --message=${message}```?
rjones (Fri, 09 Mar 2018 15:43:34 GMT):
no, it will look like everything after and including the gerrit command
rjones (Fri, 09 Mar 2018 15:44:31 GMT):
it will look like `gerrit review
tongli (Fri, 09 Mar 2018 15:45:03 GMT):
```gerrit review ${change},${patch} --label=customLabel=${result} --message=${message}``` this?
rjones (Fri, 09 Mar 2018 15:45:17 GMT):
https://stackoverflow.com/a/43848896
rjones (Fri, 09 Mar 2018 15:45:26 GMT):
says exactly how you need to format it
tongli (Fri, 09 Mar 2018 15:49:29 GMT):
I looked at few times before and I looked at that few times today, but I can not figure out what you really mean.
tongli (Fri, 09 Mar 2018 15:49:49 GMT):
what you pasted above does not look like a url.
rjones (Fri, 09 Mar 2018 15:49:54 GMT):
I don't know how to make it more plain
rjones (Fri, 09 Mar 2018 15:50:00 GMT):
It isn't a URL
tongli (Fri, 09 Mar 2018 15:50:39 GMT):
that article talks about how to customize the gerrit server using customized command.
rjones (Fri, 09 Mar 2018 15:50:57 GMT):
Read more closely
tongli (Fri, 09 Mar 2018 15:51:09 GMT):
which is different from the each job's advanced configuration section.
tongli (Fri, 09 Mar 2018 15:53:11 GMT):
@rjones, please tell me which field you are talking about on the advanced section of gerrit trigger and how the content should be formed.
rjones (Fri, 09 Mar 2018 15:54:39 GMT):
I just did? That answer does? It will need to be different depending on the result of the build, for each field
tongli (Fri, 09 Mar 2018 15:55:37 GMT):
no. it was not clear to me. that post is all about using it in the gerrit trigger configuration, not at a specific job configuration.
tongli (Fri, 09 Mar 2018 15:56:39 GMT):
it also shows why it was not possible doing it at the job level.
jtclark (Fri, 09 Mar 2018 16:10:37 GMT):
GM
jtclark (Fri, 09 Mar 2018 16:10:52 GMT):
@rameshthoomu looks like we've got data: https://jenkins.hyperledger.org/sandbox/job/fabric-test-daily-s390x/18/artifact/gopath/src/github.com/hyperledger/fabric-test/fabric-sdk-node/test/PTE/CITest/scripts/3833.log
jtclark (Fri, 09 Mar 2018 16:10:58 GMT):
I'll share this with @dongming
rjones (Fri, 09 Mar 2018 16:22:16 GMT):
you're right, I'm wrong
dave.enyeart (Fri, 09 Mar 2018 17:07:25 GMT):
@rameshthoomu for release-1.0 CI topic... `release-1.0` branches have been created for the SDKs. please use `release-1.0` branch for all 1.0.x related CI
rameshthoomu (Fri, 09 Mar 2018 17:07:58 GMT):
yes.. I am working on that..
rjones (Fri, 09 Mar 2018 17:42:37 GMT):
@tongli you were right, I was wrong, follow this example please: https://jenkins-new.hyperledger.org/job/votes/configure look at the bottom stanza
rjones (Fri, 09 Mar 2018 17:43:18 GMT):
@tongli you should have some logic to vote on the values you care about per job
tongli (Fri, 09 Mar 2018 17:44:53 GMT):
that makes sense to me. thanks for correct that.
tongli (Fri, 09 Mar 2018 17:45:01 GMT):
@ry. see above.
tongli (Fri, 09 Mar 2018 17:45:23 GMT):
@rjones see above.
rjones (Fri, 09 Mar 2018 17:47:28 GMT):
@tongli the next thing to do is to add the comments and the like, but I think you are unblocked for development, correct? I apologize for the delay
rjones (Fri, 09 Mar 2018 17:47:51 GMT):
@tongli I needed to add the jenkins user to the ACL for the new labels
tongli (Fri, 09 Mar 2018 17:48:00 GMT):
@rjones doing that means not using gerrit trigger to post the votes. it is using the script to do that.
tongli (Fri, 09 Mar 2018 17:48:55 GMT):
basically ssh remote api call against gerrit.
rjones (Fri, 09 Mar 2018 17:48:58 GMT):
I think you still get the vote on exit
rjones (Fri, 09 Mar 2018 17:49:22 GMT):
but you can over-ride that, no?
rjones (Fri, 09 Mar 2018 17:50:07 GMT):
@tongli please also see my earlier comments about parsing the commit message. I'll add an example
tongli (Fri, 09 Mar 2018 17:52:27 GMT):
not sure. gerrit trigger should vote the last. but it does not vote on the customized labels , so I guess it is ok.
rjones (Fri, 09 Mar 2018 17:55:01 GMT):
@tongli take a look at the last stanza of https://jenkins-new.hyperledger.org/job/votes/configure now, there is some logic you will need to write to parse commit messages
rjones (Fri, 09 Mar 2018 17:55:39 GMT):
@tongli I was more concerned with having, say, the docs job only vote on DOCS label, for instance, and not VERIFIED label
tongli (Fri, 09 Mar 2018 17:56:25 GMT):
if the doc job vote on some other labels, what does it mean though?
rjones (Fri, 09 Mar 2018 17:57:01 GMT):
I think it is up to you to decide.
rjones (Fri, 09 Mar 2018 17:57:41 GMT):
there must be a way to tell the gerrit trigger to not vote on a label. let me goof with it
tongli (Fri, 09 Mar 2018 17:59:26 GMT):
vote 0 should be that.
rjones (Fri, 09 Mar 2018 18:00:05 GMT):
@tongli look at configuration now. You can tell it to skip a vote.
rjones (Fri, 09 Mar 2018 18:05:09 GMT):
@tongli look at gerrit trigger advanced. I said it should not vote in any condition, since we are handling that
tongli (Fri, 09 Mar 2018 18:06:07 GMT):
i got it.
rjones (Fri, 09 Mar 2018 18:06:39 GMT):
@tongli OK. are you completely unblocked? I will leave this example voting job, and that change, around if you like
tongli (Fri, 09 Mar 2018 18:07:16 GMT):
yeah. got it, I think that we are good for now. Thanks.
rjones (Fri, 09 Mar 2018 18:07:30 GMT):
sure thing.
rjones (Fri, 09 Mar 2018 18:09:35 GMT):
@tongli when you get to the point that you want to add your final labels, and you have the names you want, please open a ticket helpdesk@hyperledger.org and tell me exactly what you want.
tongli (Fri, 09 Mar 2018 18:10:06 GMT):
great. like that. thanks and will do.
tongli (Fri, 09 Mar 2018 18:10:14 GMT):
:thumbsup:
rameshthoomu (Fri, 09 Mar 2018 21:08:25 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=pjPdz8CAgwNu83ruX) @dave.enyeart this has to apply to release-1.1 branch for all 1.1.x related CI
rameshthoomu (Fri, 09 Mar 2018 21:08:25 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=pjPdz8CAgwNu83ruX) @dave.enyeart this has to apply to `release-1.1` branch for all `1.1.x`related CI
dave.enyeart (Fri, 09 Mar 2018 21:38:06 GMT):
@rameshthoomu agreed, but `release-1.1` branch is not yet created for the SDKs
rameshthoomu (Fri, 09 Mar 2018 21:38:20 GMT):
yes.. We have to do that..
rameshthoomu (Fri, 09 Mar 2018 21:39:02 GMT):
I have pushed a change https://gerrit.hyperledger.org/r/#/c/18981/ to update the CI configuration
rameshthoomu (Fri, 09 Mar 2018 21:39:25 GMT):
```
set +e
BRANCH_NAME=$(echo $GERRIT_BRANCH | grep 'release*')
echo "-----> $BRANCH_NAME"
if [ ! -z "$BRANCH_NAME" ]; then
echo "-----> Checkout to $GERRIT_BRANCH branch"
git checkout $GERRIT_BRANCH
fi
set -e
echo "-----> $GERRIT_BRANCH"
```
dave.enyeart (Fri, 09 Mar 2018 21:39:30 GMT):
we plan to do that for the SDKs around release day. do we need to do that prior? for example to ensure all the tests and publishing works well from release-1.1?
rameshthoomu (Fri, 09 Mar 2018 21:40:16 GMT):
yes it's better to do before to make sure release-1.1 is good across the repos..
dave.enyeart (Fri, 09 Mar 2018 21:40:35 GMT):
makes sense
dave.enyeart (Fri, 09 Mar 2018 21:42:21 GMT):
@bretharrison are you ready to create release-1.1 branch from master for fabric-sdk-node?
dave.enyeart (Fri, 09 Mar 2018 21:42:50 GMT):
i believe you have permission to do that here https://gerrit.hyperledger.org/r/#/admin/projects/fabric-sdk-node,branches
bretharrison (Fri, 09 Mar 2018 21:43:20 GMT):
No, I would prefer to put in a few more changes
dave.enyeart (Fri, 09 Mar 2018 21:43:24 GMT):
it simply means any subsequent CRs will have to be cherry picked to both
dave.enyeart (Fri, 09 Mar 2018 21:43:41 GMT):
we need to close down fabric-sdk-node... how about on monday?
bretharrison (Fri, 09 Mar 2018 21:43:42 GMT):
right, could we wait till Monday
dave.enyeart (Fri, 09 Mar 2018 21:43:48 GMT):
deal
bretharrison (Fri, 09 Mar 2018 21:43:57 GMT):
great, thanks
rameshthoomu (Fri, 09 Mar 2018 21:46:24 GMT):
thanks @bretharrison
rameshthoomu (Fri, 09 Mar 2018 21:48:26 GMT):
@rjones regarding FAB-8747 ,you have pointed default branch in fabric-sdk-node to `release-1.0` but I still see `release` branch
rameshthoomu (Fri, 09 Mar 2018 21:48:26 GMT):
@rjones regarding FAB-8747, you have pointed default branch in fabric-sdk-node to `release-1.0` but I still see `release` branch
rickr (Fri, 09 Mar 2018 21:53:55 GMT):
`BRANCH_NAME=$(echo $GERRIT_BRANCH | grep 'release-*')`
rjones (Fri, 09 Mar 2018 21:56:14 GMT):
@rameshthoomu I cleaned them up
rameshthoomu (Fri, 09 Mar 2018 21:56:31 GMT):
thanks @rjones
rjones (Fri, 09 Mar 2018 21:56:34 GMT):
but I agree with the pattern @rickr suggests
rameshthoomu (Fri, 09 Mar 2018 21:56:57 GMT):
@rickr, pls post your comments if you have any in https://gerrit.hyperledger.org/r/#/c/18981/
rickr (Fri, 09 Mar 2018 22:09:44 GMT):
besides isn't your grep pattern wrong ? `e*` really mean optionally as meany `e`s on the end ?
rickr (Fri, 09 Mar 2018 22:09:44 GMT):
besides isn't your grep pattern wrong ? `e*` really mean optionally as many `e`s on the end ?
rickr (Fri, 09 Mar 2018 22:11:45 GMT):
BRANCH_NAME=$(echo $GERRIT_BRANCH | grep 'release-.*') like dot asterisk match option anything else on the end ?
rickr (Fri, 09 Mar 2018 22:12:53 GMT):
I think you can just go with `BRANCH_NAME=$(echo $GERRIT_BRANCH | grep 'release-')`
rameshthoomu (Fri, 09 Mar 2018 22:20:27 GMT):
ok
rjones (Fri, 09 Mar 2018 22:33:14 GMT):
probably `grep "^release-"` , @rickr ?
rjones (Fri, 09 Mar 2018 22:33:14 GMT):
probably `grep `^release-` , @rickr ?
rickr (Fri, 09 Mar 2018 23:49:10 GMT):
Maybe if you expect thing like "test-release-3.1.0 :)
rjones (Fri, 09 Mar 2018 23:50:13 GMT):
I trust people to create random branch names, not knowing the spooky consequences at a distance
rickr (Fri, 09 Mar 2018 23:54:04 GMT):
Clipboard - March 9, 2018 6:52 PM
rjones (Sat, 10 Mar 2018 00:03:22 GMT):
:working:
rjones (Sat, 10 Mar 2018 00:03:33 GMT):
I like it when the gif is larger
SethiSaab (Sat, 10 Mar 2018 19:46:47 GMT):
hi team i am getting error while doing channel configuration config update generation failure: could not parse application to application group: setting up the MSP manager failed: the supplied identity is not valid: x509: certificate signed by unknown authority (possibly because of "x509: ECDSA verification failure" while trying to verify candidate authority certificate "ca.org1.example.com")
jtclark (Mon, 12 Mar 2018 19:44:17 GMT):
@rameshthoomu made some progress
jtclark (Mon, 12 Mar 2018 19:44:27 GMT):
https://jenkins.hyperledger.org/sandbox/job/fabric-test-daily-s390x/2/
rameshthoomu (Mon, 12 Mar 2018 20:13:02 GMT):
That's great.. Do you know why the tests are failing?
rameshthoomu (Mon, 12 Mar 2018 20:13:29 GMT):
may be work with @dongming tomorrow when you are in lab..
Vthot4 (Tue, 13 Mar 2018 12:54:53 GMT):
Has joined the channel.
jtclark (Tue, 13 Mar 2018 13:24:05 GMT):
GM
jtclark (Tue, 13 Mar 2018 13:25:07 GMT):
@rameshthoomu we're working on each test now... basically when I update the channelTX attribute in the test scenarios, things start to work. @dongming and I have been working through each one.
rameshthoomu (Tue, 13 Mar 2018 13:35:49 GMT):
Ok thanks for the update.. It's okay to keep 1 or 2 tests in daily test run..
jtclark (Tue, 13 Mar 2018 13:55:56 GMT):
ok
Snixells (Wed, 14 Mar 2018 11:32:11 GMT):
Has joined the channel.
jtclark (Wed, 14 Mar 2018 13:25:54 GMT):
GM all
rameshthoomu (Fri, 16 Mar 2018 13:09:16 GMT):
@rickr seeing consistent java sdk e2e failures in fabric-ca e2e tests
rameshthoomu (Fri, 16 Mar 2018 13:10:30 GMT):
https://gerrit.hyperledger.org/r/c/19273/ failing on e2e test
rameshthoomu (Fri, 16 Mar 2018 14:28:35 GMT):
@rickr see this one
```00:27:02.246 testGetInfo(org.hyperledger.fabric_ca.sdkintegration.HFCAClientIT) Time elapsed: 0.341 sec <<< FAILURE!
00:27:02.246 java.lang.AssertionError
00:27:02.246 at org.hyperledger.fabric_ca.sdkintegration.HFCAClientIT.testGetInfo(HFCAClientIT.java:1095)
00:27:02.246
00:27:02.693
00:27:02.693 Results :
00:27:02.693
00:27:02.693 Failed tests:
00:27:02.693 HFCAClientIT.testGetInfo:1095
rameshthoomu (Fri, 16 Mar 2018 16:50:48 GMT):
https://wiki.hyperledger.org/projects/fabric/fabric_ci_documentation
rickr (Fri, 16 Mar 2018 17:12:10 GMT):
That test and function is called may times before the point of failure. None of the recent commits has touched that code area either
kostas (Fri, 16 Mar 2018 17:14:23 GMT):
How do I handle this CI case? https://gerrit.hyperledger.org/r/c/19081/
rickr (Fri, 16 Mar 2018 17:15:26 GMT):
@rameshthoomu It looks to me that the very last build passed. Seems like it's more of a system or networking issue that needs to be addressed
rameshthoomu (Fri, 16 Mar 2018 17:16:52 GMT):
@kostas try reverify-x
rameshthoomu (Fri, 16 Mar 2018 18:57:29 GMT):
@rickr please see Allen comment in the patch set https://gerrit.hyperledger.org/r/#/c/19273/
rickr (Fri, 16 Mar 2018 19:48:58 GMT):
@mastersingh24 --> https://gerrit.hyperledger.org/r/#/c/19315/
troyronda (Sat, 17 Mar 2018 15:59:36 GMT):
@rameshthoomu we are getting no space left on the device from the CI
troyronda (Sat, 17 Mar 2018 16:00:16 GMT):
(S390 go SDK builds)
rameshthoomu (Sat, 17 Mar 2018 16:03:11 GMT):
@harrijk could you pls look into this..
rameshthoomu (Sat, 17 Mar 2018 16:03:35 GMT):
I am on mobile. Can’t access machine to cleanup
harrijk (Sat, 17 Mar 2018 16:14:17 GMT):
Hi I will look at this now
harrijk (Sat, 17 Mar 2018 16:19:04 GMT):
@ramesh @troyronda I have cleared out the docker issue on node -16. That was the only one with space issues.
harrijk (Sat, 17 Mar 2018 16:19:04 GMT):
@rameshthoomu @troyronda I have cleared out the docker issue on node -16. That was the only one with space issues.
harrijk (Sat, 17 Mar 2018 16:20:16 GMT):
I suspect that one of the builds failed miserably and the usual cleaning out of docker containers and docker images at the start of each job didn't work due to the weird state that docker was in.
harrijk (Sat, 17 Mar 2018 16:21:25 GMT):
Please let me know if you run into any other out of space conditions.
harrijk (Sat, 17 Mar 2018 16:24:24 GMT):
I see a different issue on node -17. Looking at that now.
harrijk (Sat, 17 Mar 2018 16:31:50 GMT):
The space issue on node -17 has been resolved. A large number of directories and files were in /tmp.
harrijk (Sat, 17 Mar 2018 17:06:13 GMT):
I've also updated my cronjob to clean out /tmp during periods of inactivity.
mastersingh24 (Sat, 17 Mar 2018 17:10:01 GMT):
seem thing on Node SDK https://jenkins.hyperledger.org/job/fabric-sdk-node8-verify-s390x/349/console
mastersingh24 (Sat, 17 Mar 2018 17:10:01 GMT):
same thing on Node SDK https://jenkins.hyperledger.org/job/fabric-sdk-node8-verify-s390x/349/console
trying again ... ran it before your psot
mastersingh24 (Sat, 17 Mar 2018 17:10:01 GMT):
same thing on Node SDK https://jenkins.hyperledger.org/job/fabric-sdk-node8-verify-s390x/349/console
trying again ... ran it before the "fix"
harrijk (Sat, 17 Mar 2018 17:19:30 GMT):
I assume that job timestamp is GMT. If so it should be okay now
harrijk (Sat, 17 Mar 2018 17:19:33 GMT):
If you re run it
harrijk (Sat, 17 Mar 2018 17:19:33 GMT):
If you re-run it
kostas (Sun, 18 Mar 2018 15:48:56 GMT):
@rameshthoomu: Any idea why this call for `rebuild-x` from 2 days ago is still pending? https://gerrit.hyperledger.org/r/c/19083/
rameshthoomu (Sun, 18 Mar 2018 15:49:50 GMT):
Try reverify-x
rjones (Sun, 18 Mar 2018 16:52:39 GMT):
it's not like we're running out of verbs, we should add verbs when wanted.
davidkhala (Mon, 19 Mar 2018 08:47:34 GMT):
has the node8z CI been problem-free?
davidkhala (Mon, 19 Mar 2018 10:43:26 GMT):
gulp-debug: 19 items
manifest for hyperledger/fabric-orderer:latest not found
[03:59:26] 'docker-ready' errored after 1.21 s
[03:59:26] Error in plugin "gulp-shell"
Message:
Command `docker-compose -f test/fixtures/docker-compose.yaml up -d` failed with exit code 1
davidkhala (Mon, 19 Mar 2018 10:44:01 GMT):
saw this in reverify-node8z
rameshthoomu (Mon, 19 Mar 2018 11:31:00 GMT):
@davidkhala This could be the curl issue.. orderer image is not build due to curl failed to download required artifacts..
rameshthoomu (Mon, 19 Mar 2018 11:31:44 GMT):
reverify-node8z always trigger a node8 CI job on s390x platform
anrgbndhu (Mon, 19 Mar 2018 13:42:30 GMT):
Has joined the channel.
andrasfe (Tue, 20 Mar 2018 18:17:45 GMT):
Has joined the channel.
wjzheng (Tue, 20 Mar 2018 19:04:53 GMT):
Has joined the channel.
ShikarSharma (Tue, 20 Mar 2018 22:42:23 GMT):
Has joined the channel.
sykesm (Wed, 21 Mar 2018 11:31:25 GMT):
I'm continually hitting the following on x86 verify builds. Who's able to look into it?
```
10:52:13 ---> Running in 083cc6568365
10:52:14 curl: (18) transfer closed with 8192989 bytes remaining to read
10:52:14
10:52:14 gzip: stdin: unexpected end of file
10:52:14 tar: Unexpected EOF in archive
10:52:14 tar: Unexpected EOF in archive
10:52:14 tar: Error is not recoverable: exiting now
10:52:15 The command '/bin/sh -c mkdir -p /usr/share/maven /usr/share/maven/ref && curl -fsSL http://www-us.apache.org/dist/maven/maven-3/$MAVEN_VERSION/binaries/apache-maven-$MAVEN_VERSION-bin.tar.gz | tar -xzC /usr/share/maven --strip-components=1 && ln -s /usr/share/maven/bin/mvn /usr/bin/mvn' returned a non-zero code: 2
10:52:15 Makefile:304: recipe for target 'build/image/javaenv/.dummy-x86_64-1.1.0-snapshot-94ca92e' failed
10:52:15 make: *** [build/image/javaenv/.dummy-x86_64-1.1.0-snapshot-94ca92e] Error 2
10:52:15 Build step 'Execute shell' marked build as failure
```
Thanks.
sykesm (Wed, 21 Mar 2018 11:31:25 GMT):
I'm continually hitting the following on x86 verify builds. Who is the best person to look into it?
```
10:52:13 ---> Running in 083cc6568365
10:52:14 curl: (18) transfer closed with 8192989 bytes remaining to read
10:52:14
10:52:14 gzip: stdin: unexpected end of file
10:52:14 tar: Unexpected EOF in archive
10:52:14 tar: Unexpected EOF in archive
10:52:14 tar: Error is not recoverable: exiting now
10:52:15 The command '/bin/sh -c mkdir -p /usr/share/maven /usr/share/maven/ref && curl -fsSL http://www-us.apache.org/dist/maven/maven-3/$MAVEN_VERSION/binaries/apache-maven-$MAVEN_VERSION-bin.tar.gz | tar -xzC /usr/share/maven --strip-components=1 && ln -s /usr/share/maven/bin/mvn /usr/bin/mvn' returned a non-zero code: 2
10:52:15 Makefile:304: recipe for target 'build/image/javaenv/.dummy-x86_64-1.1.0-snapshot-94ca92e' failed
10:52:15 make: *** [build/image/javaenv/.dummy-x86_64-1.1.0-snapshot-94ca92e] Error 2
10:52:15 Build step 'Execute shell' marked build as failure
```
Thanks.
sykesm (Wed, 21 Mar 2018 11:31:49 GMT):
https://jenkins.hyperledger.org/job/fabric-verify-x86_64/21660/console
rameshthoomu (Wed, 21 Mar 2018 11:43:57 GMT):
@rjones the above error is popping up in most of the builds.. Sometimes if re-trigger build may fix the issue temporarily
rameshthoomu (Wed, 21 Mar 2018 11:44:37 GMT):
@sykesm could you please re-trigger the build through gerrit comment `reverify-x`
sykesm (Wed, 21 Mar 2018 11:44:55 GMT):
I've been doing that for two days across 13 CRs. It's no longer scalable.
sykesm (Wed, 21 Mar 2018 11:45:55 GMT):
If your around this morning, would also love to get your input on a makefile change that I'm having issues with. Completely unrelated and only if you have some time...
sykesm (Wed, 21 Mar 2018 11:45:55 GMT):
If you're around this morning, would also love to get your input on a makefile change that I'm having issues with. Completely unrelated and only if you have some time...
rameshthoomu (Wed, 21 Mar 2018 11:46:22 GMT):
sure.. will be in office around 8:45 AM
sykesm (Wed, 21 Mar 2018 11:46:27 GMT):
cool. thanks.
rameshthoomu (Wed, 21 Mar 2018 11:58:24 GMT):
FAB-8978
rjones (Wed, 21 Mar 2018 12:03:53 GMT):
@rameshthoomu it already exists. https://nexus.hyperledger.org/content/repositories/hosted_installers/apache-maven/apache-maven/3.3.9/ it's existed since we set up nexus
rameshthoomu (Wed, 21 Mar 2018 12:04:41 GMT):
nice.. I will keep this reference in javaenv docker image reference..
rameshthoomu (Wed, 21 Mar 2018 12:04:41 GMT):
nice.. I will keep this reference in javaenv docker image
FORFIRM (Wed, 21 Mar 2018 14:26:45 GMT):
Has joined the channel.
crissi (Wed, 21 Mar 2018 16:46:36 GMT):
Has joined the channel.
risentveber (Thu, 22 Mar 2018 09:56:13 GMT):
Has joined the channel.
rameshthoomu (Thu, 22 Mar 2018 12:01:47 GMT):
@dave.enyeart when you get time, pls see this FAB-9043
rjones (Fri, 23 Mar 2018 17:57:43 GMT):
is master broken?
rjones (Fri, 23 Mar 2018 17:57:46 GMT):
```17:33:41 unit-tests_1 | real 4m14.880s
17:33:41 unit-tests_1 | user 5m54.444s
17:33:41 unit-tests_1 | sys 0m39.168s
17:33:46 unit-tests_1 | ok github.com/hyperledger/fabric/gossip/api 0.004s coverage: 100.0% of statements
17:33:54 unit-tests_1 | --- FAIL: TestReConnections (0.00s)
17:33:54 unit-tests_1 | panic: listen tcp :43612: bind: address already in use [recovered]
17:33:54 unit-tests_1 | panic: listen tcp :43612: bind: address already in use
17:33:54 unit-tests_1 |
17:33:54 unit-tests_1 | goroutine 31 [running]:
17:33:54 unit-tests_1 | testing.tRunner.func1(0xc4201aea50)
17:33:54 unit-tests_1 | /opt/go/src/testing/testing.go:711 +0x2d2
17:33:54 unit-tests_1 | panic(0xd534e0, 0xc420310ff0)
17:33:54 unit-tests_1 | /opt/go/src/runtime/panic.go:491 +0x283
17:33:54 unit-tests_1 | github.com/hyperledger/fabric/gossip/comm.createGRPCLayer(0xaa5c, 0x0, 0xc420375140, 0x34630c7e02c, 0xf, 0x10)
17:33:54 unit-tests_1 | github.com/hyperledger/fabric/gossip/comm/_test/_obj_test/comm_impl.go:833 +0x78f
17:33:54 unit-tests_1 | github.com/hyperledger/fabric/gossip/comm.NewCommInstanceWithServer(0xaa5c, 0x136d640, 0xc4203a0d20, 0xc42042a600, 0xf, 0x10, 0x0, 0x0, 0x0, 0x0, ...)
17:33:54 unit-tests_1 | github.com/hyperledger/fabric/gossip/comm/_test/_obj_test/comm_impl.go:61 +0xb46
17:33:54 unit-tests_1 | github.com/hyperledger/fabric/gossip/comm.newCommInstance(0xaa5c, 0x13c54e0, 0x136db20, 0xc42038c100, 0x0, 0x0)
17:33:54 unit-tests_1 | /opt/gopath/src/github.com/hyperledger/fabric/gossip/comm/comm_test.go:112 +0x1bb
17:33:54 unit-tests_1 | github.com/hyperledger/fabric/gossip/comm.TestReConnections(0xc4201aea50)
17:33:54 unit-tests_1 | /opt/gopath/src/github.com/hyperledger/fabric/gossip/comm/comm_test.go:650 +0x86
17:33:54 unit-tests_1 | testing.tRunner(0xc4201aea50, 0xe26298)
17:33:54 unit-tests_1 | /opt/go/src/testing/testing.go:746 +0xd0
17:33:54 unit-tests_1 | created by testing.(*T).Run
17:33:54 unit-tests_1 | /opt/go/src/testing/testing.go:789 +0x2de
17:33:54 unit-tests_1 | FAIL github.com/hyperledger/fabric/gossip/comm 2.038s
```
rjones (Fri, 23 Mar 2018 17:58:09 GMT):
https://logs.hyperledger.org/production/vex-yul-hyp-jenkins-3/fabric-verify-x86_64/21786/
rjones (Fri, 23 Mar 2018 17:58:20 GMT):
https://jenkins.hyperledger.org/job/fabric-verify-x86_64/21786/
kostas (Fri, 23 Mar 2018 20:26:32 GMT):
Any objections to my manually overriding CI's -1 here? https://gerrit.hyperledger.org/r/c/19083/ This has been verified locally, a simple inspection of the code shows there's no reason why it would trigger a CI failure, and most importantly -- I've been reverifying for several days now w/o success. (Life's too short for that!)
salmanbaset (Mon, 26 Mar 2018 16:35:43 GMT):
cross posting from fabric-samples:
how can I run jenkins jobs for fabric-samples locally? I put a fix for fabric-samples/first-network, but jenkins is giving errors...
https://gerrit.hyperledger.org/r/#/c/19757/
rameshthoomu (Mon, 26 Mar 2018 16:46:36 GMT):
@salmanbaset I see the last build was passed
rameshthoomu (Mon, 26 Mar 2018 16:51:59 GMT):
you can run byfn.sh , eyfn.sh scripts passing default, custom, couchdb and node chaincode parameters
salmanbaset (Mon, 26 Mar 2018 19:00:50 GMT):
@rameshthoomu thanks. this is what I was doing before. Yes, the current does seem to have passed.
sheehan (Mon, 26 Mar 2018 20:51:03 GMT):
Has joined the channel.
sheehan (Mon, 26 Mar 2018 20:53:18 GMT):
Hi @rameshthoomu - I hit https://jira.hyperledger.org/browse/FAB-9171. Simple fix is at https://gerrit.hyperledger.org/r/c/19783/, but I'm curious how this made it past CI, but I am encountering it in my local build?
rameshthoomu (Mon, 26 Mar 2018 21:11:41 GMT):
@sheehan I see the jobs are failed to build javaenv image. Seems it's a timeout error
```00:03:53.587 > Could not download org.eclipse.sisu.plexus.jar (org.eclipse.sisu:org.eclipse.sisu.plexus:0.0.0.M5)
00:03:53.588 > Could not get resource 'https://plugins.gradle.org/m2/org/eclipse/sisu/org.eclipse.sisu.plexus/0.0.0.M5/org.eclipse.sisu.plexus-0.0.0.M5.jar'.
00:03:53.589 > Read timed out
rameshthoomu (Mon, 26 Mar 2018 21:12:49 GMT):
seems @rjones re-triggered the patchset.. Should work now..
rjones (Mon, 26 Mar 2018 21:27:28 GMT):
Yes I fired it again
greg.haskins (Tue, 27 Mar 2018 21:59:52 GMT):
@rameshthoomu https://jira.hyperledger.org/browse/FAB-9201
sheehan (Wed, 28 Mar 2018 13:58:23 GMT):
@rameshthoomu are there known issues with fabric CI? I haven't seen anything pass in a while
rameshthoomu (Wed, 28 Mar 2018 14:00:26 GMT):
I see these two are failing inconsistently
FAB-9093 FAB-9100
sheehan (Wed, 28 Mar 2018 14:08:40 GMT):
here's another example of one that kept failing
https://gerrit.hyperledger.org/r/c/19783/
sheehan (Wed, 28 Mar 2018 14:09:58 GMT):
I'd run `make all` locally and everything would pass. But always fails in the build env
rameshthoomu (Wed, 28 Mar 2018 14:17:14 GMT):
yes it's very inconsistent..
rameshthoomu (Wed, 28 Mar 2018 14:17:50 GMT):
this error is keep poping up from past couple of days and I see the same in your end-2-end job
```
00:04:20.620 > Could not resolve all files for configuration ':core:chaincode:shim:java:classpath'.
00:04:20.626 > Could not resolve javax.enterprise:cdi-api:1.0.
rameshthoomu (Wed, 28 Mar 2018 14:17:50 GMT):
this error is keep poping up from past couple of days and I see the same in your end-2-end & unit-test job
```
00:04:20.620 > Could not resolve all files for configuration ':core:chaincode:shim:java:classpath'.
00:04:20.626 > Could not resolve javax.enterprise:cdi-api:1.0.
rameshthoomu (Wed, 28 Mar 2018 14:34:02 GMT):
above issue is inconsistent.. This could be network issue.. See the timeout in success and failed case
```(failed)
00:02:07.306 Step 14/15 : RUN core/chaincode/shim/java/javabuild.sh
00:02:07.378 ---> Running in a580be2d73af
00:04:20.605
00:04:20.609 FAILURE: Build failed with an exception. *(more than 2 mins)*
``` (success)
00:02:48.235 Step 14/15 : RUN core/chaincode/shim/java/javabuild.sh
00:02:48.346 ---> Running in e148a6613fe9
00:03:22.309 Removing intermediate container e148a6613fe9 *(34 secs)*
rameshthoomu (Wed, 28 Mar 2018 14:34:02 GMT):
above issue is inconsistent.. This could be network issue.. See the timeout in success and failed case
``` (failed)
00:02:07.306 Step 14/15 : RUN core/chaincode/shim/java/javabuild.sh
00:02:07.378 ---> Running in a580be2d73af
00:04:20.605
00:04:20.609 FAILURE: Build failed with an exception. *(more than 2 mins)*
``` (success)
00:02:48.235 Step 14/15 : RUN core/chaincode/shim/java/javabuild.sh
00:02:48.346 ---> Running in e148a6613fe9
00:03:22.309 Removing intermediate container e148a6613fe9 *(34 secs)*
troyronda (Thu, 29 Mar 2018 13:53:15 GMT):
@rameshthoomu as we look at adding 1.2 functions to the SDK, I'm wondering if we could target 1.2 snapshot docker builds for our integration tests?
troyronda (Thu, 29 Mar 2018 13:53:15 GMT):
@rameshthoomu as we look at adding 1.2 functions to the Go SDK, I'm wondering if we could target 1.2 snapshot docker builds for our integration tests?
troyronda (Thu, 29 Mar 2018 13:53:15 GMT):
@rameshthoomu as we look at adding 1.2 functions to the Go SDK, I'm wondering if we could target 1.2/master snapshot docker builds for our integration tests?
rameshthoomu (Thu, 29 Mar 2018 13:55:52 GMT):
are you pulling docker images now or building them?
troyronda (Thu, 29 Mar 2018 13:55:57 GMT):
pulling now
troyronda (Thu, 29 Mar 2018 13:56:12 GMT):
we pull 1.0.6 and 1.1.0 currently
troyronda (Thu, 29 Mar 2018 13:56:19 GMT):
would be nice to add a master/snapshot
rameshthoomu (Thu, 29 Mar 2018 13:59:45 GMT):
We publish fabric & fabric-ca images to nexus3 daily depends on the e2e test results
rameshthoomu (Thu, 29 Mar 2018 13:59:46 GMT):
https://nexus3.hyperledger.org/#browse/browse/components:docker.snapshot
rameshthoomu (Thu, 29 Mar 2018 14:00:01 GMT):
you can search with `latest` tag here in nexus.
rameshthoomu (Thu, 29 Mar 2018 14:01:01 GMT):
if you are ok, I can pull these images in CI
troyronda (Thu, 29 Mar 2018 14:04:01 GMT):
If I understand correctly, the latest tag is only updated with successful e2e tests?
rameshthoomu (Thu, 29 Mar 2018 14:05:42 GMT):
yes
troyronda (Thu, 29 Mar 2018 14:06:48 GMT):
ok i just kicked off a test locally with that tag; one sec.
troyronda (Thu, 29 Mar 2018 14:10:48 GMT):
btw - I previously had a setup using devstable tag - I assume that's no longer used?
troyronda (Thu, 29 Mar 2018 14:10:48 GMT):
btw - I previously had the same script setup using devstable tag - I assume that's no longer used?
rameshthoomu (Thu, 29 Mar 2018 14:17:56 GMT):
yes.. that's right
troyronda (Thu, 29 Mar 2018 14:27:48 GMT):
thanks @rameshthoomu . works locally - i pushed a patch into the Go SDK to use latest tag instead of devstable (https://gerrit.hyperledger.org/r/c/19915/).
troyronda (Thu, 29 Mar 2018 14:27:48 GMT):
thanks @rameshthoomu. works locally. i just pushed a patch into the Go SDK to use latest tag instead of devstable (https://gerrit.hyperledger.org/r/c/19915/).
troyronda (Thu, 29 Mar 2018 14:27:48 GMT):
thanks @rameshthoomu. works locally. i just now pushed a patch into the Go SDK to use latest tag instead of devstable (https://gerrit.hyperledger.org/r/c/19915/).
troyronda (Thu, 29 Mar 2018 14:28:39 GMT):
(and also enabled that target to run in the CI)
troyronda (Thu, 29 Mar 2018 15:14:28 GMT):
yup - works for x86 (guess s390 doesn't have this tag, just as devstable didn't).
troyronda (Thu, 29 Mar 2018 15:19:01 GMT):
merged the enablement of latest tag for x86.
troyronda (Thu, 29 Mar 2018 15:19:01 GMT):
merged the enablement of latest tag for x86 in Go SDK.
troyronda (Thu, 29 Mar 2018 15:19:01 GMT):
@rameshthoomu merged the enablement of latest tag for x86 in Go SDK - it would be good to pull these images in CI
rameshthoomu (Thu, 29 Mar 2018 15:27:53 GMT):
ok got you.. then latest may not work in that case.. as docker supports only one latest tag per image
troyronda (Thu, 29 Mar 2018 15:36:46 GMT):
yup - i have it setup to do x86 only for latest.
rameshthoomu (Thu, 29 Mar 2018 16:19:54 GMT):
@mastersingh24 updated comment in https://jira.hyperledger.org/browse/FAB-9079
rameshthoomu (Fri, 30 Mar 2018 11:20:49 GMT):
@sambhavdutt @jtclark please review this change https://gerrit.hyperledger.org/r/#/q/topic:FAB-8710+(status:open+OR+status:merged)
sambhavdutt (Fri, 30 Mar 2018 11:25:28 GMT):
Good Morning,
will check
jyellick (Fri, 30 Mar 2018 16:23:37 GMT):
@rameshthoomu I am seeing "This project is currently disabled" https://jenkins.hyperledger.org/job/fabric-verify-x86_64/
jyellick (Fri, 30 Mar 2018 16:25:12 GMT):
(and am not seeing reverifies for it work etc.)
jyellick (Fri, 30 Mar 2018 17:08:14 GMT):
@rjones Since you're active and @rameshthoomu seems not to be, any idea what's going on with the above?
rjones (Fri, 30 Mar 2018 17:08:40 GMT):
I think it's been replaced? I really can't answer that question
rjones (Fri, 30 Mar 2018 17:09:12 GMT):
I think that job has been atomized into four other jobs.
rameshthoomu (Fri, 30 Mar 2018 17:09:19 GMT):
@jyellick working on couple of fixes.. sorry
rameshthoomu (Fri, 30 Mar 2018 17:09:43 GMT):
@jyellick https://github.com/rameshthoomu/ci-management/blob/master/docs/fabric.md
jyellick (Fri, 30 Mar 2018 17:12:30 GMT):
Ah thanks, would explain why my reverifies are being ignored
pandrejko (Fri, 30 Mar 2018 19:52:50 GMT):
Has joined the channel.
jyellick (Fri, 30 Mar 2018 20:26:41 GMT):
@rameshthoomu Could you look at https://jenkins.hyperledger.org/job/fabric-verify-build-checks-x86_64/14/console ?
rameshthoomu (Fri, 30 Mar 2018 20:27:06 GMT):
checking
jyellick (Fri, 30 Mar 2018 20:27:09 GMT):
It claims there is a trailing whitespace, but, when I look at the CR: https://gerrit.hyperledger.org/r/c/19969/2/sampleconfig/configtx.yaml#149 I see no trailing whitespace
jyellick (Fri, 30 Mar 2018 20:27:27 GMT):
(Is there a way to run these checks locally to maybe get a specific line etc. that it is upset about?)
jyellick (Fri, 30 Mar 2018 20:28:25 GMT):
I do see a couple bits of whitespace that are trailing in a section of that file which I did not modify, but it seems like all builds should be failing then?
rameshthoomu (Fri, 30 Mar 2018 20:30:14 GMT):
```# Verify if there are trailing spaces in the files.
COMMIT_FILES=`git diff-tree --name-only -r HEAD~1..HEAD`
for filename in `echo $COMMIT_FILES`; do
if [[ `file $filename` == *"ASCII text"* ]];
then
if [ ! -z "`egrep -l " +$" $filename`" ];
then
FOUND_TRAILING='yes'
echo "Error: Trailing white spaces found in file:$filename"
fi
fi
done
if [ ! -z ${FOUND_TRAILING+x} ];
then
exit 1
fi
jyellick (Fri, 30 Mar 2018 20:30:51 GMT):
Ah, so because I touched this file, I inherit any bugs in that file against my CI build?
rjones (Fri, 30 Mar 2018 20:37:24 GMT):
Seems like the checks should apply to the diff
rjones (Fri, 30 Mar 2018 20:40:18 GMT):
https://status.linuxfoundation.org/incidents/tqkfpb0c3ywb
jyellick (Fri, 30 Mar 2018 20:58:11 GMT):
As a general point, I don't think we should have anything in CI that cannot be executed as part of a local build. Perhaps there is some broader plan here I am missing, but it seems like CI should essentially consist of a single line calling into the project to execute the tests. The notion that to discover why CI is failing, I need to pull a separate repo and attempt to find the failing test seems problematic to me.
jyellick (Fri, 30 Mar 2018 20:58:11 GMT):
As a general point, I don't think we should have anything in CI that cannot be executed as part of a local build. Perhaps there is some broader plan here I am missing, but it seems like CI repo should essentially consist of a single line [perhaps hyperbolic as there could be env setup etc.] calling into the project to execute the tests. The notion that to discover why CI is failing, I need to pull a separate repo and attempt to find the failing test seems problematic to me.
jyellick (Fri, 30 Mar 2018 21:01:44 GMT):
(I know for instance, I've mentioned this with respect to the 'fabric-samples' repository. That there's no way to test a change locally to see if it will pass CI without going and finding the corresponding script in another repo and executing it)
rameshthoomu (Fri, 30 Mar 2018 21:03:09 GMT):
Agree @jyellick.. Will call these extra checks from fabric make file and will create single point script to call from CI
mastersingh24 (Fri, 30 Mar 2018 22:32:58 GMT):
will the unit test job work anytime soon?
mastersingh24 (Fri, 30 Mar 2018 22:35:55 GMT):
CI is just killing me. I'm sure people who are doing more than me are even more frustrated
rameshthoomu (Fri, 30 Mar 2018 22:48:43 GMT):
@mastersingh24 are these inconsistent failures? I have 5 FAB's created on these failures..
rameshthoomu (Fri, 30 Mar 2018 22:49:24 GMT):
not sure what's going wrong.. someone has to verify the those failures..
mastersingh24 (Sat, 31 Mar 2018 10:16:32 GMT):
the main thing that was failing was pulling down images .... I'm aware of the test flakes and am trying to fix a few of those, for example
https://gerrit.hyperledger.org/r/19977
https://gerrit.hyperledger.org/r/20015
mastersingh24 (Sat, 31 Mar 2018 10:16:32 GMT):
the main thing that was failing was pulling down images .... I'm aware of the test flakes and am trying to fix a few of those, for example
https://gerrit.hyperledger.org/r/19977
https://gerrit.hyperledger.org/r/20015
rameshthoomu (Sun, 01 Apr 2018 02:00:54 GMT):
Thanks @mastersingh24 for the fixes..
rameshthoomu (Sun, 01 Apr 2018 02:02:48 GMT):
all, please go through this doc to understand the optimized fabric CI build process.. Will push this doc to ci-management repo soon or will post in wiki after fine tune. https://github.com/rameshthoomu/ci-management/blob/master/docs/fabric_ci_build_process.md
rameshthoomu (Sun, 01 Apr 2018 02:03:28 GMT):
If any question please post your questions in this channel or #ci-pipeline
thalisson (Sun, 01 Apr 2018 02:44:18 GMT):
Has joined the channel.
yacovm (Sun, 01 Apr 2018 14:11:35 GMT):
@rameshthoomu @rjones is it possible for CI not to send an email when it is starting a job?
yacovm (Sun, 01 Apr 2018 14:11:56 GMT):
Clipboard - April 1, 2018 5:12 PM
yacovm (Sun, 01 Apr 2018 14:12:17 GMT):
what am I supposed to do with this information :rolling_eyes:
rameshthoomu (Sun, 01 Apr 2018 14:14:35 GMT):
@yacovm I am on drive now.. can’t help you now.. will check build settings once I get access to machine
yacovm (Sun, 01 Apr 2018 14:14:43 GMT):
sure no pressure
rjones (Sun, 01 Apr 2018 15:52:37 GMT):
@yacovm do you want all emails turned off?
yacovm (Sun, 01 Apr 2018 15:52:46 GMT):
not all emails....
rjones (Sun, 01 Apr 2018 15:52:55 GMT):
it used to be jenkins sent no emails.
rjones (Sun, 01 Apr 2018 15:53:07 GMT):
so that would be a return to the previous way it was
yacovm (Sun, 01 Apr 2018 15:53:13 GMT):
jenkins sent me emails when i was a watcher for a change set
yacovm (Sun, 01 Apr 2018 15:53:21 GMT):
i.e someone commented something
yacovm (Sun, 01 Apr 2018 15:53:50 GMT):
can we remove emails from the job builder only?
rjones (Sun, 01 Apr 2018 15:54:14 GMT):
OK. I need to be more clear. The emails come from gerrit. the previous way this worked was no jenkins comment triggered an email from gerrit.
rjones (Sun, 01 Apr 2018 15:54:37 GMT):
I'm proposing a return to that - no jenkins emails about job status.
yacovm (Sun, 01 Apr 2018 15:54:58 GMT):
seems right to me
rjones (Sun, 01 Apr 2018 15:55:23 GMT):
OK. give me a bit
yacovm (Sun, 01 Apr 2018 15:55:44 GMT):
you can have even 8 bits
rjones (Sun, 01 Apr 2018 15:59:20 GMT):
https://gerrit.hyperledger.org/r/20053
rjones (Sun, 01 Apr 2018 20:51:50 GMT):
@yacovm did you get an email from the start of this build https://jenkins.hyperledger.org/job/fabric-verify-unit-tests-x86_64/673/ ?
rjones (Sun, 01 Apr 2018 20:52:13 GMT):
It's the first build to use the `--notify=NON` thing
rjones (Sun, 01 Apr 2018 20:53:58 GMT):
ignore that.
rjones (Sun, 01 Apr 2018 20:59:06 GMT):
@yacovm I'll rerun your build in a bit, OK?
rjones (Sun, 01 Apr 2018 21:05:39 GMT):
@yacovm retriggered, sorry for the turbulence
yacovm (Sun, 01 Apr 2018 22:44:47 GMT):
I don't know...
yacovm (Sun, 01 Apr 2018 22:46:01 GMT):
so - my last email from it was 2:29 EST
yacovm (Sun, 01 Apr 2018 22:46:43 GMT):
it won't pass the build because I have some problem in the UT that doesn't manifest in my local environment, something with files I guess. I'll fix it today/tomorrow and will see if it keeps spamming me. thanks @rjones
jtclark (Mon, 02 Apr 2018 14:21:43 GMT):
GM :-)
yacovm (Mon, 02 Apr 2018 16:38:05 GMT):
so I think it worked Ry, thanks
yacovm (Mon, 02 Apr 2018 20:46:02 GMT):
Any idea why the green +1s don't show up on https://gerrit.hyperledger.org/r/#/c/14771/ ?
yacovm (Mon, 02 Apr 2018 20:46:18 GMT):
all tests passed...
rameshd (Mon, 02 Apr 2018 20:53:53 GMT):
Has joined the channel.
yacovm (Mon, 02 Apr 2018 21:02:47 GMT):
does it not show up if you're a reviewer of the change set?
yacovm (Mon, 02 Apr 2018 21:02:47 GMT):
does it not show up if you're a reviewer of the change set? (Ry)
rjones (Mon, 02 Apr 2018 21:15:58 GMT):
Wrong patch probably
Ammu (Tue, 03 Apr 2018 07:55:45 GMT):
byfn generate.png
Ammu (Tue, 03 Apr 2018 07:55:54 GMT):
solve this error please
jtclark (Tue, 03 Apr 2018 13:28:01 GMT):
Hi @Ammu - are you still having trouble with BYFN script?
Ammu (Tue, 03 Apr 2018 13:28:25 GMT):
yup
Ammu (Tue, 03 Apr 2018 13:28:30 GMT):
@jtclark
jtclark (Tue, 03 Apr 2018 13:30:00 GMT):
and you're following the instructions here: http://hyperledger-fabric.readthedocs.io/en/latest/build_network.html ?
jtclark (Tue, 03 Apr 2018 13:30:16 GMT):
@Ammu :point_up_tone2:
Ammu (Tue, 03 Apr 2018 13:34:51 GMT):
up.png
Ammu (Tue, 03 Apr 2018 13:34:56 GMT):
up2.png
Ammu (Tue, 03 Apr 2018 13:35:35 GMT):
i am just struck here actually
jtclark (Tue, 03 Apr 2018 16:32:30 GMT):
@Ammu my suggestion would be to ask this question in the #fabric-questions channel.
cammachusa (Tue, 03 Apr 2018 18:49:33 GMT):
Has joined the channel.
cammachusa (Tue, 03 Apr 2018 18:49:57 GMT):
Hello everyone! In first-network example from https://github.com/hyperledger/fabric-samples, I couldn't find the network-config.yaml, but I can find it from "balance-transfer" network. So, I am wondering where/how I can find/generate the network-config.yaml file?
jtclark (Tue, 03 Apr 2018 20:15:49 GMT):
@cammachusa the best place to ask this question would be in the #fabric-questions channel
cammachusa (Tue, 03 Apr 2018 20:23:42 GMT):
Thank you, @jtclark
jtclark (Tue, 03 Apr 2018 20:23:55 GMT):
@cammachusa np.
Ammu (Wed, 04 Apr 2018 04:37:53 GMT):
ok i will ask @jtclark
Ammu (Wed, 04 Apr 2018 12:52:40 GMT):
peers.png
jtclark (Wed, 04 Apr 2018 13:07:25 GMT):
GM @Ammu
jtclark (Wed, 04 Apr 2018 13:07:36 GMT):
this particular error I'm not as familiar with
jtclark (Wed, 04 Apr 2018 13:08:13 GMT):
also, this channel is reserved for Hyperledger contributors who have issues/requests with our CI infrastructure.
jtclark (Wed, 04 Apr 2018 13:08:38 GMT):
I would ask you to please ask this question in the #fabric-questions channel, where issues like this are addressed.
Ammu (Wed, 04 Apr 2018 13:12:00 GMT):
ok
jtclark (Wed, 04 Apr 2018 14:30:49 GMT):
thanks @Ammu
wlahti (Wed, 04 Apr 2018 16:24:34 GMT):
Is there any reason to check for trailing white spaces in vendored files, especially a license file? https://gerrit.hyperledger.org/r/c/19767/
wlahti (Wed, 04 Apr 2018 16:24:34 GMT):
Is there any reason for CI to check for trailing white spaces in vendored files, especially a license file? https://gerrit.hyperledger.org/r/c/19767/
rameshthoomu (Wed, 04 Apr 2018 16:27:11 GMT):
@wlahti right now the script will check for all the files in the patchset..
rameshthoomu (Wed, 04 Apr 2018 16:28:03 GMT):
will update script to ignore vendor files.. but for now, please fix the trailing space in the license file..
rameshthoomu (Wed, 04 Apr 2018 16:28:35 GMT):
if possible, could you please create a FAB item in fabric-ci component..
rjones (Wed, 04 Apr 2018 17:00:25 GMT):
@rameshthoomu you should just check white space in there delta
rameshthoomu (Wed, 04 Apr 2018 17:01:18 GMT):
yes that;s what the script is doing now.. but the request is to ignore the vendor files
rameshthoomu (Wed, 04 Apr 2018 17:01:37 GMT):
https://gerrit.hyperledger.org/r/#/c/19767/2/vendor/github.com/tedsuo/ifrit/LICENSE
rjones (Wed, 04 Apr 2018 17:02:42 GMT):
Are we editing vendor files?
rameshthoomu (Wed, 04 Apr 2018 17:02:42 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=mu99oPDwaRpmb84GpQ) @rjones I have addressed your comment
rjones (Wed, 04 Apr 2018 17:03:21 GMT):
I had to fix master a few months ago because of a line ending issue in a vendor file
rjones (Wed, 04 Apr 2018 17:04:10 GMT):
If there is a white space issue in a vendor file it will still break the build
rameshthoomu (Wed, 04 Apr 2018 17:05:45 GMT):
yes.. that's true.. It's better to add this check as a target in fabric make file
rameshthoomu (Wed, 04 Apr 2018 17:06:15 GMT):
and developer have to check `make basic-checks` & `make unit-tests` before they push a change set to gerrit..
rjones (Wed, 04 Apr 2018 17:06:29 GMT):
Agreed
rameshthoomu (Wed, 04 Apr 2018 17:07:08 GMT):
right now, I see issues with license check.. that;s the reason i have disabled `make basic-checks` target from CI and enabled only `make linter` and `make unit-tests`
scottz (Thu, 05 Apr 2018 17:32:24 GMT):
I cannot build peer using vagrant, with latest fabric and fabric-test. I noticed the GO version in vagrant env is still 1.9. Is there a jira task open, to change it to 1.10? Could that be the reason for this failure?```ubuntu@hyperledger-devenv:4311236:/opt/gopath/src/github.com/hyperledger/fabric$ make peer
.build/bin/peer
CGO_CFLAGS=" " GOBIN=/opt/gopath/src/github.com/hyperledger/fabric/.build/bin go install -tags "experimental" -ldflags "-X github.com/hyperledger/fabric/common/metadata.Version=1.2.0-snapshot-c149c1e -X github.com/hyperledger/fabric/common/metadata.BaseVersion=0.4.7 -X github.com/hyperledger/fabric/common/metadata.BaseDockerLabel=org.hyperledger.fabric -X github.com/hyperledger/fabric/common/metadata.DockerNamespace=hyperledger -X github.com/hyperledger/fabric/common/metadata.BaseDockerNamespace=hyperledger -X github.com/hyperledger/fabric/common/metadata.Experimental=true" github.com/hyperledger/fabric/peer
go install vendor/golang_org/x/crypto/chacha20poly1305: open /opt/go/pkg/linux_amd64/vendor/golang_org/x/crypto/chacha20poly1305.a: permission denied
Makefile:250: recipe for target '.build/bin/peer' failed
make: *** [.build/bin/peer] Error 1
```
rjones (Thu, 05 Apr 2018 20:05:24 GMT):
I'm going to bounce gerrit due to 500 errors in the UI
rameshthoomu (Thu, 05 Apr 2018 20:07:48 GMT):
ok
rjones (Thu, 05 Apr 2018 20:08:02 GMT):
gerrit is restarted.
rjones (Thu, 05 Apr 2018 20:24:36 GMT):
Jenkins will bounce soon.
rameshthoomu (Thu, 05 Apr 2018 20:38:05 GMT):
@troyronda @yacovm I see you have posted all comments in one go (VerifyBuild, Run DocsBuild, Run UnitTest and Run SmokeTest) in https://gerrit.hyperledger.org/r/#/c/20223/ -- as mentioned in https://github.com/rameshthoomu/ci-management/blob/master/docs/fabric_ci_build_process.md you have to post `VerifyBuild` comment first to build and publish docker images and binaries
yacovm (Thu, 05 Apr 2018 20:38:57 GMT):
makes sense
yacovm (Thu, 05 Apr 2018 20:39:04 GMT):
but the first one didn't start either
rameshthoomu (Thu, 05 Apr 2018 20:39:38 GMT):
yes had issues with gerrit.. @rjones restarted gerrit and jenkins..
rameshthoomu (Thu, 05 Apr 2018 20:40:11 GMT):
Once it's ready will re-trigger this patch by posting `VerifyBuild`
troyronda (Fri, 06 Apr 2018 00:17:17 GMT):
ok, thanks
rjones (Fri, 06 Apr 2018 16:11:29 GMT):
there will be a sort-of emergency outage of ingress (which means all Jenkins) and gerrit for ~1 hour later today. I hope to do it after COB Pacific.
cbf (Sun, 08 Apr 2018 00:59:41 GMT):
@rameshthoomu https://gerrit.hyperledger.org/r/c/20081/ keeps failing, but works like a charm locally (I've explored multiple variations of byfn, eyfn, fabcar, etc and everything works as expected. However, I also note that for the fabric-samples build we are building fabric. This seems wrong. I thought that we were going to leverage tagged binaries and images from a previous build of fabric (eg a stable nightly build).
cbf (Sun, 08 Apr 2018 01:00:33 GMT):
@bmos299 ^^
cbf (Sun, 08 Apr 2018 01:29:45 GMT):
@rameshthoomu also need to research this failure https://gerrit.hyperledger.org/r/c/18233/
cbf (Sun, 08 Apr 2018 01:31:04 GMT):
I have a feeling that https://gerrit.hyperledger.org/r/c/20187/ has broken the build @mastersingh24 @greg.haskins
rameshthoomu (Sun, 08 Apr 2018 01:47:59 GMT):
@cbf https://gerrit.hyperledger.org/r/#/c/20081/ is failing on go1.10.. see the updates in FAB-9379
rameshthoomu (Sun, 08 Apr 2018 01:49:41 GMT):
https://gerrit.hyperledger.org/r/#/c/18233/ seems this is failing with the recent CI configuration change.. It didn't find the BASE_VERSION from the makefile.. Will check this and submit a quick patch
cbf (Sun, 08 Apr 2018 02:01:00 GMT):
thanks
greg.haskins (Sun, 08 Apr 2018 13:11:55 GMT):
@cbf anything is possible, but im trying to wrap my head around how the CI passed for 20187 if it broke it
greg.haskins (Sun, 08 Apr 2018 13:11:59 GMT):
let me look deeper
mastersingh24 (Sun, 08 Apr 2018 14:30:05 GMT):
18233 passed
rameshthoomu (Sun, 08 Apr 2018 14:39:58 GMT):
@greg.haskins the failure is not because of 20187.. Ignore that error..
rameshthoomu (Sun, 08 Apr 2018 14:40:56 GMT):
But I see error in master unit-test coverage build job with 20187 change..
rameshthoomu (Sun, 08 Apr 2018 14:41:29 GMT):
https://jenkins.hyperledger.org/view/Daily/job/fabric-unit-test-coverage-daily-master-x86_64/14/consoleFull
zhaochy (Mon, 09 Apr 2018 06:09:21 GMT):
hello, any one can help look at this https://logs.hyperledger.org/production/vex-yul-hyp-jenkins-3/fabric-sdk-node8-verify-x86_64/614/console-timestamp.log.gz
zhaochy (Mon, 09 Apr 2018 06:09:42 GMT):
it seems the CI forgot to build the `ccenv` image
rjones (Mon, 09 Apr 2018 08:29:09 GMT):
@zhaochy I think that was recently changed
zhaochy (Mon, 09 Apr 2018 08:30:33 GMT):
has this already fixed?
rjones (Mon, 09 Apr 2018 08:34:35 GMT):
@zhaochy I don't think so. I was wrong: I didn't pay close enough attention to the link
rjones (Mon, 09 Apr 2018 08:36:11 GMT):
@zhaochy I do see this though: https://github.com/hyperledger/ci-management/blame/master/jjb/fabric-sdk-node/fabric-sdk-node-jobs.yaml#L28 that job did change three days ago
zhaochy (Mon, 09 Apr 2018 08:40:55 GMT):
@rjones https://jira.hyperledger.org/browse/FAB-9363
zhaochy (Mon, 09 Apr 2018 08:41:19 GMT):
the ccenv build has been removed from `make peer-docker`
rjones (Mon, 09 Apr 2018 08:41:32 GMT):
ah ha. you might add yourself as a watcher to that bug
zhaochy (Mon, 09 Apr 2018 08:57:48 GMT):
@rjones I created a ticket for this https://jira.hyperledger.org/browse/FAB-9422
zhaochy (Mon, 09 Apr 2018 08:58:10 GMT):
and submitted a CR https://gerrit.hyperledger.org/r/20331
rjones (Mon, 09 Apr 2018 09:03:54 GMT):
https://jenkins.hyperledger.org/job/fabric-sdk-node8-verify-x86_64/615/console you can watch
sheehan (Mon, 09 Apr 2018 15:03:10 GMT):
Hey @rameshthoomu - how can we add check_license.sh to the CI process? People keep checking stuff in that does not pass this check and it causes 'make all' to fail on our local systems. I'll be happy to add it if you point me to the script I need to update
rameshthoomu (Mon, 09 Apr 2018 15:05:08 GMT):
We have this added in basic-checks make target.. recently I have added and removed because I see issues in License files..
rameshthoomu (Mon, 09 Apr 2018 15:05:48 GMT):
I thinks it’s better to fix all the issues which basic-checks target is reporting and enable the same in CI script
sheehan (Mon, 09 Apr 2018 15:08:33 GMT):
sounds like a good plan. I'll report back here when issues are fixed
tongli (Mon, 09 Apr 2018 19:02:18 GMT):
@rjones, I would like to add a new cello image, still in the works, my understanding is that once I have the dockerfile checked in merged, I should ask you to create an automated build on docker hub, please let me know if that is correct.
rjones (Mon, 09 Apr 2018 19:03:20 GMT):
I'm not sure exactly what you're asking. I think those are two orthogonal requests.
rjones (Mon, 09 Apr 2018 19:03:42 GMT):
If you mean `packer` image, that has nothing to do with dockerhub.
tongli (Mon, 09 Apr 2018 19:04:31 GMT):
@rjones, I mean a docker image like this one.
tongli (Mon, 09 Apr 2018 19:04:56 GMT):
https://hub.docker.com/r/hyperledger/cello-engine/
rjones (Mon, 09 Apr 2018 19:05:28 GMT):
I see. just open a helpdesk ticket
tongli (Mon, 09 Apr 2018 19:07:09 GMT):
so, once the Dockerfile is there, i open the ticket with the project url and docker file path, then after you done your part, the image will be automatically built when there is a change to the file, correct?
tongli (Mon, 09 Apr 2018 19:11:39 GMT):
@rjones
rjones (Mon, 09 Apr 2018 20:21:43 GMT):
I've never looked into exactly how or when docker hub rebuilds. I usually just point out at the repo.
rjones (Tue, 10 Apr 2018 16:54:33 GMT):
There will be an outage at 1600 Thursday. https://lists.hyperledger.org/pipermail/hyperledger-tsc/2018-April/001450.html
jyellick (Tue, 10 Apr 2018 19:31:14 GMT):
@rameshthoomu You had linked me to https://github.com/rameshthoomu/ci-management/blob/master/docs/fabric.md previously, but it appears to be gone now. Is there a new location for this document?
rameshthoomu (Tue, 10 Apr 2018 19:32:07 GMT):
sorry I might be renamed it to this https://github.com/rameshthoomu/ci-management/blob/master/docs/fabric_ci_build_process.md
kostas (Tue, 10 Apr 2018 19:35:09 GMT):
Can we carry over these commands to the original`ci-management` repo as well?
kostas (Tue, 10 Apr 2018 19:35:09 GMT):
Can we carry over these commands to the original`ci-management` repo as well?
kostas (Tue, 10 Apr 2018 19:35:09 GMT):
Can we carry over these commands to the original`ci-management` repo as well?
kostas (Tue, 10 Apr 2018 19:35:09 GMT):
Can we carry over these commands to the original `ci-management` repo as well?
kostas (Tue, 10 Apr 2018 19:35:28 GMT):
https://github.com/hyperledger/ci-management/blob/master/docs/fabric_ci_process.md doesn't list them as best as I can tell.
rameshthoomu (Tue, 10 Apr 2018 19:53:54 GMT):
@kostas yes that's the target repo.. We have submitted patch.. It's in review https://gerrit.hyperledger.org/r/#/c/20307/
rameshthoomu (Tue, 10 Apr 2018 19:54:37 GMT):
trying to keep the same in RTD format.. see here http://ci-management1.readthedocs.io/en/latest/fabric_ci_process.html
kostas (Tue, 10 Apr 2018 20:50:59 GMT):
And just to confirm: are these commands case-sensitive? If they are (as I suspect), would it be easy to make them case-insensitive? (Not a dealbreaker.)
rjones (Tue, 10 Apr 2018 20:55:45 GMT):
@kostas I suspect you are correct
rjones (Tue, 10 Apr 2018 20:56:59 GMT):
@kostas I just verified, they are case sensitive
zhaochy (Wed, 11 Apr 2018 03:12:12 GMT):
@rjones we update the scripts for fabric-sdk-node 2 days ago, however only the master branch changed the Makefile, so I update the scripts again for other branches except master. https://gerrit.hyperledger.org/r/20425
rameshthoomu (Wed, 11 Apr 2018 03:20:13 GMT):
@zhaochy there is a patch updated with few more changes.. https://gerrit.hyperledger.org/r/#/c/20423/
zhaochy (Wed, 11 Apr 2018 05:51:55 GMT):
:smiley:
yacovm (Wed, 11 Apr 2018 09:27:14 GMT):
https://gerrit.hyperledger.org/r/#/q/owner:957245109%2540qq.com+status:open
yacovm (Wed, 11 Apr 2018 09:27:34 GMT):
@grapebaba
yacovm (Wed, 11 Apr 2018 09:27:51 GMT):
the guy that submitted these change sets is from your company no?
yacovm (Wed, 11 Apr 2018 09:27:51 GMT):
the guy (zhang gang) that submitted these change sets is from your company no?
grapebaba (Wed, 11 Apr 2018 09:28:45 GMT):
:sweat_smile:no
yacovm (Wed, 11 Apr 2018 09:28:50 GMT):
why no? qq.com ?
grapebaba (Wed, 11 Apr 2018 09:29:06 GMT):
just like gmail.com
yacovm (Wed, 11 Apr 2018 09:29:35 GMT):
oh
grapebaba (Wed, 11 Apr 2018 09:29:40 GMT):
a popular public email in China
yacovm (Wed, 11 Apr 2018 09:29:45 GMT):
you were the only one using qq.com in this project
yacovm (Wed, 11 Apr 2018 09:29:52 GMT):
so i thought you work there... sorry
grapebaba (Wed, 11 Apr 2018 09:29:58 GMT):
:sweat_smile:
yacovm (Wed, 11 Apr 2018 09:30:25 GMT):
so anyway @rjones - this is considered spam in a way, isn't it?
yacovm (Wed, 11 Apr 2018 09:30:57 GMT):
Clipboard - April 11, 2018 12:30 PM
jtclark (Wed, 11 Apr 2018 13:27:39 GMT):
GM
rjones (Wed, 11 Apr 2018 14:41:41 GMT):
@yacovm gone dot com
rjones (Thu, 12 Apr 2018 12:42:23 GMT):
Reminder: outage in about 10 hours: https://chat.hyperledger.org/channel/infra-support?msg=Lgno5LZYh7bBTr4Tc
rameshthoomu (Thu, 12 Apr 2018 12:53:34 GMT):
@rjones I think it's better to use notify this through @ here..
rjones (Thu, 12 Apr 2018 12:58:28 GMT):
eh there are 300 people in here, and only maybe a dozen are active.
skarim (Thu, 12 Apr 2018 16:40:57 GMT):
Hi, I am curious why are CI tests failing intermittently for fabric-ca? I am having to do a bunch of reverifies. See: https://gerrit.hyperledger.org/r/#/c/20247/
rameshthoomu (Thu, 12 Apr 2018 16:49:13 GMT):
@skarim looking into this..
rameshthoomu (Thu, 12 Apr 2018 16:52:57 GMT):
I see multiple failures on this patch but the last one says gerrit timeout which will fix after today's upgrade https://lists.hyperledger.org/pipermail/hyperledger-tsc/2018-April/001450.html
skarim (Thu, 12 Apr 2018 16:54:15 GMT):
@rameshthoomu Yeah, the end-2-end fails occasionally too and then will pass other times
rameshthoomu (Thu, 12 Apr 2018 16:58:43 GMT):
yes.. One suggestion is.. when a specific build fails, please trigger only that failed job.. see the comments you have to use to trigger the failed jobs
https://wiki.hyperledger.org/projects/fabric/fabric_ci_documentation?&#comment_phrases_to_trigger_failed_jobs
rameshthoomu (Thu, 12 Apr 2018 16:59:04 GMT):
@sambhavdutt could you please e2e build failures
rameshthoomu (Thu, 12 Apr 2018 16:59:04 GMT):
@sambhavdutt could you please check e2e build failures
sambhavdutt (Thu, 12 Apr 2018 17:00:34 GMT):
sure, will do
rameshthoomu (Thu, 12 Apr 2018 17:45:15 GMT):
@skarim got +1 on your patch..
skarim (Thu, 12 Apr 2018 17:46:06 GMT):
@rameshthoomu Thanks
floatware (Thu, 12 Apr 2018 19:09:09 GMT):
Has joined the channel.
sheehan (Thu, 12 Apr 2018 19:19:53 GMT):
Hi @rameshthoomu - it looks like `make basic checks` is passing now. For the license check, it only looks at the last two git commits which is why it was sometimes failing and sometimes passing. I think if you enable it in CI now it should prevent people from adding or editing files without the updated lincense
rameshthoomu (Thu, 12 Apr 2018 19:21:20 GMT):
👍
rjones (Fri, 13 Apr 2018 20:02:30 GMT):
Jenkins will be in shutdown mode for the next hour.
rjones (Fri, 13 Apr 2018 21:02:36 GMT):
shutdown mode is over
bdu 5 (Sat, 14 Apr 2018 20:55:31 GMT):
Has joined the channel.
zhaochy (Mon, 16 Apr 2018 08:14:49 GMT):
@rjones can you have a look at https://gerrit.hyperledger.org/r/#/c/20603/ s390x always fail
rameshthoomu (Mon, 16 Apr 2018 11:17:31 GMT):
@zhaochy I have deleted `/tmp/fabric-shim` which has root permission.. Build is triggered now..
jtclark (Mon, 16 Apr 2018 14:15:09 GMT):
GM all
jtclark (Mon, 16 Apr 2018 14:15:22 GMT):
@scottz do you have a dial in for the meeting this AM?
rameshthoomu (Mon, 16 Apr 2018 14:37:14 GMT):
@jtclark ping him directly or post in #fabric-quality
jtclark (Mon, 16 Apr 2018 14:37:24 GMT):
@rameshthoomu thx
rjones (Mon, 16 Apr 2018 17:17:04 GMT):
there is a pypi outage causing some build turbulence https://status.python.org/
sanchezl (Mon, 16 Apr 2018 18:58:15 GMT):
I'm getting a `make basic-checks are failed on this patch set for release-1.0: https://gerrit.hyperledger.org/r/c/20633/
```
16:57:55 + echo '-------> Perform make basic-checks (license spelling linter)'
16:57:55 -------> Perform make basic-checks (license spelling linter)
16:57:55 + make basic-checks
16:57:59 make: *** No rule to make target 'basic-checks'. Stop.
16:57:59 + '[' 2 = 0 ']'
16:57:59 + echo '------> make linter FAILED'
16:57:59 ------> make linter FAILED
16:57:59 + vote -m '"make basic-checks are failed"' -l F1-VerifyBuild=-1
16:57:59 + ssh -p 29418 hyperledger-jobbuilder@gerrit.hyperledger.org gerrit review 20633,1 --notify '"NONE"' -m '"make basic-checks are failed"' -l F1-VerifyBuild=-1
16:58:00 + exit 1
16:58:00 Build step 'Execute shell' marked build as failure
```
There is no `basic-checks` target in the Makefile.
sanchezl (Mon, 16 Apr 2018 18:58:15 GMT):
I'm getting a `make basic-checks are failed` on this patch set for release-1.0: https://gerrit.hyperledger.org/r/c/20633/
```
16:57:55 + echo '-------> Perform make basic-checks (license spelling linter)'
16:57:55 -------> Perform make basic-checks (license spelling linter)
16:57:55 + make basic-checks
16:57:59 make: *** No rule to make target 'basic-checks'. Stop.
16:57:59 + '[' 2 = 0 ']'
16:57:59 + echo '------> make linter FAILED'
16:57:59 ------> make linter FAILED
16:57:59 + vote -m '"make basic-checks are failed"' -l F1-VerifyBuild=-1
16:57:59 + ssh -p 29418 hyperledger-jobbuilder@gerrit.hyperledger.org gerrit review 20633,1 --notify '"NONE"' -m '"make basic-checks are failed"' -l F1-VerifyBuild=-1
16:58:00 + exit 1
16:58:00 Build step 'Execute shell' marked build as failure
```
There is no `basic-checks` target in the Makefile.
rameshthoomu (Mon, 16 Apr 2018 19:06:32 GMT):
oh yes,. This fails in release-1.0 branch.. ommm
rameshthoomu (Mon, 16 Apr 2018 19:20:56 GMT):
Will update CI script
Ammu (Tue, 17 Apr 2018 10:25:44 GMT):
if hackers taking information illegally from bank(AXIS bank), if the project into fabrics. if the data is taken from 1 peer how the owner of the bank get notification that our bank information has been stolen? in blockchain/fabrics
sambhavdutt (Tue, 17 Apr 2018 12:49:52 GMT):
Hello @Ammu
You can possibly ask this question in #fabric-questions channel
Ammu (Tue, 17 Apr 2018 13:56:25 GMT):
ok
jtclark (Wed, 18 Apr 2018 01:51:21 GMT):
@scottz - https://gerrit.hyperledger.org/r/#/c/20705/ <-- we can perhaps use this patch to test PTE. I'll ping you about this tomorrow AM.
YorkYu (Wed, 18 Apr 2018 04:23:34 GMT):
Has joined the channel.
pjjp (Wed, 18 Apr 2018 12:44:29 GMT):
Has joined the channel.
manish-sethi (Wed, 18 Apr 2018 23:36:07 GMT):
@rjones I rebased a stack of CRs starting with https://gerrit.hyperledger.org/r/#/c/14347/. However, for some of the CRs build did not kick of. Is there a key-word that I can type for starting the entire build (as I type 'Run UnitTest' for UTs only).
manish-sethi (Wed, 18 Apr 2018 23:36:07 GMT):
@rjones I rebases a stack of CRs starting with https://gerrit.hyperledger.org/r/#/c/14347/. However, for some of the CRs build did not kick of. Is there a key-word that I can type for starting the entire build (as I type 'Run UnitTest' for UTs only).
rjones (Wed, 18 Apr 2018 23:36:24 GMT):
hold still, OK?
manish-sethi (Wed, 18 Apr 2018 23:36:44 GMT):
sure
rjones (Wed, 18 Apr 2018 23:37:44 GMT):
boom
manish-sethi (Wed, 18 Apr 2018 23:38:01 GMT):
But just to know is there some word for this or have to kickoff Smoke test/ Unit test... individually?
rjones (Wed, 18 Apr 2018 23:38:47 GMT):
you would need to ask @tongli or @rameshthoomu . Also, in 22 minutes, I no longer directly support CI, so you will need to ask @jwagantall
rameshthoomu (Wed, 18 Apr 2018 23:39:30 GMT):
@manish-sethi will check
rjones (Wed, 18 Apr 2018 23:39:54 GMT):
I used the manual gerrit query for `owner:"Manish Sethi" status:open`, selected all, and hit the GO GO GO button
manish-sethi (Wed, 18 Apr 2018 23:41:16 GMT):
Thanks Ry and Ramesh
manish-sethi (Wed, 18 Apr 2018 23:42:02 GMT):
Do we have access to this 'GO' button? I don;t see in the UI..
rameshthoomu (Wed, 18 Apr 2018 23:42:08 GMT):
@manish-sethi I think it triggered now
rameshthoomu (Wed, 18 Apr 2018 23:42:25 GMT):
https://jenkins.hyperledger.org/job/fabric-verify-build-checks-x86_64/551/
manish-sethi (Wed, 18 Apr 2018 23:43:15 GMT):
Yes Ramesh. If I get stuck at times, is there a way for me to start the way you did it?
rameshthoomu (Wed, 18 Apr 2018 23:43:43 GMT):
yes. pls check fabric section here https://wiki.hyperledger.org/projects/fabric/fabric_ci_documentation?&#comment_phrases_to_trigger_failed_jobs
rameshthoomu (Wed, 18 Apr 2018 23:44:48 GMT):
Before you post `Run SmokeTest/Run UnitTest`, please make sure the patch got +1 on verifyBuild
rjones (Wed, 18 Apr 2018 23:45:02 GMT):
I think what @manish-sethi is looking for is a way to restart the whole build chain for a string of patchsets.
manish-sethi (Wed, 18 Apr 2018 23:45:14 GMT):
yes Ry
rjones (Wed, 18 Apr 2018 23:45:36 GMT):
I have superpowers in Jenkins that let me do that.
manish-sethi (Wed, 18 Apr 2018 23:45:53 GMT):
Will reverify-x trigger everything a fresh?
manish-sethi (Wed, 18 Apr 2018 23:45:53 GMT):
Will reverify-x trigger everything afresh?
rameshthoomu (Wed, 18 Apr 2018 23:47:30 GMT):
No.. You should not do `reverify` in fabric builds.. as these are dependent on each other..
rameshthoomu (Wed, 18 Apr 2018 23:49:17 GMT):
You always have to look for VerifyBuild result, as this is the first job get trigger by patch set.. If you want to trigger any failed builds after VerifyBuild got +1, you can post comment phrases in the gerrit patch set..
rameshthoomu (Wed, 18 Apr 2018 23:51:12 GMT):
Will that help
rjones (Wed, 18 Apr 2018 23:51:45 GMT):
of course you could script it
manish-sethi (Wed, 18 Apr 2018 23:53:09 GMT):
Sure, thanks folks :thumbsup:
jyellick (Thu, 19 Apr 2018 05:07:59 GMT):
Any guess as to why this rebase did not trigger CI: https://gerrit.hyperledger.org/r/c/20749 ?
jyellick (Thu, 19 Apr 2018 05:07:59 GMT):
Any guess as to why this rebase (patchset 1) did not trigger CI: https://gerrit.hyperledger.org/r/c/20749 ? After an hour and a half, still nothing, so rebased again and kicked off within minutes.
rjones (Thu, 19 Apr 2018 13:49:50 GMT):
https://status.linuxfoundation.org/incidents/y1hf910j199d
jtclark (Thu, 19 Apr 2018 14:19:24 GMT):
@rjones is there an ETA on when the jenkins infra will be back up?
jtclark (Thu, 19 Apr 2018 14:23:51 GMT):
just checked the status update - looks to be resolved....
rjones (Thu, 19 Apr 2018 14:24:10 GMT):
It is resolved and builds are happening
sambhavdutt (Thu, 19 Apr 2018 14:25:46 GMT):
:thumbsup:
jtclark (Thu, 19 Apr 2018 19:48:09 GMT):
trying to get some info to complete FAB-5283
jtclark (Thu, 19 Apr 2018 19:48:37 GMT):
was this the change that modifies the gopath that just got merged: https://gerrit.hyperledger.org/r/#/c/20723/
jtclark (Thu, 19 Apr 2018 19:49:15 GMT):
hmmm this looks like something else.....
rjones (Fri, 20 Apr 2018 02:22:11 GMT):
Has left the channel.
sanchezl (Fri, 20 Apr 2018 18:34:52 GMT):
We're trying to run node tests as a non-root user when we run into this:
```not ok 323 Checking: for valid PIN failed with ::Error: /temp: cannot read file data: Is a directory at Error (native) Load:136[00m[00m[2m[38;5;66m
---[00m
operator: fail
at: checkError (/home/jenkins/gopath/src/github.com/hyperledger/fabric-sdk-node/test/unit/cryptosuite-pkcs11.js:91:6)
stack: |-
Error: Checking: for valid PIN failed with ::Error: /temp: cannot read file data: Is a directory
at Error (native) Load:136
at Test.assert [as _assert] (/home/jenkins/gopath/src/github.com/hyperledger/fabric-sdk-node/node_modules/tape/lib/test.js:225:54)
at Test.bound [as _assert] (/home/jenkins/gopath/src/github.com/hyperledger/fabric-sdk-node/node_modules/tape/lib/test.js:77:32)
at Test.fail (/home/jenkins/gopath/src/github.com/hyperledger/fabric-sdk-node/node_modules/tape/lib/test.js:318:10)
at Test.bound [as fail] (/home/jenkins/gopath/src/github.com/hyperledger/fabric-sdk-node/node_modules/tape/lib/test.js:77:32)
at checkError (/home/jenkins/gopath/src/github.com/hyperledger/fabric-sdk-node/test/unit/cryptosuite-pkcs11.js:91:6)
at test (/home/jenkins/gopath/src/github.com/hyperledger/fabric-sdk-node/test/unit/cryptosuite-pkcs11.js:101:3)
at Test.
cbf (Sun, 22 Apr 2018 16:59:48 GMT):
@rameshthoomu check out https://gerrit.hyperledger.org/r/20875
rameshthoomu (Sun, 22 Apr 2018 17:17:03 GMT):
Missing license header in .gitignore file..
cbf (Sun, 22 Apr 2018 20:13:24 GMT):
yeah, saw that remedied
jtclark (Mon, 23 Apr 2018 13:11:53 GMT):
GM all.
cbf (Mon, 23 Apr 2018 14:30:54 GMT):
hey @rameshthoomu are you free at noon or 1 pm to chat?
rameshthoomu (Mon, 23 Apr 2018 14:31:35 GMT):
yes @cbf
cbf (Mon, 23 Apr 2018 14:35:56 GMT):
cool, will send an invite
aambati (Mon, 23 Apr 2018 15:13:58 GMT):
@rameshthoomu have you seen this error...i see in the fabric-ca-rtd-verify-job output: ```07:06:00 [ssh-agent] Using credentials hyperledger-jobbuilder
07:06:01 FATAL: java.io.IOException: Unexpected termination of the channel
07:06:01 java.io.EOFException
07:06:01 at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2670)
07:06:01 at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3145)
07:06:01 at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:857)
07:06:01 at java.io.ObjectInputStream.
aambati (Mon, 23 Apr 2018 15:14:05 GMT):
https://jenkins.hyperledger.org/job/fabric-ca-rtd-verify-job/15/console
aambati (Mon, 23 Apr 2018 15:14:31 GMT):
btw, what is the comment text to rerun this job?
rameshthoomu (Mon, 23 Apr 2018 15:23:55 GMT):
@aambati try `recheck`
rameshthoomu (Mon, 23 Apr 2018 15:24:04 GMT):
Could be a network glitch..
jtclark (Mon, 23 Apr 2018 17:27:23 GMT):
@rameshthoomu - any reason why I can't generate the s390x jenkins jobs from ci-management ?
jtclark (Mon, 23 Apr 2018 17:28:18 GMT):
when I try to generate an x86_64 job, it works fine
rameshthoomu (Mon, 23 Apr 2018 17:50:25 GMT):
@jtclark which job you are trying? You should have a jjb template to push
jtclark (Mon, 23 Apr 2018 17:51:07 GMT):
fabric-ca-safesql-weekly
jtclark (Mon, 23 Apr 2018 17:51:17 GMT):
I have the jjb template
jtclark (Mon, 23 Apr 2018 17:51:38 GMT):
what I wanted to try was fabric-ca-safesql-weekly-s390x
jtclark (Mon, 23 Apr 2018 17:51:51 GMT):
but when I try to generate that template, it won't generate it.
jtclark (Mon, 23 Apr 2018 17:52:23 GMT):
I just generated the x86_64 job: https://jenkins.hyperledger.org/sandbox/job/fabric-ca-safesql-weekly-x86_64
jtclark (Mon, 23 Apr 2018 19:51:13 GMT):
@rameshthoomu :point_up_tone2:
rameshthoomu (Mon, 23 Apr 2018 20:18:37 GMT):
was at scott desk..
rameshthoomu (Mon, 23 Apr 2018 20:19:16 GMT):
You have to specify the arch value in the template..
rameshthoomu (Mon, 23 Apr 2018 20:20:02 GMT):
little different.. remove the {arch} and hardcode the s390x.. OR change the node, and properties values in x86_64 job to s390x
jtclark (Mon, 23 Apr 2018 21:35:41 GMT):
ah ok
zhaochy (Tue, 24 Apr 2018 03:24:44 GMT):
@rjones can you have a look at https://gerrit.hyperledger.org/r/#/c/20609/
rjones (Tue, 24 Apr 2018 03:24:45 GMT):
Has joined the channel.
rjones (Tue, 24 Apr 2018 03:25:35 GMT):
what am I supposed to look at?
zhaochy (Tue, 24 Apr 2018 03:25:49 GMT):
ls: cannot access '/w/workspace/fabric-sdk-node8-verify-x86_64/archives/': No such file or directory
rjones (Tue, 24 Apr 2018 03:27:23 GMT):
```package golang.org/x/lint: unrecognized import path "golang.org/x/lint" (parse https://golang.org/x/lint?go-get=1: no go-import meta tags ())
make[1]: *** [gotool.golint] Error 1
gotools.mk:53: recipe for target 'gotool.golint' failed
make[1]: Leaving directory '/opt/gopath/src/github.com/hyperledger/fabric'
gotools.mk:58: recipe for target '/opt/gotools/bin/golint' failed
make: *** [/opt/gotools/bin/golint] Error 2
Makefile:242: recipe for target '.build/docker/gotools' failed
make: *** [.build/docker/gotools] Error 2
-----> make docker failed
``` looks more interesting
zhaochy (Tue, 24 Apr 2018 03:28:30 GMT):
seems can't build the docker images
rjones (Tue, 24 Apr 2018 03:38:19 GMT):
it looks like a lint error
rameshthoomu (Tue, 24 Apr 2018 03:38:41 GMT):
@zhaochy golint is a thirdparty package.. seems there is some problem with the golint package..
zhaochy (Tue, 24 Apr 2018 03:38:54 GMT):
find a issue here https://github.com/golang/lint/issues/288
rameshthoomu (Tue, 24 Apr 2018 03:38:58 GMT):
all the builds are failing with this error.. Irrespective of the branches..
rjones (Tue, 24 Apr 2018 03:40:38 GMT):
Has left the channel.
zhaochy (Tue, 24 Apr 2018 03:42:04 GMT):
maybe a network problem?
rameshthoomu (Tue, 24 Apr 2018 03:46:30 GMT):
or something might have changed at the golint side..
rameshthoomu (Tue, 24 Apr 2018 03:47:04 GMT):
@zhaochy see this one https://github.com/golang/lint/issues/397
rameshthoomu (Tue, 24 Apr 2018 03:47:08 GMT):
this is open bug
rameshthoomu (Tue, 24 Apr 2018 03:48:36 GMT):
There are few workarounds mentioned in the bug..
zhaochy (Tue, 24 Apr 2018 03:50:27 GMT):
we have to wait until golint fix the error
rameshthoomu (Tue, 24 Apr 2018 03:54:05 GMT):
yes.. otherwise, we have to incorporate the same workaround in all the fabric branches
rameshthoomu (Tue, 24 Apr 2018 04:50:51 GMT):
@zhaochy FAB has been created to incorporate workaround in fabric code till we get the fix in golint https://jira.hyperledger.org/browse/FAB-9667
rameshthoomu (Tue, 24 Apr 2018 04:50:58 GMT):
Murali is working on the fix..
hosemose (Tue, 24 Apr 2018 04:58:44 GMT):
Has joined the channel.
cbf (Tue, 24 Apr 2018 12:42:03 GMT):
@rameshthoomu looks like I need some changes in the verify tests in order to transition from use of uname to determine architecture
cbf (Tue, 24 Apr 2018 12:42:13 GMT):
fabric-baseimage-verify-docker-x86_64
cbf (Tue, 24 Apr 2018 12:57:22 GMT):
I *think* I know what needs to be changed, what I am less clear on is how to submit the change... does a change to ci-management run against the sandbox to test?
rameshthoomu (Tue, 24 Apr 2018 13:41:16 GMT):
Chris, got in trouble with car .. could be battery is dead.
rameshthoomu (Tue, 24 Apr 2018 13:41:59 GMT):
Push the change to CI-management gerrit and provide the patchset
rameshthoomu (Tue, 24 Apr 2018 13:42:11 GMT):
Will test this in sandbox
jtclark (Tue, 24 Apr 2018 13:45:31 GMT):
@cbf not familiar with what you're trying to test, but if it's a new jenkins job template, I can try to get it on the sandbox for you
jtclark (Tue, 24 Apr 2018 13:46:14 GMT):
sounds like it, based on the fact that you mentioned `fabric-baseimage-verify-docker-x86_64`
cbf (Tue, 24 Apr 2018 14:14:07 GMT):
ok thanks guys
cbf (Tue, 24 Apr 2018 14:21:27 GMT):
https://gerrit.hyperledger.org/r/20943
kostas (Tue, 24 Apr 2018 16:03:28 GMT):
Regarding the golint snafu -- any reason why we do not vendor these tools instead of go getting them every time?
sambhavdutt (Tue, 24 Apr 2018 20:48:47 GMT):
goes without saying , after the Merge, this work around patch https://gerrit.hyperledger.org/r/#/c/20929/ has fixed the golint problem, Tested a fabric-end-2-end CI job and it is working fine without running into the golint error, a rebase should fix this patch, for older fabric- patchsets
cbf (Wed, 25 Apr 2018 19:55:39 GMT):
@jwagantall @rameshthoomu @rjones ok, https://gerrit.hyperledger.org/r/c/20875/ has been merged, this gives us the script to generate and optionally push manifests for v1.1 multi-arch images
cbf (Wed, 25 Apr 2018 19:55:39 GMT):
@jwagantall @rameshthoomu @rjones ok, https://gerrit.hyperledger.org/r/c/20875/ has been merged, this gives us the script to generate and optionally push manifests for v1.1 images
rjones (Wed, 25 Apr 2018 19:55:42 GMT):
Has joined the channel.
cbf (Wed, 25 Apr 2018 19:56:17 GMT):
and for v0.4.7 baseimage images as well
cbf (Wed, 25 Apr 2018 19:59:08 GMT):
all it needs is someone with the right credentials to run that script in publish mode
rameshthoomu (Wed, 25 Apr 2018 20:31:28 GMT):
Nice @cbf .. Will use this script to publish images to nexus3
rameshthoomu (Wed, 25 Apr 2018 20:35:57 GMT):
so will this `username ${USER} --password ${PASSWORD}` look for dockerhub credentials? What else we need to push images from CI?
rameshthoomu (Wed, 25 Apr 2018 20:36:58 GMT):
manifest tool should be available for sure..
rjones (Wed, 25 Apr 2018 20:59:36 GMT):
the `duckerhub` credentials should be in there somewhere
rjones (Wed, 25 Apr 2018 21:02:09 GMT):
@rameshthoomu `DOCKER_HUB_USERNAME` `DOCKER_HUB_EMAIL` `DOCKER_HUB_PASSWORD`
rameshthoomu (Wed, 25 Apr 2018 21:02:42 GMT):
yes..
rjones (Wed, 25 Apr 2018 21:02:59 GMT):
OK.
rjones (Wed, 25 Apr 2018 21:03:24 GMT):
@jwagantall ^^^
rameshthoomu (Wed, 25 Apr 2018 21:03:29 GMT):
If USER and PASSWORD is looking for dockerhub, then it need to modified accordingly
rjones (Wed, 25 Apr 2018 21:04:07 GMT):
I think when you call it you just call it that way.
rjones (Wed, 25 Apr 2018 21:04:25 GMT):
call it with $DOCKER_HUB_USER for argv[1] and ... for ...
cbf (Wed, 25 Apr 2018 21:04:51 GMT):
right... you don't need to publish the images, they are already published
cbf (Wed, 25 Apr 2018 21:07:06 GMT):
usage() {
echo "Usage: $0 [-g] | [-p
jwagantall (Wed, 25 Apr 2018 21:45:27 GMT):
sorry for the delay... were you guys able to use the dockerhub creds? they are defined globally in Jenkins
rjones (Thu, 26 Apr 2018 00:00:19 GMT):
Has left the channel.
voutasaurus (Thu, 26 Apr 2018 17:02:49 GMT):
Has joined the channel.
voutasaurus (Thu, 26 Apr 2018 17:06:32 GMT):
I'm curious about this, if all of these containers are explicitly pulled into the hyperledger project dockerhub, wouldn't it make sense to make the versions of the dependent containers match the version of fabric?
[ ](https://chat.hyperledger.org/channel/fabric-questions?msg=hLYb4eAcYfyQfsnBs)
voutasaurus (Thu, 26 Apr 2018 17:09:42 GMT):
It seems like the version required for "third party images" is currently 0.4.6 https://github.com/hyperledger/fabric/blob/release-1.1/scripts/bootstrap.sh#L13
voutasaurus (Thu, 26 Apr 2018 17:10:16 GMT):
This seems strange to me seeing as the version of fabric is 1.1.0, why not make the version numbers line up?
rartin (Thu, 26 Apr 2018 17:28:23 GMT):
Has joined the channel.
jtclark (Thu, 26 Apr 2018 18:13:33 GMT):
@rameshthoomu, @scottz - I think that both of these are ready. please review once more, I've updated both patches with the test results:
jtclark (Thu, 26 Apr 2018 18:13:47 GMT):
https://gerrit.hyperledger.org/r/#/c/20695/
jtclark (Thu, 26 Apr 2018 18:13:52 GMT):
https://gerrit.hyperledger.org/r/#/c/20681/
rjones (Thu, 26 Apr 2018 19:15:29 GMT):
Has joined the channel.
rjones (Thu, 26 Apr 2018 19:15:50 GMT):
@rameshthoomu congratulations: https://gerrit.hyperledger.org/r/#/c/20521/ sorry it took so long!
rameshthoomu (Thu, 26 Apr 2018 20:05:31 GMT):
Thanks @rjones .. Will do my best
sambhavdutt (Thu, 26 Apr 2018 20:36:20 GMT):
@rameshthoomu Congrats !
rameshthoomu (Fri, 27 Apr 2018 12:24:49 GMT):
@sambhavdutt test this change in sandbox https://gerrit.hyperledger.org/r/#/c/20923/
sambhavdutt (Fri, 27 Apr 2018 12:31:24 GMT):
sure, will do
chainsaw (Fri, 27 Apr 2018 15:51:06 GMT):
Has joined the channel.
cbf (Fri, 27 Apr 2018 22:43:44 GMT):
hi @rameshthoomu - trying to make sense of this failure
cbf (Fri, 27 Apr 2018 22:44:19 GMT):
the build step successfully built the image that the smoketest is failing on (fabric-ccenv:etc)
cbf (Fri, 27 Apr 2018 22:44:33 GMT):
https://gerrit.hyperledger.org/r/c/20853/
rameshthoomu (Fri, 27 Apr 2018 22:53:06 GMT):
Looking into it
rameshthoomu (Fri, 27 Apr 2018 22:59:34 GMT):
@cbf CI config has to update.. See this line https://github.com/hyperledger/ci-management/blob/master/jjb/fabric-samples/include-raw-fabric-samples-byfn-smoke.sh#L25
rameshthoomu (Fri, 27 Apr 2018 23:01:53 GMT):
CI still looking for (uname -m) value..
cbf (Fri, 27 Apr 2018 23:11:33 GMT):
ah, do you want me to submit that change?
rameshthoomu (Fri, 27 Apr 2018 23:18:07 GMT):
better to change after the patch is merged. Otherwise, all the builds will fail till this patch is merged.. I can test this in sandbox if you want.
jyellick (Sat, 28 Apr 2018 04:37:42 GMT):
@rameshthoomu @rjones It looks like the smoke tests are being kicked off even on CRs which are pushed with a WIP tag for some reason:
For example: https://gerrit.hyperledger.org/r/c/21169/ (and see some of its WIP parents with the same symptoms)
rjones (Sat, 28 Apr 2018 04:38:16 GMT):
@jwagantall ^^^
jwagantall (Sat, 28 Apr 2018 04:41:10 GMT):
@jyellick Can you please create an RT ticket (email to helpdesk@hyperledger.org) I can look into it..
jyellick (Sat, 28 Apr 2018 04:41:51 GMT):
@jwagantall Sure -- is there anything more to it than emailing my problem to this address? Any special content in the subject like or body?
jyellick (Sat, 28 Apr 2018 04:41:51 GMT):
@jwagantall Sure -- is there anything more to it than emailing my problem to this address? Any special content in the subject line or body?
jwagantall (Sat, 28 Apr 2018 04:42:52 GMT):
as long as you add a description of the behavior expected i should be fine with that.. I can ask any questions back to you in case I have.
rameshthoomu (Sat, 28 Apr 2018 04:48:18 GMT):
@jyellick pls ignore that.. I have pushed smoke test job to sandbox to test Chris patch..
jyellick (Sat, 28 Apr 2018 04:48:45 GMT):
@rameshthoomu @jwagantall You were 30 seconds late, I just sent that email off
rameshthoomu (Sat, 28 Apr 2018 04:49:16 GMT):
I have deleted the "trigger-on" now from the smoketest job..
rameshthoomu (Sat, 28 Apr 2018 04:49:16 GMT):
I have deleted the "trigger-on" now from the sandbox smoketest job..
jyellick (Sat, 28 Apr 2018 04:49:56 GMT):
Thanks for the update. So, I should not have to worry about getting these additional messages if I push updates to the WIP now?
rameshthoomu (Sat, 28 Apr 2018 04:50:05 GMT):
Yes..
jwagantall (Sat, 28 Apr 2018 04:50:27 GMT):
ill close the ticket if not needed
rameshthoomu (Sat, 28 Apr 2018 04:50:43 GMT):
@jwagantall yes please close the ticket..
jtclark (Mon, 30 Apr 2018 11:02:09 GMT):
GM all
rameshthoomu (Mon, 30 Apr 2018 12:49:03 GMT):
I will be OOO today and tomorrow..
paul.sitoh (Mon, 30 Apr 2018 15:30:58 GMT):
Has joined the channel.
jtclark (Mon, 30 Apr 2018 17:49:12 GMT):
@sambhavdutt how are things today?
sambhavdutt (Mon, 30 Apr 2018 17:50:52 GMT):
Hi @jtclark
not bad I'd say, a few build fails that have been going on but nothing new that needs a bug
jtclark (Mon, 30 Apr 2018 17:51:00 GMT):
ok cool.
jtclark (Mon, 30 Apr 2018 17:51:18 GMT):
submitting some stuff for review today....
Aswath8687 (Tue, 01 May 2018 03:03:39 GMT):
Has joined the channel.
rameshthoomu (Tue, 01 May 2018 03:40:37 GMT):
@cbf tested this patch https://gerrit.hyperledger.org/r/#/c/20853/ in sandbox and it worked. See the log here https://logs.hyperledger.org/sandbox/vex-yul-hyp-jenkins-2/fabric-smoke-tests-x86_64/1/
manish-sethi (Tue, 01 May 2018 13:30:08 GMT):
@jwagantall / @rameshthoomu smoke tests are failing for CRs https://gerrit.hyperledger.org/r/#/c/14355/, https://gerrit.hyperledger.org/r/#/c/14511/
manish-sethi (Tue, 01 May 2018 13:30:31 GMT):
Can you please see what could be the potential issue?
rjones (Tue, 01 May 2018 13:54:33 GMT):
@rameshthoomu @jwagantall Smoke tests are running for change sets it should not run. Look at this: https://gerrit.hyperledger.org/r/#/c/21239/ smoke and unit tests are set +1 correctly, then smoke test runs and removes those votes. Why did smoke test run at all?
rameshthoomu (Tue, 01 May 2018 13:59:44 GMT):
@sambhavdutt @jtclark could you pls check this issue..
rameshthoomu (Tue, 01 May 2018 14:00:07 GMT):
I am on drive right now..
sambhavdutt (Tue, 01 May 2018 14:00:11 GMT):
Good Day, sure, will look into it
jtclark (Tue, 01 May 2018 14:00:13 GMT):
we will lok
jtclark (Tue, 01 May 2018 14:00:13 GMT):
we will look
jtclark (Tue, 01 May 2018 14:08:32 GMT):
the smoke test triggered, even though it was just a change to the .md file
jtclark (Tue, 01 May 2018 14:08:43 GMT):
which isn't right.....
jtclark (Tue, 01 May 2018 14:08:47 GMT):
still looking.....
sambhavdutt (Tue, 01 May 2018 14:11:18 GMT):
Hello @rjones
This voting was from sandbox, for a fabric-smoke-test job that was tested. This job has been removed from sandbox now
rjones (Tue, 01 May 2018 14:13:17 GMT):
@sambhavdutt @jwagantall I disabled the gerrit trigger in sandbox specifically to prevent these issues. Please don't re-enable gerrit trigger in sandbox.
sambhavdutt (Tue, 01 May 2018 14:13:47 GMT):
sure thing
rjones (Tue, 01 May 2018 14:15:42 GMT):
@jwagantall I've edited the configuration for gerrit-trigger in sandbox to be invalid.
jtclark (Tue, 01 May 2018 14:16:58 GMT):
so, basically we weren't seeing a vote from the production Jenkins instance? is that what you guys are saying?
jtclark (Tue, 01 May 2018 14:17:31 GMT):
cause I just looked at the job: https://jenkins.hyperledger.org/view/fabric/job/fabric-verify-build-checks-x86_64/1043/console
jtclark (Tue, 01 May 2018 14:17:39 GMT):
and I don't see where the smoke test ran at all....
sambhavdutt (Tue, 01 May 2018 14:18:04 GMT):
@jtclark yes, this was a voting from sandbox job and not from production.
jtclark (Tue, 01 May 2018 14:18:47 GMT):
@sambhavdutt ok. if we reverify, then will it display the correct votes?
sambhavdutt (Tue, 01 May 2018 14:20:14 GMT):
@jtclark yes, it should just run the docs-build job as this is a .md change
jtclark (Tue, 01 May 2018 14:20:25 GMT):
ok cool.
jtclark (Tue, 01 May 2018 14:30:31 GMT):
@rjones, @sambhavdutt - should we try a reverify then?
silliman (Tue, 01 May 2018 14:32:57 GMT):
Has left the channel.
sambhavdutt (Tue, 01 May 2018 14:33:03 GMT):
@jtclark not required, the tests were already retriggered, and it ran as expected last time
jtclark (Tue, 01 May 2018 14:35:23 GMT):
I see. fair enough.
jyellick (Tue, 01 May 2018 15:24:57 GMT):
@rameshthoomu @jwagantall When I modify a commit message to remove the WIP tag, CI is not kicked off. Is this being tracked somehow?
jyellick (Tue, 01 May 2018 15:24:57 GMT):
@rameshthoomu @jwagantall When I modify a commit message to remove the WIP tag, CI is not kicked off. Is this being tracked somehow / slated to be fixed?
jyellick (Tue, 01 May 2018 15:26:18 GMT):
Will commenting `VerifyBuild` do everything I need? Or do I need to also include each of the `Run
jyellick (Tue, 01 May 2018 15:32:38 GMT):
(To answer my own question, it looks like `VerifyBuild` is re-running the whole CI)
jtclark (Tue, 01 May 2018 15:42:21 GMT):
@rjones - ping
jtclark (Tue, 01 May 2018 15:42:38 GMT):
saw your comment... what is meant by draft?
rjones (Tue, 01 May 2018 15:44:07 GMT):
look in the upper left corner: https://gerrit.hyperledger.org/r/#/c/20681/
rjones (Tue, 01 May 2018 15:44:44 GMT):
`Change 20681 - Draft`
jtclark (Tue, 01 May 2018 15:49:54 GMT):
ah.
jtclark (Tue, 01 May 2018 15:49:58 GMT):
I just hit publish
jtclark (Tue, 01 May 2018 15:50:01 GMT):
does that fix things?
rjones (Tue, 01 May 2018 15:51:02 GMT):
yup. in the queue
jtclark (Tue, 01 May 2018 15:51:29 GMT):
:thumbsup:
sambhavdutt (Tue, 01 May 2018 15:55:56 GMT):
@jyellick
yes, like you said `VerifyBuild` will trigger all builds that includes smoke tests, unit tests, and docs build , depending on what the patchset conatains,
for e.g. if it is a documentation job without any other changes ` .rst, .md, .py, .png,.css,.html .ini ` , the docs-build job will trigger
jwagantall (Tue, 01 May 2018 16:03:51 GMT):
@rjones thanks a lot .. i will leave it disabled.. should be disabled
rjones (Tue, 01 May 2018 16:04:37 GMT):
@jwagantall I basically mis-configured the gerrit trigger, so it should be some effort for it to get re-enabled
jwagantall (Tue, 01 May 2018 16:05:25 GMT):
thnak you .. also .. let me double check our setting files ... they should be just dummy ones.. except for some configuration (non-credentials) ones we have
rjones (Tue, 01 May 2018 16:09:29 GMT):
I feel that since testing this new workflow is over, the gerrit trigger config could be deleted completely from sandbox. But that is just a feeling.
kostas (Tue, 01 May 2018 16:17:17 GMT):
> yes, like you said `VerifyBuild` will trigger all builds that includes smoke tests, unit tests, and docs build , depending on what the patchset conatains
Is this documented anywhere?
jwagantall (Tue, 01 May 2018 16:49:04 GMT):
@kostas Ramesh has been working on a lot of documentation here: https://gerrit.hyperledger.org/r/#/c/20307/ This change just needs Sphinx corrections and should be ok to go..
rameshthoomu (Tue, 01 May 2018 16:59:19 GMT):
@jyellick I am on leave today.. got some time to check messages.. Jobs won’t trigger for a commit message change.. that means build won’t trigger if you remove WIP from Commit message
rameshthoomu (Tue, 01 May 2018 17:00:35 GMT):
@sambhavdutt VerifyBuild comment won’t trigger all the jobs. It just trigger the VerifyBuild job and it further triggers rest of the jobs based on the condition match..
rameshthoomu (Tue, 01 May 2018 17:01:00 GMT):
Pls refer documentation if you need any clarity
jtclark (Tue, 01 May 2018 17:18:08 GMT):
either of you know what the coala failures are?
jtclark (Tue, 01 May 2018 17:18:10 GMT):
```
jtclark (Tue, 01 May 2018 17:18:10 GMT):
```
00:02:06.184 ERROR: invocation failed (exit code 1), logfile: /w/workspace/ci-management-tox-verify-master/.tox/coala/log/coala-5.log
```
jtclark (Tue, 01 May 2018 17:20:12 GMT):
@rjones, @jwagantall, @sambhavdutt :point_up_tone2:
jtclark (Tue, 01 May 2018 17:20:29 GMT):
and it this the reason behind this failure: https://jenkins.hyperledger.org/job/ci-management-tox-verify-master/1047/
jtclark (Tue, 01 May 2018 17:20:29 GMT):
and is this the reason behind this failure: https://jenkins.hyperledger.org/job/ci-management-tox-verify-master/1047/
jwagantall (Tue, 01 May 2018 17:21:52 GMT):
let me check @jtclark
jwagantall (Tue, 01 May 2018 17:22:34 GMT):
@jtclark take a look a little bit further.. you will see the actual failure:
jwagantall (Tue, 01 May 2018 17:22:35 GMT):
15:55:23 jjb/fabric-ca/include-raw-safesql-scan.sh
15:55:23 | 8| cd·$FABRIC_CA_ROOT_DIR
15:55:23 | | [NORMAL] ShellCheckBear:
15:55:23 | | Use 'cd ... || exit' or 'cd ... || return' in case cd fails. [SC2164]
15:55:23 Executing section cli...
jtclark (Tue, 01 May 2018 17:22:49 GMT):
ah
jtclark (Tue, 01 May 2018 17:22:58 GMT):
looking...
jwagantall (Tue, 01 May 2018 17:23:01 GMT):
i recommend running tox locally in your machine so that you dont have to wait for Jenkins to throw any new errors
jwagantall (Tue, 01 May 2018 17:23:24 GMT):
make sure you have the latest HEAD of ci-management if you do so, since that has the latest tox configuration
jtclark (Tue, 01 May 2018 17:23:47 GMT):
ok
jtclark (Tue, 01 May 2018 17:23:52 GMT):
I'll try that.
jtclark (Tue, 01 May 2018 17:53:03 GMT):
@rjones - is this what you disabled?
jtclark (Tue, 01 May 2018 17:53:08 GMT):
```
com.jcraft.jsch.JSchException: java.net.UnknownHostException: gerrit-disable.hyperledger.org
```
jtclark (Tue, 01 May 2018 17:53:30 GMT):
trying to trigger a job on the sandbox using a patch that I submitted
jtclark (Tue, 01 May 2018 18:08:56 GMT):
@jwagantall :point_up_tone2: same question
rjones (Tue, 01 May 2018 18:10:14 GMT):
@jtclark gerrit trigger in sandbox is disabled
jwagantall (Tue, 01 May 2018 18:11:17 GMT):
@jtclark this is becuase the sandbox should not be making any kind of posts back into Gerrit..
jwagantall (Tue, 01 May 2018 18:11:34 GMT):
and vice versa
jtclark (Tue, 01 May 2018 18:12:20 GMT):
what is the recommended way of testing jenkins jobs
jtclark (Tue, 01 May 2018 18:13:20 GMT):
if there is a job that we've made changes too (which we have) what should we do to ensure that it will run w/o error on the Jenkins prod system? I understand why we've disabled it, but what's the alternative?
jtclark (Tue, 01 May 2018 18:13:20 GMT):
if there is a job that we've made changes to (which we have) what should we do to ensure that it will run w/o error on the Jenkins prod system? I understand why we've disabled it, but what's the alternative?
jtclark (Tue, 01 May 2018 18:13:48 GMT):
@rjones, @jwagantall :point_up_tone2:
jwagantall (Tue, 01 May 2018 18:14:52 GMT):
Which is the job that you are tying to test? @jtclark .. You can still use the manual triggers
jtclark (Tue, 01 May 2018 18:15:10 GMT):
fabric-test-daily
jtclark (Tue, 01 May 2018 18:15:27 GMT):
https://jenkins.hyperledger.org/sandbox/job/fabric-test-daily-x86_64/
jtclark (Tue, 01 May 2018 18:15:33 GMT):
but I want to test my patch
jtclark (Tue, 01 May 2018 18:15:50 GMT):
https://gerrit.hyperledger.org/r/#/c/19755/
jwagantall (Tue, 01 May 2018 18:17:56 GMT):
@jtclark Can you try running it manually .. via https://jenkins.hyperledger.org/sandbox/job/fabric-test-daily-x86_64/build?delay=0sec you will need to fill out the GERRIT_REFSPEC parameter with your change
jwagantall (Tue, 01 May 2018 18:18:15 GMT):
refs/changes/55/19755/13
jtclark (Tue, 01 May 2018 18:18:32 GMT):
ok
sambhavdutt (Tue, 01 May 2018 18:58:45 GMT):
@manish-sethi
https://gerrit.hyperledger.org/r/#/c/14355/, https://gerrit.hyperledger.org/r/#/c/14511/
have passed the verify tests now that the patchsets are triggered with the latest commit
manish-sethi (Tue, 01 May 2018 18:59:22 GMT):
yes, thanks @sambhavdutt
bretharrison (Tue, 01 May 2018 19:29:35 GMT):
Any idea why the cloning on S390 is taking so long
```
17:20:16 Cloning into '/w/workspace/fabric-sdk-node8-verify-s390x/gopath/src/github.com/hyperledger/fabric'...
17:35:33 ----->
17:35:33 -----> master
17:35:33 =======> FABRIC_COMMIT <======= d9a207c
```
davidkhala (Wed, 02 May 2018 08:04:27 GMT):
I saw cli keep falling with that error, which would not appear on my local machine when running node-sdk:`gulp test `
`
06:26:19 not ok 1527 failed check for exists on install again
06:26:19 ---
06:26:19 operator: fail
06:26:19 at: installChaincode.then (/w/workspace/fabric-sdk-node8-verify-x86_64/gopath/src/github.com/hyperledger/fabric-sdk-node/test/integration/install.js:84:9)
06:26:19 stack: |-
06:26:19 Error: failed check for exists on install again
06:26:19 at Test.assert [as _assert] (/w/workspace/fabric-sdk-node8-verify-x86_64/gopath/src/github.com/hyperledger/fabric-sdk-node/node_modules/tape/lib/test.js:225:54)
06:26:19 at Test.bound [as _assert] (/w/workspace/fabric-sdk-node8-verify-x86_64/gopath/src/github.com/hyperledger/fabric-sdk-node/node_modules/tape/lib/test.js:77:32)
06:26:19 at Test.fail (/w/workspace/fabric-sdk-node8-verify-x86_64/gopath/src/github.com/hyperledger/fabric-sdk-node/node_modules/tape/lib/test.js:318:10)
06:26:19 at Test.bound [as fail] (/w/workspace/fabric-sdk-node8-verify-x86_64/gopath/src/github.com/hyperledger/fabric-sdk-node/node_modules/tape/lib/test.js:77:32)
06:26:19 at installChaincode.then (/w/workspace/fabric-sdk-node8-verify-x86_64/gopath/src/github.com/hyperledger/fabric-sdk-node/test/integration/install.js:84:9)
06:26:19 at
davidkhala (Wed, 02 May 2018 08:04:27 GMT):
I saw cli keep falling with that error, which would not appear on my local machine when running node-sdk:``gulp test ``
```
06:26:19 not ok 1527 failed check for exists on install again
06:26:19 ---
06:26:19 operator: fail
06:26:19 at: installChaincode.then (/w/workspace/fabric-sdk-node8-verify-x86_64/gopath/src/github.com/hyperledger/fabric-sdk-node/test/integration/install.js:84:9)
06:26:19 stack: |-
06:26:19 Error: failed check for exists on install again
06:26:19 at Test.assert [as _assert] (/w/workspace/fabric-sdk-node8-verify-x86_64/gopath/src/github.com/hyperledger/fabric-sdk-node/node_modules/tape/lib/test.js:225:54)
06:26:19 at Test.bound [as _assert] (/w/workspace/fabric-sdk-node8-verify-x86_64/gopath/src/github.com/hyperledger/fabric-sdk-node/node_modules/tape/lib/test.js:77:32)
06:26:19 at Test.fail (/w/workspace/fabric-sdk-node8-verify-x86_64/gopath/src/github.com/hyperledger/fabric-sdk-node/node_modules/tape/lib/test.js:318:10)
06:26:19 at Test.bound [as fail] (/w/workspace/fabric-sdk-node8-verify-x86_64/gopath/src/github.com/hyperledger/fabric-sdk-node/node_modules/tape/lib/test.js:77:32)
06:26:19 at installChaincode.then (/w/workspace/fabric-sdk-node8-verify-x86_64/gopath/src/github.com/hyperledger/fabric-sdk-node/test/integration/install.js:84:9)
06:26:19 at
cbf (Wed, 02 May 2018 13:47:52 GMT):
hi @rameshthoomu are you back?
cbf (Wed, 02 May 2018 13:48:27 GMT):
I think that there was a CI job that needed to be updated to allow https://gerrit.hyperledger.org/r/c/20853/ to be merged
cbf (Wed, 02 May 2018 13:48:58 GMT):
also, what about publishing the multi-arch manifest for v1.1.0? should I work with @jwagantall ?
rameshthoomu (Wed, 02 May 2018 14:08:50 GMT):
@cbf yes.. I made changes in sandbox... If I update CI config without this patch merge, all builds will fail.. It's better to merge based on the sandbox changes and then update CI config..
rameshthoomu (Wed, 02 May 2018 14:09:04 GMT):
I am looking in unit-test failures. Give me few mins..
cbf (Wed, 02 May 2018 14:25:26 GMT):
ok thanks
rameshthoomu (Wed, 02 May 2018 14:29:42 GMT):
@cbf few unit-tests are still referring 0.4.7 baseos.. Why these are referring to 0.4.7 on this commit.
```
00:06:33.890 unit-tests_1 | 2018-05-01 15:47:23.340 UTC [chaincode-platform] generateDockerfile -> DEBU 3a3
00:06:33.891 unit-tests_1 | FROM hyperledger/fabric-baseos:amd64-0.4.7
00:06:33.891 unit-tests_1 | ADD binpackage.tar /usr/local/bin
```
cbf (Wed, 02 May 2018 14:38:19 GMT):
ah, found the culprit... the baseimage is now hard-coded in the metadata
cbf (Wed, 02 May 2018 14:38:26 GMT):
uploading a fix
jtclark (Wed, 02 May 2018 14:53:33 GMT):
@rameshthoomu hi. welcome back :-)
jtclark (Wed, 02 May 2018 14:53:44 GMT):
Can you re-review this patch: https://gerrit.hyperledger.org/r/#/c/20681/ ?
rameshthoomu (Wed, 02 May 2018 14:54:53 GMT):
LGTM.. Did you run this change in sandbox..?
jtclark (Wed, 02 May 2018 14:55:20 GMT):
awhile back, yes.
jtclark (Wed, 02 May 2018 14:55:44 GMT):
the output shows the report
jtclark (Wed, 02 May 2018 14:56:01 GMT):
and there was some conversation about the weekly scan job stuff
jtclark (Wed, 02 May 2018 14:56:22 GMT):
but to answer your question, yes I did and it worked
cbf (Wed, 02 May 2018 14:57:17 GMT):
@rameshthoomu uploaded the fix
jtclark (Wed, 02 May 2018 15:18:06 GMT):
@rameshthoomu any chance of getting this one merged today?
cbf (Wed, 02 May 2018 15:23:26 GMT):
@rameshthoomu now failing smoke test - sigh
cbf (Wed, 02 May 2018 15:23:38 GMT):
this appears to be same as before
cbf (Wed, 02 May 2018 15:23:38 GMT):
this appears to be same error as before
rameshthoomu (Wed, 02 May 2018 15:25:35 GMT):
yes.. Will take care of that now..
rjones (Wed, 02 May 2018 15:25:52 GMT):
```2018-05-02 15:13:57.670 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 002 Using default vscc
Error: Error endorsing chaincode: rpc error: code = Unknown desc = error starting container: Failed to generate platform-specific docker build: Failed to pull hyperledger/fabric-ccenv:amd64-1.2.0-snapshot-a20555e: API error (404): manifest for hyperledger/fabric-ccenv:amd64-1.2.0-snapshot-a20555e not found
!!!!!!!!!!!!!!! Chaincode instantiation on peer0.org2 on channel 'mychannel' failed !!!!!!!!!!!!!!!!
========= ERROR !!! FAILED to execute End-2-End Scenario ===========
```
rjones (Wed, 02 May 2018 15:26:26 GMT):
@cbf @rameshthoomu ^^^
cbf (Wed, 02 May 2018 15:26:40 GMT):
right
cbf (Wed, 02 May 2018 15:26:46 GMT):
that is same failure as before
rameshthoomu (Wed, 02 May 2018 15:26:51 GMT):
yes
rameshthoomu (Wed, 02 May 2018 15:50:21 GMT):
Sending votes between sandbox and production env is removed.. So I can't send +1 to patch set but the smoke tests are passed https://jenkins.hyperledger.org/sandbox/job/fabric-smoke-tests-x86_64/
rameshthoomu (Wed, 02 May 2018 16:15:03 GMT):
@jtclark Can I see the safesql log from sandbox?
jtclark (Wed, 02 May 2018 16:15:20 GMT):
@rameshthoomu I'll have to add that job back I think
jtclark (Wed, 02 May 2018 16:15:24 GMT):
it's been removed
jtclark (Wed, 02 May 2018 16:15:37 GMT):
let me look
jtclark (Wed, 02 May 2018 16:16:04 GMT):
yes, it's been removed. I'll add it back
rameshthoomu (Wed, 02 May 2018 16:16:32 GMT):
sure. let me once done. I have removed -2 from your patchset.. Will get it merge today..
jtclark (Wed, 02 May 2018 16:18:18 GMT):
saw that. thanks. I'll add it back after lunch
jtclark (Wed, 02 May 2018 16:18:46 GMT):
next on my list is FAB-8501. FYI.
cbf (Wed, 02 May 2018 17:08:31 GMT):
Ok, how about unit tests then? @rameshthoomu I can manually vote
rameshthoomu (Wed, 02 May 2018 17:33:11 GMT):
I ran twice in sandbox.. failed twice https://jenkins.hyperledger.org/sandbox/job/fabric-verify-unit-tests-x86_64/2/consoleFull
cbf (Wed, 02 May 2018 17:34:46 GMT):
I don't see this as related
rjones (Wed, 02 May 2018 18:28:55 GMT):
@rameshthoomu if you link to the shipped logs on https://logs... it's faster and puts less load on Jenkins :)
rameshthoomu (Wed, 02 May 2018 18:29:36 GMT):
ya... forgot to take that as a reference..
cbf (Wed, 02 May 2018 19:54:54 GMT):
@rameshthoomu I ran the CR https://gerrit.hyperledger.org/r/c/20853/ locally and it runs fine...
cbf (Wed, 02 May 2018 19:55:06 GMT):
shall we merge and merge the CI changes?
rameshthoomu (Wed, 02 May 2018 19:56:21 GMT):
Yes.. that's sounds like a good plan.
rameshthoomu (Wed, 02 May 2018 19:56:28 GMT):
Will submit changes.
cbf (Wed, 02 May 2018 19:57:50 GMT):
let's coordinate on this... I need to get others to help us merge my CR
rameshthoomu (Wed, 02 May 2018 19:58:20 GMT):
sure.. Will submit patch to CI now.. and will merge this after your CR is approved
jtclark (Wed, 02 May 2018 20:07:53 GMT):
@rameshthoomu the job is back on the sandbox
jtclark (Wed, 02 May 2018 20:08:12 GMT):
I'm running it using the refs/changes/95/20695/2 ref from the fabric_ca repo
rameshthoomu (Wed, 02 May 2018 20:59:12 GMT):
I have pushed CI config change.. https://gerrit.hyperledger.org/r/#/c/21339/
rameshthoomu (Wed, 02 May 2018 21:01:17 GMT):
both fabric and CI changes should go hand in hand..
rameshthoomu (Wed, 02 May 2018 21:11:28 GMT):
@jtclark Did you run this change in sandbox https://gerrit.hyperledger.org/r/#/c/19755/
jtclark (Wed, 02 May 2018 21:11:57 GMT):
yes, we have
jtclark (Wed, 02 May 2018 21:12:39 GMT):
@rameshthoomu https://jenkins.hyperledger.org/sandbox/job/fabric-test-daily-x86_64/2/
rameshthoomu (Wed, 02 May 2018 21:12:46 GMT):
ok
rameshthoomu (Wed, 02 May 2018 21:15:03 GMT):
How did it run?
rameshthoomu (Wed, 02 May 2018 21:17:35 GMT):
ok Safesql is in.. I just merged it..
rameshthoomu (Wed, 02 May 2018 21:17:44 GMT):
let me know the PTE test results..
rameshthoomu (Wed, 02 May 2018 21:17:53 GMT):
from sandbox job
jtclark (Wed, 02 May 2018 21:24:43 GMT):
PTE needs to be ran once more
jtclark (Wed, 02 May 2018 21:24:47 GMT):
in the sandbox
jtclark (Wed, 02 May 2018 21:25:06 GMT):
@scottz identified that perhaps the submodules were not updated
jtclark (Wed, 02 May 2018 21:25:20 GMT):
and with the git-latest change that was just merged
jtclark (Wed, 02 May 2018 21:25:24 GMT):
I should re-run it again
jtclark (Wed, 02 May 2018 21:25:32 GMT):
to ensure that the underlying repos are updated
jtclark (Wed, 02 May 2018 21:25:48 GMT):
@rameshthoomu :point_up_tone2:
jtclark (Wed, 02 May 2018 21:26:21 GMT):
this was from @scottz: "The jenkins job runs git-init but not the git-latest to update the submodules, so he is pushing a fix today and will let you know when done so you can kick off your test again."
jtclark (Wed, 02 May 2018 21:26:55 GMT):
so I think I should test it once more just to be sure
rameshthoomu (Wed, 02 May 2018 21:30:53 GMT):
@jtclark @scottz Issue is not with the submodules.. There is an error with grpc module error.. see the bug here https://jira.hyperledger.org/browse/FAB-9828
jtclark (Wed, 02 May 2018 21:31:06 GMT):
oh ok
rameshthoomu (Wed, 02 May 2018 21:31:31 GMT):
@jtclark but you can run these tests with an workaround.. `npm install grpc@1.10.1`
jtclark (Wed, 02 May 2018 21:31:57 GMT):
ok
rameshthoomu (Wed, 02 May 2018 21:32:00 GMT):
Please run this command after you do `npm install` from daily or smoke test suite..
rameshthoomu (Wed, 02 May 2018 21:32:23 GMT):
Will merge your patch based on the sandbox test results..
jtclark (Wed, 02 May 2018 21:32:26 GMT):
ok
jtclark (Wed, 02 May 2018 21:32:29 GMT):
one sec
jtclark (Wed, 02 May 2018 21:33:51 GMT):
@rameshthoomu - see my comment: https://gerrit.hyperledger.org/r/#/c/19755/
jtclark (Wed, 02 May 2018 21:34:04 GMT):
that's what you mean, correct?
rameshthoomu (Wed, 02 May 2018 21:35:03 GMT):
ommm.. Not in the patchset.. this is just a workaround step.. Run this in sandbox
jtclark (Wed, 02 May 2018 21:35:42 GMT):
ok
rameshthoomu (Wed, 02 May 2018 21:41:21 GMT):
@sambhavdutt @jtclark please list of issues in open status https://jira.hyperledger.org/issues/?filter=11500
rameshthoomu (Wed, 02 May 2018 21:42:45 GMT):
There are so many tasks are in open status.. Please check and assign it to your self if you have bandwidth
jtclark (Wed, 02 May 2018 21:44:13 GMT):
I'll do that now, @rameshthoomu
rameshthoomu (Wed, 02 May 2018 21:46:21 GMT):
Thanks.. will talk about the these tomorrow..
jtclark (Wed, 02 May 2018 21:46:24 GMT):
sure.
jtclark (Wed, 02 May 2018 21:46:28 GMT):
I grabbed 3 just now.
rameshthoomu (Wed, 02 May 2018 21:46:37 GMT):
can you show me what are those?
jtclark (Wed, 02 May 2018 21:46:41 GMT):
sure.
jtclark (Wed, 02 May 2018 21:46:56 GMT):
4945
jtclark (Wed, 02 May 2018 21:47:08 GMT):
6730
jtclark (Wed, 02 May 2018 21:47:16 GMT):
6394
scottz (Wed, 02 May 2018 21:47:38 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=ktsuADnz3HAMjchG2) @rameshthoomu That makes sense. Not sure why that did not occur to me.
scottz (Wed, 02 May 2018 21:48:51 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=pJPYXy4pjojw2ssYi) @rameshthoomu Are you suggesting we should merge jtclark's update even if 9828 is not fixed yet???
rameshthoomu (Wed, 02 May 2018 21:49:23 GMT):
This is the priority one https://jira.hyperledger.org/browse/FAB-9323
jtclark (Wed, 02 May 2018 21:53:28 GMT):
cool. that's next for me.
rameshthoomu (Wed, 02 May 2018 21:58:43 GMT):
@jtclark Please take 9323 first
rameshthoomu (Wed, 02 May 2018 21:58:47 GMT):
thanks
jtclark (Wed, 02 May 2018 22:16:46 GMT):
sure, np.
kevin-s-wang (Thu, 03 May 2018 02:34:47 GMT):
Has joined the channel.
davidkhala (Thu, 03 May 2018 06:43:27 GMT):
@rameshthoomu has CI recovered?
rameshthoomu (Thu, 03 May 2018 12:22:28 GMT):
@davidkhala did you see any issue?
binhn (Thu, 03 May 2018 13:13:45 GMT):
Has left the channel.
rameshthoomu (Thu, 03 May 2018 14:39:00 GMT):
@bretharrison could you please push this change to release-1.0 and release-1.1 branches https://gerrit.hyperledger.org/r/#/c/21021/11/fabric-client/package.json
rameshthoomu (Thu, 03 May 2018 14:39:24 GMT):
I see e2e tests are failing in above branches..
manish-sethi (Thu, 03 May 2018 16:23:39 GMT):
@rameshthoomu - for the CR https://gerrit.hyperledger.org/r/#/c/21385/ from @aso, build does not kick off..
manish-sethi (Thu, 03 May 2018 16:23:50 GMT):
Can you please have a look
rameshthoomu (Thu, 03 May 2018 16:24:16 GMT):
@manish-sethi seems x86_64 nodes went offline.
rameshthoomu (Thu, 03 May 2018 16:24:21 GMT):
all builds are in queue
manish-sethi (Thu, 03 May 2018 16:24:28 GMT):
OK, sure. thanks
rameshthoomu (Thu, 03 May 2018 16:27:08 GMT):
@jwagantall could you please check
rjones (Thu, 03 May 2018 16:40:59 GMT):
@rameshthoomu I see nodes being spawned and builds running
rjones (Thu, 03 May 2018 16:42:08 GMT):
@rameshthoomu can you see https://jenkins.hyperledger.org/cloud-stats/ ?
rameshthoomu (Thu, 03 May 2018 16:42:43 GMT):
Yes.. they are in action now.
rjones (Thu, 03 May 2018 16:43:00 GMT):
scroll down on cloud-stats page
rameshthoomu (Thu, 03 May 2018 16:43:38 GMT):
Oh no. I don’t have access to this
rjones (Thu, 03 May 2018 16:44:09 GMT):
ok. there was some turbulence earlier. I see that it's up against the minion limit right now.
rjones (Thu, 03 May 2018 16:44:48 GMT):
```Error
Instance cap of Cattle is now reached: 45```
rameshthoomu (Thu, 03 May 2018 16:45:32 GMT):
Ok
rjones (Thu, 03 May 2018 16:46:03 GMT):
@jwagantall it looks like HYP CI cloud needs cleaned up for orphans
rjones (Thu, 03 May 2018 16:47:57 GMT):
@jwagantall I boosted the minion limit. Now this error: ```Error
Failed to boot server ubuntu1604-x86_64-4c-16g-7622: status=ERROR vmState=error fault=500: No valid host was found. There are not enough hosts available. (null)```
rjones (Thu, 03 May 2018 16:52:47 GMT):
@rameshthoomu @jwagantall please join the IRC channel https://www.irccloud.com/irc/freenode/channel/lf-releng if you want more information
rjones (Thu, 03 May 2018 16:53:51 GMT):
You can of course use whatever client you want, I use IRC cloud
rameshthoomu (Thu, 03 May 2018 17:04:13 GMT):
Waiting for email confirmation
rjones (Thu, 03 May 2018 17:04:34 GMT):
@rameshthoomu the core of the issue is uninteresting but one of the plugins we rely on for openstack only supports v1 of an API. an upgrade of openstack caused v1 to be disabled.
rjones (Thu, 03 May 2018 17:06:25 GMT):
HYPCI.png
jwagantall (Thu, 03 May 2018 17:46:51 GMT):
thanks @rjones for jumping in... will keep an eye on Jenkins to make sure it does not halt again
rameshthoomu (Thu, 03 May 2018 18:39:49 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=8arHKN9v2cSKQ27Yr) @sambhavdutt please create two Highest bugs in JIRA for these two issues and assign it to @bretharrison
rameshthoomu (Thu, 03 May 2018 18:40:45 GMT):
please mention FAB-9828 in those two new issues..
sambhavdutt (Thu, 03 May 2018 18:51:25 GMT):
yes, will do
jtclark (Thu, 03 May 2018 20:34:52 GMT):
@rameshthoomu I commented out the all the other tests
jtclark (Thu, 03 May 2018 20:34:58 GMT):
and re-ran the job on the sandbox
cbf (Thu, 03 May 2018 20:47:13 GMT):
https://chat.hyperledger.org/channel/fabric-maintainers?msg=8K9fCYoDHYHhyhDot
rameshthoomu (Thu, 03 May 2018 21:00:02 GMT):
@cbf patch is ready for CI
jtclark (Thu, 03 May 2018 21:13:15 GMT):
@rameshthoomu test is stalled: https://jenkins.hyperledger.org/sandbox/job/fabric-test-daily-x86_64/5/console
jtclark (Thu, 03 May 2018 21:13:19 GMT):
:-(
jtclark (Thu, 03 May 2018 21:23:59 GMT):
@rameshthoomu, @scottz - however, I do see results: https://jenkins.hyperledger.org/sandbox/job/fabric-test-daily-x86_64/5/artifact/gopath/src/github.com/hyperledger/fabric-test/fabric-sdk-node/test/PTE/CITest/Logs/FAB-3832-4i_0503205948.log
jtclark (Thu, 03 May 2018 21:25:57 GMT):
https://jenkins.hyperledger.org/sandbox/job/fabric-test-daily-x86_64/5/artifact/gopath/src/github.com/hyperledger/fabric-test/fabric-sdk-node/test/PTE/CITest/Logs/FAB-3834-4q_0503212106.log
rameshthoomu (Thu, 03 May 2018 21:26:08 GMT):
Nice to see the TPS from daily test run.. What is the expected time to finish the first test?
jtclark (Thu, 03 May 2018 21:26:47 GMT):
can tell how long it took. I cancelled it b/c I thought it was stalled
jtclark (Thu, 03 May 2018 21:26:47 GMT):
can't tell how long it took. I cancelled it b/c I thought it was stalled!
jtclark (Thu, 03 May 2018 21:27:17 GMT):
that's my bad.
jtclark (Thu, 03 May 2018 21:27:25 GMT):
let me just let it run and see what happens
jtclark (Thu, 03 May 2018 21:33:53 GMT):
@rameshthoomu, @scottz - ok, it's running once more. I'll check on it a bit later to see what happens.
rameshthoomu (Thu, 03 May 2018 21:40:06 GMT):
@cbf CI patch is merged..
rameshthoomu (Thu, 03 May 2018 21:40:17 GMT):
Please merge your change
cbf (Thu, 03 May 2018 21:45:40 GMT):
ok, I'm merging now
cbf (Thu, 03 May 2018 21:46:03 GMT):
merged
cbf (Thu, 03 May 2018 21:50:06 GMT):
@jtclark there's a bunch of NaN results... is this expected? Also, what we really need is a dashboard that tracks results over time
jtclark (Thu, 03 May 2018 21:52:25 GMT):
@cbf I see this as well, and I'm not sure that this is expected. RE: dashboard, I agree.
jtclark (Thu, 03 May 2018 21:54:28 GMT):
perhaps @scottz or @dongming can chime in on that
jtclark (Thu, 03 May 2018 21:55:34 GMT):
perhaps killing the job prematurely did this during that job run?
jtclark (Thu, 03 May 2018 21:56:04 GMT):
we'll see if the most recent run (currently running) show us the same results
rameshthoomu (Thu, 03 May 2018 21:58:19 GMT):
@cbf the test only ran PTE and remaining all tests are skipped.. that results NaN..
rameshthoomu (Thu, 03 May 2018 21:59:03 GMT):
@jtclark there is a performance jenkins plugin https://wiki.jenkins.io/display/JENKINS/Performance+Plugin
jtclark (Thu, 03 May 2018 22:01:04 GMT):
@rameshthoomu IIUC the NaNs he is referring to are in the PTE test results log:
jtclark (Thu, 03 May 2018 22:01:04 GMT):
@rameshthoomu IIUC the NaNs @cbf is referring to are in the PTE test results log:
jtclark (Thu, 03 May 2018 22:01:08 GMT):
`[32minfo[39m: [PTE 1 main]: Test Summary[3]: [Nid:chan:org:id=0:testorgschannel1:org2:0 latency_output] pte-exec:completed event latency stats: tx num= 20000, total time: NaN ms, min= 847 ms, max= 5469 ms, avg= NaN ms
`
jtclark (Thu, 03 May 2018 22:01:08 GMT):
```[32minfo[39m: [PTE 1 main]: Test Summary[3]: [Nid:chan:org:id=0:testorgschannel1:org2:0 latency_output] pte-exec:completed event latency stats: tx num= 20000, total time: NaN ms, min= 847 ms, max= 5469 ms, avg= NaN ms
```
rameshthoomu (Thu, 03 May 2018 22:01:23 GMT):
oh ok..
jtclark (Thu, 03 May 2018 22:02:03 GMT):
@rameshthoomu re: plugin - I can look into that. I'll add a JIRA task for it.
rameshthoomu (Thu, 03 May 2018 22:05:12 GMT):
We have one already will give you later
rameshthoomu (Thu, 03 May 2018 22:05:20 GMT):
Or you can search in Jira
jtclark (Thu, 03 May 2018 22:07:17 GMT):
Ok
scottz (Thu, 03 May 2018 22:07:56 GMT):
Glad to hear the PTE test is running; yes the first step was to get a few running and merged into CI. Next step was to use a plugin and track over time. Hopefully Jason can finish that next in short order.
jtclark (Thu, 03 May 2018 22:21:06 GMT):
Took some time to work out the gopath stuff among other things but we’re finally getting there.
jtclark (Thu, 03 May 2018 22:22:17 GMT):
@scottz indeed.
jtclark (Thu, 03 May 2018 22:26:04 GMT):
@scottz any thoughts on the NaN values we’re seeing in the PTE results?
rjones (Thu, 03 May 2018 22:29:00 GMT):
@rameshthoomu @jtclark I looked in the Jenkins plugin manager, and I don't see https://plugins.jenkins.io/performance as available under that name.
scottz (Thu, 03 May 2018 23:18:35 GMT):
@jtclark That PTE Test Summary log was just merged yesterday, so maybe there is an error with it. Looks like the time accumulation didn't go right. Create a bug for @dongming
against the PTE tool. This might be helpful: https://stackoverflow.com/questions/14422207/object-returning-nan-when-sum-values
jtclark (Fri, 04 May 2018 00:04:56 GMT):
Fair enough.
jtclark (Fri, 04 May 2018 00:05:47 GMT):
At this point I’d like to go ahead and submit the final patchset for FAB-5283
jtclark (Fri, 04 May 2018 00:06:11 GMT):
I think it’s basically ready now.
jtclark (Fri, 04 May 2018 00:59:58 GMT):
@rameshthoomu, @scottz, @rjones - new patchset is ready: https://gerrit.hyperledger.org/r/#/c/19755/
rjones (Fri, 04 May 2018 01:01:29 GMT):
@jtclark OK - not sure I can help with it
jtclark (Fri, 04 May 2018 01:01:42 GMT):
no worries. sry 2 bother
jtclark (Fri, 04 May 2018 01:03:09 GMT):
Results from the most recent PTE tests ran from the sandbox job: https://jenkins.hyperledger.org/sandbox/job/fabric-test-daily-x86_64/6/
rameshthoomu (Fri, 04 May 2018 01:03:30 GMT):
@jtclark Updated comment.. Pls address
jtclark (Fri, 04 May 2018 01:29:47 GMT):
@rameshthoomu done.
rameshthoomu (Fri, 04 May 2018 01:31:55 GMT):
ok
davidkhala (Fri, 04 May 2018 01:53:04 GMT):
@rameshthoomu problem fixed by bret now. Thanks anyway
rameshthoomu (Fri, 04 May 2018 01:53:44 GMT):
yes.. it's fixed in all the branches..
rameshthoomu (Fri, 04 May 2018 14:17:05 GMT):
Please see the list of open tasks in fabric-ci component https://jira.hyperledger.org/secure/Dashboard.jspa?selectPageId=11417
rameshthoomu (Fri, 04 May 2018 14:17:20 GMT):
Use this dashboard for reference
jtclark (Fri, 04 May 2018 14:19:04 GMT):
Ok
sambhavdutt (Fri, 04 May 2018 14:19:45 GMT):
ok
kostas (Fri, 04 May 2018 22:29:04 GMT):
Any particular reason for failing smoke tests today?
kostas (Fri, 04 May 2018 22:29:11 GMT):
Should I keep re-running that task?
rameshthoomu (Fri, 04 May 2018 23:45:50 GMT):
@kostas could you pls refer the patch set or build number
kostas (Sat, 05 May 2018 12:24:29 GMT):
@rameshthoomu: https://gerrit.hyperledger.org/r/c/21383/
rameshthoomu (Sat, 05 May 2018 12:54:35 GMT):
@kostas pls rebase your patchset. That should work
rselvakct (Sat, 05 May 2018 18:35:38 GMT):
Has joined the channel.
yacovm (Sat, 05 May 2018 19:25:44 GMT):
why, o why this change set https://gerrit.hyperledger.org/r/#/c/21051/ doesn't pass the smoke tests?
```
19:22:31 + docker pull nexus3.hyperledger.org:10003/hyperledger/fabric-peer:073669c
19:22:31 Error response from daemon: manifest for nexus3.hyperledger.org:10003/hyperledger/fabric-peer:073669c not found
19:22:31 + post_Result 1
19:22:31 + '[' 1 '!=' 0 ']'
19:22:31 + vote -m '"Failed"' -l F2-SmokeTest=-1
19:22:31 + ssh -p 29418 hyperledger-jobbuilder@gerrit.hyperledger.org gerrit review 21051,10 --notify '"NONE"' -m '"Failed"' -l F2-SmokeTest=-1
```
yacovm (Sat, 05 May 2018 19:25:56 GMT):
I pulled locally and rebuilt the images and it passes e2e on my machine
yacovm (Sat, 05 May 2018 19:26:05 GMT):
but here it can't even start the environment....
yacovm (Sat, 05 May 2018 19:26:11 GMT):
https://jenkins.hyperledger.org/job/fabric-smoke-tests-x86_64/879/console
yacovm (Sat, 05 May 2018 19:26:16 GMT):
@rameshthoomu any idea?
rameshthoomu (Sat, 05 May 2018 19:27:06 GMT):
Will check
rameshthoomu (Sat, 05 May 2018 20:14:04 GMT):
@yacovm patch#10-11 are rebase and commit message change. so the verify build is not triggered on these patchsets.. Now, when you try to run the smoketests on 10 or 11 patchsets, the build will fail as there are no images published on these commits.
yacovm (Sat, 05 May 2018 20:14:53 GMT):
yeah i figured as much.... that's why i already pushed a new patch set
yacovm (Sat, 05 May 2018 20:15:02 GMT):
took me long enough
rameshthoomu (Sat, 05 May 2018 20:15:04 GMT):
Patch#12 will fix this..
rameshthoomu (Sat, 05 May 2018 20:15:53 GMT):
ok..
yacovm (Sat, 05 May 2018 20:16:32 GMT):
thanks @rameshthoomu
rameshthoomu (Sat, 05 May 2018 20:17:08 GMT):
sure.. took sometime for me to reply.. Was out for lunch.
yacovm (Sat, 05 May 2018 20:17:26 GMT):
np
jtclark (Mon, 07 May 2018 13:16:21 GMT):
Gm all
jtclark (Mon, 07 May 2018 19:51:03 GMT):
@rameshthoomu, @sambhavdutt - got a sec?
jtclark (Mon, 07 May 2018 19:51:11 GMT):
working on FAB-9323
jtclark (Mon, 07 May 2018 19:51:19 GMT):
finishing up the script.....
jtclark (Mon, 07 May 2018 19:52:10 GMT):
here's a gist of what I have so far:
jtclark (Mon, 07 May 2018 19:52:35 GMT):
https://gist.github.com/ibm-jason/d65e8c7ada61152a6c1db4046dd677b3
jtclark (Mon, 07 May 2018 19:53:35 GMT):
I'm working on getting the /bin directory copied from the fabric repo
jtclark (Mon, 07 May 2018 19:53:43 GMT):
but it doesn't exist
jtclark (Mon, 07 May 2018 19:53:52 GMT):
is there something I'm missing from the fabric repo?
jtclark (Mon, 07 May 2018 19:54:29 GMT):
perhaps we can talk more about this tmrw if you guys don't have an idea
jtclark (Mon, 07 May 2018 19:54:29 GMT):
perhaps we can talk more about this tmrw if you guys don't have an idea about this yet
jtclark (Mon, 07 May 2018 19:55:12 GMT):
I can run the script locally, and it goes through the `run_local_build()` function
jtclark (Mon, 07 May 2018 19:55:38 GMT):
which tries to grab all of the important local variables to get BYFN to run w/o error.
sambhavdutt (Mon, 07 May 2018 19:55:44 GMT):
@jtclark will check on this and let you know
jtclark (Mon, 07 May 2018 19:56:29 GMT):
@sambhavdutt yes, just check out what I have, and you can see what I'm doing. I talked about detecting the hostname, so that we can determine if the script is being ran by our Jenkins host(s) or by the developer locally.
jtclark (Mon, 07 May 2018 19:57:51 GMT):
if that doesn't work, the other idea that I had was to have the devs set a local variable to `true` to determine if you are running it locally or not.
jtclark (Mon, 07 May 2018 19:58:43 GMT):
like `LOCAL_DEV=true` or something, but have a look and let me know your thoughts.
jtclark (Mon, 07 May 2018 20:26:54 GMT):
@rameshthoomu, @sambhavdutt - I think that the problem is that there no `fabric/release/linux-amd64/bin/` directory in the master branch
jtclark (Mon, 07 May 2018 20:27:55 GMT):
I think I may have found something.... `fabric_preload.sh`
sambhavdutt (Mon, 07 May 2018 20:27:55 GMT):
@jtclark did you execute a make release, or , make-release all
jtclark (Mon, 07 May 2018 20:28:07 GMT):
in fabric-samples?
sambhavdutt (Mon, 07 May 2018 20:28:44 GMT):
no, scratch that, I meant this for fabric repo
jtclark (Mon, 07 May 2018 20:29:09 GMT):
hmm
jtclark (Mon, 07 May 2018 20:29:11 GMT):
I haven't
hrt031293 (Tue, 08 May 2018 12:26:55 GMT):
Has joined the channel.
kostas (Tue, 08 May 2018 15:49:36 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=p9RL5TomI35Mu8RZbi) @rameshthoomu Unfortunately, it didn't. See: https://gerrit.hyperledger.org/r/c/21383#message-ef7faef7_8039c139
kostas (Tue, 08 May 2018 15:49:51 GMT):
Do we know what's causing the smoke test to fail?
kostas (Tue, 08 May 2018 15:49:51 GMT):
Do we know what's causing the smoke test to fail? /cc @latitiah
rameshthoomu (Tue, 08 May 2018 15:56:16 GMT):
checking
rameshthoomu (Tue, 08 May 2018 16:00:49 GMT):
I see the images are not published for the commit#90ff463
rameshthoomu (Tue, 08 May 2018 22:07:54 GMT):
@sambhavdutt Observed few vulnerbale issues in fabric-chaincode-node builds.. Could you please create a bug for this and push a vulnerable job in CI
rameshthoomu (Tue, 08 May 2018 22:08:33 GMT):
```
00:08:55.624 npm WARN deprecated formatio@1.2.0: This package is unmaintained. Use @sinonjs/formatio instead
00:08:56.074 npm WARN deprecated graceful-fs@3.0.11: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
00:08:56.721 npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
00:08:56.724 npm WARN deprecated natives@1.1.3: This module relies on Node.js's internals and will break at some point. Do not use it, and update to graceful-fs@4.x.
00:08:57.496 npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
00:08:57.785 npm WARN deprecated graceful-fs@1.2.3: please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
00:09:08.448 npm WARN notice [SECURITY] protobufjs has and 1 moderate vulnerability. Go here for more details: https://nodesecurity.io/advisories?search=protobufjs&version=5.0.2 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info.
00:09:10.722 npm WARN notice [SECURITY] minimatch has and 1 high vulnerability. Go here for more details: https://nodesecurity.io/advisories?search=minimatch&version=0.2.14 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info.
00:09:13.063 npm WARN notice [SECURITY] lodash has and 1 low vulnerability. Go here for more details: https://nodesecurity.io/advisories?search=lodash&version=1.0.2 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info.
00:09:13.094 npm WARN notice [SECURITY] minimatch has and 1 high vulnerability. Go here for more details: https://nodesecurity.io/advisories?search=minimatch&version=2.0.10 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info.
```
rjones (Wed, 09 May 2018 20:25:10 GMT):
Has left the channel.
rjones (Thu, 10 May 2018 20:34:18 GMT):
Has joined the channel.
rjones (Thu, 10 May 2018 20:35:42 GMT):
@rameshthoomu I ask you to work with @sykesm and @gennadyl to store some binaries in nexus please see https://gerrit.hyperledger.org/r/#/c/20857/ for context @jwagantall
rjones (Thu, 10 May 2018 20:36:05 GMT):
tyvm
rjones (Thu, 10 May 2018 20:36:47 GMT):
@rameshthoomu @jwagantall I ask you to add "fail first stage of CI if a jar file is checked in" to the fabric CI as well
rjones (Thu, 10 May 2018 20:36:47 GMT):
@rameshthoomu @jwagantall furthermore, I ask you to add "fail first stage of CI if a jar file is checked in" to the fabric CI as well
rameshthoomu (Thu, 10 May 2018 20:39:42 GMT):
ok.. sure.. We store binaries in nexus2 as part of our fabric build https://nexus.hyperledger.org/content/repositories/releases/org/hyperledger/fabric/hyperledger-fabric-build/ I think we will follow the same here..
rameshthoomu (Thu, 10 May 2018 20:39:42 GMT):
ok.. sure.. We store binaries in nexus2 as part of our fabric build https://nexus.hyperledger.org/content/repositories/releases/org/hyperledger/fabric/hyperledger-fabric-build/ will follow the same here..
rjones (Thu, 10 May 2018 20:40:09 GMT):
FAB-10006
rjones (Thu, 10 May 2018 20:40:25 GMT):
OK thank you.
rjones (Thu, 10 May 2018 20:40:34 GMT):
do you want a JIRA for the first ask?
rjones (Thu, 10 May 2018 20:40:34 GMT):
do you want a JIRA for the first request?
rameshthoomu (Thu, 10 May 2018 20:41:05 GMT):
yes pls
rjones (Thu, 10 May 2018 20:42:57 GMT):
FAB-10007
rameshthoomu (Thu, 10 May 2018 21:57:21 GMT):
@jtclark could you please work on 10007 and 10006 JIRA tasks..
jtclark (Thu, 10 May 2018 21:58:32 GMT):
@rameshthoomu ok, will do.
rameshthoomu (Thu, 10 May 2018 21:59:21 GMT):
thanks
gennadyl (Sat, 12 May 2018 19:05:24 GMT):
@rameshthoomu Hi, Ramesh. How I can update ci to ignore extra whitespaces in java file. I updated grpc compiler and now generated file cause problem with build. Here change set:
https://gerrit.hyperledger.org/r/#/c/21495/
rameshthoomu (Sat, 12 May 2018 19:59:03 GMT):
@gennadyl Instead of ignoring white spaces better to fix them.. I see white spaces here https://gerrit.hyperledger.org/r/#/c/21495/3/fabric-chaincode-protos/src/main/grpc/org/hyperledger/fabric/protos/peer/ChaincodeSupportGrpc.java
gennadyl (Sun, 13 May 2018 06:58:28 GMT):
@rameshthoomu This file generated by grpc compiler. each time I run build it regenerated :(
gennadyl (Sun, 13 May 2018 06:59:43 GMT):
btw, did you saw my answer in FAB-10007?
rameshthoomu (Sun, 13 May 2018 14:44:32 GMT):
@jtclark are you working on FAB-10007?
jtclark (Sun, 13 May 2018 14:45:10 GMT):
Haven’t started that one yet. @rameshthoomu
rameshthoomu (Sun, 13 May 2018 14:45:56 GMT):
Could you pls work on that. Patch set is waiting for this change
jtclark (Sun, 13 May 2018 14:46:12 GMT):
Ok sure.
rameshthoomu (Sun, 13 May 2018 14:46:20 GMT):
Thanks
jtclark (Sun, 13 May 2018 14:55:49 GMT):
@rameshthoomu - so I'm creating a jenkins job that will pull the chaincode.jar file from fabric-sdk-java inside the core/chaincode/platforms/java/testdata/SimpleSample directory
jtclark (Sun, 13 May 2018 14:56:35 GMT):
and storing it on nexus2?
jtclark (Sun, 13 May 2018 14:58:15 GMT):
@rameshthoomu - will this job be manually triggered? or, do we want this to run daily? weekly?
jtclark (Sun, 13 May 2018 14:58:28 GMT):
just need a bit more info.
gennadyl (Sun, 13 May 2018 18:45:52 GMT):
@jtclark No, please don't do it
gennadyl (Sun, 13 May 2018 18:47:17 GMT):
It is not connected to java sdk
Right now in https://gerrit.hyperledger.org/r/#/c/20857/ I have chaincode.jar file
jtclark (Sun, 13 May 2018 18:47:26 GMT):
@gennadyl don't?
gennadyl (Sun, 13 May 2018 18:47:33 GMT):
This jar used for tesing
gennadyl (Sun, 13 May 2018 18:48:25 GMT):
And decision was to keep it in nexus, instead checkin it in each time
jtclark (Sun, 13 May 2018 18:48:27 GMT):
so for FAB-10007 where should the chaincode.jar file come from?
gennadyl (Sun, 13 May 2018 18:48:57 GMT):
Right now you can take it from change set
jtclark (Sun, 13 May 2018 18:49:00 GMT):
what jars and where should the come from
jtclark (Sun, 13 May 2018 18:49:00 GMT):
what jars and where should they come from
gennadyl (Sun, 13 May 2018 18:49:06 GMT):
i mentioned earlier
jtclark (Sun, 13 May 2018 18:49:26 GMT):
ok so for now, we just need to store the chaincode.jar file on nexus
jtclark (Sun, 13 May 2018 18:49:34 GMT):
from your patchset
jtclark (Sun, 13 May 2018 18:50:05 GMT):
but in the future is there a plan to store numerous jars on nexus?
gennadyl (Sun, 13 May 2018 18:50:15 GMT):
yes. And checkout it during ci build to core/chaincode/platforms/java/testdata/SimpleSample directory
gennadyl (Sun, 13 May 2018 18:50:20 GMT):
And yes
gennadyl (Sun, 13 May 2018 18:50:41 GMT):
But there is no build process for it, now it is static
jtclark (Sun, 13 May 2018 18:51:08 GMT):
so.... checkout the jar from your patchset, and store it on the nexus repository.... no building nothing.... correct?
gennadyl (Sun, 13 May 2018 18:51:12 GMT):
and in any case it is not connected to java sdk, but to fabric-chaincode-java
gennadyl (Sun, 13 May 2018 18:51:19 GMT):
yes
jtclark (Sun, 13 May 2018 18:51:25 GMT):
gotcha
jtclark (Sun, 13 May 2018 18:51:35 GMT):
fabric-chaincode-java not the sdk
jtclark (Sun, 13 May 2018 18:51:38 GMT):
ok
jtclark (Sun, 13 May 2018 18:51:50 GMT):
I'll create something on the sandbox
jtclark (Sun, 13 May 2018 18:51:52 GMT):
and test it
jtclark (Sun, 13 May 2018 18:52:13 GMT):
then submit it to be merged so that this job will be on the Jenkins prod host
gennadyl (Sun, 13 May 2018 18:52:14 GMT):
No need to test jar itself, it used for fabric testing
jtclark (Sun, 13 May 2018 18:52:21 GMT):
ok
gennadyl (Sun, 13 May 2018 18:53:37 GMT):
After you will store it in nexus, I will remove it from my changeset and will be able to merge it, finally
jtclark (Sun, 13 May 2018 18:53:56 GMT):
gotcha.
jtclark (Sun, 13 May 2018 18:54:08 GMT):
actually, do we even need a job for this?
jtclark (Sun, 13 May 2018 18:54:17 GMT):
for this temporary solution?
gennadyl (Sun, 13 May 2018 18:55:19 GMT):
We don't need job to build jar file, for sure. It is totally static at this point
gennadyl (Sun, 13 May 2018 18:56:05 GMT):
But I have one question, if you have a minute
gennadyl (Sun, 13 May 2018 18:57:11 GMT):
I need this jar be placed in specific location during fabric ci build, for unit tests to succeed
gennadyl (Sun, 13 May 2018 18:57:24 GMT):
How you make it happen?
gennadyl (Sun, 13 May 2018 18:57:24 GMT):
How do you make it happen?
jtclark (Sun, 13 May 2018 18:59:24 GMT):
well, I understand this to be a couple tasks:
jtclark (Sun, 13 May 2018 19:00:06 GMT):
1. for now, we just need to put the jar file that you have on nexus. there's not building needed, we just need to store it on nexus
jtclark (Sun, 13 May 2018 19:00:06 GMT):
1. for now, we just need to put the jar file that you have on nexus. there's no building needed for the jar that's in your patchset, we just need to store it on nexus
jtclark (Sun, 13 May 2018 19:01:20 GMT):
2. the long term, we will need to figure out where that location is
jtclark (Sun, 13 May 2018 19:01:20 GMT):
2. for the long term, we will need to figure out where that location is
jtclark (Sun, 13 May 2018 19:02:00 GMT):
it depends on where it needs to be stored
gennadyl (Sun, 13 May 2018 19:03:12 GMT):
So, now you just store it in nexus. But how I will get it in core/chaincode/platforms/java/testdata/SimpleSample directory during build?
gennadyl (Sun, 13 May 2018 19:03:30 GMT):
I think I miss something here
jtclark (Sun, 13 May 2018 19:06:35 GMT):
we'll have to think about that.
jtclark (Sun, 13 May 2018 19:06:52 GMT):
but let me see if I can get the chaincode.jar file you have in that commit stored on nexus
gennadyl (Sun, 13 May 2018 19:08:04 GMT):
ok
gennadyl (Sun, 13 May 2018 19:13:46 GMT):
keep me posted
jtclark (Sun, 13 May 2018 19:14:53 GMT):
sure thing.
C0rWin (Sun, 13 May 2018 20:44:02 GMT):
@gennadyl why do you still need to store this jar into nexus? IMO this is completely redundant and not need, please see my comments on your CR.
gennadyl (Sun, 13 May 2018 21:25:57 GMT):
@C0rWin - see my reply to your comment. It is real test, but I can cancel it, if you want...
jtclark (Mon, 14 May 2018 01:10:54 GMT):
@gennadyl, @C0rWin - did you come to an agreement on whether or not the .jar needs to be stored on nexus?
davidkhala (Mon, 14 May 2018 01:43:04 GMT):
Dear maintainer,
``
The following files are missing SPDX-License-Identifier headers:
test/integration/e2e/create-channel.js
test/unit/cryptosuite-pkcs11.js
test/unit/hash.js
test/unit/network-config.js
davidkhala (Mon, 14 May 2018 01:52:39 GMT):
I found that now
```
SPDX-License-Identifier: Apache-2.0
```
davidkhala (Mon, 14 May 2018 01:52:39 GMT):
I found that now
```
SPDX-License-Identifier: Apache-2.0
```
is required in changed files in a patch, is it ?
jtclark (Mon, 14 May 2018 02:10:42 GMT):
@davidkhala do you have a failed verification test or something?
jtclark (Mon, 14 May 2018 02:11:09 GMT):
@davidkhala has Jenkins reported a -1 vote on your patchset?
davidkhala (Mon, 14 May 2018 02:11:19 GMT):
yes, but I think I got the idea.
davidkhala (Mon, 14 May 2018 02:11:46 GMT):
the new check-license test has been added to fabric-node-sdk
davidkhala (Mon, 14 May 2018 02:12:02 GMT):
I just used the old test methods
jtclark (Mon, 14 May 2018 02:12:22 GMT):
right. if there's a test for it, then looks like it will have to be added
davidkhala (Mon, 14 May 2018 02:12:47 GMT):
Thanks anyway.
gennadyl (Mon, 14 May 2018 06:12:23 GMT):
@jtclark I assume we were sleeping at this time :)
versus (Mon, 14 May 2018 09:04:17 GMT):
Has joined the channel.
davidkhala (Mon, 14 May 2018 09:22:48 GMT):
Another problem is I found that
```
08:40:42 not ok 1444 should have duration roughly equals 3000
08:40:42 ---
08:40:42 operator: equal
08:40:42 expected: 3
08:40:42 actual: 1
08:40:42 at: timeOutTest (/w/workspace/fabric-sdk-node8-verify-x86_64/gopath/src/github.com/hyperledger/fabric-sdk-node/test/integration/fabric-ca-services-tests.js:441:7)
08:40:42 stack: |-
08:40:42 Error: should have duration roughly equals 3000
08:40:42 at Test.assert [as _assert] (/w/workspace/fabric-sdk-node8-verify-x86_64/gopath/src/github.com/hyperledger/fabric-sdk-node/node_modules/tape/lib/test.js:225:54)
08:40:42 at Test.bound [as _assert] (/w/workspace/fabric-sdk-node8-verify-x86_64/gopath/src/github.com/hyperledger/fabric-sdk-node/node_modules/tape/lib/test.js:77:32)
08:40:42 at Test.equal.Test.equals.Test.isEqual.Test.is.Test.strictEqual.Test.strictEquals (/w/workspace/fabric-sdk-node8-verify-x86_64/gopath/src/github.com/hyperledger/fabric-sdk-node/node_modules/tape/lib/test.js:388:10)
08:40:42 at Test.bound [as equal] (/w/workspace/fabric-sdk-node8-verify-x86_64/gopath/src/github.com/hyperledger/fabric-sdk-node/node_modules/tape/lib/test.js:77:32)
08:40:42 at timeOutTest (/w/workspace/fabric-sdk-node8-verify-x86_64/gopath/src/github.com/hyperledger/fabric-sdk-node/test/integration/fabric-ca-services-tests.js:441:7)
08:40:42 at
jtclark (Mon, 14 May 2018 10:44:54 GMT):
@davidkhala can you provide a link to the failed job?
jtclark (Mon, 14 May 2018 10:46:48 GMT):
@davidkhala I can see it's the fabric-sdk-node8-verify-x86_64 job, but I'd like to know which build attempt we're talking about....
jtclark (Mon, 14 May 2018 10:46:54 GMT):
actually I think I found it: https://jenkins.hyperledger.org/view/fabric-sdk-node/job/fabric-sdk-node8-verify-x86_64/686/
gennadyl (Mon, 14 May 2018 13:13:14 GMT):
@jtclark At this point the agreement is not to same anything in nexus
gennadyl (Mon, 14 May 2018 13:13:29 GMT):
I will remove file
jtclark (Mon, 14 May 2018 13:23:29 GMT):
@gennadyl sounds good.
jtclark (Mon, 14 May 2018 13:23:44 GMT):
@rameshthoomu Good Morning
jtclark (Mon, 14 May 2018 13:23:53 GMT):
sounds like they don't need to have the jar files stored on nexus
jtclark (Mon, 14 May 2018 13:24:26 GMT):
I'll comment and close out on FAB-10007
rameshthoomu (Mon, 14 May 2018 13:24:33 GMT):
sure
jtclark (Mon, 14 May 2018 13:25:42 GMT):
@rameshthoomu, @gennadyl do we still want to fail the job *if* a jar file is checked in?
gennadyl (Mon, 14 May 2018 13:26:11 GMT):
@rameshthoomu Do you remember I asked you about white spaces in automatically generated files
jtclark (Mon, 14 May 2018 13:26:14 GMT):
@rameshthoomu, @gennadyl or do we want to add *.jar to the .gitignore?
gennadyl (Mon, 14 May 2018 13:26:30 GMT):
@jtclark I did removed the jar file from changeset
gennadyl (Mon, 14 May 2018 13:26:52 GMT):
adding it to gitignore sounds like good idea
jtclark (Mon, 14 May 2018 13:26:59 GMT):
@gennadyl +1 sounds good. this is for future patchsets...
jtclark (Mon, 14 May 2018 13:36:03 GMT):
@gennadyl, @rameshthoomu - do either of you mind if I use FAB-10007 to denote that this is what we are going to do to prevent *.jar checkins? (via .gitignore) ?
jtclark (Mon, 14 May 2018 13:36:21 GMT):
I'll submit the change now for review.
gennadyl (Mon, 14 May 2018 13:41:54 GMT):
Ok for me, but I am not maintainer :)
jtclark (Mon, 14 May 2018 13:47:27 GMT):
sounds good. I'll submit it, and see how it goes
jtclark (Mon, 14 May 2018 13:56:02 GMT):
@gennadyl https://gerrit.hyperledger.org/r/#/c/21751/
jtclark (Mon, 14 May 2018 13:56:16 GMT):
who should I add as reviewers?
gennadyl (Mon, 14 May 2018 13:59:10 GMT):
Ramesh, maybe?
jtclark (Mon, 14 May 2018 13:59:38 GMT):
sure, I can add him. I was thinking about fabric-chaincode-java maintainers though. :-)
gennadyl (Mon, 14 May 2018 14:02:30 GMT):
You can add Artem
jtclark (Mon, 14 May 2018 14:03:11 GMT):
Artem Barger ?
jtclark (Mon, 14 May 2018 14:06:48 GMT):
@gennadyl :point_up_tone2:
gennadyl (Mon, 14 May 2018 14:07:07 GMT):
Yes, Artem Barger
gennadyl (Mon, 14 May 2018 14:07:32 GMT):
Sorry, phone and coding not go well together :)
rameshthoomu (Mon, 14 May 2018 14:12:39 GMT):
@jtclark updated comments in the patchset
jtclark (Mon, 14 May 2018 14:12:54 GMT):
got it. I'll take a look now.
jtclark (Mon, 14 May 2018 14:14:20 GMT):
@rameshthoomu I agree. we can still check the verify job to see if a *.jar file is checked in.
jtclark (Mon, 14 May 2018 14:14:20 GMT):
@rameshthoomu I agree. we can still check in the verify job to see if a *.jar file is checked in.
jtclark (Mon, 14 May 2018 14:14:39 GMT):
but this would add an additional safeguard
jtclark (Mon, 14 May 2018 14:16:06 GMT):
if someone forces it in, then we still need to fail the verify job. so, there will be two patches to cover this case. one for the .gitignore and the other for updating the job to check for jar files.
rameshthoomu (Mon, 14 May 2018 14:19:10 GMT):
@gennadyl I think you can follow something similar to this https://github.com/hyperledger/fabric/blob/master/scripts/check_license.sh#L14
gennadyl (Mon, 14 May 2018 14:29:21 GMT):
@rameshthoomu Do you want me to change verify job?
rameshthoomu (Mon, 14 May 2018 14:29:35 GMT):
I am checking
rameshthoomu (Mon, 14 May 2018 14:29:47 GMT):
I think it's ok to ignore `protos` directory
rameshthoomu (Mon, 14 May 2018 14:30:02 GMT):
all the files in this are generated by compiler
rameshthoomu (Mon, 14 May 2018 14:30:26 GMT):
I mean ignore whitespaces
gennadyl (Mon, 14 May 2018 14:31:54 GMT):
Ah, got it. But does fabric-chaincode-java have this kind of verify job
gennadyl (Mon, 14 May 2018 14:32:40 GMT):
?
gennadyl (Mon, 14 May 2018 14:32:56 GMT):
Have to move, ttyl
jtclark (Mon, 14 May 2018 14:36:03 GMT):
@rameshthoomu I updated the patch: https://gerrit.hyperledger.org/r/#/c/21751/
jtclark (Mon, 14 May 2018 14:49:58 GMT):
@rameshthoomu I have another issue. I'm testing https://gerrit.hyperledger.org/r/#/c/21585/ on my vlaunch node, and the networkUp function doesn't work
jtclark (Mon, 14 May 2018 14:50:14 GMT):
I can show you what it does....
jtclark (Mon, 14 May 2018 14:58:18 GMT):
@rameshthoomu https://asciinema.org/a/xZuKm8Cbt5Lf0b9Kdl3Iqfaai
jtclark (Mon, 14 May 2018 15:12:46 GMT):
@rameshthoomu any idea what I might be missing here?
rjones (Mon, 14 May 2018 17:21:39 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=T3ktxnRYFPufYXrEd) @jtclark yes
rameshthoomu (Mon, 14 May 2018 17:37:01 GMT):
https://jenkins.hyperledger.org/view/fabric-sdk-node/job/fabric-sdk-node8-verify-x86_64/680/consoleFull
rameshthoomu (Mon, 14 May 2018 17:38:50 GMT):
@jtclark pushing change to verify .jar file and ignore whitespace on compiler generated files
latitiah (Mon, 14 May 2018 18:10:19 GMT):
This CR: https://gerrit.hyperledger.org/r/#/c/21715/ adds a new make target for executing integration tests
latitiah (Mon, 14 May 2018 18:11:31 GMT):
Note: this executes outside of a docker container because it may dynamically generate docker containers based on the test scenario setup executed.
rameshthoomu (Mon, 14 May 2018 18:14:15 GMT):
@latitiah thanks for the info.. So, I think it's better to add these tests (integration tests) as part of the smoketest build
rameshthoomu (Mon, 14 May 2018 18:14:56 GMT):
I mean parallel to the existing cli & sdk integration tests what we are doing as part of smoke test jobs
rameshthoomu (Mon, 14 May 2018 18:14:56 GMT):
I mean parallel to the existing cli & sdk integration tests what we are doing as part of smoke test job
rameshthoomu (Mon, 14 May 2018 18:14:56 GMT):
I mean parallel to the existing byfn, eyfn tests what we are doing as part of smoke test job
rameshthoomu (Mon, 14 May 2018 18:15:39 GMT):
@sambhavdutt could you please test this change in sandbox and see what are the dependencies
rameshthoomu (Mon, 14 May 2018 18:17:20 GMT):
Create a task in JIRA referring to this https://jira.hyperledger.org/browse/FAB-10017 base work
rameshthoomu (Mon, 14 May 2018 18:23:28 GMT):
@latitiah just curios to know, why these tests are not configured to run inside the container?
jtclark (Mon, 14 May 2018 18:31:22 GMT):
@rjones thanks - I'll add the second patch
jtclark (Mon, 14 May 2018 18:33:45 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=AaFdbGMAoTJCjxFaA) @rameshthoomu do you have the CR link?
latitiah (Mon, 14 May 2018 18:34:11 GMT):
@rameshthoomu The E2E tests may use kafka and zookeeper docker containers. We don't necessarily know what network or how many or the name, config, etc... that each of these containers will have so they are dynamically built based on the specific test scenario. This is not like CouchDB which has a basic setup which doesn't change.
jtclark (Mon, 14 May 2018 18:35:05 GMT):
also, are going to merge https://gerrit.hyperledger.org/r/#/c/21751/ ?
jtclark (Mon, 14 May 2018 18:35:05 GMT):
@ramesh also, are going to merge https://gerrit.hyperledger.org/r/#/c/21751/ ?
jtclark (Mon, 14 May 2018 18:35:05 GMT):
@rameshthoomu also, are going to merge https://gerrit.hyperledger.org/r/#/c/21751/ ?
latitiah (Mon, 14 May 2018 18:36:20 GMT):
@rameshthoomu For most integration tests this won't be an issue but with all tests that use kafka (and thus zookeeper) will be affected since these are docker containers. (With the current setup, you can't run docker containers in docker containers.)
sambhavdutt (Mon, 14 May 2018 18:44:35 GMT):
@latitiah @rameshthoomu
I will run the integration test this in sandbox and let you know..
sambhavdutt (Mon, 14 May 2018 18:44:35 GMT):
@latitiah @rameshthoomu
I will run the integration test in sandbox and let you know..
rameshthoomu (Mon, 14 May 2018 18:48:10 GMT):
yes.. In the current we can't run docker in docker.. and I got your point
jtclark (Mon, 14 May 2018 18:53:55 GMT):
@rameshthoomu do you have the CR link for the *.jar file test?
rameshthoomu (Mon, 14 May 2018 18:59:31 GMT):
https://gerrit.hyperledger.org/r/#/c/21773/
jtclark (Mon, 14 May 2018 19:23:57 GMT):
@rameshthoomu thanks
jtclark (Mon, 14 May 2018 19:46:30 GMT):
@rameshthoomu did you also get a chance to look at https://asciinema.org/a/xZuKm8Cbt5Lf0b9Kdl3Iqfaai ?
jtclark (Mon, 14 May 2018 19:46:48 GMT):
it shows what happens when I run my script for FAB-9323
gennadyl (Mon, 14 May 2018 19:52:12 GMT):
@rameshthoomu Hi Ramesh. Have a minute to talk about this white spaces in java file?
rameshthoomu (Mon, 14 May 2018 19:53:16 GMT):
@gennadyl I am ignoring whitespace using this command `COMMIT_FILES=$(git diff-tree --no-commit-id --name-only -r HEAD | grep -Ev '(^|/)protos/')`
rameshthoomu (Mon, 14 May 2018 19:53:53 GMT):
https://gerrit.hyperledger.org/r/#/c/21773/
rameshthoomu (Mon, 14 May 2018 19:56:26 GMT):
@jtclark It seems the machine which you are using for testing is very slow..
rameshthoomu (Mon, 14 May 2018 19:56:57 GMT):
When I get time, I will run this test in my vlauch machine
gennadyl (Mon, 14 May 2018 19:59:00 GMT):
@rameshthoomu Great, you updated build scripts! Thanks!
jtclark (Mon, 14 May 2018 20:08:46 GMT):
@rameshthoomu I'm using a vlaunch machine for this.
rameshthoomu (Mon, 14 May 2018 20:09:01 GMT):
yes.. it;s very slow..
jtclark (Mon, 14 May 2018 20:09:30 GMT):
yeah, I don't know why. but my issue is that after the certificates are generated, it sits there and does nothing.....
jtclark (Mon, 14 May 2018 20:10:35 GMT):
I get this message and then nothing:
jtclark (Mon, 14 May 2018 20:10:40 GMT):
```
Starting with channel 'mychannel' and CLI timeout of '60' seconds and CLI delay of '3' seconds
proceeding ...
```
jtclark (Mon, 14 May 2018 20:11:14 GMT):
so I'm not sure what's going on with that....
jtclark (Mon, 14 May 2018 20:12:02 GMT):
but we can look at that later.... tomorrow perhaps. I'm going to move over to working on the PTE image one
rameshthoomu (Mon, 14 May 2018 20:18:38 GMT):
ok
hnadim (Mon, 14 May 2018 22:15:16 GMT):
Has joined the channel.
manish-sethi (Mon, 14 May 2018 22:44:57 GMT):
@rameshthoomu - when you get a chance, can you please see the reason for the build failure for - https://gerrit.hyperledger.org/r/#/c/21775/
rameshthoomu (Mon, 14 May 2018 23:43:23 GMT):
@manish-sethi I see this error
```
00:01:12.795 DEP: Checking for dependency issues..
00:01:13.253 dep:
00:01:13.253 version : v0.4.1
00:01:13.253 build date : 2018-05-14
00:01:13.253 git hash :
00:01:13.253 go version : go1.10
00:01:13.253 go compiler : gc
00:01:13.253 platform : linux/amd64
00:01:14.191 Gopkg.lock was not up to date
00:01:14.462 Makefile:210: recipe for target 'check-deps' failed
rameshthoomu (Mon, 14 May 2018 23:44:14 GMT):
If possible, could you please run `make check-deps` in your machine on this patch
rameshthoomu (Mon, 14 May 2018 23:45:46 GMT):
I see Gopkg.lock has been updated recently. https://github.com/hyperledger/fabric/commit/1a20bac1a6c522df14ab2a7ef8fc943dd425fcca
rameshthoomu (Mon, 14 May 2018 23:45:56 GMT):
may be rebase will fix this
rameshthoomu (Tue, 15 May 2018 00:34:44 GMT):
@gennadyl I reverified your change after the fix the whitespace error and the patch is passed now..
rameshthoomu (Tue, 15 May 2018 00:34:48 GMT):
https://gerrit.hyperledger.org/r/#/c/21495/
davidkhala (Tue, 15 May 2018 02:00:44 GMT):
@jtclark yes it is https://jenkins.hyperledger.org/job/fabric-sdk-node8-verify-x86_64/686/ , Do you have any idea?
rameshthoomu (Tue, 15 May 2018 02:27:08 GMT):
@davidkhala could be timeout error.. I just re-triggered test now..
davidkhala (Tue, 15 May 2018 02:27:53 GMT):
@rameshthoomu Thanks, let's see
rameshthoomu (Tue, 15 May 2018 02:36:47 GMT):
again failed..
rameshthoomu (Tue, 15 May 2018 02:58:10 GMT):
@davidkhala seems it's failing consistently.. Could you please check the test
davidkhala (Tue, 15 May 2018 04:57:26 GMT):
@rameshthoomu saw that, I will try
davidkhala (Tue, 15 May 2018 05:56:08 GMT):
@rameshthoomu to isolate my code
davidkhala (Tue, 15 May 2018 05:56:08 GMT):
@rameshthoomu to isolate my code's affect, I create a test patch but found failure still: https://gerrit.hyperledger.org/r/#/c/21803/
jtclark (Tue, 15 May 2018 13:33:23 GMT):
@davidkhala I was initially thinking that it was a timeout error as well
jtclark (Tue, 15 May 2018 15:10:50 GMT):
@rameshthoomu - https://gist.github.com/ibm-jason/d65e8c7ada61152a6c1db4046dd677b3
zhaochy (Wed, 16 May 2018 02:22:37 GMT):
hello, how can I see the fabric-peer logs when I submit a CR ?
rameshthoomu (Wed, 16 May 2018 02:37:29 GMT):
@zhaochy the container logs are not available from unit-test job..
rameshthoomu (Wed, 16 May 2018 02:38:51 GMT):
but the same are available from smoke test job.. You can see docker container logs from nexus log server ex: https://logs.hyperledger.org/production/vex-yul-hyp-jenkins-3/fabric-smoke-tests-x86_64/1158/
latitiah (Wed, 16 May 2018 03:44:04 GMT):
@rameshthoomu @sambhavdutt Please try the execution of https://gerrit.hyperledger.org/r/#/c/21451/ using the integration make target. This CR has been updated to account for the vscc changes that were merged earlier.
nirro (Wed, 16 May 2018 07:11:14 GMT):
Has joined the channel.
nirro (Wed, 16 May 2018 07:13:03 GMT):
@rjones hi, I have this item in gerrit - https://gerrit.hyperledger.org/r/#/c/21185/ and from some reason the unit tests don't run.
is it related to the comment you wrote there `Removed F3-UnitTest-1`?
rjones (Wed, 16 May 2018 07:25:31 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=eWvjs7rku4v8JFTXy) @nirro manually triggered
nirro (Wed, 16 May 2018 07:37:55 GMT):
thank you
rjones (Wed, 16 May 2018 07:38:40 GMT):
@nirro the issue is we turned off retrigger on minor rebase, and the previous change apparently had no votes to carry forward. not sure why
nirro (Wed, 16 May 2018 07:39:44 GMT):
when I first pushed the change to gerrit it was WIP, and after several tests I removed the WIP prefix. maybe related?
rjones (Wed, 16 May 2018 07:39:58 GMT):
oh yes that would do it
rameshthoomu (Wed, 16 May 2018 15:49:22 GMT):
@harrijk We are seeing fabric clone in s390x builds taking huge time.. see this build https://jenkins.hyperledger.org/sandbox/job/fabric-sdk-node6-merge-release-1.0-s390x/1/console
rameshthoomu (Wed, 16 May 2018 15:53:28 GMT):
this took almost 13 mins
```
0:00:16.053 Cloning into '/w/workspace/fabric-sdk-node6-merge-release-1.0-s390x/gopath/src/github.com/hyperledger/fabric'...
00:13:11.521 Total 65834 (delta 22), reused 65721 (delta 22)
```
harrijk (Wed, 16 May 2018 16:06:16 GMT):
@rameshthoomu OK, I will take a look.
rameshthoomu (Wed, 16 May 2018 19:42:11 GMT):
@ashutosh_kumar Could you please take a look at the OWASP dependency check results on fabric-sdk-java https://jenkins.hyperledger.org/sandbox/job/fabric-sdk-java-verify-x86_64/OWSP_20Dependency_20Check_20Results/
rameshthoomu (Wed, 16 May 2018 19:42:21 GMT):
let me know if the results are good..
rameshthoomu (Wed, 16 May 2018 19:42:34 GMT):
Will push this change based on your comments
ashutosh_kumar (Wed, 16 May 2018 19:43:17 GMT):
ok. Will do.
jtclark (Wed, 16 May 2018 21:21:23 GMT):
@ashutosh_kumar have you also been getting the safesql emails?
ashutosh_kumar (Wed, 16 May 2018 21:25:11 GMT):
yes , I am getting safesql emails.
rameshthoomu (Thu, 17 May 2018 20:24:50 GMT):
@ashutosh_kumar please check the OWASP results https://jenkins.hyperledger.org/view/Weekly/job/fabric-sdk-java-owasp-weekly-x86_64/OWSP_20Dependency_20Check_20Results/
rameshthoomu (Thu, 17 May 2018 20:25:15 GMT):
@ashutosh_kumar this is all yours now https://jenkins.hyperledger.org/view/Weekly/
rameshthoomu (Thu, 17 May 2018 20:25:15 GMT):
@ashutosh_kumar this is all yours now https://jenkins.hyperledger.org/view/Weekly/ :wink:
ashutosh_kumar (Thu, 17 May 2018 20:29:02 GMT):
I am trying to understand the result.
ashutosh_kumar (Thu, 17 May 2018 20:29:02 GMT):
I am trying to understand OWASP dependency check result.
rameshthoomu (Thu, 17 May 2018 20:29:53 GMT):
ok check the above link that's the latest result from production jenkins
ashutosh_kumar (Thu, 17 May 2018 20:30:16 GMT):
Did you run maven before you run dependency check ?
ashutosh_kumar (Thu, 17 May 2018 20:32:04 GMT):
Per DependencyCheck result , it seems like there is no vulnerable dependency.
ashutosh_kumar (Thu, 17 May 2018 20:32:49 GMT):
Also , I am not seeing scan for Fabric CA and NSP in the link https://jenkins.hyperledger.org/view/Weekly/.
ashutosh_kumar (Thu, 17 May 2018 20:33:35 GMT):
I assume , I am going to get weekly email notification as well , right ? @rameshthoomu
rameshthoomu (Thu, 17 May 2018 20:35:56 GMT):
patches are on the way to nsp and ca
rameshthoomu (Thu, 17 May 2018 20:36:20 GMT):
and yes I run maven and run all the tests on before dependency check on the target jar
rameshthoomu (Thu, 17 May 2018 20:36:56 GMT):
I think email notification is not configured on owasp.. will enable in the next patch
rameshthoomu (Thu, 17 May 2018 20:45:28 GMT):
@ashutosh_kumar do you need ca and nsp on all the branches?
ashutosh_kumar (Thu, 17 May 2018 20:46:13 GMT):
what do you mean by all branches ?
rameshthoomu (Thu, 17 May 2018 20:46:30 GMT):
like master, relaese-1.0 and release-1.1
ashutosh_kumar (Thu, 17 May 2018 20:46:39 GMT):
hmm.
ashutosh_kumar (Thu, 17 May 2018 20:46:56 GMT):
what are you doing for Fabric ?
rameshthoomu (Thu, 17 May 2018 20:47:04 GMT):
only on master
ashutosh_kumar (Thu, 17 May 2018 20:47:16 GMT):
then do the same for others too.
ashutosh_kumar (Thu, 17 May 2018 20:47:24 GMT):
master will suffice.
rameshthoomu (Thu, 17 May 2018 20:47:59 GMT):
ok
rameshthoomu (Fri, 18 May 2018 18:58:45 GMT):
@bretharrison looking at this FAB-10167.. Do you want me to push 8.11.2 in fabric-baseimage?
rameshthoomu (Fri, 18 May 2018 18:58:45 GMT):
@bretharrison looking at this FAB-10167 .. Do you want me to push 8.11.2 in fabric-baseimage?
rameshthoomu (Fri, 18 May 2018 18:59:38 GMT):
We have to test this first before publish baseimage..
rjones (Fri, 18 May 2018 18:59:39 GMT):
@rameshthoomu I've noticed that when the first step of the new workflow fails, it doesn't set -1 in F1, it sets v=-1
rjones (Fri, 18 May 2018 18:59:53 GMT):
sometimes. I've also noticed it frequently doesn't vote at all.
bretharrison (Fri, 18 May 2018 19:00:11 GMT):
is that what the Chaincode node container is based on ?
rameshthoomu (Fri, 18 May 2018 19:00:39 GMT):
oh let me check the script
rjones (Fri, 18 May 2018 19:00:47 GMT):
@rameshthoomu see https://gerrit.hyperledger.org/r/#/q/status:open+project:fabric+is:mergeable+label:F1-VerifyBuild%253D0 for instance
rameshthoomu (Fri, 18 May 2018 19:01:19 GMT):
Checking @rjones
rjones (Fri, 18 May 2018 19:01:29 GMT):
OK
rjones (Fri, 18 May 2018 19:02:06 GMT):
https://gerrit.hyperledger.org/r/#/q/status:open+project:fabric+is:mergeable+label:F1-VerifyBuild%253D0+owner:%22Matthias+Neugschwandtner+%253Ceug%2540zurich.ibm.com%253E%22
rameshthoomu (Fri, 18 May 2018 19:08:55 GMT):
I think it's because of quotes are missing from the -m flag in this command ` vote -m "$CHECKS_CMD are failed" -l F1-VerifyBuild=-1`
rameshthoomu (Fri, 18 May 2018 19:09:30 GMT):
other commands vote command looks like this `vote -m '"make docker failed"' -l F1-VerifyBuild=-1`
rameshthoomu (Fri, 18 May 2018 19:10:49 GMT):
I think this change is made to fix the $CHECK_CMD command appearing in gerrit without resolving..
jtclark (Fri, 18 May 2018 19:13:27 GMT):
@rameshthoomu question: how long do the release jobs typically take?
jtclark (Fri, 18 May 2018 19:14:49 GMT):
@rameshthoomu specifically the run_node_sdk_byfn.sh test
jtclark (Fri, 18 May 2018 19:15:23 GMT):
now that I've fixed that in the patch the release test job is now taking a lot longer
jtclark (Fri, 18 May 2018 19:15:23 GMT):
now that I've fixed that in the patch, the release test job is now taking a lot longer
rameshthoomu (Fri, 18 May 2018 19:16:43 GMT):
check what's there in that test..
rjones (Fri, 18 May 2018 19:25:03 GMT):
@rameshthoomu you could vote in one step and comment on another
jtclark (Fri, 18 May 2018 19:25:54 GMT):
```
rm -rf ${WORKSPACE}/gopath/src/github.com/hyperledger/fabric-sdk-node
WD="${WORKSPACE}/gopath/src/github.com/hyperledger/fabric-sdk-node"
SDK_REPO_NAME=fabric-sdk-node
git clone ssh://hyperledger-jobbuilder@gerrit.hyperledger.org:29418/$SDK_REPO_NAME $WD
cd $WD
git checkout tags/v1.0.0
NODE_SDK_COMMIT=$(git log -1 --pretty=format:"%h")
echo "FABRIC NODE SDK COMMIT ========> " $NODE_SDK_COMMIT >> ${WORKSPACE}/gopath/src/github.com/hyperledger/commit_history.log
cd test/fixtures
cat docker-compose.yaml > docker-compose.log
docker-compose up >> dockerlogfile.log 2>&1 &
sleep 10
docker ps -a
cd ../.. && npm install
npm config set prefix ~/npm && npm install -g gulp && npm install -g istanbul
gulp && gulp ca
rm -rf node_modules/fabric-ca-client && npm install
node test/integration/e2e.js
```
jtclark (Fri, 18 May 2018 19:32:03 GMT):
@rameshthoomu :point_up_tone2: that's what's in the script.
jtclark (Fri, 18 May 2018 19:35:10 GMT):
@rameshthoomu also, were you ready to share that management dashboard we were looking at yesterday?
rameshthoomu (Fri, 18 May 2018 19:35:50 GMT):
@rjones looking into that now
rameshthoomu (Fri, 18 May 2018 20:00:54 GMT):
@rjones patch is merged now and I triggered this patch. Now I see voting back to gerrit https://gerrit.hyperledger.org/r/#/c/14769/
rameshthoomu (Fri, 18 May 2018 20:01:27 GMT):
if possible could you please trigger the effected patchsets
scottz (Fri, 18 May 2018 20:05:17 GMT):
three
rjones (Fri, 18 May 2018 20:05:58 GMT):
Yes
scottz (Fri, 18 May 2018 20:08:45 GMT):
I created bug https://jira.hyperledger.org/browse/FAB-10216, and assigned Component = fabric-build. Please reroute if that was not the right place. When I "make docker-images" in fabric, is there really a need for THREE of everything, with slightly differing tags? It's using up so much space.
rjones (Fri, 18 May 2018 20:15:57 GMT):
@rameshthoomu https://gerrit.hyperledger.org/r/#/q/status:open+project:fabric+is:mergeable+label:F1-VerifyBuild%253D-1 :thumbsup:
aambati (Fri, 18 May 2018 20:45:56 GMT):
@rameshthoomu is there anything wrong with e2e tests, they are failing
rameshthoomu (Fri, 18 May 2018 21:30:01 GMT):
@aambati could you pls provide failed build
aambati (Fri, 18 May 2018 21:30:41 GMT):
https://jenkins.hyperledger.org/job/fabric-ca-verify-end-2-end-x86_64/403/
rameshthoomu (Fri, 18 May 2018 21:49:52 GMT):
@aambati I see a bug is created here FAB-10223
rameshthoomu (Fri, 18 May 2018 21:50:20 GMT):
seems fabric-sdk-java tests are failing.. @rickr could you please check
aambati (Fri, 18 May 2018 22:09:34 GMT):
@rameshthoomu i think i know what is causing it...we pushed a change set in fabric CA, need to make corresponding changes in SDKs
rameshthoomu (Fri, 18 May 2018 22:11:52 GMT):
ok
rameshthoomu (Fri, 18 May 2018 22:12:08 GMT):
can you please update the same in FAB-10223
rameshthoomu (Fri, 18 May 2018 22:13:13 GMT):
How the verify build passed?
rickr (Sat, 19 May 2018 05:51:07 GMT):
@aambati SDKs run tests to make sure we work before we integrate. CA obviously then does not ? You broke you fix FAB-10223 assigned to you thanks
dave.enyeart (Mon, 21 May 2018 02:44:29 GMT):
@cbf @mastersingh24 @rameshthoomu fabric-samples is failing CI due to amd64 vs x86_64 change. What do you think? See the comment and failure in https://gerrit.hyperledger.org/r/#/c/22039/ for details.
rameshthoomu (Mon, 21 May 2018 03:16:46 GMT):
@dave.enyeart it's because of the ARCH value has been changed with this change https://gerrit.hyperledger.org/r/#/c/21733/4/Makefile . So, the maked docker from fabric-ca is failing to build fabric-ca-* images.
rameshthoomu (Mon, 21 May 2018 03:17:15 GMT):
fabric-ca sample test is looking for fabric-ca-* images..
cbf (Mon, 21 May 2018 10:01:53 GMT):
we publish the image tags. I provided the script a month ago
dave.enyeart (Mon, 21 May 2018 10:34:17 GMT):
@rameshthoomu @cbf Ok, and where in fabric-samples do we need to change from x86_64 to amd64, so that fabric-samples CI starts working again?
cbf (Mon, 21 May 2018 10:34:53 GMT):
sigh... just publish the tags
dave.enyeart (Mon, 21 May 2018 10:35:35 GMT):
could you be more specific please
cbf (Mon, 21 May 2018 10:39:42 GMT):
https://gerrit.hyperledger.org/r/c/20875/
cbf (Mon, 21 May 2018 10:40:18 GMT):
the script was merged almost a month ago... it needs to be run by someone with push privs to dockerhub hyperledger org
cbf (Mon, 21 May 2018 10:40:59 GMT):
that will let us use multi-arch everywhere
cbf (Mon, 21 May 2018 10:41:25 GMT):
the other thing that can be done - just tag the x86_64 images as amd64
dave.enyeart (Mon, 21 May 2018 10:42:27 GMT):
ok, and I assume both of those actions would be done by @rameshthoomu and team, right?
cbf (Mon, 21 May 2018 10:42:38 GMT):
someone with push privs
dave.enyeart (Mon, 21 May 2018 10:42:50 GMT):
that's my question... who has that?
cbf (Mon, 21 May 2018 10:43:04 GMT):
probably @jwagantall
dave.enyeart (Mon, 21 May 2018 10:45:19 GMT):
@cbf https://gerrit.hyperledger.org/r/#/c/20875/ is on release-1.1, is there as master equivalent/
dave.enyeart (Mon, 21 May 2018 10:45:19 GMT):
@cbf https://gerrit.hyperledger.org/r/#/c/20875/ is on release-1.1, is there as master equivalent?
dave.enyeart (Mon, 21 May 2018 10:45:19 GMT):
@cbf https://gerrit.hyperledger.org/r/#/c/20875/ is on release-1.1, is there a master equivalent?
cbf (Mon, 21 May 2018 10:45:49 GMT):
docker pull hyperledger/fabric-peer:x86_64-1.1.0
cbf (Mon, 21 May 2018 10:46:25 GMT):
docker tag hyperledger/fabric-peer:x86_64-1.1.0 hyperledger/fabric-peer:amd64-1.1.0
cbf (Mon, 21 May 2018 10:46:36 GMT):
docker push hyperledger/fabric-peer:amd64-1.1.0
cbf (Mon, 21 May 2018 10:46:48 GMT):
lather, rinse and repeat for all images
cbf (Mon, 21 May 2018 10:47:06 GMT):
do that and do the script in the CR above so we can move on
cbf (Mon, 21 May 2018 10:47:18 GMT):
yes, there is
cbf (Mon, 21 May 2018 10:47:57 GMT):
https://jira.hyperledger.org/browse/FAB-9652
dave.enyeart (Mon, 21 May 2018 10:48:26 GMT):
ok, not pushed yet...
dave.enyeart (Mon, 21 May 2018 10:48:43 GMT):
and in general, are you driving the other subtasks for multi-arch? https://jira.hyperledger.org/browse/FAB-9629
cbf (Mon, 21 May 2018 10:48:43 GMT):
no, because not urgent
cbf (Mon, 21 May 2018 10:48:51 GMT):
we don't need it until the release
cbf (Mon, 21 May 2018 10:49:12 GMT):
and that process is changing
cbf (Mon, 21 May 2018 10:49:14 GMT):
so...
dave.enyeart (Mon, 21 May 2018 10:49:44 GMT):
it's almost june, it will be urgent soon enough :)
rickr (Mon, 21 May 2018 12:34:12 GMT):
@aambati FAB-10223 ? I wan't to upgrade my fabric but without this bug
rickr (Mon, 21 May 2018 14:07:42 GMT):
@rameshthoomu https://jenkins.hyperledger.org/job/fabric-sdk-java-verify-x86_64/1841/console
rickr (Mon, 21 May 2018 14:08:28 GMT):
```
07:09:38 Step 1/6 : FROM hyperledger/fabric-orderer:amd64-1.1.0
07:09:38 manifest for hyperledger/fabric-orderer:amd64-1.1.0 not found
07:09:38 Makefile:128: recipe for target 'build/image/fabric-ca-orderer/.dummy-amd64-1.2.0-snapshot-c583d33' failed
```
rameshthoomu (Mon, 21 May 2018 14:18:28 GMT):
fixing
jtclark (Mon, 21 May 2018 14:46:29 GMT):
@rameshthoomu, @sambhavdutt - testing FAB-8501 once more.
jtclark (Mon, 21 May 2018 14:56:18 GMT):
I also saw @scottz comments, so I'll need to address those
rameshthoomu (Mon, 21 May 2018 16:03:30 GMT):
@rickr Update CI config and re-triggered your change set.. Now the patchset is failing with FAB-10223.
rickr (Mon, 21 May 2018 16:13:35 GMT):
k thx
cbf (Tue, 22 May 2018 11:35:52 GMT):
@rameshthoomu where are we on the multi-arch manifests?
cbf (Tue, 22 May 2018 11:36:22 GMT):
also, if we could get amd64 tags added to all 1.1.0 images that would be a good thing, too
cbf (Tue, 22 May 2018 11:36:34 GMT):
eg
cbf (Tue, 22 May 2018 11:37:09 GMT):
docker tag hyperledger/fabric-peer:x86_64-1.1.0 hyperledger/fabric-peer:amd64-1.1.0
cbf (Tue, 22 May 2018 11:37:22 GMT):
docker push hyperledger/fabric-peer:amd64-1.1.0
cbf (Tue, 22 May 2018 11:37:35 GMT):
this will help the transition to multi-arch
rameshthoomu (Tue, 22 May 2018 13:01:16 GMT):
I don't have permission to push this manually.. Will update Jenkins job to publish these images.. I was testing gen-manifests.sh yesterday..
cbf (Tue, 22 May 2018 13:40:12 GMT):
that seems unnecessary
cbf (Tue, 22 May 2018 13:40:23 GMT):
can @jwagantall run now that you've tested?
rameshthoomu (Tue, 22 May 2018 13:40:46 GMT):
yes.. I have prepared a script to do this..
cbf (Tue, 22 May 2018 13:40:52 GMT):
the whole: "maintainers cannot do stuff" thing is really annoying
rameshthoomu (Tue, 22 May 2018 13:40:52 GMT):
will share that with her..
cbf (Tue, 22 May 2018 13:41:17 GMT):
if you cannot trust the maintainers, who can you trust?
rjones (Tue, 22 May 2018 14:07:34 GMT):
the question is who can push to dockerhub?
rjones (Tue, 22 May 2018 14:10:40 GMT):
@cbf using fabric-peer, the fabric team has had write access since day one, and still has write access. the fabric team is: you, @greg.haskins , @mastersingh24 , @sheehan .
rjones (Tue, 22 May 2018 14:11:07 GMT):
I can look at other fabric repos on dockerhub but they _should_ be set up the same way.
cbf (Tue, 22 May 2018 14:11:20 GMT):
hmmm
rjones (Tue, 22 May 2018 14:12:30 GMT):
I just checked four random fabric repos and the permissions are the same.
rjones (Tue, 22 May 2018 14:14:31 GMT):
cello is doing something interesting: they have dockerfiles for each repo, and they're automagically built on merge. it seems like one more thing to worry about to me, since you have to add specific build targets each time
rjones (Tue, 22 May 2018 14:15:40 GMT):
https://hub.docker.com/r/hyperledger/cello-baseimage/ for instance builds from /dockerhub/latest/baseimage inside the cello repo
cbf (Tue, 22 May 2018 14:21:44 GMT):
ok thx
cbf (Tue, 22 May 2018 14:22:04 GMT):
@rameshthoomu did you modify the script I previously shared for v1.1?
rameshthoomu (Tue, 22 May 2018 14:23:17 GMT):
No I didn't modify
cbf (Tue, 22 May 2018 14:24:47 GMT):
ok, I'm going to run that and publish manifest
cbf (Tue, 22 May 2018 14:25:09 GMT):
also going to tag all x86_64 images as amd64
cbf (Tue, 22 May 2018 14:36:31 GMT):
ok done
cbf (Tue, 22 May 2018 14:39:24 GMT):
https://chat.hyperledger.org/channel/fabric-maintainers?msg=kqga4RndmWWsPyy8J
rameshthoomu (Tue, 22 May 2018 15:43:45 GMT):
@dave.enyeart e2e_cli is broken. FAB-10253
sheehan (Tue, 22 May 2018 17:28:54 GMT):
@rjones I'm not actively pushing to the Fabric dockerhub repos so you can remove my write permission
rjones (Tue, 22 May 2018 17:29:02 GMT):
OK.
rjones (Tue, 22 May 2018 17:29:46 GMT):
done. It may be an artifact of when dockerhub was being spun up two years ago
sheehan (Tue, 22 May 2018 17:29:58 GMT):
yes, was using it back then
sheehan (Tue, 22 May 2018 17:30:18 GMT):
thanks
rjones (Tue, 22 May 2018 17:31:16 GMT):
for dockerhub, since it's super easy to delegate permissions, maintainers that have a dockerhub ID have always had write access. For github ACLs are more problematic :(
rjones (Tue, 22 May 2018 17:31:16 GMT):
for dockethub, since it's super easy to delegate permissions, maintainers that have a dockerhub ID have always had write access. For github ACLs are more problematic :(
cbf (Tue, 22 May 2018 18:59:23 GMT):
@rjones I think that the dockerhub privs should be release managers (me, gari, dave enyeart)... I am ok with greg staying on for baseimage and chaintool
rjones (Tue, 22 May 2018 19:08:11 GMT):
I don't see a chaintool repo on dockerhub. Jessica would need a dockerhub ID for Dave.
rjones (Tue, 22 May 2018 19:11:46 GMT):
what is this repo? https://hub.docker.com/r/hyperledger/fabric-starter-kit-private/
jtclark (Tue, 22 May 2018 21:30:51 GMT):
@rameshthoomu, @sambhavdutt - plz review: https://gerrit.hyperledger.org/r/22173
sambhavdutt (Tue, 22 May 2018 21:32:40 GMT):
looks good to me, just the owasp removed from the job
rameshthoomu (Tue, 22 May 2018 21:38:09 GMT):
@jtclark I have updated comment. Could you please address it..
rameshthoomu (Tue, 22 May 2018 21:38:28 GMT):
also, please add Jessica as well..
rjones (Tue, 22 May 2018 21:38:45 GMT):
or `ci-cr`
rjones (Tue, 22 May 2018 21:38:45 GMT):
or `cr-ci`
sudeshrshetty (Tue, 22 May 2018 21:44:04 GMT):
@rameshthoomu any idea on when latest image for fabric-ca will be created?
nexus3.hyperledger.org:10001/hyperledger/fabric-ca latest 6c977f28d92d 4 days ago
latest fabric-ca has some important fix needed for fabric sdks
rameshthoomu (Tue, 22 May 2018 21:46:47 GMT):
Waiting for this patch to merge.. https://gerrit.hyperledger.org/r/#/c/22157/
jtclark (Tue, 22 May 2018 22:13:26 GMT):
@rameshthoomu I removed it from the script. won't that remove it from ALL jobs that use it?
rameshthoomu (Tue, 22 May 2018 22:13:53 GMT):
yes it will
jtclark (Tue, 22 May 2018 22:14:11 GMT):
ok so, what should the commit msg be?
jtclark (Tue, 22 May 2018 22:14:29 GMT):
just to add that we are running OWASP test with the other job?
jtclark (Tue, 22 May 2018 22:15:22 GMT):
@rameshthoomu :point_up_tone2:
sudeshrshetty (Tue, 22 May 2018 22:30:44 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=SDwmzrkkZn6RcQo7Q) @rameshthoomu Thanks
ping40 (Wed, 23 May 2018 13:13:35 GMT):
Has joined the channel.
rjones (Wed, 23 May 2018 18:54:16 GMT):
@rameshthoomu I added "Run IntegrationTest" to several Fabric changes and no builds were kicked off
rameshthoomu (Wed, 23 May 2018 18:55:03 GMT):
ci-management merge job finished just now.. I have added comment on the patchset now it;s triggered https://jenkins.hyperledger.org/job/fabric-verify-integration-tests-x86_64/
rjones (Wed, 23 May 2018 18:55:33 GMT):
ok
dave.enyeart (Wed, 23 May 2018 19:27:23 GMT):
@rjones @rameshthoomu @sykesm 3 of the IntegrationTests have failed this hour for 3 different reasons. Is it too flakey to enable at this time?
rjones (Wed, 23 May 2018 19:28:29 GMT):
@dave.enyeart that's a good question for @rameshthoomu :)
dave.enyeart (Wed, 23 May 2018 19:28:45 GMT):
https://gerrit.hyperledger.org/r/#/q/project:fabric++label:F3-IntegrationTest%253D-1
rjones (Wed, 23 May 2018 19:30:56 GMT):
https://gerrit.hyperledger.org/r/#/q/label:F3-IntegrationTest%253D1+is:mergeable+is:open+project:fabric a few passed
rjones (Wed, 23 May 2018 19:31:42 GMT):
but there _are_ ~50 changes in flight that will need attention https://gerrit.hyperledger.org/r/#/q/label:F3-IntegrationTest%253C1+is:mergeable+is:open+project:fabric
dave.enyeart (Wed, 23 May 2018 19:34:09 GMT):
can we grandfather the pre-existing 50 somehow, to not require a +1 there?
rjones (Wed, 23 May 2018 19:35:11 GMT):
@dave.enyeart you _should_ see a button to insert that +1 manually
rameshthoomu (Wed, 23 May 2018 19:35:29 GMT):
@dave.enyeart
https://gerrit.hyperledger.org/r/#/c/20533/ - Patch#7 has been rebased.. So no images published from patch#7 to pull. So the test is failed while pulling these images.
https://gerrit.hyperledger.org/r/#/c/22015/ - Time out error
https://gerrit.hyperledger.org/r/#/c/22169/ - Not sure why it’s failed..
rjones (Wed, 23 May 2018 19:35:45 GMT):
and as a maintainer, your discretion on when to over-ride or add votes.
dave.enyeart (Wed, 23 May 2018 19:36:14 GMT):
yeah, i just used my discretion on one and +1ed it
rameshthoomu (Wed, 23 May 2018 19:36:40 GMT):
@latitiah said they are some timeout errors and she fixed with this change set https://gerrit.hyperledger.org/r/#/c/22015/
rjones (Wed, 23 May 2018 19:37:15 GMT):
votes.png
dave.enyeart (Wed, 23 May 2018 19:37:27 GMT):
but https://gerrit.hyperledger.org/r/#/c/22015/ has the timeout :)
dave.enyeart (Wed, 23 May 2018 19:38:42 GMT):
https://gerrit.hyperledger.org/r/#/c/20533/ - not sure what you mean
sykesm (Wed, 23 May 2018 19:38:59 GMT):
Let's take a step back, please.
sykesm (Wed, 23 May 2018 19:39:14 GMT):
First, the CI system isn't running the make target so it's living in its own little world.
sykesm (Wed, 23 May 2018 19:39:34 GMT):
Second, I had no insight into when or how this was to be integrated or I would have said something earlier.
sykesm (Wed, 23 May 2018 19:39:53 GMT):
So, I think we should revert what was done and try again.
sykesm (Wed, 23 May 2018 19:40:04 GMT):
Ideally we can do it *together* to make sure it does what it needs to do.
sykesm (Wed, 23 May 2018 19:40:53 GMT):
And, as far as I can tell, we enabled this without notifying anyone (again). Maybe I'm a little frustrated but, there it is
dave.enyeart (Wed, 23 May 2018 19:41:08 GMT):
right, some announcement should be made here and in fabric-maintainers for CI changes
dave.enyeart (Wed, 23 May 2018 19:42:03 GMT):
I just happened to notice it in gerrit
sykesm (Wed, 23 May 2018 19:42:15 GMT):
https://github.com/hyperledger/ci-management/blob/master/jjb/fabric/fabric-macros.yaml#L354 is what's running the tests and it seems relatively arbitrary and disconnected from what's in the source tree.
rameshthoomu (Wed, 23 May 2018 19:48:03 GMT):
@sykesm we don't build the images in the downstream jobs (smoke, unit, integration) as the images are build and publish from build check job.. So, the integration test is running on the same patch set commit..
dave.enyeart (Wed, 23 May 2018 19:49:09 GMT):
I also recommend revert and Ramesh/Matt review together before it is re-enabled.
rameshthoomu (Wed, 23 May 2018 19:50:12 GMT):
ok.. @jwagantall @rjones could you please revert this change https://gerrit.hyperledger.org/r/#/c/22215/ and remove the "IntegrationTest" label
rjones (Wed, 23 May 2018 19:50:33 GMT):
@rameshthoomu I propose people over-ride it instead of reverting it
dave.enyeart (Wed, 23 May 2018 19:53:01 GMT):
4th one has failed... nobody understands what this is doing well enough to know the criteria for over-riding
dave.enyeart (Wed, 23 May 2018 19:53:40 GMT):
I recommend revert, Matt/Ramesh review, communicate the coming change, then re-enable
sykesm (Wed, 23 May 2018 19:54:42 GMT):
I won't pretend to know how difficult some of these changes may be. Does it make sense to leave the label and just have a dummy job that sets the label until we enable it?
jwagantall (Wed, 23 May 2018 19:54:42 GMT):
@rjones how do we override it?
rjones (Wed, 23 May 2018 19:54:55 GMT):
@sykesm that would be much easier
rjones (Wed, 23 May 2018 19:55:22 GMT):
@jwagantall just vote on the job. See the screenshot I posted above - maintainers can just vote +1 for that vote
sykesm (Wed, 23 May 2018 19:55:31 GMT):
So, that's probably the path forward. Have a dummy job that just states it's a placeholder, set the label, and we can go from there.
rameshthoomu (Wed, 23 May 2018 19:56:05 GMT):
But I see people are posting a comment "Run IntegrationTest" as soon they see label with out vote
rjones (Wed, 23 May 2018 19:56:24 GMT):
well, I ran through and posted a bunch of them
rjones (Wed, 23 May 2018 19:56:59 GMT):
replace the existing script with one that votes +1 and move on
rameshthoomu (Wed, 23 May 2018 19:57:08 GMT):
not you.. someone posted.. don't remember the patchset..
rameshthoomu (Wed, 23 May 2018 19:57:34 GMT):
Ok.. so it's always +1
dave.enyeart (Wed, 23 May 2018 20:04:35 GMT):
and for the pre-existing CRs, somebody gives them all a +1 manually?
rjones (Wed, 23 May 2018 20:04:53 GMT):
at the same time you're giving the +2, I would assume
dave.enyeart (Wed, 23 May 2018 20:05:45 GMT):
can it be done in bulk now? otherwise need a post to fabric-maintainers explaining it. actually need a post to fabric-maintainers explaining it all in general.
rjones (Wed, 23 May 2018 20:07:10 GMT):
it would bump all of those changes to the top of the list. if you're OK with that, I think it could be done
rameshthoomu (Wed, 23 May 2018 20:13:32 GMT):
@rjones could you please review this https://gerrit.hyperledger.org/r/#/c/22225/
dave.enyeart (Wed, 23 May 2018 20:13:42 GMT):
probably don't want to bump them to the top... ok, @rjones could you post the action plan to #fabric-maintainers so that everybody knows they need to +1 in the interim
rjones (Wed, 23 May 2018 20:13:52 GMT):
@jwagantall ^^^^
rameshthoomu (Wed, 23 May 2018 20:13:58 GMT):
This change will not test the IntegrationTest but posts +1 against the label
rameshthoomu (Wed, 23 May 2018 20:16:29 GMT):
But if someone want to test the IntegrationTests, they can post a comment "Run IntegrationTest"
jwagantall (Wed, 23 May 2018 20:42:00 GMT):
reviewing the change now
rjones (Wed, 23 May 2018 22:28:10 GMT):
Has left the channel.
rjones (Thu, 24 May 2018 00:22:53 GMT):
Has joined the channel.
rjones (Thu, 24 May 2018 00:23:26 GMT):
https://gerrit.hyperledger.org/r/#/c/21447/ https://gerrit.hyperledger.org/r/#/c/21903/ are doc-only builds broken? @jwagantall @rameshthoomu
rjones (Thu, 24 May 2018 00:23:52 GMT):
@jwagantall @rameshthoomu the build fails ad doesn't vote.
rameshthoomu (Thu, 24 May 2018 00:35:31 GMT):
checking
rameshthoomu (Thu, 24 May 2018 00:40:25 GMT):
previous patchset missed -l flag to IntegrationTest lable
rameshthoomu (Thu, 24 May 2018 00:41:30 GMT):
https://gerrit.hyperledger.org/r/#/c/22241/
sumn2u (Thu, 24 May 2018 03:02:56 GMT):
Has joined the channel.
rjones (Thu, 24 May 2018 03:15:05 GMT):
Has left the channel.
nvmadhav (Fri, 25 May 2018 02:37:24 GMT):
Has joined the channel.
jtclark (Fri, 25 May 2018 13:29:52 GMT):
Morning
jtclark (Fri, 25 May 2018 14:27:24 GMT):
@rameshthoomu, @jwagantall - can either of you manually trigger this job: https://jenkins.hyperledger.org/view/fabric-test/job/fabric-test-pte-publish-x86_64/
jtclark (Fri, 25 May 2018 14:27:35 GMT):
I don't have access to trigger this job on prod
rameshthoomu (Fri, 25 May 2018 14:34:58 GMT):
@jtclark it's not required
rameshthoomu (Fri, 25 May 2018 14:35:14 GMT):
next time when you we need that image will trigger
jtclark (Fri, 25 May 2018 14:35:19 GMT):
I just wanted to test it out to make sure it works, but ok
rameshthoomu (Fri, 25 May 2018 14:35:31 GMT):
pl
rameshthoomu (Fri, 25 May 2018 14:35:31 GMT):
ok
jwagantall (Fri, 25 May 2018 15:54:46 GMT):
triggered 1 more just in case you guys needed it https://jenkins.hyperledger.org/view/fabric-test/job/fabric-test-pte-publish-x86_64/
jtclark (Fri, 25 May 2018 16:32:23 GMT):
@rameshthoomu so, now that the PTE image one is complete, I wanted to ask you what the next highest priority task is
rameshthoomu (Fri, 25 May 2018 16:32:59 GMT):
I thought you are working on release-tests
rameshthoomu (Fri, 25 May 2018 16:33:05 GMT):
8501
jtclark (Fri, 25 May 2018 17:07:03 GMT):
I was, yes.
jtclark (Fri, 25 May 2018 17:07:03 GMT):
@rameshthoomu I am, but I want to make sure the priority hasn't changed.
jtclark (Fri, 25 May 2018 17:07:43 GMT):
that's fine.
jwagantall (Tue, 29 May 2018 21:19:19 GMT):
Hi Team! https://jenkins.hyperledger.org/ is now set to quietDown mode. We are upgrading Nexus3 to version 3.8.0-02 in order to get real anonymous access to the binaries. This will take 20 mins or less.
rameshthoomu (Tue, 29 May 2018 21:20:48 GMT):
@cbf @tongli I have pushed pipeline script for fabric-samples repository and output looks like this.. This has been tested in sandbox.. This is WIP patchset.. have to push few more changes to Jenkinsfile to support gerrit trigger events
https://jenkins.hyperledger.org/sandbox/job/fabric-verify-byfn-x86_64/
https://gerrit.hyperledger.org/r/#/c/22443/
karmicway (Tue, 29 May 2018 21:35:40 GMT):
Has joined the channel.
jwagantall (Tue, 29 May 2018 21:38:28 GMT):
just waiting for my lead to +2 my change
cbf (Tue, 29 May 2018 21:47:59 GMT):
@rameshthoomu why are we building images? Should we not be pulling tagged images, instead?
rameshthoomu (Tue, 29 May 2018 21:49:00 GMT):
yes.. that's the plan.. right now the docker images with DOCKER_NS is not working in fabric-ca.. https://gerrit.hyperledger.org/r/#/c/22467/
cbf (Tue, 29 May 2018 21:49:07 GMT):
also, I am thinking that we should be building from the make file... e.g. instead of .byfn.sh up etc we should have a makefile with a target that handles what we want
cbf (Tue, 29 May 2018 21:49:44 GMT):
so, to add jenkins to fabric-chaincode-evm I could write a jenkinsfile?
jwagantall (Tue, 29 May 2018 21:50:20 GMT):
dona and upgraded now.. Jenkins is back on track
rameshthoomu (Tue, 29 May 2018 21:50:22 GMT):
Yes. We need JJB and jenkinfile should go hand in hand..
rameshthoomu (Tue, 29 May 2018 21:50:33 GMT):
Thanks @jwagantall
cbf (Tue, 29 May 2018 21:51:01 GMT):
so need a jjb to kick off the jenkinsfile in a repo?
rameshthoomu (Tue, 29 May 2018 21:51:36 GMT):
yes
rameshthoomu (Tue, 29 May 2018 21:52:40 GMT):
I am still working on this change set to make it compatible to gerrit triggers.. Once this is done, will roll out on fabric-samples first
rameshthoomu (Tue, 29 May 2018 21:52:44 GMT):
https://gerrit.hyperledger.org/r/#/c/22443/
cbf (Tue, 29 May 2018 21:58:37 GMT):
ok
yacovm (Tue, 29 May 2018 22:30:39 GMT):
Clipboard - May 30, 2018 1:30 AM
yacovm (Tue, 29 May 2018 22:30:52 GMT):
how did I get +1s so fast on everything? :thinking_face: @rameshthoomu
yacovm (Tue, 29 May 2018 22:31:32 GMT):
the change set has 900 lines of golang code https://gerrit.hyperledger.org/r/#/c/22507/
yacovm (Tue, 29 May 2018 22:31:32 GMT):
the change set has hundreds lines of golang code https://gerrit.hyperledger.org/r/#/c/22507/
yacovm (Tue, 29 May 2018 22:44:24 GMT):
so is https://gerrit.hyperledger.org/r/#/c/22509/
yacovm (Tue, 29 May 2018 22:44:27 GMT):
something is amiss here
rameshthoomu (Tue, 29 May 2018 22:54:12 GMT):
I think it’s considering it as a documentation build
rameshthoomu (Tue, 29 May 2018 22:54:30 GMT):
On the way to home.. will check after sometime
yacovm (Tue, 29 May 2018 22:56:57 GMT):
I think all my change sets should be considered as docs build.
yacovm (Tue, 29 May 2018 22:56:57 GMT):
I think all my change sets should be considered as doc builds and get automatically +1s from jenkins.
yacovm (Tue, 29 May 2018 22:57:45 GMT):
Very good. I think all my change sets should be considered as doc builds and get automatically and immediately +1s from jenkins.
yacovm (Tue, 29 May 2018 23:06:39 GMT):
anyway the unit tests passed on the parent 3rd change set https://gerrit.hyperledger.org/r/#/c/22463/ so i conclude that the bottom 2 are OK
sambhavdutt (Wed, 30 May 2018 01:12:42 GMT):
@yacovm
yes, I see now that all tests have passed for yours, https://gerrit.hyperledger.org/r/#/c/22463/
sudeshrshetty (Wed, 30 May 2018 14:59:35 GMT):
@rameshthoomu Looks like 'latest' docker images are not properly set, now they show up as 2 months old
REPOSITORY TAG IMAGE ID CREATED SIZE
nexus3.hyperledger.org:10001/hyperledger/fabric-ca latest 72617b4fa9b4 2 months ago 299MB
registry.hub.docker.com/hyperledger/fabric-ca x86_64-1.1.0 72617b4fa9b4 2 months ago 299MB
nexus3.hyperledger.org:10001/hyperledger/fabric-orderer latest ce0c810df36a 2 months ago 180MB
registry.hub.docker.com/hyperledger/fabric-orderer x86_64-1.1.0 ce0c810df36a 2 months ago 180MB
registry.hub.docker.com/hyperledger/fabric-peer x86_64-1.1.0 b023f9be0771 2 months ago 187MB
nexus3.hyperledger.org:10001/hyperledger/fabric-peer latest b023f9be0771 2 months ago 187MB
nexus3.hyperledger.org:10001/hyperledger/fabric-ccenv latest c8b4909d8d46 2 months ago 1.39GB
registry.hub.docker.com/hyperledger/fabric-ccenv x86_64-1.1.0 c8b4909d8d46 2 months ago 1.39GB
registry.hub.docker.com/hyperledger/fabric-baseos x86_64-0.4.6 220e5cf3fb7f 3 months ago 151MB
nexus3.hyperledger.org:10001/hyperledger/fabric-baseos x86_64-0.4.6 220e5cf3fb7f 3 months ago 151MB
rameshthoomu (Wed, 30 May 2018 15:00:20 GMT):
yes.. working on this..
rameshthoomu (Wed, 30 May 2018 15:00:25 GMT):
these worked earlier right
sudeshrshetty (Wed, 30 May 2018 15:00:29 GMT):
Yes
sudeshrshetty (Wed, 30 May 2018 15:00:39 GMT):
Since yesterday we are facing issues
sudeshrshetty (Wed, 30 May 2018 15:00:53 GMT):
Thanks @rameshthoomu
cbf (Wed, 30 May 2018 15:31:35 GMT):
@rameshthoomu, are all the images now tagged with stable if nightly is clean?
rameshthoomu (Wed, 30 May 2018 15:41:12 GMT):
yes all fabric and fabric-ca images tagged with stable from master branch but after this patch is merged https://gerrit.hyperledger.org/r/#/c/22467/ will publish with DOCKER_NS and override the PROJECT_VERSION to `amd64-stable`
rameshthoomu (Wed, 30 May 2018 15:41:12 GMT):
yes all fabric and fabric-ca images tagged with stable from master branch but after this patch is merged https://gerrit.hyperledger.org/r/#/c/22467/ will publish with DOCKER_NS and override the PROJECT_VERSION to `amd64-stable` while building images
rameshthoomu (Wed, 30 May 2018 15:41:12 GMT):
yes all fabric and fabric-ca images tagged with stable from master branch but after this patch is merged https://gerrit.hyperledger.org/r/#/c/22467/ will publish with DOCKER_NS and override the PROJECT_VERSION to `stable` while building images
rameshthoomu (Wed, 30 May 2018 15:41:34 GMT):
as we are going to publish images from s390x builds..
rameshthoomu (Wed, 30 May 2018 15:45:17 GMT):
also, these images are publishing from every merge e2e job (which runs e2e_cli, byfn, efyn, sdk e2e tests)
rameshthoomu (Wed, 30 May 2018 15:45:45 GMT):
and there is an svt job which leverages these images..
jtclark (Wed, 30 May 2018 16:26:37 GMT):
@rameshthoomu wrapping up 8501. last test is running now. I'll ping you shortly
jtclark (Wed, 30 May 2018 16:27:38 GMT):
@rameshthoomu is this one I can pickup? it's assigned to you atm... are you working on this one yet?
jtclark (Wed, 30 May 2018 16:27:40 GMT):
https://jira.hyperledger.org/browse/FAB-10258
rameshthoomu (Wed, 30 May 2018 16:28:58 GMT):
Once this patch is merged https://gerrit.hyperledger.org/r/#/c/22467/ the highest priority is to publish nexus images with nexus docker name space and pull these images in sdk's and fabric-samples
jtclark (Wed, 30 May 2018 16:29:23 GMT):
ok, is there a JIRA item for this?
rameshthoomu (Wed, 30 May 2018 16:29:28 GMT):
@sambhavdutt is working on creating e2e merge s390x job..
rameshthoomu (Wed, 30 May 2018 16:30:03 GMT):
yes.. see here https://jira.hyperledger.org/issues/?jql=project%20%3D%20FAB%20AND%20status%20in%20(%22In%20Progress%22%2C%20%22To%20Do%22%2C%20%22In%20Review%22%2C%20Backlog%2C%20Unverified)%20AND%20component%20%3D%20fabric-ci%20AND%20%22Epic%20Link%22%20is%20not%20EMPTY%20AND%20project%20in%20(10002)%20AND%20cf%5B10006%5D%20%3D%20FAB-10068
rameshthoomu (Wed, 30 May 2018 16:30:46 GMT):
Once the fabric-ca is merged, the remaining task should finish by EOD today
jtclark (Wed, 30 May 2018 16:33:47 GMT):
so this one: https://jira.hyperledger.org/browse/FAB-10066
jtclark (Wed, 30 May 2018 16:34:30 GMT):
which change are we waiting to merge? to you have the gerrit link?
jtclark (Wed, 30 May 2018 16:34:30 GMT):
which change are we waiting to merge? do you have the gerrit link?
jtclark (Wed, 30 May 2018 16:34:48 GMT):
@rameshthoomu :point_up_tone2:
rameshthoomu (Wed, 30 May 2018 16:35:33 GMT):
https://gerrit.hyperledger.org/r/#/c/22467/
rameshthoomu (Wed, 30 May 2018 16:43:24 GMT):
build_flow-1.png
rameshthoomu (Wed, 30 May 2018 16:44:48 GMT):
@jtclark @sambhavdutt Basically we are trying to finish the above flow EOD today.. You can ignore ppc64le for now..
cbf (Wed, 30 May 2018 17:03:19 GMT):
@rameshthoomu coolio... so stable is retagged every merge?
cbf (Wed, 30 May 2018 17:03:55 GMT):
possibility that during a pull of images, you could have images from different commit-levels
jtclark (Wed, 30 May 2018 18:13:47 GMT):
@rameshthoomu see: https://jenkins.hyperledger.org/sandbox/job/fabric-test-release-x86_64/6/artifact/gopath/src/github.com/hyperledger/fabric-test/regression/release/output_e2e_node_sdk_release_tests.log
rameshthoomu (Wed, 30 May 2018 18:14:12 GMT):
yes e2e job publishes every merge e2e job..
jtclark (Wed, 30 May 2018 18:14:50 GMT):
@rameshthoomu not sure why I'm seeing this...
rameshthoomu (Wed, 30 May 2018 18:16:40 GMT):
along with stable, we can also publish the images with commit (7 chars) tag but pull images with commit tag is little difficult from nexus
rameshthoomu (Wed, 30 May 2018 18:20:44 GMT):
@jtclark see where you are setting value to NODE_VER here this https://gerrit.hyperledger.org/r/#/c/18339/17/pre_setup.sh
jtclark (Wed, 30 May 2018 18:21:33 GMT):
@rameshthoomu and where is $NODE_VER set?
rameshthoomu (Wed, 30 May 2018 18:24:58 GMT):
you have to initialize this.. You have change this in patch#15 https://gerrit.hyperledger.org/r/#/c/18339/1..15/pre_setup.sh
rameshthoomu (Wed, 30 May 2018 18:25:23 GMT):
assign 8.9.4 or 8.11.2
rameshthoomu (Wed, 30 May 2018 18:25:53 GMT):
8.11.2 is future upgrade version in node sdk builds
jtclark (Wed, 30 May 2018 18:40:09 GMT):
@rameshthoomu so this var should be hard-coded for now?
rameshthoomu (Wed, 30 May 2018 18:46:11 GMT):
yes
jtclark (Wed, 30 May 2018 19:16:51 GMT):
ok
rogerwilcos (Wed, 30 May 2018 22:01:17 GMT):
Has joined the channel.
nagap (Thu, 31 May 2018 16:15:13 GMT):
Has joined the channel.
jtclark (Thu, 31 May 2018 17:44:42 GMT):
maybe I can push my fix and test
jtclark (Thu, 31 May 2018 17:44:49 GMT):
then while the job is running work on something else
jtclark (Thu, 31 May 2018 17:44:55 GMT):
so I need to know that the next highest thing is
rameshthoomu (Thu, 31 May 2018 17:46:11 GMT):
you can work on https://jira.hyperledger.org/browse/FAB-8461
jtclark (Thu, 31 May 2018 17:47:01 GMT):
ok
rameshthoomu (Thu, 31 May 2018 17:47:07 GMT):
Basically it's very simple.. @sambhavdutt and myself pushed change here https://gerrit.hyperledger.org/r/#/c/20307/
jtclark (Thu, 31 May 2018 17:47:19 GMT):
ok
rameshthoomu (Thu, 31 May 2018 17:47:29 GMT):
but as it is huge change, you have to split that into multiple patchsets..
jtclark (Thu, 31 May 2018 17:47:34 GMT):
I gotcha
jtclark (Thu, 31 May 2018 17:47:36 GMT):
I can do that.
rameshthoomu (Thu, 31 May 2018 17:47:42 GMT):
like this https://gerrit.hyperledger.org/r/#/c/22271/
jtclark (Thu, 31 May 2018 17:47:52 GMT):
did you look at my update to https://gerrit.hyperledger.org/r/#/c/22173/
jtclark (Thu, 31 May 2018 17:49:01 GMT):
I do have one more thing to add
jtclark (Thu, 31 May 2018 17:49:15 GMT):
which is the comment about the tar command at the end. what's that for, exactly?
rameshthoomu (Thu, 31 May 2018 17:50:12 GMT):
ok. will look into this
jtclark (Thu, 31 May 2018 17:51:04 GMT):
took out alot of the obvious stuff. just lemme know what needs to be changed (if anything) and I'll push this one quickly.
jtclark (Thu, 31 May 2018 17:51:32 GMT):
we can just get this done, and talk about stuff again once we're past the 1.2 release
VinayChaudharyOfficial (Fri, 01 Jun 2018 04:54:40 GMT):
Has joined the channel.
jtclark (Fri, 01 Jun 2018 21:16:24 GMT):
@rameshthoomu, @sambhavdutt, @jwagantall - plz review: https://gerrit.hyperledger.org/r/#/c/22695/
jwagantall (Fri, 01 Jun 2018 21:17:48 GMT):
yep
rameshthoomu (Fri, 01 Jun 2018 21:25:22 GMT):
https://gerrit.hyperledger.org/r/#/c/22271/
https://gerrit.hyperledger.org/r/#/c/22695/
cbf (Sat, 02 Jun 2018 11:53:10 GMT):
https://gerrit.hyperledger.org/r/c/22543/ @rameshthoomu something's broken in fabric-samples CI... this change has nothing to do with policy
cbf (Sat, 02 Jun 2018 11:53:19 GMT):
and it runs fine locally
rameshthoomu (Sat, 02 Jun 2018 13:41:41 GMT):
channel creation failed while testing byfn on nodejs chaincode (`echo y | ./byfn.sh -m up -l node -t 60`) but I see the latest e2e test on release-1.1 is passed https://jenkins.hyperledger.org/view/Daily/job/fabric-end-2-end-daily-release-1.1-x86_64/ -- re-triggered again
rameshthoomu (Sat, 02 Jun 2018 13:41:41 GMT):
channel creation failed while testing byfn on nodejs chaincode ( `echo y | ./byfn.sh -m up -l node -t 60` ) but I see the latest e2e test on release-1.1 is passed https://jenkins.hyperledger.org/view/Daily/job/fabric-end-2-end-daily-release-1.1-x86_64/ -- re-triggered again
cbf (Sat, 02 Jun 2018 15:35:31 GMT):
still broken
rameshthoomu (Sun, 03 Jun 2018 01:18:14 GMT):
Not sure what change your patchset failing node test.. I am suspecting some container are still left over from the previous and it's not clearing them with your change set..
I have submitted WIP change https://gerrit.hyperledger.org/r/#/c/22701/ and got +1 and fabric-samples is not broken as the existing fabric-sample tests are working as expected.
rameshthoomu (Sun, 03 Jun 2018 01:18:14 GMT):
Not sure what in change your patchset causing failure.. I am suspecting some container are left over from the previous test and your change set is not clearing them.
I have submitted WIP change https://gerrit.hyperledger.org/r/#/c/22701/ and got +1 and fabric-samples is not broken as the existing fabric-sample tests are working as expected.
cbf (Sun, 03 Jun 2018 12:24:57 GMT):
not sure what's amiss with this... have submitted a new cp version
jtclark (Sun, 03 Jun 2018 17:02:37 GMT):
@rameshthoomu, @sambhavdutt, @jwagantall - plz review: https://gerrit.hyperledger.org/r/#/c/22709/
sambhavdutt (Sun, 03 Jun 2018 17:03:16 GMT):
@jtclark sure, will look into it
jtclark (Sun, 03 Jun 2018 17:03:49 GMT):
@sambhavdutt thx!
jtclark (Sun, 03 Jun 2018 17:03:57 GMT):
I've one more to submit
jtclark (Mon, 04 Jun 2018 02:13:15 GMT):
@rameshthoomu, @sambhavdutt, @jwagantall - plz review: https://gerrit.hyperledger.org/r/#/c/22715/
jwagantall (Mon, 04 Jun 2018 16:03:00 GMT):
@jtclark reviewing..
jwagantall (Mon, 04 Jun 2018 16:03:16 GMT):
your 2nd change has a ci issue..
jtclark (Mon, 04 Jun 2018 16:06:38 GMT):
@jwagantall I'll check
jtclark (Mon, 04 Jun 2018 16:25:04 GMT):
@rameshthoomu - https://gerrit.hyperledger.org/r/22733 <--- verify job update
jtclark (Mon, 04 Jun 2018 16:25:17 GMT):
I'll add another patch for the merge job
rameshthoomu (Mon, 04 Jun 2018 16:25:41 GMT):
ok.. so you will amend right?
jtclark (Mon, 04 Jun 2018 16:25:54 GMT):
sure, I can add it to this patchset.
jtclark (Mon, 04 Jun 2018 16:28:24 GMT):
@rameshthoomu done.
rameshthoomu (Mon, 04 Jun 2018 17:25:32 GMT):
@sykesm @latitiah @jwagantall pls review https://gerrit.hyperledger.org/r/#/c/22737/
rameshthoomu (Mon, 04 Jun 2018 17:25:56 GMT):
@jwagantall wait for +1 from other reviewers
jwagantall (Mon, 04 Jun 2018 17:26:06 GMT):
yea.. reviewing the change too
rameshthoomu (Mon, 04 Jun 2018 17:26:12 GMT):
sure.. thanks
jtclark (Mon, 04 Jun 2018 18:06:39 GMT):
@jwagantall updated this patch set: https://gerrit.hyperledger.org/r/#/c/22715/
jwagantall (Mon, 04 Jun 2018 18:06:54 GMT):
thnaks! ill review it soon..
jwagantall (Mon, 04 Jun 2018 18:15:37 GMT):
@jtclark just check the CI issue... everything else so far looks ok
jtclark (Mon, 04 Jun 2018 18:51:33 GMT):
@jwagantall fixed: https://gerrit.hyperledger.org/r/#/c/22715/
jwagantall (Mon, 04 Jun 2018 18:51:48 GMT):
thanks.. let me see...
jwagantall (Mon, 04 Jun 2018 18:53:24 GMT):
Looks good to me approved
rameshthoomu (Mon, 04 Jun 2018 18:56:57 GMT):
http://ci-docs.readthedocs.io/en/latest/index.html#
rameshthoomu (Mon, 04 Jun 2018 19:47:47 GMT):
@jwagantall I think you have merged the integration test change..
jwagantall (Mon, 04 Jun 2018 19:48:07 GMT):
yea.. it had 2 +1's
rameshthoomu (Mon, 04 Jun 2018 19:48:12 GMT):
Could you please enable the Integration-Test on gerrit voting?
rameshthoomu (Mon, 04 Jun 2018 19:48:18 GMT):
is that disabled now?
jwagantall (Mon, 04 Jun 2018 19:49:01 GMT):
not that i know of... it should be enabled already from the fabric project rules
rameshthoomu (Mon, 04 Jun 2018 19:49:13 GMT):
ok let me do quick test
jwagantall (Mon, 04 Jun 2018 19:49:18 GMT):
sure..
rameshthoomu (Mon, 04 Jun 2018 20:29:04 GMT):
@jwagantall verified few builds on integrationTest job and seems changes are correct..
cbf (Wed, 06 Jun 2018 18:07:20 GMT):
@rameshthoomu this CR just does not like me... I started from a clean repo, release-1.1 branch and applied the changes manually to create a new CR... same unrelated failure
cbf (Wed, 06 Jun 2018 18:07:23 GMT):
https://gerrit.hyperledger.org/r/c/22707/
rameshthoomu (Wed, 06 Jun 2018 19:00:51 GMT):
@jtclark could you please check above issue.. FYI it's happening only with this patch..
rameshthoomu (Wed, 06 Jun 2018 19:01:35 GMT):
if you don't find enough information from the prod logs, enable logs in sandbox and test this patchset
jtclark (Wed, 06 Jun 2018 19:07:02 GMT):
ok
jtclark (Wed, 06 Jun 2018 20:19:06 GMT):
@rameshthoomu currently testing https://jira.hyperledger.org/browse/FAB-10066
jtclark (Wed, 06 Jun 2018 20:19:28 GMT):
some problems there- working on it here: https://jenkins.hyperledger.org/sandbox/job/fabric-byfn-verify-x86_64/7/console
jtclark (Thu, 07 Jun 2018 13:33:40 GMT):
Good Morning :sunrise:
jtclark (Thu, 07 Jun 2018 15:10:46 GMT):
@rameshthoomu testing the issue mentioned by @cbf in the sandbox. I'll keep you posted.
jtclark (Thu, 07 Jun 2018 15:10:51 GMT):
https://jenkins.hyperledger.org/sandbox/job/fabric-byfn-verify-x86_64/
jtclark (Thu, 07 Jun 2018 15:24:35 GMT):
@rameshthoomu this initial run of the code seems to be working: https://jenkins.hyperledger.org/sandbox/job/fabric-byfn-verify-x86_64/1/console
jtclark (Thu, 07 Jun 2018 15:25:22 GMT):
next iteration will be to update the GERRIT_BRANCH build parameter to be `release-1.1`
jtclark (Thu, 07 Jun 2018 15:25:22 GMT):
next run will be to update the GERRIT_BRANCH build parameter to be `release-1.1`
jtclark (Thu, 07 Jun 2018 15:38:11 GMT):
@rameshthoomu this job completed successfully: https://jenkins.hyperledger.org/sandbox/job/fabric-byfn-verify-x86_64/1/consoleFull
jtclark (Thu, 07 Jun 2018 15:49:50 GMT):
@cbf not quite working yet. need to cherry-pick your CR to the release-1.1 branch- I previously reported that this was working, but it was from the master branch.
aambati (Thu, 07 Jun 2018 16:54:04 GMT):
@rameshthoomu Can u pls check https://jenkins.hyperledger.org/job/fabric-ca-verify-s390x/3248/, i don't see that error when i do make format in my workspace...Even after i fixed the formatting error, it is still failing...it is as though CI is not picking up latest change.
rameshthoomu (Thu, 07 Jun 2018 17:12:26 GMT):
let me check
aambati (Thu, 07 Jun 2018 17:17:59 GMT):
@rameshthoomu never mind...i repushed , it seems to went further this time...but we need to figure out why make format fails in CI but works on Mac
aambati (Thu, 07 Jun 2018 17:17:59 GMT):
@rameshthoomu never mind...i repushed , it seems to went further this time...but we need to figure out why make format fails in CI but does not fail on Mac
rameshthoomu (Thu, 07 Jun 2018 17:18:47 GMT):
we execute `make ci-tests` target.. I think you also execute the same right
rameshthoomu (Thu, 07 Jun 2018 17:19:04 GMT):
ok
firas.qutishat (Thu, 07 Jun 2018 17:25:55 GMT):
Hi
I trying to use fabric-baseos image 0.4.8 but there is no x86_64-0.4.8 tag in docker hub
https://hub.docker.com/r/hyperledger/fabric-baseos/tags/
rameshthoomu (Thu, 07 Jun 2018 17:27:23 GMT):
it should be on amd64-0.4.8 tag
firas.qutishat (Thu, 07 Jun 2018 17:28:10 GMT):
thanks
Baha-sk (Thu, 07 Jun 2018 17:44:28 GMT):
Has joined the channel.
cbf (Thu, 07 Jun 2018 17:59:31 GMT):
@rameshthoomu hmmm I think I know what's going on... I must be deleting an image I shouldn't be... I'll add some debugging
cbf (Thu, 07 Jun 2018 18:05:29 GMT):
no, that isn't it either... already seeing multiple tests run this is a puzzlement
rameshthoomu (Thu, 07 Jun 2018 18:06:05 GMT):
yes.. except node js chaincode tests .. rest all tests are working..
rameshthoomu (Thu, 07 Jun 2018 18:06:25 GMT):
Will look into this in sometime.. Pushing last change of pipeline script
cbf (Thu, 07 Jun 2018 18:09:53 GMT):
this is low priority, I can make it WIP for now
cbf (Thu, 07 Jun 2018 18:11:06 GMT):
@rameshthoomu where do we stand on having only one set of images tagged/day?
cbf (Thu, 07 Jun 2018 18:11:06 GMT):
@rameshthoomu where do we stand on having only one set of images tagged stable/day?
rameshthoomu (Thu, 07 Jun 2018 18:12:01 GMT):
yes.. We pushed stable images with 1.2.0-stable tag and working on Downstream jobs to kickoff (performance, svt and sdk's)
rameshthoomu (Thu, 07 Jun 2018 18:12:50 GMT):
couple of patches are on in queue.. Target to finish them by EOD today
jtclark (Thu, 07 Jun 2018 18:17:43 GMT):
@rameshthoomu latest test attempt: https://jenkins.hyperledger.org/sandbox/job/fabric-byfn-verify-x86_64/5/
abraham (Fri, 08 Jun 2018 04:19:09 GMT):
Has joined the channel.
jtclark (Fri, 08 Jun 2018 10:26:57 GMT):
@rameshthoomu, @cbf - I captured the above issue (now marked WIP) in the following JIRA task: https://jira.hyperledger.org/browse/FAB-10584
rickr (Fri, 08 Jun 2018 15:00:58 GMT):
I think there are issues with this machine NODE_NAME=prd-ubuntu1604-x86_64-4c-16g-4815
```
10:17:40 [ERROR] /w/workspace/fabric-sdk-java-verify-1.0.0-x86_64/src/main/java/org/hyperledger/fabric/sdk/security/CryptoPrimitives.java:[325,46] cannot access java.security.SignatureSpi
10:17:40 bad class file: /usr/lib/jvm/java-8-openjdk-amd64/lib/ct.sym(META-INF/sym/rt.jar/java/security/SignatureSpi.class)
10:17:40 unable to access file: corrupted zip file
```
I keep seeing this occasionally and theory it's on one of the machines
https://jenkins.hyperledger.org/job/fabric-sdk-java-verify-1.0.0-x86_64/851/console
Don't know if / who can rebuild it or fix that zip .. or can log on to it and investigate
rickr (Fri, 08 Jun 2018 15:02:22 GMT):
@rameshthoomu @rjones ^^
rjones (Fri, 08 Jun 2018 15:02:23 GMT):
Has joined the channel.
rameshthoomu (Fri, 08 Jun 2018 15:02:43 GMT):
@jwagantall could you please check this
jwagantall (Fri, 08 Jun 2018 15:45:39 GMT):
checking..
jtclark (Fri, 08 Jun 2018 15:51:12 GMT):
@rameshthoomu now that FAB-10584 is WIP for now, I'm back to finishing up FAB-10066
rameshthoomu (Fri, 08 Jun 2018 15:52:40 GMT):
@jtclark 10066 is in-progress for master branch.. But would like to split the existing job to release branches
rameshthoomu (Fri, 08 Jun 2018 15:52:46 GMT):
Could you please work on that
rameshthoomu (Fri, 08 Jun 2018 15:52:48 GMT):
https://gerrit.hyperledger.org/r/#/c/22443/
rameshthoomu (Fri, 08 Jun 2018 15:53:33 GMT):
I am not using 10066 for the above patchset but you can use existing jobs for release-1.1 and release-1.0 branches
jtclark (Fri, 08 Jun 2018 15:53:53 GMT):
so 10066 will get merged, but it will just be for pulling the images for master branch tests?
jtclark (Fri, 08 Jun 2018 15:54:15 GMT):
@rameshthoomu :point_up_tone2:
rameshthoomu (Fri, 08 Jun 2018 15:55:58 GMT):
Modify this change only to release branches https://gerrit.hyperledger.org/r/#/c/22733/
jtclark (Fri, 08 Jun 2018 15:57:14 GMT):
I can do that, but 10066 modifies the the job to not build docker images
rameshthoomu (Fri, 08 Jun 2018 15:57:56 GMT):
that's now happening with pipeline..
rameshthoomu (Fri, 08 Jun 2018 15:58:11 GMT):
as we have images only from master branch..
jtclark (Fri, 08 Jun 2018 15:58:54 GMT):
hmmm
rameshthoomu (Fri, 08 Jun 2018 15:59:16 GMT):
Create a Makefile and drive the byfn and eyfn tests through it..
rameshthoomu (Fri, 08 Jun 2018 15:59:45 GMT):
for release branches..
jtclark (Fri, 08 Jun 2018 15:59:54 GMT):
ok which one do we want to go first?
rameshthoomu (Fri, 08 Jun 2018 16:00:08 GMT):
10066
rameshthoomu (Fri, 08 Jun 2018 16:00:35 GMT):
it's all parallel tasks.. My changes are already pushed for master branch with pipeline
jtclark (Fri, 08 Jun 2018 16:00:45 GMT):
it can't be.
jtclark (Fri, 08 Jun 2018 16:00:53 GMT):
https://gerrit.hyperledger.org/r/#/c/22733/5/jjb/fabric-samples/fabric-samples-jobs.yaml
jtclark (Fri, 08 Jun 2018 16:01:04 GMT):
fabric-samples is modified
jtclark (Fri, 08 Jun 2018 16:01:04 GMT):
fabric-samples-jobs is modified
rameshthoomu (Fri, 08 Jun 2018 16:01:24 GMT):
ok let me add review comments
jtclark (Fri, 08 Jun 2018 16:01:35 GMT):
https://gerrit.hyperledger.org/r/#/c/22761/4/jjb/fabric-samples/fabric-samples-jobs.yaml
jtclark (Fri, 08 Jun 2018 16:01:46 GMT):
fabric-samples-jobs is modified here too.
jtclark (Fri, 08 Jun 2018 16:01:59 GMT):
22761 will step on 22733
rameshthoomu (Fri, 08 Jun 2018 16:03:58 GMT):
ok I have modified my patchset..
rameshthoomu (Fri, 08 Jun 2018 16:04:58 GMT):
or you can amend to my patchset.. which ever you like
rameshthoomu (Fri, 08 Jun 2018 16:06:41 GMT):
let me modify that
jtclark (Fri, 08 Jun 2018 16:08:43 GMT):
ok
jtclark (Fri, 08 Jun 2018 16:08:57 GMT):
I see where your patch is for master, not release, is this right?
jtclark (Fri, 08 Jun 2018 16:09:15 GMT):
b/c I thought 10066 is for master
jtclark (Fri, 08 Jun 2018 16:12:59 GMT):
@rameshthoomu :point_up_tone2:
rjones (Fri, 08 Jun 2018 17:35:53 GMT):
@rickr: I no longer do tech support, please ask @jwagantall
rjones (Fri, 08 Jun 2018 17:36:02 GMT):
Has left the channel.
jwagantall (Fri, 08 Jun 2018 17:37:21 GMT):
@rickr if this is regarding the build issue.. i am checking on it
jwagantall (Fri, 08 Jun 2018 17:38:47 GMT):
@rickr do you have a Jenkins link to the build where this is happening? since these are dynamic nodes is not easy to login into it and see why this is failing as the
workspace gets removed as soon as the job ends
rickr (Fri, 08 Jun 2018 17:40:23 GMT):
console output https://jenkins.hyperledger.org/job/fabric-sdk-java-verify-1.0.0-x86_64/851/console
rickr (Fri, 08 Jun 2018 17:40:59 GMT):
build 851
rickr (Fri, 08 Jun 2018 17:54:39 GMT):
I thought this would help I think there are issues with this machine NODE_NAME=prd-ubuntu1604-x86_64-4c-16g-4815
rickr (Fri, 08 Jun 2018 17:55:57 GMT):
I don't it's in the workspace . I'm suspecting the Java install on that machine is not up to par.
jwagantall (Fri, 08 Jun 2018 18:12:20 GMT):
i can update the packer image... let me see
jwagantall (Fri, 08 Jun 2018 18:30:48 GMT):
@rickr there was a new image available.. i have updated to that new one and ran the build once but i guess this issue is more sporadic .. right?
jwagantall (Fri, 08 Jun 2018 18:31:04 GMT):
please let me know if you see it again ..
rameshthoomu (Fri, 08 Jun 2018 22:41:26 GMT):
@jtclark I have pushed change here https://gerrit.hyperledger.org/r/#/c/22761/
rameshthoomu (Fri, 08 Jun 2018 22:41:43 GMT):
with this fabric-sdk-node jobs are ready with nexus images
rameshthoomu (Fri, 08 Jun 2018 22:42:12 GMT):
please check the change and let me know if any changes required
jtclark (Fri, 08 Jun 2018 22:42:20 GMT):
Ok
cbf (Mon, 11 Jun 2018 12:25:18 GMT):
@rameshthoomu presume this will be post 1.2? https://gerrit.hyperledger.org/r/c/22119/
cbf (Mon, 11 Jun 2018 12:25:44 GMT):
same with any dependency on new version of baseimage
rameshthoomu (Mon, 11 Jun 2018 14:33:53 GMT):
yes.. We can push this post 1.2 as it is depending on baseimage
cbf (Mon, 11 Jun 2018 16:55:43 GMT):
@rameshthoomu @tongli while I agree with Tong's observation, we can refactor later. I would prefer we didn't hold up progress, please as we need to apply this to other repos.
cbf (Mon, 11 Jun 2018 16:57:52 GMT):
because when all is said and done, this could simply use the scripts/bootstrap.sh script with some tweaks to be able to load nexus images
cbf (Mon, 11 Jun 2018 16:58:23 GMT):
but again, we can refactor
rameshthoomu (Mon, 11 Jun 2018 17:05:20 GMT):
yes I agree with you.. we can refactor this later.
rameshthoomu (Mon, 11 Jun 2018 17:06:04 GMT):
Once this change is merged, will ask @jwagantall to re-enable pipeline job in fabric-samples
rameshthoomu (Mon, 11 Jun 2018 17:07:48 GMT):
@jwagantall once this change (https://gerrit.hyperledger.org/r/#/c/22443/) is merged, could you please revert this change https://gerrit.hyperledger.org/r/#/c/22945/
jwagantall (Mon, 11 Jun 2018 19:16:59 GMT):
waiting for https://gerrit.hyperledger.org/r/#/c/22443/ , do we have any concerns about this?
cbf (Mon, 11 Jun 2018 20:58:30 GMT):
@rameshthoomu @jtclark any reason this is being tracked as a bug and not a task? https://jira.hyperledger.org/browse/FAB-10598
jtclark (Mon, 11 Jun 2018 20:59:31 GMT):
that's a question for @rameshthoomu..... not sure why it was classified this way....
jtclark (Mon, 11 Jun 2018 20:59:48 GMT):
should be a task, IMHO.
cbf (Mon, 11 Jun 2018 21:02:14 GMT):
made it a task
cbf (Tue, 12 Jun 2018 16:11:37 GMT):
@rameshthoomu https://jira.hyperledger.org/browse/FAB-10294
cbf (Tue, 12 Jun 2018 16:11:58 GMT):
I pushed script for fabric and fabric-baseimage that pushes manifest via template
cbf (Tue, 12 Jun 2018 16:12:07 GMT):
can you please test that out against nexus?
cbf (Tue, 12 Jun 2018 16:12:21 GMT):
(or someone with the login)
rameshthoomu (Tue, 12 Jun 2018 16:15:29 GMT):
ok will test and let you know.. What abt fabric-ca?
cbf (Tue, 12 Jun 2018 19:13:13 GMT):
coming
cbf (Tue, 12 Jun 2018 19:13:17 GMT):
working on another CR
rameshthoomu (Wed, 13 Jun 2018 06:24:22 GMT):
@cbf I have tested fabric multiarch patch some extent and added my comments here https://gerrit.hyperledger.org/r/#/c/22981/
rameshthoomu (Wed, 13 Jun 2018 06:25:20 GMT):
observed few issues.. Will test full multiarch functionality tomorrow morning
sstone1 (Wed, 13 Jun 2018 09:18:24 GMT):
https://jenkins.hyperledger.org/job/fabric-verify-integration-tests-x86_64/146/console
sstone1 (Wed, 13 Jun 2018 09:18:34 GMT):
as far as i can see it failed because it got a timeout stopping couchdb
sstone1 (Wed, 13 Jun 2018 09:18:49 GMT):
what am i meant to do in this case? how do i respin it?
cbf (Wed, 13 Jun 2018 10:34:24 GMT):
@rameshthoomu why do you think that CheckAvailability is preferable to a much simpler docker pull?
cbf (Wed, 13 Jun 2018 10:49:04 GMT):
note that CheckAvailability won't work against nexus
rameshthoomu (Wed, 13 Jun 2018 13:18:50 GMT):
@cbf I thought, docker pull is not required as we have an option to verify the image availability through docker api also the verification we will do on dockerhub account
rameshthoomu (Wed, 13 Jun 2018 13:19:13 GMT):
But I am ok with any approach
jtclark (Wed, 13 Jun 2018 13:22:22 GMT):
@rameshthoomu good morning. just checked all of the jobs... everything looks ok :sunny:
rameshthoomu (Wed, 13 Jun 2018 13:33:40 GMT):
Oh ok so you have pushed the changes which I have asked yesterday and all jobs are now good for master, release branches or is this yesterday's status?
rameshthoomu (Wed, 13 Jun 2018 13:34:02 GMT):
oh ignore my comment
rameshthoomu (Wed, 13 Jun 2018 13:34:05 GMT):
got it now..
rameshthoomu (Wed, 13 Jun 2018 13:34:23 GMT):
Did you push changes to publish thirdparty images to nexus?
rameshthoomu (Wed, 13 Jun 2018 13:34:42 GMT):
let me know if you need any help
rameshthoomu (Wed, 13 Jun 2018 13:38:43 GMT):
@jtclark you also have to verify the svt and pte jobs (fabric-test-svt-x86_64 , fabric-test-pte-x86_64)
I see few issues in svt job.. I am fixing those two issues
rameshthoomu (Wed, 13 Jun 2018 13:38:56 GMT):
FAB-10620
jtclark (Wed, 13 Jun 2018 13:52:00 GMT):
@rameshthoomu I'm going to push my changes for publishing the thirdparty images to nexus this morning
jtclark (Wed, 13 Jun 2018 13:52:35 GMT):
@rameshthoomu ok, I'll add those to my list
rameshthoomu (Wed, 13 Jun 2018 13:52:51 GMT):
so you are ready with the change?
jtclark (Wed, 13 Jun 2018 13:54:02 GMT):
@rameshthoomu let me ask you - I'm implementing this by adding a new job via the fabric-images-release-jobs.yaml
jtclark (Wed, 13 Jun 2018 13:55:02 GMT):
I have the script ready, but we're using templates there, so looks like I will need a new template to add a buildthirdparty builder to the JJB
jtclark (Wed, 13 Jun 2018 13:55:23 GMT):
unless I can create these two jobs w/o using the template?
jtclark (Wed, 13 Jun 2018 13:57:15 GMT):
@rameshthoomu ^
rameshthoomu (Wed, 13 Jun 2018 13:58:19 GMT):
see this job jjb/releases/fabric-baseimage-images-release-template.yaml
rameshthoomu (Wed, 13 Jun 2018 13:58:19 GMT):
see this job template jjb/releases/fabric-baseimage-images-release-template.yaml
jtclark (Wed, 13 Jun 2018 14:00:27 GMT):
ok
cbf (Wed, 13 Jun 2018 14:40:54 GMT):
@rameshthoomu I found the other approach more complicated than we need... I did address your other issue.
rameshthoomu (Wed, 13 Jun 2018 14:41:33 GMT):
ok
rameshthoomu (Wed, 13 Jun 2018 18:17:04 GMT):
@cbf builds with "make docker" is broken with https://github.com/golang/go/issues/25872
cbf (Wed, 13 Jun 2018 18:30:47 GMT):
wonderful
rameshthoomu (Wed, 13 Jun 2018 18:43:07 GMT):
Seems it's fixed now..
rameshthoomu (Mon, 18 Jun 2018 20:51:33 GMT):
@cbf if this is a valid change (https://gerrit.hyperledger.org/r/#/c/23277/), will push the same in fabric-ca repo
rameshthoomu (Tue, 19 Jun 2018 04:17:19 GMT):
@latitiah Could you please verify Integration test failure https://jenkins.hyperledger.org/view/Daily/job/fabric-nightly-release-job-x86_64/20/console
nirro (Tue, 19 Jun 2018 12:56:28 GMT):
hi, is there any issue with the Jenkins server?
I see in several different CRs failures, not related to the change, the failures are in SmokeTest/UnitTest/IntegrationTest inconsistently.. each time in different tests
rameshthoomu (Tue, 19 Jun 2018 13:33:55 GMT):
@jtclark could you please check this
jtclark (Tue, 19 Jun 2018 13:44:34 GMT):
@rameshthoomu yes, I'll look into it
jtclark (Tue, 19 Jun 2018 13:44:52 GMT):
in fact, I just checked all of the jobs:
```
## Jun 19, 2018
### Daily
* fabric-end-2-end-daily-master-x86_64
* fabric-nightly-release-job-x86_64
### fabric
* fabric-smoke-tests-x86_64*
* fabric-verify-integration-tests-x86_64*
* fabric-verify-unit-tests-x86_64*
### fabric-baseimage
* fabric-baseimage-ppc64le-nexus-release-jobs
### fabric-sdk-go
* fabric-sdk-go-tests-verify-s390x*
```
jtclark (Tue, 19 Jun 2018 13:45:28 GMT):
the ones with the `*` are the jobs I wasn't sure needed to have JIRA tasks opened for them....
jtclark (Tue, 19 Jun 2018 13:46:04 GMT):
I'll start with the fabric jobs first.
rameshthoomu (Tue, 19 Jun 2018 13:55:20 GMT):
@jtclark I was referring @nirro job failure..
rameshthoomu (Tue, 19 Jun 2018 13:55:30 GMT):
@nirro could you please give us the failed job
rameshthoomu (Tue, 19 Jun 2018 13:55:36 GMT):
will analyze
nirro (Tue, 19 Jun 2018 13:56:13 GMT):
here is one job for example:
https://gerrit.hyperledger.org/r/#/c/22857/
rameshthoomu (Tue, 19 Jun 2018 13:56:43 GMT):
@jtclark as said, you no need analyze verify jobs failures until they are failing consistently..
rameshthoomu (Tue, 19 Jun 2018 13:58:23 GMT):
@nirro I see images are not pulled in smoke and integration test job.
rameshthoomu (Tue, 19 Jun 2018 14:00:33 GMT):
@nirro you have rebased your patch that created patchset#6 (If there is not change in the code, CI don't trigger jobs)
rameshthoomu (Tue, 19 Jun 2018 14:01:26 GMT):
and posted comments to trigger the jobs which failed to pull the images as no images and binaries available on the rebased commit
jtclark (Tue, 19 Jun 2018 14:01:30 GMT):
@rameshthoomu here is the failure reason for the smoke test:
```
Error: timeout waiting for channel creation
!!!!!!!!!!!!!!! Channel creation failed !!!!!!!!!!!!!!!!
================== ERROR !!! FAILED to execute End-2-End Scenario ==================
```
jtclark (Tue, 19 Jun 2018 14:01:30 GMT):
@rameshthoomu here is the failure I'm seeing for the smoke test:
```
Error: timeout waiting for channel creation
!!!!!!!!!!!!!!! Channel creation failed !!!!!!!!!!!!!!!!
================== ERROR !!! FAILED to execute End-2-End Scenario ==================
```
nirro (Tue, 19 Jun 2018 14:01:58 GMT):
yes, I ran the smoke and other manually, the questions is why images are not pulled in the tests..
rameshthoomu (Tue, 19 Jun 2018 14:04:36 GMT):
@nirro I have posted the reason above
rameshthoomu (Tue, 19 Jun 2018 14:06:19 GMT):
Note: When you want to trigger a specific job, you can trigger the job by posting a comment against the job (ex: Run SmokeTest)
rameshthoomu (Tue, 19 Jun 2018 14:09:41 GMT):
I just posted comment (VerifyBuild) in your patchset and let me see how this will go
rameshthoomu (Tue, 19 Jun 2018 14:40:06 GMT):
@nirro pls don;t rebase your changeset... It's working as expected.. I will take care of this changeset
nirro (Tue, 19 Jun 2018 14:40:48 GMT):
sure, I actually had to rebase since there were changes in different CRs
rameshthoomu (Tue, 19 Jun 2018 14:41:20 GMT):
Ok I think you did the final rebase right?
nirro (Tue, 19 Jun 2018 14:42:52 GMT):
as far as I know now I think it's final, but some of the CRs I'm depending on are not in my scope.. so I hope I won't need to rebase again :/
rameshthoomu (Tue, 19 Jun 2018 15:27:50 GMT):
@nirro I see Integration tests are failing.. https://jenkins.hyperledger.org/job/fabric-verify-integration-tests-x86_64/282/console. I think it's not related to your change..
rameshthoomu (Tue, 19 Jun 2018 15:28:32 GMT):
@latitiah is analyzing Integration Test failures..
rameshthoomu (Tue, 19 Jun 2018 15:50:58 GMT):
@jtclark Could you please create a High priority bug on integration test failures.. Reference Builds are here
https://jenkins.hyperledger.org/view/Daily/job/fabric-nightly-release-job-x86_64/20/consoleFull
https://jenkins.hyperledger.org/view/fabric/job/fabric-verify-integration-tests-x86_64/285/console
rameshthoomu (Tue, 19 Jun 2018 15:50:58 GMT):
@jtclark Could you please create a High priority bug on integration test failures.. Reference Builds are here
https://jenkins.hyperledger.org/view/Daily/job/fabric-nightly-release-job-x86_64/20/consoleFull
https://jenkins.hyperledger.org/view/fabric/job/fabric-verify-integration-tests-x86_64/285/console
this is blocking us to publish stable build images
jtclark (Tue, 19 Jun 2018 15:51:21 GMT):
Sure thing.
jtclark (Tue, 19 Jun 2018 15:58:52 GMT):
@rameshthoomu just finished creating this one: https://jira.hyperledger.org/browse/FAB-10713
jtclark (Tue, 19 Jun 2018 15:59:09 GMT):
the one you mentioned is next.
latitiah (Tue, 19 Jun 2018 16:11:40 GMT):
I'm using https://jira.hyperledger.org/browse/FAB-10662 for the timeout issue...
jtclark (Tue, 19 Jun 2018 17:44:21 GMT):
@rameshthoomu, https://jira.hyperledger.org/browse/FAB-10715
jtclark (Tue, 19 Jun 2018 17:44:32 GMT):
@latitiah :point_up_tone2: FYI
jwagantall (Tue, 19 Jun 2018 17:44:36 GMT):
Team!, There will be a Jenkins restart scheduled for 12:00pm PT time. Looks like some job data is not being picked up properly and we want to restart the server to refresh the configuration.
latitiah (Tue, 19 Jun 2018 20:13:42 GMT):
@rameshthoomu : https://gerrit.hyperledger.org/r/#/c/23343/
rameshthoomu (Tue, 19 Jun 2018 20:31:59 GMT):
Thanks @latitiah
rameshthoomu (Wed, 20 Jun 2018 06:00:48 GMT):
@aambati Could you please check fabric-ca binaries issue in master branch see here FAB-10737
rameshthoomu (Wed, 20 Jun 2018 13:20:13 GMT):
@latitiah Seems this is new error https://jenkins.hyperledger.org/view/Daily/job/fabric-nightly-release-job-x86_64/23/console Could you please check
harsha (Wed, 20 Jun 2018 14:42:39 GMT):
@rjones @jwagantall @rameshthoomu Can you kindly grant me permission to trigger job in Sandbox Jenkins env plz.
https://jenkins.hyperledger.org/sandbox/job/fabric-daily-ppc64le/
rjones (Wed, 20 Jun 2018 14:42:39 GMT):
Has joined the channel.
rjones (Wed, 20 Jun 2018 14:44:16 GMT):
I don't do tech support any more. please file a ticket: helpdesk@hyperledger.org
rjones (Wed, 20 Jun 2018 14:44:25 GMT):
Has left the channel.
latitiah (Wed, 20 Jun 2018 14:48:47 GMT):
@rameshthoomu: looks like another timeout issue.
rameshthoomu (Wed, 20 Jun 2018 14:49:19 GMT):
@harsha will do
cbf (Wed, 20 Jun 2018 16:19:29 GMT):
ramesh... do we need a script to copy/or rename the binaries tarballs for the release?
cbf (Wed, 20 Jun 2018 16:19:29 GMT):
@rameshthoomu ^^
cbf (Wed, 20 Jun 2018 16:19:51 GMT):
ugh
cbf (Wed, 20 Jun 2018 16:19:51 GMT):
do we need a script to rename or copy the binaries tarballs to the release location?
rameshthoomu (Wed, 20 Jun 2018 16:22:21 GMT):
I have pushed a script to fabric to publish images to dockerhub https://gerrit.hyperledger.org/r/#/c/23361/3/scripts/pull_build_artifacts.sh
rameshthoomu (Wed, 20 Jun 2018 16:23:12 GMT):
will update the same for binaries
jwagantall (Wed, 20 Jun 2018 16:27:21 GMT):
@harsha I can add you
jwagantall (Wed, 20 Jun 2018 16:30:52 GMT):
@harsha added now your LFID "harsha"
harsha (Wed, 20 Jun 2018 17:47:29 GMT):
@jwagantall Thank you !!
rameshthoomu (Wed, 20 Jun 2018 18:02:34 GMT):
@cbf think similar change has to go in fabric-ca repo https://gerrit.hyperledger.org/r/#/c/22993/
rameshthoomu (Wed, 20 Jun 2018 18:02:34 GMT):
is it merged or open patchset?
cbf (Wed, 20 Jun 2018 18:03:02 GMT):
Gari did make a change
cbf (Wed, 20 Jun 2018 18:03:06 GMT):
not exactly the same
rameshthoomu (Wed, 20 Jun 2018 18:03:55 GMT):
is it merged or open patchset?
cbf (Wed, 20 Jun 2018 18:08:50 GMT):
merged
rameshthoomu (Wed, 20 Jun 2018 18:14:00 GMT):
ok
rameshthoomu (Wed, 20 Jun 2018 19:49:01 GMT):
@harsha Created JIRA item for unit-test failures in ppc64le FAB-10778
rameshthoomu (Wed, 20 Jun 2018 19:49:22 GMT):
Thanks for all the help
harsha (Thu, 21 Jun 2018 02:15:41 GMT):
Is Sandbox env down ?
rameshthoomu (Thu, 21 Jun 2018 02:16:24 GMT):
it seems . @jwagantall ^^
jwagantall (Thu, 21 Jun 2018 02:16:39 GMT):
yeaaa.. i think it is.. i was also using it :'(
jwagantall (Thu, 21 Jun 2018 02:16:44 GMT):
let me report it :'( :'(
jwagantall (Thu, 21 Jun 2018 02:25:05 GMT):
should be back now
jwagantall (Thu, 21 Jun 2018 02:27:17 GMT):
actually.. let me try restarting it..
rameshthoomu (Thu, 21 Jun 2018 02:29:02 GMT):
let us know once you restart
rameshthoomu (Thu, 21 Jun 2018 02:53:31 GMT):
seems issue still exists in sandbox
jwagantall (Thu, 21 Jun 2018 03:02:04 GMT):
the team is looking into it..
jwagantall (Thu, 21 Jun 2018 03:23:31 GMT):
back now.. lets see if it stays stable
rameshthoomu (Fri, 22 Jun 2018 08:35:40 GMT):
@aambati Could you please check this bug.. FAB-10811
Tcnguyen (Fri, 22 Jun 2018 09:58:06 GMT):
Has joined the channel.
nvxtien (Fri, 22 Jun 2018 11:25:19 GMT):
Has joined the channel.
jtclark (Fri, 22 Jun 2018 13:43:34 GMT):
Good Morning
jtclark (Mon, 25 Jun 2018 18:20:42 GMT):
@rameshthoomu this should be ready to merge, yes? https://gerrit.hyperledger.org/r/#/c/23395/
rameshthoomu (Mon, 25 Jun 2018 18:28:58 GMT):
yes.. rebased.. will merge after the final run
jtclark (Mon, 25 Jun 2018 18:29:03 GMT):
thanks.
jtclark (Mon, 25 Jun 2018 18:33:46 GMT):
@rameshthoomu this looks like an easy one too: https://gerrit.hyperledger.org/r/#/c/21751/
DivyaAgrawal (Tue, 26 Jun 2018 10:45:34 GMT):
Has joined the channel.
DivyaAgrawal (Tue, 26 Jun 2018 10:45:40 GMT):
Hi all
On running make dist-clean all on release-1.1 I get following error
Step 1/10 : FROM hyperledger/fabric-buildenv:x86_64-1.1.1-snapshot-c257bb3
pull access denied for hyperledger/fabric-buildenv, repository does not exist or may require 'docker login'
Makefile:305: recipe for target 'build/image/testenv/.dummy-x86_64-1.1.1-snapshot-ff5e861' failed
make: *** [build/image/testenv/.dummy-x86_64-1.1.1-snapshot-ff5e861] Error 1
Can anyone please help with this . TIA
I could find the following JIRA for this. But am not able to understand , how can I resolve this.
https://jira.hyperledger.org/browse/FAB-8354
rameshthoomu (Tue, 26 Jun 2018 19:10:46 GMT):
@jtclark could you please check this failure.. seems it's consistent now.. https://jenkins.hyperledger.org/view/Daily/job/fabric-end-2-end-daily-release-1.0-x86_64/104/console
rameshthoomu (Wed, 27 Jun 2018 02:55:56 GMT):
@harrijk Could you please suggest me the right person to discuss on FAB-10883
DivyaAgrawal (Wed, 27 Jun 2018 10:35:54 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=btgQyapvmsDdQ66iK) Can anyone please help me with this. Thanks
DivyaAgrawal (Wed, 27 Jun 2018 10:48:16 GMT):
cd ..
firas.qutishat (Wed, 27 Jun 2018 19:39:44 GMT):
Hi I can't build fabric in s390x
Step 6/7 : RUN apt-get update
---> Running in 289b806de414
Get:1 http://security.debian.org jessie/updates InRelease [44.9 kB]
Ign http://deb.debian.org jessie InRelease
Get:2 http://deb.debian.org jessie-updates InRelease [145 kB]
Get:3 http://deb.debian.org jessie Release.gpg [2420 B]
Get:4 http://deb.debian.org jessie Release [148 kB]
Get:5 http://deb.debian.org jessie-updates/main s390x Packages [23.0 kB]
Get:6 http://deb.debian.org jessie/main s390x Packages [8798 kB]
Fetched 9162 kB in 6s (1323 kB/s)
W: Failed to fetch http://security.debian.org/dists/jessie/updates/InRelease Unable to find expected entry 'main/binary-s390x/Packages' in Release file (Wrong sources.list entry or malformed file)
E: Some index files failed to download. They have been ignored, or old ones used instead.
rameshthoomu (Wed, 27 Jun 2018 19:47:09 GMT):
@firas.qutishat FAB-10883
rameshthoomu (Wed, 27 Jun 2018 19:47:52 GMT):
while building testenv image on s390x, it's failing to download softhsm libraries..
rameshthoomu (Wed, 27 Jun 2018 19:58:24 GMT):
@firas.qutishat working on the fix... will let you know the update
firas.qutishat (Wed, 27 Jun 2018 20:02:36 GMT):
thanks
rameshthoomu (Wed, 27 Jun 2018 20:12:57 GMT):
@firas.qutishat https://gerrit.hyperledger.org/r/#/c/23753/
rameshthoomu (Wed, 27 Jun 2018 20:12:57 GMT):
@firas.qutishat @troyronda https://gerrit.hyperledger.org/r/#/c/23753/
firas.qutishat (Thu, 28 Jun 2018 15:16:33 GMT):
@rameshthoomu is base image will be updated in 1.2 release branch
firas.qutishat (Thu, 28 Jun 2018 15:16:38 GMT):
https://github.com/hyperledger/fabric/blob/release-1.2/Makefile#L49
jwagantall (Thu, 28 Jun 2018 21:45:29 GMT):
User User_1 added by jwagantall.
jwagantall (Thu, 28 Jun 2018 22:09:15 GMT):
User User_2 added by jwagantall.
troyronda (Fri, 29 Jun 2018 11:05:23 GMT):
@rameshthoomu Looks like multiarch baseimage 0.4.10 tag didn't get pushed to dockerhub yet
troyronda (Fri, 29 Jun 2018 14:46:54 GMT):
does that happen as a separate job?
rameshthoomu (Fri, 29 Jun 2018 14:49:32 GMT):
yes that;s a manual step.. @cbf has to push
troyronda (Fri, 29 Jun 2018 14:49:40 GMT):
ah
cbf (Fri, 29 Jun 2018 16:55:28 GMT):
I can do that
cbf (Fri, 29 Jun 2018 17:03:15 GMT):
@troyronda done
troyronda (Fri, 29 Jun 2018 17:18:20 GMT):
Thanks!
sigma67 (Sun, 01 Jul 2018 19:49:56 GMT):
Has joined the channel.
davidkhala (Tue, 03 Jul 2018 04:10:36 GMT):
@rameshthoomu see continuous failure on node8z test https://gerrit.hyperledger.org/r/#/c/23923/
rameshthoomu (Tue, 03 Jul 2018 12:04:09 GMT):
@davidkhala this is a known issue in master, release-1.1, release-1.0 branches.. We have to update the baseimage with s390x/debian:stretch..
yacovm (Tue, 03 Jul 2018 13:04:12 GMT):
@rameshthoomu I think builds are failing on goimports
yacovm (Tue, 03 Jul 2018 13:04:22 GMT):
```
12:31:10 orderer/common/server/main.go
12:31:10 The goimports command 'goimports -l -w' must be run for these files
12:31:10 Makefile:212: recipe for target 'linter' failed
12:31:10 make: *** [linter] Error 1
```
yacovm (Tue, 03 Jul 2018 13:04:43 GMT):
However I pulled latest master and ran goimports on the file and it didn't look like something was wrong
rameshthoomu (Tue, 03 Jul 2018 13:05:05 GMT):
@cbf fixed in release-1.2 branch.. https://gerrit.hyperledger.org/r/#/c/23977/3/orderer/common/server/main.go
rameshthoomu (Tue, 03 Jul 2018 13:05:29 GMT):
have to push similar change in master.
cbf (Tue, 03 Jul 2018 13:07:10 GMT):
I can add that to my master branch CR
cbf (Tue, 03 Jul 2018 13:07:19 GMT):
after this call
suchith.arodi (Tue, 03 Jul 2018 18:24:22 GMT):
Has joined the channel.
wenjian (Tue, 03 Jul 2018 19:31:33 GMT):
Has joined the channel.
BabuPallam (Wed, 04 Jul 2018 22:20:17 GMT):
Has joined the channel.
krupakar_linux (Thu, 05 Jul 2018 05:00:47 GMT):
Has joined the channel.
sykesm (Thu, 05 Jul 2018 18:57:46 GMT):
https://jenkins.hyperledger.org/job/fabric-smoke-tests-x86_64/2017/ looks to be a hung build. Anyone able to take a look and cancel it?
rameshthoomu (Thu, 05 Jul 2018 19:16:36 GMT):
done
C0rWin (Fri, 06 Jul 2018 23:00:05 GMT):
We didn't use to have integration tests for 1.1, probably we should not also try to trigger it for `release-1.1` branch? see: https://jenkins.hyperledger.org/job/fabric-verify-integration-tests-x86_64/660/console
C0rWin (Fri, 06 Jul 2018 23:01:43 GMT):
```19:15:50 + vote -m '"Starting Integration tests"' -l F3-IntegrationTest=0
19:15:50 + ssh -p 29418 hyperledger-jobbuilder@gerrit.hyperledger.org gerrit review 24179,1 --notify '"NONE"' -m '"Starting Integration tests"' -l F3-IntegrationTest=0
19:15:51 + cd gopath/src/github.com/hyperledger/fabric
19:15:51 + make integration-test
19:15:52 make: *** No rule to make target 'integration-test'. Stop.```
C0rWin (Fri, 06 Jul 2018 23:06:21 GMT):
Reported JIRA: FAB-11091
davidkhala (Sat, 07 Jul 2018 14:17:11 GMT):
Is there and updates on problem `reverify-node8z` failed continuously?
davidkhala (Sat, 07 Jul 2018 14:17:15 GMT):
https://gerrit.hyperledger.org/r/#/c/23923/
nishant_thite (Mon, 09 Jul 2018 02:43:15 GMT):
Has joined the channel.
mastersingh24 (Mon, 09 Jul 2018 10:30:15 GMT):
@rameshthoomu @cbf .... I had to re-tag Fabric v1.1.1 (we needed to add a fix this weekend to fix another fix :-) )
mastersingh24 (Mon, 09 Jul 2018 10:31:51 GMT):
I also modified the Makefile to no longer build `buildenv` and `testenv` when using `make docker` target
mastersingh24 (Mon, 09 Jul 2018 10:32:41 GMT):
So I think we should be able to build and publish images for x86, s390x and Power
rameshthoomu (Mon, 09 Jul 2018 13:43:52 GMT):
tahnks @mastersingh24
rameshthoomu (Mon, 09 Jul 2018 13:43:52 GMT):
thanks @mastersingh24
mastersingh24 (Mon, 09 Jul 2018 13:51:30 GMT):
:pray:
rameshthoomu (Mon, 09 Jul 2018 14:53:48 GMT):
@mastersingh24 Published x86, s390x 1.1.1 images to dockerhub.. Do you want me to publish ppc64le as well?
rameshthoomu (Mon, 09 Jul 2018 14:56:27 GMT):
how about fabric binaries?
mastersingh24 (Mon, 09 Jul 2018 14:59:50 GMT):
We should probably do PPC since we did it for 1.1.0.
And yes ... if you can publish the binaries that would be fantastic
mastersingh24 (Mon, 09 Jul 2018 14:59:56 GMT):
And thanks for the help!
rameshthoomu (Mon, 09 Jul 2018 15:00:13 GMT):
sure.. Will do
cbf (Mon, 09 Jul 2018 18:40:14 GMT):
Hi @rameshthoomu https://gerrit.hyperledger.org/r/c/24159/ not sure what is wrong here... does not seem to be related to the change
rameshthoomu (Mon, 09 Jul 2018 18:48:57 GMT):
not sure.. @bretharrison @davidkhala could you please check this failure.. https://jenkins.hyperledger.org/job/fabric-sdk-node8-verify-master-x86_64/162/consoleFull
rameshthoomu (Mon, 09 Jul 2018 20:42:26 GMT):
@mastersingh24 Published 1.1.1 images and binaries from x,p and z
rameshthoomu (Mon, 09 Jul 2018 20:42:26 GMT):
@mastersingh24 Published 1.1.1 images and binaries from x,p and z. fabric-ca still on 1.1.0
davidkhala (Tue, 10 Jul 2018 05:06:58 GMT):
@rameshthoomu I saw an error originated from nodejs code itself saying `00:06:14 not ok 2116 TypeError: Cannot read property 'peers' of undefined` in that job, what is the change number of it?
davidkhala (Tue, 10 Jul 2018 05:06:58 GMT):
@rameshthoomu I saw an error originated from nodejs code itself saying `00:06:14 not ok 2116 TypeError: Cannot read property 'peers' of undefined` in that job
rameshthoomu (Tue, 10 Jul 2018 05:08:44 GMT):
Yes .. is that a known issue?
davidkhala (Tue, 10 Jul 2018 05:10:34 GMT):
@rameshthoomu This part locates at testing Service discovery, I guess it is new. Checking
baohua (Tue, 10 Jul 2018 07:51:04 GMT):
Has joined the channel.
baohua (Tue, 10 Jul 2018 07:51:21 GMT):
Seems gerrit is down, returned "502 Bad Gateway" always.
baohua (Tue, 10 Jul 2018 08:21:42 GMT):
it's back now!
deghislain (Tue, 10 Jul 2018 18:18:41 GMT):
Has joined the channel.
baohua (Wed, 11 Jul 2018 01:13:09 GMT):
@rameshthoomu the CI seems not working since the breaking yesterday. e.g., no ci work is triggered after new patchset with https://gerrit.hyperledger.org/r/#/c/24141/
rameshthoomu (Wed, 11 Jul 2018 01:28:49 GMT):
I see integration tests are failing in the patchset..
rameshthoomu (Wed, 11 Jul 2018 01:29:22 GMT):
I just re-triggered Integration test with `Run IntegrationTest`
baohua (Wed, 11 Jul 2018 01:53:12 GMT):
thanks!
baohua (Wed, 11 Jul 2018 01:53:48 GMT):
btw, can u help check the errors in https://gerrit.hyperledger.org/r/#/c/24281/? It seems some images and nexus artifacts are missed, which trigger error report. I believe it's not related to the code itself.
rameshthoomu (Wed, 11 Jul 2018 02:10:49 GMT):
When you rebase the patchset, you have to trigger a job with `Run VerifyBuild` or `VerifyBuild`
rameshthoomu (Wed, 11 Jul 2018 02:11:44 GMT):
When you rebase the patchset, will get a new commit and then you have provided a comment `Run SmokeTest` which looks for the images on the new commit..
rameshthoomu (Wed, 11 Jul 2018 02:12:29 GMT):
see this one https://ci-docs.readthedocs.io/en/latest/source/fabric_ci_process.html#rebasing-patch-sets
rameshthoomu (Wed, 11 Jul 2018 02:14:08 GMT):
by the way, Before rebase, the smoketests are failed due to the timeout error
```
00:02:50.528 Error: timeout waiting for channel creation
00:02:50.528 !!!!!!!!!!!!!!! Channel creation failed !!!!!!!!!!!!!!!!
00:02:50.528 ========= ERROR !!! FAILED to execute End-2-End Scenario ===========
00:02:50.529
```
baohua (Wed, 11 Jul 2018 02:21:54 GMT):
thanks, ram. Seems sometime it passed when i repeat the testing. not sure what's the reason.
NoLimitHoldem (Wed, 11 Jul 2018 06:16:56 GMT):
Has joined the channel.
BhaskarNarayan (Thu, 12 Jul 2018 09:21:45 GMT):
Has joined the channel.
rameshthoomu (Fri, 13 Jul 2018 13:50:28 GMT):
@latitiah Could you please check this failure https://jenkins.hyperledger.org/view/Daily/job/fabric-nightly-release-job-master-x86_64/23/consoleFull
jiulama (Sat, 14 Jul 2018 07:10:41 GMT):
Has joined the channel.
yacovm (Sat, 14 Jul 2018 21:21:10 GMT):
https://chat.hyperledger.org/channel/ci-pipeline?msg=hvE5bAhkMquiQfNE9
mastersingh24 (Sat, 14 Jul 2018 21:29:43 GMT):
I was able to clone that URL locally
mastersingh24 (Sun, 15 Jul 2018 12:57:00 GMT):
Who can actually resolve this?
baohua (Sun, 15 Jul 2018 13:45:31 GMT):
Has left the channel.
rameshthoomu (Sun, 15 Jul 2018 15:46:19 GMT):
@jwagantall @TimJohnson
[Hyperledger Helpdesk #58347]
rameshthoomu (Sun, 15 Jul 2018 15:47:28 GMT):
Seems all builds are failing trying to clone "clone.hyperledger.org".. Any configuration update happend?
rameshthoomu (Sun, 15 Jul 2018 19:28:48 GMT):
@mastersingh24 @yacovm @baohua the issue has been resolved and builds are going through.. thanks @jwagantall
baohua (Sun, 15 Jul 2018 19:28:48 GMT):
Has joined the channel.
davidkhala (Mon, 16 Jul 2018 02:35:56 GMT):
@rameshthoomu Are `reverify-node8x` or `reverify-node8z` still working now ?
rameshthoomu (Mon, 16 Jul 2018 03:20:56 GMT):
Yes
jtonline (Mon, 16 Jul 2018 12:11:17 GMT):
Has joined the channel.
bestbeforetoday (Mon, 16 Jul 2018 12:12:18 GMT):
Has joined the channel.
rameshthoomu (Mon, 16 Jul 2018 13:18:34 GMT):
@latitiah could you please verify this failure.. It's intermittent https://jenkins.hyperledger.org/view/Daily/job/fabric-nightly-release-job-master-x86_64/28/consoleFull
latitiah (Mon, 16 Jul 2018 13:28:33 GMT):
Yes, I will put out a CR to increase the timeout for waiting for the orderer to come up fully
rameshthoomu (Mon, 16 Jul 2018 13:34:54 GMT):
one more here https://jenkins.hyperledger.org/view/Daily/job/fabric-nightly-release-job-release-1.2-x86_64/36/console
rameshthoomu (Mon, 16 Jul 2018 13:35:19 GMT):
it seems same issue but I would like you to verify
jtclark (Mon, 16 Jul 2018 13:35:30 GMT):
Good morning
jtclark (Mon, 16 Jul 2018 13:35:43 GMT):
back from my 2-week vacation
rameshthoomu (Mon, 16 Jul 2018 13:36:03 GMT):
this is blocking us to publish daily images and binaries..
jtclark (Mon, 16 Jul 2018 13:36:17 GMT):
@rameshthoomu have you been checking the Jenkins jobs?
jtclark (Mon, 16 Jul 2018 13:36:49 GMT):
I assume that you have..... is @sambhavdutt doing this too? Just wondering when I need to pick this back up now that I'm back
rameshthoomu (Mon, 16 Jul 2018 13:37:28 GMT):
yes..
rameshthoomu (Mon, 16 Jul 2018 13:37:53 GMT):
@sambhavdutt is not here.. He will be back this week..
jtclark (Mon, 16 Jul 2018 13:37:54 GMT):
@rameshthoomu ok, I can take that back up
rameshthoomu (Mon, 16 Jul 2018 13:38:01 GMT):
sure.. thanks
jtclark (Mon, 16 Jul 2018 13:38:27 GMT):
at least until @sambhavdutt is back, then he and I can work out how to do it going fwd
jtclark (Mon, 16 Jul 2018 13:38:31 GMT):
ok
rameshthoomu (Mon, 16 Jul 2018 17:39:13 GMT):
github.com is down.. https://status.github.com/messages
adarshsaraf123 (Tue, 17 Jul 2018 05:15:26 GMT):
Has joined the channel.
rameshthoomu (Tue, 17 Jul 2018 13:58:49 GMT):
@mastersingh24 we need to implement this as soon as possible FAB-11181
rameshthoomu (Tue, 17 Jul 2018 14:00:42 GMT):
I tried to build fabric and fabric-ca images on release-1.1 branch with 0.4.10 baseimage and observed linter is failed https://jenkins.hyperledger.org/sandbox/job/fabric-unit-test-daily-release-1.1-s390x/5/console
rameshthoomu (Tue, 17 Jul 2018 16:48:17 GMT):
@jwagantall if possible could you please keep this doc https://ci-docs.readthedocs.io/en/latest/ in the fabric-ci chat room description
mastersingh24 (Tue, 17 Jul 2018 19:16:03 GMT):
@rameshthoomu - I know the problem .... 0.4.10 use Go 1.10
mastersingh24 (Tue, 17 Jul 2018 19:16:15 GMT):
1.1 was originally built against 1.9
rameshthoomu (Tue, 17 Jul 2018 19:20:58 GMT):
yes.. also we have baseimage (0.4.10) with amd64 but the 1.1, 1.0 expecting x86_64.. I made changed to pull amd64-0.4.10 but the lint errors with go version..
ZackPhan (Tue, 17 Jul 2018 20:14:48 GMT):
Has joined the channel.
jwagantall (Tue, 17 Jul 2018 20:56:45 GMT):
https://ci-docs.readthedocs.io/en/latest/
mbwhite (Thu, 19 Jul 2018 11:56:47 GMT):
Has joined the channel.
mbwhite (Thu, 19 Jul 2018 11:57:45 GMT):
I've submitted a Change Request - my local branch has multiple commits within it (making the progress of how I worked). is this bad practice in the Hyperledger setup (Fabric-chaincode-node in this case)
rameshthoomu (Thu, 19 Jul 2018 15:16:46 GMT):
@latitiah Could you please look into this FAB-11233
latitiah (Thu, 19 Jul 2018 15:41:11 GMT):
@rameshthoomu: rebase and try again. There has been a recent change that refactors much of this. https://gerrit.hyperledger.org/r/#/c/24317/
rameshthoomu (Thu, 19 Jul 2018 16:25:58 GMT):
I see the same issue in Build 32, 33 from this job https://jenkins.hyperledger.org/view/Daily/job/fabric-nightly-release-job-master-x86_64/
latitiah (Thu, 19 Jul 2018 16:33:43 GMT):
That's a different timeout. I'll look into that one a bit more
rameshthoomu (Thu, 19 Jul 2018 16:46:26 GMT):
ok
junewalk2 (Sat, 21 Jul 2018 02:47:09 GMT):
Has joined the channel.
Swaroop.Kondru (Sat, 21 Jul 2018 19:06:23 GMT):
Has joined the channel.
jtclark (Mon, 23 Jul 2018 17:09:55 GMT):
plz review: https://gerrit.hyperledger.org/r/24665
jtclark (Mon, 23 Jul 2018 18:08:20 GMT):
seems like we are pointing most people to https://ci-docs.readthedocs.io/en/latest/
jtclark (Mon, 23 Jul 2018 18:09:08 GMT):
also... once it is posted, we should communicate this via the mailing-list I think
iamksseo (Tue, 24 Jul 2018 03:05:39 GMT):
Has joined the channel.
SadhviNayak (Wed, 25 Jul 2018 11:39:14 GMT):
Has joined the channel.
grapebaba (Wed, 25 Jul 2018 12:37:47 GMT):
how to re trigger the fabric CI unit test right now?
rameshthoomu (Wed, 25 Jul 2018 12:49:01 GMT):
@grapebaba pls see this https://ci-docs.readthedocs.io/en/latest/source/fabric_ci_process.html#trigger-failed-jobs-through-gerrit-comments
nkl199 (Wed, 25 Jul 2018 15:52:10 GMT):
Has joined the channel.
rickr (Wed, 25 Jul 2018 21:12:19 GMT):
@jwagantall 16:09:11 [INFO] -------------------------------------------------------------
16:09:11 [ERROR] /w/workspace/fabric-sdk-java-verify-1.0.0-x86_64/src/main/java/org/hyperledger/fabric/sdk/BlockInfo.java:[60,27] cannot access java.lang.AssertionError
16:09:11 bad class file: /usr/lib/jvm/java-8-openjdk-amd64/lib/ct.sym(META-INF/sym/rt.jar/java/lang/AssertionError.class)
rickr (Wed, 25 Jul 2018 21:12:38 GMT):
https://jenkins.hyperledger.org/job/fabric-sdk-java-verify-1.0.0-x86_64/941/console
rickr (Wed, 25 Jul 2018 21:14:10 GMT):
I'm see a lot of these ... my guess is the Java sdk aka in this case `java-8-open` is bad
rickr (Wed, 25 Jul 2018 21:14:10 GMT):
I'm seeing a lot of these ... my guess is the Java sdk aka in this case `java-8-open` is bad
rickr (Wed, 25 Jul 2018 21:43:28 GMT):
That build just passed .. once again I'm guessing it got allocated to a vm build system where the java sdk is ok
jwagantall (Wed, 25 Jul 2018 23:40:10 GMT):
that was stange, we are only using one image for all these ubuntu nodes.. 1 single template. .. maybe a glitch?
rickr (Wed, 25 Jul 2018 23:45:16 GMT):
do you generate the vm each time from the template ?
rickr (Wed, 25 Jul 2018 23:46:52 GMT):
I'm guessing not -- You have a pool of vms that have been created by that single image that get continually reused and on some that file is corrupt.
baohua (Thu, 26 Jul 2018 01:23:29 GMT):
@grapebaba Run xxxxxTest
kostas (Thu, 26 Jul 2018 01:55:28 GMT):
Has left the channel.
vijay.bP (Thu, 26 Jul 2018 02:37:17 GMT):
Has joined the channel.
naviat (Thu, 26 Jul 2018 08:59:45 GMT):
Has joined the channel.
dave.enyeart (Thu, 26 Jul 2018 12:27:56 GMT):
@nirro - multiple integration test failures due to "[It] verifies private data is purged after BTL has passed and new peer doesn't pull private data that was purged".
dave.enyeart (Thu, 26 Jul 2018 12:28:00 GMT):
https://jenkins.hyperledger.org/job/fabric-verify-integration-tests-x86_64/922/console
dave.enyeart (Thu, 26 Jul 2018 12:28:20 GMT):
https://gerrit.hyperledger.org/r/#/c/24547/
dave.enyeart (Thu, 26 Jul 2018 12:28:23 GMT):
any ideas?
dave.enyeart (Thu, 26 Jul 2018 12:28:47 GMT):
if it has been fixed then we could rebase that CR...
dave.enyeart (Thu, 26 Jul 2018 14:51:12 GMT):
opened bug https://jira.hyperledger.org/browse/FAB-11327
dave.enyeart (Thu, 26 Jul 2018 14:52:19 GMT):
and https://jira.hyperledger.org/browse/FAB-11329
dave.enyeart (Thu, 26 Jul 2018 15:07:46 GMT):
@sykesm @nirro we'll revert the private data integration tests until the issue is resolved. revert CRs: https://gerrit.hyperledger.org/r/24815 and https://gerrit.hyperledger.org/r/24817
wlahti (Thu, 26 Jul 2018 16:32:49 GMT):
Any known issues with the fabric SmokeTest at the moment? keeps failing for me saying `cryptogen tool not found. exiting` - https://jenkins.hyperledger.org/job/fabric-smoke-tests-x86_64/2259/
wlahti (Thu, 26 Jul 2018 16:32:49 GMT):
Any known issues with the fabric SmokeTest job at the moment? keeps failing for me saying `cryptogen tool not found. exiting` - https://jenkins.hyperledger.org/job/fabric-smoke-tests-x86_64/2259/
jtclark (Thu, 26 Jul 2018 16:34:36 GMT):
@wlahti we'll take a look
rameshthoomu (Thu, 26 Jul 2018 17:10:57 GMT):
@jtclark did you find root cause of the failure?
jtclark (Thu, 26 Jul 2018 17:11:55 GMT):
I mean the issue stems from the cryptogen tool not being found
rameshthoomu (Thu, 26 Jul 2018 17:13:18 GMT):
yes.. I see that . but do you know why?
jtclark (Thu, 26 Jul 2018 17:13:26 GMT):
not yet, no.
rameshthoomu (Thu, 26 Jul 2018 17:13:35 GMT):
ok
jtclark (Thu, 26 Jul 2018 17:13:36 GMT):
any ideas?
jtclark (Thu, 26 Jul 2018 17:14:03 GMT):
that's provided as a binary right?
jtclark (Thu, 26 Jul 2018 17:15:02 GMT):
```
00:00:27.979 Error response from daemon: manifest for nexus3.hyperledger.org:10003/hyperledger/fabric-peer:be620ce not found
00:00:28.097 Error response from daemon: No such image: nexus3.hyperledger.org:10003/hyperledger/fabric-peer:be620ce
00:00:28.100 ==> nexus3.hyperledger.org:10003/hyperledger/fabric-peer:be620ce
00:00:28.100 ==> orderer
00:00:28.100
00:00:28.451 Error response from daemon: manifest for nexus3.hyperledger.org:10003/hyperledger/fabric-orderer:be620ce not found
00:00:28.534 Error response from daemon: No such image: nexus3.hyperledger.org:10003/hyperledger/fabric-orderer:be620ce
00:00:28.541 ==> nexus3.hyperledger.org:10003/hyperledger/fabric-orderer:be620ce
00:00:28.541 ==> ccenv
00:00:28.541
00:00:28.750 Error response from daemon: manifest for nexus3.hyperledger.org:10003/hyperledger/fabric-ccenv:be620ce not found
00:00:28.891 Error response from daemon: No such image: nexus3.hyperledger.org:10003/hyperledger/fabric-ccenv:be620ce
00:00:28.893 ==> nexus3.hyperledger.org:10003/hyperledger/fabric-ccenv:be620ce
00:00:28.893 ==> tools
00:00:28.893
00:00:29.093 Error response from daemon: manifest for nexus3.hyperledger.org:10003/hyperledger/fabric-tools:be620ce not found
00:00:29.170 Error response from daemon: No such image: nexus3.hyperledger.org:10003/hyperledger/fabric-tools:be620ce
```
rameshthoomu (Thu, 26 Jul 2018 17:15:15 GMT):
Patch#8 was a commit update change.. so we don't trigger build on patch#8.. and then @will tried to post a comment "Run SmokeTest" and there is no commit available in nexus to pull them.. So the curl command failed to download on Patch#8
rameshthoomu (Thu, 26 Jul 2018 17:15:48 GMT):
@wlahti please type `VerifyBuild` and this should fix the failures
jtclark (Thu, 26 Jul 2018 17:16:05 GMT):
ah. makes sense.
jtclark (Thu, 26 Jul 2018 17:16:07 GMT):
thanks.
rameshthoomu (Thu, 26 Jul 2018 17:16:49 GMT):
@wlahti just for reference https://ci-docs.readthedocs.io/en/latest/source/fabric_ci_process.html#rebasing-patch-sets
rameshthoomu (Thu, 26 Jul 2018 21:17:04 GMT):
All,
System downtime for Hyperledger CI Tools*
Today (July 26) 6-8:00 PM EDT
Updating OS on the servers for Gerrit, Jenkins & Nexus
Updatng Jenkins, Nexus & JIRA
rameshthoomu (Fri, 27 Jul 2018 17:07:58 GMT):
@latitiah I see integration tests are failing on master branch consistently https://jenkins.hyperledger.org/view/Daily/job/fabric-nightly-release-job-master-x86_64/48/console
rameshthoomu (Fri, 27 Jul 2018 17:08:28 GMT):
could you please check Build# 44 to #48
latitiah (Fri, 27 Jul 2018 17:17:22 GMT):
looks like something is failing around Private data
dave.enyeart (Fri, 27 Jul 2018 17:21:11 GMT):
@rameshthoomu @latitiah , @C0rWin is preparing a CR to disable the failing private data tests... then we'll need to rebase each of the other failing CRs on top...
rameshthoomu (Fri, 27 Jul 2018 17:35:54 GMT):
@dave.enyeart FAB-11367
zjubfd (Sat, 28 Jul 2018 10:08:17 GMT):
Has joined the channel.
zjubfd (Sat, 28 Jul 2018 10:16:52 GMT):
So after the issue FAB-11367 fixed. How can i make Hyperledger Jobbuilder run again in gerrit?
kostas (Sat, 28 Jul 2018 18:51:19 GMT):
Has joined the channel.
rameshthoomu (Sun, 29 Jul 2018 00:04:35 GMT):
If integration tests are failing in your patchset pls trigger through comment.. type Run IntegrationTest in your patchset
zjubfd (Sun, 29 Jul 2018 00:59:22 GMT):
thks, it works
zjubfd (Mon, 30 Jul 2018 01:53:33 GMT):
Hi，i am a newbie in contruibuting fabric program. I don’t know if i add the right reviewers, and what should i do next after CI passed?
jtclark (Mon, 30 Jul 2018 01:54:06 GMT):
@zjubfd what project are you contributing to?
zjubfd (Mon, 30 Jul 2018 01:54:12 GMT):
FAB
jtclark (Mon, 30 Jul 2018 01:54:20 GMT):
fabric ?
zjubfd (Mon, 30 Jul 2018 01:54:25 GMT):
yes
jtclark (Mon, 30 Jul 2018 01:54:37 GMT):
do you have the patchset link?
zjubfd (Mon, 30 Jul 2018 01:54:54 GMT):
https://gerrit.hyperledger.org/r/#/c/24887/
zjubfd (Mon, 30 Jul 2018 01:55:06 GMT):
can you open it ?
jtclark (Mon, 30 Jul 2018 01:55:52 GMT):
yes
jtclark (Mon, 30 Jul 2018 01:56:05 GMT):
Dave is a good person to add
jtclark (Mon, 30 Jul 2018 01:56:32 GMT):
@zjubfd you can also post this patchset to #fabric-pr-review
jtclark (Mon, 30 Jul 2018 01:56:42 GMT):
and ask for a review
zjubfd (Mon, 30 Jul 2018 01:56:57 GMT):
thks a lot!
zjubfd (Mon, 30 Jul 2018 01:57:02 GMT):
:wink:
jtclark (Mon, 30 Jul 2018 01:57:08 GMT):
sure, yw :thumbsup:
zjubfd (Mon, 30 Jul 2018 01:58:56 GMT):
one more thing... There are a lot of Dave.. is David Enyeart?
jtclark (Mon, 30 Jul 2018 01:59:07 GMT):
yes, that's the correct Dave
zjubfd (Mon, 30 Jul 2018 01:59:22 GMT):
:thumbsup:
rameshthoomu (Mon, 30 Jul 2018 20:20:12 GMT):
@bretharrison Published sdk-node 1.2.1 node modules..
rameshthoomu (Mon, 30 Jul 2018 20:22:24 GMT):
https://www.npmjs.com/package/fabric-client
https://www.npmjs.com/package/fabric-ca-client
kostas (Mon, 30 Jul 2018 23:27:53 GMT):
Has left the channel.
zhaochy (Tue, 31 Jul 2018 02:20:45 GMT):
hello, how can I reverify a integration test for fabric ci ?
rameshthoomu (Tue, 31 Jul 2018 02:44:39 GMT):
@zhaochy Run IntegrationTest
zhaochy (Tue, 31 Jul 2018 02:46:33 GMT):
thanks, I found the doc~
sykesm (Tue, 31 Jul 2018 17:59:56 GMT):
https://jira.hyperledger.org/browse/FAB-11377 breaks builds on mac os
sykesm (Tue, 31 Jul 2018 17:59:56 GMT):
https://jira.hyperledger.org/browse/FAB-11377 breaks builds on mac os - take that back; not broken now - just noisy
sykesm (Tue, 31 Jul 2018 17:59:56 GMT):
https://jira.hyperledger.org/browse/FAB-11377 breaks builds on mac os - take that back; not broken now - just noisy; well sort of broken. it doesn't clean up any more
sykesm (Tue, 31 Jul 2018 17:59:56 GMT):
https://jira.hyperledger.org/browse/FAB-11377 breaks the clean phase of builds on MacOS. Previous behavior would generate noise when no images exist to clean but the target would succeed. Now the target succeeds but leaves behind the images.
zmaro (Fri, 03 Aug 2018 15:17:01 GMT):
Has joined the channel.
pankajanand26 (Fri, 03 Aug 2018 15:33:08 GMT):
Has joined the channel.
gennadyl (Mon, 06 Aug 2018 13:54:55 GMT):
@rameshthoomu Hi. I need little help with integrating javacc with CI
gennadyl (Mon, 06 Aug 2018 13:55:12 GMT):
Or maybe big help
rameshthoomu (Mon, 06 Aug 2018 14:05:34 GMT):
@gennadyl Could you please check with @jtclark
jtclark (Mon, 06 Aug 2018 14:05:50 GMT):
@gennadyl what seems to be the issue?
gennadyl (Mon, 06 Aug 2018 14:14:23 GMT):
Hi Jason
jtclark (Mon, 06 Aug 2018 14:14:30 GMT):
:wave:
gennadyl (Mon, 06 Aug 2018 14:14:49 GMT):
I changed the way fabric-chaincode-java build
jtclark (Mon, 06 Aug 2018 14:15:04 GMT):
ok
gennadyl (Mon, 06 Aug 2018 14:15:52 GMT):
Now build result is 3 artifacts - protos jar, shim jar and docker image
jtclark (Mon, 06 Aug 2018 14:16:28 GMT):
ok
gennadyl (Mon, 06 Aug 2018 14:17:36 GMT):
So, how I make those artifacts deployed - jars to maven central or other public repo we use and docker image pushed to docker hub?
jtclark (Mon, 06 Aug 2018 14:17:59 GMT):
do you have a patch set prepared for this change?
gennadyl (Mon, 06 Aug 2018 14:18:10 GMT):
yep
jtclark (Mon, 06 Aug 2018 14:18:16 GMT):
can you link that here?
gennadyl (Mon, 06 Aug 2018 14:18:27 GMT):
https://gerrit.hyperledger.org/r/#/c/20573/
jtclark (Mon, 06 Aug 2018 14:20:49 GMT):
@gennadyl right off, I'll have to look at what we do in the fabric-chaincode-java by taking a look at the Jenkins jobs we have out there
gennadyl (Mon, 06 Aug 2018 14:21:09 GMT):
Ok
jtclark (Mon, 06 Aug 2018 14:21:15 GMT):
my first thought is that if we want to test this, we probably have to push one of the jobs to the sandbox, pull this patch and test
jtclark (Mon, 06 Aug 2018 14:21:44 GMT):
otherwise, the new jars and/or images won't get pushed until this patch is Merged
gennadyl (Mon, 06 Aug 2018 14:21:54 GMT):
sure.
jtclark (Mon, 06 Aug 2018 14:22:14 GMT):
give me a few mins here this morning to take a look at this
gennadyl (Mon, 06 Aug 2018 14:22:31 GMT):
np
gennadyl (Mon, 06 Aug 2018 14:23:02 GMT):
build run by gradle
gennadyl (Mon, 06 Aug 2018 14:23:10 GMT):
gradle build
jtclark (Mon, 06 Aug 2018 14:23:13 GMT):
ok
gennadyl (Mon, 06 Aug 2018 14:23:14 GMT):
and
gennadyl (Mon, 06 Aug 2018 14:23:19 GMT):
gradle buildImage
rameshthoomu (Mon, 06 Aug 2018 16:09:15 GMT):
@vijay.bP hi
rameshthoomu (Mon, 06 Aug 2018 17:36:37 GMT):
@harsha could you please comment the latest progress on this FABCI-34
SriramaSharma (Tue, 07 Aug 2018 05:25:57 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=eWP2icJbtJuQqmcd6) @rameshthoomu Hi @rameshthoomu , As of late last week @harsha was ironing out finer setup tasks on the new 7 (beefed up) VMs with more resources (compute and memory) assigned to them. Will follow up and ensure we close on this at the earliest. Thanks for your constant support!
SriramaSharma (Tue, 07 Aug 2018 05:25:57 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=eWP2icJbtJuQqmcd6) Hi @rameshthoomu , As of late last week @harsha was ironing out finer setup tasks on the new 7 (beefed up) VMs with more resources (compute and memory) assigned to them. Will follow up and ensure we close on this at the earliest. Thanks for your constant support!
gennadyl (Tue, 07 Aug 2018 13:28:53 GMT):
@jtclark Any news with java cc build?
jtclark (Tue, 07 Aug 2018 13:30:27 GMT):
@gennadyl none yet. need to push the fabric-chaincode-java job out to the Sandbox today to finish testing.
jtclark (Tue, 07 Aug 2018 13:30:39 GMT):
will give you an update this AM
gennadyl (Tue, 07 Aug 2018 13:30:51 GMT):
ok
gennadyl (Tue, 07 Aug 2018 13:30:55 GMT):
thanks
rameshthoomu (Tue, 07 Aug 2018 14:31:16 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=ypCZLb7f6u2aT2wBm) @gennadyl @jtclark Look at the fabric-chaincode-java merge job to publish jar, you have to create a release job to publish chaincode-java docker image...
rameshthoomu (Tue, 07 Aug 2018 14:31:46 GMT):
to publish a docker image, first you have to request @jwagantall to create a repo in dockerhub
rameshthoomu (Tue, 07 Aug 2018 14:31:46 GMT):
to publish a docker image, first you have to request @jwagantall to create a image repo in dockerhub
jtclark (Tue, 07 Aug 2018 14:32:05 GMT):
@gennadyl I'm going to create a couple JIRA tasks: 1) updating the merge job 2) creating a release job to push the docker image
rameshthoomu (Tue, 07 Aug 2018 14:32:26 GMT):
Check with @gennadyl, when he want us to publish the jar files
gennadyl (Tue, 07 Aug 2018 14:32:32 GMT):
@rameshthoomu I think javaenv repo in docker hub already exist
rameshthoomu (Tue, 07 Aug 2018 14:32:39 GMT):
yes we have..
rameshthoomu (Tue, 07 Aug 2018 14:32:48 GMT):
if it is javaenv.. then we have a repo..
gennadyl (Tue, 07 Aug 2018 14:33:02 GMT):
https://hub.docker.com/r/hyperledger/fabric-javaenv/
gennadyl (Tue, 07 Aug 2018 14:35:31 GMT):
@jtclark I think we need to push jars as well
rameshthoomu (Tue, 07 Aug 2018 14:35:43 GMT):
as part of merge or release?
gennadyl (Tue, 07 Aug 2018 14:37:09 GMT):
At the end, end user, who write java chaincode, need those jars to compile it.
gennadyl (Tue, 07 Aug 2018 14:38:09 GMT):
I mean, as part of compile dependencies in maven/gradle
rameshthoomu (Tue, 07 Aug 2018 14:38:25 GMT):
ok
gennadyl (Tue, 07 Aug 2018 14:39:08 GMT):
And same jars should be part of docker image, to reduce build time during instantiate
rameshthoomu (Tue, 07 Aug 2018 14:39:15 GMT):
do we have any commands/steps, how to publish these artifacts..
jtclark (Tue, 07 Aug 2018 14:40:11 GMT):
when a patch set is merged to fabric-chaincode-java, do we need to publish jars and a docker image ?
jtclark (Tue, 07 Aug 2018 14:40:34 GMT):
when we run a release of fabric-chaincode-java, do we need to publish jars and a docker image?
rameshthoomu (Tue, 07 Aug 2018 14:40:49 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=xW8fRXYzouo2hc4eB) @gennadyl I think we have to update this as part of the image build process.. Do we have this step in the current image build process?
jtclark (Tue, 07 Aug 2018 14:41:13 GMT):
those are my questions :point_up_tone2:
gennadyl (Tue, 07 Aug 2018 14:41:17 GMT):
Yes, as part of build
gennadyl (Tue, 07 Aug 2018 14:42:03 GMT):
@jtclark I think we need to publish both - jars and image
gennadyl (Tue, 07 Aug 2018 14:42:40 GMT):
@rameshthoomu Yes, jars are pushed to image during image build
jtclark (Tue, 07 Aug 2018 14:42:59 GMT):
@rameshthoomu so it sounds like we need to modify the merge job to publish the jars and publish the image to nexus
gennadyl (Tue, 07 Aug 2018 14:43:14 GMT):
@jtclark What the difference between merge and release?
jtclark (Tue, 07 Aug 2018 14:43:34 GMT):
@gennadyl merge jobs happen with every merge to the master branch
jtclark (Tue, 07 Aug 2018 14:44:14 GMT):
@gennadyl release jobs are manually triggered during a release where we tag then publish stable artifacts for the release in play
gennadyl (Tue, 07 Aug 2018 14:44:18 GMT):
Let me think a minute
jtclark (Tue, 07 Aug 2018 14:44:37 GMT):
@rameshthoomu is this correct ?
rameshthoomu (Tue, 07 Aug 2018 14:44:51 GMT):
@gennadyl I would like you to create tasks for this work.. Please specify what exactly you need in the JIRA
rameshthoomu (Tue, 07 Aug 2018 14:45:10 GMT):
please create these tasks in FABCI Project
gennadyl (Tue, 07 Aug 2018 14:45:20 GMT):
@rameshthoomu Ok. Will do
jtclark (Tue, 07 Aug 2018 14:45:30 GMT):
@gennadyl I can help you if needed.
rameshthoomu (Tue, 07 Aug 2018 14:45:32 GMT):
also, before we publish these, could you please check this bug FAB-9701
rameshthoomu (Tue, 07 Aug 2018 14:46:06 GMT):
fabric-chaincode-java merge job is broken since months..
gennadyl (Tue, 07 Aug 2018 14:47:12 GMT):
I don't think we had any merges tofabric-chaincode-java since months
rameshthoomu (Tue, 07 Aug 2018 14:50:30 GMT):
thanks @SriramaSharma @harsha for the update. Please let us know when you are ready with the build nodes..
rameshthoomu (Tue, 07 Aug 2018 14:51:00 GMT):
I have assigned this to @sambhavdutt . He will test the jobs once the nodes are available for test..
sambhavdutt (Tue, 07 Aug 2018 14:52:33 GMT):
:thumbsup:
gennadyl (Tue, 07 Aug 2018 14:56:50 GMT):
@rameshthoomu I looked into FAB-9701 - it is one of the thing I hope we will solve now.
gennadyl (Tue, 07 Aug 2018 15:00:27 GMT):
I will add comment there with links to new jiras
gennadyl (Tue, 07 Aug 2018 15:07:34 GMT):
@jtclark I think we will need to publish jars and image only during release
harsha (Tue, 07 Aug 2018 15:07:48 GMT):
@rameshthoomu @sambhavdutt The nodes are already added to the jenkins-ci
gennadyl (Tue, 07 Aug 2018 15:12:13 GMT):
@jtclark Is it possible to publish during merge not each time, but only once jars API changed?
jtclark (Tue, 07 Aug 2018 15:15:56 GMT):
@gennadyl not entirely sure. we may be able to add some logic that looks for diffs....
gennadyl (Tue, 07 Aug 2018 15:26:22 GMT):
@jtclarck
gennadyl (Tue, 07 Aug 2018 15:27:03 GMT):
@jtclark I just opened jira and explained there problem with publishing
jtclark (Tue, 07 Aug 2018 15:27:16 GMT):
thanks
gennadyl (Tue, 07 Aug 2018 15:27:40 GMT):
I have to move now, will try to reconnect later this evening
jtclark (Tue, 07 Aug 2018 15:28:08 GMT):
I'll have a look shortly
rameshthoomu (Tue, 07 Aug 2018 15:29:40 GMT):
Yes that’s possible.. @jtclark pls look into the docs job for the logic @gennadyl [ ](https://chat.hyperledger.org/channel/fabric-ci?msg=MQwHqgQMgWuy3A8uN)
EvgenyK (Tue, 07 Aug 2018 15:40:04 GMT):
Has joined the channel.
dave.enyeart (Tue, 07 Aug 2018 19:32:55 GMT):
@rameshthoomu @cbf do we need to do anything about the ppc CI errors in baseimage? I'd like to get the updates that we reverted before v1.2 merged back in: https://gerrit.hyperledger.org/r/#/c/24427/
cbf (Tue, 07 Aug 2018 19:33:27 GMT):
hmmm, I thought we disabled ppc in CI
dave.enyeart (Tue, 07 Aug 2018 19:38:24 GMT):
ok, i'll manually verify and merge, while Ramesh looks into that
rameshthoomu (Tue, 07 Aug 2018 19:41:45 GMT):
baseimage jobs are not disabled. Will disable that
rameshthoomu (Tue, 07 Aug 2018 19:42:12 GMT):
I see the postbuild action step is failed here https://jenkins.hyperledger.org/view/fabric-baseimage/job/fabric-baseimage-verify-docker-ppc64le/
rameshthoomu (Tue, 07 Aug 2018 19:48:08 GMT):
https://gerrit.hyperledger.org/r/#/c/25219/
rameshthoomu (Tue, 07 Aug 2018 19:58:29 GMT):
ppc baseimage jobs are now disabled in CI
gennadyl (Tue, 07 Aug 2018 20:06:16 GMT):
@jtclark Any news?
jtclark (Tue, 07 Aug 2018 20:07:00 GMT):
@gennadyl patch sets aren't quite ready. I can add you as a reviewer
gennadyl (Tue, 07 Aug 2018 20:07:34 GMT):
Great. Thanks. Did you had chance to look into jira I opened?
gennadyl (Tue, 07 Aug 2018 20:08:40 GMT):
FABCI-50
jtclark (Tue, 07 Aug 2018 20:09:08 GMT):
got it.
jtclark (Tue, 07 Aug 2018 20:09:18 GMT):
I've assigned it to myself.
gennadyl (Tue, 07 Aug 2018 20:27:09 GMT):
Thanks.
SriramaSharma (Wed, 08 Aug 2018 04:52:35 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=XxwMJJKhpBmYw7Nxu) @rameshthoomu Hi @rameshthoomu , I don't see the link coming up properly and it gives an error saying "Not Found".
SriramaSharma (Wed, 08 Aug 2018 04:54:35 GMT):
@cbf @rameshthoomu Would like to get the ppc64le builds back on to the CI. When the builds were disabled before 1.2 release, we weren't having any issues with the build nodes. Now that we have beefed up the build servers with more compute, we can even plan to have nightly builds done. So request your support and consent in getting the ppc64le builds back in community CI.
rameshthoomu (Wed, 08 Aug 2018 04:58:14 GMT):
@SriramaSharma Will test these unit and e2e tests on new power nodes and will update the results..
rameshthoomu (Wed, 08 Aug 2018 04:59:57 GMT):
let me check the update on the unit-test failures
SriramaSharma (Wed, 08 Aug 2018 05:16:43 GMT):
Sure. Do let know if there is something we need to act on.
mulser (Wed, 08 Aug 2018 08:31:53 GMT):
Has joined the channel.
dave.enyeart (Wed, 08 Aug 2018 14:30:13 GMT):
@rameshthoomu @bretharrison I'm trying to pin fabric-samples v1.2.x use node sdk and node chaincode v1.2.x. It works local when I run byfn with `-l node`, but it fails in CI with a npm error. Could you take a look?
dave.enyeart (Wed, 08 Aug 2018 14:30:13 GMT):
@rameshthoomu @bretharrison I'm trying to pin fabric-samples v1.2.x to use node sdk and node chaincode v1.2.x. It works local when I run byfn with `-l node` local, but it fails in CI with a npm error. Could you take a look?
dave.enyeart (Wed, 08 Aug 2018 14:30:16 GMT):
https://gerrit.hyperledger.org/r/#/c/25271/
dave.enyeart (Wed, 08 Aug 2018 14:30:25 GMT):
https://jenkins.hyperledger.org/job/fabric-samples-verify-byfn-release-1.2-x86_64/11/console
dave.enyeart (Wed, 08 Aug 2018 14:32:12 GMT):
https://github.com/npm/npm/issues/16861 says to upgrade to 5.7.1 or try `npm cache verify`
rameshthoomu (Wed, 08 Aug 2018 14:36:29 GMT):
let me check
rameshthoomu (Wed, 08 Aug 2018 15:48:02 GMT):
@dave.enyeart it seems chaincode container is not started properly.. that could be the reason for the failure.
rameshthoomu (Wed, 08 Aug 2018 15:48:12 GMT):
I have re-triggered the job, and it worked this time..
latitiah (Thu, 09 Aug 2018 14:35:07 GMT):
I've opened https://jira.hyperledger.org/browse/FABCI-59
sambhavdutt (Thu, 09 Aug 2018 14:36:04 GMT):
Hello @latitiah
I will work on this one and let you know
swetha (Thu, 09 Aug 2018 16:27:22 GMT):
Has joined the channel.
swetha (Thu, 09 Aug 2018 16:35:15 GMT):
@rameshthoomu, Hello, we are having an issue with jenkins for the `fabric-chaincode-evm`. All of our runs are failing at the same stage: https://jenkins.hyperledger.org/job/fabric-chaincode-evm-verify-master-x86_64/4/console. We get that JENKINS-41339 error. I am thinking it is because we try to modify the PATH variable. I think we have to do something like `PATH+EXTRA`, but I am not familiar with jenkins. Also wondering if you can help me test changes in the Jenkinsfile in general.
swetha (Thu, 09 Aug 2018 16:35:15 GMT):
@rameshthoomu, Hello, we are having an issue with jenkins for the `fabric-chaincode-evm` repo. All of our runs are failing at the same stage: https://jenkins.hyperledger.org/job/fabric-chaincode-evm-verify-master-x86_64/4/console. We get that JENKINS-41339 error. I am thinking it is because we try to modify the PATH variable. I think we have to do something like `PATH+EXTRA`, but I am not familiar with jenkins. Also wondering if you can help me test changes in the Jenkinsfile in general.
jtclark (Thu, 09 Aug 2018 16:36:01 GMT):
Hi @swetha!
swetha (Thu, 09 Aug 2018 16:36:08 GMT):
Hey Jason!
jtclark (Thu, 09 Aug 2018 16:36:24 GMT):
I can take a quick look....
rameshthoomu (Thu, 09 Aug 2018 16:37:12 GMT):
checking
rameshthoomu (Thu, 09 Aug 2018 16:37:49 GMT):
ok got the issue
rameshthoomu (Thu, 09 Aug 2018 16:37:54 GMT):
let me fix it
jtclark (Thu, 09 Aug 2018 16:38:34 GMT):
@rameshthoomu this, correct?
jtclark (Thu, 09 Aug 2018 16:38:39 GMT):
```
Warning: JENKINS-41339 probably bogus PATH=/opt/go/go1.10.linux.amd64/bin:/w/workspace/fabric-chaincode-evm-verify-master-x86_64/gopath/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:~/npm/bin:/home/jenkins/.nvm/versions/node/v6.9.5/bin:/home/jenkins/.nvm/versions/node/v8.9.4/bin:$GOROOT/bin:$WORKSPACE/gopath/bin:~/npm/bin:$GOROOT/bin:$GOPATH/bin:~/npm/bin:$PATH:$WORKSPACE/gopath/src/github.com/hyperledger/fabric/build/bin:/home/jenkins/.nvm/versions/node/v6.9.5/bin:/home/jenkins/.nvm/versions/node/v8.9.4/bin:$WORKSPACE/gopath/src/github.com/hyperledger/fabric/.build/bin:$WORKSPACE/gopath/src/github.com/hyperledger/fabric/build/bin:/home/jenkins/.nvm/versions/node/v6.9.5/bin:/home/jenkins/.nvm/versions/node/v8.9.4/bin:$WORKSPACE/gopath/src/github.com/hyperledger/fabric/.build/bin; perhaps you meant to use ‘PATH+EXTRA=/something/bin’?
```
rameshthoomu (Thu, 09 Aug 2018 16:41:46 GMT):
@swetha https://gerrit.hyperledger.org/r/#/c/25363/
rameshthoomu (Thu, 09 Aug 2018 16:42:29 GMT):
@jwagantall could you please review this change and merge pls https://gerrit.hyperledger.org/r/#/c/25363/
swetha (Thu, 09 Aug 2018 16:47:41 GMT):
Thanks @rameshthoomu & @jtclark
swetha (Thu, 09 Aug 2018 16:47:41 GMT):
Thanks @rameshthoomu & @jtclark !
jtclark (Fri, 10 Aug 2018 00:22:01 GMT):
@rameshthoomu, @scottz, @latitiah, @sambhavdutt - please have a look at https://jira.hyperledger.org/browse/FABCI-7. With @jwagantall support, I was able to implement a *new tab* that highlights the merge jobs (production), and a new build-monitor dashboard view (sandbox).
jtclark (Fri, 10 Aug 2018 00:24:27 GMT):
@cbf :point_up_tone2: FYI - this is to address the "overall health" feedback we heard during the CI playback
scottz (Fri, 10 Aug 2018 00:32:10 GMT):
That's a lot of jobs. Can we keep only the "master branch" merge jobs and daily SVT jobs and the interop job (once we establish it) here on this birds-eye-openstream tab, and move all others to another tab for the birds-eye-prev-rls?
jtclark (Fri, 10 Aug 2018 00:46:26 GMT):
@scottz sure, we can have as many or as few as we want.
jtclark (Fri, 10 Aug 2018 00:47:24 GMT):
as we discussed, we started with highlighting all MERGE jobs, but if that's too many, we should def narrow it down to the most important.
jtclark (Fri, 10 Aug 2018 00:48:15 GMT):
@scottz re: multiple tabs, in my opinion, that defeats the purpose. one tab is enough, IMHO.
jtclark (Fri, 10 Aug 2018 00:50:23 GMT):
https://jenkins.hyperledger.org/sandbox/view/Build-Monitor/ <---- this to me is where we should go.
rameshthoomu (Fri, 10 Aug 2018 04:59:26 GMT):
@scottz we have couple of more options as per the build monitor plugin https://github.com/jan-molak/jenkins-build-monitor-plugin#i-have-too-many-jobs-on-one-screen-what-should-i-do.. I have requested LF team to install required plugins in sandbox.. Once these are installed, will look into it and see how we can minimize these with the filter option
rameshthoomu (Fri, 10 Aug 2018 05:05:05 GMT):
Also, we have to follow consistent names across the repositories. TODO#
vijay.bP (Fri, 10 Aug 2018 12:58:00 GMT):
Hi @harsha @SriramaSharma i have enabled the node for fabric-daily-ppc64le, it is getting failure when i tried in sandbox.
rameshthoomu (Fri, 10 Aug 2018 13:34:35 GMT):
@vijay.bP Update the status here FAB-10778
vijay.bP (Fri, 10 Aug 2018 13:57:01 GMT):
sure, Thanks
SriramaSharma (Fri, 10 Aug 2018 15:23:20 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=q2x4hF22wLYn59pxm) @vijay.bP Hi @vijay.bP , could you please point me to the build logs ? I believe @jwagantall has given me access to sandbox. it will be great if you could point me to the job which I can run and play around with to have it fixed on Power
SriramaSharma (Fri, 10 Aug 2018 15:24:40 GMT):
@vijay.bP never mind ! I got it - https://jenkins.hyperledger.org/sandbox/view/Build-Monitor/job/fabric-end-2-end-daily-master-ppc64le/
rameshthoomu (Fri, 10 Aug 2018 15:26:10 GMT):
@SriramaSharma e2e jobs are working as expected.. Issue is only with unit-tests
vijay.bP (Fri, 10 Aug 2018 15:27:46 GMT):
@SriramaSharma Please check with this link https://jenkins.hyperledger.org/sandbox/job/fabric-daily-ppc64le/6/console i guess not the above one
rameshthoomu (Fri, 10 Aug 2018 15:27:47 GMT):
@SriramaSharma triggered this job after updating the gopath https://jenkins.hyperledger.org/sandbox/job/fabric-daily-ppc64le/8/console
rameshthoomu (Fri, 10 Aug 2018 15:28:23 GMT):
@vijay.bP that's a gopath issue fixed and triggered new one just now..
vijay.bP (Fri, 10 Aug 2018 15:28:41 GMT):
ok
SriramaSharma (Fri, 10 Aug 2018 15:35:24 GMT):
@rameshthoomu Thanks! I just saw it. I see that build is going through. Hopefully it goes through this time.
rameshthoomu (Fri, 10 Aug 2018 17:03:44 GMT):
@sambhavdutt seems nightly-release-1.2 builds are failing since two days.. Is there any known issue in integration tests?
sambhavdutt (Fri, 10 Aug 2018 18:07:36 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=qaZwS7PwMgvFh9qam) @rameshthoomu I saw that the integration tests are timing out in one test but integration are passing in the fabric-builds, so I didn't create a bug thinking it would be a slow test error like curl
sambhavdutt (Fri, 10 Aug 2018 18:08:20 GMT):
I'll go ahead and create one now
rameshthoomu (Fri, 10 Aug 2018 18:08:46 GMT):
Could you please create a bug and assign it to @latitiah
sambhavdutt (Fri, 10 Aug 2018 18:09:10 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=xMnXKxMf4PAaf7HF4) @rameshthoomu will do, thanks
latitiah (Fri, 10 Aug 2018 18:14:56 GMT):
@sambhavdutt @rameshthoomu : I'm already working on it. I noticed it yesterday
sambhavdutt (Fri, 10 Aug 2018 18:24:39 GMT):
@rameshthoomu @latitiah
FAB-11546
VuiLenDi (Mon, 13 Aug 2018 08:44:21 GMT):
Has joined the channel.
JaccobSmith (Tue, 14 Aug 2018 03:07:14 GMT):
Has joined the channel.
davidkel (Tue, 14 Aug 2018 11:37:27 GMT):
@rameshthoomu Seeing a problem with the node chaincode builds on Z. Don't think it's related to the CR could be environmental ?
rameshthoomu (Tue, 14 Aug 2018 13:51:18 GMT):
@sambhavdutt could you pls check
sambhavdutt (Tue, 14 Aug 2018 13:52:21 GMT):
@rameshthoomu will check
rameshthoomu (Tue, 14 Aug 2018 13:54:04 GMT):
@davidkel there is an issue while removing /tmp/fabric-shim directory
rameshthoomu (Tue, 14 Aug 2018 13:54:12 GMT):
Have to remove this manually..
gennadyl (Tue, 14 Aug 2018 14:46:58 GMT):
@jtclark Any news about fabric-chaincode-java CI?
jtclark (Tue, 14 Aug 2018 14:51:09 GMT):
@gennadyl our sandbox has been experiencing intermittent outages over the last 24 hours, so not much movement yet. things look much better today, so I'm working on getting this in-review today
jtclark (Tue, 14 Aug 2018 14:51:52 GMT):
it's my next highest priority task.
gennadyl (Tue, 14 Aug 2018 14:52:33 GMT):
@jtclark Great. Waiting for it - it become blocking - I can't run any real tests, that really use java chaincode
jtclark (Tue, 14 Aug 2018 14:52:49 GMT):
@gennadyl understood. it DEF in my queue.
jtclark (Tue, 14 Aug 2018 14:52:49 GMT):
@gennadyl understood. it's DEF in my queue.
gennadyl (Tue, 14 Aug 2018 14:52:56 GMT):
Thanks
jtclark (Tue, 14 Aug 2018 14:53:06 GMT):
yw. thanks for checking in.
davidkel (Tue, 14 Aug 2018 14:53:26 GMT):
ok thanks @rameshthoomu will it be working again soon ?
rameshthoomu (Tue, 14 Aug 2018 15:00:33 GMT):
@davidkel re-triggered the job now.. this should work now.
rameshthoomu (Tue, 14 Aug 2018 15:01:24 GMT):
@jtclark let me know if you need any help on fabric-chaincode-java CI task..
troyronda (Tue, 14 Aug 2018 17:32:08 GMT):
I'm periodically seeing rm: cannot remove '/tmp/fabric-shim/chaincode/hyperledger/fabric/peer/mychannel.block': Permission denied in the Go SDK S390 job (which fails the job). Created https://jira.hyperledger.org/browse/FABCI-61
rameshthoomu (Tue, 14 Aug 2018 17:45:30 GMT):
@troyronda sometimes our s390x cleanup script is not deleting /tmp/fabric-shim directory.. We updated scripts to delete this directory but it seems some jobs are missing this command
rameshthoomu (Tue, 14 Aug 2018 17:45:32 GMT):
https://github.com/hyperledger/ci-management/blob/8a3734e641f25830d7561ce707c85a440cf2dc25/jjb/fabric-ca/fabric-ca-jobs.yaml#L232
troyronda (Tue, 14 Aug 2018 17:49:33 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=rE76YKr7phtjmnfME) @rameshthoomu Does this cause the permission denied error?
rameshthoomu (Tue, 14 Aug 2018 17:56:55 GMT):
yes.. I think fabric-sdk-node or fabric-chaincode-node tests are setting root permissions on this directory.. So, Jenkins is unable to delete this directory.. In s390x we use a cleanup script after the build is completed.. It seems some times it's failing to delete
troyronda (Tue, 14 Aug 2018 18:03:03 GMT):
btw - are builds able to interfere with each other by using the same directory name?
jeremyphelps (Tue, 14 Aug 2018 22:24:00 GMT):
@troyronda That is a definite possibility. if they run on statically configured nodes in the same workspace.
jeremyphelps (Tue, 14 Aug 2018 22:25:16 GMT):
on a dynamically provisioned node, even if the workspace doesn't get deleted, it should not be reused for a subsequent job. Although I have heard of this happening before.
pandrejko (Wed, 15 Aug 2018 18:36:23 GMT):
@rameshthoomu We noticed the readthedocs icon links are broken again. https://jira.hyperledger.org/browse/FAB-11604 It appears the fix we added earlier for this may not work when the content topic resides inside a folder instead of in the root /source tree.
rameshthoomu (Thu, 16 Aug 2018 13:29:35 GMT):
I don't see any broken icons here https://hyperledger-fabric.readthedocs.io/en/latest/
rameshthoomu (Thu, 16 Aug 2018 13:29:57 GMT):
could you please point me the exact link which shows broken icons
suryalanka (Thu, 16 Aug 2018 13:34:22 GMT):
@rameshthoomu can we get fabric-testviewer published to nexus?
rameshthoomu (Thu, 16 Aug 2018 13:38:01 GMT):
the newer version?
rameshthoomu (Thu, 16 Aug 2018 13:46:55 GMT):
Published latest image to nexus
```
1.2.0
1.2.0-cb7dd0c
```
rameshthoomu (Fri, 17 Aug 2018 16:59:15 GMT):
@gennadyl Could you please look into the comments I have added https://jira.hyperledger.org/browse/FABCI-50
gennadyl (Fri, 17 Aug 2018 19:32:51 GMT):
I added my comment
vijay.bP (Fri, 17 Aug 2018 20:32:38 GMT):
@harsha i changed the permission and tested it on sandbox, but the job is failed, i will check that again.
harsha (Fri, 17 Aug 2018 20:33:45 GMT):
@vijay.bP I have pushed a PR via https://gerrit.hyperledger.org/r/#/c/25637/ , this should address peer UT failure on ppc64le.
harsha (Sat, 18 Aug 2018 09:30:02 GMT):
@rameshthoomu @vijay.bP With above PR, Peer UT is now passing on ppc64le.
vijay.bP (Sat, 18 Aug 2018 13:19:01 GMT):
@harsha ok :thumbsup:
minskeyguo (Sat, 18 Aug 2018 20:24:24 GMT):
Has joined the channel.
sudeshrshetty (Mon, 20 Aug 2018 16:27:36 GMT):
@rameshthoomu https://jenkins.hyperledger.org/job/fabric-sdk-go-tests-verify-x86_64/ `All nodes of label ‘hyp-x86_64’ are offline`
is everything alright?
jtclark (Mon, 20 Aug 2018 16:28:17 GMT):
the build queue is tacking up
jtclark (Mon, 20 Aug 2018 16:28:17 GMT):
the build queue is stacking up
sambhavdutt (Mon, 20 Aug 2018 16:28:18 GMT):
@sudeshrshetty the `x86_64` nodes are offline
sambhavdutt (Mon, 20 Aug 2018 16:29:30 GMT):
from sometime, the jobs will be active as this is being looked into
sudeshrshetty (Mon, 20 Aug 2018 16:42:12 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=DW4mLCQhuSkSDN9KB) @sambhavdutt Thanks
rameshthoomu (Mon, 20 Aug 2018 17:06:47 GMT):
@dave.enyeart @mastersingh24 any ETA on publishing 0.4.11 baseimage with https://github.com/hyperledger/fabric-baseimage/blob/master/scripts/common/setup.sh#L70 (node js 8.11.3 version)
dave.enyeart (Mon, 20 Aug 2018 17:10:41 GMT):
@rameshthoomu I think we could cut it now... would you like to prepare the cut CR and try it in fabric tests? then i can +2 and merge
rameshthoomu (Mon, 20 Aug 2018 17:13:33 GMT):
ok @dave.enyeart
dave.enyeart (Mon, 20 Aug 2018 17:15:22 GMT):
be sure to make the new couchdb image and that the tests exercise it... that was a major change
rameshthoomu (Mon, 20 Aug 2018 17:15:36 GMT):
x86_64 build nodes went offline.. Created ticket to LF team Hyperledger Helpdesk #59890
rameshthoomu (Mon, 20 Aug 2018 17:16:21 GMT):
I will build 0.4.11 baseimage and push it to my personal dockerhub account and will ask one of my team member to test this..
rameshthoomu (Mon, 20 Aug 2018 17:16:52 GMT):
Do you suggest any specific tests on couchdb otherthan e2e tests?
dave.enyeart (Mon, 20 Aug 2018 17:17:18 GMT):
the e2e that uses couchdb would be sufficient
rameshthoomu (Mon, 20 Aug 2018 17:17:24 GMT):
ok
manish-sethi (Mon, 20 Aug 2018 17:19:19 GMT):
@rameshthoomu - Can you have a look at https://gerrit.hyperledger.org/r/#/c/24431/
'SmokeTest' not starting for this
rameshthoomu (Mon, 20 Aug 2018 17:22:46 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=nPNQ7jw372L3GvzEw) @manish-sethi
rameshthoomu (Mon, 20 Aug 2018 17:23:08 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=nPNQ7jw372L3GvzEw) @manish-sethi x86_64 build nodes went offline.. Created ticket to LF team Hyperledger Helpdesk #59890
manish-sethi (Mon, 20 Aug 2018 17:24:19 GMT):
Thanks @rameshthoomu for the update
rameshthoomu (Mon, 20 Aug 2018 18:00:58 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=BM8YAxeYjpTRyzu6A) @harsha Thanks @harsha for the patch..
rameshthoomu (Mon, 20 Aug 2018 18:01:34 GMT):
@vijay.bP did you run unit-tests on power nodes? if yes, could you please update the JIRA with the results
vijay.bP (Mon, 20 Aug 2018 18:03:50 GMT):
@harsha I will check and give the update.
yacovm (Mon, 20 Aug 2018 18:05:14 GMT):
@rameshthoomu can you or anyone else tell me what's wrong with https://gerrit.hyperledger.org/r/#/c/25533/ ? why isn't it building?
harsha (Mon, 20 Aug 2018 18:07:03 GMT):
@vijay.bP I have triggered one UT on ppc64le.
harsha (Mon, 20 Aug 2018 18:07:03 GMT):
@rameshthoomu @vijay.bP I have triggered one UT on ppc64le.
rameshthoomu (Mon, 20 Aug 2018 18:08:25 GMT):
@yacovm all x nodes went offline..
rameshthoomu (Mon, 20 Aug 2018 18:08:34 GMT):
Hyperledger Helpdesk #59890 -- LF team is working on this..
yacovm (Mon, 20 Aug 2018 18:22:32 GMT):
oh ok thanks
vijay.bP (Mon, 20 Aug 2018 19:07:39 GMT):
@harsha https://jenkins.hyperledger.org/sandbox/job/fabric-daily-ppc64le/2/console
rameshthoomu (Mon, 20 Aug 2018 19:40:55 GMT):
@gennadyl @C0rWin observed below error while build fabric-chaincode-javaenv image. Could you please check
```
00:02:05.376 ---> 418562592533
00:02:05.377 Step 8/31 : ADD build/distributions/ /root/
00:02:05.377 ADD failed: stat /var/lib/docker/tmp/docker-builder250372208/build/distributions: no such file or directory
00:02:05.398 Build step 'Execute shell' marked build as failure
```
rameshthoomu (Mon, 20 Aug 2018 19:41:17 GMT):
same observed in local machine.
rameshthoomu (Mon, 20 Aug 2018 20:40:07 GMT):
@dave.enyeart @chris.elder Observed below error while build couchdb on s390x
```
00:00:27.380 E: Unable to locate package libicu55
00:00:27.778 The command '/bin/sh -c apt-get update -y && apt-get install -y --no-install-recommends ca-certificates curl erlang-nox erlang-reltool libicu55 libmozjs185-1.0 openssl && rm -rf /var/lib/apt/lists/*' returned a non-zero code: 100
00:00:27.779 Makefile:125: recipe for target 'build/image/couchdb/.dummy' failed
```
dave.enyeart (Mon, 20 Aug 2018 20:41:52 GMT):
@rameshthoomu is this based on the new base-image? Any issues on the other platforms?
rameshthoomu (Mon, 20 Aug 2018 20:43:11 GMT):
we are building on x and z.. I don't see any issue in x
rameshthoomu (Mon, 20 Aug 2018 20:44:07 GMT):
while building the cochdb image with latest couchdb changes https://gerrit.hyperledger.org/r/#/c/25711/
dave.enyeart (Mon, 20 Aug 2018 20:52:47 GMT):
@rameshthoomu The prior CRs got verified fine... does the IS_RELEASE=true CR do something different?
rameshthoomu (Mon, 20 Aug 2018 20:53:41 GMT):
When prior CR's got verified, the `make dependent-images` target was in action in CI..
rameshthoomu (Mon, 20 Aug 2018 20:53:41 GMT):
When prior CR's got verified, the `make dependent-images` target was not in action in CI..
rameshthoomu (Mon, 20 Aug 2018 20:54:17 GMT):
which builds all third party images..
dave.enyeart (Mon, 20 Aug 2018 20:54:35 GMT):
ok, so we never tried to build the 3rd party images until today?
rameshthoomu (Mon, 20 Aug 2018 20:55:18 GMT):
yes.. it;s there in the release jobs..
dave.enyeart (Mon, 20 Aug 2018 20:55:53 GMT):
i mean, this is the first time building the 3rd party images after the couchdb images changes?
rameshthoomu (Mon, 20 Aug 2018 20:56:10 GMT):
yes
dave.enyeart (Mon, 20 Aug 2018 20:56:31 GMT):
ok, we'll see what happens upon your reverify
rameshthoomu (Mon, 20 Aug 2018 20:56:39 GMT):
ok
rameshthoomu (Mon, 20 Aug 2018 20:58:04 GMT):
it's again failed
dave.enyeart (Mon, 20 Aug 2018 21:04:45 GMT):
@rameshthoomu any idea why it would succeed on x but not z?
rameshthoomu (Mon, 20 Aug 2018 21:07:10 GMT):
it seems the libicu55 package is not available in z nodes.. Have to look into this..
rameshthoomu (Mon, 20 Aug 2018 21:07:40 GMT):
will let you know..
harsha (Mon, 20 Aug 2018 22:24:17 GMT):
@vijay.bP @rameshthoomu Pushed another PR via https://gerrit.hyperledger.org/r/#/c/25735/ to address issue in https://jenkins.hyperledger.org/sandbox/job/fabric-daily-ppc64le/2/console
harryc (Mon, 20 Aug 2018 22:39:54 GMT):
Has joined the channel.
harryc (Mon, 20 Aug 2018 23:32:25 GMT):
Has left the channel.
davidkel (Tue, 21 Aug 2018 09:16:51 GMT):
Is it possible to re-run a failed merge build for fabric-chaincode-node, or is the only way to drive it to submit another CR albeit some minor change in order to get it to re-run ?
rameshthoomu (Tue, 21 Aug 2018 09:19:35 GMT):
@davidkel you can post `remerge` comment in the failed patchset..
davidkel (Tue, 21 Aug 2018 09:24:07 GMT):
Thanks for the quick reply @rameshthoomu, and also thanks for reviewing and merging the node-sdk changes.
jtclark (Tue, 21 Aug 2018 14:51:21 GMT):
@vijay.bP one more error:
jtclark (Tue, 21 Aug 2018 14:51:27 GMT):
```
/w/workspace/ci-management-tox-verify-master/docs/source/newproject-startup.rst:59:Unexpected indentation.
```
vijay.bP (Tue, 21 Aug 2018 14:52:54 GMT):
ya i found the Unexpected indentation on line 57, still trying to figure out its showing on number of lines
rameshthoomu (Tue, 21 Aug 2018 15:00:35 GMT):
@vijay.bP Don't worry about the errors.. It's a WIP patch
vijay.bP (Tue, 21 Aug 2018 15:01:23 GMT):
ok ill do the changes what you have mentioned and push again
dave.enyeart (Tue, 21 Aug 2018 15:15:43 GMT):
@rameshthoomu who can review https://gerrit.hyperledger.org/r/#/c/25675/. maybe @jwagantall ?
rameshthoomu (Tue, 21 Aug 2018 15:17:07 GMT):
yes.. Only @jwagantall has permissions to merge..
dave.enyeart (Tue, 21 Aug 2018 15:22:05 GMT):
ok, thanks in advance @jwagantall :)
rameshthoomu (Tue, 21 Aug 2018 19:44:38 GMT):
@gennadyl Re-triggered fabric-chaincode-java merge after CI patch is merged, I see fabric-chaincode-javaenv image has been pushed to nexus with amd64-latest and amd64-1.2.0-
rameshthoomu (Tue, 21 Aug 2018 20:40:29 GMT):
@dave.enyeart https://gerrit.hyperledger.org/r/#/c/25773/
bdjidi (Tue, 21 Aug 2018 22:47:36 GMT):
Has joined the channel.
MHBauer (Wed, 22 Aug 2018 01:13:39 GMT):
Has joined the channel.
rameshthoomu (Wed, 22 Aug 2018 12:58:51 GMT):
@harrijk I see this failure https://jenkins.hyperledger.org/job/fabric-baseimage-verify-docker-s390x/219/consoleFull in s390x
harrijk (Wed, 22 Aug 2018 13:23:54 GMT):
@rameshthoomu I will take a look
rameshthoomu (Wed, 22 Aug 2018 13:25:02 GMT):
thanks @harrijk
rameshthoomu (Wed, 22 Aug 2018 18:50:11 GMT):
@dave.enyeart the patch is ready for review now https://gerrit.hyperledger.org/r/#/c/25773/ Thanks @harrijk for the fix
dave.enyeart (Wed, 22 Aug 2018 19:02:13 GMT):
@rameshthoomu +2ed
rameshthoomu (Thu, 23 Aug 2018 16:38:56 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=Sspcfs97anGa9wvwE) @bretharrison ^^
rameshthoomu (Thu, 23 Aug 2018 19:01:11 GMT):
@jtclark Could you please work on these two FABCI-72 and FABCI-73 ( Both are Highest Priority) as per @dave.enyeart these are blockers for SDK integration testing..
rameshthoomu (Thu, 23 Aug 2018 19:04:02 GMT):
@dave.enyeart FYI javaenv image is not available on s390x platform..
dave.enyeart (Thu, 23 Aug 2018 19:07:14 GMT):
@rameshthoomu ok, what needs to be done?
rameshthoomu (Thu, 23 Aug 2018 19:09:07 GMT):
we have to add a s390x job for fabric-chaincode-java builds and publish images which is compaitable for s390x platforms
rameshthoomu (Thu, 23 Aug 2018 19:09:07 GMT):
we have to add a s390x job for fabric-chaincode-java builds and publish javaenv image which is compatible for s390x platforms.
rameshthoomu (Thu, 23 Aug 2018 19:09:30 GMT):
Not sure whether it supports or not.. have to check @gennadyl
rameshthoomu (Thu, 23 Aug 2018 19:09:30 GMT):
Not sure whether the existing fabric-chaincode-java build file supports s390x or not.. have to check @gennadyl
rameshthoomu (Thu, 23 Aug 2018 19:13:13 GMT):
@jtclark there?
jtclark (Thu, 23 Aug 2018 20:33:42 GMT):
sorry here now
jtclark (Thu, 23 Aug 2018 20:33:42 GMT):
@rameshthoomu ^
jtclark (Thu, 23 Aug 2018 20:33:47 GMT):
@rameshthoomu yes, I'll work on these.
rameshthoomu (Thu, 23 Aug 2018 20:36:15 GMT):
Worked on FAB-72 https://gerrit.hyperledger.org/r/#/c/25837/
rameshthoomu (Thu, 23 Aug 2018 20:36:15 GMT):
Worked on FABCI-72 https://gerrit.hyperledger.org/r/#/c/25837/
rameshthoomu (Thu, 23 Aug 2018 21:01:54 GMT):
I may not be available till afternoon tomorrow
dave.enyeart (Fri, 24 Aug 2018 18:32:53 GMT):
@rameshthoomu @bretharrison Do you know why the merge job always fails on fabric release-1.2? appears to be related to node sdk. e.g. https://gerrit.hyperledger.org/r/#/c/25827/
rameshthoomu (Fri, 24 Aug 2018 18:34:41 GMT):
@sambhavdutt ^^ any open issue on this?
dave.enyeart (Fri, 24 Aug 2018 18:35:11 GMT):
actually it is not specific to release-1.2, also fails on fabric master merge job, e.g.: https://gerrit.hyperledger.org/r/#/c/25463/
dave.enyeart (Fri, 24 Aug 2018 18:35:31 GMT):
but not always
sambhavdutt (Fri, 24 Aug 2018 18:36:19 GMT):
@rameshthoomu yes
https://jira.hyperledger.org/browse/FABN-890
rameshthoomu (Fri, 24 Aug 2018 18:37:11 GMT):
ok Good.. Assigned to Brett..
gennadyl (Sat, 25 Aug 2018 08:24:13 GMT):
@rameshthoomu s390x not supported yet
mastersingh24 (Sat, 25 Aug 2018 10:18:47 GMT):
Is CI down?
C0rWin (Sat, 25 Aug 2018 10:35:35 GMT):
> Is CI down?
seems so :/
sambhavdutt (Sat, 25 Aug 2018 13:27:01 GMT):
@C0rWin yes, looks like al x86_64 nodes are offline
dave.enyeart (Sat, 25 Aug 2018 15:47:08 GMT):
@rameshthoomu @jwagantall It appears no CI jobs are starting today
sambhavdutt (Sat, 25 Aug 2018 15:48:29 GMT):
@dave.enyeart yes, no jobs triggering on the `x86_64` nodes, and many waiting in line even if they come back online, it might take a while
dave.enyeart (Sat, 25 Aug 2018 15:49:09 GMT):
Do we know if anybody is working to get it online?
sambhavdutt (Sat, 25 Aug 2018 15:51:00 GMT):
@dave.enyeart maybe not yet. This incident has been reported the in the CI channels
dave.enyeart (Sat, 25 Aug 2018 15:51:41 GMT):
anybody have cell phone number for those that could help?
sambhavdutt (Sat, 25 Aug 2018 15:54:33 GMT):
I dont have number but I'll check online
gennadyl (Sat, 25 Aug 2018 16:15:24 GMT):
@rameshthoomu Hi Ramesh. Can you change in java docker image push scripts *$NEXUS_URL/$ORG_NAME-chaincode-javaenv:* to *$NEXUS_URL/$ORG_NAME-javaenv:*
gennadyl (Sat, 25 Aug 2018 16:15:54 GMT):
It is same as it was originally: https://hub.docker.com/r/hyperledger/fabric-javaenv/
gennadyl (Sat, 25 Aug 2018 16:15:54 GMT):
I want to keep same name: https://hub.docker.com/r/hyperledger/fabric-javaenv/
jtclark (Sat, 25 Aug 2018 16:19:16 GMT):
@dave.enyeart, @sambhavdutt, @C0rWin, @gennadyl - I just texted @tijohnson to see if he could help
dave.enyeart (Sat, 25 Aug 2018 16:19:47 GMT):
thanks!
rameshthoomu (Sat, 25 Aug 2018 16:51:30 GMT):
@sambhavdutt @jtclark did any one create Help desk ticket
sambhavdutt (Sat, 25 Aug 2018 16:52:09 GMT):
I put a word to Jessica and Tim, let me create a JIRA now
rameshthoomu (Sat, 25 Aug 2018 16:58:15 GMT):
not jira
rameshthoomu (Sat, 25 Aug 2018 16:58:19 GMT):
Cretaed Helpdesk ticket [Hyperledger Helpdesk #60159
sambhavdutt (Sat, 25 Aug 2018 16:58:46 GMT):
@rameshthoomu ok, I'll close mine
sambhavdutt (Sat, 25 Aug 2018 16:59:46 GMT):
I closed the JIRA ticket for this
rameshthoomu (Sat, 25 Aug 2018 17:02:40 GMT):
@jtclark @sambhavdutt @vijay.bP Pls follow instruction mentioned to reachout LF team if need quick help https://github.com/hyperledger/ci-management/blob/master/docs/index.rst
rameshthoomu (Sat, 25 Aug 2018 17:03:30 GMT):
If nodes are not available or Jenkins is down pls create help desk ticket.. Pinging in channels may not work during non working hours
sambhavdutt (Sat, 25 Aug 2018 17:03:59 GMT):
@rameshthoomu thank you. Will do this in case of similar incident
rameshthoomu (Sat, 25 Aug 2018 17:26:56 GMT):
@sambhavdutt Could you please create a JIRA to send a notification to LF & CI team, if the build queue is more than 1 hr..
rameshthoomu (Sat, 25 Aug 2018 17:27:24 GMT):
Please assign this to me.
sambhavdutt (Sat, 25 Aug 2018 17:27:28 GMT):
@rameshthoomu will do now
rameshthoomu (Sat, 25 Aug 2018 17:29:42 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=Ypc3MoB9hCx97ihsv) @gennadyl Will work on this.. But this may take time to merge as the nodes went offline..
rameshthoomu (Sat, 25 Aug 2018 17:32:51 GMT):
https://gerrit.hyperledger.org/r/#/c/25887/
sambhavdutt (Sat, 25 Aug 2018 17:45:00 GMT):
The nodes are offline still, created a ticket in JIRA
https://jira.hyperledger.org/browse/FABCI-75
rameshthoomu (Sat, 25 Aug 2018 18:05:34 GMT):
seems x nodes back in action now
rameshthoomu (Sat, 25 Aug 2018 18:05:41 GMT):
queue is clearing
sambhavdutt (Sat, 25 Aug 2018 18:05:45 GMT):
looks like the worker nodes for x86_64 are coming back online. I can see two jobs executing on the `x` nodes. However it will take a while as there are jobs waiting in queue
sambhavdutt (Sat, 25 Aug 2018 18:05:50 GMT):
yes
gennadyl (Sat, 25 Aug 2018 18:09:12 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=jdMMKM77NDwLScgKn) Thanks a lot
rameshthoomu (Sat, 25 Aug 2018 18:32:58 GMT):
@gennadyl the patch had been merged and retirggered chaincode- java merge job to push javaenv image to nexus
rameshthoomu (Sat, 25 Aug 2018 18:33:28 GMT):
pls check your tests now with fabric-javaenv image
gennadyl (Sat, 25 Aug 2018 19:10:54 GMT):
Ok, thanks
rameshthoomu (Mon, 27 Aug 2018 19:45:55 GMT):
@gennadyl Updated fabric-sdk-java CI scripts to pull javaenv image from nexus and re-tag .. I have reverified the java patch https://gerrit.hyperledger.org/r/#/c/25825/ and it worked
rameshthoomu (Mon, 27 Aug 2018 19:45:55 GMT):
@gennadyl @rickr, I have Updated fabric-sdk-java CI scripts to pull javaenv image from nexus and re-tag .. I have reverified the java patch https://gerrit.hyperledger.org/r/#/c/25825/ and it worked
rameshthoomu (Tue, 28 Aug 2018 16:44:22 GMT):
@vijay.bP could you please change this to BASE_VERSION and test e2e tests from master branch https://github.com/hyperledger/fabric-ca/blob/master/Makefile#L41
vijay.bP (Tue, 28 Aug 2018 17:37:08 GMT):
ok
vijay.bP (Tue, 28 Aug 2018 17:37:29 GMT):
went for lunch just came
vijay.bP (Tue, 28 Aug 2018 17:37:43 GMT):
ok
vijay.bP (Tue, 28 Aug 2018 18:39:11 GMT):
14:34:51 java.lang.OutOfMemoryError: Java heap space
vijay.bP (Tue, 28 Aug 2018 18:39:25 GMT):
https://jenkins.hyperledger.org/sandbox/job/fabric-ca-merge-end-2-end-x86_64/1/consoleFull
vijay.bP (Tue, 28 Aug 2018 18:40:02 GMT):
@rameshthoomu please check
AbhinayB (Wed, 29 Aug 2018 05:08:59 GMT):
Has joined the channel.
rameshthoomu (Wed, 29 Aug 2018 06:40:33 GMT):
@sambhavdutt Did you report this to LF team.. I see `no space left on the device` message after a successful build
```
00:40:24.571
00:40:24.571 gzip: stdout: No space left on device
00:40:24.607 Build step 'Execute shell' marked build as failure
00:40:24.659 $ ssh-agent -k
```
rameshthoomu (Wed, 29 Aug 2018 06:43:04 GMT):
@tijohnson Please see this job output https://jenkins.hyperledger.org/view/Daily/job/fabric-nightly-release-job-master-x86_64/89/console
sambhavdutt (Wed, 29 Aug 2018 13:05:26 GMT):
@rameshthoomu , sorry didn't report in the pipeline or any ci channels, I opened a JIRA ticket for this about 2 days back, but left it unassigned.
rameshthoomu (Wed, 29 Aug 2018 13:08:27 GMT):
You can create a JIRA for that but It's not related to code issue.. it's an environment issue..
rameshthoomu (Wed, 29 Aug 2018 13:08:33 GMT):
check with LF team
sambhavdutt (Wed, 29 Aug 2018 13:08:51 GMT):
@rameshthoomu thanks, will check
jtclark (Wed, 29 Aug 2018 13:46:01 GMT):
good morning all
dave.enyeart (Wed, 29 Aug 2018 20:53:41 GMT):
@rameshthoomu @jwagantall Can https://gerrit.hyperledger.org/r/#/c/25837/ be merged now?
rameshthoomu (Thu, 30 Aug 2018 08:03:16 GMT):
yes.. I have asked @jwagantall to give +2.. I can not merge this as I have submitted that change..
rameshthoomu (Thu, 30 Aug 2018 18:41:29 GMT):
@dave.enyeart here is the final patch to pull images and binaries from nexus https://gerrit.hyperledger.org/r/#/c/23361/
rameshthoomu (Thu, 30 Aug 2018 18:41:58 GMT):
Could you please test this and merge this change..
dave.enyeart (Thu, 30 Aug 2018 21:33:20 GMT):
@rameshthoomu It worked well for me... add a few minor comments
dave.enyeart (Thu, 30 Aug 2018 21:33:20 GMT):
@rameshthoomu It worked well for me... I added a few minor comments
dave.enyeart (Thu, 30 Aug 2018 21:34:00 GMT):
@jwagantall How about a merge on https://gerrit.hyperledger.org/r/#/c/25837/ ?
jwagantall (Thu, 30 Aug 2018 23:34:53 GMT):
thanks! looks good to me
dave.enyeart (Fri, 31 Aug 2018 15:32:47 GMT):
@rameshthoomu @sambhavdutt @jtclark Could you take a look at the release-1.2 CI failures? I've commented in https://jira.hyperledger.org/browse/FABN-890.
sambhavdutt (Fri, 31 Aug 2018 15:33:22 GMT):
@dave.enyeart Sure, will check now
sambhavdutt (Fri, 31 Aug 2018 15:37:30 GMT):
@dave.enyeart I have updated a fix for this recently. I have just updated the Gerrit link in https://jira.hyperledger.org/browse/FABN-890. comment
scottz (Fri, 31 Aug 2018 15:46:44 GMT):
@sambhavdutt When you are through with Dave... it looks like the daily master PTE tests did not run last night. When I looked to determine why, it looks like the upstream job did not work: https://jenkins.hyperledger.org/view/fabric-test/job/fabric-nightly-release-job-master-x86_64/96/. Would that have prevented the pte tests from running?
sambhavdutt (Fri, 31 Aug 2018 15:52:02 GMT):
@scottz yes, that prevented the daily tests from running, the x node was out of space even when the build was successful. Updated the details morning today in the JIRA Bug for this,
FABCI-76
dave.enyeart (Fri, 31 Aug 2018 15:56:20 GMT):
Thanks @sambhavdutt ! I'll defer review to @rameshthoomu and @jwagantall
sambhavdutt (Fri, 31 Aug 2018 15:56:51 GMT):
@dave.enyeart Thank you
dave.enyeart (Fri, 31 Aug 2018 15:57:05 GMT):
BTW - always put a FAB number in the commit message
sambhavdutt (Fri, 31 Aug 2018 15:57:39 GMT):
@dave.enyeart will do
dave.enyeart (Fri, 31 Aug 2018 15:58:32 GMT):
i converted it from FABN to FAB-CI : https://jira.hyperledger.org/browse/FABCI-79
scottz (Fri, 31 Aug 2018 16:00:20 GMT):
@sambhavdutt should we apply the ci_failure label to that, and other similar bugs? Since we now have a FABCI project, I guess the fabric-ci label is not so useful anymore. The filters can sort the LF and CI issues into different list, based on project.
sambhavdutt (Fri, 31 Aug 2018 16:02:32 GMT):
@scottz yes, the FABCI project should be good, I will change the `labels`
rameshthoomu (Fri, 31 Aug 2018 16:09:53 GMT):
@sambhavdutt merged
sambhavdutt (Fri, 31 Aug 2018 16:10:18 GMT):
@rameshthoomu thank you
scottz (Fri, 31 Aug 2018 16:12:53 GMT):
https://jira.hyperledger.org/issues/?filter=12103&jql=status%20!%3D%20closed%20AND%20labels%20in%20(fabric-ci%2C%20ci_failure)%20ORDER%20BY%20project Is one version of a filter of all the open bugs generated by CI tests. After we finish editing labels we should refine this, and publicize the list. Also, some of these bugs will automatically show up on the Defect lists of the v1.3 page (those in Fabric project that are not quality/sdk issues); we need to make sure you and the team create the CI_FAILURE bugs by filling in the correct fields in such a way that they will be visible on the "Needs Triage" defect list: https://jira.hyperledger.org/issues/?filter=12267
sambhavdutt (Fri, 31 Aug 2018 16:16:10 GMT):
@scottz thanks, will update the JIRA items accordingly
dave.enyeart (Fri, 31 Aug 2018 16:21:32 GMT):
@sambhavdutt @rameshthoomu Thanks for merging FABCI-79. Can we see if it works now, by re-running the merge jobs for a fabric release-1.2 CR. For example https://gerrit.hyperledger.org/r/#/c/26010/.
sambhavdutt (Fri, 31 Aug 2018 16:23:18 GMT):
@dave.enyeart yes, @rameshthoomu will be able to retrigger the job
nfrunza (Fri, 31 Aug 2018 16:24:33 GMT):
Has left the channel.
rameshthoomu (Fri, 31 Aug 2018 16:49:13 GMT):
@dave.enyeart s390x job worked https://jenkins.hyperledger.org/view/Daily/job/fabric-end-2-end-daily-release-1.2-s390x/
rameshthoomu (Fri, 31 Aug 2018 16:49:54 GMT):
will check x job and let you know
dave.enyeart (Fri, 31 Aug 2018 16:55:43 GMT):
@rameshthoomu end-2-end also passed on release-1.2 fabric-ca CR https://gerrit.hyperledger.org/r/#/c/25918/ now. Question - why is there no regular fabric-ca-verify job for fabric-ca release-1.2, like there is for fabric-ca master?
dave.enyeart (Fri, 31 Aug 2018 16:56:25 GMT):
end-2-end appears to be the only job that runs in fabric-ca release-1.2
odowdaibm (Fri, 31 Aug 2018 17:15:31 GMT):
Has joined the channel.
sambhavdutt (Fri, 31 Aug 2018 17:40:35 GMT):
@dave.enyeart the e2e is successful on the x node too
https://jenkins.hyperledger.org/view/Daily/job/fabric-end-2-end-daily-release-1.2-x86_64/56/
rameshthoomu (Fri, 31 Aug 2018 17:56:21 GMT):
@dave.enyeart we have fabric-ca-verify-x86_64 and fabric-ca-verify-s390x jobs run on any branch in fabric-ca.. Please see the number of jobs triggered on this patch https://gerrit.hyperledger.org/r/#/c/25918/
rameshthoomu (Fri, 31 Aug 2018 17:56:55 GMT):
the job names are not configured with branch name.
dave.enyeart (Fri, 31 Aug 2018 18:03:35 GMT):
@rameshthoomu you're right, we're all good, I was looking at the final entry only... I see in earlier entries that fabric-ca-verify did indeed run.
SMiskey (Sun, 02 Sep 2018 18:50:48 GMT):
Has joined the channel.
draysams (Sun, 02 Sep 2018 19:26:33 GMT):
Has joined the channel.
gennadyl (Mon, 03 Sep 2018 11:35:49 GMT):
@rameshthoomu Can you add javaenv image pull before fabric build, in same way as you did for fabric-sdk-java?
bestbeforetoday (Mon, 03 Sep 2018 13:48:04 GMT):
I am seeing a _fabric-sdk-node_ CR build passing on X86 but failing on s390x. The failure looks to be this, which isn't something I can influence or fix:
```14:43:53 [fabric-sdk-node8-verify-master-s390x] $ /bin/bash -eu /tmp/jenkins110674015023732511.sh
14:43:53 rm: cannot remove '/tmp/fabric-shim/chaincode/hyperledger/fabric/peer/mychannel.block': Permission denied
14:43:53 rm: cannot remove '/tmp/fabric-shim/chaincode/hyperledger/fabric/peer/crypto': Permission denied
14:43:53 Build step 'Execute shell' marked build as failure
```
Can anyone help?
rameshthoomu (Mon, 03 Sep 2018 15:00:58 GMT):
@bestbeforetoday deleted /tmp/fabric-shim directory and re-trigger the job
rameshthoomu (Mon, 03 Sep 2018 15:01:06 GMT):
let me know if you see this error again
rameshthoomu (Tue, 04 Sep 2018 17:08:47 GMT):
@gennadyl sorry for the delay.. Will update changes soon and let you know the status
rameshthoomu (Tue, 04 Sep 2018 17:08:57 GMT):
@sambhavdutt Could you please look into it
sambhavdutt (Tue, 04 Sep 2018 17:15:01 GMT):
@rameshthoomu I will check on this
rameshthoomu (Tue, 04 Sep 2018 17:50:14 GMT):
@jtclark @sambhavdutt @vijay.bP @jwagantall @tijohnson --- I will be OOO on Wed, Thurs and Friday..
rameshthoomu (Tue, 04 Sep 2018 17:51:41 GMT):
I will be available on RC.. Please tag me in RC if there is any urgent request..
sambhavdutt (Tue, 04 Sep 2018 17:52:10 GMT):
@rameshthoomu yes
rameshthoomu (Tue, 04 Sep 2018 18:07:05 GMT):
@vijay.bP You have to make sure all the release jobs are up to date and make sure all release jobs are ready for 1.3 rc1 release which is in next ~1 week
vijay.bP (Tue, 04 Sep 2018 18:08:21 GMT):
ok, i am on it, if i change i'll let you know.
rameshthoomu (Tue, 04 Sep 2018 18:08:27 GMT):
We have to update nightly jobs and release jobs with javaenv image.
sambhavdutt (Tue, 04 Sep 2018 18:08:58 GMT):
should I submit for that
rameshthoomu (Tue, 04 Sep 2018 18:09:00 GMT):
Javaenv image code is available in fabric-chaincode-java repository..
rameshthoomu (Tue, 04 Sep 2018 18:10:03 GMT):
pls check this job config https://jenkins.hyperledger.org/view/fabric-chaincode-java/job/fabric-chaincode-java-merge-x86_64/configure
rameshthoomu (Tue, 04 Sep 2018 18:10:20 GMT):
```
./gradlew buildImage
```
rameshthoomu (Tue, 04 Sep 2018 18:37:41 GMT):
@vijay.bP Once the above is finish, could you please test e2e and unit tests on power nodes in sandbox and update the status in JIRA
vijay.bP (Tue, 04 Sep 2018 18:37:56 GMT):
ok
rameshthoomu (Tue, 04 Sep 2018 18:38:25 GMT):
@harsha was telling, all tests are now working as expected in sandbox.
rameshthoomu (Tue, 04 Sep 2018 18:39:17 GMT):
please test from your end and update the status.. We have to decide to include power ARCH images in 1.3 release
harsha (Tue, 04 Sep 2018 18:52:50 GMT):
@rameshthoomu FWIW, I triggered few jobs in sandbox-env earlier today. Jobs #26-#28 are passing in https://jenkins.hyperledger.org/sandbox/job/fabric-daily-ppc64le/
harsha (Tue, 04 Sep 2018 19:00:44 GMT):
@rameshthoomu @vijay.bP request you to kindly wait, until I give heads-up for fabric-daily-ppc64le to be triggered. I am checking fabric-baseimage related changes wrt ppc64le on one of the nodes. I don't want sandbox job to clear it off.
harsha (Tue, 04 Sep 2018 19:00:44 GMT):
@rameshthoomu @vijay.bP request you to kindly wait, until I give heads-up for fabric-daily-ppc64le to be triggered. I am checking fabric-baseimage related changes wrt ppc64le on one of the nodes. I don't want sandbox job to get clear it off.
vijay.bP (Tue, 04 Sep 2018 19:01:13 GMT):
ok
rameshthoomu (Wed, 05 Sep 2018 14:34:24 GMT):
https://gerrit.hyperledger.org/r/#/c/25936/ -@sambhav could you pls check this
rameshthoomu (Wed, 05 Sep 2018 14:34:29 GMT):
i mean failures
sambhavdutt (Wed, 05 Sep 2018 14:35:47 GMT):
@rameshthoomu yes, I was just looking at it, will check
rameshthoomu (Wed, 05 Sep 2018 14:37:25 GMT):
thanks
rameshthoomu (Wed, 05 Sep 2018 14:50:24 GMT):
@vijay.bP @sambhavdutt pls make sure this doc is upto date for 1.3 release Also- - https://docs.google.com/document/d/12IpQnREUoJEUj2pF2z-0Up55geItFd94fcsbAkPacTg/edit#
sambhavdutt (Wed, 05 Sep 2018 14:51:03 GMT):
@rameshthoomu sure, will check
rameshthoomu (Wed, 05 Sep 2018 14:54:42 GMT):
ask vijay to verify
rameshthoomu (Wed, 05 Sep 2018 14:54:54 GMT):
you pls work on sdk node patch failure
sambhavdutt (Wed, 05 Sep 2018 14:55:13 GMT):
@rameshthoomu yes
vijay.bP (Wed, 05 Sep 2018 14:55:37 GMT):
yes already on it.
Baha-sk (Wed, 05 Sep 2018 19:42:49 GMT):
hi, can someone from Jenkins admin look into https://jenkins.hyperledger.org/job/fabric-sdk-go-tests-verify-s390x/ please? the s390 builds are unstable
sambhavdutt (Wed, 05 Sep 2018 19:43:34 GMT):
@Baha-sk let me check
Baha-sk (Wed, 05 Sep 2018 19:43:50 GMT):
thank you @sambhavdutt , appreciate your help
rameshthoomu (Wed, 05 Sep 2018 19:55:51 GMT):
Hi @sambhavdutt
rameshthoomu (Wed, 05 Sep 2018 19:56:24 GMT):
I am seeing fabric verify jobs are failing while doing lint checking
```
00:03:31.708 gossip/privdata/reconcile_test.go:94:46: too many errors
00:03:43.206 Makefile:213: recipe for target 'linter' failed
```
rameshthoomu (Wed, 05 Sep 2018 19:56:38 GMT):
is this known issue if not, could yo please create one
rameshthoomu (Wed, 05 Sep 2018 19:57:37 GMT):
seems local build also failign at the same step..
rameshthoomu (Wed, 05 Sep 2018 19:57:51 GMT):
Could you please create highest bug if none there
sambhavdutt (Wed, 05 Sep 2018 19:57:56 GMT):
yes, and peer id failing too, not getting created,
sambhavdutt (Wed, 05 Sep 2018 19:57:58 GMT):
yes
Baha-sk (Wed, 05 Sep 2018 19:58:40 GMT):
this job just ended: https://jenkins.hyperledger.org/job/fabric-sdk-go-tests-verify-s390x/3912/
no errors in integration tests, just this script error in the build at the end:
```19:54:03 ---> create-netrc.sh
19:54:04 [fabric-sdk-go-tests-verify-s390x] $ /bin/bash -l /tmp/jenkins31278409727449894.sh
19:54:04 ++ mktemp /tmp/requirements-XXXX.txt
19:54:04 + REQUIREMENTS_FILE=/tmp/requirements-3tGI.txt
19:54:04 + cat
19:54:04 + pip install --user --quiet --upgrade pip==18.0 setuptools==40.0.0
19:54:04 Traceback (most recent call last):
19:54:04 File "/usr/local/bin/pip", line 7, in
Baha-sk (Wed, 05 Sep 2018 20:00:34 GMT):
also, I've seen these error when cleaning docker images at the beginning.. not sure if it does impact the build: ```19:42:10 ---- No containers available for deletion ----
19:42:10 ---- No snapshot images available for deletion ----
19:42:10 Error response from daemon: invalid reference format: repository name must be lowercase
19:42:10 Error response from daemon: conflict: unable to delete b96aeb4b61e3 (cannot be forced) - image has dependent child images
19:42:10 Error response from daemon: conflict: unable to delete 6f2f81c2ee04 (cannot be forced) - image has dependent child images```
Baha-sk (Wed, 05 Sep 2018 20:00:34 GMT):
also, I've seen these errors when cleaning docker images at the beginning.. not sure if it does impact the build: ```19:42:10 ---- No containers available for deletion ----
19:42:10 ---- No snapshot images available for deletion ----
19:42:10 Error response from daemon: invalid reference format: repository name must be lowercase
19:42:10 Error response from daemon: conflict: unable to delete b96aeb4b61e3 (cannot be forced) - image has dependent child images
19:42:10 Error response from daemon: conflict: unable to delete 6f2f81c2ee04 (cannot be forced) - image has dependent child images```
rameshthoomu (Wed, 05 Sep 2018 20:18:58 GMT):
@sambhavdutt Create a JIRA to clean up unused images from s390x build nodes.. I see old baseimages are also available in s390x build nodes..
rameshthoomu (Wed, 05 Sep 2018 20:19:20 GMT):
we have to keep only latest active developement images (0.4.11 or 0.4.10 versions)
Baha-sk (Wed, 05 Sep 2018 20:21:23 GMT):
@rameshthoomu will this remove these errors :```19:42:10 Error response from daemon: conflict: unable to delete b96aeb4b61e3 (cannot be forced) - image has dependent child images
19:42:10 Error response from daemon: conflict: unable to delete 6f2f81c2ee04 (cannot be forced) - image has dependent child images```?
rameshthoomu (Wed, 05 Sep 2018 20:21:55 GMT):
yes
Baha-sk (Wed, 05 Sep 2018 20:22:18 GMT):
ok great.. hopefully it will make the builds more stable
rameshthoomu (Wed, 05 Sep 2018 20:22:59 GMT):
yes right.. but this not impacting your build results..
rameshthoomu (Wed, 05 Sep 2018 20:23:26 GMT):
you can ignore above two errors for now.. @sambhavdutt will create Jira items and will work on this
rameshthoomu (Wed, 05 Sep 2018 20:24:03 GMT):
@Baha-sk Are you generating cobertura coverage report in sdk-go jobs?
Baha-sk (Wed, 05 Sep 2018 20:24:19 GMT):
ok, not sure why the builds are not stable though.. sometimes integration tests fail, and sometimes not.. and sometimes I see the errors above
rameshthoomu (Wed, 05 Sep 2018 20:24:40 GMT):
I see this
```
00:11:57.926 [Cobertura] Publishing Cobertura coverage report...
00:11:57.926
00:11:58.865 [Cobertura] No coverage results were found using the pattern '**/report.xml' relative to '/w/workspace/fabric-sdk-go-tests-verify-s390x'. Did you enter a pattern relative to the correct directory? Did you generate the XML report(s) for Cobertura?
00:11:58.865
00:11:58.865 [Cobertura] Skipped cobertura reports.
```
Baha-sk (Wed, 05 Sep 2018 20:25:07 GMT):
not sure.. but we use pure go tests, the same way as Fabric's build
Baha-sk (Wed, 05 Sep 2018 20:25:07 GMT):
not sure.. but we use pure go tests, the same way as in Fabric builds
sambhavdutt (Wed, 05 Sep 2018 20:25:20 GMT):
@rameshthoomu will do
rameshthoomu (Wed, 05 Sep 2018 20:26:00 GMT):
@sambhavdutt assign the first issue to LF team
```
00:12:00.439 + cat
00:12:00.445 + pip install --user --quiet --upgrade pip==18.0 setuptools==40.0.0
00:12:00.447 Traceback (most recent call last):
00:12:00.447 File "/usr/local/bin/pip", line 7, in
rameshthoomu (Wed, 05 Sep 2018 20:27:48 GMT):
@Baha-sk I think the cobertura coverage report name should be `**/cobertura-coverage.xml` not the `**/report.xml`
rameshthoomu (Wed, 05 Sep 2018 20:27:55 GMT):
will test this in sandbox and let you know..
Baha-sk (Wed, 05 Sep 2018 20:29:36 GMT):
@rameshthoomu we don't use cobertura in Fabric SDK Go.. this is probably a job script copy from Fabric? we have no control over this
rameshthoomu (Wed, 05 Sep 2018 20:30:30 GMT):
ok.. will remove this
Baha-sk (Wed, 05 Sep 2018 20:30:39 GMT):
ok
rameshthoomu (Wed, 05 Sep 2018 20:31:48 GMT):
@sambhavdutt could you please create a JIRA task to remove `**/report.xml` from sdk-go jobs
rameshthoomu (Wed, 05 Sep 2018 20:31:57 GMT):
assign this to Vijay
sambhavdutt (Wed, 05 Sep 2018 20:32:16 GMT):
@rameshthoomu yes, will do
Baha-sk (Wed, 05 Sep 2018 20:32:39 GMT):
@troyronda @aleksandar.likic ^^^^
gennadyl (Thu, 06 Sep 2018 08:44:47 GMT):
Any progress with FABCI-83?
dave.enyeart (Thu, 06 Sep 2018 16:23:24 GMT):
@jtclark @sambhavdutt FABCI-83 is a priority while @rameshthoomu is out, could it be done this week?
sambhavdutt (Thu, 06 Sep 2018 16:39:48 GMT):
@dave.enyeart Sure Dave, will check
jtclark (Thu, 06 Sep 2018 16:40:20 GMT):
@dave.enyeart yes, I'm working on this one RN
jtclark (Thu, 06 Sep 2018 16:40:40 GMT):
@sambhavdutt hey, can you stop by my desk? let's talk about this one
sambhavdutt (Thu, 06 Sep 2018 17:32:19 GMT):
Hi @jtclark
will be over there in a short while, checking on some changes in gerrit
jtclark (Thu, 06 Sep 2018 17:51:24 GMT):
@sambhavdutt sounds good.
dave.enyeart (Thu, 06 Sep 2018 18:19:46 GMT):
There have been many intermittent unit test failures in fabric CI the last couple days. Here’s an update on the two most common ones:
- TestCreds intermittent unit test failure being worked under: https://gerrit.hyperledger.org/r/#/c/26136/.
- TestGoodChannelCreateConfigUpdate unit test fix was merged today as https://gerrit.hyperledger.org/r/#/c/26144/, rebase on master to pick up that fix.
sambhavdutt (Thu, 06 Sep 2018 18:20:14 GMT):
yes, today especially
sambhavdutt (Thu, 06 Sep 2018 18:20:37 GMT):
the bug is ready, can I post it
sambhavdutt (Thu, 06 Sep 2018 18:21:09 GMT):
I held back when some of the unit-tests passed about a couple hours back
sambhavdutt (Thu, 06 Sep 2018 18:21:40 GMT):
@dave.enyeart thanks, got my answer
jtclark (Thu, 06 Sep 2018 18:21:42 GMT):
@dave.enyeart can you confirm which fabric jobs we are looking to pull the fabric-chaincode-java images for? I'm thinking we want to for the smoke, verify, merge, and merge-e2e tests
jtclark (Thu, 06 Sep 2018 18:22:16 GMT):
@gennadyl :point_up_tone2:
dave.enyeart (Thu, 06 Sep 2018 18:28:32 GMT):
and IntegrationTest
jtclark (Thu, 06 Sep 2018 18:29:47 GMT):
@dave.enyeart thanks
sambhavdutt (Thu, 06 Sep 2018 18:35:21 GMT):
Hello @jwagantall @tijohnson
Can you merge this change https://gerrit.hyperledger.org/r/#/c/26080/
sambhavdutt (Thu, 06 Sep 2018 19:18:12 GMT):
@tijohnson
Addressed all comments on https://gerrit.hyperledger.org/r/#/c/25837/
tijohnson (Thu, 06 Sep 2018 20:11:23 GMT):
@sambhavdutt please my latest comment before you merge
jtclark (Fri, 07 Sep 2018 00:29:08 GMT):
@dave.enyeart https://gerrit.hyperledger.org/r/#/c/26157/ <-- FABCI-83 change is in review.
sambhavdutt (Fri, 07 Sep 2018 15:45:40 GMT):
@jwagantall @tijohnson @dave.enyeart @jtclark
Jason and I just had a chat about https://gerrit.hyperledger.org/r/#/c/26157/ and https://gerrit.hyperledger.org/r/#/c/26080/
we agreed that https://gerrit.hyperledger.org/r/#/c/26080/ can be merged first, then make the changes in other accordingly, can I request to get https://gerrit.hyperledger.org/r/#/c/26080/ merged if you think it's ok
sambhavdutt (Fri, 07 Sep 2018 16:48:42 GMT):
@jwagantall @dave.enyeart @tijohnson @rameshthoomu
Can you look into this CR too, I hope I am not rushing you
https://gerrit.hyperledger.org/r/#/c/26169/
jwagantall (Fri, 07 Sep 2018 16:57:07 GMT):
no worries @sambhavdutt let me take a peek
jwagantall (Fri, 07 Sep 2018 16:57:18 GMT):
so https://gerrit.hyperledger.org/r/#/c/26080/ first.. right?
sambhavdutt (Fri, 07 Sep 2018 16:57:38 GMT):
@jwagantall yes & thank you
jtclark (Fri, 07 Sep 2018 16:58:15 GMT):
that patch is basically a prereq for the other
jtclark (Fri, 07 Sep 2018 16:58:39 GMT):
we're basically doing the same thing in both the patches mentioned above (pulling the java chaincode image)
jtclark (Fri, 07 Sep 2018 16:59:04 GMT):
so we need that one merged first, then I'll have to rebase and update my patchset
jtclark (Fri, 07 Sep 2018 16:59:17 GMT):
so that we're not pulling the image twice
jtclark (Fri, 07 Sep 2018 16:59:22 GMT):
@jwagantall :point_up_tone2:
jwagantall (Fri, 07 Sep 2018 17:00:07 GMT):
thnaks @jtclark .. ok.. on https://gerrit.hyperledger.org/r/#/c/26080/
jwagantall (Fri, 07 Sep 2018 17:08:03 GMT):
@jtclark @sambhavdutt whats the difference between "MARCH" and "ARCH" ?
jwagantall (Fri, 07 Sep 2018 17:08:14 GMT):
other than a missing "M" :joy_cat:
jtclark (Fri, 07 Sep 2018 17:09:21 GMT):
I don't think that there is a diff, is there @sambhavdutt ?
sambhavdutt (Fri, 07 Sep 2018 17:10:09 GMT):
@jwagantall yes, it is just that in this particular script the *MARCH* variable runs the `go env GOARCH` which would output the architecture as we know
jwagantall (Fri, 07 Sep 2018 17:10:29 GMT):
Can we use the same varaible across scripts?
jwagantall (Fri, 07 Sep 2018 17:10:36 GMT):
same name
sambhavdutt (Fri, 07 Sep 2018 17:11:19 GMT):
yes, let me change that
jwagantall (Fri, 07 Sep 2018 17:11:28 GMT):
thank you!
jwagantall (Fri, 07 Sep 2018 17:11:31 GMT):
is less confusing
sambhavdutt (Fri, 07 Sep 2018 17:11:42 GMT):
yes
jwagantall (Fri, 07 Sep 2018 17:12:56 GMT):
Also.. if you need to unset that variable between scripts you might need to add that.. If we want the same value between scripts, we should be good to go..
sambhavdutt (Fri, 07 Sep 2018 17:14:05 GMT):
@jwagantall yes, will checkon this
sambhavdutt (Fri, 07 Sep 2018 17:30:11 GMT):
@jwagantall I have updated the `ARCH` on the scripts in https://gerrit.hyperledger.org/r/#/c/26080/ , I checked that there are no followup scripts that would need the `MARCH`
jwagantall (Fri, 07 Sep 2018 17:34:36 GMT):
thnaks!
jwagantall (Fri, 07 Sep 2018 17:34:40 GMT):
let me re-review
jwagantall (Fri, 07 Sep 2018 17:35:59 GMT):
looks good to me approved!
jwagantall (Fri, 07 Sep 2018 17:36:03 GMT):
next https://gerrit.hyperledger.org/r/#/c/26157/ right?
jtclark (Fri, 07 Sep 2018 17:36:19 GMT):
@jwagantall yes, but now it needs to be updated
sambhavdutt (Fri, 07 Sep 2018 17:36:42 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=upTMGTqzuMiWRZaFv) @jwagantall thank you
jwagantall (Fri, 07 Sep 2018 17:36:43 GMT):
oh yes please.. the MARCH thingy
jtclark (Fri, 07 Sep 2018 17:40:32 GMT):
ok
sambhavdutt (Fri, 07 Sep 2018 17:46:34 GMT):
@jwagantall Can you look into this too when you are free https://gerrit.hyperledger.org/r/#/c/26169/
jwagantall (Fri, 07 Sep 2018 17:51:47 GMT):
sure
sambhavdutt (Fri, 07 Sep 2018 17:52:02 GMT):
thank you
jwagantall (Fri, 07 Sep 2018 17:52:22 GMT):
yes.. looks good to me
jwagantall (Fri, 07 Sep 2018 17:52:36 GMT):
let me know once the https://gerrit.hyperledger.org/r/#/c/26157/ is ready
sambhavdutt (Fri, 07 Sep 2018 17:53:08 GMT):
@jwagantall will do
jtclark (Fri, 07 Sep 2018 19:35:58 GMT):
@sambhavdutt question for you
jtclark (Fri, 07 Sep 2018 19:37:13 GMT):
with FABCI-84 that was just merged, you added the chaincode java image pull to the `fabric-unit-tests-verification` right?
jtclark (Fri, 07 Sep 2018 19:37:45 GMT):
that means that any of the fabric jobs that DON'T utilize this builder
jtclark (Fri, 07 Sep 2018 19:37:59 GMT):
still aren't pulling the chaincode java image, correct?
sambhavdutt (Fri, 07 Sep 2018 19:39:26 GMT):
@jtclark yes, and I have added this to the fabric-integration tests too, the javaenv image pull
jtclark (Fri, 07 Sep 2018 19:40:06 GMT):
ok so I just need to make sure that **my** patch set doesn't use the builder I created
jtclark (Fri, 07 Sep 2018 19:40:11 GMT):
later we can fix it
jtclark (Fri, 07 Sep 2018 19:41:16 GMT):
for example: fabric-merge does not use the `fabric-unit-tests-verification` builder
jtclark (Fri, 07 Sep 2018 19:41:33 GMT):
so I can safely add my `pull-nexus-chaincode-java-image` builder
jtclark (Fri, 07 Sep 2018 19:41:48 GMT):
and it won't pull the image twice
sambhavdutt (Fri, 07 Sep 2018 19:42:53 GMT):
yes
jtclark (Fri, 07 Sep 2018 19:43:24 GMT):
ok I think we're good. I just rebased my patch and from what I can see, we're not using both builders in the same fabric job.
jtclark (Fri, 07 Sep 2018 19:59:52 GMT):
@jwagantall I think that this change is ready
jtclark (Fri, 07 Sep 2018 20:00:28 GMT):
@sambhavdutt @jwagantall can you take a look plz? https://gerrit.hyperledger.org/r/#/c/26157/
sambhavdutt (Fri, 07 Sep 2018 20:01:05 GMT):
@jtclark will check
dave.enyeart (Sun, 09 Sep 2018 13:07:49 GMT):
@rameshthoomu @sambhavdutt @smithbk @skarim Any idea why CI is failing for fabric-ca? https://gerrit.hyperledger.org/r/#/c/26117/
rameshthoomu (Sun, 09 Sep 2018 13:44:03 GMT):
@dave.enyeart I am on mobile right now but checked the basic logs.. Seems we can ignore this result as s390x build is showing unstable
rameshthoomu (Sun, 09 Sep 2018 13:45:10 GMT):
unstable is because we are getting error in the post build action which is not related to the build
rameshthoomu (Sun, 09 Sep 2018 13:45:30 GMT):
@sambhavdutt could you pls verify this and confirm pls
sambhavdutt (Sun, 09 Sep 2018 14:55:55 GMT):
@dave.enyeart @rameshthoomu I will look into this now
sambhavdutt (Sun, 09 Sep 2018 15:31:25 GMT):
it's still unstable in fabric-ca for https://gerrit.hyperledger.org/r/#/c/26117/, does not look like a build error to me too
sambhavdutt (Mon, 10 Sep 2018 17:49:33 GMT):
Hello @jwagantall
Can you merge this if merge this CR https://gerrit.hyperledger.org/r/#/c/26194/
sambhavdutt (Mon, 10 Sep 2018 17:49:33 GMT):
Hello @jwagantall
Can you merge this CR https://gerrit.hyperledger.org/r/#/c/26194/
sambhavdutt (Tue, 11 Sep 2018 00:45:15 GMT):
Hello team
are we facing this error for sandbox
```
504 Gateway Time-out
```
jtclark (Tue, 11 Sep 2018 00:46:09 GMT):
@jwagantall @tijohnson :point_up_tone2:
rameshthoomu (Tue, 11 Sep 2018 07:13:02 GMT):
@jtclark @sambhavdutt Please create help desk ticket if quick action required.
rameshthoomu (Tue, 11 Sep 2018 07:29:07 GMT):
@harsha I am flying back to US.. In airport now..
rameshthoomu (Tue, 11 Sep 2018 07:29:22 GMT):
Any update on ppc e2e and unit-test..
rameshthoomu (Tue, 11 Sep 2018 07:29:36 GMT):
Seems both are working but would like to hear from you..
harsha (Tue, 11 Sep 2018 08:25:28 GMT):
@rameshthoomu ppc64le e2e are passing so is UT passing. with few transient failures which are seen on x86 as well.
jtclark (Tue, 11 Sep 2018 11:50:21 GMT):
@rameshthoomu looks like the sandbox is back online now.
latitiah (Tue, 11 Sep 2018 14:13:43 GMT):
@rameshthoomu @sambhavdutt: can someone please publish fabric 1.3 docker images for use with fabric-ca? Right now, they are using 1.2 images in the makefile.
latitiah (Tue, 11 Sep 2018 14:14:24 GMT):
I can change the makefile to use the correct version, but it still errors out because the 1.3 builds for fabric have not been published
sambhavdutt (Tue, 11 Sep 2018 14:15:39 GMT):
@latitiah
I will check on this
latitiah (Tue, 11 Sep 2018 14:16:09 GMT):
Thanks!
sambhavdutt (Tue, 11 Sep 2018 14:45:48 GMT):
@latitiah
I'm looking at one of the fabric-verify-end-2-end job,
```
03:48:27 hyperledger/fabric-ccenv amd64-1.3.0-snapshot-e188e53 6ae23c67d2c5 2 minutes ago 1.43GB
03:48:27 hyperledger/fabric-ccenv amd64-latest 6ae23c67d2c5 2 minutes ago 1.43GB
03:48:27 hyperledger/fabric-ccenv latest 6ae23c67d2c5 2 minutes ago 1.43GB
03:48:27 hyperledger/fabric-orderer amd64-1.3.0-snapshot-e188e53 d8a35fd6d49b 3 minutes ago 145MB
03:48:27 hyperledger/fabric-orderer amd64-latest d8a35fd6d49b 3 minutes ago 145MB
03:48:27 hyperledger/fabric-orderer latest d8a35fd6d49b 3 minutes ago 145MB
03:48:27 hyperledger/fabric-peer amd64-1.3.0-snapshot-e188e53 998e5491b97b 3 minutes ago 151MB
03:48:27 hyperledger/fabric-peer amd64-latest 998e5491b97b 3 minutes ago 151MB
03:48:27 hyperledger/fabric-peer latest 998e5491b97b 3 minutes ago 151MB
03:48:27 hyperledger/fabric-ca amd64-1.3.0-snapshot-a24cd9d e19aca007218 6 minutes ago 253MB
03:48:27 hyperledger/fabric-ca latest e19aca007218 6 minutes ago 253MB
```
the fabric and ca are using the 1.3.0, I had rebased one of Ramesh's change and pushed it for this, just wanted to make sure if we are pulling the right ones on the latest build.
Did I answer your question correctly..
latitiah (Tue, 11 Sep 2018 14:47:27 GMT):
no, the fabric-ca-peer and fabric-ca-orderer builds are using v1.2 fabric-peer/orderer builds. I've verified this already.
latitiah (Tue, 11 Sep 2018 14:48:33 GMT):
I am fixing the Makefile so that the builds for these images uses the correct base image, but one of the issues that I had was with pulling the correct published fabric-peer and fabric-orderer builds.
latitiah (Tue, 11 Sep 2018 14:48:48 GMT):
I've fixed this for local builds.
latitiah (Tue, 11 Sep 2018 14:49:38 GMT):
I'm not totally sure how CI is performing these builds - do you build fabric, then build fabric-ca?
latitiah (Tue, 11 Sep 2018 14:49:58 GMT):
Do you only build fabric-ca and pull the necessary images as needed?
latitiah (Tue, 11 Sep 2018 14:51:33 GMT):
I can spend more time to make sure that both scenarios work, but it's not necessary to do so, if you always build a set, prescribed way.
sambhavdutt (Tue, 11 Sep 2018 14:54:00 GMT):
in the `fabric-ca` now, we are building the images for ca and fabric,
latitiah (Tue, 11 Sep 2018 14:54:28 GMT):
(you can see my posts and conversations about this in #fabric-ca and #fabric-orderer from last night)
latitiah (Tue, 11 Sep 2018 14:55:34 GMT):
fabric-ca only builds ca images. It pulls fabric images.
latitiah (Tue, 11 Sep 2018 14:56:19 GMT):
https://pastebin.com/rq0Bnk52
latitiah (Tue, 11 Sep 2018 14:56:29 GMT):
You can look at the Steps in the pastebin above
latitiah (Tue, 11 Sep 2018 14:56:51 GMT):
You'll notice it's pulling v1.2 images for fabric-ca-peer and fabric-ca-orderer
sambhavdutt (Tue, 11 Sep 2018 14:58:03 GMT):
thanks I'll check,
sorry, yes, I mean we are cloning the fabric and `make docker` in the `ca` builds
I'll see if I can update this wit a CR
latitiah (Tue, 11 Sep 2018 14:59:17 GMT):
no worries. I already have a fix for the Makefile issue, but wanted to make sure that I didn't break anything that CI has in place.
latitiah (Tue, 11 Sep 2018 14:59:45 GMT):
I'll be sure to put you on the CR that I'm about to push now, then maybe you can test it in the sandbox
sambhavdutt (Tue, 11 Sep 2018 15:01:56 GMT):
yes, sure thing. I can test it in sandbox
latitiah (Tue, 11 Sep 2018 15:02:38 GMT):
https://gerrit.hyperledger.org/r/26226
scottz (Wed, 12 Sep 2018 00:03:04 GMT):
I pushed a CR into fabric-test 90 minutes ago, but it has not started yet. (There are actually two jobs pending.) Is there a problem with the hyperledger VMs? `(pending—There are no nodes with the label ‘hyp-x86_64’)` https://jenkins.hyperledger.org/view/fabric-test/job/fabric-test-verify-x86_64/
rameshthoomu (Wed, 12 Sep 2018 00:27:17 GMT):
@scottz yes x nodes went offline. Created help desk ticket Hyperledger Helpdesk #60791
scottz (Wed, 12 Sep 2018 01:08:24 GMT):
ok, thanks. by the way, welcome back to NC (just in time to maybe flee).
sambhavdutt (Wed, 12 Sep 2018 01:36:03 GMT):
all nodes are back online, jobs in queue and catching up
kirin (Wed, 12 Sep 2018 03:59:34 GMT):
Has joined the channel.
sykesm (Wed, 12 Sep 2018 13:52:05 GMT):
@rameshthoomu two CRs were merged to fabric-baseimage; when/how do the images get updated and pushed?
rameshthoomu (Wed, 12 Sep 2018 14:18:49 GMT):
@cbf or @dave.enyeart has to tag fabric-baseimage.. Once the repo is tagged with new baseimage version, jobs will trigger and push images to dockerhub
cbf (Wed, 12 Sep 2018 14:28:38 GMT):
@rameshthoomu ok will do shortly
cbf (Wed, 12 Sep 2018 14:29:00 GMT):
on a separate note, we aren't publishing the fabric-javaenv images to nexus (or dockerhub, for that matter)
cbf (Wed, 12 Sep 2018 14:29:12 GMT):
built in the CI for fabric-chaincode-java
cbf (Wed, 12 Sep 2018 14:30:06 GMT):
then we also need to update the pull_artifacts script and the various bootstrap
cbf (Wed, 12 Sep 2018 14:30:11 GMT):
for 1.3
rameshthoomu (Wed, 12 Sep 2018 14:31:05 GMT):
yes.. will update..
jtclark (Wed, 12 Sep 2018 14:31:33 GMT):
@rameshthoomu
jtclark (Wed, 12 Sep 2018 14:31:33 GMT):
@rameshthoomu we just got the new fabric-macro merged in that will pull the javaenv image (from nexus) in all associated fabric jobs
rameshthoomu (Wed, 12 Sep 2018 14:31:40 GMT):
every successful fabric-chaincode-java merge will publish javaenv image to nexus repo..
rameshthoomu (Wed, 12 Sep 2018 14:32:06 GMT):
Will update release job CI scripts to push javaenv image to dockerhub..
cbf (Wed, 12 Sep 2018 14:33:54 GMT):
ah, so then the sha is not the same as fabric
cbf (Wed, 12 Sep 2018 14:33:57 GMT):
interesting
rameshthoomu (Wed, 12 Sep 2018 14:34:49 GMT):
Pushing it to nexus with `amd64-latest` tag..
cbf (Wed, 12 Sep 2018 14:34:52 GMT):
how do we label the latest stable version?
cbf (Wed, 12 Sep 2018 14:34:57 GMT):
latests thanls
rameshthoomu (Wed, 12 Sep 2018 14:35:24 GMT):
in all the subsequent jobs we are using above tag to pull and re-tagging
cbf (Wed, 12 Sep 2018 14:35:40 GMT):
ok, the pull_artifacts.sh needs a section for that
rameshthoomu (Wed, 12 Sep 2018 14:36:38 GMT):
yes.. will update
jtclark (Wed, 12 Sep 2018 16:25:45 GMT):
@rameshthoomu https://gerrit.hyperledger.org/r/#/c/26254/ - plz review
rameshthoomu (Wed, 12 Sep 2018 16:31:50 GMT):
added comments..
harsha (Wed, 12 Sep 2018 18:35:34 GMT):
@rameshthoomu fabric-verify-unit-tests for x86_64 are failing constantly.. looks like it's failing at func `testInvokeOKPvtDataOnly` and would need addressing. Creating JIRA item.
harsha (Wed, 12 Sep 2018 18:44:12 GMT):
Created Jira Item FAB-11971 for above.
JaydipMakadia (Thu, 13 Sep 2018 12:50:51 GMT):
Has joined the channel.
bretharrison (Thu, 13 Sep 2018 13:00:41 GMT):
Could we get the NodeSDK release build kicked off again
https://jenkins.hyperledger.org/view/fabric-sdk-node/job/fabric-sdk-node-npm-release-x86_64/lastBuild/
rameshthoomu (Thu, 13 Sep 2018 13:46:34 GMT):
@bretharrison re-triggred
bretharrison (Thu, 13 Sep 2018 13:46:49 GMT):
thanks
rameshthoomu (Thu, 13 Sep 2018 13:57:28 GMT):
@bretharrison pubished 1.2.2 npm modules https://www.npmjs.com/package/fabric-client
bretharrison (Thu, 13 Sep 2018 14:00:46 GMT):
thanks
jtclark (Fri, 14 Sep 2018 13:38:37 GMT):
plz review: https://gerrit.hyperledger.org/r/#/c/26254/
rameshthoomu (Sat, 15 Sep 2018 14:28:26 GMT):
@jtclark could you please address these comments https://gerrit.hyperledger.org/r/#/c/26254/
flyerwing (Tue, 18 Sep 2018 05:48:28 GMT):
Has joined the channel.
jtclark (Tue, 18 Sep 2018 14:33:01 GMT):
https://gerrit.hyperledger.org/r/#/c/26254/ - plz review
izumix (Wed, 19 Sep 2018 08:36:41 GMT):
Has joined the channel.
rickr (Wed, 19 Sep 2018 17:07:23 GMT):
@rameshthoomu https://gerrit.hyperledger.org/r/#/c/26281/2..3 `reverify-x86` ?
rameshthoomu (Wed, 19 Sep 2018 17:11:52 GMT):
reverify-x
rameshthoomu (Wed, 19 Sep 2018 17:12:30 GMT):
just for reference https://ci-docs.readthedocs.io/en/latest/source/fabric_sdk_java_process.html
rickr (Wed, 19 Sep 2018 17:34:06 GMT):
A nice touch IMO across all project for every build would be a `reverify-failed` that would see what builds failed and retrigger :)
rickr (Wed, 19 Sep 2018 17:37:41 GMT):
@rameshthoomu https://gerrit.hyperledger.org/r/#/c/26281/
```
13:33:43 Error response from daemon: No such image: nexus3.hyperledger.org:10001/hyperledger/fabric-javaenv:amd64-latest
```
rameshthoomu (Wed, 19 Sep 2018 17:52:40 GMT):
checking
cbf (Wed, 19 Sep 2018 17:53:29 GMT):
@jtclark https://gerrit.hyperledger.org/r/c/26254/ has been merged, but I just realized it did not include the JIRA reference... no matter, but if you could let me know what the JIRA is I will close it
jtclark (Wed, 19 Sep 2018 18:08:24 GMT):
@cbf sure. We took this as a request from the maintainers meeting and worked on it w/o a JIRA task. I'll create one and mark it as complete.
cbf (Wed, 19 Sep 2018 18:08:40 GMT):
ok thanks
jtclark (Wed, 19 Sep 2018 18:12:44 GMT):
@cbf https://jira.hyperledger.org/browse/FAB-12057
tijohnson (Wed, 19 Sep 2018 20:46:39 GMT):
@all Jenkins Sandbox is down again
tijohnson (Wed, 19 Sep 2018 20:59:14 GMT):
@all Jenkins Sandbox is up
rgunn (Thu, 20 Sep 2018 03:58:26 GMT):
Has joined the channel.
tijohnson (Thu, 20 Sep 2018 21:25:25 GMT):
@all Jenkins sandbox is struggling IT is looking at it
dave.enyeart (Sun, 23 Sep 2018 19:11:20 GMT):
@sambhavdutt @rameshthoomu @rickr Can you look into the fabric merge job failures, e.g.: https://jenkins.hyperledger.org/job/fabric-merge-end-2-end-x86_64/3276/console
sambhavdutt (Sun, 23 Sep 2018 19:11:45 GMT):
@dave.enyeart Will check now
rameshthoomu (Sun, 23 Sep 2018 19:38:24 GMT):
@dave.enyeart seems these are consistent now. I see couple of tests are failed here. Maybe @rickr knows what's wrong with these tests.
rameshthoomu (Sun, 23 Sep 2018 19:46:53 GMT):
@dave.enyeart looking into it
rameshthoomu (Sun, 23 Sep 2018 22:16:46 GMT):
@dave.enyeart I see the latest change worked here https://jenkins.hyperledger.org/view/fabric/job/fabric-merge-end-2-end-x86_64/3282/console
rickr (Sun, 23 Sep 2018 22:37:33 GMT):
nothing wrong on that run with the JSDK ```
Tests run: 50, Failures: 0, Errors: 0, Skipped: 3, Time elapsed: 563.374 sec - in org.hyperledger.fabric.sdkintegration.IntegrationSuite
17:32:47
17:32:47 Results :
17:32:47
17:32:47 Tests run: 50, Failures: 0, Errors: 0, Skipped: 3
17:32:47
```
rameshthoomu (Sun, 23 Sep 2018 22:38:45 GMT):
yes.. seems the environment is not clean before running the sdk-java tests.. will work on this post 1.3 rc1
rickr (Tue, 25 Sep 2018 15:26:52 GMT):
@rameshthoomu Trying to see if merged change still is running >> https://gerrit.hyperledger.org/r/#/c/26507/
reverify remerge is not starting anything up :(
rameshthoomu (Tue, 25 Sep 2018 15:27:37 GMT):
@jtclark could you please check this
jtclark (Tue, 25 Sep 2018 15:27:50 GMT):
@rameshthoomu sure.
jtclark (Tue, 25 Sep 2018 15:44:48 GMT):
@rickr looks like the remerge comment worked this time
jtclark (Tue, 25 Sep 2018 15:45:04 GMT):
not sure why this glitch happens but seems like it triggered this time.
rickr (Tue, 25 Sep 2018 15:47:51 GMT):
Well have seen this now twice -- only when @rameshthoomu specifies it it seems to kick off
rameshthoomu (Tue, 25 Sep 2018 15:52:21 GMT):
:)
rickr (Tue, 25 Sep 2018 15:59:13 GMT):
Can you investigate ?
rameshthoomu (Tue, 25 Sep 2018 16:03:37 GMT):
Sure @rickr could you please create JIRA on FABCI project
rameshthoomu (Tue, 25 Sep 2018 16:03:46 GMT):
assign this to me
rickr (Tue, 25 Sep 2018 16:13:49 GMT):
FABCI-116
davidkel (Wed, 26 Sep 2018 10:20:14 GMT):
@rameshthoomu I'm trying to get a snapshot build of the release-1.1 fabric-chaincode-node published, but the merge job looks like it is failing with
```
[09:52:24] Finished 'test-e2e' after 356 μs
10:52:24 [fabric-chaincode-node-merge-x86_64] $ /bin/bash -eu /tmp/jenkins2867381484470751448.sh
10:52:25 /tmp/jenkins2867381484470751448.sh: line 68: cd: fabric-shim: No such file or directory
10:52:25 Build step 'Execute shell' marked build as failure
10:52:25 $ ssh-agent -k
```
Would appreciate some help on this if you can
rameshthoomu (Wed, 26 Sep 2018 12:17:59 GMT):
Looking into it
rameshthoomu (Wed, 26 Sep 2018 17:41:10 GMT):
@davidkel this has been fixed now..
rickr (Thu, 27 Sep 2018 14:21:37 GMT):
https://jenkins.hyperledger.org/job/fabric-sdk-java-verify-x86_64/2461/console ?
rameshthoomu (Thu, 27 Sep 2018 14:27:41 GMT):
@rickr please re-trigger this
```
00:01:37.979 package golang.org/x/crypto/ssh/terminal: unrecognized import path "golang.org/x/crypto/ssh/terminal" (parse https://golang.org/x/crypto/ssh/terminal?go-get=1: no go-import meta tags ())
00:01:43.644 make[1]: *** [gotool.counterfeiter] Error 1
00:01:43.645 gotools.mk:53: recipe for target 'gotool.counterfeiter' failed
```
rameshthoomu (Thu, 27 Sep 2018 14:28:21 GMT):
docker is unable to download the package. Could you please re-trigger
rickr (Thu, 27 Sep 2018 14:34:51 GMT):
I have it happened twic
rickr (Thu, 27 Sep 2018 14:34:51 GMT):
I have it happened twice
rickr (Thu, 27 Sep 2018 14:35:12 GMT):
Past that point now.
tijohnson (Thu, 27 Sep 2018 18:18:36 GMT):
@here System Downtime: All HYP system Oct 2 6-8 PM EST Another reminder will be sent out on Tuesday
rameshthoomu (Thu, 27 Sep 2018 18:49:31 GMT):
Thanks @tijohnson for the note
aso (Fri, 28 Sep 2018 13:32:08 GMT):
Has left the channel.
tijohnson (Fri, 28 Sep 2018 16:51:03 GMT):
@here Due to Sandbox going down again we are performing VM upgrade NOW
Only sandbox effected, the reset will be done next Tuesday
tijohnson (Fri, 28 Sep 2018 16:51:03 GMT):
@here Due to Sandbox going down again we are performing VM upgrade NOW
Only sandbox effected, the rest will be done next Tuesday
tijohnson (Fri, 28 Sep 2018 17:06:49 GMT):
@here Sandbox is back online
zacpl (Fri, 28 Sep 2018 18:36:35 GMT):
Has joined the channel.
rameshthoomu (Fri, 28 Sep 2018 20:22:46 GMT):
e2e_cli tests are failing in fabric master branch https://jira.hyperledger.org/browse/FAB-12229
rameshthoomu (Sat, 29 Sep 2018 22:43:27 GMT):
FAB-12236 - s390x unit-tests builds are failing
rameshthoomu (Sat, 29 Sep 2018 22:43:27 GMT):
FAB-12236 -"go test: -race and -msan" are only supported on "amd64" not on "s390x"
rameshthoomu (Mon, 01 Oct 2018 13:30:48 GMT):
FAB-12242 - fabric unit-tests are failing on master branch
dave.enyeart (Mon, 01 Oct 2018 13:34:14 GMT):
@sykesm ^^^^^^^^
dave.enyeart (Mon, 01 Oct 2018 13:34:30 GMT):
is this related to the updated race flag?
yacovm (Mon, 01 Oct 2018 13:36:33 GMT):
it is
yacovm (Mon, 01 Oct 2018 13:36:38 GMT):
race detector can't handle so much
yacovm (Mon, 01 Oct 2018 13:37:42 GMT):
https://gerrit.hyperledger.org/r/#/c/26692/
yacovm (Mon, 01 Oct 2018 13:37:42 GMT):
https://gerrit.hyperledger.org/r/#/c/26678/
yacovm (Mon, 01 Oct 2018 13:40:58 GMT):
@dave.enyeart ^
nekia (Tue, 02 Oct 2018 02:48:25 GMT):
Has joined the channel.
Bartb0 (Tue, 02 Oct 2018 10:51:07 GMT):
Has joined the channel.
nirro (Tue, 02 Oct 2018 11:49:28 GMT):
hello,
I have a CR where I removed old (legacy) tests and it looks like there is a CI issue.
can someone take a look please?
https://gerrit.hyperledger.org/r/#/c/26605/
nirro (Tue, 02 Oct 2018 11:56:58 GMT):
I'm seeing an error that the Jenkins cannot open the deleted files.. for example:
```
11:39:34 + for filename in '`echo $COMMIT_FILES`'
11:39:34 ++ file integration/pvtdata/e2e_suite_test.go
11:39:34 + [[ integration/pvtdata/e2e_suite_test.go: cannot open `integration/pvtdata/e2e_suite_test.go' (No such file or directory) == *\A\S\C\I\I\ \t\e\x\t* ]]
```
nirro (Tue, 02 Oct 2018 11:56:58 GMT):
I'm seeing an error that Jenkins cannot open the deleted files.. for example:
```
11:39:34 + for filename in '`echo $COMMIT_FILES`'
11:39:34 ++ file integration/pvtdata/e2e_suite_test.go
11:39:34 + [[ integration/pvtdata/e2e_suite_test.go: cannot open `integration/pvtdata/e2e_suite_test.go' (No such file or directory) == *\A\S\C\I\I\ \t\e\x\t* ]]
```
sambhavdutt (Tue, 02 Oct 2018 12:30:53 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=oauvxkfdpuK2JpvWJ) @nirro Like you said , the test is failing in *basic-checks* that performs basic checks like license, spelling and linter checks. Could they be because of a syntax or typo
nirro (Tue, 02 Oct 2018 12:32:13 GMT):
I have no idea.. I haven't changed anything except for removing one directory
jtclark (Tue, 02 Oct 2018 12:32:59 GMT):
@sambhavdutt perhaps we open a bug for this, and investigate?
sambhavdutt (Tue, 02 Oct 2018 12:35:16 GMT):
@jtclark yes if it is a consistent fail, will check if it happens again and we can decide to open one
jtclark (Tue, 02 Oct 2018 12:37:09 GMT):
@sambhavdutt looks like the `check-deps` step in the Makefile is failing
sambhavdutt (Tue, 02 Oct 2018 12:40:10 GMT):
@jtclark yes, one of the linter checks `make linter`
jtclark (Tue, 02 Oct 2018 12:43:27 GMT):
@sambhavdutt right. that make target calls check-deps
jtclark (Tue, 02 Oct 2018 12:44:06 GMT):
which basically just runs dep version and dep check
rameshthoomu (Tue, 02 Oct 2018 13:04:50 GMT):
@nirro ignore the above error you have posted. In CI, we have condition which checks for the trailing spaces on the files committed in the patchset. As these files are removed from the patchset it's says it can't find that files. The script continued further and executed dep-check and failed with the below error.
```
00:02:46.348 # Gopkg.lock is out of sync:
00:02:46.348 github.com/alecthomas/template: in Gopkg.lock's input-imports, but neither imported nor required
00:02:46.809
00:02:46.810 github.com/grpc-ecosystem/go-grpc-middleware: hash of vendored tree not equal to digest in Gopkg.lock (CHECK IGNORED: marked noverify in Gopkg.toml)
00:02:47.177 Makefile:218: recipe for target 'check-deps' failed
```
jtclark (Tue, 02 Oct 2018 13:06:34 GMT):
@nirro yes, this is the actual error, not the "cannot find file" error
jtclark (Tue, 02 Oct 2018 13:06:34 GMT):
@nirro yes, this is the actual error, not the "cannot find file" msg
nirro (Tue, 02 Oct 2018 13:16:01 GMT):
how can I understand what's going on using make linter command?
I can't understand from this error what is the problem..
nirro (Tue, 02 Oct 2018 13:16:30 GMT):
I just tried running make before deleting those files and it works, and after deleting the files I'm getting this error
rameshthoomu (Tue, 02 Oct 2018 13:21:23 GMT):
ok. got the same error while running `make check-deps` in my local machine..
tijohnson (Tue, 02 Oct 2018 15:10:56 GMT):
@here System Downtime: All HYP systems Today 6-8 PM EST
I will freeze job scheduling on Jenkins servers 30min before
rameshthoomu (Tue, 02 Oct 2018 18:12:00 GMT):
@sambhavdutt thanks for keeping all the CI failures with label `ci_failure`. Could you please update this with the latest status https://jira.hyperledger.org/issues/?filter=12103
rameshthoomu (Tue, 02 Oct 2018 18:12:34 GMT):
I see there are 21 issues in open status.. Could you please update the JIRA with proper comments and take action
sambhavdutt (Tue, 02 Oct 2018 18:14:03 GMT):
@rameshthoomu will do
sambhavdutt (Tue, 02 Oct 2018 18:14:03 GMT):
@rameshthoomu sure, will do
sambhavdutt (Tue, 02 Oct 2018 19:53:26 GMT):
@rameshthoomu I have modified the JIRA items according to the current status.
rameshthoomu (Tue, 02 Oct 2018 20:25:44 GMT):
@troyronda Could you please verify the merge job failures. This seems consistent now. Is there any known issue you logged in JIRA?
tijohnson (Tue, 02 Oct 2018 21:12:35 GMT):
@here System Downtime: All HYP system Oct 2 6-8 PM EST starting shutdown of Jenkins Servers @ 5:30
tijohnson (Wed, 03 Oct 2018 00:00:00 GMT):
@here All Hyp system are back on-line
sambhavdutt (Wed, 03 Oct 2018 00:39:20 GMT):
FAB-12272
sambhavdutt (Wed, 03 Oct 2018 00:43:51 GMT):
This issue is related to CouchDB Custom Channel BYFN tests that are failing because of Timeout. The default timeout was increased from 3 seconds to 15 seconds, but this issue is still intermittent. What I want to ask is, the same test runs well on the local systems, with even the 3 second Delay but does not when it runs on the x or z nodes even when the time is increased to 15 seconds.
sambhavdutt (Wed, 03 Oct 2018 00:44:26 GMT):
Does it have to do with the Jenkins worker nodes that run these tests
sambhavdutt (Wed, 03 Oct 2018 00:45:53 GMT):
@tijohnson @jwagantall ^^
jwagantall (Wed, 03 Oct 2018 00:58:44 GMT):
@sambhavdutt can you point us to an example.. i am not sure..
sambhavdutt (Wed, 03 Oct 2018 01:19:32 GMT):
@jwagantall
https://jenkins.hyperledger.org/view/Daily/job/fabric-nightly-release-job-release-1.3-x86_64/9/consoleFull
```
22:23:15 ======Channel 'custom-channel-couchdb' created =====================
22:23:15
22:23:15 Having all peers join the channel...
22:23:15 + peer channel join -b custom-channel-couchdb.block
22:23:18 + res=1
22:23:18 + set +x
22:23:18 Error: error getting endorser client for channel: endorser client failed to connect to peer0.org1.example.com:7051: failed to create new connection: context deadline exceeded
22:23:18 peer0.org1 failed to join the channel, Retry after 15 seconds
.
.
.
22:24:12 Error: error getting endorser client for channel: endorser client failed to connect to peer0.org1.example.com:7051: failed to create new connection: context deadline exceeded
22:24:12 peer0.org1 failed to join the channel, Retry after 15 seconds
22:24:27 + peer channel join -b custom-channel-couchdb.block
22:24:30 + res=1
22:24:30 + set +x
22:24:30 Error: error getting endorser client for channel: endorser client failed to connect to peer0.org1.example.com:7051: failed to create new connection: context deadline exceeded
22:24:30 !!!!!!!!!!!!!!! After 5 attempts, peer0.org1 has failed to join channel 'custom-channel-couchdb' !!!!!!!!!!!!!!!!
22:24:30 ========= ERROR !!! FAILED to execute End-2-End Scenario ===========
22:24:30
22:24:30 ERROR !!!! Test failed
```
sambhavdutt (Wed, 03 Oct 2018 01:20:25 GMT):
This test runs fine on local system, with the same script and lesser wait/delay time
jwagantall (Wed, 03 Oct 2018 01:20:52 GMT):
i have never seen that before.. let me re-run
sambhavdutt (Wed, 03 Oct 2018 01:21:10 GMT):
@jwagantall thank you
jwagantall (Wed, 03 Oct 2018 01:21:15 GMT):
my pleasure..
rameshthoomu (Wed, 03 Oct 2018 01:36:44 GMT):
@sambhavdutt can you please get the peer0.org1.example.com container logs
rameshthoomu (Wed, 03 Oct 2018 01:39:07 GMT):
@sambhavdutt see the couch log here https://logs.hyperledger.org/production/vex-yul-hyp-jenkins-3/fabric-nightly-release-job-release-1.3-x86_64/9/Docker_Container_Logs/peer0.org1-custom-channel-couch.log.gz
rameshthoomu (Wed, 03 Oct 2018 01:39:46 GMT):
handleRequest -> WARN 04d[0m Retrying couchdb request in 125ms. Attempt:1 Error:Get http://couchdb0:5984/: dial tcp 172.19.0.6:5984: connect: connection refused
rameshthoomu (Wed, 03 Oct 2018 01:40:25 GMT):
@AdnanC could you please give us some inputs on the above error
dave.enyeart (Wed, 03 Oct 2018 01:42:01 GMT):
it means couchdb was not available when the peer tried to connect, all retries were exhausted
dave.enyeart (Wed, 03 Oct 2018 01:42:38 GMT):
do you have the log from the couchdb container? would be interesting to compare timestamps with the associated peer log
dave.enyeart (Wed, 03 Oct 2018 01:43:15 GMT):
are the CI machines resource constrained relative to local hardware?
dave.enyeart (Wed, 03 Oct 2018 01:44:08 GMT):
@chris.elder has been looking into relative slow couchdb start time ever since the new baseimage was created
dave.enyeart (Wed, 03 Oct 2018 01:44:27 GMT):
we have seen it be a couple seconds slower than prior baseimage
dave.enyeart (Wed, 03 Oct 2018 01:45:03 GMT):
but i can't explain why it would be 30 seconds or more slower, unless the environments are very resource constrained
rameshthoomu (Wed, 03 Oct 2018 01:45:30 GMT):
yes I too observed the same error while testing new baseimage but this got fixed after we increase the timeout
rameshthoomu (Wed, 03 Oct 2018 01:45:39 GMT):
@dave.enyeart see the couch logs here https://logs.hyperledger.org/production/vex-yul-hyp-jenkins-3/fabric-nightly-release-job-release-1.3-x86_64/9/Docker_Container_Logs/
dave.enyeart (Wed, 03 Oct 2018 01:48:26 GMT):
in this example, the last peer retry was at 02:24:12.777 , while couchdb0 container first log message was at 02:24:14.483
dave.enyeart (Wed, 03 Oct 2018 01:48:59 GMT):
so it missed by a few seconds
dave.enyeart (Wed, 03 Oct 2018 01:49:22 GMT):
why it is taking so long to spin up the couchdb0 container, i do not know...
rameshthoomu (Wed, 03 Oct 2018 01:51:49 GMT):
We had these issues intermittently with build nodes but in this case it seems consistent with the latest changes in couchdb..
dave.enyeart (Wed, 03 Oct 2018 01:51:59 GMT):
until we figure this out, CORE_LEDGER_STATE_COUCHDBCONFIG_MAXRETRIESONSTARTUP could be increased from default of 10 to 20
dave.enyeart (Wed, 03 Oct 2018 01:51:59 GMT):
until we figure this out, peer's CORE_LEDGER_STATE_COUCHDBCONFIG_MAXRETRIESONSTARTUP could be increased from default of 10 to 20
dave.enyeart (Wed, 03 Oct 2018 01:52:42 GMT):
each retry will wait 2x as long as the prior retry
rameshthoomu (Wed, 03 Oct 2018 01:52:46 GMT):
may be increasing few more secs may fix this issue but we need to look into these issues more closely..
rameshthoomu (Wed, 03 Oct 2018 01:53:19 GMT):
@tijohnson @jwagantall ^^ we need your help in accessing one x build and try this test case manually
sambhavdutt (Wed, 03 Oct 2018 01:57:17 GMT):
Thank you all for your inputs on this
dave.enyeart (Wed, 03 Oct 2018 02:00:37 GMT):
also MAX_RETRY can be increased from 5 in https://github.com/hyperledger/fabric-samples/blob/master/first-network/scripts/script.sh#L24
dave.enyeart (Wed, 03 Oct 2018 02:01:12 GMT):
that would probably be better than further increasing the 15 second delay
dave.enyeart (Wed, 03 Oct 2018 02:03:26 GMT):
increase to maybe 15, for about 225 seconds (15x15) of retries rather than current 75 (5x15) seconds of retries
sambhavdutt (Wed, 03 Oct 2018 02:04:14 GMT):
@dave.enyeart thank you, I will submit a CR to increase this
rameshthoomu (Wed, 03 Oct 2018 02:04:34 GMT):
https://gerrit.hyperledger.org/r/#/c/26733/ -- Just for testing
rameshthoomu (Wed, 03 Oct 2018 02:07:00 GMT):
in fabric-samples, the same test is taking 4 retries..
dave.enyeart (Wed, 03 Oct 2018 02:30:58 GMT):
I am changing maxRetriesOnStartup, so that you don't have to override it: https://gerrit.hyperledger.org/r/#/c/26735/
dave.enyeart (Wed, 03 Oct 2018 02:33:04 GMT):
that will take it from 2minutes to 8minutes of total retries... i don't like it... but better than failing a CI job
rameshthoomu (Wed, 03 Oct 2018 02:35:18 GMT):
@dave.enyeart please submit the same change in release-1.3
rameshthoomu (Wed, 03 Oct 2018 02:35:36 GMT):
Do you want me to abandon my change https://gerrit.hyperledger.org/r/#/c/26734/
dave.enyeart (Wed, 03 Oct 2018 02:43:28 GMT):
we need both
dave.enyeart (Wed, 03 Oct 2018 02:43:54 GMT):
mine will keep peer alive longer, yours will keep byfn alive longer :)
rameshthoomu (Wed, 03 Oct 2018 02:44:18 GMT):
:)
dave.enyeart (Wed, 03 Oct 2018 02:44:53 GMT):
I'd advise move MAX_RETRY higher than 7
rameshthoomu (Wed, 03 Oct 2018 02:45:15 GMT):
how much you suggest? 15 ?
dave.enyeart (Wed, 03 Oct 2018 02:45:42 GMT):
for now yes... it's a painful delay, but better than CI failure until we figure this out
dave.enyeart (Wed, 03 Oct 2018 02:46:30 GMT):
I cherry picked mine to release-1.3 as well: https://gerrit.hyperledger.org/r/#/c/26737/
rameshthoomu (Wed, 03 Oct 2018 02:47:00 GMT):
I don't think this will take more than 5 re-tries..
dave.enyeart (Wed, 03 Oct 2018 02:47:36 GMT):
it's failing at current 5 MAX_RETRIES sometimes right
dave.enyeart (Wed, 03 Oct 2018 02:47:36 GMT):
it's failing at current 5 MAX_RETRY sometimes right
rameshthoomu (Wed, 03 Oct 2018 02:48:02 GMT):
correct..
dave.enyeart (Wed, 03 Oct 2018 02:48:19 GMT):
how about 10 then
rameshthoomu (Wed, 03 Oct 2018 02:48:52 GMT):
I think that's; better.. Will run few times with that number in sandbox
dave.enyeart (Wed, 03 Oct 2018 02:49:03 GMT):
ok, want me to +2 it?
rameshthoomu (Wed, 03 Oct 2018 02:49:51 GMT):
Will update to 10
rickr (Wed, 03 Oct 2018 15:44:28 GMT):
https://jira.hyperledger.org/browse/FABJ-373
rickr (Wed, 03 Oct 2018 15:44:49 GMT):
There's been no change in the JSDK
rickr (Wed, 03 Oct 2018 15:47:08 GMT):
So I just closed it -- please reopen for JavaCC if that for Fabric if they changed
rameshthoomu (Wed, 03 Oct 2018 15:48:11 GMT):
Updating the JIRA with the comments
rameshthoomu (Wed, 03 Oct 2018 15:56:03 GMT):
Moved this to https://jira.hyperledger.org/browse/FAB-12289
rameshthoomu (Wed, 03 Oct 2018 15:56:07 GMT):
and reopend
rickr (Wed, 03 Oct 2018 16:05:15 GMT):
https://jira.hyperledger.org/browse/FABCI-116
rickr (Wed, 03 Oct 2018 16:05:24 GMT):
any progress ?
rickr (Wed, 03 Oct 2018 16:05:45 GMT):
Just tried that again and nothing seems to kick off.
rameshthoomu (Wed, 03 Oct 2018 16:07:00 GMT):
Will check.. Could you please assign this to me
rickr (Wed, 03 Oct 2018 16:08:16 GMT):
ok done to many Ramesh here :)
rickr (Wed, 03 Oct 2018 16:08:16 GMT):
ok done too many Ramesh here :)
rameshthoomu (Wed, 03 Oct 2018 16:24:42 GMT):
:)
dave.enyeart (Wed, 03 Oct 2018 16:30:22 GMT):
@rameshthoomu @jwagantall can this one be merged today to unblock the docs : https://gerrit.hyperledger.org/r/#/c/26720/ (FYI @mbwhite )
rameshthoomu (Wed, 03 Oct 2018 16:30:55 GMT):
yes.. posted the same in #ci-pipeline
scottz (Wed, 03 Oct 2018 21:50:40 GMT):
I could use some help to understand why our weekly test suite, which passed a 12hour test on Oct 1 and created a console log and an xml file, shows no results when I click on "Test Results Analyzer" link. https://jenkins.hyperledger.org/view/fabric-test/job/fabric-test-svt-weekly-pte-x86_64/
scottz (Wed, 03 Oct 2018 21:51:41 GMT):
Does the jenkins job look for the xml file in the fabric-test/regression/weekly/ folder as it should?
scottz (Thu, 04 Oct 2018 00:21:08 GMT):
@sambhavdutt @latitiah The CI Daily behave tests must be failing every day in orderer.feature file because
there is NO peer or orderer rows with any xml file results in the display at
https://jenkins.hyperledger.org/view/fabric-test/job/fabric-test-daily-behave-master-x86_64/test_results_analyzer/
For example, see this job:
https://jenkins.hyperledger.org/view/fabric-test/job/fabric-test-daily-behave-master-x86_64/41/consoleFull
IS there a bug open for this failure? I don't see one. If not, we need one and need to fix this pronto!
orderer.feature FAB3852 1.3 : solo, nodejs sdk
When an admin instantiates the chaincode on "peer0.org1.example.com"
Assertion Failed: The expected chaincode container 6d75a2a2c55011e8965dfa163e3c24df-peer0.org1.example.com-mycc-0 is not running
OError: [Errno 11] Resource temporarily unavailable
And this one
https://jenkins.hyperledger.org/view/fabric-test/job/fabric-test-daily-behave-master-x86_64/42/console
fails at
orderer.feature FAB3851 1.1 : solo, nodejs sdk
sambhavdutt (Thu, 04 Oct 2018 00:43:51 GMT):
@scottz FAB-12040 is the open bug for Behave tests, and some comment on FABCI-144
I will create one for orderer.feature FAB3852 1.3 : solo, nodejs sdk
sambhavdutt (Thu, 04 Oct 2018 00:49:35 GMT):
@latitiah just checked the test on Sandbox that was triggered after the latest patch was merged ,
https://jenkins.hyperledger.org/sandbox/job/fabric-test-daily-behave-master-x86_64/1/consoleFull
failed because of a Jenkins error,
```
hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on snd-ubuntu1604-x86_64-4c-16g-16 failed. The channel is closing down or has closed down
```
sambhavdutt (Thu, 04 Oct 2018 00:52:42 GMT):
should wait for the nightly build to kick off the Behave tests for an accurate result
rameshthoomu (Thu, 04 Oct 2018 01:09:53 GMT):
@mbwhite https://fabric-shim.github.io/master/
latitiah (Thu, 04 Oct 2018 01:23:57 GMT):
Yes, also the test above mentioned by @scottz failed due to resource issues (again) ```04:08:19 IOError: [Errno 11] Resource temporarily unavailable
``` It should be noted, I'm 99% sure there are containers that are still running with those jobs after the first failure (as we've discussed before) so I can see there being possible resource issues.
mbwhite (Thu, 04 Oct 2018 07:51:47 GMT):
@rameshthoomu excellent - many thanks!
swetha (Fri, 05 Oct 2018 17:38:14 GMT):
Hi! Working on some integration tests for `fabric-chaincode-evm` and was wondering does the travis job have node installed on it or do we have to do something to enable that?
rameshthoomu (Fri, 05 Oct 2018 17:45:20 GMT):
Hi @swetha is that travis or Jenkins?
jtclark (Fri, 05 Oct 2018 17:45:36 GMT):
Jenkins I think
swetha (Fri, 05 Oct 2018 17:45:40 GMT):
Sorry I meant jenkins
jtclark (Fri, 05 Oct 2018 17:46:05 GMT):
Hi @swetha! :wave:
swetha (Fri, 05 Oct 2018 17:46:17 GMT):
hi jason!
swetha (Fri, 05 Oct 2018 17:46:31 GMT):
:wave:
jtclark (Fri, 05 Oct 2018 17:49:50 GMT):
@rameshthoomu I'm looking at the `fabric-chaincode-evm` jobs....verify and merge... I don't see in the configuration where node is installed, does this mean that the baseimage has node included?
jtclark (Fri, 05 Oct 2018 17:52:13 GMT):
@swetha I'm confirm my question above with Ramesh, but if you let us know what your integration tests need, we can make sure that the job launches nodes with any prerequisite tools
jtclark (Fri, 05 Oct 2018 17:52:13 GMT):
@swetha I'll confirm my question above with Ramesh, but if you let us know what your integration tests need, we can make sure that the job launches nodes with any prerequisite tools
swetha (Fri, 05 Oct 2018 17:53:01 GMT):
@jtclark Thanks! Currently just need to add node. I am planning on packaging the node_modules required with the tests so that should be covered
rameshthoomu (Fri, 05 Oct 2018 17:53:30 GMT):
@swetha As we have multiple versions of node dealing in different repo's.. We use nvm to install node on the vm for every build.
rameshthoomu (Fri, 05 Oct 2018 17:53:50 GMT):
if you use containers to do your tests, then the node is installed in baseimage.
swetha (Fri, 05 Oct 2018 17:54:44 GMT):
I don't think we are using containers, but if nvm is there I can use that to install node and packages I need
rameshthoomu (Fri, 05 Oct 2018 17:55:03 GMT):
https://github.com/hyperledger/ci-management/blob/master/jjb/fabric/shell/npm-install.sh
rameshthoomu (Fri, 05 Oct 2018 17:56:13 GMT):
I have to rush to meeting now.. Please create task in FABCI to include this
swetha (Fri, 05 Oct 2018 17:56:24 GMT):
Okay thanks! Will do
swetha (Fri, 05 Oct 2018 17:59:52 GMT):
@jtclark Does this line imply node is installed? https://github.com/hyperledger/fabric-chaincode-evm/blob/master/Jenkinsfile#L10
jtclark (Fri, 05 Oct 2018 18:00:59 GMT):
ah.... didn't realize that this was a Pipeline Jenkins job....
swetha (Fri, 05 Oct 2018 18:02:04 GMT):
does that mean we need to do something else?
jtclark (Fri, 05 Oct 2018 18:02:25 GMT):
we're adding the path that's for sure, but I'd have to look into whether or not node is installed. I think what Ramesh said is true- since we use containers for most of our jobs, we have a baseimage for those containers that includes node.
jtclark (Fri, 05 Oct 2018 18:02:41 GMT):
no using Pipeline is ok, we're switching to it.
swetha (Fri, 05 Oct 2018 18:03:01 GMT):
okay, how do I see if we are using containers?
jtclark (Fri, 05 Oct 2018 18:04:09 GMT):
https://jenkins.hyperledger.org/view/fabric-chaincode-evm/job/fabric-chaincode-evm-merge-master-x86_64/configure
jtclark (Fri, 05 Oct 2018 18:04:31 GMT):
this is the merge job for fabric-chaincode-evm. I'm going to dig through this to see if I can answer your question :-)
swetha (Fri, 05 Oct 2018 18:04:55 GMT):
Thanks so much! Please let me know what I can do to help in this process
jtclark (Fri, 05 Oct 2018 18:05:16 GMT):
Indeed. Adding the FABCI JIRA task would help.
swetha (Fri, 05 Oct 2018 18:05:26 GMT):
Writing it up as we speak.
swetha (Fri, 05 Oct 2018 18:07:36 GMT):
Created this JIRA: https://jira.hyperledger.org/browse/FAB-12326
rameshthoomu (Fri, 05 Oct 2018 20:36:27 GMT):
@jtclark are you working on fAB-12326?
jtclark (Fri, 05 Oct 2018 20:36:42 GMT):
I will assign it to myself, yes.
jtclark (Fri, 05 Oct 2018 20:36:53 GMT):
done
rameshthoomu (Fri, 05 Oct 2018 20:37:20 GMT):
Are you done with release test suite?
jtclark (Fri, 05 Oct 2018 20:37:46 GMT):
trying to get it running on the sandbox
rameshthoomu (Fri, 05 Oct 2018 20:37:58 GMT):
that's the highest priority for now for you..
jtclark (Fri, 05 Oct 2018 20:37:59 GMT):
I won't work on this until I'm done with that
rameshthoomu (Fri, 05 Oct 2018 20:38:35 GMT):
FAB-12326 should not take 5-10 mins..
rameshthoomu (Fri, 05 Oct 2018 20:38:54 GMT):
We have script available in ci.. just copy and paste in evm repository.
rameshthoomu (Fri, 05 Oct 2018 20:39:09 GMT):
anyway, I will work on this..
rameshthoomu (Fri, 05 Oct 2018 20:39:18 GMT):
continue work on release test suite
jtclark (Fri, 05 Oct 2018 20:39:21 GMT):
o
jtclark (Fri, 05 Oct 2018 20:39:21 GMT):
ok
rameshthoomu (Sat, 06 Oct 2018 12:52:14 GMT):
@swetha I have added a function to install nodejs in ci script.. and added before run the integration test.. https://gerrit.hyperledger.org/r/#/c/26827/
rameshthoomu (Sat, 06 Oct 2018 12:52:39 GMT):
please review and let me know if that is correct.
swetha (Sat, 06 Oct 2018 18:21:29 GMT):
@rameshthoomu it looks good. thanks! i will get others to review and merge the change in
rameshthoomu (Mon, 08 Oct 2018 02:39:38 GMT):
@nkl199 Added comment in https://jira.hyperledger.org/browse/FABN-953
rameshthoomu (Mon, 08 Oct 2018 02:40:12 GMT):
could you please check and let me know what javaenv tag you are expecting.
rameshthoomu (Mon, 08 Oct 2018 02:40:50 GMT):
@dthom Could you please check this https://jira.hyperledger.org/browse/FAB-1794
dthom (Mon, 08 Oct 2018 02:40:51 GMT):
Has joined the channel.
nkl199 (Mon, 08 Oct 2018 12:40:42 GMT):
@rameshthoomu the java chaincode tests are now passing, i suspect that the node build was looking for a tagged npm modulet that didn't exist yet. The failures (looking at the last set of available logs) are now failing at the "fabric network" tests. There was a decision made to prevent the publishing of `fabric-network`, which leads me to believe that we are witnessing the same type of "module not found" error here. Is there any way i can view the peer logs on the fabric-sdk-node merge builds to verify this suspicion?
dthom (Mon, 08 Oct 2018 13:04:53 GMT):
@rameshthoomu yes, I'm working on recreating the issue
rameshthoomu (Mon, 08 Oct 2018 13:06:59 GMT):
@dthom thanks
rameshthoomu (Mon, 08 Oct 2018 13:07:57 GMT):
@nkl199 I will run this in sandbox and provide you the logs..
rameshthoomu (Mon, 08 Oct 2018 18:59:58 GMT):
@bretharrison shall I close this https://jira.hyperledger.org/browse/FABCI-138?
bretharrison (Mon, 08 Oct 2018 19:04:13 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=6RqotQYq85mFFgqTu) @rameshthoomu Once we work out how the first unstable gets out there
rameshthoomu (Mon, 08 Oct 2018 19:04:28 GMT):
ok
bretharrison (Mon, 08 Oct 2018 19:04:35 GMT):
Shall I come out ?
bretharrison (Mon, 08 Oct 2018 19:05:20 GMT):
OK, maybe tomorrow
rameshthoomu (Mon, 08 Oct 2018 19:07:04 GMT):
this should go first before trigger any chaincode-node merge job from master branch https://gerrit.hyperledger.org/r/#/c/26773/
sambhavdutt (Mon, 08 Oct 2018 20:47:27 GMT):
Can you check this one when free, not done yet, have to add the baseimage condition to change `-snapshot` to 0.4.13
https://gerrit.hyperledger.org/r/#/c/26861/
rameshthoomu (Mon, 08 Oct 2018 21:01:56 GMT):
yes. please add that and let me know once done.. I have added a comment
rameshthoomu (Mon, 08 Oct 2018 21:02:12 GMT):
please address them and verify this in sandbox on s390x platform
rameshthoomu (Mon, 08 Oct 2018 21:02:55 GMT):
@jwagantall Could you please add `gopath/src/github.com/hyperledger/$PROJECT` to BASE_DIR
rameshthoomu (Mon, 08 Oct 2018 21:03:06 GMT):
like $GIT_BASE
jwagantall (Mon, 08 Oct 2018 21:14:42 GMT):
@tijohnson Can you please help on this request please? I can review your change once you have it ready
rameshthoomu (Mon, 08 Oct 2018 21:34:37 GMT):
@tijohnson could you please verify this error https://jenkins.hyperledger.org/job/ci-management-jjb-verify/1811/console
tijohnson (Mon, 08 Oct 2018 22:23:54 GMT):
I expect the add the path to BASE_DIR will solve that problem, sending change out for review in about a minute
tijohnson (Mon, 08 Oct 2018 22:54:00 GMT):
@ramesh change is out for review: https://gerrit.hyperledger.org/r/26862
rameshthoomu (Mon, 08 Oct 2018 22:55:57 GMT):
Thank you.. will look into this
NageshCR (Tue, 09 Oct 2018 02:44:09 GMT):
Has joined the channel.
chandrakanthMamillapalli (Wed, 10 Oct 2018 00:09:17 GMT):
Has joined the channel.
14gracel (Wed, 10 Oct 2018 15:12:52 GMT):
Has joined the channel.
sambhavdutt (Thu, 11 Oct 2018 18:13:51 GMT):
The gotools are failing to build in fabric, this is affecting all the fabric related jobs.
https://jira.hyperledger.org/browse/FAB-12423
dave.enyeart (Thu, 11 Oct 2018 18:34:02 GMT):
@sambhavdutt Matt has provided a fix in https://gerrit.hyperledger.org/r/#/c/26937/
dave.enyeart (Thu, 11 Oct 2018 18:34:41 GMT):
Do you have rebase privilege on other people's CRs? I believe all failing CRs will need to be rebased after https://gerrit.hyperledger.org/r/#/c/26937/ is merged
sambhavdutt (Thu, 11 Oct 2018 18:38:41 GMT):
@dave.enyeart I don't have the rebase access, I will check with @rameshthoomu who has the rebase privilege for ci jobs
dave.enyeart (Thu, 11 Oct 2018 18:42:59 GMT):
@sambhavdutt ok, probably better if you just add a comment to each failing CR suggesting that clicking 'Rebase' will resolve the problem, after https://gerrit.hyperledger.org/r/#/c/26937/ is merged of course
sambhavdutt (Thu, 11 Oct 2018 18:43:45 GMT):
@dave.enyeart sure thing, will do that
sambhavdutt (Thu, 11 Oct 2018 18:44:06 GMT):
and thank you
rickr (Thu, 11 Oct 2018 23:25:01 GMT):
@rameshthoomu Java SDK verify-1.0.0 is having issues tried 3 times `reverify-1.0.0`.
```
19:15:11 ++ docker ps -a
19:15:11 CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
19:15:11 ++ export ORG_HYPERLEDGER_FABRIC_SDK_DIAGNOSTICFILEDIR=target/diagDump
```
rickr (Thu, 11 Oct 2018 23:25:21 GMT):
not showing any Fabric/ca continers starting
rameshthoomu (Thu, 11 Oct 2018 23:25:32 GMT):
@jtclark could you pls check this
rickr (Thu, 11 Oct 2018 23:28:41 GMT):
doesn't look like the 1.0.0 images are being pulled
```
19:15:11 ++ docker images
19:15:11 REPOSITORY TAG IMAGE ID CREATED SIZE
19:15:11 hyperledger/fabric-zookeeper amd64-0.4.12 bca71b814159 3 weeks ago 1.39GB
19:15:11 hyperledger/fabric-kafka amd64-0.4.12 58b901c762ea 3 weeks ago 1.4GB
19:15:11 hyperledger/fabric-couchdb amd64-0.4.12 fe8d64d1233c 3 weeks ago 1.45GB
19:15:11 hyperledger/fabric-baseimage amd64-0.4.12 30004c8e8e06 3 weeks ago 1.34GB
19:15:11 hyperledger/fabric-baseos amd64-0.4.12 e0cee7b03d39 3 weeks ago 124MB
19:15:11 hyperledger/fabric-zookeeper amd64-0.4.10 2b51158f3898 3 months ago 1.44GB
19:15:11 hyperledger/fabric-kafka amd64-0.4.10 936aef6db0e6 3 months ago 1.45GB
19:15:11 hyperledger/fabric-couchdb amd64-0.4.10 3092eca241fc 3 months ago 1.61GB
19:15:11 hyperledger/fabric-baseimage amd64-0.4.10 62513965e238 3 months ago 1.39GB
19:15:11 hyperledger/fabric-baseos amd64-0.4.10 52190e831002 3 months ago 132MB
19:15:11 hyperledger/cello-user-dashboard x86_64-latest 7e031789d0e0 6 months ago 1.11GB
19:15:11 hyperledger/cello-engine x86_64-latest 19e5423b5b3e 6 months ago 792MB
19:15:11 hyperledger/cello-mongo x86_64-latest f208b65acfc4 6 months ago 792MB
19:15:11 hyperledger/cello-watchdog x86_64-latest a0f80ccc5cea 6 months ago 792MB
19:15:11 hyperledger/cello-operator-dashboard x86_64-latest c929cc4cfee7 6 months ago 792MB
19:15:11 hyperledger/cello-baseimage x86_64-latest a59b2a3337bd 6 months ago 792MB
19:15:11 hyperledger/cello-nginx x86_64-latest 402226293772 6 months ago 792MB
19:15:11 hyperledger/fabric-baseimage x86_64-0.4.7 390ac2e95bc7 6 months ago 1.41GB
19:15:11 hyperledger/fabric-zookeeper x86_64-0.4.7 1ce465be7112 6 months ago 1.39GB
19:15:11 hyperledger/fabric-kafka x86_64-0.4.7 4fed436fc0a0 6 months ago 1.4GB
19:15:11 hyperledger/fabric-couchdb x86_64-0.4.7 35228d48a25a 6 months ago 1.56GB
19:15:11 hyperledger/fabric-baseos x86_64-0.4.7 c0e784934c4e 6 months ago 152MB
19:15:11 hyperledger/fabric-baseimage x86_64-0.4.6 dbe6787b5747 7 months ago 1.37GB
19:15:11 hyperledger/fabric-zookeeper x86_64-0.4.6 92cbb952b6f8 7 months ago 1.39GB
19:15:11 hyperledger/fabric-kafka x86_64-0.4.6 554c591b86a8 7 months ago 1.4GB
19:15:11 hyperledger/fabric-couchdb x86_64-0.4.6 7e73c828fc5b 7 months ago 1.56GB
19:15:11 hyperledger/fabric-baseos x86_64-0.4.6 220e5cf3fb7f 7 months ago 151MB
19:15:11 hyperledger/indy-core-baseci 0.0.1 69b63d0d1c20 10 months ago 638MB
19:15:11 ++ docker ps -a
```
jtclark (Thu, 11 Oct 2018 23:32:01 GMT):
@rameshthoomu yes, I will look into it
jtclark (Fri, 12 Oct 2018 01:03:33 GMT):
@rickr, @rameshthoomu triggered the job once more... one thing I noticed in the dockerlog file:
jtclark (Fri, 12 Oct 2018 01:03:42 GMT):
```
Creating network "sdkintegration_default" with the default driver
Pulling ca0 (hyperledger/fabric-ca:x86_64-1.0.0)...
x86_64-1.0.0: Pulling from hyperledger/fabric-ca
Digest: sha256:b7094644bcbf6c28948fcdd0c38ffe65f98889a57da0e1bf23bd18731ef44800
Status: Downloaded newer image for hyperledger/fabric-ca:x86_64-1.0.0
Pulling orderer.example.com (hyperledger/fabric-orderer:x86_64-1.0.0)...
x86_64-1.0.0: Pulling from hyperledger/fabric-orderer
Digest: sha256:d0ea1f7e7ca04f0c4b7484f8835fd68e9bf13e6fcb700cf3a70f00a4059fc344
Status: Downloaded newer image for hyperledger/fabric-orderer:x86_64-1.0.0
Pulling peer0.org1.example.com (hyperledger/fabric-peer:x86_64-1.0.0)...
x86_64-1.0.0: Pulling from hyperledger/fabric-peer
Digest: sha256:b7c1c2a6b356996c3dbe2b9554055cd2b63194cd7a492a83de2dbabf7f7e3c65
Status: Downloaded newer image for hyperledger/fabric-peer:x86_64-1.0.0
Pulling ccenv (hyperledger/fabric-ccenv:x86_64-1.0.0)...
x86_64-1.0.0: Pulling from hyperledger/fabric-ccenv
Digest: sha256:eb2e87ea07e29a0b6b6e51e200efcc0cbaa571b8124c6b2dcc704da93bf39f24
Status: Downloaded newer image for hyperledger/fabric-ccenv:x86_64-1.0.0
```
jtclark (Fri, 12 Oct 2018 01:05:50 GMT):
not sure if `Downloaded newer image` means here.
jtclark (Fri, 12 Oct 2018 01:05:50 GMT):
not sure what `Downloaded newer image` means here.
jtclark (Fri, 12 Oct 2018 01:29:32 GMT):
Created a JIRA task to track this: https://jira.hyperledger.org/browse/FABCI-156
mbwhite (Fri, 12 Oct 2018 09:50:21 GMT):
FYI I've raised https://jira.hyperledger.org/browse/FABCI-157 to re-instate fabric-contract node module... Thanks!!!
jtclark (Fri, 12 Oct 2018 12:09:05 GMT):
@mbwhite I've prepped https://gerrit.hyperledger.org/r/#/c/26948/ to handle this. I'll have @rameshthoomu review this to ensure we have everything covered.
rickr (Fri, 12 Oct 2018 12:50:52 GMT):
@jtclark I don't think anything has changed there .. this is to test Fabric 1.0.0
jtclark (Fri, 12 Oct 2018 12:52:20 GMT):
@rickr yes, you're right..... I'm looking in to the script to see what's going on..... did this ever work? say prior to 1.3 release?
jtclark (Fri, 12 Oct 2018 12:53:24 GMT):
the thing that's interesting to me is `Downloaded newer image for hyperledger/fabric-ca:x86_64-1.0.0`
sykesm (Fri, 12 Oct 2018 12:56:59 GMT):
@dave.enyeart, @rameshthoomu I'd like to complete the go 1.11.1 upgrade. I believe go 1.11.1 is already in all of the packer images so the big hold up is the base image. The CR is out there so, iiuc, the next required steps are merging, tagging, and publishing.
rickr (Fri, 12 Oct 2018 13:01:54 GMT):
@jtclark It's been there since 1.2 it part of the verify merge
rickr (Fri, 12 Oct 2018 13:02:22 GMT):
I don't see how any recent changes impacted that.
jtclark (Fri, 12 Oct 2018 13:03:21 GMT):
@rickr ok. I'll continue diggin into it...
rickr (Fri, 12 Oct 2018 13:04:52 GMT):
I just tried to do a remerge of https://gerrit.hyperledger.org/r/#/c/26848/ this was already merged and passed then. But remerge has not been working for me .. @rameshthoomu @jtclark If that can run and passes means something really is different here.
jtclark (Fri, 12 Oct 2018 13:06:01 GMT):
@rickr agreed. something has changed.
rickr (Fri, 12 Oct 2018 13:06:50 GMT):
can we get that already merged CR to run again ? @rameshthoomu will tell us alot
jtclark (Fri, 12 Oct 2018 13:07:48 GMT):
I'm actually looking at the run that passed for that change
jtclark (Fri, 12 Oct 2018 13:08:04 GMT):
https://jenkins.hyperledger.org/job/fabric-sdk-java-merge-x86_64/318/
jtclark (Fri, 12 Oct 2018 13:08:12 GMT):
seeing if this shows us anything.....
rickr (Fri, 12 Oct 2018 13:14:21 GMT):
wrong run you need to look at 1.0.0 Other triggered builds for this event. :wink:
jtclark (Fri, 12 Oct 2018 13:14:41 GMT):
yep just realized that after looking at it :-)
jtclark (Fri, 12 Oct 2018 13:14:55 GMT):
almost right when you said it..... lol
rickr (Fri, 12 Oct 2018 13:15:34 GMT):
can you see if you can retrigger this PC https://gerrit.hyperledger.org/r/#/c/26848/ it doesn't work for me on for @rameshthoomu
rickr (Fri, 12 Oct 2018 13:15:34 GMT):
can you see if you can retrigger this PC https://gerrit.hyperledger.org/r/#/c/26848/ it doesn't work for me only for @rameshthoomu
dave.enyeart (Fri, 12 Oct 2018 13:43:09 GMT):
@sykesm I've +2ed go 1.11.1 update in https://gerrit.hyperledger.org/r/#/c/26772/
sykesm (Fri, 12 Oct 2018 13:44:09 GMT):
@dave.enyeart thanks
sykesm (Fri, 12 Oct 2018 13:45:35 GMT):
@dave.enyeart Can you submit as well?
dave.enyeart (Fri, 12 Oct 2018 13:46:59 GMT):
@sykesm you can add the second +2
rickr (Fri, 12 Oct 2018 13:47:28 GMT):
@jtclark the merged build passed again so maybe it really is something with that change :( but doesn't seem likely
rameshthoomu (Fri, 12 Oct 2018 13:57:44 GMT):
@rickr I am not a magician to make it work with my magics, sometimes that's works when I re-trigger..
rameshthoomu (Fri, 12 Oct 2018 13:57:44 GMT):
@rickr I am not a magician to make it work with my magics, sometimes that's works when I re-trigger.. :wink:
rameshthoomu (Fri, 12 Oct 2018 13:58:22 GMT):
I have asked LF team to look into this.. Will let you know by next week..
rickr (Fri, 12 Oct 2018 13:59:26 GMT):
hey mr *magician* seemed I think to work for me this time
jtclark (Fri, 12 Oct 2018 14:16:31 GMT):
@rickr should this be happening with the reverify-1.0.0:
jtclark (Fri, 12 Oct 2018 14:16:35 GMT):
`No such service: ccenv`
rickr (Fri, 12 Oct 2018 14:17:33 GMT):
where do you see that ?
jtclark (Fri, 12 Oct 2018 14:17:45 GMT):
in the dockerlog
jtclark (Fri, 12 Oct 2018 14:17:51 GMT):
https://jenkins.hyperledger.org/job/fabric-sdk-java-verify-1.0.0-x86_64/1294/artifact/src/test/fixture/sdkintegration/dockerlogfile.log
rickr (Fri, 12 Oct 2018 14:18:25 GMT):
let me try something
rickr (Fri, 12 Oct 2018 14:20:26 GMT):
I removed that cause it shouldn't be needed as current sdk seems to work .. not sure why 1.0.0 would choke
jtclark (Fri, 12 Oct 2018 14:21:26 GMT):
you removed it just now, or it's been removed?
rickr (Fri, 12 Oct 2018 14:21:33 GMT):
no
rickr (Fri, 12 Oct 2018 14:21:34 GMT):
now
jtclark (Fri, 12 Oct 2018 14:21:37 GMT):
ok
jtclark (Fri, 12 Oct 2018 14:21:50 GMT):
trying another reverify?
rickr (Fri, 12 Oct 2018 14:21:56 GMT):
wait
jtclark (Fri, 12 Oct 2018 14:21:59 GMT):
ok
rickr (Fri, 12 Oct 2018 14:29:24 GMT):
I restored that .. I'm confused cause it isn't needed for 1.3
sudeshrshetty (Fri, 12 Oct 2018 14:33:27 GMT):
Hi, looks like s390 is encountering some issues,
https://jenkins.hyperledger.org/job/fabric-sdk-go-tests-verify-s390x/4092/console
all SDK s390 builds started to fail since last night
rickr (Fri, 12 Oct 2018 14:33:50 GMT):
@jtclark I'm fairly certain that was it -- have to update fabric.sh too for it work thanks .. didn't know dockerlogs were directed there or else I would have caught this
jtclark (Fri, 12 Oct 2018 14:44:48 GMT):
good that they are
jtclark (Fri, 12 Oct 2018 14:45:12 GMT):
I'll up the JIRA and close <--- @rameshthoomu
rameshthoomu (Fri, 12 Oct 2018 16:05:43 GMT):
@swetha could you please look into this https://gerrit.hyperledger.org/r/#/c/26827/
rameshthoomu (Fri, 12 Oct 2018 18:17:02 GMT):
@sykesm observed goimport errors on fabric builds. Could you please check this https://jenkins.hyperledger.org/view/fabric/job/fabric-verify-build-checks-x86_64/6052/console
sykesm (Fri, 12 Oct 2018 18:52:15 GMT):
This is another example of fallout from constantly rebuilding tools from master.
sykesm (Fri, 12 Oct 2018 18:52:57 GMT):
3 hours ago, a commit landed (that I disagree with) into goimports. It no longer honors explicit grouping
sykesm (Fri, 12 Oct 2018 18:53:19 GMT):
since each and every one of our builds pulls the tools from master at the time of the build, we get what we get
sykesm (Fri, 12 Oct 2018 18:53:38 GMT):
so, as with earlier in the week with lint, we've been bitten by imports
sykesm (Fri, 12 Oct 2018 18:58:22 GMT):
for those that want to look: https://github.com/golang/tools/commit/12a7c317e894c0a622b5ed27f0a102fcdd56d1ad
It impacts builds back to at least 1.2
sykesm (Fri, 12 Oct 2018 19:18:50 GMT):
actually looks like linting 1.0 is impacted as well
swetha (Sat, 13 Oct 2018 02:21:49 GMT):
@rameshthoomu just reviewed it
baoyangc (Sun, 14 Oct 2018 12:53:32 GMT):
https://jenkins.hyperledger.org/job/fabric-sdk-go-tests-verify-x86_64/3989/
why this meet an failure?
baoyangc (Sun, 14 Oct 2018 12:53:41 GMT):
Clipboard - October 14, 2018 8:52 PM
jtclark (Sun, 14 Oct 2018 13:07:09 GMT):
@baoyangc Hi there. the Jenkins reporting in the comment section of your patch set doesn't show the reason(s) behind the failure, but if you click on the link provided it will show you
jtclark (Sun, 14 Oct 2018 13:07:14 GMT):
https://jenkins.hyperledger.org/job/fabric-sdk-go-tests-verify-x86_64/3989/console
jtclark (Sun, 14 Oct 2018 13:07:23 GMT):
appears that there are some linter issues
jtclark (Sun, 14 Oct 2018 13:08:19 GMT):
```
00:05:11.619 pkg/msp/fabcaadapter.go:47:39:error: undefined: cappi (vet, vet)
00:05:11.619 Makefile:289: recipe for target 'unit-test' failed
```
jtclark (Sun, 14 Oct 2018 13:08:41 GMT):
```
00:05:11.618 pkg/msp/fabcaadapter.go:69:15:error: cannot use name (variable of type int) as string value in struct literal (gotype, interfacer, maligned, unconvert)
```
jtclark (Sun, 14 Oct 2018 13:08:50 GMT):
and several others
baoyangc (Sun, 14 Oct 2018 17:06:11 GMT):
@jtclark thanks
mastersingh24 (Mon, 15 Oct 2018 08:36:02 GMT):
@rameshthoomu - can you take a look at https://jira.hyperledger.org/browse/FABCI-162 ?
mastersingh24 (Mon, 15 Oct 2018 08:36:02 GMT):
@rameshthoomu - can you take a look at https://jira.hyperledger.org/browse/FABCI-162 ?
Here's a fix (I think) https://gerrit.hyperledger.org/r/26996
jtclark (Mon, 15 Oct 2018 10:50:44 GMT):
@rameshthoomu :point_up_tone2: reviewed. LGTM.
mbwhite (Mon, 15 Oct 2018 15:43:01 GMT):
Hi @jtclark - the change for the fabric-chaincode-node has been merged... though it seemed to have some problems on the publish
mbwhite (Mon, 15 Oct 2018 15:43:12 GMT):
a 1.4.0 snapshot has been published though
jtclark (Mon, 15 Oct 2018 15:43:38 GMT):
@mbwhite thanks for the update. will have a look
mbwhite (Mon, 15 Oct 2018 15:43:48 GMT):
:-)
jtclark (Mon, 15 Oct 2018 15:46:26 GMT):
@mbwhite can you also confirm which branch we need to publish the fabric-contract-api module?
mbwhite (Mon, 15 Oct 2018 15:52:10 GMT):
it's master
mbwhite (Mon, 15 Oct 2018 15:52:24 GMT):
as a 1.4.0
jtclark (Mon, 15 Oct 2018 18:59:09 GMT):
@mbwhite changed has been merged.
AdnanC (Tue, 16 Oct 2018 18:42:49 GMT):
nexus
AdnanC (Tue, 16 Oct 2018 18:48:28 GMT):
@rameshthoomu trying tp pull latest nexus images. With `./pull_build_artifacts.sh --pull_All`, I am seeing a gzip error
```
gzip: unknown compression format
tar: Child returned status 1
tar: Error is not recoverable: exiting now
```
Have anyone seen this error before?
AdnanC (Tue, 16 Oct 2018 18:48:50 GMT):
in OSX
rameshthoomu (Tue, 16 Oct 2018 18:50:41 GMT):
@AdnanC did you try this `STABLE_VERSION=1.3.0-stable BASE_VERSION=1.3.0 ./scripts/pull_build_artifacts.sh --pull_All`
rameshthoomu (Tue, 16 Oct 2018 18:51:04 GMT):
check the help provided in the script
AdnanC (Tue, 16 Oct 2018 18:51:32 GMT):
I was trying 1.4.0
rameshthoomu (Tue, 16 Oct 2018 18:51:42 GMT):
let me check that
AdnanC (Tue, 16 Oct 2018 18:52:26 GMT):
`Adnans-MacBook-Pro:scripts adnanc$ STABLE_VERSION=1.4.0 BASE_VERSION=1.4.0 ./pull_build_artifacts.sh --pull_All`
rameshthoomu (Tue, 16 Oct 2018 18:53:00 GMT):
STABLE_VERSION should be 1.4.0-stable
AdnanC (Tue, 16 Oct 2018 18:55:28 GMT):
ah ok, thanks! trying it now
rameshthoomu (Wed, 17 Oct 2018 04:16:34 GMT):
@sambhavdutt seems fabric merge job is failing since ~5 builds.. Could you please check and create a bug for this
sambhavdutt (Wed, 17 Oct 2018 12:49:06 GMT):
@rameshthoomu
sure, will do
sambhavdutt (Wed, 17 Oct 2018 12:51:12 GMT):
this has been passing now, I'll create one if it fails again
nkl199 (Wed, 17 Oct 2018 13:25:45 GMT):
Hi all, I've just raised https://jira.hyperledger.org/browse/FABCI-170 as it is currently blocking work on a fabric-sdk-node jira. It relates to the requirement of publishing a new npm package to enable code consolidation within the fabric-sdk-node repository
rameshthoomu (Wed, 17 Oct 2018 14:06:34 GMT):
https://ci-docs.readthedocs.io/en/latest/
nkl199 (Wed, 17 Oct 2018 14:56:44 GMT):
the above doesn't indicate how to get a new npm module out though ....
rameshthoomu (Wed, 17 Oct 2018 14:57:00 GMT):
@nkl199 checking
nkl199 (Wed, 17 Oct 2018 14:57:04 GMT):
thanks
rameshthoomu (Wed, 17 Oct 2018 14:58:52 GMT):
@nkl199 so you want me to publish fabric-common module
rameshthoomu (Wed, 17 Oct 2018 14:59:35 GMT):
@bretharrison @davidkel ^^
rameshthoomu (Wed, 17 Oct 2018 15:10:41 GMT):
@andrew-coleman ^^
andrew-coleman (Wed, 17 Oct 2018 15:10:41 GMT):
Has joined the channel.
nkl199 (Wed, 17 Oct 2018 15:28:48 GMT):
thats the plan :thumbsup:
rameshthoomu (Wed, 17 Oct 2018 15:41:41 GMT):
@jtclark Could you please work on this FABCI-170
jtclark (Wed, 17 Oct 2018 15:42:08 GMT):
@rameshthoomu I'll take a look
jtclark (Wed, 17 Oct 2018 15:43:20 GMT):
@rameshthoomu I took the JIRA ticket
rameshthoomu (Wed, 17 Oct 2018 15:43:48 GMT):
yes.. it's assigned to you
Baha-sk (Wed, 17 Oct 2018 21:12:26 GMT):
@rameshthoomu something changed for z builds? they've been surprisingly successful all day long :)
rameshthoomu (Wed, 17 Oct 2018 21:14:28 GMT):
@Baha-sk good to know.. Nothing changed from CI configuration
Baha-sk (Wed, 17 Oct 2018 22:16:45 GMT):
@rameshthoomu ok.. then probably my patch corrected the z build discrepancy .. cheers!
rameshthoomu (Thu, 18 Oct 2018 14:38:38 GMT):
@mastersingh24 Could you please check this FAB-12527
rameshthoomu (Thu, 18 Oct 2018 14:39:27 GMT):
00:03:17.609 W: Failed to fetch http://security.debian.org/dists/jessie/updates/InRelease Unable to find expected entry 'main/binary-s390x/Packages' in Release file (Wrong sources.list entry or malformed file)
Observed above error while building fabric-ca image in release-1.1 branch
rameshthoomu (Thu, 18 Oct 2018 14:39:51 GMT):
it's the `apt-get udpate` is causing this issue
atirekg (Thu, 18 Oct 2018 16:48:39 GMT):
Has joined the channel.
AndrewNRise (Fri, 19 Oct 2018 08:16:04 GMT):
Has joined the channel.
rameshthoomu (Fri, 19 Oct 2018 13:39:08 GMT):
@dave.enyeart Could you please check this https://jira.hyperledger.org/browse/FAB-12512
dexhunter (Sat, 20 Oct 2018 10:23:52 GMT):
Has joined the channel.
dave.enyeart (Sat, 20 Oct 2018 14:32:34 GMT):
@rameshthoomu the update to go 1.11.1 broke windows, have to do some revendoring to fix it: https://gerrit.hyperledger.org/r/#/c/27120/
dave.enyeart (Sat, 20 Oct 2018 15:50:10 GMT):
@rameshthoomu @sambhavdutt See failure here: https://logs.hyperledger.org/production/vex-yul-hyp-jenkins-3/fabric-ca-merge-s390x/558/console.log.gz
dave.enyeart (Sat, 20 Oct 2018 15:50:29 GMT):
it is complaining about goimport errors in fabric-ca that have already been merged in master
dave.enyeart (Sat, 20 Oct 2018 15:50:51 GMT):
I thought the merge jobs ran against latest master, rather than the CR dependency stack
dave.enyeart (Sat, 20 Oct 2018 15:50:57 GMT):
What am I missing?
rameshthoomu (Sat, 20 Oct 2018 15:54:15 GMT):
@dave.enyeart yes that should be the case.. Will check
rameshthoomu (Sat, 20 Oct 2018 15:54:40 GMT):
I re-triggered this morning and I see the build passed successfully
dave.enyeart (Sat, 20 Oct 2018 15:55:02 GMT):
you'll see that https://gerrit.hyperledger.org/r/#/c/26986/ has fixed the same goimport errors
dave.enyeart (Sat, 20 Oct 2018 15:55:02 GMT):
you'll see that https://gerrit.hyperledger.org/r/#/c/26986/ has fixed the same goimport errors last week
rameshthoomu (Sat, 20 Oct 2018 15:55:21 GMT):
yes..
laurasp (Wed, 24 Oct 2018 08:34:33 GMT):
Has joined the channel.
NavjotSingh (Thu, 25 Oct 2018 11:52:27 GMT):
Has joined the channel.
14gracel (Thu, 25 Oct 2018 13:24:26 GMT):
docs
14gracel (Thu, 25 Oct 2018 13:24:26 GMT):
docs
rameshthoomu (Fri, 26 Oct 2018 13:54:12 GMT):
@dthom all Z nodes went offline.. Could you please check
rameshthoomu (Fri, 26 Oct 2018 13:54:27 GMT):
both in Sandbox and Production env..
dthom (Fri, 26 Oct 2018 13:59:33 GMT):
@rameshthoomu checking now
rameshthoomu (Fri, 26 Oct 2018 14:00:57 GMT):
thank you
dthom (Fri, 26 Oct 2018 14:05:14 GMT):
@rameshthoomu mainframes are down from 8am to 10am today to fix an issue in storage system
rameshthoomu (Fri, 26 Oct 2018 14:06:34 GMT):
ok what is the action now?
rameshthoomu (Fri, 26 Oct 2018 14:06:34 GMT):
are you restarting now?
dthom (Fri, 26 Oct 2018 14:08:28 GMT):
I will as soon as the systems are back up
rameshthoomu (Fri, 26 Oct 2018 14:11:34 GMT):
ok
dthom (Fri, 26 Oct 2018 17:37:28 GMT):
@rameshthoomu systems are back online
AbhinayB (Mon, 29 Oct 2018 09:14:55 GMT):
Hi!
Is there a plan to integrate IoTs to fabric?
For example, an IoT can update transactions into the fabric periodically.
How do we authenticate it?
What APIs are provided for the IoT to connect?
How do we secure the APIs?
AbhinayB (Mon, 29 Oct 2018 09:14:55 GMT):
Hi!
Is there a plan to integrate IoTs to fabric?
For example, consider a case where an IoT can query and update transactions in the fabric periodically.
How do we authenticate it?
What APIs are provided for the IoT to connect?
How do we secure the APIs?
mko (Mon, 29 Oct 2018 12:56:39 GMT):
Has joined the channel.
rameshthoomu (Mon, 29 Oct 2018 15:32:43 GMT):
@vijay.bP Patch to remove e2e_cli https://gerrit.hyperledger.org/r/#/c/27253/
rameshthoomu (Mon, 29 Oct 2018 15:32:56 GMT):
I think we have to remove the same from CI scripts
rameshthoomu (Mon, 29 Oct 2018 15:33:08 GMT):
in e2e, we execute e2e_cli tests..
Baha-sk (Tue, 30 Oct 2018 14:19:19 GMT):
guys... https://jenkins.hyperledger.org/job/fabric-sdk-go-tests-verify-x86_64/ and https://jenkins.hyperledger.org/job/fabric-sdk-go-tests-verify-s390x/ are passing every two builds without code change.. the environments to be more solid (docker containers to respond faster, etc.).. the issue is not related to code change.. the source of the issue is related to the environment being able to handle requests on time..
Baha-sk (Tue, 30 Oct 2018 14:19:19 GMT):
guys... https://jenkins.hyperledger.org/job/fabric-sdk-go-tests-verify-x86_64/ and https://jenkins.hyperledger.org/job/fabric-sdk-go-tests-verify-s390x/ are passing every two builds without code change.. the environments need to be more solid (docker containers to respond faster, etc.).. the issue is not related to code change.. the source of the issue is related to the environment being able to handle requests on time..
rameshthoomu (Wed, 31 Oct 2018 15:20:10 GMT):
@tijohnson @jwagantall We are seeing maven issues in fabric-sdk-java tests.. Tests are working as expected in local machines but seems CI env some issue with maven.. Could you please check this issue
```
00:12:45.334 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test (default-test) on project fabric-sdk-java: Execution default-test of goal org.apache.maven.plugins:maven-surefire-plugin:2.19.1:test failed: The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
```
rameshthoomu (Wed, 31 Oct 2018 15:21:06 GMT):
@rickr what is the version of maven-surefire-plugin you have? CI has maven-surefire-plugin:2.19.1
rickr (Wed, 31 Oct 2018 15:31:52 GMT):
mvn --version
Apache Maven 3.5.0 (Red Hat 3.5.0-6)
rameshthoomu (Wed, 31 Oct 2018 15:34:11 GMT):
Seems this plugin is causing the problem
```
org.apache.maven.plugins:maven-surefire-plugin:2.19.1
```
tijohnson (Wed, 31 Oct 2018 16:52:52 GMT):
@ramesh you still seeing this problem ?
tijohnson (Wed, 31 Oct 2018 16:59:21 GMT):
This might be problem: 06:57:05 [WARNING] Some problems were encountered while building the effective model for org.hyperledger.fabric-sdk-java:fabric-sdk-java:jar:1.3.0-SNAPSHOT
06:57:05 [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-jar-plugin is missing. @ line 515, column 21
06:57:05 [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
06:57:05 [WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
tijohnson (Wed, 31 Oct 2018 16:59:21 GMT):
This might be problem:06:57:05 [WARNING] Some problems were encountered while building the effective model for org.hyperledger.fabric-sdk-java:fabric-sdk-java:jar:1.3.0-SNAPSHOT
06:57:05 [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-jar-plugin is missing. @ line 515, column 21
06:57:05 [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
06:57:05 [WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
tijohnson (Wed, 31 Oct 2018 16:59:21 GMT):
This might be problem:
06:57:05 [WARNING] Some problems were encountered while building the effective model for org.hyperledger.fabric-sdk-java:fabric-sdk-java:jar:1.3.0-SNAPSHOT
06:57:05 [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-jar-plugin is missing. @ line 515, column 21
06:57:05 [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
06:57:05 [WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
rameshthoomu (Wed, 31 Oct 2018 17:48:38 GMT):
Yes we are still seeing this issue..
rameshthoomu (Wed, 31 Oct 2018 17:48:50 GMT):
The above error is just a warning and I see the same in successful builds
tijohnson (Wed, 31 Oct 2018 17:49:16 GMT):
I just noticed that
rameshthoomu (Wed, 31 Oct 2018 17:49:25 GMT):
@rickr We are using 1.8.0 JAVA_HOME=/usr/lib/jvm/java-1.8.0-openjdk-amd64
tijohnson (Wed, 31 Oct 2018 17:51:09 GMT):
I see same in Config for fabric-sdk-java-merge-x86
rickr (Wed, 31 Oct 2018 17:51:53 GMT):
what has changed ? nothing the JSDK
rameshthoomu (Wed, 31 Oct 2018 18:02:15 GMT):
from CI config, as far as I know, nothing has changed recently..
rickr (Wed, 31 Oct 2018 18:02:44 GMT):
is this a solid break ? intermittent ?
rameshthoomu (Wed, 31 Oct 2018 18:02:58 GMT):
It's failing consistently..
rameshthoomu (Wed, 31 Oct 2018 18:03:29 GMT):
Seems somethings has been changed org.apache.maven.plugins:maven-surefire-plugin:2.19.1
rameshthoomu (Wed, 31 Oct 2018 18:04:11 GMT):
2.19.1 is very old plugin.. https://mvnrepository.com/artifact/org.apache.maven.plugins/maven-surefire-plugin
rickr (Wed, 31 Oct 2018 18:04:37 GMT):
Well I clean out my .m2 repo locally to build from scratch .. no problems
rameshthoomu (Wed, 31 Oct 2018 18:04:52 GMT):
:(
tijohnson (Wed, 31 Oct 2018 18:05:09 GMT):
feeling pretty useless....
rameshthoomu (Wed, 31 Oct 2018 18:06:13 GMT):
@rickr do you have the same version 2.19.1 for maven-surefire-plugin
rameshthoomu (Wed, 31 Oct 2018 18:06:17 GMT):
could you please check
rickr (Wed, 31 Oct 2018 18:06:39 GMT):
where is it displayed ?
rickr (Wed, 31 Oct 2018 18:06:54 GMT):
what maven version are you using ?
rameshthoomu (Wed, 31 Oct 2018 18:07:13 GMT):
have to check
rickr (Wed, 31 Oct 2018 18:07:21 GMT):
Apache Maven 3.5.0 (Red Hat 3.5.0-6)
rameshthoomu (Wed, 31 Oct 2018 18:07:30 GMT):
ok
tijohnson (Wed, 31 Oct 2018 18:09:40 GMT):
an earlier log of successful fabric-sdk-java-merge-x86_64 build uses version 2.19.1
it also re-compiles the maven modules but did not get a Error when it attempts to load them
rickr (Wed, 31 Oct 2018 18:10:32 GMT):
I'd check the maven version you're running
tijohnson (Wed, 31 Oct 2018 18:11:39 GMT):
That build was from Oct 24
rameshthoomu (Wed, 31 Oct 2018 18:21:02 GMT):
```
00:00:12.574 Apache Maven 3.3.9
00:00:12.574 Maven home: /usr/share/maven
00:00:12.574 Java version: 1.8.0_181, vendor: Oracle Corporation
```
rickr (Wed, 31 Oct 2018 18:21:34 GMT):
maybe move up to 3.5 ?
rameshthoomu (Wed, 31 Oct 2018 18:22:21 GMT):
@tijohnson can we do that now
tijohnson (Wed, 31 Oct 2018 18:24:28 GMT):
I can inquire....
tijohnson (Wed, 31 Oct 2018 18:24:51 GMT):
about what that would take and what the risks are
tijohnson (Wed, 31 Oct 2018 18:29:54 GMT):
Does Maven 3.5 work with our current version of Java
tijohnson (Wed, 31 Oct 2018 18:29:54 GMT):
Does Maven 3.5 work with our current version of Java: ava-1.8.0-openjdk-amd64
tijohnson (Wed, 31 Oct 2018 18:55:27 GMT):
We have Maven 3.5 available, looking into making it available. You would still have to make change your builds to use it
tijohnson (Wed, 31 Oct 2018 18:55:27 GMT):
We have Maven 3.5 available, looking into installing it You would still have to make change your builds to use it
rameshthoomu (Wed, 31 Oct 2018 18:55:54 GMT):
@tijohnson give me 5 mins time..
rameshthoomu (Wed, 31 Oct 2018 18:56:22 GMT):
I will let you know.. trying to fix this with this change https://gerrit.hyperledger.org/r/#/c/27292/2/src/test/cirun.sh
rameshthoomu (Wed, 31 Oct 2018 18:56:55 GMT):
still failed
rameshthoomu (Wed, 31 Oct 2018 18:57:40 GMT):
https://stackoverflow.com/questions/13170860/failed-to-execute-goal-org-apache-maven-pluginsmaven-surefire-plugin2-10test
tijohnson (Wed, 31 Oct 2018 19:01:35 GMT):
Just added mvn35 (maven 3.5.0) to production, I will also do sandbox
tijohnson (Wed, 31 Oct 2018 19:04:33 GMT):
I assume you know what to do to use mvn35 (instead of mvn33) ?
rameshthoomu (Wed, 31 Oct 2018 19:06:18 GMT):
did you update to sandbox? Apache Maven 3.3.9
rameshthoomu (Wed, 31 Oct 2018 19:06:23 GMT):
I still see above version
tijohnson (Wed, 31 Oct 2018 19:07:30 GMT):
just saved sandbox
tijohnson (Wed, 31 Oct 2018 19:07:30 GMT):
just saved tool config for sandbox
tijohnson (Wed, 31 Oct 2018 19:18:29 GMT):
stomach growling, need lunch, back in 30min
rameshthoomu (Wed, 31 Oct 2018 19:19:23 GMT):
ok..
tijohnson (Wed, 31 Oct 2018 19:21:40 GMT):
other yaml files in ci-managment: mvn-version: mvn35
jjb/fabric-sdk-java/fabric-sdk-java-jobs.yaml: maven-version: 'mvn33' should it be mvn-version ?
tijohnson (Wed, 31 Oct 2018 19:21:47 GMT):
just a thought
rameshthoomu (Wed, 31 Oct 2018 19:23:07 GMT):
we don;t use that job
tijohnson (Wed, 31 Oct 2018 19:52:49 GMT):
back from lunch
rameshthoomu (Wed, 31 Oct 2018 19:55:16 GMT):
Did you upgrade maven ins andbox
rameshthoomu (Wed, 31 Oct 2018 19:55:19 GMT):
I still see 00:00:09.901 Apache Maven 3.3.9
rameshthoomu (Wed, 31 Oct 2018 19:55:33 GMT):
only in sandbox
tijohnson (Wed, 31 Oct 2018 19:57:13 GMT):
oops mnv35 not mvn35 fixed now
rameshthoomu (Wed, 31 Oct 2018 19:57:29 GMT):
cool
rameshthoomu (Wed, 31 Oct 2018 20:00:27 GMT):
Still showing 00:00:11.480 Apache Maven 3.3.9
00:00:11.480 Maven home: /usr/share/maven
rameshthoomu (Wed, 31 Oct 2018 20:20:44 GMT):
@tijohnson Let me know after you update the the maven version to 3.5.0
tijohnson (Wed, 31 Oct 2018 20:25:40 GMT):
It should install both versions (3.3.9 & 3.5.0) same as production
tijohnson (Wed, 31 Oct 2018 20:25:40 GMT):
It should install both versions (3.3.9 & 3.5.0) same as production AKA mvn33 mvn35
rameshthoomu (Wed, 31 Oct 2018 20:27:18 GMT):
It seems 3.3.9 is active
tijohnson (Wed, 31 Oct 2018 20:34:53 GMT):
it that true for both production and sandbox ?
tijohnson (Wed, 31 Oct 2018 20:47:38 GMT):
I don't understand how your build selects which maven to use when both 3.3.9 & 3.5.0 are installed
tijohnson (Wed, 31 Oct 2018 21:04:30 GMT):
is it possible they are are both installed in /usr/share/maven and last one wins ?
rameshthoomu (Wed, 31 Oct 2018 21:58:16 GMT):
FABJ-381
rameshthoomu (Wed, 31 Oct 2018 21:59:31 GMT):
@tijohnson if possible can you make 3.5.0 is the default version
rameshthoomu (Wed, 31 Oct 2018 21:59:31 GMT):
@tijohnson if possible can you make 3.5.0 as the default version
tijohnson (Wed, 31 Oct 2018 22:30:20 GMT):
I changed sandbox so mvn35 is ONLY version here is log https://jenkins.hyperledger.org/sandbox/job/fabric-sdk-java-merge-x86_64/7/console
swetha (Wed, 31 Oct 2018 22:41:23 GMT):
Hi All, We are still having issues with node in our jenkins pipeline job for fabric-chaincode-evm. It does seem like it successfully installs but some reason from our run integration script node is no longer there. We need a little help to make sure we are running our tests correctly with the node installation.
rameshthoomu (Thu, 01 Nov 2018 00:31:45 GMT):
@swetha Shall I push change on top of your patch?
rameshthoomu (Thu, 01 Nov 2018 00:32:04 GMT):
It seems npm is not set globally..
swetha (Thu, 01 Nov 2018 00:51:02 GMT):
@rameshthoomu Oh I didn't realize that. But we aren't able to find the node installation at all
swetha (Thu, 01 Nov 2018 00:51:09 GMT):
https://jenkins.hyperledger.org/job/fabric-chaincode-evm-verify-master-x86_64/205/execution/node/47/log/
swetha (Thu, 01 Nov 2018 00:51:35 GMT):
But sure pleas feel free to push change on top of our patch
swetha (Thu, 01 Nov 2018 00:51:35 GMT):
But sure please feel free to push change on top of our patch
swetha (Thu, 01 Nov 2018 00:51:35 GMT):
But sure please feel free to push changes on top of our patch
m.hago (Thu, 01 Nov 2018 12:17:59 GMT):
Has joined the channel.
rameshthoomu (Thu, 01 Nov 2018 13:39:58 GMT):
@tijohnson
rameshthoomu (Thu, 01 Nov 2018 13:39:59 GMT):
https://jira.hyperledger.org/browse/IN-39
rickr (Thu, 01 Nov 2018 17:32:05 GMT):
@rameshthoomu @tijohnson https://gerrit.hyperledger.org/r/#/c/27308/ +1 Hyperledger Jobbuilder
rickr (Thu, 01 Nov 2018 17:37:36 GMT):
I stopped it from forking. But it affects Jcoco so not a good solution. I want Maven upgraded to the version I'm running 3.5 .
I have another *theory* that it can't fork because of lack of memory -- it's a long shot. Maybe fabric and the JDK has gone over what the VM will give?
But still lets get Maven updated
rameshthoomu (Thu, 01 Nov 2018 17:39:04 GMT):
Yes.. @tijohnson is working on this..
tijohnson (Thu, 01 Nov 2018 17:40:29 GMT):
Slowing but surely....
rameshthoomu (Thu, 01 Nov 2018 17:45:54 GMT):
@swetha I am still working on npm path issue..
rameshthoomu (Thu, 01 Nov 2018 17:46:01 GMT):
Will update you.. sorry for the delay
rameshthoomu (Thu, 01 Nov 2018 17:46:46 GMT):
npm path is resetting between shells ..
swetha (Thu, 01 Nov 2018 17:50:21 GMT):
@rameshthoomu Thanks for looking into it! Please let me know how I can help in the debugging
rameshthoomu (Thu, 01 Nov 2018 20:51:48 GMT):
@swetha pushed the change set with the fix but I see web3 integration test is failing
rameshthoomu (Thu, 01 Nov 2018 20:52:08 GMT):
Is there any way to export the PATH before you run this test..
rameshthoomu (Thu, 01 Nov 2018 20:55:03 GMT):
@dthom any update on this https://jira.hyperledger.org/browse/FAB-12670
swetha (Thu, 01 Nov 2018 21:50:23 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=DK6pMZafKWgKa7YpW) @rameshthoomu Do you want me to add a print statement or what should I export the path as?
rameshthoomu (Thu, 01 Nov 2018 22:40:25 GMT):
@swetha export PATH=$PATH:/home/jenkins/.nvm/versions/node/v8.11.3/bin
swetha (Thu, 01 Nov 2018 22:52:06 GMT):
Okay I think that is already in the path. The error I see now is about the npm module so I will debug. Thanks so much for your help!
rameshthoomu (Fri, 02 Nov 2018 13:19:36 GMT):
@rickr https://gerrit.hyperledger.org/r/#/c/27308/ Could you please merge this change to make e2e tests stable..
iserikov (Fri, 02 Nov 2018 13:20:14 GMT):
Has joined the channel.
rickr (Fri, 02 Nov 2018 13:47:11 GMT):
no can do Not in my powers. Also as stated this is *not* the *solution* .
rickr (Fri, 02 Nov 2018 16:11:06 GMT):
@tijohnson Is it easy to try and up the memory on one of these systems and see if it helps ?
tijohnson (Fri, 02 Nov 2018 18:15:34 GMT):
@rickr There are multiple images which one is your build using
rickr (Fri, 02 Nov 2018 18:33:49 GMT):
Sorry not sure what you mean by `images` .
This was last merged and was of course successful. If that helps you any.
tijohnson (Fri, 02 Nov 2018 22:18:03 GMT):
look for line in first 20 lines of build log: Building remotely on snd-ubuntu1604-x86_64-4c-16g-131
this is ubunbtu 1604 on x86_64 4 cores 16g memory
tijohnson (Fri, 02 Nov 2018 22:18:11 GMT):
@rickr
rameshthoomu (Mon, 05 Nov 2018 19:44:45 GMT):
@dthom @harrijk
rameshthoomu (Mon, 05 Nov 2018 19:44:45 GMT):
@dthom @harrijk Could you please look into this.. FAB-12670
rameshthoomu (Mon, 05 Nov 2018 19:45:40 GMT):
this is related to the softhsm issue in s390x builds.. I tried to install in one of the z build node in sandbox but getting error with gpgchecks
swetha (Mon, 05 Nov 2018 19:55:26 GMT):
Hi all, running into another issue with the fabric-chaincode-evm tests. It seems like downloading the patch is running into errors: https://jenkins.hyperledger.org/job/fabric-chaincode-evm-verify-master-x86_64/234/console. Is anyone familiar with this error?
rameshthoomu (Mon, 05 Nov 2018 19:57:19 GMT):
yes @swetha .. It seems gerrit mirror is failed Linux Foundation Infra support team is working on this
swetha (Mon, 05 Nov 2018 19:57:29 GMT):
Okay, thanks!
sambhavdutt (Mon, 05 Nov 2018 21:36:25 GMT):
Please note that all the e2e tests(master branch) are failing in the sdk-node tests, including the fabric-merge-end-2-end, and fabric-ca-end-2-end tests.
https://jira.hyperledger.org/browse/FABN-996
sambhavdutt (Mon, 05 Nov 2018 21:39:27 GMT):
Got an update from Bret Harrison that he will look into this tomorrow
swetha (Mon, 05 Nov 2018 21:53:24 GMT):
@rameshthoomu Question about the node fix for the fabric-chaincode integration tests. Is it unavoidable about installing node in the integration test script? I am trying to keep all the jenkins specific aspect of the tests in the Jenkinsfile
rameshthoomu (Mon, 05 Nov 2018 21:54:18 GMT):
I think it is possible.. I am doing the same in fabric-sdk-node and it's working as expected..
rameshthoomu (Mon, 05 Nov 2018 21:54:42 GMT):
not sure why we are getting npm not found error..
rameshthoomu (Mon, 05 Nov 2018 21:55:04 GMT):
Keep it in Jenkinsfile and will see how that goes..
rameshthoomu (Mon, 05 Nov 2018 21:55:29 GMT):
if that doesn't work, then I will use withEnv to install the node from Jenkinsfile
swetha (Mon, 05 Nov 2018 21:55:40 GMT):
Okay, thanks I will let you know how that goes
rameshthoomu (Mon, 05 Nov 2018 21:56:03 GMT):
ok sure
MHBauer (Mon, 05 Nov 2018 21:58:38 GMT):
@rameshthoomu I'm working with @swetha , does the jenkins have docker support? or docker installed? I'm used to having some kind of containerized environment for my builds.
rameshthoomu (Mon, 05 Nov 2018 22:00:01 GMT):
yes.. it's installed Version: 18.06.1-ce
swetha (Tue, 06 Nov 2018 00:03:36 GMT):
@rameshthoomu I think we need to do the withEnv piece you were mentioning. Is there an example I could look at for that?
rameshthoomu (Tue, 06 Nov 2018 00:11:06 GMT):
I was looking into this https://stackoverflow.com/questions/36575480/installing-node-on-jenkins-2-0-using-the-pipeline-plugin
swetha (Tue, 06 Nov 2018 00:13:30 GMT):
Thanks, I will take a look at that
swetha (Tue, 06 Nov 2018 00:24:27 GMT):
Are these plugins installed in our jenkins pipeline already?
rameshthoomu (Tue, 06 Nov 2018 00:28:08 GMT):
I don't think they are installed.. Could you please ask @jwagantall to install
MHBauer (Tue, 06 Nov 2018 01:23:05 GMT):
is there a general artifact place for images and zips and such, or should I just go ahead and think about dockerhub/quay/etc?
rameshthoomu (Tue, 06 Nov 2018 01:25:56 GMT):
@MHBauer for which images? fabric?
rameshthoomu (Tue, 06 Nov 2018 01:26:22 GMT):
We publish in nexus (nightly builds) and dockerhub (Official builds)
jwagantall (Tue, 06 Nov 2018 01:27:35 GMT):
@swetha the jenkins sandbox has the pipeline v2.5 installed.. we can install it in prod once is tested in sandbox
MHBauer (Tue, 06 Nov 2018 01:28:46 GMT):
if I wanted to have a build image, rather than some final artifact. I suppose I can build it in one step and carry it around through future steps, but it might make more sense for it to be commonly available rather than 'only on the build makchine'.
rameshthoomu (Tue, 06 Nov 2018 01:30:51 GMT):
You can use nexus3 for docker and nexu2 for binaries to keep regular artifacts..
MHBauer (Tue, 06 Nov 2018 01:31:00 GMT):
neat.
swetha (Tue, 06 Nov 2018 01:31:25 GMT):
@jwagantall Okay so until that happens we won't be able to have the node plugin?
rameshthoomu (Tue, 06 Nov 2018 01:32:30 GMT):
@jwagantall I think you have install https://wiki.jenkins.io/display/JENKINS/NodeJS+Plugin in sandbox to test with pipeline
jwagantall (Tue, 06 Nov 2018 01:33:11 GMT):
yea.. the node one it is there too
jwagantall (Tue, 06 Nov 2018 01:33:42 GMT):
looks like for some reason Node JS 1.2.7 is installed in prod but the pipeline plugin in not..
jwagantall (Tue, 06 Nov 2018 01:33:53 GMT):
I can re-adjust prod once sandbox is tested
awes0menessInc (Tue, 06 Nov 2018 03:35:57 GMT):
Has joined the channel.
rameshthoomu (Tue, 06 Nov 2018 03:59:12 GMT):
@dthom for some reason, cleanup script in s390x build nodes is not deleting workspace.. for now, I have manually deleted all the repos under workspace and deleted all the leftover docker images from all s390x build nodes..
rameshthoomu (Tue, 06 Nov 2018 03:59:52 GMT):
I would like to discuss the way we are cleaning up the leftover build artifacts from s390x build nodes.. ping me when you are available
smpakes (Tue, 06 Nov 2018 19:52:04 GMT):
Has joined the channel.
enriquebusti (Wed, 07 Nov 2018 12:01:00 GMT):
Has joined the channel.
rameshthoomu (Wed, 07 Nov 2018 16:33:32 GMT):
@dave.enyeart https://gerrit.hyperledger.org/r/#/c/27379/ need one more +2 on this
jtclark (Wed, 07 Nov 2018 21:58:16 GMT):
@latitiah I'm going to see if I can compile a list of all the images and binaries we need tagged with :latest.
jtclark (Wed, 07 Nov 2018 21:58:44 GMT):
should we do it like we were doing before? analyzing the nightly job output?
latitiah (Wed, 07 Nov 2018 21:59:18 GMT):
I have a list of what we need. I posted it earlier... Let me find it...
jtclark (Wed, 07 Nov 2018 22:02:21 GMT):
ok thanks
jtclark (Wed, 07 Nov 2018 22:02:37 GMT):
we'll start off by tagging those manually
jtclark (Wed, 07 Nov 2018 22:02:49 GMT):
then we'll work on the automation for de-associate/associate
latitiah (Wed, 07 Nov 2018 22:03:25 GMT):
fabric-peer, fabric-orderer, fabric-ca-peer, fabric-ca-orderer, cryptogen, configtxen, configtxlator, idemixgen,
fabric-javaenv, fabric-ca, fabric-baseimage, fabric-ccenv, fabric-couchdb, fabric-kafka, fabric-zookeeper, fabric-tools
latitiah (Wed, 07 Nov 2018 22:03:31 GMT):
Sounds good
rameshthoomu (Wed, 07 Nov 2018 22:04:10 GMT):
@jtclark are you coming to RTP tomorrow..
jtclark (Wed, 07 Nov 2018 22:04:15 GMT):
yes
rameshthoomu (Wed, 07 Nov 2018 22:04:18 GMT):
nice
jtclark (Wed, 07 Nov 2018 22:04:21 GMT):
I'll be in.
jtclark (Wed, 07 Nov 2018 22:04:47 GMT):
Tuesday was election day, and kids were on a 2-hour delay, which is why I wasn't there yesterday.
jtclark (Wed, 07 Nov 2018 22:04:57 GMT):
but yes, I'll be in tmrw.
rickr (Thu, 08 Nov 2018 18:03:52 GMT):
@jtclark Any update on upgrading Maven ?
rickr (Thu, 08 Nov 2018 18:03:52 GMT):
@tijohnson Any update on upgrading Maven ?
rameshthoomu (Thu, 08 Nov 2018 18:09:29 GMT):
@tijohnson ^^
rickr (Thu, 08 Nov 2018 18:10:20 GMT):
:) ^^^
tijohnson (Thu, 08 Nov 2018 23:01:53 GMT):
Yes, I have learned a GR8 deal today about this issue
tijohnson (Thu, 08 Nov 2018 23:19:10 GMT):
More info coming. I will update the ticket IN-39
SamRasha (Fri, 09 Nov 2018 14:16:33 GMT):
Has joined the channel.
tijohnson (Fri, 09 Nov 2018 17:48:10 GMT):
@rickr what are using for dev system (disto, memory/swap)
rickr (Fri, 09 Nov 2018 18:07:24 GMT):
fedora 32GB/32BG
rickr (Fri, 09 Nov 2018 18:09:23 GMT):
I've heard of no issues of anyone else building the JSDK so I'm guessing it's being built on quite a few different os platforms with different memory sizes
rickr (Fri, 09 Nov 2018 18:14:59 GMT):
BTW just be sure you don't grab temporary workaround to stop forking. Given the build works then I'm _slightly_ doubtful_ it's the the Maven version. *Irregardless that needs updating too.*
rickr (Fri, 09 Nov 2018 18:14:59 GMT):
BTW just be sure you don't grab temporary workaround to stop forking. Given the build works then I'm _slightly doubtful_ it's the the Maven version. *Irregardless that needs updating too.*
jwagantall (Fri, 09 Nov 2018 19:03:32 GMT):
@here Heads up, we will pause Jenkins in 45 mins to upgrade it to the latest LTS and upgrade the OpenStack plugin. The current API being used it will deprecate soon and we need to upgrade. Thanks! This should take about 30 mins
jwagantall (Fri, 09 Nov 2018 20:20:14 GMT):
@here Jenkins upgrade is now completed.. Thanks!
MHBauer (Fri, 09 Nov 2018 23:10:19 GMT):
yay
rameshthoomu (Sat, 10 Nov 2018 13:42:48 GMT):
@swetha finally got +1 https://gerrit.hyperledger.org/r/#/c/26824/ :woo:
raccoonrat (Mon, 12 Nov 2018 07:56:54 GMT):
Has joined the channel.
rameshthoomu (Mon, 12 Nov 2018 13:35:22 GMT):
@vijay.bP @sambhavdutt this will fix the release-1.2 build failure (fabric-end-2-end-daily-release-1.2-x86_64) https://gerrit.hyperledger.org/r/#/c/27506/
rameshthoomu (Mon, 12 Nov 2018 13:40:38 GMT):
FAB-12819 release-1.2 integration test failure (fabric-nightly-release-job-release-1.2-x86_64)
rameshthoomu (Mon, 12 Nov 2018 13:41:44 GMT):
@sambhavdutt or @vijay.bP Did you create bug for this https://jenkins.hyperledger.org/view/Daily/job/fabric-unit-test-coverage-daily-master-x86_64/261/consoleFull failure
rameshthoomu (Mon, 12 Nov 2018 13:41:44 GMT):
@sambhavdutt or @vijay.bP do we have bug for this https://jenkins.hyperledger.org/view/Daily/job/fabric-unit-test-coverage-daily-master-x86_64/261/consoleFull failure
jtclark (Mon, 12 Nov 2018 13:41:57 GMT):
Morning :sunrise:
jtclark (Mon, 12 Nov 2018 13:42:49 GMT):
@rameshthoomu, @vijay.bP, @sambhavdutt - I've been getting emails for build failures too
jtclark (Mon, 12 Nov 2018 13:43:01 GMT):
quite a few. is there something not configured right?
jtclark (Mon, 12 Nov 2018 13:43:38 GMT):
@tijohnson do you have an update re: nexus tagging?
rameshthoomu (Mon, 12 Nov 2018 13:44:21 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=qGferdZDTmuG58KbJ) @jtclark Gm.. Push this discussion to #ci-pipeline
sambhavdutt (Mon, 12 Nov 2018 13:44:32 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=TjtL5jLzvGemtsjqx) @rameshthoomu @rameshthoomu
Will do
jtclark (Mon, 12 Nov 2018 13:44:45 GMT):
@rameshthoomu will do.
maozhuzi (Mon, 12 Nov 2018 13:47:14 GMT):
Has joined the channel.
vijay.bP (Mon, 12 Nov 2018 13:53:02 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=TjtL5jLzvGemtsjqx) @rameshthoomu JIRA number for the above error FAB-12823
rameshthoomu (Mon, 12 Nov 2018 14:04:36 GMT):
@vijay.bP Do we have bug for this https://jenkins.hyperledger.org/view/fabric/job/fabric-merge-x86_64/4944/consoleFull
vijay.bP (Mon, 12 Nov 2018 14:08:08 GMT):
@rameshthoomu Let me check and update the status for the ^^job
jtclark (Mon, 12 Nov 2018 16:10:41 GMT):
@vijay.bP updated my comment on: https://gerrit.hyperledger.org/r/#/c/27511/
swetha (Mon, 12 Nov 2018 17:13:35 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=bWKjnkpEZMZJouc4F) @rameshthoomu Thank you! :woo:
rameshthoomu (Mon, 12 Nov 2018 19:52:34 GMT):
@nkl199 Please check this FAB-12831
tsnyder (Tue, 13 Nov 2018 03:20:50 GMT):
Questions on Fabric CA - I recall some discussions pre 1.0 where intermediary certs could be used for channel user authorizations and any user cert created from them would be authorized for the channel per the authorizations associated with the intermediary cert. Is this the case? If so, does this extend to any Roles and Attributes associated with the intermediary cert, or constrain the certs generated from the intermediary cert?
tsnyder (Tue, 13 Nov 2018 03:21:51 GMT):
Note - I asked this question in the fabric-questions channel but got no responses
rameshthoomu (Tue, 13 Nov 2018 12:59:22 GMT):
Historyleveldb unit-test case is failed FAB-12838
jtclark (Tue, 13 Nov 2018 15:06:12 GMT):
@rameshthoomu here in the lab - where is everyone?
rameshthoomu (Tue, 13 Nov 2018 15:07:07 GMT):
We are near to the conference room
rameshthoomu (Tue, 13 Nov 2018 15:07:30 GMT):
come out from lab.. Sambhav will take you here..
jtclark (Tue, 13 Nov 2018 15:07:32 GMT):
did you move?
jtclark (Tue, 13 Nov 2018 15:07:40 GMT):
ok
rameshthoomu (Tue, 13 Nov 2018 15:21:41 GMT):
@mbwhite Could you please check this https://jira.hyperledger.org/browse/FAB-12831
mbwhite (Tue, 13 Nov 2018 15:41:43 GMT):
@rameshthoomu we've seen this a few times... not sure why.. I'm a little worried it's connected somehow to statebased endorsement
rameshthoomu (Tue, 13 Nov 2018 15:43:47 GMT):
Observed root permissions are settingup after execute this step `DEVMODE=false gulp channel-init`
rameshthoomu (Tue, 13 Nov 2018 15:44:15 GMT):
```
10:07:44 [15:07:44] Finished 'channel-init' after 2.87 s
10:07:44 #################################################################
10:07:44 ------> Run Integration and Scenario Tests
10:07:44 #################################################################
10:07:44 total 4
10:07:44 drwxr-xr-x 3 root root 4096 Nov 13 15:07 peer
10:07:44 total 4
10:07:44 drwxr-xr-x 3 root root 4096 Nov 13 15:07 fabric
```
rickr (Tue, 13 Nov 2018 16:18:26 GMT):
@tijohnson @rameshthoomu I was able to reproduce the Java build with forking issue on a Ubuntu machine. I updated to the latest maven 3.6.0 and it continued to fail.
I also got the memory increased (16G) with still the same failing results. I also upgraded to the latest plugin version still failed. Finally I download and used the latest Oracle jdk and that worked.
I read where this was a bug in open-jdk so I'm pretty sure that the root of this.
rickr (Tue, 13 Nov 2018 16:27:42 GMT):
I think the first step is to see how we can get an older verison of the open jdk installed that does not experience this problem. Not sure off the bat how to do that.
rickr (Tue, 13 Nov 2018 16:53:19 GMT):
@tijohnson Please don't stop getting Maven upgraded even though I'm fairly certain it's not going to fix this issue.
tijohnson (Tue, 13 Nov 2018 18:01:49 GMT):
In complete agreement, I will work toward a process that can deployed. Duplicating this problem on Ubuntu is a GR8 idea
rickr (Tue, 13 Nov 2018 18:02:55 GMT):
I was able to try a back level open jdk and it seems to work
```
322 apt-get --purge remove openjdk-8-jdk-headless openjdk-8-jre-headless
325 apt-get install openjdk-8-jre-headless=8u77-b03-3ubuntu3
326 apt-get install openjdk-8-jdk-headless=8u77-b03-3ubuntu3
328 apt-get install maven
```
tijohnson (Tue, 13 Nov 2018 18:04:32 GMT):
Let me try that, I have a big meeting in 30min (talking about this issue and the Nexus Tagging issue), so it will be a couple of hours
rameshthoomu (Tue, 13 Nov 2018 18:05:45 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=cJoLBiGQC9RwbHQh5) @tijohnson Tim, Is this with CI team or LF team?
tijohnson (Tue, 13 Nov 2018 18:06:18 GMT):
LF Team
rameshthoomu (Tue, 13 Nov 2018 18:07:10 GMT):
ok before that, do you have few mins to disucss on couple of things on nexus tagging
rameshthoomu (Tue, 13 Nov 2018 18:07:12 GMT):
https://zoom.us/j/489881635
rameshthoomu (Tue, 13 Nov 2018 18:07:14 GMT):
pls join here
rameshthoomu (Wed, 14 Nov 2018 14:24:50 GMT):
@dthom any update on softhsm issue? FAB-12670
rameshthoomu (Wed, 14 Nov 2018 14:31:01 GMT):
@bretharrison FABN-1016 Update the "tag" value in all the release branches..
rameshthoomu (Wed, 14 Nov 2018 14:40:49 GMT):
@rickr I think we have to apply this patch in all the branches to resume to broken builds.. https://gerrit.hyperledger.org/r/#/c/27506/
rameshthoomu (Wed, 14 Nov 2018 14:41:33 GMT):
I know that is just a workaround but this will fix the broken builds
rickr (Wed, 14 Nov 2018 15:01:37 GMT):
@rameshthoomu @tijohnson I think we now know what the issue is. I provided what I seen worked for me that lets forking working and should keep Jacoco running. Let pursue getting that done than perpetuating a hack.
tijohnson (Wed, 14 Nov 2018 18:11:17 GMT):
@rickr I must have missed something here. I don't know 'what the issue is'.
tijohnson (Wed, 14 Nov 2018 18:30:09 GMT):
@ramesh do you know what rickr is talking about ? He mentions something about a specific version of 'open-jdk-8' it is with maven 3.3 or 3.5 ?
tijohnson (Wed, 14 Nov 2018 18:30:09 GMT):
@rameshthoomu do you know what rickr is talking about ? He mentions something about a specific version of 'open-jdk-8' it is with maven 3.3 or 3.5 ?
tijohnson (Wed, 14 Nov 2018 18:51:12 GMT):
@rameshthoomu @rickr I have to leave early today. I will be back on-line first thing tomorrow
rameshthoomu (Wed, 14 Nov 2018 19:47:36 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=wtNdwzmx87TG7xTBw) @tijohnson Please see his above messages..
vijay.bP (Thu, 15 Nov 2018 14:28:19 GMT):
@bretharrison Can you please look into this bug FABN-1021
Merge jobs are failing on master branch
vijay.bP (Thu, 15 Nov 2018 14:28:19 GMT):
@bretharrison Can you please look this into this bug FABN-1021
Merge jobs are failing on master branch
tijohnson (Thu, 15 Nov 2018 14:57:24 GMT):
@rickr @rameshthoomu 27506 just disables 'pipelines' on some more branches
I am also working on 'real' fix which is maven 3.5 & with specific versions of 'open-jdk-8'
I will be looking into installing 'open-jdk-8' today, I already know it is NOT as simple as running 'apt' in a build script
awjh (Thu, 15 Nov 2018 15:13:27 GMT):
Has joined the channel.
awjh (Thu, 15 Nov 2018 15:13:47 GMT):
I can't get any build logs from failing builds at the minute?
awjh (Thu, 15 Nov 2018 15:13:56 GMT):
This is on fabric-chaincode-node
mbwhite (Thu, 15 Nov 2018 15:18:34 GMT):
chaincode-node failing with Error: failed to import '/w/workspace/fabric-chaincode-node-verify-x86_64/gopath/src/github.com/hyperledger/fabric-chaincode-node/fabric-shim/lib/protos/token/expectations.proto' in 'peer/proposal.proto': file not found
mbwhite (Thu, 15 Nov 2018 15:18:52 GMT):
can anybody shed light on what proto definition this is?
dave.enyeart (Thu, 15 Nov 2018 15:25:15 GMT):
@mbwhite @bretharrison looks like that proto was added yesterday to fabric: https://gerrit.hyperledger.org/r/#/c/27460/. I guess sdk needs to add it.
mbwhite (Thu, 15 Nov 2018 15:32:43 GMT):
@adc I believe this is a change related to FAB 12788
dave.enyeart (Thu, 15 Nov 2018 15:44:58 GMT):
@bretharrison @rickr How have proto updates been handled in the past? First it is merged to fabric, temporarily breaks the SDKs, and then the SDKs have to quickly sync the protos? Is there anything that can be done to improve it beyond quick coordination?
rickr (Thu, 15 Nov 2018 15:53:23 GMT):
No we have a copy of the protos. It's a manual sync. The proto's need to be kept backward compatible. Given that there should be no breakage.
bretharrison (Thu, 15 Nov 2018 15:56:13 GMT):
Adding new protos is not supposed to break the SDK's, what is broken ?
dave.enyeart (Thu, 15 Nov 2018 15:57:57 GMT):
Ah right, I was thinking of a scenario in past dev where we all agreed to change a contract. for normal additions there should be no breakage
rickr (Thu, 15 Nov 2018 16:03:10 GMT):
@tijohnson I don't think you can run any sudo needed commands .. I doubt that privilege would or should be given. If it really was that _simple_ the issue would now be closed. I gave you those commandsto help you know this appeared to fix the issue for me locally and what JDK version worked. I suspect you need to run those commands or something similar and then create a VM image of that which would get reused.
tijohnson (Thu, 15 Nov 2018 16:05:19 GMT):
I am able to run sudo, the problem is a bug in Ubuntu the prevents me from running apt
tijohnson (Thu, 15 Nov 2018 16:05:19 GMT):
I am able to run sudo, the problem is a bug in Ubuntu that prevents me from running apt
tijohnson (Thu, 15 Nov 2018 16:05:58 GMT):
Which means we have to make the changes to the original image
tijohnson (Thu, 15 Nov 2018 16:05:58 GMT):
Which means we have to make the changes to the original image @rickr
tijohnson (Thu, 15 Nov 2018 16:12:52 GMT):
If we are going to do that, maybe we should just add maven 3.5 to the base image also
rickr (Thu, 15 Nov 2018 16:14:41 GMT):
I thought that was the plan. Why would we want that overhead on each build.
tijohnson (Thu, 15 Nov 2018 16:19:25 GMT):
Updating the base is cumbersome and we don't want to do it until we are sure we have all the correct pieces and the changes are compatible with all the build that use it
tijohnson (Thu, 15 Nov 2018 16:19:25 GMT):
Updating the base image is cumbersome and we don't want to do it until we are sure we have all the correct pieces and the changes are compatible with all the build that use it
rickr (Thu, 15 Nov 2018 16:21:21 GMT):
Ok that's part of testing. Production should have all prerequisites present.
tijohnson (Thu, 15 Nov 2018 17:01:07 GMT):
@rickr @rameshthoomu Which images need maven 3.5 ? I know 'snd-ubuntu1604-x86_64-4c-16g'. Is that only one or do we need it in
'snd-ubuntu1604-test-common-packer-x86_64-4c-16g' & 'snd-ubuntu1604-indy-x86_64-4c-16g' ?
rameshthoomu (Thu, 15 Nov 2018 18:15:27 GMT):
we need it in snd-ubuntu1604-x86_64-4c-16g'
rameshthoomu (Thu, 15 Nov 2018 18:15:36 GMT):
I am not sure about other two images..
rameshthoomu (Thu, 15 Nov 2018 18:15:54 GMT):
you can always keep this in sandbox before rollout to production
sstone1 (Fri, 16 Nov 2018 10:43:09 GMT):
@rameshthoomu is anybody looking at the fabric-sdk-node merge build failures?
sstone1 (Fri, 16 Nov 2018 10:43:21 GMT):
i see the following error in the latest log:
```
18:34:29 npm ERR! publish Failed PUT 403
18:34:29 npm ERR! code E403
18:34:29 npm ERR! You do not have permission to publish "fabric-ca-client". Are you logged in as the correct user? : fabric-ca-client
18:34:29
18:34:29 npm ERR! A complete log of this run can be found in:
18:34:29 npm ERR! /home/jenkins/.npm/_logs/2018-11-15T18_34_28_966Z-debug.log
```
mbwhite (Fri, 16 Nov 2018 11:25:06 GMT):
The chaincode zOS builds have also failed now when trying to clone from gerrit
```
11:14:54 + git clone --single-branch -b master git://cloud.hyperledger.org/mirror/fabric
11:14:54 Cloning into 'fabric'...
11:15:03 fatal: read error: Connection reset by peer
11:15:03 fatal: early EOF
11:15:03 fatal: index-pack failed
```
14gracel (Fri, 16 Nov 2018 11:35:23 GMT):
peer logs
rameshthoomu (Fri, 16 Nov 2018 12:50:20 GMT):
Yes .. didn’t change credentials of NPM Token.. not sure what’s wrong here.. will let you know.. @sstone1 [ ](https://chat.hyperledger.org/channel/fabric-ci?msg=iiLkgGSwimgK4C3hD)
rameshthoomu (Fri, 16 Nov 2018 13:13:49 GMT):
Checked little deeper into this.. It's not about the credentials.. I see the steps Unstable Increment version is not fetching the right version..
```
06:32:15 ===> UNSTABLE VERSION --> 1.2.0-snapshot
06:32:16 -------->* UNSTABLE_INCREMENT_VERSION 1.2.3-snapshot.1.2.0-snapshot.81*
06:32:18 npm ERR! publish Failed PUT 403
```
rameshthoomu (Fri, 16 Nov 2018 13:16:16 GMT):
Current Version and unstable version is not matching
```
06:32:09 [32m ===> Current Version --> 1.2.3-snapshot [0m
06:32:09
06:32:15 ===> UNSTABLE VERSION --> 1.2.0-snapshot
I will check with @bretharrison in office
```
rameshthoomu (Fri, 16 Nov 2018 13:16:16 GMT):
Current Version and unstable version is not matching
```
06:32:09 [32m ===> Current Version --> 1.2.3-snapshot [0m
06:32:09
06:32:15 ===> UNSTABLE VERSION --> 1.2.0-snapshot
```
I will check with @bretharrison in office
sstone1 (Fri, 16 Nov 2018 13:44:21 GMT):
thanks ramesh!
awjh (Fri, 16 Nov 2018 14:49:34 GMT):
I'm unable to get jenkins.hyperledger.org to load, just hangs anyone else getting this?
awjh (Fri, 16 Nov 2018 14:50:27 GMT):
Means that builds in chaincode-node aren't running when patches pushed (and I assume elsewhere)
sambhavdutt (Fri, 16 Nov 2018 14:55:50 GMT):
We are not able to login too, 504 Gateway error there is a Hyperledger ticket created for this
sambhavdutt (Fri, 16 Nov 2018 14:56:10 GMT):
@awjh
awjh (Fri, 16 Nov 2018 14:56:32 GMT):
:+1:
sambhavdutt (Fri, 16 Nov 2018 14:59:41 GMT):
*[Hyperledger Helpdesk #63804]*
rameshthoomu (Fri, 16 Nov 2018 16:25:26 GMT):
@tijohnson @jwagantall any update on the Helpdesk #63804.. We are unable to access Jenkins page..
rameshthoomu (Fri, 16 Nov 2018 16:55:19 GMT):
https://status.linuxfoundation.org/
tijohnson (Fri, 16 Nov 2018 17:27:45 GMT):
@all Things are coming back on-line
tijohnson (Fri, 16 Nov 2018 17:44:46 GMT):
@all We are currently aware of additions network issues affecting the CI systems. The issue is being worked currently but we do not have an ETA on resolution.
I will update again when systems are 100% operational.
tijohnson (Fri, 16 Nov 2018 17:44:46 GMT):
@all We are currently aware of additional network issues affecting the CI systems. The issue is being worked currently but we do not have an ETA on resolution.
I will update again when systems are 100% operational.
BellaAdams (Sat, 17 Nov 2018 00:45:42 GMT):
Has joined the channel.
rameshthoomu (Sat, 17 Nov 2018 04:47:24 GMT):
@skarim https://jira.hyperledger.org/browse/FAB-12907
rameshthoomu (Sat, 17 Nov 2018 04:47:45 GMT):
make dist-all is failing to build windows binary.. this seems caused with this patch https://gerrit.hyperledger.org/r/#/c/27452/
rameshthoomu (Mon, 19 Nov 2018 14:31:44 GMT):
@skarim Any update on the above failure? @dave.enyeart FYI
skarim (Mon, 19 Nov 2018 14:38:58 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=Zr62Kxu9wWEys4hfD) @rameshthoomu I'll look into it today
rameshthoomu (Mon, 19 Nov 2018 14:39:08 GMT):
thank you
rameshthoomu (Mon, 19 Nov 2018 15:13:06 GMT):
@dthom Connection reset failure only on fabric repository
```
10:09:08 + git clone --single-branch -b master git://cloud.hyperledger.org/mirror/fabric
10:09:08 Cloning into 'fabric'...
10:09:21 fatal: read error: Connection reset by peer
10:09:21 fatal: early EOF
10:09:21 fatal: index-pack failed
```
vijay.bP (Mon, 19 Nov 2018 15:44:19 GMT):
@rameshthoomu @dthom Jira number for the connection reset failure on fabric repository error [FAB-12927]
nyet (Mon, 19 Nov 2018 17:03:09 GMT):
Has joined the channel.
nyet (Mon, 19 Nov 2018 17:03:50 GMT):
Is there a sandbox place to put test merges for submission to jenkins? I'd like to do a couple reverify-z with a temp change to test a patch on z.
i dont want to clutter jenkins with a `git review
nyet (Mon, 19 Nov 2018 17:03:50 GMT):
Is there a sandbox place to put test merges for submission to jenkins? I'd like to do a couple reverify-z with a temp change to test a patch on z.
i dont want to clutter jenkins with a `git review`
rameshthoomu (Mon, 19 Nov 2018 17:06:54 GMT):
yes, please follow this https://github.com/hyperledger/ci-management/blob/master/Sandbox_Setup.md
Baha-sk (Mon, 19 Nov 2018 17:24:16 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=TPQba3SJsa4M6DNSK) @rameshthoomu @nyet --- thanks @rameshthoomu
sambhavdutt (Mon, 19 Nov 2018 21:04:47 GMT):
@harrijk @dthom
Can you take a look at this
https://jira.hyperledger.org/browse/FAB-12921
jtclark (Mon, 19 Nov 2018 21:28:25 GMT):
still looking for a review on: https://gerrit.hyperledger.org/r/#/c/27511/
vijay.bP (Tue, 20 Nov 2018 16:15:58 GMT):
@rameshthoomu @jtclark Please look into this patch https://gerrit.hyperledger.org/r/#/c/27663/ to revert changes on curl command
jtclark (Tue, 20 Nov 2018 16:21:05 GMT):
@vijay.bP commented
scottz (Tue, 20 Nov 2018 16:58:48 GMT):
@sambhavdutt @rameshthoomu for the `make dist-all` problem that was causing build failures for days, a fix for https://jira.hyperledger.org/browse/FAB-12907 was submitted and this Bug closed yesterday. Is this required to pass to trigger the "downstream jobs" for fabric-test daily jobs? https://jenkins.hyperledger.org/view/fabric-test/job/fabric-test-daily-results-master-x86_64/test_results_analyzer/ shows that the fabric-test daily jobs did run, except for the behave tests that have NO results for the past 5 days. I am trying to find a bug for the "no results" for the behave tests.
scottz (Tue, 20 Nov 2018 17:01:38 GMT):
was that 12907 blocking the daily behave tests (which use x86)? that one is a windows problem, so I don't see why, so maybe we can tweak the job.
Also I am confused why the other daily tests ran ok, but not the behave tests. can you explain why?
rameshthoomu (Tue, 20 Nov 2018 17:10:45 GMT):
@scottz give me few mins.. Will let you know
rameshthoomu (Tue, 20 Nov 2018 22:08:39 GMT):
CI Team: FYI https://gerrit.hyperledger.org/r/#/c/27491/
dave.enyeart (Sun, 25 Nov 2018 16:03:23 GMT):
Anybody have ideas on this failure?
dave.enyeart (Sun, 25 Nov 2018 16:03:24 GMT):
https://jenkins.hyperledger.org/job/fabric-verify-unit-tests-x86_64/6439/console
dave.enyeart (Sun, 25 Nov 2018 16:03:33 GMT):
```15:35:55 unit-tests_1 | --- FAIL: TestDockerPull (0.18s)
15:35:55 unit-tests_1 | utils_test.go:371: Error during build: Failed to pull hyperledger/fabric-ccenv:x86_64-1.0.0-alpha2: API error (500): {"message":"unauthorized: authentication required"}```
rameshthoomu (Mon, 26 Nov 2018 04:39:15 GMT):
@harrijk still getting fabric clone issue on release-1.0 branch https://jenkins.hyperledger.org/view/Daily/job/fabric-end-2-end-daily-release-1.0-s390x/configure
rameshthoomu (Mon, 26 Nov 2018 04:39:20 GMT):
will check this tomororw
rameshthoomu (Mon, 26 Nov 2018 06:33:29 GMT):
@dave.enyeart it failed to pull the docker image.. Could be network glitch.. Re-triggered again..
sambhavdutt (Mon, 26 Nov 2018 17:37:51 GMT):
@tijohnson
https://jira.hyperledger.org/browse/IN-39
The sdk-java jobs still fail as the maven plugin is not resolved yet, so we have removed the `sdk-java` tests temporarily, Can you give an update on this
vijay.bP (Thu, 29 Nov 2018 14:19:27 GMT):
@ashutosh_kumar Please check with @mbwhite for FAB-12808
sambhavdutt (Thu, 29 Nov 2018 14:51:42 GMT):
@dave.enyeart
Can we add a new job-status field for Bugs in JIRA with tags like `first-time` , `failed-twice` , `Intermittent` , `Consistent` , if this is helpful.
dave.enyeart (Thu, 29 Nov 2018 20:48:56 GMT):
@sambhavdutt I recommend to use 'labels'. we already have a label `flake` that we use for flakey test failures. i would certainly recommend using `first-time`, `intermittent`, and `consistent` in addition to the `flake` label.
sambhavdutt (Thu, 29 Nov 2018 20:52:05 GMT):
@dave.enyeart
thank you , I will use the `flake` label for the test fails appropriately.
dave.enyeart (Thu, 29 Nov 2018 20:54:45 GMT):
go ahead and use `first-time`, `intermittent`, and `consistent` as well. if it doesn't let you use those labels let me know, i may have to create them in advance.
dave.enyeart (Thu, 29 Nov 2018 20:55:41 GMT):
and in general would make sense to set priority as Low/Medium/High respectively
nyet (Fri, 30 Nov 2018 01:04:25 GMT):
Has left the channel.
sambhavdutt (Fri, 30 Nov 2018 01:35:50 GMT):
@dave.enyeart
thank you
knagware9 (Fri, 30 Nov 2018 07:24:55 GMT):
Has joined the channel.
ks2117 (Sat, 01 Dec 2018 18:21:47 GMT):
Has joined the channel.
cn-ygf (Mon, 03 Dec 2018 06:25:56 GMT):
Has joined the channel.
cn-ygf (Mon, 03 Dec 2018 06:26:14 GMT):
Has left the channel.
sambhavdutt (Mon, 03 Dec 2018 16:19:45 GMT):
There is one Bug for the Integration tests fail today , Master branch. This is a one time fail and in the nightly job yesterday, not in the current verify integration tests,
https://jira.hyperledger.org/browse/FAB-13137
rameshthoomu (Mon, 03 Dec 2018 16:30:51 GMT):
@sambhavdutt @bretharrison @mbwhite I see sdk-node and chaincode-node merge jobs are failing.. Could you please check what went wrong..
rameshthoomu (Mon, 03 Dec 2018 16:31:00 GMT):
See the #jenkins-robot channel for the failures
sambhavdutt (Mon, 03 Dec 2018 16:32:17 GMT):
@rameshthoomu
I will check
jtclark (Mon, 03 Dec 2018 16:41:50 GMT):
@rameshthoomu yes, those were false positives. it has ran twice now successfully: https://jenkins.hyperledger.org/sandbox/job/fabric-docs-build-x86_64/
bretharrison (Mon, 03 Dec 2018 16:59:01 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=kqrQPkiRDpdXBofwi) @rameshthoomu Getting that same intermittent logging error, how do I kick off the merge job again ... i tried `remerge`
sambhavdutt (Mon, 03 Dec 2018 16:59:44 GMT):
@rameshthoomu I have created a Bug for this issue , https://jira.hyperledger.org/browse/FABN-1047
sambhavdutt (Mon, 03 Dec 2018 17:06:18 GMT):
@bretharrison
yes, it is `remerge` to trigger the merge jobs,
sambhavdutt (Mon, 03 Dec 2018 17:06:42 GMT):
Let me try once too
sambhavdutt (Mon, 03 Dec 2018 17:09:08 GMT):
It will be triggered in a while, I see this job waiting in jenkins job queue
bretharrison (Mon, 03 Dec 2018 17:23:59 GMT):
oh OK, thanks
rickr (Mon, 03 Dec 2018 20:18:18 GMT):
@rameshthoomu trying to get this re run --> https://gerrit.hyperledger.org/r/#/c/27308/
sambhavdutt (Mon, 03 Dec 2018 20:21:16 GMT):
I have retriggered them now
sambhavdutt (Mon, 03 Dec 2018 20:22:43 GMT):
can see them in job queue
sambhavdutt (Mon, 03 Dec 2018 20:22:49 GMT):
@rickr
rickr (Mon, 03 Dec 2018 20:23:36 GMT):
k thx -- wonder why that does not work for me :(
sambhavdutt (Mon, 03 Dec 2018 20:24:47 GMT):
it's happening today, just some glitch
sambhavdutt (Mon, 03 Dec 2018 20:25:26 GMT):
this wont be a long standing problem
rameshthoomu (Tue, 04 Dec 2018 14:42:12 GMT):
@mbwhite Could you please check this failure https://gerrit.hyperledger.org/r/#/c/27901/
rameshthoomu (Tue, 04 Dec 2018 17:18:22 GMT):
@sambhavdutt any blockers from CI for 1.4 release?
rameshthoomu (Tue, 04 Dec 2018 17:18:42 GMT):
Could you please check the open bugs.. Will discuss post lunch
vijay.bP (Tue, 04 Dec 2018 17:18:51 GMT):
@rameshthoomu I'm checking
rameshthoomu (Tue, 04 Dec 2018 17:18:58 GMT):
ok
sambhavdutt (Tue, 04 Dec 2018 17:25:02 GMT):
@rameshthoomu will let you know in a while
rameshthoomu (Tue, 04 Dec 2018 17:25:17 GMT):
Both are working?
vijay.bP (Tue, 04 Dec 2018 17:27:33 GMT):
@rameshthoomu I'm checking release jobs and sambhav checking open bugs.
rameshthoomu (Tue, 04 Dec 2018 17:28:11 GMT):
ok thanks
rameshthoomu (Tue, 04 Dec 2018 18:26:31 GMT):
@skarim could you please check this https://jira.hyperledger.org/browse/FABC-767
skarim (Tue, 04 Dec 2018 18:27:08 GMT):
yup
sambhavdutt (Tue, 04 Dec 2018 19:04:45 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=zWjq6r3pZuZpXkLG2) @rameshthoomu I can see 3 high priority Bugs for 1.4, these are being worked on. I'll inform if any high priority bugs are created by someone or me
https://jira.hyperledger.org/browse/FAB-13022 (Behave, daily fabric-ca Service test)
https://jira.hyperledger.org/browse/FAB-13085 (Behave daily orderer test)
https://jira.hyperledger.org/browse/FAB-13160 (LTE daily)
jtclark (Tue, 04 Dec 2018 19:07:28 GMT):
@rameshthoomu when you get a sec, need to chat with you about the latest docker images that were published to nexus
rameshthoomu (Tue, 04 Dec 2018 19:18:42 GMT):
Yes pls
jtclark (Tue, 04 Dec 2018 19:19:23 GMT):
@rameshthoomu can you tell us how the docker images were published? were they published by manually running a nightly job, and when did that last occur?
jtclark (Tue, 04 Dec 2018 19:19:46 GMT):
specifically the amd64-latest docker images
rameshthoomu (Tue, 04 Dec 2018 19:22:15 GMT):
from nightly job..
jtclark (Tue, 04 Dec 2018 19:24:52 GMT):
how long ago?
jtclark (Tue, 04 Dec 2018 19:29:00 GMT):
@rameshthoomu :point_up_tone2:
rameshthoomu (Tue, 04 Dec 2018 19:29:11 GMT):
yesterday night
rameshthoomu (Tue, 04 Dec 2018 19:29:21 GMT):
check the job..
jtclark (Tue, 04 Dec 2018 19:29:24 GMT):
hmmmm
jtclark (Tue, 04 Dec 2018 19:29:25 GMT):
ok
jtclark (Tue, 04 Dec 2018 19:29:58 GMT):
what @latitiah and I saw earlier (hence the Slack ping last night) was that the image tagged latest wasn't actually the latest one
jtclark (Tue, 04 Dec 2018 19:30:17 GMT):
I'll check
rameshthoomu (Tue, 04 Dec 2018 19:31:01 GMT):
ok
jtclark (Tue, 04 Dec 2018 19:34:11 GMT):
@rameshthoomu one more thing
jtclark (Tue, 04 Dec 2018 19:35:31 GMT):
@latitiah also needs the $GIT_COMMIT in the names of the artifacts. my understanding is that the can use it to check and ENSURE that the artifacts are indeed the latest
jtclark (Tue, 04 Dec 2018 19:35:31 GMT):
@latitiah also needs the $GIT_COMMIT in the names of the artifacts. my understanding is that they can use it to check and ENSURE that the artifacts are indeed the latest
rameshthoomu (Tue, 04 Dec 2018 19:36:25 GMT):
sure will check
jtclark (Tue, 04 Dec 2018 19:36:32 GMT):
I'm thinking that the change we just made: https://github.com/hyperledger/ci-management/blob/d6a0717af8de91385a20847b8464a17d52a5f68d/jjb/fabric/fabric-macros.yaml#L665
jtclark (Tue, 04 Dec 2018 19:36:42 GMT):
we should modify this to say:
jtclark (Tue, 04 Dec 2018 19:37:05 GMT):
`-Dversion=$binary.$PROJECT_VERSION-$COMMIT-SNAPSHOT`
jtclark (Tue, 04 Dec 2018 19:37:37 GMT):
this way each artifact will have the $COMMIT in the name too.
jtclark (Tue, 04 Dec 2018 19:38:02 GMT):
@rameshthoomu :point_up_tone2:
jtclark (Tue, 04 Dec 2018 19:38:58 GMT):
I've got a patch set ready for that, if you find that this should be done.
rameshthoomu (Tue, 04 Dec 2018 19:44:04 GMT):
@jtclark sure.. Before I merge this patch, please also write a script to pull the latest binaries with the above approach
jtclark (Tue, 04 Dec 2018 19:52:12 GMT):
@rameshthoomu https://nexus.hyperledger.org/#view-repositories;snapshots~browsestorage
jtclark (Tue, 04 Dec 2018 19:52:21 GMT):
this is where the binaries are, correct?
rameshthoomu (Tue, 04 Dec 2018 19:53:05 GMT):
Ok shall we push this discussion to #ci-pipeline
jtclark (Tue, 04 Dec 2018 19:53:16 GMT):
no prob.
sykesm (Tue, 04 Dec 2018 20:13:46 GMT):
Looks like we may broken PKCS#11 differently
```
./scripts/config_softhsm2.sh
Update SOFTHSM2_CONF via export SOFTHSM2_CONF=/Users/sykesm/lib/softhsm/softhsm2.conf
CKR_SLOT_ID_INVALID: Slot 0 does not exist.
make: *** [softhsm2_initialization] Error 1
```
sykesm (Tue, 04 Dec 2018 20:13:50 GMT):
it's like cat and mouse
sykesm (Tue, 04 Dec 2018 20:15:07 GMT):
That was local. In CI (not my CR) we get a different behavior:
```
00:27:21.343 ? github.com/hyperledger/fabric/bccsp/mocks [no test files]
00:27:21.343 Immutable = [false]Failed initiliazing BCCSP at [{SecLevel:256 HashFamily:SHA2 Ephemeral:false FileKeystore:
sykesm (Tue, 04 Dec 2018 20:16:57 GMT):
Sorry to be grumpy but we have yet again made assumptions.
rameshthoomu (Tue, 04 Dec 2018 20:17:45 GMT):
@sykesm could you please give the CR or build#
sykesm (Tue, 04 Dec 2018 20:17:59 GMT):
CR that breaks me is
commit af5e9f0192be0013e0202c463328e13b9886a7e0
Author: Krishna Harsha Voora
sykesm (Tue, 04 Dec 2018 20:18:08 GMT):
that's local (was a perfectly working environment)
sykesm (Tue, 04 Dec 2018 20:18:20 GMT):
CI build is https://jenkins.hyperledger.org/job/fabric-verify-unit-tests-x86_64/6787/console
sykesm (Tue, 04 Dec 2018 20:18:44 GMT):
putting a configuration file in *my home directory* is not okay with me.
sykesm (Tue, 04 Dec 2018 20:19:03 GMT):
```
+cd $HOME
+mkdir -p $HOME/lib/softhsm/tokens
+cd $HOME/lib/softhsm/
+echo "directories.tokendir = $PWD/tokens" > softhsm2.conf
+echo "Update SOFTHSM2_CONF via export SOFTHSM2_CONF=$HOME/lib/softhsm/softhsm2.conf"
```
sykesm (Tue, 04 Dec 2018 20:19:46 GMT):
this is like a previous project I was on where we were told to run our tests as root since that's how CI was run; it's the wrong model.
rameshthoomu (Tue, 04 Dec 2018 20:20:41 GMT):
the above CR parent commit is not on this fix.. this needs to be rebased
sykesm (Tue, 04 Dec 2018 20:20:58 GMT):
yes - there are two separate issues
sykesm (Tue, 04 Dec 2018 20:21:21 GMT):
the first is that my local dev environment is once again broken. This happens at least twice on ever release.
sykesm (Tue, 04 Dec 2018 20:21:59 GMT):
the second is that contributors (who don't know what's going on) get CI failures because we've changed the CI to run off of things that are not in the tree. This leaves a terrible taste in their mouths.
sykesm (Tue, 04 Dec 2018 20:22:40 GMT):
AFAICT, the CR that was merged is making a mess of things
rameshthoomu (Tue, 04 Dec 2018 20:23:22 GMT):
we have not changed the CI, fabric make file has been changed. We still run the `make unit-test`
rameshthoomu (Tue, 04 Dec 2018 20:23:44 GMT):
@harsha posted this in other channel
harsha 2:10 PM
@kostas here's the flow :-
1) After cherry-pick, issue `./scripts/config_softhsm2.sh`
2) Update `SOFTHSM2_CONF` via `export =$HOME/lib/softhsm/softhsm2.conf`
3) trigger `make unit-test` , this should hopefully work now.
kostas (Tue, 04 Dec 2018 20:23:44 GMT):
Has joined the channel.
sykesm (Tue, 04 Dec 2018 20:23:46 GMT):
then why does anyone need to rebase? something changed outside the tree
sykesm (Tue, 04 Dec 2018 20:23:59 GMT):
let's step back
sykesm (Tue, 04 Dec 2018 20:25:11 GMT):
Let's look at the change first.
sykesm (Tue, 04 Dec 2018 20:25:31 GMT):
1. Is is appropriate in anyone's mind for a build system to put artifacts outside of the build tree>?
sykesm (Tue, 04 Dec 2018 20:25:31 GMT):
1. Is is appropriate in anyone's mind for a build system to put artifacts outside of the build tree?
rameshthoomu (Tue, 04 Dec 2018 20:27:02 GMT):
I agree on that..
rameshthoomu (Tue, 04 Dec 2018 20:27:25 GMT):
let's pull @harsha into this..
sykesm (Tue, 04 Dec 2018 20:37:08 GMT):
I would like to create the CR to revert that change. This is for these reasons:
1. the build process should never modify items outside of the build tree
2. pkcs11 configuration is an aspect of how the build system is setup
3. creating the softhsm token may be inappropriate if the current environment has already configured PKCS11_LIB, PKCS11_PIN, and PKCS11_LABEL as required by the tests
4. this change conflicts with the pending documentation update that describes how to install and configure softhsm to use during development
sykesm (Tue, 04 Dec 2018 20:37:08 GMT):
I would like to create the CR to revert that change. This is for these reasons:
1. the build process should never modify items outside of the build tree
2. pkcs11 configuration is an aspect of how the build system is setup
3. creating the softhsm token may be inappropriate if the current environment has already configured PKCS11_LIB, PKCS11_PIN, and PKCS11_LABEL as required by the tests
4. this change conflicts with the pending documentation update that describes how to install and configure softhsm to use during development
And a CI change was also made: https://github.com/hyperledger/ci-management/commit/2b128c523b4ef438f2d0f5900d693659291d43b1
arjitkhullar (Wed, 05 Dec 2018 00:01:57 GMT):
Has joined the channel.
Pradeep_Pentakota (Wed, 05 Dec 2018 01:40:18 GMT):
Has joined the channel.
harsha (Wed, 05 Dec 2018 03:39:24 GMT):
Developers are forced to install softhsm2-util post removal of `testenv` target from Makefile, where following things happened.
1) softhsm2-util token creation was done as a root user that leverages default `directories.tokendir` definition from `/etc/softhsm/softhsm2.conf` . As listed here https://github.com/hyperledger/fabric/blob/release-1.3/images/testenv/install-softhsm2.sh#L24
2) Post removal of target testenv, every developer had to install softhsm which was no where found to be documented. Despite installation of softhsm, as non-root one still will be writing to `directories.tokendir` i.e `/var/lib/softhsm/token` on which no non-root user have access permission.
3) Despite initializing PKCS11_LIB, PKCS11_PIN, and PKCS11_LABEL inside environment, I still see we run into this issue
```Could not get Slot List [pkcs11: 0x190: CKR_CRYPTOKI_NOT_INITIALIZED]]FAIL github.com/hyperledger/fabric/bccsp/pkcs11 0.008s```
latitiah (Wed, 05 Dec 2018 15:00:20 GMT):
@rameshthoomu @jtclark : It looks like there is no fabric-javaenv:amd64-latest ```09:55:41 Error response from daemon: manifest for nexus3.hyperledger.org:10001/hyperledger/fabric-javaenv:amd64-latest not found```
jtclark (Wed, 05 Dec 2018 15:04:46 GMT):
@latitiah I don't see where that particular image is published as amd64-latest in the nightly job....
latitiah (Wed, 05 Dec 2018 15:24:03 GMT):
... so I would say that needs to be added. We need to be sure to pull this latest image as well.
latitiah (Wed, 05 Dec 2018 15:24:54 GMT):
Who was working on that sambhavdutt or rameshthoomu?
manish-sethi (Wed, 05 Dec 2018 16:19:14 GMT):
Looks like release-1.3 is broken and not in good shape. The integration tests are failing with a message - "missing required image: hyperledger/fabric-javaenv:amd64-latest" - https://gerrit.hyperledger.org/r/#/c/27948/
manish-sethi (Wed, 05 Dec 2018 16:19:14 GMT):
Looks like CI for release-1.3 is broken. The integration tests are failing with a message - "missing required image: hyperledger/fabric-javaenv:amd64-latest" - https://gerrit.hyperledger.org/r/#/c/27948/
rameshthoomu (Wed, 05 Dec 2018 16:44:24 GMT):
Looking into it
rameshthoomu (Wed, 05 Dec 2018 16:50:29 GMT):
@latitiah yes we are publishing as amd64-1.4.0-stable
rameshthoomu (Wed, 05 Dec 2018 16:50:40 GMT):
Do you need amd64-latest for javaenv too?
latitiah (Wed, 05 Dec 2018 17:01:26 GMT):
yes. That's what is missing. It looks like it is missing for integration tests as well.
jtclark (Wed, 05 Dec 2018 17:01:41 GMT):
@latitiah Looks like we need to add that
rameshthoomu (Thu, 06 Dec 2018 14:43:16 GMT):
@sambhavdutt please re-open FAB-12670 Softhsm issue.. The fix has been reverted recently from fabric.. https://jenkins.hyperledger.org/view/Daily/job/fabric-daily-s390x/
rameshthoomu (Thu, 06 Dec 2018 15:16:36 GMT):
@harsha @SriramaSharma Getting this error while building baseimage on ppc
```
10:03:58 + gpg --keyserver ha.pool.sks-keyservers.net --recv-keys B42F6819007F00F88E364FD4036A9C25BF357DD4
10:03:59 gpg: cannot open '/dev/tty': No such device or address
10:03:59 + :
10:03:59 + gpg --batch --verify /usr/local/bin/gosu.asc /usr/local/bin/gosu
10:03:59 gpg: Signature made Wed Sep 28 22:22:57 2016 UTC
10:03:59 gpg: using RSA key 036A9C25BF357DD4
10:03:59 gpg: Can't check signature: No public key
```
harsha (Thu, 06 Dec 2018 15:17:38 GMT):
@rameshthoomu Can you kindly point me to respective job ?
rameshthoomu (Thu, 06 Dec 2018 15:18:26 GMT):
ignore that.. that's on s390x
rameshthoomu (Thu, 06 Dec 2018 15:47:50 GMT):
Harsha, we can not publish ppc 0.4.14 baseimages and thirdparty. images without java version fix
rameshthoomu (Thu, 06 Dec 2018 15:47:50 GMT):
@harsha @SriramaSharma, it's not possible to publish ppc 0.4.14 baseimages and thirdparty images without java version fix
rameshthoomu (Thu, 06 Dec 2018 15:49:21 GMT):
if you apply the JAVA Version fix, then we have to publish a new baseimage (0.4.15).
rameshthoomu (Thu, 06 Dec 2018 15:56:00 GMT):
updated comment in https://jira.hyperledger.org/browse/FABB-113
sambhavdutt (Thu, 06 Dec 2018 16:36:57 GMT):
The unit-tests on `s390x` , master are failing again as softhsm is not installed, this might be an expected error so I have not created a High priority bug on this,
https://jira.hyperledger.org/browse/FAB-13182
rameshthoomu (Thu, 06 Dec 2018 16:37:24 GMT):
@bharadwajambati hi
bharadwajambati (Thu, 06 Dec 2018 16:37:24 GMT):
Has joined the channel.
rameshthoomu (Thu, 06 Dec 2018 16:37:29 GMT):
is ede there?
rameshthoomu (Thu, 06 Dec 2018 16:37:29 GMT):
is eddie there?
bharadwajambati (Thu, 06 Dec 2018 16:37:37 GMT):
yup ramesh garu
rameshthoomu (Thu, 06 Dec 2018 16:38:54 GMT):
Can you ask him log in to RocketChat
rameshthoomu (Thu, 06 Dec 2018 16:39:02 GMT):
I have an issue with s390x build nodes
rameshthoomu (Thu, 06 Dec 2018 16:39:05 GMT):
```
11:36:21 docker: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?.
11:36:21 See 'docker run --help'.
11:36:21 Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
11:36:21 Build step 'Execute shell' marked build as failure
11:36:21 $ ssh-agent -k
```
rameshthoomu (Thu, 06 Dec 2018 16:39:11 GMT):
It seems he is working on it
bharadwajambati (Thu, 06 Dec 2018 16:42:14 GMT):
oaky
bharadwajambati (Thu, 06 Dec 2018 16:42:14 GMT):
okay
harsha (Thu, 06 Dec 2018 16:43:52 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=hpSCwHc26BpHBZSZK) @rameshthoomu How should this be taken ahead ? @dave.enyeart ^^^ request for your response.
eddie.allen (Thu, 06 Dec 2018 16:44:14 GMT):
Has joined the channel.
eddie.allen (Thu, 06 Dec 2018 16:45:50 GMT):
@rameshthoomu I am working on the `s390x` build issues, will update here shortly
rameshthoomu (Thu, 06 Dec 2018 16:46:08 GMT):
sure. Thank @eddie.allen
rameshthoomu (Thu, 06 Dec 2018 16:50:04 GMT):
I see above error in ubuntu1604-s390x-2c-16g-20
eddie.allen (Thu, 06 Dec 2018 16:59:44 GMT):
can you try now
eddie.allen (Thu, 06 Dec 2018 16:59:48 GMT):
@rameshthoomu
rameshthoomu (Thu, 06 Dec 2018 16:59:57 GMT):
sure
rameshthoomu (Thu, 06 Dec 2018 17:01:24 GMT):
seeing different issue now https://jenkins.hyperledger.org/view/fabric-baseimage/job/fabric-baseimage-verify-docker-s390x/275/console
rameshthoomu (Thu, 06 Dec 2018 17:01:54 GMT):
unable to clone the repo..
eddie.allen (Thu, 06 Dec 2018 17:04:18 GMT):
where is the error message? I don't see one
rameshthoomu (Thu, 06 Dec 2018 17:08:01 GMT):
no error message.. It's unable to clone the repository..
rameshthoomu (Thu, 06 Dec 2018 17:21:04 GMT):
even in this job, https://jenkins.hyperledger.org/view/fabric-chaincode-node/job/fabric-chaincode-node-verify-s390x/143/console
eddie.allen (Thu, 06 Dec 2018 18:01:13 GMT):
the `s390x` build issues should now be resolved
rameshthoomu (Thu, 06 Dec 2018 18:10:50 GMT):
Thanks @eddie.allen
dave.enyeart (Thu, 06 Dec 2018 23:57:07 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=bshBHfXx3h4ywvyjH) @harsha There is no intent to support ppc64le docker images in open source in v1.4 timeframe. I've -1ed the multi-arch CR. Harsha I pinged you some suggestions for taking the request forward for next releases
harsha (Fri, 07 Dec 2018 03:22:03 GMT):
Hi Dave,
Thank you for taking your time to review the patch, thanks for your inputs :)
rameshthoomu (Fri, 07 Dec 2018 14:31:42 GMT):
@sambhavdutt when you get some time, please cherry-pick this change https://gerrit.hyperledger.org/r/#/c/27946/ and execute upgrade test in sandbox
sambhavdutt (Fri, 07 Dec 2018 14:35:40 GMT):
@rameshthoomu , sure thing, I will let you know
rameshthoomu (Fri, 07 Dec 2018 20:34:37 GMT):
@jtclark any update on release test suite? Planning to release 1.4.0-rc1 on monday..
jtclark (Fri, 07 Dec 2018 20:34:53 GMT):
I'm working on it in parallel
rameshthoomu (Fri, 07 Dec 2018 20:35:06 GMT):
are you able to run the jobs?
jtclark (Fri, 07 Dec 2018 20:35:19 GMT):
need to test again.....
jtclark (Fri, 07 Dec 2018 20:35:27 GMT):
I'll push that out to the sandbox as well.
rameshthoomu (Fri, 07 Dec 2018 20:36:40 GMT):
sure.. We don;t have any back jobs for this task.. Please let me know the status by today EOD or tomorrow morning
jtclark (Fri, 07 Dec 2018 20:36:52 GMT):
of course.
jtclark (Fri, 07 Dec 2018 20:36:54 GMT):
we'll do.
jtclark (Fri, 07 Dec 2018 20:36:54 GMT):
will do.
rameshthoomu (Fri, 07 Dec 2018 20:37:13 GMT):
ok
MadhuriBhargav (Mon, 10 Dec 2018 06:06:40 GMT):
Has joined the channel.
scottz (Tue, 11 Dec 2018 03:16:03 GMT):
@sambhavdutt ```06:46:24 ======== PULL DOCKER IMAGES ========
06:46:24 Fetching images from Nexus
06:46:24 ---------> STABLE_VERSION: 1.3.0-stable
06:46:24 Images: peer
06:46:24
06:46:25 Error response from daemon: manifest for nexus3.hyperledger.org:10001/hyperledger/fabric-peer:amd64-1.3.0-stable not found
06:46:25 Makefile:129: recipe for target 'pull-images' failed
06:46:25 make: *** [pull-images] Error 1
06:46:25 Build step 'Execute shell' marked build as failure``` is the error I see when looking at the 1.3 pte tests in job 16 https://jenkins.hyperledger.org/job/fabric-test-svt-weekly-pte-x86_64/16/console.
sambhavdutt (Tue, 11 Dec 2018 04:39:37 GMT):
@scottz
Yes, I was not able to pull this image from my local system now. I see that peer:amd64-1.3.1 is available, let me check the scripts
sambhavdutt (Tue, 11 Dec 2018 04:54:02 GMT):
In the `12HrTest.py` file in the weekly directory, I cant see the script that is pulling the `1.3.0-stable` If that is replaced to `1.3.1-stable` this should work.
@scottz
manish-sethi (Tue, 11 Dec 2018 05:05:07 GMT):
@Ramesh - VerifyBuild is failing for this CR on release-1.1 branch with linter error for the files that are not present in this CR - https://gerrit.hyperledger.org/r/#/c/22749/.
manish-sethi (Tue, 11 Dec 2018 05:05:07 GMT):
@rameshthoomu - VerifyBuild is failing for this CR on release-1.1 branch with linter error for the files that are not present in this CR - https://gerrit.hyperledger.org/r/#/c/22749/.
rameshthoomu (Tue, 11 Dec 2018 05:10:49 GMT):
@manish-sethi linter script is executing from this script https://github.com/hyperledger/fabric/blob/release-1.1/scripts/golinter.sh
manish-sethi (Tue, 11 Dec 2018 05:42:17 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=zR95JYrPqsiqvC9vQ) @rameshthoomu My bad... it needed a rebase - didn't expect that for release-1.1 :-)
sstone1 (Tue, 11 Dec 2018 07:50:00 GMT):
@rameshthoomu seem to be getting this failure on the fabric-samples verify build:
```
06:36:21 + ./CI_Script.sh --byfn_eyfn_Tests
06:36:21
06:36:21 -----------> Execute Byfn and Eyfn Tests
06:36:21 -----------> MARCH linux
06:36:21 -----------> PROJECT_VERSION: 1.4.0-rc1-stable
06:36:21 % Total % Received % Xferd Average Speed Time Time Time Current
06:36:21 Dload Upload Total Spent Left Speed
06:36:21
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 899 100 899 0 0 5742 0 --:--:-- --:--:-- --:--:-- 5726
06:36:21 -----------> COMMIT = stable
06:36:21 % Total % Received % Xferd Average Speed Time Time Time Current
06:36:21 Dload Upload Total Spent Left Speed
06:36:21
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 1325 0 1325 0 0 9960 0 --:--:-- --:--:-- --:--:-- 10037
06:36:21
06:36:21 gzip: stdin: not in gzip format
06:36:21 tar: Child returned status 1
06:36:21 tar: Error is not recoverable: exiting now
06:36:21 FAILED to download binaries
```
sstone1 (Tue, 11 Dec 2018 07:50:10 GMT):
@dave.enyeart FYI
sstone1 (Tue, 11 Dec 2018 07:50:14 GMT):
https://jenkins.hyperledger.org/job/fabric-samples-verify-byfn/129/console
rameshthoomu (Tue, 11 Dec 2018 08:36:32 GMT):
@sstone1 nightly jobs has to re-trigger to publish latest images from fabric master branch.
rameshthoomu (Tue, 11 Dec 2018 08:36:56 GMT):
published images to nexus and re-triggered above patch and it's working now..
rameshthoomu (Tue, 11 Dec 2018 08:37:08 GMT):
https://jenkins.hyperledger.org/job/fabric-samples-verify-byfn/130/console
sstone1 (Tue, 11 Dec 2018 14:08:48 GMT):
:+1: thanks for fixing that @rameshthoomu
tijohnson (Tue, 11 Dec 2018 23:04:12 GMT):
@rickr @rameshthoomu We have merged RELENG-1541 Install Maven 3.5
Maven 3.5.4 is now available in the following builds: fabric-sdk-java-merge-x86_64 & fabric-sdk-java-verify-x86_64
If you want it available on some other builds I would be willing to lend a hand
rickr (Wed, 12 Dec 2018 14:20:57 GMT):
thx @tijohnson @rameshthoomu is the JSDK built for any other fabric tests? I really think they should all be made consistent.
rameshthoomu (Wed, 12 Dec 2018 14:32:32 GMT):
yes.. Will check and implement the same
rickr (Wed, 12 Dec 2018 19:18:25 GMT):
@rameshthoomu @tijohnson Hey - - little help on JSDK verify -- I don't think it's ever even getting to the cirun script https://jenkins.hyperledger.org/job/fabric-sdk-java-verify-x86_64/2547/console
rickr (Wed, 12 Dec 2018 21:41:13 GMT):
@rameshthoomu @tijohnson blocking ^^^^ !!! :(
rameshthoomu (Wed, 12 Dec 2018 21:42:26 GMT):
let me see what changes went in recently.
tijohnson (Thu, 13 Dec 2018 00:59:54 GMT):
It looks like it dies trying to execute the first build script.... invalid reference format ??
tijohnson (Thu, 13 Dec 2018 01:04:25 GMT):
Running it on sandbox...
tijohnson (Thu, 13 Dec 2018 01:04:25 GMT):
Running it on sandbox... and that passed next step is to update with fresh bits and run again
rameshthoomu (Thu, 13 Dec 2018 02:11:19 GMT):
Tim, this is fixed ..
rameshthoomu (Thu, 13 Dec 2018 02:11:26 GMT):
All good now
davidkhala (Thu, 13 Dec 2018 02:52:43 GMT):
https://jenkins.hyperledger.org/job/fabric-sdk-node-verify-s390x/350/ weird behavior, the log file shows not found
sambhavdutt (Thu, 13 Dec 2018 02:55:35 GMT):
@davidkhala
Is this the log file you are looking for,
https://jenkins.hyperledger.org/job/fabric-sdk-node-verify-s390x/350/artifact/gopath/src/github.com/hyperledger/fabric-sdk-node/node_modules/socks/yarn-error.log
davidkhala (Thu, 13 Dec 2018 02:57:37 GMT):
@sambhavdutt but this is not the one I was familiar with. Where is the gulp test log?
sambhavdutt (Thu, 13 Dec 2018 03:04:13 GMT):
@davidkhala let me check this again if this is failing because of gulp tests
sambhavdutt (Thu, 13 Dec 2018 03:23:16 GMT):
I see that the orderer container is failing,
Can you check this test output log, you can find the errors after the gulp tests start,
https://jenkins.hyperledger.org/job/fabric-sdk-node-verify-s390x/355/consoleFull
davidkhala (Thu, 13 Dec 2018 03:28:25 GMT):
@sambhavdutt thanks, I get some hints
rameshthoomu (Thu, 13 Dec 2018 03:29:16 GMT):
@davidkhala it seems orderer is exited https://jenkins.hyperledger.org/job/fabric-sdk-node-verify-s390x/355/artifact/gopath/src/github.com/hyperledger/fabric-sdk-node/orderer.log
sambhavdutt (Thu, 13 Dec 2018 14:55:38 GMT):
@tijohnson @rameshthoomu @rickr
The sdk-node tests are failing in the fabric end-2-end merge consistently with the maven?NPM error,
I have updated the latest fail in https://jira.hyperledger.org/browse/IN-39
sambhavdutt (Thu, 13 Dec 2018 14:55:38 GMT):
@tijohnson @rameshthoomu @rickr
The sdk-node tests are failing in the fabric end-2-end merge consistently with the maven/NPM error,
I have updated the latest fail in https://jira.hyperledger.org/browse/IN-39
rickr (Thu, 13 Dec 2018 14:57:48 GMT):
@bretharrison ^^^
rickr (Thu, 13 Dec 2018 14:59:19 GMT):
Is that consistent ? or one time ? It IMO has to be an environment issue .. not seeing this locally
rickr (Thu, 13 Dec 2018 15:01:18 GMT):
whole stack for v1.4 merge built ok yesterday -> https://gerrit.hyperledger.org/r/#/c/28145/
rameshthoomu (Thu, 13 Dec 2018 15:05:38 GMT):
@rickr checking this.. I will let you know if this is consistent
sambhavdutt (Fri, 14 Dec 2018 16:24:45 GMT):
@bretharrison
I see that sdk-node merge , Headless/Integration tests are failing with this error. |
```
10:24:37 not ok 97 Failed to register "testUser". Error: Calling register endpoint failed, READ Timeout at ClientRequest.request.setTimeout (/w/workspace/fabric-sdk-node-merge-x86_64/gopath/src/github.com/hyperledger/fabric-sdk-node/fabric-ca-client/lib/FabricCAClient.js:349:13) at Object.onceWrapper (events.js:313:30) at emitNone (events.js:106:13) at ClientRequest.emit (events.js:208:7) at TLSSocket.emitRequestTimeout (_http_client.js:644:42) at Object.onceWrapper (events.js:313:30) at emitNone (events.js:111:20) at TLSSocket.emit (events.js:208:7) at TLSSocket.Socket._onTimeout (net.js:410:8) at ontimeout (timers.js:498:11) at tryOnTimeout (timers.js:323:5) at Timer.listOnTimeout (timers.js:290:5)
10:24:37 ---
10:24:37 operator: fail
```
I'll check the progress of these jobs and create Bug
rameshthoomu (Fri, 14 Dec 2018 16:28:03 GMT):
I re-triggered this job again .. will see
vijay.bP (Sat, 15 Dec 2018 16:30:04 GMT):
@bretharrison @mbwhite Could you please look into this https://jira.hyperledger.org/browse/FABN-1079
rameshthoomu (Sat, 15 Dec 2018 16:37:47 GMT):
@mbwhite I think this lines needs to modify to `release-1.4` and this line to `master` https://github.com/hyperledger/fabric-sdk-node/blob/release-1.4/scripts/Jenkins_Scripts/Publish_API_Docs.sh#L27
kostas (Sat, 15 Dec 2018 22:08:51 GMT):
Has left the channel.
mbwhite (Mon, 17 Dec 2018 09:47:53 GMT):
@rameshthoomu correct this should be master - as it's referring to the docs repo rather than the code.
mastersingh24 (Mon, 17 Dec 2018 12:25:42 GMT):
Are the x86 executor nodes down?
rameshthoomu (Mon, 17 Dec 2018 13:05:51 GMT):
Seems LF network issue effected CI services https://status.linuxfoundation.org/
rameshthoomu (Mon, 17 Dec 2018 13:25:18 GMT):
Issue is resolved.
edisinovcic (Mon, 17 Dec 2018 14:01:27 GMT):
Has joined the channel.
sambhavdutt (Mon, 17 Dec 2018 17:19:04 GMT):
As of today, these are the high priority Bugs,
https://jira.hyperledger.org/browse/FABN-1077 - fabric-sdk-node
https://jira.hyperledger.org/browse/FAB-13296 - fabric-chaincode-java
https://jira.hyperledger.org/browse/FAB-12670 - unit-test s390x (Softhsm)
=============================
Medium priority,
https://jira.hyperledger.org/browse/FAB-13295
https://jira.hyperledger.org/browse/FAB-13313
rameshthoomu (Mon, 17 Dec 2018 17:45:39 GMT):
Thanks @sambhavdutt
rameshthoomu (Mon, 17 Dec 2018 17:46:31 GMT):
FAB-13296 is a flake.. The build failure log shows
> Could not get resource 'https://plugins.gradle.org/m2/com/google/guava/guava/18.0/guava-18.0.jar'.
18:05:47 > Connection reset
I see the jar is available https://jcenter.bintray.com/com/google/guava/guava/18.0/:guava-18.0.jar
rameshthoomu (Mon, 17 Dec 2018 17:46:42 GMT):
Let me re-trigger
sambhavdutt (Mon, 17 Dec 2018 17:47:17 GMT):
ok, thank you
rameshthoomu (Mon, 17 Dec 2018 17:48:53 GMT):
Assigned FAB-13296 to Matt
rameshthoomu (Mon, 17 Dec 2018 17:48:53 GMT):
Assigned FAB-13296 to Matt and added mist-fix label to it
rameshthoomu (Mon, 17 Dec 2018 17:54:48 GMT):
@mbwhite @bretharrison API docs now published to release-1.4 branch https://fabric-sdk-node.github.io/release-1.4/index.html
rameshthoomu (Mon, 17 Dec 2018 17:54:59 GMT):
How to validate?
dave.enyeart (Mon, 17 Dec 2018 18:01:33 GMT):
@rameshthoomu is FAB-13296 the correct number? Not seeing it assigned to Matt or marked must-fix
rameshthoomu (Mon, 17 Dec 2018 18:01:50 GMT):
Let me check
rameshthoomu (Mon, 17 Dec 2018 18:02:06 GMT):
FAB-13295
rameshthoomu (Mon, 17 Dec 2018 18:02:48 GMT):
goimports issue on release-1.0 and 1.1
bretharrison (Mon, 17 Dec 2018 19:22:07 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=WHNPK6jmhc3fWvKGc) @rameshthoomu Docs look good, seeing latest changes for 1.4 in the 1.4 docs,
however the default is master, now that 1.4 is publishing will set master straight.
davidkhala (Tue, 18 Dec 2018 03:42:46 GMT):
https://jenkins.hyperledger.org/job/fabric-sdk-node-verify-x86_64/1763/ found x86 build failed continuously, is it because of ca container problem?
sambhavdutt (Tue, 18 Dec 2018 03:50:26 GMT):
@davidkhala
I see that the chaincode instantiation failed, starting with the node chaincode container,
```
22:09:08 not ok 477 Error: All proposals were not good at e2eUtils.tlsEnroll.then.then.then.then.then (/w/workspace/fabric-sdk-node-verify-x86_64/gopath/src/github.com/hyperledger/fabric-sdk-node/test/integration/e2e/e2eUtils.js:363:11) at
sambhavdutt (Tue, 18 Dec 2018 16:29:50 GMT):
There have been multiple unit test and code coverage fails due to timeout
https://jira.hyperledger.org/browse/FAB-13335
https://jira.hyperledger.org/browse/FAB-13313
davidkhala (Wed, 19 Dec 2018 02:24:43 GMT):
Hi experts. I find that previously CI will have node8 built, node6 built environment and corresponding tests, but now seems look only one. So how compability test is implemented for different node version now?
sambhavdutt (Wed, 19 Dec 2018 02:34:34 GMT):
@davidkhala Recently jenkins configuration was changed from freestyle to pipeline, which can execute job on node 6 or node 8 given accordingly in the scripts.
https://github.com/hyperledger/fabric-sdk-node/blob/ca9b9d10fcb13a16353aed12dd75d7bda023d55e/Jenkinsfile.x#L10
lightcap (Thu, 20 Dec 2018 16:37:56 GMT):
Has joined the channel.
dave.enyeart (Thu, 20 Dec 2018 21:20:29 GMT):
@sambhavdutt @vijay.bP @rameshthoomu any idea on the failure here? https://gerrit.hyperledger.org/r/#/c/28338/
sambhavdutt (Thu, 20 Dec 2018 21:21:08 GMT):
@dave.enyeart I will ceck
sambhavdutt (Thu, 20 Dec 2018 21:21:08 GMT):
@dave.enyeart I will check
sambhavdutt (Thu, 20 Dec 2018 21:36:54 GMT):
I can see that a variable `BASE_IMAGE_TAG` for thirdparty images is not fetching the complete value, but the script looks fine,
https://github.com/hyperledger/fabric-samples/blob/ab46e3548c46acf1c541eca71914c20bbe212f6a/Jenkinsfile#L14
the value should be `amd64-0.4.14` but it is just getting till `amd64-`
there have been no changes in the script from last successful build, I'll confirm if this is because of infrastructure
sambhavdutt (Thu, 20 Dec 2018 21:36:54 GMT):
I can see that a variable `BASE_IMAGE_TAG` for thirdparty images is not fetching the complete value, but the script looks fine,
https://github.com/hyperledger/fabric-samples/blob/ab46e3548c46acf1c541eca71914c20bbe212f6a/Jenkinsfile#L16
the value should be `amd64-0.4.14` but it is just getting till `amd64-`
there have been no changes in the script from last successful build, I'll confirm if this is because of infrastructure
vijay.bP (Thu, 20 Dec 2018 22:37:39 GMT):
@dave.enyeart @rameshthoomu https://github.com/hyperledger/fabric/blob/6e56e6e30274579b1895d84980a4bd5b8950a52e/Makefile#L51
https://github.com/hyperledger/fabric-samples/blob/ab46e3548c46acf1c541eca71914c20bbe212f6a/Jenkinsfile#L16
Space error while grep BASE_IMAGE_RELEASE
dave.enyeart (Thu, 20 Dec 2018 22:38:03 GMT):
Ramesh just had me fix it, passes now: https://gerrit.hyperledger.org/r/#/c/28338/
seokm0 (Fri, 21 Dec 2018 02:24:52 GMT):
Has joined the channel.
mbwhite (Fri, 21 Dec 2018 10:52:20 GMT):
FYI https://gerrit.hyperledger.org/r/#/c/28313/ is consistently failing on zOS... any ideas welcome?
rameshthoomu (Fri, 21 Dec 2018 14:54:12 GMT):
@vijay.bP @sambhavdutt ^^
sambhavdutt (Fri, 21 Dec 2018 14:58:52 GMT):
@rameshthoomu I will ook into this
sambhavdutt (Fri, 21 Dec 2018 14:58:52 GMT):
@rameshthoomu I will look into this
vijay.bP (Fri, 21 Dec 2018 14:59:32 GMT):
@rameshthoomu @mbwhite
```
07:09:56 fatal: read error: Connection reset by peer
07:09:56 fatal: early EOF
07:09:56 fatal: index-pack failed
```
vijay.bP (Fri, 21 Dec 2018 14:59:41 GMT):
while cloning to fabric
vijay.bP (Fri, 21 Dec 2018 15:01:37 GMT):
```
07:20:18 -----------> Publish npm modules from amd64
07:20:18 ====== PUBLISH NPM MODULES ======
07:20:18 ======> CURRENT_TAG: latest-1.2
07:20:18 ======> Current RELEASE VERSION: 1.2.3
07:20:18 ======> Publishing fabric-shim
07:20:18 ======> RELEASE_VERSION: 1.2.3
07:20:18
07:20:18 ======> CURRENT_TAG: latest-1.2
07:20:20 npm ERR! publish Failed PUT 403
07:20:20 npm ERR! code E403
07:20:20 npm ERR! You cannot publish over the previously published versions: 1.2.3. : fabric-shim
```
vijay.bP (Fri, 21 Dec 2018 15:01:37 GMT):
```
07:20:18 -----------> Publish npm modules from amd64
07:20:18 ====== PUBLISH NPM MODULES ======
07:20:18 ======> CURRENT_TAG: latest-1.2
07:20:18 ======> Current RELEASE VERSION: 1.2.3
07:20:18 ======> Publishing fabric-shim
07:20:18 ======> RELEASE_VERSION: 1.2.3
07:20:18
07:20:18 ======> CURRENT_TAG: latest-1.2
07:20:20 npm ERR! publish Failed PUT 403
07:20:20 npm ERR! code E403
07:20:20 npm ERR! You cannot publish over the previously published versions: 1.2.3. : fabric-shim
```
Is this the job for official release of the modules? why the TAG is latest-1.2
C0rWin (Fri, 21 Dec 2018 15:02:46 GMT):
is there any authentication problem to gerrit? I'm trying to login in, while getting `Authentication unavailable at this time.`... anyone aware of something which might be related?
vijay.bP (Fri, 21 Dec 2018 15:03:45 GMT):
@C0rWin It's coming for me too. I think wait for some time.
dave.enyeart (Fri, 21 Dec 2018 15:05:31 GMT):
For any issues like this send email to helpdesk@hyperledger.org sooner than later to ensure it gets looked at
C0rWin (Fri, 21 Dec 2018 15:09:57 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=NSw3c8kAQ45Ekyj88) @dave.enyeart ```Greetings!
Starting Dec. 14, 2018 through Jan. 1, 2019 the Linux Foundation will be operating with reduced staff in observance of our office closure. Responses to inbound support requests will be delayed, or otherwise addressed after Jan. 2, 2019.
Happy Holidays!
Your support ticket regarding:
"Cannot loging into my LF account",
has been entered in our ticket tracker.```
C0rWin (Fri, 21 Dec 2018 15:10:24 GMT):
Just got this answer from LF :joy:
vijay.bP (Fri, 21 Dec 2018 15:12:48 GMT):
@mbwhite @rameshthoomu We don't have fabric-shim in release-1.2 branch but job is mentioning the above error to publish fabric-shim.
vijay.bP (Fri, 21 Dec 2018 15:58:18 GMT):
@C0rWin Gerrit working now.
mbwhite (Fri, 21 Dec 2018 16:13:54 GMT):
what's the command to respin the merge build. x86 failed but zos passed, and I beileve the x is the only tht does npm publish
rameshthoomu (Fri, 21 Dec 2018 16:14:47 GMT):
Could you pls post the failed job link?
mbwhite (Fri, 21 Dec 2018 16:15:12 GMT):
https://gerrit.hyperledger.org/r/#/c/28349/
rameshthoomu (Fri, 21 Dec 2018 16:16:09 GMT):
ok
mbwhite (Fri, 21 Dec 2018 16:17:01 GMT):
https://jenkins.hyperledger.org/job/fabric-chaincode-node-merge-x86_64/57/
mbwhite (Fri, 21 Dec 2018 16:17:07 GMT):
that's the specific job
rameshthoomu (Fri, 21 Dec 2018 16:18:35 GMT):
you triggered already.. will see
mbwhite (Fri, 21 Dec 2018 16:20:06 GMT):
ah..... I couldn't see the build appear so didn't think it'd worked :-)
mbwhite (Fri, 21 Dec 2018 16:23:42 GMT):
it failed again in the same way I believe;
rameshthoomu (Fri, 21 Dec 2018 16:24:36 GMT):
yes same issue..
rameshthoomu (Fri, 21 Dec 2018 16:24:44 GMT):
Could you pls check why it is failing
mbwhite (Fri, 21 Dec 2018 16:26:21 GMT):
I have no idea; the s390 merge build worked, as did the first builds.... this is a version from 1.1.4 to 1.1.5
rameshthoomu (Fri, 21 Dec 2018 16:39:45 GMT):
@mbwhite what is the target to build API docs in release-1.3?
rameshthoomu (Fri, 21 Dec 2018 16:39:55 GMT):
I see below error
```
00:09:29.706 [12:20:45] Using gulpfile /w/workspace/fabric-chaincode-node-merge-x86_64/gopath/src/github.com/hyperledger/fabric-chaincode-node/gulpfile.js
00:09:29.707 [12:20:45] Task 'doc' is not in your gulpfile
```
rameshthoomu (Fri, 21 Dec 2018 16:40:11 GMT):
I think we have to modify this to `gulp docs`
mbwhite (Fri, 21 Dec 2018 16:41:05 GMT):
ah.. not sure why that would have changed.; but yes
rameshthoomu (Fri, 21 Dec 2018 16:43:10 GMT):
@vijay.bP could you please push this change to fabric-chaincode-node release-1.3 branch?
rameshthoomu (Fri, 21 Dec 2018 16:43:24 GMT):
so that @mbwhite can merge your change
vijay.bP (Fri, 21 Dec 2018 16:44:53 GMT):
Ok
mbwhite (Fri, 21 Dec 2018 16:45:21 GMT):
FYI tried repsining the merge build again.. and 3rd time it worked!
vijay.bP (Fri, 21 Dec 2018 16:45:42 GMT):
:woo:
mbwhite (Fri, 21 Dec 2018 16:46:00 GMT):
Absolutly!!
vijay.bP (Fri, 21 Dec 2018 17:23:37 GMT):
@mbwhite Need +2 for this change https://gerrit.hyperledger.org/r/#/c/28351/
mbwhite (Fri, 21 Dec 2018 17:33:23 GMT):
done!
rameshthoomu (Sun, 23 Dec 2018 01:48:09 GMT):
byfn node chaincode tests are failing with the below error
```
00:26:03.711 Error: could not assemble transaction, err proposal response was not successful, error code 500, msg error starting container: error starting container: pull access denied for hyperledger/fabric-nodeenv, repository does not exist or may require 'docker login'
00:26:03.711 !!!!!!!!!!!!!!! Chaincode instantiation on peer0.org2 on channel 'mychannel' failed !!!!!!!!!!!!!!!!
00:26:03.711 ========= ERROR !!! FAILED to execute End-2-End Scenario ===========
00:26:03.711
00:26:03.744 ERROR !!!! Test failed
```
rameshthoomu (Sun, 23 Dec 2018 01:48:30 GMT):
It seems the tests are now expecting hyperledger/fabric-nodeenv image..
rameshthoomu (Sun, 23 Dec 2018 01:49:52 GMT):
@sambhavdutt @vijay.bP @jtclark we have to publish publish nodenv image from fabric-chaincode-node repository..
rameshthoomu (Sun, 23 Dec 2018 01:53:25 GMT):
https://jira.hyperledger.org/browse/FAB-13431
davidkhala (Mon, 24 Dec 2018 09:28:36 GMT):
I have a question about recently change on fabric-sdk-node log. I could not find the log file printed via `logger.debug(...)` now. Previous it locates in /tmp/hfc-log/debug.log
davidkhala (Mon, 24 Dec 2018 09:28:36 GMT):
I have a question about recently change on fabric-sdk-node log. I could not find the log file printed via `logger.debug(...)` now. Previous it locates in /tmp/hfc/hfc-log/debug.log
davidkhala (Mon, 24 Dec 2018 09:28:36 GMT):
I have a question about recently change on fabric-sdk-node log. I could not find the log file printed via `logger.debug(...)` now. Previous it locates in `debug.log`
sambhavdutt (Mon, 24 Dec 2018 14:11:53 GMT):
@davidkhala
Let me check on this, I will let you know
sambhavdutt (Mon, 24 Dec 2018 14:21:46 GMT):
@davidkhala
https://jenkins.hyperledger.org/view/fabric-sdk-node/job/fabric-sdk-node-verify-x86_64/1798/artifact/gopath/src/github.com/hyperledger/fabric-sdk-node/
I see this in your last CR, are these the logs you are looking for, I can see two fails in the console log below,
https://jenkins.hyperledger.org/view/fabric-sdk-node/job/fabric-sdk-node-verify-x86_64/1798/consoleFull
sambhavdutt (Mon, 24 Dec 2018 14:21:46 GMT):
@davidkhala
https://jenkins.hyperledger.org/view/fabric-sdk-node/job/fabric-sdk-node-verify-x86_64/1798/artifact/gopath/src/github.com/hyperledger/fabric-sdk-node/
I see this in your last CR, are these the logs you are looking for, I can see two fails in the console log below in `** FabricCAServices: Test enroll() With Dynamic CSR **`
https://jenkins.hyperledger.org/view/fabric-sdk-node/job/fabric-sdk-node-verify-x86_64/1798/consoleFull
sambhavdutt (Mon, 24 Dec 2018 14:21:46 GMT):
@davidkhala
https://jenkins.hyperledger.org/view/fabric-sdk-node/job/fabric-sdk-node-verify-x86_64/1798/artifact/gopath/src/github.com/hyperledger/fabric-sdk-node/
I see this in your last CR, are these the logs you are looking for, I can see two fails in the console log below in `** FabricCAServices: Test enroll() With Dynamic CSR **` on x and z platforms,
https://jenkins.hyperledger.org/view/fabric-sdk-node/job/fabric-sdk-node-verify-x86_64/1798/consoleFull
rameshthoomu (Tue, 25 Dec 2018 20:31:08 GMT):
@MartinC @chrispoole @dave.enyeart The last commit to fabric-sdk-rest jobs was almost 8 months back. Do we need to maintain CI configuration for this repo? Is this repo active or the code moved to some other repo?
fgimenez (Wed, 26 Dec 2018 09:30:11 GMT):
Has joined the channel.
dave.enyeart (Thu, 27 Dec 2018 15:43:56 GMT):
@rameshthoomu It looks like it is dead so I would not invest CI resources on it at this point. @odowdaibm @andrew-coleman What is the strategic direction for REST SDK on top of Node.js SDK? Fundamentally, it seems a little odd to me to have a synchronous REST API on top of an async node API.
sambhavdutt (Fri, 28 Dec 2018 16:36:50 GMT):
These are the list of current Bugs for the failing tests,
https://jira.hyperledger.org/browse/FABN-1090 - E2E daily test
https://jira.hyperledger.org/browse/FABN-1089 - E2E daily test
https://jira.hyperledger.org/browse/FAB-13452 - Daily unit-tests, daily-unit-test-coverage
https://jira.hyperledger.org/browse/FAB-12670 - unit-tests s390x
https://jira.hyperledger.org/browse/FAB-13295 - goimports error, r-1.0, r-1.1 branches
https://jira.hyperledger.org/browse/FABN-1088 - sdk-node Gulp tests
rameshthoomu (Sat, 29 Dec 2018 00:50:04 GMT):
Seems FABN-1090 and FABN-1089 are related errors..
rameshthoomu (Sat, 29 Dec 2018 02:01:55 GMT):
@sambhavdutt FAB-12670 is closed.
dave.enyeart (Sun, 30 Dec 2018 15:03:26 GMT):
fabric-samples is failing CI https://gerrit.hyperledger.org/r/#/c/28420/: "Failed to pull hyperledger/fabric-ccenv:2.0.0"
sambhavdutt (Sun, 30 Dec 2018 15:10:39 GMT):
@dave.enyeart
I will check this now
sambhavdutt (Sun, 30 Dec 2018 16:12:46 GMT):
I see this error,
```
Failed to generate platform-specific docker build: Failed to pull hyperledger/fabric-ccenv:2.0.0: API error (404): manifest for hyperledger/fabric-ccenv:2.0.0 not found
00:15:13.719 !!!!!!!!!!!!!!! Chaincode instantiation on peer0.org2 on channel 'mychannel' failed !!!!!!!!!!!!!!!!
```
I am able to get the ccenv image from Nexus on my local system,
sambhavdutt (Mon, 31 Dec 2018 00:05:48 GMT):
I have added tested the fabric-ssamples after addeing a new tag for the docker images `:image-version` I get the images tagged but the test script i BYFN is looking for 2.0.0 version of Baseos which doesn't seem right
```
error starting container: manifest for hyperledger/fabric-baseos:2.0.0 not found
```
https://gerrit.hyperledger.org/r/#/c/28368/
rameshthoomu (Mon, 31 Dec 2018 00:09:34 GMT):
add the same in pull thirdparty function
sambhavdutt (Mon, 31 Dec 2018 00:15:32 GMT):
thanks, I just added that in my patch
rameshthoomu (Mon, 31 Dec 2018 00:18:26 GMT):
I think you missed to add baseos to the pull list
sambhavdutt (Mon, 31 Dec 2018 00:21:21 GMT):
done
rameshthoomu (Mon, 31 Dec 2018 00:23:13 GMT):
and no need to take tension.. Nothing will happen
sambhavdutt (Mon, 31 Dec 2018 02:18:56 GMT):
There have been consistent fails in the end-2-end java tests.
https://jira.hyperledger.org/browse/FAB-13457
dave.enyeart (Mon, 31 Dec 2018 13:54:58 GMT):
@sambhavdutt @rameshthoomu I see multiple repositories have CI failures due to the end2end java sdk tests, I added comment to https://jira.hyperledger.org/browse/FAB-13457
dave.enyeart (Mon, 31 Dec 2018 13:56:09 GMT):
Concerning the prior conversation, I'm still seeing "Failed to pull hyperledger/fabric-ccenv:2.0.0" in fabric-samples verify job. What is the next step for that?
sambhavdutt (Mon, 31 Dec 2018 13:57:28 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=qBby5MpbDJPybpzTp) @dave.enyeart https://gerrit.hyperledger.org/r/#/c/28368/
I have submitted CR to fix this,
sambhavdutt (Mon, 31 Dec 2018 13:58:20 GMT):
I am getting a +1 on this, I have added tag 2.0.0 for ccenv and the thirdparty in thsi
sambhavdutt (Mon, 31 Dec 2018 13:58:20 GMT):
I am getting a +1 on this, I have added tag 2.0.0 for ccenv and the thirdparty in this
sambhavdutt (Mon, 31 Dec 2018 13:59:29 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=ESAjbRSgnCMtniMtH) @dave.enyeart There has been no change in the location of fabric repository, I will address your concerns
dave.enyeart (Mon, 31 Dec 2018 14:01:36 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=TrNv7BoWbQZBH39Ab) @sambhavdutt +2ed
sambhavdutt (Mon, 31 Dec 2018 14:02:03 GMT):
thank you
dave.enyeart (Mon, 31 Dec 2018 14:02:14 GMT):
Let's get @rameshthoomu to +1 and then we'll find another +2
vijay.bP (Mon, 31 Dec 2018 16:13:03 GMT):
@mbwhite @bretharrison Please look into this fabric-chaincode-node builds are failing consistently https://jira.hyperledger.org/browse/FAB-13462
vijay.bP (Mon, 31 Dec 2018 16:13:03 GMT):
@mbwhite @bretharrison Please look into this fabric-chaincode-node builds are failing https://jira.hyperledger.org/browse/FAB-13462
sambhavdutt (Mon, 31 Dec 2018 16:30:53 GMT):
These are the list of active Bugs as of today other than FAB-13462
https://jira.hyperledger.org/browse/FAB-13457 e2e-java
https://jira.hyperledger.org/browse/IN-42 Infra team
gongliaoan (Wed, 02 Jan 2019 09:02:14 GMT):
Has joined the channel.
davidkhala (Wed, 02 Jan 2019 09:56:15 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=t4i3w5EMoJT2Bpmaz) @dave.enyeart By the way here, we could always await for those async node API and reponse back. Not a problem, but I have a feeling from community that most application will provide their own REST service along with application access control, making REST sdk inactive and only provide a reference.
davidkhala (Wed, 02 Jan 2019 09:56:15 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=t4i3w5EMoJT2Bpmaz) @dave.enyeart By the way here, we could always await for those async node API and reponse back. Not a problem, but I have a feeling from community that most application will provide their own REST service along with application access control. We only see it as a reference mostly
davidkhala (Wed, 02 Jan 2019 10:53:04 GMT):
Is job builder out of service now? I find after reply with `reverify`, the CI is `aborted`
pandrejko (Wed, 02 Jan 2019 12:43:58 GMT):
@rameshthoomu @jtclark Just wondering if the Documentation broken link analyzer is turned on and now running against all Documentation builds? We had a few broken links over the holiday, but I did not see any notifications of this.
jtclark (Wed, 02 Jan 2019 13:27:49 GMT):
@pandrejko I'll have to check
jtclark (Wed, 02 Jan 2019 13:45:26 GMT):
@pandrejko in the current configuration of the fabric-docs-build job, I don't see where the linkchecker is enabled
rameshthoomu (Wed, 02 Jan 2019 15:04:15 GMT):
@vijay.bP could you please help above question..
vijay.bP (Wed, 02 Jan 2019 15:05:42 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=T99dACiJRM4fGnhSa) @rameshthoomu give me a sec
vijay.bP (Wed, 02 Jan 2019 15:09:33 GMT):
@jtclark Please see this file for linkckeck https://github.com/hyperledger/fabric/blob/eca1b14b7e3453a5d32296af79cc7bad10c7673b/tox.ini#L5
vijay.bP (Wed, 02 Jan 2019 15:09:33 GMT):
@jtclark Please see this file for linkckeck https://github.com/hyperledger/fabric/blob/eca1b14b7e3453a5d32296af79cc7bad10c7673b/tox.ini#L15
vijay.bP (Wed, 02 Jan 2019 15:55:28 GMT):
@jtclark @pandrejko In the current config we didn't enable linkcheck https://github.com/hyperledger/ci-management/blob/3b9dcdf1c44a8e180a9f42ce41e534262f05f9e5/jjb/fabric/shell/include-raw-fabric-build-docs.sh#L52
sambhavdutt (Wed, 02 Jan 2019 16:18:36 GMT):
These are the list of important Bugs as of today
https://jira.hyperledger.org/browse/FAB-13457 sdk-java
https://jira.hyperledger.org/browse/FABN-1090 sdk-node
https://jira.hyperledger.org/browse/IN-42
rameshthoomu (Wed, 02 Jan 2019 17:40:04 GMT):
@rickr need your thoughts on this https://jira.hyperledger.org/browse/FABJ-397
pandrejko (Wed, 02 Jan 2019 17:51:24 GMT):
@rameshthoomu @jtclark @vijay.bP Are we ready to enable to the documentation link checker now then? Or are there still some kinks to be worked out?
rameshthoomu (Wed, 02 Jan 2019 17:53:19 GMT):
@jtclark said there are two patches out for review couple of weeks back..
vijay.bP (Wed, 02 Jan 2019 17:53:22 GMT):
@jtclark Can you give update on this ^^
rameshthoomu (Wed, 02 Jan 2019 17:53:40 GMT):
He is trying to skip the false link check failures..
rameshthoomu (Wed, 02 Jan 2019 17:55:01 GMT):
I don;t see any open patchsets on fabric but I see one here https://gerrit.hyperledger.org/r/#/c/27511/
rameshthoomu (Wed, 02 Jan 2019 17:55:28 GMT):
Jason, Could you please test above patch set in sandbox and make sure there are no failures on the docs builds..
rameshthoomu (Wed, 02 Jan 2019 17:55:44 GMT):
please re-run this job multiple times in sandbox and let me know the update..
rameshthoomu (Wed, 02 Jan 2019 17:55:50 GMT):
will merge it later today
jtclark (Wed, 02 Jan 2019 18:49:16 GMT):
@vijay.bP, @vijay.bP, @vijay.bP Yes, we can re-enable it.
jtclark (Wed, 02 Jan 2019 18:49:16 GMT):
@vijay.bP, @vijay.bP, @vijay.bP Yes, we can enable it.
jtclark (Wed, 02 Jan 2019 18:49:16 GMT):
@vijay.bP, @rameshthoomu, @pandrejko Yes, we can enable it.
jtclark (Wed, 02 Jan 2019 18:50:02 GMT):
I will push it out to the sandbox once more just to make sure things are configured properly, and then we can merge the changes that enable link checking
jtclark (Wed, 02 Jan 2019 20:06:22 GMT):
@pandrejko, @vijay.bP - https://jenkins.hyperledger.org/sandbox/job/fabric-docs-build-x86_64/1/console
jtclark (Wed, 02 Jan 2019 20:07:14 GMT):
there are several broken links associated with the 1.4.0 tag.... @pandrejko are these the broken links you noticed in the documentation?
dave.enyeart (Wed, 02 Jan 2019 20:58:26 GMT):
@rameshthoomu any idea why readthedocs is not getting published?
dave.enyeart (Wed, 02 Jan 2019 20:58:37 GMT):
for example I merged a doc change: https://gerrit.hyperledger.org/r/#/c/28436/
dave.enyeart (Wed, 02 Jan 2019 20:59:53 GMT):
but a RTD build is not getting triggered for the change: https://readthedocs.org/projects/hyperledger-fabric/builds/
dave.enyeart (Wed, 02 Jan 2019 21:00:22 GMT):
last RTD build was more than a week ago
dave.enyeart (Wed, 02 Jan 2019 21:00:33 GMT):
I just triggered one manually for 'latest'
dave.enyeart (Wed, 02 Jan 2019 21:00:44 GMT):
you can see the same issue for release-1.4
rameshthoomu (Wed, 02 Jan 2019 21:05:43 GMT):
let me check
rameshthoomu (Wed, 02 Jan 2019 21:08:09 GMT):
Could you please check webhook configuration in fabric repository..
pandrejko (Wed, 02 Jan 2019 21:25:11 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=urZmpDXagofvrpY6Q) @jtclark Thanks @jtclark - No. Those are not the ones we ran into, but I will create a jira and investigate.
rameshthoomu (Wed, 02 Jan 2019 21:33:15 GMT):
@vijay.bP could you please point me the bug which you have created for fabric-chaincode-node failures
pandrejko (Wed, 02 Jan 2019 21:34:31 GMT):
@jtclark I opened jira https://jira.hyperledger.org/browse/FAB-13474 for the broken links. Could you look at #4 on the list in there. I think it is a false positive. We will address the others.
sambhavdutt (Wed, 02 Jan 2019 21:34:31 GMT):
@rameshthoomu
https://jira.hyperledger.org/browse/FAB-13462
rameshthoomu (Thu, 03 Jan 2019 04:27:17 GMT):
@sambhavdutt added comment in https://jira.hyperledger.org/browse/FAB-13457
rameshthoomu (Thu, 03 Jan 2019 04:27:50 GMT):
sdk-java tests are consistently failing when we use latest fabric images (i.e frm master branch)...
rameshthoomu (Thu, 03 Jan 2019 04:28:11 GMT):
but they are working when we use sdk-java configuration.. added comments in the bug.. pls check
sambhavdutt (Thu, 03 Jan 2019 04:29:41 GMT):
@rameshthoomu thank you, will modify sdk-java tests accordingly
rameshthoomu (Thu, 03 Jan 2019 04:29:53 GMT):
didn't get you..
rameshthoomu (Thu, 03 Jan 2019 04:30:09 GMT):
what you will modify?
sambhavdutt (Thu, 03 Jan 2019 04:31:17 GMT):
should I disable the sdk-java tests from the master branch for now
sambhavdutt (Thu, 03 Jan 2019 04:31:40 GMT):
in the e2e tests
rameshthoomu (Thu, 03 Jan 2019 04:32:43 GMT):
e2e and daily.. Yes
sambhavdutt (Thu, 03 Jan 2019 04:32:52 GMT):
ok
sambhavdutt (Thu, 03 Jan 2019 04:44:29 GMT):
Done
xaviarias (Thu, 03 Jan 2019 11:02:55 GMT):
Has joined the channel.
rameshthoomu (Thu, 03 Jan 2019 16:58:47 GMT):
@sambhavdutt Disabled fabric-sdk-java tests on master branch in e2e merge and daily jobs. This is a temporary change.. Will re-enable after we get an update on FABJ-397
sambhavdutt (Thu, 03 Jan 2019 16:59:50 GMT):
@rameshthoomu thank you , I will make a note
bretharrison (Thu, 03 Jan 2019 17:29:29 GMT):
What is the plan for running the `fabric-samples` build in master ? I am getting
```
19:54:19 Error: could not assemble transaction, err proposal response was not successful, error code 500, msg error starting container: error starting container: Failed to generate platform-specific docker build: Failed to pull hyperledger/fabric-ccenv:2.0.0: API error (404): manifest for hyperledger/fabric-ccenv:2.0.0 not found
19:54:19 !!!!!!!!!!!!!!! Chaincode instantiation on peer0.org2 on channel 'mychannel' failed !!!!!!!!!!!!!!!!
```
sambhavdutt (Thu, 03 Jan 2019 17:33:01 GMT):
@bretharrison
There is a CR in place to fix this issue, I'm adding tags for the 2.0.0 version, this specific error in BYFN tests will be fixed
https://gerrit.hyperledger.org/r/#/c/28368/
bretharrison (Thu, 03 Jan 2019 17:39:49 GMT):
thanks
bretharrison (Thu, 03 Jan 2019 18:55:15 GMT):
`fabric-node-sdk` release-1.3 build fails with
```
18:31:30 npm version ------> 5.6.0
18:31:30 node version ------> v8.11.3
18:31:30 [13:31:30] Local gulp not found in /w/workspace/fabric-sdk-node-verify-s390x/gopath/src/github.com/hyperledger/fabric-sdk-node
18:31:30 [13:31:30] Try running: npm install gulp
18:31:30 ERROR!!! gulp failed
```
sambhavdutt (Thu, 03 Jan 2019 18:56:48 GMT):
@bretharrison
I'll check if I can submit a fix/patch for this
bretharrison (Thu, 03 Jan 2019 19:02:13 GMT):
thanks
rameshthoomu (Thu, 03 Jan 2019 19:04:21 GMT):
@bretharrison see this error
```
13:34:05 node version ------> v8.11.3
13:34:05 npm notice created a lockfile as package-lock.json. You should commit this file.
13:34:05 npm WARN Invalid name: "fabric-sdk-node TESTING"
```
bretharrison (Thu, 03 Jan 2019 19:04:49 GMT):
thanks, did not see that
davidkhala (Fri, 04 Jan 2019 09:29:39 GMT):
package-lock is good, but always make CI failure, has it been added back now? @bretharrison
bretharrison (Fri, 04 Jan 2019 13:37:42 GMT):
@davidkhala no, i think it cause more problems than it solved
scottz (Fri, 04 Jan 2019 20:44:54 GMT):
@rameshthoomu @sambhavdutt please take a look at https://gerrit.hyperledger.org/r/#/c/28472/. Latitia created fabric-test release-1.4 branch and this is the patchset to get it all working. Sambhav, make sure your jenkins 1.4 daily/verify/merge jobs will work with the Makefile and pull scripts in her CR for the 1.4 branch.
rameshthoomu (Fri, 04 Jan 2019 20:48:34 GMT):
@scottz CI change for release-1.4 branch https://gerrit.hyperledger.org/r/#/c/28380/5/jjb/fabric-test/fabric-test-daily-job.yaml
rameshthoomu (Fri, 04 Jan 2019 20:48:53 GMT):
FYI
sambhavdutt (Fri, 04 Jan 2019 20:48:54 GMT):
@scottz
will check this,
The Jenkins patch is ready for fabric-test r-1.4
rodolfoleal (Sat, 05 Jan 2019 17:35:58 GMT):
Has joined the channel.
vijay.bP (Sat, 05 Jan 2019 19:04:44 GMT):
@rameshthoomu @gennadyl please review the patch https://gerrit.hyperledger.org/r/#/c/28497/
rameshthoomu (Sat, 05 Jan 2019 19:05:56 GMT):
Merged
sambhavdutt (Sun, 06 Jan 2019 18:20:37 GMT):
@rameshthoomu
Can you look into this when you are free and merge if ok,
https://gerrit.hyperledger.org/r/#/c/28501/
sstone1 (Tue, 08 Jan 2019 14:41:28 GMT):
@rameshthoomu the node SDK verify builds for master are failing with the following error... is it a known problem?
sstone1 (Tue, 08 Jan 2019 14:41:32 GMT):
```
14:34:39 # Proposal failed to end2endnodesdk :: Error: error starting container: error starting container: Failed to generate platform-specific docker build: Failed to pull hyperledger/fabric-ccenv:2.0.0: API error (404): manifest for hyperledger/fabric-ccenv:2.0.0 not found
```
sambhavdutt (Tue, 08 Jan 2019 14:44:58 GMT):
@sstone1
I can say this is not the first time this error happened, I'll check the jobs
sambhavdutt (Tue, 08 Jan 2019 14:44:58 GMT):
@sstone1
I can say it is is not the first time this error happened, I'll check the jobs
rameshthoomu (Tue, 08 Jan 2019 14:48:05 GMT):
I am not sure from when sdk-node tests are expecting ccenv images..
rameshthoomu (Tue, 08 Jan 2019 14:49:31 GMT):
@sstone1 could you please share the build# or the patchset?
sstone1 (Tue, 08 Jan 2019 14:50:49 GMT):
https://gerrit.hyperledger.org/r/#/c/28551/
sstone1 (Tue, 08 Jan 2019 14:50:56 GMT):
https://jenkins.hyperledger.org/job/fabric-sdk-node-verify-x86_64/1825/consoleFull
sstone1 (Tue, 08 Jan 2019 14:51:45 GMT):
the s390x build has the same problem
rameshthoomu (Tue, 08 Jan 2019 15:06:36 GMT):
@sstone1 root cause for the above issue is this change https://github.com/hyperledger/fabric/commit/fdd1c72eaf45bb987e407b57ba09d7ba72e5bc31#diff-c3b211cbb38006d86e2305da1240bf37
rameshthoomu (Tue, 08 Jan 2019 15:07:07 GMT):
Could you please add ccenv image here in your patchset https://github.com/hyperledger/fabric-sdk-node/blob/master/scripts/Jenkins_Scripts/CI_Script.sh#L129
sstone1 (Tue, 08 Jan 2019 15:09:55 GMT):
Will do @rameshthoomu, thanks for looking
rameshthoomu (Tue, 08 Jan 2019 15:12:50 GMT):
wait
rameshthoomu (Tue, 08 Jan 2019 15:14:20 GMT):
also, pls add `docker tag $NEXUS_URL/$ORG_NAME-$IMAGES:${IMAGE_TAG} $ORG_NAME-$IMAGES:${VERSION}` line after this https://github.com/hyperledger/fabric-sdk-node/blob/master/scripts/Jenkins_Scripts/CI_Script.sh#L144 and https://github.com/hyperledger/fabric-sdk-node/blob/master/scripts/Jenkins_Scripts/CI_Script.sh#L156
sstone1 (Tue, 08 Jan 2019 15:17:34 GMT):
we probably need the new nodeenv image as well
rameshthoomu (Tue, 08 Jan 2019 15:19:44 GMT):
yes.. could you pls add that as well
sstone1 (Tue, 08 Jan 2019 15:21:46 GMT):
done, let's see how it goes
sstone1 (Tue, 08 Jan 2019 15:33:22 GMT):
need baseos as well!
rameshthoomu (Tue, 08 Jan 2019 15:38:00 GMT):
:( we are not publishing baseos from nightly jobs to nexus..
rameshthoomu (Tue, 08 Jan 2019 15:38:06 GMT):
let us do that now..
rameshthoomu (Tue, 08 Jan 2019 15:38:06 GMT):
Will work on it now..
sstone1 (Tue, 08 Jan 2019 15:38:29 GMT):
thanks
sstone1 (Tue, 08 Jan 2019 15:38:30 GMT):
15:35:14 # Proposal failed to end2endnodesdk :: Error: error starting container: error starting container: manifest for hyperledger/fabric-baseos:2.0.0 not found
sstone1 (Tue, 08 Jan 2019 15:39:01 GMT):
i see baseos-0.4.14 is on the system from the logs
sstone1 (Tue, 08 Jan 2019 15:39:09 GMT):
has it got the wrong version number from somewhere?
sstone1 (Tue, 08 Jan 2019 15:39:45 GMT):
or is there a new baseos:2.0.0 image just not being published?
rameshthoomu (Tue, 08 Jan 2019 15:48:36 GMT):
baseos is now part of fabric like other images (peer. etc..)..
sstone1 (Tue, 08 Jan 2019 15:48:44 GMT):
gotcha
rameshthoomu (Tue, 08 Jan 2019 15:49:08 GMT):
@vijay.bP is pushing change to publish baseos from nightly jobs to nexus..
rameshthoomu (Tue, 08 Jan 2019 15:51:57 GMT):
Vijay please use this jira https://jira.hyperledger.org/browse/FABCI-261
rameshthoomu (Tue, 08 Jan 2019 18:01:34 GMT):
@sstone1 baseos is available in nexus3 with 2.0.0-stable for both x and z platforms..
rameshthoomu (Tue, 08 Jan 2019 18:01:46 GMT):
could you please include this in your patch
sstone1 (Tue, 08 Jan 2019 21:15:15 GMT):
@rameshthoomu will do, thanks for sorting that
sstone1 (Wed, 09 Jan 2019 09:28:41 GMT):
@rameshthoomu the x build now runs cleanly... but the z build aborts
sstone1 (Wed, 09 Jan 2019 09:29:53 GMT):
can see timeouts starting chaincode containers
sstone1 (Wed, 09 Jan 2019 09:30:54 GMT):
```
09:26:10 Archiving artifacts
[Pipeline] }
[Pipeline] // timestamps
[Pipeline] }
[Pipeline] // node
[Pipeline] }
[Pipeline] // timeout
[Pipeline] End of Pipeline
Timeout has been exceeded
Finished: ABORTED
```
sstone1 (Wed, 09 Jan 2019 09:30:57 GMT):
https://jenkins.hyperledger.org/job/fabric-sdk-node-verify-s390x/436/consoleFull
sstone1 (Wed, 09 Jan 2019 09:31:40 GMT):
any way to see what was going on - i can't see any docker logs in jenkins?
sambhavdutt (Wed, 09 Jan 2019 09:42:52 GMT):
@sstone1
The docker container logs are not available as of now, we can just access these two logs other than the full console output
https://jenkins.hyperledger.org/view/fabric-sdk-node/job/fabric-sdk-node-verify-s390x/436/artifact/gopath/src/github.com/hyperledger/fabric-sdk-node/node_modules/socks/yarn-error.log
sambhavdutt (Wed, 09 Jan 2019 09:43:10 GMT):
I see that the latest build passed now for z
sstone1 (Wed, 09 Jan 2019 09:44:15 GMT):
i can't see an up to date passing build?
sstone1 (Wed, 09 Jan 2019 09:44:17 GMT):
https://jenkins.hyperledger.org/view/fabric-sdk-node/job/fabric-sdk-node-verify-s390x/
sambhavdutt (Wed, 09 Jan 2019 09:48:14 GMT):
unfortunately no, but we are working to to get the container logs, we can't ssh into a ongoing build system for s390x, and the build data is purged after every run
sstone1 (Wed, 09 Jan 2019 10:03:13 GMT):
ah okay
sstone1 (Wed, 09 Jan 2019 10:03:17 GMT):
thanks for looking
sambhavdutt (Wed, 09 Jan 2019 10:04:00 GMT):
no probs
rameshthoomu (Wed, 09 Jan 2019 14:56:02 GMT):
@sstone1 could you please increase the buildtimeout to 50mins here https://github.com/hyperledger/fabric-sdk-node/blob/master/Jenkinsfile.x#L5
sstone1 (Wed, 09 Jan 2019 14:58:10 GMT):
should that be in Jenkinsfile.x or Jenkinsfile.z ?
rameshthoomu (Wed, 09 Jan 2019 14:58:32 GMT):
Change in both files..
sstone1 (Wed, 09 Jan 2019 14:58:36 GMT):
:+1:
sstone1 (Wed, 09 Jan 2019 14:59:06 GMT):
updated my CR
rameshthoomu (Wed, 09 Jan 2019 15:00:27 GMT):
I see this error in your patchset build log
```
03:55:50 # Proposal failed to e2enodecc :: Error: timeout expired while starting chaincode e2enodecc:v0 for transaction
03:55:50 # Proposal failed to e2enodecc :: Error: timeout expired while starting chaincode e2enodecc:v0 for transaction
03:5
```
sstone1 (Wed, 09 Jan 2019 15:01:25 GMT):
yeah i suspect there's a problem building the CC images
sstone1 (Wed, 09 Jan 2019 15:01:33 GMT):
but quite difficult to see what without the docker logs
sstone1 (Wed, 09 Jan 2019 16:31:26 GMT):
@rameshthoomu still fails... is there a z box i can get access to ?
rameshthoomu (Wed, 09 Jan 2019 17:25:25 GMT):
yes.. we can get access..
rameshthoomu (Wed, 09 Jan 2019 17:25:31 GMT):
give me the build#
sstone1 (Wed, 09 Jan 2019 17:26:06 GMT):
https://jenkins.hyperledger.org/job/fabric-sdk-node-verify-s390x/436/consoleFull
rameshthoomu (Wed, 09 Jan 2019 17:30:42 GMT):
triggered s390x job again.. checking the tests and logs in the machine
rameshthoomu (Wed, 09 Jan 2019 17:30:48 GMT):
will let u know
sstone1 (Wed, 09 Jan 2019 17:33:02 GMT):
thanks
swetha (Wed, 09 Jan 2019 20:26:59 GMT):
@rameshthoomu We are having issues pulling patches: https://jenkins.hyperledger.org/job/fabric-chaincode-evm-verify-x86_64/8/console. Is this related to https://gerrit.hyperledger.org/r/#/c/28373/
rameshthoomu (Wed, 09 Jan 2019 20:36:56 GMT):
checking
rameshthoomu (Wed, 09 Jan 2019 21:10:51 GMT):
Hi Swetha.. Seems there is an issue with this patch https://gerrit.hyperledger.org/r/#/c/28596/ - I triggered build in sandbox and I see below commits. Observed this https://gerrit.hyperledger.org/r/#/c/28597/ related change to this patch is missing from the log.
```
16:01:42 + git log -n6 --pretty=oneline --abbrev-commit
16:01:42 9414f93 FAB-13102 refactor to use new burrow evm
16:01:42 0a9fe21 FAB-13102 - update burrow to 0.23.3
16:01:42 19768da [FAB-13263] Update Fabric dependency to 1.4
16:01:42 97cb415 FAB-13435 Rename job name in Jenkinsfile
16:01:42 61bb885 FAB-13435 Update pipeline CI script on cc-evm
16:01:42 5f6f073 Configure Stale ProBot
```
swetha (Wed, 09 Jan 2019 22:19:10 GMT):
The second patch you linked depends on the first.
rameshthoomu (Wed, 09 Jan 2019 22:21:00 GMT):
I don't see any issue with the CI change.. it's working for other patchsets submitted to evm..
swetha (Wed, 09 Jan 2019 22:21:24 GMT):
We will try investigating more and let you know what we find
rameshthoomu (Wed, 09 Jan 2019 22:22:09 GMT):
yes. all 4 patchsets are linked each other.. but the 2nd patchset is missing from the first patchset build log
swetha (Wed, 09 Jan 2019 22:22:49 GMT):
Okay I think maybe some temporary git issue. All 4 patches are now able to get the patchset
vijay.bP (Thu, 10 Jan 2019 21:49:31 GMT):
@rickr https://gerrit.hyperledger.org/r/#/c/28641/ Patch was sucessfully merged and the changes are updated.
rickr (Thu, 10 Jan 2019 22:04:47 GMT):
@vijay.bP @rameshthoomu not sure what went wrong but I think it's still building the latest Fabric : https://jenkins.hyperledger.org/job/fabric-sdk-java-verify-x86_64/2575/console
rickr (Thu, 10 Jan 2019 22:06:37 GMT):
https://gerrit.hyperledger.org/r/#/c/28145/10/src/test/fabric_test_commitlevel.sh
vijay.bP (Thu, 10 Jan 2019 22:08:04 GMT):
@rickr The variable name is kept different in CI `$FABRIC_NO_BUILD"`
vijay.bP (Thu, 10 Jan 2019 22:08:13 GMT):
let me change this
rickr (Thu, 10 Jan 2019 22:10:03 GMT):
I got it!
davidkel (Fri, 11 Jan 2019 14:41:17 GMT):
Has left the channel.
sambhavdutt (Fri, 11 Jan 2019 16:11:57 GMT):
These the list of *fabric* Bugs in the last day's CI tests,
https://jira.hyperledger.org/browse/FAB-13634
https://jira.hyperledger.org/browse/FAB-12320
https://jira.hyperledger.org/browse/FAB-13635
https://jira.hyperledger.org/browse/FAB-13629
rameshthoomu (Fri, 11 Jan 2019 16:17:05 GMT):
@sambhavdutt don't use first time in the summary of the bug.. Keep that as a label
rameshthoomu (Fri, 11 Jan 2019 16:17:05 GMT):
@sambhavdutt don't use "first time" word in the summary of the bug.. Keep that as a label
sambhavdutt (Fri, 11 Jan 2019 16:17:38 GMT):
ok
dave.enyeart (Sun, 13 Jan 2019 18:44:46 GMT):
@sambhavdutt see my guidance about opening unit test failure bugs: https://jira.hyperledger.org/browse/FAB-13634?focusedCommentId=55581&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-55581
sambhavdutt (Sun, 13 Jan 2019 19:48:42 GMT):
@dave.enyeart thank you
sambhavdutt (Sun, 13 Jan 2019 19:51:51 GMT):
I'll update a flake with comments if a similar fail happens in different versions to avoid duplicate
davidkhala (Mon, 14 Jan 2019 02:06:38 GMT):
Has CI for sdk-node recovered?
sstone1 (Mon, 14 Jan 2019 10:28:48 GMT):
@davidkhala seems to be working for me :+1:
davidkhala (Mon, 14 Jan 2019 10:29:48 GMT):
Cool, I would retry on https://gerrit.hyperledger.org/r/#/c/28446/
rickr (Mon, 14 Jan 2019 15:08:06 GMT):
Seeing issues with uploading a patch to gerrit just gets stuck on command line @rameshthoomu @jtclark
rameshthoomu (Mon, 14 Jan 2019 15:09:04 GMT):
What is the issue? @vijay.bP could you please check
rickr (Mon, 14 Jan 2019 15:11:30 GMT):
after a long pause :
```
Connection to gerrit.hyperledger.org closed by remote host.
Connection to gerrit.hyperledger.org closed by remote host.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
```
rameshthoomu (Mon, 14 Jan 2019 15:13:27 GMT):
@rickr please post in #infra-support channel.. this seems network issue
vijay.bP (Mon, 14 Jan 2019 15:13:49 GMT):
@rameshthoomu @rickr Im trying to rebase on my machine, but gets stuck, same issue for me too, problem with gerrit let me check with other member's.
rameshthoomu (Mon, 14 Jan 2019 15:13:51 GMT):
getting the same error here..
lehors (Mon, 14 Jan 2019 17:15:04 GMT):
hi, is it ok to store in fabric/unit-test some test artifacts?
lehors (Mon, 14 Jan 2019 17:16:00 GMT):
specifically, I'm looking for a place to move some of the "examples" which really are not quite examples but test artifacts into a different, more meaningfully called, directory
lehors (Mon, 14 Jan 2019 17:16:00 GMT):
I'm looking for a place to move some of the "examples" which really are not quite examples but more like test artifacts into a different, more meaningfully called, director
lehors (Mon, 14 Jan 2019 17:16:00 GMT):
I'm looking for a place to move some of the "examples" which really are not quite examples but more like test artifacts into a different, more meaningfully called, directory
lehors (Mon, 14 Jan 2019 17:16:39 GMT):
I just don't know whether I should simple create a new directory such as test-artifacts or if unit-test is good for that
lehors (Mon, 14 Jan 2019 17:17:32 GMT):
I'm specifically referring to what's today under examples/chaincode and examples/plugins
lehors (Mon, 14 Jan 2019 17:18:33 GMT):
thanks
sykesm (Mon, 14 Jan 2019 18:27:07 GMT):
please don't put anything under unit-test; IMO, most of what's under examples should be killed with fire or moved to where they are used.
sykesm (Mon, 14 Jan 2019 18:27:34 GMT):
unit-test should also be removed; we don't use the compose file any longer and the script can be relocated to scripts
sykesm (Mon, 14 Jan 2019 18:27:44 GMT):
the miscellaneous references can then be updated
lehors (Mon, 14 Jan 2019 18:57:57 GMT):
ok, thanks for the input
lehors (Mon, 14 Jan 2019 18:58:33 GMT):
if something is used in a single place it's easy enough to put it there but for instance we have chaincode/go/example02 used about everywhere
lehors (Mon, 14 Jan 2019 18:58:47 GMT):
so, some central place is needed
lehors (Mon, 14 Jan 2019 18:59:48 GMT):
if anyone needs convincing, just run: git grep examples/chaincode/go/example0 :-)
lehors (Mon, 14 Jan 2019 18:59:48 GMT):
if anyone needs convincing, just run: git grep examples/chaincode/go/example02 :-)
dave.enyeart (Mon, 14 Jan 2019 19:16:10 GMT):
I don't see a problem with putting common chaincode artifacts in /test-artifacts directory, at least as a means to remove /examples until some larger test refactor occurs
dave.enyeart (Mon, 14 Jan 2019 19:16:10 GMT):
@lehors I don't see a problem with putting common chaincode artifacts in /test-artifacts directory, at least as a means to remove /examples until some larger test refactor occurs. See an issue @sykesm ?
sykesm (Mon, 14 Jan 2019 19:51:32 GMT):
@lehors @dave.enyeart Instead of moving the fixtures, let's do the right thing. Here are the references to example02 in current master:
```
$ ag -l 'go/example02'
core/chaincode/exectransaction_test.go
core/chaincode/platforms/golang/platform_test.go
core/common/ccprovider/ccinfocache_test.go
core/scc/lscc/lscc_test.go
core/handlers/validation/builtin/v12/validation_logic_test.go
core/handlers/validation/builtin/v13/validation_logic_test.go
docs/source/chaincode4noah.rst
docs/source/peer-chaincode-devmode.rst
peer/chaincode/install_test.go
peer/chaincode/upgrade_test.go
examples/chaincode/go/example02/cmd/main.go
examples/chaincode/go/example05/chaincode_test.go
examples/chaincode/go/example04/chaincode_test.go
```
I only see a few buckets.
1. The peer chaincode command tests
2. Documentation. (Which, IMO, should not be referencing these artifacts as they're not really user consumable and they don't show any best practices.)
3. The core/chaincode tests.
4. The ccprovider tests
5. Lifecycle tests
sykesm (Mon, 14 Jan 2019 19:51:32 GMT):
@lehors @dave.enyeart Instead of moving the fixtures, let's do the right thing. Here are the references to example02 in current master:
```
$ ag -l 'go/example'
core/chaincode/exectransaction_test.go
core/chaincode/platforms/golang/platform_test.go
core/container/dockercontroller/dockercontroller_test.go
core/common/ccprovider/ccinfocache_test.go
core/scc/lscc/lscc_test.go
core/handlers/validation/builtin/v12/validation_logic_test.go
core/handlers/validation/builtin/v13/validation_logic_test.go
docs/source/chaincode4noah.rst
docs/source/peer-chaincode-devmode.rst
peer/chaincode/upgrade_test.go
peer/chaincode/install_test.go
examples/chaincode/go/example02/cmd/main.go
examples/chaincode/go/example05/chaincode_test.go
examples/chaincode/go/example05/cmd/main.go
examples/chaincode/go/example04/cmd/main.go
examples/chaincode/go/example04/chaincode_test.go
examples/chaincode/go/example03/cmd/main.go
examples/chaincode/go/example01/cmd/main.go
```
I only see a few buckets.
1. The peer chaincode command tests
2. Documentation. (Which, IMO, should not be referencing these artifacts as they're not really user consumable and they don't show any best practices.)
3. The core/chaincode tests.
4. The ccprovider tests
5. Lifecycle tests
rickr (Mon, 14 Jan 2019 20:29:16 GMT):
@rameshthoomu I'm building the JSDK which is building Fabric 2.0 master but I'm seeing when invoking Node CC this >
```
peer Peer{ id: 184, name: peer0.org1.example.com, channelName: foo, url: grpcs://localhost:7051} status: 500, message: error starting container: error starting container: pull access denied for hyperledger/fabric-nodeenv, repository does not exist or may require 'docker login'
```
rickr (Mon, 14 Jan 2019 20:30:04 GMT):
Bret said you man know something about this ?
lehors (Mon, 14 Jan 2019 20:31:04 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=SBq3qTybETSmE82Kk) @sykesm so, what's "the right thing" in your opinion??
sambhavdutt (Mon, 14 Jan 2019 20:49:42 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=cb483zEHBxxYCGjF7) @rickr We need the `nodeenv` image in master branch now,
this can't be pulled from the docker-compose.yaml in the sdkintegration as the nodeenv image is not available on dockerhub yet, just on Nexus. If ok, I can get the nodeenv image from nexus, and tag it so it doesn't have to pull again during the test
sambhavdutt (Mon, 14 Jan 2019 20:49:42 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=cb483zEHBxxYCGjF7) @rickr We need the `nodeenv` image in master branch now,
this can't be pulled as the nodeenv image is not available on dockerhub yet, just on Nexus. If ok, I can get the nodeenv image from nexus, and tag it so it doesn't have to pull again during the test
sykesm (Mon, 14 Jan 2019 20:54:30 GMT):
@lehors the right thing is to
1. delete the stuff that's not actively referenced in code
2. remove doc references
3. evalute the tests and see what they're doing; My guess is that the vast majority are simply looking for assets that will compile - not run. That means we can have a 10 loc chaincode impl that lives with the test that needs the code.
4. Where we need actual running chaincode, consider if we can reference the integration/chaincode artifacts in the interim and open issues to remove that dependency
mbwhite (Tue, 15 Jan 2019 09:33:05 GMT):
Hello; FYI I'd like to raise an issue to get nodev10 added to the node builds; wanted to just raise it first here in case there are any major gotchas
rickr (Tue, 15 Jan 2019 14:30:39 GMT):
@sambhavdutt thx
rickr (Tue, 15 Jan 2019 17:35:10 GMT):
I tried to download the Node CC image from nexus locally on my system. However running node cc gets me :
```
```
rickr (Tue, 15 Jan 2019 17:35:10 GMT):
I tried to download the Node CC image from nexus locally on my system. However running node cc gets me :
```
```
rickr (Tue, 15 Jan 2019 17:35:20 GMT):
$docker logs 4edb51b79e3b
> example_cc@1.0.0 start /usr/local/src
> node chaincode.js "--peer.address" "peer0.org1.example.com:7052"
/usr/local/src/node_modules/grpc/src/grpc_extension.js:55
throw error;
^
Error: Failed to load gRPC binary module because it was not installed for the current system
Expected directory: node-v57-linux-x64-glibc
Found: [node-v57-linux-x64-musl]
This problem can often be fixed by running "npm rebuild" on the current system
Original error: Cannot find module '/usr/local/src/node_modules/grpc/src/node/extension_binary/node-v57-linux-x64-glibc/grpc_node.node'
at Object.
rickr (Tue, 15 Jan 2019 17:35:36 GMT):
@sambhavdutt @rameshthoomu ^^^
rickr (Tue, 15 Jan 2019 17:36:55 GMT):
```
docker pull nexus3.hyperledger.org:10001/hyperledger/fabric-nodeenv:amd64-2.0.0-stable&&docker tag nexus3.hyperledger.org:10001/hyperledger/fabric-nodeenv:amd64-2.0.0-stable hyperledger/fabric-nodeenv:amd64-latest&&docker tag nexus3.hyperledger.org:10001/hyperledger/fabric-javaenv:amd64-2.0.0-stable hyperledger/fabric-nodeenv
```
rickr (Tue, 15 Jan 2019 18:15:06 GMT):
@dave.enyeart ^^
rickr (Tue, 15 Jan 2019 18:31:05 GMT):
End2endNodeIT.setup:51->End2endIT.runFabricTest:211->End2endIT.runChannel:527 Not enough endorsers for instantiate :0endorser failed with error starting container: error starting container: pull access denied for hyperledger/fabric-nodeenv, repository does not exist or may require 'docker login'. Was verified:false
13:25:05
rickr (Tue, 15 Jan 2019 18:31:29 GMT):
https://jenkins.hyperledger.org/job/fabric-sdk-java-verify-x86_64/2591/console
rickr (Tue, 15 Jan 2019 18:31:47 GMT):
@sambhavdutt @rameshthoomu same errror
rameshthoomu (Tue, 15 Jan 2019 18:32:14 GMT):
CI patch is not yet merged..
rameshthoomu (Tue, 15 Jan 2019 18:32:17 GMT):
testing in sandbox
rameshthoomu (Tue, 15 Jan 2019 18:32:17 GMT):
testing your patch in sandbox
rickr (Tue, 15 Jan 2019 21:57:47 GMT):
Clipboard - January 15, 2019 4:57 PM
rickr (Tue, 15 Jan 2019 21:57:54 GMT):
test failed . https://jenkins.hyperledger.org/job/fabric-sdk-java-verify-x86_64/2592/consoleFull
but build marked success ?
https://gerrit.hyperledger.org/r/#/c/28665/
rameshthoomu (Tue, 15 Jan 2019 21:58:37 GMT):
oh that's strange..
rameshthoomu (Tue, 15 Jan 2019 21:58:39 GMT):
let me check
rameshthoomu (Tue, 15 Jan 2019 22:00:24 GMT):
Can you pls add -e or exit from ci_run.sh https://github.com/hyperledger/fabric-sdk-java/blob/master/src/test/cirun.sh
gaijinviki (Thu, 17 Jan 2019 04:45:12 GMT):
Has joined the channel.
SethiSaab (Thu, 17 Jan 2019 05:56:41 GMT):
HI Team
I am trying to setup channel manually
without ruunning byfn script
i am getting error while running this command peer channel create -o orderer.example.com:7050 -c $CHANNEL_NAME -f ./channel-artifacts/channel.tx --tls --cafile /opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem
to create channel
error i am getting s
Error: got unexpected status: BAD_REQUEST -- Attempted to include a member which is not in the consortium
rameshthoomu (Thu, 17 Jan 2019 14:25:20 GMT):
@sambhavdutt sdk-node merge jobs are failing consistently... please create bug and assign it to @bretharrison
sambhavdutt (Thu, 17 Jan 2019 14:28:10 GMT):
@rameshthoomu sure, I will create one for FABN
vijay.bP (Thu, 17 Jan 2019 16:03:57 GMT):
@rameshthoomu Please review the patch to fix the publish npm modules issue in node chaincode branch 1.4
vijay.bP (Thu, 17 Jan 2019 16:03:57 GMT):
@rameshthoomu Please review the patch to fix the publish npm modules issue in node chaincode branch 1.4
@mbwhite Need +2 for the CR https://gerrit.hyperledger.org/r/#/c/28785/
vijay.bP (Thu, 17 Jan 2019 16:03:57 GMT):
@rameshthoomu Please review the patch to fix the publish npm modules issue in node chaincode branch 1.4
@mbwhite Need +2 for the CR https://gerrit.hyperledger.org/r/#/c/28785/
vijay.bP (Thu, 17 Jan 2019 16:05:12 GMT):
@mbwhite Need +2 for the CR https://gerrit.hyperledger.org/r/#/c/28785/
mbwhite (Thu, 17 Jan 2019 16:37:26 GMT):
done :-)
rameshthoomu (Thu, 17 Jan 2019 19:41:40 GMT):
thanks @vijay.bP for the fix.. latest build passed after the fix
manish-sethi (Sun, 20 Jan 2019 02:10:57 GMT):
@rameshthoomu - my CR on release-1.1 is failing for an unrealed reason. Can you please have a look? - https://gerrit.hyperledger.org/r/#/c/28834/
sambhavdutt (Sun, 20 Jan 2019 03:10:41 GMT):
The manifest-tool is failing in the fabric gotools, there is an open bug for this
https://jira.hyperledger.org/browse/FAB-13715
dave.enyeart (Sun, 20 Jan 2019 19:18:25 GMT):
@sambhavdutt @manish-sethi release-1.1 gotools fix has been merged now
dave.enyeart (Sun, 20 Jan 2019 19:19:09 GMT):
rebased and rebuilding Manish's https://gerrit.hyperledger.org/r/#/c/28834/
dave.enyeart (Sun, 20 Jan 2019 19:19:56 GMT):
Onto a different issue... can sombody investigate why my second patch did not trigger CI? https://gerrit.hyperledger.org/r/#/c/28837/
vijay.bP (Sun, 20 Jan 2019 19:24:09 GMT):
@dave.enyeart Just give `VerifyBuild` Please refer this doc https://ci-docs.readthedocs.io/en/latest/source/fabric_ci_process.html
dave.enyeart (Sun, 20 Jan 2019 19:25:24 GMT):
Ramesh has mentioned to me before that either `VerifyBuild` or `Run VerifyBuild` works. But that's besides the point... the main problem is that when I uploaded patch 2 CI did not get triggered automatically.
rameshthoomu (Sun, 20 Jan 2019 19:28:35 GMT):
@dave.enyeart builds are in queue since sometime..
dave.enyeart (Sun, 20 Jan 2019 19:29:02 GMT):
it was instant for patch1 earlier today. why the queue later today?
rameshthoomu (Sun, 20 Jan 2019 19:29:12 GMT):
@tijohnson is it because of the recent patch merged in ci..
rameshthoomu (Sun, 20 Jan 2019 19:29:18 GMT):
Could you pls check
vijay.bP (Sun, 20 Jan 2019 19:30:58 GMT):
Big queue in prod
rameshthoomu (Sun, 20 Jan 2019 19:33:42 GMT):
@tijohnson you there?
rameshthoomu (Sun, 20 Jan 2019 19:37:14 GMT):
Seems Tim is not available.. @vijay.bP or @sambhavdutt Could you please create HL helpdesk ticket for the above issue
sambhavdutt (Sun, 20 Jan 2019 19:38:08 GMT):
@rameshthoomu
sure, will create now
sambhavdutt (Sun, 20 Jan 2019 19:53:27 GMT):
I have created a Helpdesk ticket for this with LF team,
we may have to wait for a while, got this reply
```
Greetings,
We are currently operating at reduced capacity and requests will be handled as quickly as possible. Your patience is appreciated as we adjust our resourcing levels.
```
rameshthoomu (Sun, 20 Jan 2019 19:53:57 GMT):
@tijohnson @jwagantall ^^
sambhavdutt (Sun, 20 Jan 2019 19:55:27 GMT):
ticket number
*[Hyperledger Helpdesk #67376]*
jwagantall (Mon, 21 Jan 2019 02:07:48 GMT):
fixed...
jwagantall (Mon, 21 Jan 2019 02:08:09 GMT):
looks like the builds are spinning now...
sambhavdutt (Mon, 21 Jan 2019 02:15:12 GMT):
@jwagantall
Thank you !
rameshthoomu (Mon, 21 Jan 2019 02:21:35 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=Q6wS6sX2YmhbcHWuh) @jwagantall THANK YOU
SethiSaab (Mon, 21 Jan 2019 06:23:34 GMT):
hi Guys i am getting the followingerror while integration Fabrci with AD
SethiSaab (Mon, 21 Jan 2019 06:23:34 GMT):
Error: POST failure of request: POST http://localhost:7054/enroll
{"hosts":["cz-1011"],"certificate_request":"-----BEGIN CERTIFICATE REQUEST-----\nMIIBPjCB5QIBADBeMQswCQYDVQQGEwJVUzEXMBUGA1UECBMOTm9ydGggQ2Fyb2xp\nbmExFDASBgNVBAoTC0h5cGVybGVkZ2VyMQ8wDQYDVQQLEwZGYWJyaWMxDzANBgNV\nBAMTBlJvYmVydDBZMBMGByqGSM49AgEGCCqGSM49AwEHA0IABL0aTZWfNaFfc3Wl\nNNvOG/qUlzVXijnYo0T7cQFynegrlCb7n6kXDXCzATWocz/ud8YFqzf5TsyG/Kr/\n7oR7clugJTAjBgkqhkiG9w0BCQ4xFjAUMBIGA1UdEQQLMAmCB2N6LTEwMTEwCgYI\nKoZIzj0EAwIDSAAwRQIhAMEb/rxX2H8MQEXS6Xakcnba+WL9NdcmHTwJVkXE+axg\nAiBRvYjDgK6yeAwzf9wT8QuZhBKlvJ0CLfBJsA6rcWpuiQ==\n-----END CERTIFICATE REQUEST-----\n","profile":"","crl_override":"","label":"","NotBefore":"0001-01-01T00:00:00Z","NotAfter":"0001-01-01T00:00:00Z","CAName":"","attr_reqs":[{"name":"hf.GenCRL"}]}: Post http://localhost:7054/enroll: dial tcp 127.0.0.1:7054: connect: connection refused
SethiSaab (Mon, 21 Jan 2019 06:23:40 GMT):
could someone pelase help me
SethiSaab (Mon, 21 Jan 2019 06:23:46 GMT):
Please*
rameshthoomu (Mon, 21 Jan 2019 14:27:27 GMT):
@vijay.bP Could you please work on this task https://jira.hyperledger.org/browse/FABCI-266
dave.enyeart (Mon, 21 Jan 2019 14:41:07 GMT):
@rameshthoomu Any ideas on https://jira.hyperledger.org/browse/FAB-13787 ? I just added a comment...
ycarmel (Tue, 22 Jan 2019 08:41:20 GMT):
Has joined the channel.
guoger (Tue, 22 Jan 2019 08:46:18 GMT):
is CI down? i'm getting `No Builds Executed`...
yacovm (Tue, 22 Jan 2019 10:33:13 GMT):
@rameshthoomu - https://gerrit.hyperledger.org/r/#/c/28692/ doesn't run the build despite trying to VerifyBuild... please help
sstone1 (Tue, 22 Jan 2019 10:38:03 GMT):
my builds are stuck on `Waiting for next available executor on ‘hyp-x’`
guoger (Tue, 22 Jan 2019 10:38:20 GMT):
same here :(
sstone1 (Tue, 22 Jan 2019 10:42:33 GMT):
seems to be two behave builds in jenkins that have been running for nearly 10hrs
hagarm (Tue, 22 Jan 2019 11:00:40 GMT):
Has joined the channel.
sambhavdutt (Tue, 22 Jan 2019 11:39:12 GMT):
@sstone1 @guoger
The CI x nodes are offline from 10 pm last night,
LF Helpdesk ticket has been created for this,
*[Hyperledger Helpdesk #67440]*
sstone1 (Tue, 22 Jan 2019 11:40:24 GMT):
thanks @sambhavdutt !
rameshthoomu (Tue, 22 Jan 2019 12:52:48 GMT):
@jwagantall @tijohnson Could you pls check this ASAP..
rameshthoomu (Tue, 22 Jan 2019 14:15:23 GMT):
@sambhavdutt did you get any update on HL ticket?
rameshthoomu (Tue, 22 Jan 2019 14:15:53 GMT):
I don't see any outage here https://status.linuxfoundation.org/
rameshthoomu (Tue, 22 Jan 2019 14:17:12 GMT):
@sstone1 @guoger @yacovm I don't have control to fix this issue. Waiting for their response.
sambhavdutt (Tue, 22 Jan 2019 14:19:40 GMT):
@rameshthoomu
I received the below message along with the helpdesk ticket number posted above at 10:47 PM EST last night, there are no updates after that
```
Greetings,
We are currently operating at reduced capacity and requests will be handled as quickly as possible. Your patience is appreciated as we adjust our resourcing levels.
Your support ticket regarding:
"Hyperledger X nodes are offline for over 60 minutes", has been entered in our ticket tracker.
```
Loofus (Tue, 22 Jan 2019 14:37:37 GMT):
Has joined the channel.
sambhavdutt (Tue, 22 Jan 2019 15:38:18 GMT):
It looks like the x nodes are online now,
I see that the jobs waiting in queue are triggered now
sambhavdutt (Tue, 22 Jan 2019 15:38:18 GMT):
It looks like the x nodes are online now,
I see that the jobs waiting in queue are triggered
rameshthoomu (Tue, 22 Jan 2019 16:07:23 GMT):
I don't know what
rameshthoomu (Tue, 22 Jan 2019 16:07:23 GMT):
I don't know what's going on.. we have almost 12 hrs outage..
bretharrison (Tue, 22 Jan 2019 16:53:02 GMT):
Help --- https://gerrit.hyperledger.org/r/#/c/28865/
sambhavdutt (Tue, 22 Jan 2019 17:00:13 GMT):
@bretharrison
There was an outage, the x nodes were offline for 12 hours from 10 PM last night. This job must have aborted after the timeout expired.
This has been retriggered now
bretharrison (Tue, 22 Jan 2019 17:00:25 GMT):
great, thanks
sambhavdutt (Tue, 22 Jan 2019 17:00:38 GMT):
no probs
rameshthoomu (Tue, 22 Jan 2019 17:03:06 GMT):
@harsha assigned this to you https://jira.hyperledger.org/browse/FABCI-34. Please add comments based on the current status
alokkv (Tue, 22 Jan 2019 17:10:45 GMT):
Has joined the channel.
vijay.bP (Wed, 23 Jan 2019 17:32:22 GMT):
@mbwhite Please look into this task https://jira.hyperledger.org/browse/FAB-13849
rameshthoomu (Wed, 23 Jan 2019 18:01:22 GMT):
After release cr is merged, we have to merge the prepare for the next release CR otherwise sdk-node and chaincode-node merge jobs will fail to publish npm modules on the same version..
sstone1 (Thu, 24 Jan 2019 10:20:54 GMT):
i seem to be having a problem with the x builds for the node SDK: https://jenkins.hyperledger.org/job/fabric-sdk-node-verify-x86_64/1921/console
sstone1 (Thu, 24 Jan 2019 10:21:08 GMT):
just seems to terminate pulling docker images
sstone1 (Thu, 24 Jan 2019 10:21:18 GMT):
no errors to go on - the z build is okay
rameshthoomu (Thu, 24 Jan 2019 11:49:40 GMT):
@sstone1 I think nightly cleanup job on nexus3 deleted x images.. @tijohnson any idea why the latest images deleted from nexus3
rameshthoomu (Thu, 24 Jan 2019 11:50:47 GMT):
Will publish them again.. Will let you know the update..
sstone1 (Thu, 24 Jan 2019 14:23:26 GMT):
thanks for taking a look @rameshthoomu
sambhavdutt (Thu, 24 Jan 2019 17:14:07 GMT):
Hello team,
Below are the list of active Bugs till date
Unit tests
https://jira.hyperledger.org/browse/FAB-13788
https://jira.hyperledger.org/browse/FAB-13821
https://jira.hyperledger.org/browse/FABCI-253 nvm compatability
https://jira.hyperledger.org/browse/FABN-1107 sdk-node
dave.enyeart (Thu, 24 Jan 2019 17:57:03 GMT):
@sambhavdutt The first one looks like a unit test flake that is happening more frequently, therefore I have raised to High priority. FYI @C0rWin
dave.enyeart (Thu, 24 Jan 2019 17:57:38 GMT):
The next two look like issues in the daily tests and CRs are already available in project ci-management
dave.enyeart (Thu, 24 Jan 2019 17:58:05 GMT):
How about the last one? Does it fail every CI job in fabric-sdk-node or is it intermittent?
sambhavdutt (Thu, 24 Jan 2019 18:01:13 GMT):
It is consistent esp on the x platform , intermittent on z
sambhavdutt (Thu, 24 Jan 2019 18:01:51 GMT):
there are few times it passed but not steady
vijay.bP (Thu, 24 Jan 2019 18:13:42 GMT):
@mbwhite Need +2 for this CR https://gerrit.hyperledger.org/r/#/c/28369/
rameshthoomu (Fri, 25 Jan 2019 15:08:24 GMT):
@vijay.bP Observed that DOCKER_NS is hardcoded to hyperledger in fabric-sdk-node docker-compose file (https://github.com/hyperledger/fabric-sdk-node/blob/release-1.4/test/fixtures/docker-compose.yaml#L10) Could you please create a bug to parametrize this so that we can pull images from any Name Space
vijay.bP (Fri, 25 Jan 2019 16:54:19 GMT):
@rameshthoomu @bretharrison Created a bug for the ^^request https://jira.hyperledger.org/browse/FABN-1119
knibals (Sun, 27 Jan 2019 14:08:49 GMT):
Has left the channel.
jd232 (Mon, 28 Jan 2019 12:43:44 GMT):
Has joined the channel.
vijay.bP (Mon, 28 Jan 2019 15:32:27 GMT):
@bretharrison @andrew-coleman Please look into this bug, merge build is failing with error in integration test https://jira.hyperledger.org/browse/FABN-1120
vijay.bP (Mon, 28 Jan 2019 15:45:46 GMT):
@mastersingh24 Please address the comment in https://jira.hyperledger.org/browse/FABCI-254
sambhavdutt (Mon, 28 Jan 2019 16:18:24 GMT):
These are the recent bugs on daily-unit-tests coverage, `flakes`
https://jira.hyperledger.org/browse/FAB-13923 unit-test release-1.4
https://jira.hyperledger.org/browse/FAB-13926 unit-test master
kostas (Tue, 29 Jan 2019 05:42:06 GMT):
Has joined the channel.
kostas (Tue, 29 Jan 2019 05:42:56 GMT):
I've always been curious about this. Why do we sometimes get a -1 vote on a test, even when the test passes? See https://gerrit.hyperledger.org/r/c/28885/ as an example.
kostas (Tue, 29 Jan 2019 05:43:06 GMT):
Screenshot 2019-01-29 at 00.41.39.png
vijay.bP (Tue, 29 Jan 2019 14:36:55 GMT):
@mbwhite Please look into this https://jira.hyperledger.org/browse/FAB-13849 merge job is unable to publish npm modules in node chaincode.
mbwhite (Tue, 29 Jan 2019 14:47:39 GMT):
will do .. thanks
mbwhite (Wed, 30 Jan 2019 15:48:23 GMT):
@vijay.bP CRs are in now in the 1.1, 1,2 and 1.3
rameshthoomu (Wed, 30 Jan 2019 16:42:07 GMT):
@sambhavdutt any open bug on this failure https://jenkins.hyperledger.org/view/Daily/job/fabric-unit-test-coverage-daily-master-s390x/?
sambhavdutt (Wed, 30 Jan 2019 16:44:47 GMT):
@rameshthoomu
yes,
https://jira.hyperledger.org/browse/FAB-13926
sambhavdutt (Wed, 30 Jan 2019 16:46:19 GMT):
this error `goroutine` is just observed in the *master* branch
vijay.bP (Thu, 31 Jan 2019 14:22:37 GMT):
@mbwhite I see merge job unable to publish npm modules for the CR merge in release-1.2, it has no overwrite property.
vijay.bP (Thu, 31 Jan 2019 16:16:56 GMT):
@dave.enyeart Could you please create a JIRA task for sending the email notification to developer when a merge is fail.
vijay.bP (Thu, 31 Jan 2019 16:17:23 GMT):
for all the repositories.
vijay.bP (Thu, 31 Jan 2019 16:28:06 GMT):
@mastersingh24 Please look into this https://jira.hyperledger.org/browse/FABCI-254
dave.enyeart (Thu, 31 Jan 2019 16:37:40 GMT):
@vijay.bP https://jira.hyperledger.org/browse/FABCI-282 - Send email to CR owner if CI merge job fails
dave.enyeart (Thu, 31 Jan 2019 16:38:57 GMT):
@vijay.bP I also posted in #fabric-maintainers to see if there is any disagreement
vijay.bP (Thu, 31 Jan 2019 16:39:30 GMT):
Kool
sykesm (Thu, 31 Jan 2019 19:46:46 GMT):
current master has an issue in test - one quick fix https://gerrit.hyperledger.org/r/c/29089/
tijohnson (Thu, 31 Jan 2019 20:54:11 GMT):
I will be performing an upgrade of Jenkins Sandbox tomorrow (Feb 01, 16:00 EST)
I have been advised to update all the plugins at the same time. One of the Pipeline plugins 'Pipeline: Supporting APIs' gave this warning:
_Warning: the new version of this plugin claims to use a different settings format than the installed version. Jobs using this plugin may need to be reconfigured, and/or you may not be able to cleanly revert to the prior version without manually restoring old settings. Consult the plugin release notes for details._
The other Pipeline Plugins had no warnings. Let me know if anyone is concerned about the warnings on the Pipeline Plugin.
This change is being tracked here: https://jira.linuxfoundation.org/browse/RELENG-1701
tijohnson (Thu, 31 Jan 2019 20:54:11 GMT):
I will be performing an upgrade of Jenkins Sandbox tomorrow (Feb 01, 16:00 EST)
I have been advised to update all the plugins at the same time. One of the Pipeline plugins 'Pipeline: Supporting APIs' gave this warning:
*Warning: the new version of this plugin claims to use a different settings format than the installed version. Jobs using this plugin may need to be reconfigured, and/or you may not be able to cleanly revert to the prior version without manually restoring old settings. Consult the plugin release notes for details.*
The other Pipeline Plugins had no warnings. Let me know if anyone is concerned about the warnings on the Pipeline Plugin.
This change is being tracked here: https://jira.linuxfoundation.org/browse/RELENG-1701
rameshthoomu (Thu, 31 Jan 2019 20:55:35 GMT):
Thanks @tijohnson what is the downtime?
tijohnson (Thu, 31 Jan 2019 20:57:22 GMT):
@rameshthoomu The downtime will be about 1hr (I will have to wait for the running jobs to complete)
rameshthoomu (Thu, 31 Jan 2019 20:58:10 GMT):
Is it possible to make it at 6:00 PM EST
tijohnson (Thu, 31 Jan 2019 20:59:33 GMT):
no I need to have help available if I have any problems
tijohnson (Thu, 31 Jan 2019 21:00:33 GMT):
4PM The Sandbox is pretty quiet
tijohnson (Fri, 01 Feb 2019 16:39:17 GMT):
Maintenance Downtime: 1H
Time: Today 16:00 EST
Effected Systems: All Hyperledeger CI Systems:
- gerrit - jira - jenkins (prod, sandbox) - nexus - wiki - chat
The OS on each of these systems will be upgraded
A version of Jenkins will also be upgraded
rameshthoomu (Fri, 01 Feb 2019 16:39:42 GMT):
@dave.enyeart FYI
sambhavdutt (Fri, 01 Feb 2019 16:39:58 GMT):
@tijohnson
Thanks for the update
sambhavdutt (Fri, 01 Feb 2019 17:31:33 GMT):
These are the list of recent bugs till date,
https://jira.hyperledger.org/browse/FAB-14030 unit-test-coverage
https://jira.hyperledger.org/browse/FAB-14031 unit-test-coverage
https://jira.hyperledger.org/browse/FAB-14032 daily-e2e v1.1
https://jira.hyperledger.org/browse/FAB-13672 Gradle , cc-java
rameshthoomu (Fri, 01 Feb 2019 17:46:54 GMT):
@tijohnson could you please @here... to post important updates.. or send out an email to mailing list
rameshthoomu (Fri, 01 Feb 2019 17:46:54 GMT):
@tijohnson could you please @here... to post important updates.. and send out an email to mailing list
ftd3 (Fri, 01 Feb 2019 19:27:21 GMT):
Has joined the channel.
tijohnson (Fri, 01 Feb 2019 20:17:49 GMT):
@rameshthoomu Sure
rameshthoomu (Fri, 01 Feb 2019 20:25:30 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=Jc98BrMFYRq52hihY) @tijohnson @dave.enyeart FYI
tijohnson (Fri, 01 Feb 2019 20:36:49 GMT):
@all Maintenance Downtime Starting
I am disabling the Jenkins queues on Production & Sandbox The existing jobs will be allowed to complete
MHBauer (Fri, 01 Feb 2019 21:04:13 GMT):
how long is this going to take?
vijay.bP (Fri, 01 Feb 2019 21:05:20 GMT):
Maintenance Downtime: 1H
MHBauer (Fri, 01 Feb 2019 21:06:09 GMT):
ah, I thought that mean, like, scheduled for first half of the year.
MHBauer (Fri, 01 Feb 2019 21:06:27 GMT):
got it now, but if you could write out the word hour, that would help.
MHBauer (Fri, 01 Feb 2019 21:06:31 GMT):
thanks.
tijohnson (Fri, 01 Feb 2019 22:43:25 GMT):
@all
All systems are back on-line and the Jenkins queues are accepting jobs
rameshthoomu (Sat, 02 Feb 2019 00:38:54 GMT):
Thanks @tijohnson for the update
tijohnson (Sun, 03 Feb 2019 18:51:10 GMT):
@rameshthoomu @jwagantall
I need you (Ramesh) to track my progress on the cleanup of docker.sandbox: https://jira.linuxfoundation.org/browse/RELENG-1669
Please add yourself as a watcher
I have generated a list of docker images that I would like to delete (the first 100 of 438)
because they lack some info, they have to be handled as a special case Please validate that all of these can be deleted
rameshthoomu (Mon, 04 Feb 2019 15:40:25 GMT):
@tijohnson please delete the list of images referred in above jira task..
sstone1 (Tue, 05 Feb 2019 14:05:25 GMT):
@rameshthoomu can you look at this Node SDK build failure please?
sstone1 (Tue, 05 Feb 2019 14:05:26 GMT):
https://jenkins.hyperledger.org/job/fabric-sdk-node-verify-s390x/546/console
sstone1 (Tue, 05 Feb 2019 14:05:34 GMT):
```
14:01:15 + ./CI_Script.sh --sdk_E2e_Tests
14:01:15 -------> ARCH: s390x
14:01:15 nvm is not compatible with the npm config "prefix" option: currently set to "/usr/local"
14:01:15 Run `npm config delete prefix` or `nvm use --delete-prefix v6.9.5 --silent` to unset it.
```
sstone1 (Tue, 05 Feb 2019 14:07:12 GMT):
x86_64 build seems to be running just fine
rameshthoomu (Tue, 05 Feb 2019 14:16:20 GMT):
@vijay.bP @sambhavdutt Could you please check this
sambhavdutt (Tue, 05 Feb 2019 14:18:17 GMT):
@rameshthoomu
I will look into this and let you know
vijay.bP (Tue, 05 Feb 2019 14:41:20 GMT):
@rameshthoomu prefix option was currently set to "/usr/local", it should change to /etc/profile.d/
rameshthoomu (Tue, 05 Feb 2019 14:42:19 GMT):
I don;t think so.. but you can test this in sandbox
vijay.bP (Tue, 05 Feb 2019 14:43:13 GMT):
on s390x machine
rameshthoomu (Tue, 05 Feb 2019 15:47:03 GMT):
@vijay.bP any update on the above issue?
vijay.bP (Tue, 05 Feb 2019 15:48:43 GMT):
I think that has to be change on s390x machine
rameshthoomu (Tue, 05 Feb 2019 17:10:09 GMT):
@sambhavdutt I see many depricated warnings in fabric-sdk-node builds on master branch. Could you please create a bug for this
rameshthoomu (Tue, 05 Feb 2019 17:54:57 GMT):
@sstone1 issue is fixed now.. Got +1 on the patchset..
rameshthoomu (Tue, 05 Feb 2019 18:58:32 GMT):
@sambhavdutt Could you please check this https://jira.hyperledger.org/browse/FABCI-285
sambhavdutt (Tue, 05 Feb 2019 19:00:19 GMT):
@rameshthoomu
will check this soon
SethiSaab (Wed, 06 Feb 2019 11:20:02 GMT):
@tijohnson HI
sambhavdutt (Wed, 06 Feb 2019 16:19:49 GMT):
@skarim
Can you take a look at this CR for `fabric-ca` and give your inputs if any,
https://gerrit.hyperledger.org/r/#/c/29057/
tijohnson (Wed, 06 Feb 2019 16:44:48 GMT):
@skarim Sure
skarim (Wed, 06 Feb 2019 16:46:53 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=gEoYqL4rrPPR9bbc9) @sambhavdutt It looks good to me
sambhavdutt (Wed, 06 Feb 2019 16:49:10 GMT):
@skarim thank you
@jwagantall @rameshthoomu
Can you approve this CR if it is fine, I have addressed the comments,
https://gerrit.hyperledger.org/r/#/c/29057/
sambhavdutt (Wed, 06 Feb 2019 16:49:10 GMT):
@skarim thank you
@jwagantall @rameshthoomu
Can you approve this CR if it is fine, I have addressed the comments,
https://gerrit.hyperledger.org/r/#/c/29057/
rameshthoomu (Thu, 07 Feb 2019 14:19:08 GMT):
@sambhavdutt @vijay.bP Could you please check fabric-sdk-node merge builds on master branch
Jonra1993 (Thu, 07 Feb 2019 14:32:32 GMT):
Has joined the channel.
sambhavdutt (Thu, 07 Feb 2019 16:44:22 GMT):
The fabric-ca tests are breaking in the fvt tests, I have communivcated this, this should be fixed soon, we can overlook the fabric-ca patchsets failing in the `fvt` tests for now
https://jira.hyperledger.org/browse/FABC-812
sambhavdutt (Thu, 07 Feb 2019 16:44:22 GMT):
The fabric-ca tests are breaking in the fvt tests, I have communicated this and should be fixed soon, we can overlook the fabric-ca patchsets failing in the `fvt` tests for now
https://jira.hyperledger.org/browse/FABC-812
vijay.bP (Thu, 07 Feb 2019 16:55:51 GMT):
@bretharrison https://jira.hyperledger.org/browse/FABN-1129 fabric-sdk-node merge job fail, please look into this.
vijay.bP (Thu, 07 Feb 2019 19:35:36 GMT):
@tijohnson As a part of the discussion in meeting, there's a nexus maintenance happening tomorrow, that doesn't relate to deleting the images right?
vijay.bP (Thu, 07 Feb 2019 22:35:13 GMT):
@tijohnson Addressed the comments for this patch, please check by mistake i posted comments instead of reply https://gerrit.hyperledger.org/r/#/c/28606/15
tijohnson (Thu, 07 Feb 2019 23:03:49 GMT):
@vijay.bP Turns out there is NO need for restarting Nexus.
tijohnson (Thu, 07 Feb 2019 23:06:22 GMT):
@vijay.bP RE: 28606 lets talk instead of lobbing comments
vijay.bP (Thu, 07 Feb 2019 23:07:35 GMT):
Sure @tijohnson
tijohnson (Thu, 07 Feb 2019 23:09:13 GMT):
Right now: I can hangout or you can zoom or we can call don't think we really need to share screen
tijohnson (Thu, 07 Feb 2019 23:09:13 GMT):
@vijay.bP Right now? I can hangout or you can zoom or we can call don't think we really need to share screen
vijay.bP (Thu, 07 Feb 2019 23:09:58 GMT):
Ok l setup now, let me send you the link.
vijay.bP (Thu, 07 Feb 2019 23:10:59 GMT):
@tijohnson
https://zoom.us/j/598097746
sambhavdutt (Fri, 08 Feb 2019 20:19:56 GMT):
For your information, The Jenkins jobs are waiting in queue as the x nodes are offline, You may expect delay if you submit your patch to Gerrit now,
A helpdesk ticket has been created for this, *[Hyperledger Helpdesk #68271]*
hexiaohu (Sat, 09 Feb 2019 10:18:42 GMT):
Has joined the channel.
vijay.bP (Mon, 11 Feb 2019 16:26:58 GMT):
@bretharrison @Andrew Coleman Please look into this, node-sdk merge job fail consistent https://jira.hyperledger.org/browse/FABN-1131
vijay.bP (Mon, 11 Feb 2019 16:26:58 GMT):
@bretharrison @andrew-coleman Please look into this, node-sdk merge job fail consistent https://jira.hyperledger.org/browse/FABN-1131
bretharrison (Mon, 11 Feb 2019 17:05:31 GMT):
@vijay.bP thanks, I will work on a fix
bretharrison (Mon, 11 Feb 2019 22:13:24 GMT):
Something is wrong with the S390 NodeSDK build
```
20:29:24 + ./CI_Script.sh --sdk_E2e_Tests
20:29:24 -------> ARCH: s390x
20:29:24 ------> Install NodeJS
20:29:24 ------> Use 8.14.0
20:29:25 v8.14.0 is already installed.
20:29:25 Now using node v8.14.0 (npm v3.10.10)
...
20:32:12 npm version ------> 3.10.10
20:32:12 node version ------> v6.9.5
```
It is not picking up the correct node version
bretharrison (Mon, 11 Feb 2019 22:13:24 GMT):
Something is wrong with the S390 NodeSDK build
```
20:29:24 + ./CI_Script.sh --sdk_E2e_Tests
20:29:24 -------> ARCH: s390x
20:29:24 ------> Install NodeJS
20:29:24 ------> Use 8.14.0
20:29:25 v8.14.0 is already installed.
20:29:25 Now using node v8.14.0 (npm v3.10.10)
...
20:32:12 npm version ------> 3.10.10
20:32:12 node version ------> v6.9.5
```
It is not picking up the correct node version
Also the NPM version is not correct it should be 6.4.1
rameshthoomu (Mon, 11 Feb 2019 22:32:52 GMT):
@sambhavdutt or @vijay.bP could you please check with @eddie.allen on this
rameshthoomu (Mon, 11 Feb 2019 22:33:10 GMT):
recently he modified the nvmrc.sh in s390x nodes..
sambhavdutt (Mon, 11 Feb 2019 22:34:46 GMT):
@rameshthoomu
Yes, I'll check
rameshthoomu (Tue, 12 Feb 2019 14:15:14 GMT):
@sambhavdutt or @vijay.bP please check with eddie on s390x
sambhavdutt (Tue, 12 Feb 2019 14:16:10 GMT):
sure, I will check with him in some time
sambhavdutt (Tue, 12 Feb 2019 14:35:08 GMT):
Hello team
These are the list of open bugs as of today, please let me know if you are not able to view this JIRA filter link
https://jira.hyperledger.org/browse/FAB-13536?filter=12705
sambhavdutt (Tue, 12 Feb 2019 14:35:08 GMT):
Hello team
These are the list of open bugs as of today, please let me know if you are not able to view this JIRA filter link
https://jira.hyperledger.org/issues/?filter=12705
eddie.allen (Tue, 12 Feb 2019 14:35:59 GMT):
@vijay.bP try using this instead of `npm config set prefix ~/npm`:
```
npm config set prefix $NVM_DIR/versions/node/v$NODE_VER
```
vijay.bP (Tue, 12 Feb 2019 14:39:54 GMT):
@eddie.allen Thanks, let me test it on.
sstone1 (Tue, 12 Feb 2019 15:03:59 GMT):
@vijay.bP @eddie.allen I've just got the following on my Node SDK s390x build:
```
ERROR: missing workspace /w/workspace/fabric-sdk-node-verify-s390x/gopath/src/github.com/hyperledger/fabric-sdk-node/scripts/Jenkins_Scripts on ubuntu1604-s390x-2c-16g-22
Finished: FAILURE
```
sstone1 (Tue, 12 Feb 2019 15:04:07 GMT):
https://jenkins.hyperledger.org/job/fabric-sdk-node-verify-s390x/605/console
vijay.bP (Tue, 12 Feb 2019 15:11:17 GMT):
Looking into it^^.
rameshthoomu (Tue, 12 Feb 2019 15:14:26 GMT):
@vijay.bP Could you please create a bug to "cleanup the workspace after the pipeline job complete"
vijay.bP (Tue, 12 Feb 2019 15:42:08 GMT):
@eddie.allen Tried with this `npm config set prefix $NVM_DIR/versions/node/v$NODE_VER` still getting the same error.
sstone1 (Tue, 12 Feb 2019 19:33:10 GMT):
it worked on an earlier master CR, but a release-1.4 CR hits this problem again:
```
ERROR: missing workspace /w/workspace/fabric-sdk-node-verify-s390x/gopath/src/github.com/hyperledger/fabric-sdk-node/scripts/Jenkins_Scripts on ubuntu1604-s390x-2c-16g-22
Finished: FAILURE
```
do you need to do anything for the different branches @vijay.bP ?
vijay.bP (Tue, 12 Feb 2019 19:35:29 GMT):
@sstone1 Acutually its' not the problem with sdk-node branches, some of the s390x minions having problem, we're working on it.
rameshthoomu (Tue, 12 Feb 2019 19:36:39 GMT):
@tijohnson Could you please disable ubuntu1604-s390x-2c-16g-22 from prod build node pool..
rameshthoomu (Tue, 12 Feb 2019 19:37:00 GMT):
I see the same node is available in sandbox and we are making changes on this..
tijohnson (Tue, 12 Feb 2019 20:32:06 GMT):
@ramesh I assume what you mean is 'Disconnect' ?
rameshthoomu (Tue, 12 Feb 2019 20:32:14 GMT):
yes
tijohnson (Tue, 12 Feb 2019 20:33:03 GMT):
done
rameshthoomu (Tue, 12 Feb 2019 20:33:10 GMT):
ok ty
vijay.bP (Wed, 13 Feb 2019 16:58:53 GMT):
@SriramaSharma Any update on this please https://gerrit.hyperledger.org/r/#/c/27953/
miloradtrninic (Wed, 13 Feb 2019 21:29:59 GMT):
Has joined the channel.
sambhavdutt (Thu, 14 Feb 2019 14:36:33 GMT):
These are the list of open bugs as of today,
https://jira.hyperledger.org/browse/FAB-13997
https://jira.hyperledger.org/issues/?filter=12705
rameshthoomu (Fri, 15 Feb 2019 14:27:07 GMT):
@nkl199 Did you create this file https://github.com/hyperledger/fabric-sdk-node/blob/master/test/scenario/chaincode/fabcar/node/metadata/.noignore intentionally? I see license check failure.. If this is intentional we have to exclude this file from license check.. https://github.com/hyperledger/fabric-sdk-node/blob/master/scripts/check_license.sh#L9
rameshthoomu (Fri, 15 Feb 2019 14:30:57 GMT):
https://jira.hyperledger.org/browse/FABN-1147
dave.enyeart (Sun, 17 Feb 2019 17:54:04 GMT):
I'm seeing failures in fabric-baseimage CI:
dave.enyeart (Sun, 17 Feb 2019 17:54:10 GMT):
`make: *** No rule to make target 'docker'. Stop.`
dave.enyeart (Sun, 17 Feb 2019 17:54:27 GMT):
See https://gerrit.hyperledger.org/r/#/c/29345/ and https://gerrit.hyperledger.org/r/#/c/29346/
rameshthoomu (Mon, 18 Feb 2019 01:24:48 GMT):
Will check
rameshthoomu (Mon, 18 Feb 2019 02:29:28 GMT):
baseimage jobs are unable to cherry-pick the change in both x and z. Not sure why it's unable to clone the files.. @sambhavdutt found a workaround for this.. He will push the change soon to sandbox
sambhavdutt (Mon, 18 Feb 2019 20:10:47 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=5xCj25dh9z8iaW9f3) @dave.enyeart The CR for the baseimage was merged,
I have retriggerd your baseimage CRs
rameshthoomu (Mon, 18 Feb 2019 20:30:07 GMT):
s390x build will fail due to java version mismatch.. See Sreerama fix here https://gerrit.hyperledger.org/r/#/c/27953/
dave.enyeart (Tue, 19 Feb 2019 15:01:04 GMT):
@rameshthoomu I've +1ed the java update now. Note that +2 privilege is not working today. I've emailed helpdesk about it. We'll want to rebase https://gerrit.hyperledger.org/r/#/c/27953/ and ensure it passes CI now.
rameshthoomu (Tue, 19 Feb 2019 15:06:48 GMT):
ok
dave.enyeart (Tue, 19 Feb 2019 15:37:10 GMT):
@rameshthoomu +2 privilege is back. It was already up to date. I've done +2 and `reverify`
houqinghui (Wed, 20 Feb 2019 06:48:35 GMT):
Has joined the channel.
houqinghui (Wed, 20 Feb 2019 06:49:13 GMT):
Hello, fabric contritutors, how many chaincodes does one fabric channel deploy?
sambhavdutt (Wed, 20 Feb 2019 18:51:49 GMT):
The BYFN tests have been failing in fabric, Can someone take a look ath this
https://jira.hyperledger.org/browse/FAB-14271
sambhavdutt (Wed, 20 Feb 2019 18:51:49 GMT):
The BYFN tests have been failing in fabric, Can someone take a look at this
https://jira.hyperledger.org/browse/FAB-14271
sambhavdutt (Wed, 20 Feb 2019 18:51:49 GMT):
The BYFN tests have been failing in fabric e2e tests, Can someone take a look at this
https://jira.hyperledger.org/browse/FAB-14271
rameshthoomu (Wed, 20 Feb 2019 18:56:25 GMT):
@jyellick ^^
jyellick (Wed, 20 Feb 2019 19:03:01 GMT):
Ah, yes @rameshthoomu we need to update that configtx.yaml
jyellick (Wed, 20 Feb 2019 19:10:41 GMT):
https://gerrit.hyperledger.org/r/c/29421/
bpbuch (Wed, 20 Feb 2019 21:08:10 GMT):
Has joined the channel.
bpbuch (Wed, 20 Feb 2019 21:17:58 GMT):
Hi - Can anyone provide guidance on setting up ci for the fabric-cli repo ?
rameshthoomu (Wed, 20 Feb 2019 22:24:12 GMT):
hi @bpbuch I can help you on this..
rameshthoomu (Thu, 21 Feb 2019 14:19:08 GMT):
@yacovm observed consistent unit-test (TestLeaderYield) failure in release-1.4 https://jira.hyperledger.org/browse/FAB-14030
yacovm (Fri, 22 Feb 2019 09:33:03 GMT):
@rameshthoomu this CR https://gerrit.hyperledger.org/r/#/c/29477/ isn't building :(
sstone1 (Fri, 22 Feb 2019 11:44:28 GMT):
same for my CR https://gerrit.hyperledger.org/r/#/c/29480/
sstone1 (Fri, 22 Feb 2019 12:53:11 GMT):
woo, it ran, but the x build failed with git errors: https://jenkins.hyperledger.org/job/fabric-sdk-node-verify-x86_64/2087/console
sstone1 (Fri, 22 Feb 2019 13:16:18 GMT):
resubmitted it and it's okay now: https://jenkins.hyperledger.org/job/fabric-sdk-node-verify-x86_64/2090/console
kostas (Fri, 22 Feb 2019 14:53:20 GMT):
Has left the channel.
rameshthoomu (Fri, 22 Feb 2019 15:51:41 GMT):
Unable to build fabric-ca-client binary.. make dist-all command on fabric-ca is failing https://jira.hyperledger.org/browse/FABC-824
rameshthoomu (Fri, 22 Feb 2019 15:52:02 GMT):
@scottz I have informed Saad on this.. he is looking into the issue..
rameshthoomu (Fri, 22 Feb 2019 20:16:26 GMT):
@jyellick Could you please look into this failure https://jira.hyperledger.org/browse/FAB-14317
nekia (Mon, 25 Feb 2019 07:47:24 GMT):
Hi I have a question about [fabric-test-daily-behave](https://jenkins.hyperledger.org/view/fabric-test/search/?q=behave). Some of them seem to have been failed since about a month before. Currently I'm trying to setup testing environment for my custom fabric-peer image, which is based on fabric v1.4.0, to run behave test locally. How can I create a testing environment which complete to run these behave tests without error.
rameshthoomu (Mon, 25 Feb 2019 14:19:14 GMT):
@nekia please post the same in #fabric-quality channel
nekia (Mon, 25 Feb 2019 22:41:48 GMT):
Thanks @rameshthoomu . OK, I got it.
sstone1 (Tue, 26 Feb 2019 15:53:39 GMT):
@rameshthoomu my z builds seem to be failing with random errors: https://jenkins.hyperledger.org/job/fabric-sdk-node-verify-s390x/720/consoleFull
sstone1 (Tue, 26 Feb 2019 15:53:50 GMT):
various network errors - ECONNRESET, stream removed, etc
sstone1 (Tue, 26 Feb 2019 15:53:55 GMT):
is the z build machine healthy?
rameshthoomu (Tue, 26 Feb 2019 15:58:18 GMT):
@sambhavdutt Could you please check.. https://jenkins.hyperledger.org/job/fabric-sdk-node-verify-s390x/720/artifact/gopath/src/github.com/hyperledger/fabric-sdk-node/orderer.log
sambhavdutt (Tue, 26 Feb 2019 15:59:04 GMT):
@rameshthoomu yes, I'll check on this
sambhavdutt (Tue, 26 Feb 2019 16:14:38 GMT):
I see that the three builds triggered for this patchset have one common fail, the orderer container is not available/down during the tests
rameshthoomu (Tue, 26 Feb 2019 16:18:30 GMT):
Could you please check why the orderer is not available.. Also, is it possible to print docker ps after docker-ready gulp task..
sambhavdutt (Tue, 26 Feb 2019 16:20:45 GMT):
yes, these 3 builds were triggered on the same z machine which is good, so this may nt be the problem with the z machines
sambhavdutt (Tue, 26 Feb 2019 16:20:45 GMT):
yes, these 3 builds were triggered on the same z machine which is good, so this may not be the problem with the z machines
rameshthoomu (Tue, 26 Feb 2019 16:20:54 GMT):
There is no information on what containers are up and running..
rameshthoomu (Tue, 26 Feb 2019 16:21:56 GMT):
try to add `docker ps -a` here https://github.com/hyperledger/fabric-sdk-node/blob/master/build/tasks/test.js#L113
rameshthoomu (Tue, 26 Feb 2019 16:22:14 GMT):
I mean after that line and see which containers are up and running..
rameshthoomu (Tue, 26 Feb 2019 16:22:39 GMT):
Also, do you know why the container logs are not showing up in buildArtifacts?
sambhavdutt (Tue, 26 Feb 2019 16:46:34 GMT):
let me check why the containers are not running
rameshthoomu (Tue, 26 Feb 2019 20:59:05 GMT):
@sstone1 I am seeing TLS handshake errors in peer logs
```
2019-02-26 20:46:21.912 UTC [nodeCmd] registerDiscoveryService -> INFO 01e Discovery service activated
2019-02-26 20:46:21.912 UTC [nodeCmd] serve -> INFO 01f Starting peer with ID=[name:"peer0.org2.example.com" ], network ID=[dev], address=[peer0.org2.example.com:8051]
2019-02-26 20:46:21.912 UTC [nodeCmd] serve -> INFO 020 Started peer with ID=[name:"peer0.org2.example.com" ], network ID=[dev], address=[peer0.org2.example.com:8051]
2019-02-26 20:46:24.903 UTC [gossip.discovery] func1 -> WARN 021 Could not connect to Endpoint: 127.0.0.1:7051, InternalEndpoint: 127.0.0.1:7051, PKI-ID:
sstone1 (Wed, 27 Feb 2019 10:38:18 GMT):
@rameshthoomu @sambhavdutt thanks for looking - turns out there's expired certs in the SDK tests, we're looking at fixing - no idea why it hit Z and not X yesterday, but is hitting both Z and X this morning.
sstone1 (Wed, 27 Feb 2019 10:38:25 GMT):
guess the clocks aren't in sync?
sambhavdutt (Wed, 27 Feb 2019 15:44:37 GMT):
Please find the list of recent and ongoing Bugs in the JIRA link,
https://jira.hyperledger.org/issues/?filter=12705
firas.qutishat (Wed, 27 Feb 2019 20:48:39 GMT):
@rameshthoomu when I set GO_TAGS env variable and build peer images I see go install -tags "" is empty
firas.qutishat (Wed, 27 Feb 2019 20:48:39 GMT):
@rameshthoomu when I set GO_TAGS env variable and build peer image I see go install -tags "" is empty
firas.qutishat (Wed, 27 Feb 2019 20:49:36 GMT):
I think the reason is not passing GO_TAGS is an arg to peer image
firas.qutishat (Wed, 27 Feb 2019 20:49:52 GMT):
https://github.com/hyperledger/fabric/blob/master/Makefile#L266
firas.qutishat (Wed, 27 Feb 2019 20:51:16 GMT):
https://github.com/hyperledger/fabric/blob/master/images/peer/Dockerfile#L24
rameshthoomu (Wed, 27 Feb 2019 20:52:41 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=27dELqok8E5RLpLRZ) @firas.qutishat I don't see GO_TAGS is passing as env to peer image..
firas.qutishat (Wed, 27 Feb 2019 20:53:18 GMT):
I think it's needed to pass
firas.qutishat (Wed, 27 Feb 2019 20:53:59 GMT):
if you export GO_TAGS="pkcs11" and then make peer-docker
firas.qutishat (Wed, 27 Feb 2019 20:55:13 GMT):
you will see that building peer image is ignore the GO_TAGS
firas.qutishat (Wed, 27 Feb 2019 20:55:25 GMT):
because it's not passed
rameshthoomu (Wed, 27 Feb 2019 20:56:03 GMT):
ok will check in sometime
rameshthoomu (Wed, 27 Feb 2019 21:00:33 GMT):
I see this when I set GO_TAGS = pkcs11
```
.build/bin/peer
CGO_CFLAGS=" " GOBIN=/go/src/github.com/hyperledger/fabric/.build/bin go install -tags "pkcs11" -ldflags "-X github.com/hyperledger/fabric/common/metadata.Version=2.0.0 -X github.com/hyperledger/fabric/common/metadata.CommitSHA=b103df528 -X github.com/hyperledger/fabric/common/metadata.BaseVersion=0.4.14 -X github.com/hyperledger/fabric/common/metadata.BaseDockerLabel=org.hyperledger.fabric -X github.com/hyperledger/fabric/common/metadata.DockerNamespace=hyperledger -X github.com/hyperledger/fabric/common/metadata.BaseDockerNamespace=hyperledger" github.com/hyperledger/fabric/peer
```
firas.qutishat (Wed, 27 Feb 2019 21:01:10 GMT):
ok
firas.qutishat (Wed, 27 Feb 2019 21:01:12 GMT):
thanks @rameshthoomu
firas.qutishat (Wed, 27 Feb 2019 21:06:29 GMT):
@rameshthoomu
firas.qutishat (Wed, 27 Feb 2019 21:07:01 GMT):
GO_TAGS="pkcs11" make clean peer-docker
[ -n "" ] && docker rmi -f || true
[ -n "" ] && docker rmi -f || true
[ -n "" ] && docker rmi -f || true
[ -n "" ] && docker rmi -f || true
[ -n "" ] && docker rmi -f || true
[ -n "" ] && docker rmi -f || true
Docker: building peer image
docker build --force-rm -f images/peer/Dockerfile \
--build-arg GO_VER=1.11.5 --build-arg ALPINE_VER=3.8 \
\
-t hyperledger/fabric-peer .
Sending build context to Docker daemon 188.9MB
Step 1/20 : ARG GO_VER
Step 2/20 : ARG ALPINE_VER
Step 3/20 : FROM alpine:${ALPINE_VER} as base
---> 491e0ff7a8d5
Step 4/20 : RUN apk add --no-cache tzdata libltdl
---> Using cache
---> a202252ff440
Step 5/20 : FROM golang:${GO_VER}-alpine${ALPINE_VER} as golang
1.11.5-alpine3.8: Pulling from library/golang
169185f82c45: Already exists
34c29055ee42: Pull complete
29802c64cdfc: Pull complete
dd82873a5b09: Pull complete
b711937b138a: Pull complete
Digest: sha256:9657ef82d7ead12e0c88c7f4708e78b50c5fd3c1893ac0f2f0924ab98873aad8
Status: Downloaded newer image for golang:1.11.5-alpine3.8
---> be1230a1b343
Step 6/20 : RUN apk add --no-cache gcc musl-dev git bash make;
---> Running in 5b33bea7c9f8
fetch http://dl-cdn.alpinelinux.org/alpine/v3.8/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.8/community/x86_64/APKINDEX.tar.gz
(1/24) Installing ncurses-terminfo-base (6.1_p20180818-r1)
(2/24) Installing ncurses-terminfo (6.1_p20180818-r1)
(3/24) Installing ncurses-libs (6.1_p20180818-r1)
(4/24) Installing readline (7.0.003-r0)
(5/24) Installing bash (4.4.19-r1)
Executing bash-4.4.19-r1.post-install
(6/24) Installing binutils (2.30-r5)
(7/24) Installing gmp (6.1.2-r1)
(8/24) Installing isl (0.18-r0)
(9/24) Installing libgomp (6.4.0-r9)
(10/24) Installing libatomic (6.4.0-r9)
(11/24) Installing pkgconf (1.5.3-r0)
(12/24) Installing libgcc (6.4.0-r9)
(13/24) Installing mpfr3 (3.1.5-r1)
(14/24) Installing mpc1 (1.0.3-r1)
(15/24) Installing libstdc++ (6.4.0-r9)
(16/24) Installing gcc (6.4.0-r9)
(17/24) Installing nghttp2-libs (1.32.0-r0)
(18/24) Installing libssh2 (1.8.0-r3)
(19/24) Installing libcurl (7.61.1-r1)
(20/24) Installing expat (2.2.5-r0)
(21/24) Installing pcre2 (10.31-r0)
(22/24) Installing git (2.18.1-r0)
(23/24) Installing make (4.2.1-r2)
(24/24) Installing musl-dev (1.1.19-r10)
Executing busybox-1.28.4-r3.trigger
OK: 122 MiB in 38 packages
Removing intermediate container 5b33bea7c9f8
---> aa21e864e420
Step 7/20 : ADD . $GOPATH/src/github.com/hyperledger/fabric
---> d31a730f968e
Step 8/20 : WORKDIR $GOPATH/src/github.com/hyperledger/fabric
---> Running in 919e13e8b1eb
Removing intermediate container 919e13e8b1eb
---> 0ae658d4b46f
Step 9/20 : ENV EXECUTABLES go git
---> Running in b8327da053df
Removing intermediate container b8327da053df
---> 69c46f8255cf
Step 10/20 : FROM golang as peer
---> 69c46f8255cf
Step 11/20 : RUN make peer
---> Running in d9cbc29c2f9b
.build/bin/peer
CGO_CFLAGS=" " GOBIN=/go/src/github.com/hyperledger/fabric/.build/bin go install -tags "" -ldflags "-X github.com/hyperledger/fabric/common/metadata.Version=2.0.0 -X github.com/hyperledger/fabric/common/metadata.CommitSHA=86933e74b -X github.com/hyperledger/fabric/common/metadata.BaseVersion=0.4.14 -X github.com/hyperledger/fabric/common/metadata.BaseDockerLabel=org.hyperledger.fabric -X github.com/hyperledger/fabric/common/metadata.DockerNamespace=hyperledger -X github.com/hyperledger/fabric/common/metadata.BaseDockerNamespace=hyperledger" github.com/hyperledger/fabric/peer
^Cmake: *** [.build/images/peer/.dummy-amd64-2.0.0-snapshot-86933e74b] Interrupt: 2
firas.qutishat (Wed, 27 Feb 2019 21:07:25 GMT):
```GO_TAGS="pkcs11" make clean peer-docker
[ -n "" ] && docker rmi -f || true
[ -n "" ] && docker rmi -f || true
[ -n "" ] && docker rmi -f || true
[ -n "" ] && docker rmi -f || true
[ -n "" ] && docker rmi -f || true
[ -n "" ] && docker rmi -f || true
Docker: building peer image
docker build --force-rm -f images/peer/Dockerfile \
--build-arg GO_VER=1.11.5 --build-arg ALPINE_VER=3.8 \
\
-t hyperledger/fabric-peer .
Sending build context to Docker daemon 188.9MB
Step 1/20 : ARG GO_VER
Step 2/20 : ARG ALPINE_VER
Step 3/20 : FROM alpine:${ALPINE_VER} as base
---> 491e0ff7a8d5
Step 4/20 : RUN apk add --no-cache tzdata libltdl
---> Using cache
---> a202252ff440
Step 5/20 : FROM golang:${GO_VER}-alpine${ALPINE_VER} as golang
1.11.5-alpine3.8: Pulling from library/golang
169185f82c45: Already exists
34c29055ee42: Pull complete
29802c64cdfc: Pull complete
dd82873a5b09: Pull complete
b711937b138a: Pull complete
Digest: sha256:9657ef82d7ead12e0c88c7f4708e78b50c5fd3c1893ac0f2f0924ab98873aad8
Status: Downloaded newer image for golang:1.11.5-alpine3.8
---> be1230a1b343
Step 6/20 : RUN apk add --no-cache gcc musl-dev git bash make;
---> Running in 5b33bea7c9f8
fetch http://dl-cdn.alpinelinux.org/alpine/v3.8/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.8/community/x86_64/APKINDEX.tar.gz
(1/24) Installing ncurses-terminfo-base (6.1_p20180818-r1)
(2/24) Installing ncurses-terminfo (6.1_p20180818-r1)
(3/24) Installing ncurses-libs (6.1_p20180818-r1)
(4/24) Installing readline (7.0.003-r0)
(5/24) Installing bash (4.4.19-r1)
Executing bash-4.4.19-r1.post-install
(6/24) Installing binutils (2.30-r5)
(7/24) Installing gmp (6.1.2-r1)
(8/24) Installing isl (0.18-r0)
(9/24) Installing libgomp (6.4.0-r9)
(10/24) Installing libatomic (6.4.0-r9)
(11/24) Installing pkgconf (1.5.3-r0)
(12/24) Installing libgcc (6.4.0-r9)
(13/24) Installing mpfr3 (3.1.5-r1)
(14/24) Installing mpc1 (1.0.3-r1)
(15/24) Installing libstdc++ (6.4.0-r9)
(16/24) Installing gcc (6.4.0-r9)
(17/24) Installing nghttp2-libs (1.32.0-r0)
(18/24) Installing libssh2 (1.8.0-r3)
(19/24) Installing libcurl (7.61.1-r1)
(20/24) Installing expat (2.2.5-r0)
(21/24) Installing pcre2 (10.31-r0)
(22/24) Installing git (2.18.1-r0)
(23/24) Installing make (4.2.1-r2)
(24/24) Installing musl-dev (1.1.19-r10)
Executing busybox-1.28.4-r3.trigger
OK: 122 MiB in 38 packages
Removing intermediate container 5b33bea7c9f8
---> aa21e864e420
Step 7/20 : ADD . $GOPATH/src/github.com/hyperledger/fabric
---> d31a730f968e
Step 8/20 : WORKDIR $GOPATH/src/github.com/hyperledger/fabric
---> Running in 919e13e8b1eb
Removing intermediate container 919e13e8b1eb
---> 0ae658d4b46f
Step 9/20 : ENV EXECUTABLES go git
---> Running in b8327da053df
Removing intermediate container b8327da053df
---> 69c46f8255cf
Step 10/20 : FROM golang as peer
---> 69c46f8255cf
Step 11/20 : RUN make peer
---> Running in d9cbc29c2f9b
.build/bin/peer
CGO_CFLAGS=" " GOBIN=/go/src/github.com/hyperledger/fabric/.build/bin go install -tags "" -ldflags "-X github.com/hyperledger/fabric/common/metadata.Version=2.0.0 -X github.com/hyperledger/fabric/common/metadata.CommitSHA=86933e74b -X github.com/hyperledger/fabric/common/metadata.BaseVersion=0.4.14 -X github.com/hyperledger/fabric/common/metadata.BaseDockerLabel=org.hyperledger.fabric -X github.com/hyperledger/fabric/common/metadata.DockerNamespace=hyperledger -X github.com/hyperledger/fabric/common/metadata.BaseDockerNamespace=hyperledger" github.com/hyperledger/fabric/peer
^Cmake: *** [.build/images/peer/.dummy-amd64-2.0.0-snapshot-86933e74b] Interrupt: 2
```
rameshthoomu (Wed, 27 Feb 2019 21:07:58 GMT):
I modified in Makefile
firas.qutishat (Wed, 27 Feb 2019 21:08:26 GMT):
I test in master 86933e74bd6c591e569c2cd091369bd1fc29a58c
firas.qutishat (Wed, 27 Feb 2019 21:08:44 GMT):
What I need to change in Mak file
rameshthoomu (Wed, 27 Feb 2019 21:09:27 GMT):
set value to GO_TAGS
rameshthoomu (Wed, 27 Feb 2019 21:09:55 GMT):
going to meeting..
rameshthoomu (Wed, 27 Feb 2019 21:09:59 GMT):
```
-GO_TAGS ?=
+GO_TAGS ?= pkcs11
```
firas.qutishat (Wed, 27 Feb 2019 21:10:10 GMT):
I can't do that
firas.qutishat (Wed, 27 Feb 2019 21:10:20 GMT):
it was working in 1.4
firas.qutishat (Wed, 27 Feb 2019 21:10:47 GMT):
we can't change makefile directly
firas.qutishat (Wed, 27 Feb 2019 21:11:15 GMT):
it's bug
rameshthoomu (Wed, 27 Feb 2019 21:12:53 GMT):
create a bug in fabric and add component as 'fabric-build'
rameshthoomu (Wed, 27 Feb 2019 21:13:10 GMT):
will be back in 1 hr.. please post the bug# here..
firas.qutishat (Wed, 27 Feb 2019 21:39:02 GMT):
Also DOCKER_DYNAMIC_LINK not working anymore
firas.qutishat (Wed, 27 Feb 2019 21:39:56 GMT):
I see DOCKER_GO_LDFLAGS was delete it https://github.com/hyperledger/fabric/commit/fdd1c72eaf45bb987e407b57ba09d7ba72e5bc31#diff-b67911656ef5d18c4ae36cb6741b7965L239
Baha-sk (Wed, 27 Feb 2019 21:42:27 GMT):
@rameshthoomu @firas.qutishat FAB-14401 created for the GO_TAGS bug
Baha-sk (Wed, 27 Feb 2019 21:42:27 GMT):
@rameshthoomu @firas.qutishat FAB-14401 (https://jira.hyperledger.org/browse/FAB-14401) created for the GO_TAGS bug
Baha-sk (Wed, 27 Feb 2019 21:44:58 GMT):
@rameshthoomu @firas.qutishat https://jira.hyperledger.org/browse/FAB-14402 created for DOCKER_DYNAMIC_LINK not working anymore
Baha-sk (Wed, 27 Feb 2019 21:44:58 GMT):
@rameshthoomu @firas.qutishat FAB-14402 (https://jira.hyperledger.org/browse/FAB-14402) created for DOCKER_DYNAMIC_LINK not working anymore
vijay.bP (Thu, 28 Feb 2019 14:49:52 GMT):
@rameshthoomu @nfrunza Please see this patch for updating build docker images script in BE https://gerrit.hyperledger.org/r/#/c/29709/
nfrunza (Thu, 28 Feb 2019 14:49:53 GMT):
Has joined the channel.
nfrunza (Thu, 28 Feb 2019 15:00:22 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=SEtxcX45ipNeiCByE) @vijay.bP thank you for fix, the commit message doesn't show correct jira: it should be BE-563
vijay.bP (Thu, 28 Feb 2019 15:01:19 GMT):
@nfrunza Thanks i'll update now.
nfrunza (Thu, 28 Feb 2019 15:03:42 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=sxndeBN9erois2mdZ) @vijay.bP :thumbsup: prompt update thank you
nfrunza (Thu, 28 Feb 2019 15:03:42 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=sxndeBN9erois2mdZ) @vijay.bP :thumbsup: prompt update thank you
nfrunza (Thu, 28 Feb 2019 15:28:16 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=2BJEEyffzByZMwtYb) reviewed, looks like Ramesh needs to approve
rameshthoomu (Thu, 28 Feb 2019 15:28:40 GMT):
done
nfrunza (Thu, 28 Feb 2019 17:09:48 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=GbTJfyRxPzBcMKDvp) I just applied a tag, can we have a manual publish, to docker hub?
rameshthoomu (Thu, 28 Feb 2019 17:10:02 GMT):
sure
nfrunza (Thu, 28 Feb 2019 17:10:08 GMT):
thank you
rameshthoomu (Thu, 28 Feb 2019 17:10:56 GMT):
0.3.7.1 - You want me to publish from this release?
rameshthoomu (Thu, 28 Feb 2019 17:11:50 GMT):
@nfrunza ^^
nfrunza (Thu, 28 Feb 2019 17:15:03 GMT):
may not work, the tag 3.8 doesn't have the new script, we may need to apply a patch to that tag
rameshthoomu (Thu, 28 Feb 2019 17:15:22 GMT):
that's not possible
rameshthoomu (Thu, 28 Feb 2019 17:15:40 GMT):
you can not push changes to tags.. only to branches..
nfrunza (Thu, 28 Feb 2019 17:15:56 GMT):
i'll have another tag from that tag clone
nfrunza (Thu, 28 Feb 2019 17:16:14 GMT):
0.3.7.2
nfrunza (Thu, 28 Feb 2019 17:16:33 GMT):
do for current tag
rameshthoomu (Thu, 28 Feb 2019 17:18:19 GMT):
v0.3.9.1 this is the latest tag..
rameshthoomu (Thu, 28 Feb 2019 17:18:31 GMT):
using this one to publish..
nfrunza (Thu, 28 Feb 2019 17:29:48 GMT):
yes
rameshthoomu (Thu, 28 Feb 2019 17:29:57 GMT):
ok
rameshthoomu (Thu, 28 Feb 2019 18:04:34 GMT):
@nfrunza published 0.3.9.1 version to dockerhub
https://hub.docker.com/r/hyperledger/explorer/tags
https://hub.docker.com/r/hyperledger/explorer-db/tags
nfrunza (Thu, 28 Feb 2019 18:34:32 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=ySF2XwjXwmsoSi4jP) @rameshthoomu thank you very much
rameshthoomu (Sun, 03 Mar 2019 23:55:52 GMT):
@sambhavdutt I see e2e master build is failing since 6 days.. Do you have bug for this? I don't see one in https://jira.hyperledger.org/issues/?filter=12705
rameshthoomu (Sun, 03 Mar 2019 23:56:30 GMT):
Could you please follow up on the bug if you have one otherwise please create one with highest priority and post it in #fabric-maintainers channel..
rameshthoomu (Sun, 03 Mar 2019 23:56:45 GMT):
Seems channel join is not working and failing consistently.
rameshthoomu (Mon, 04 Mar 2019 00:00:38 GMT):
Also, If the builds are failing consistently, please bump the priority of the issue to highest and reach out to the person or post in channels for their attention.. I see fabric-sdk-node release-1.4 and master builds are failing while joining the channel..
sambhavdutt (Mon, 04 Mar 2019 00:16:31 GMT):
@rameshthoomu
Yes, there is a bug open for this , the jobs are failing in sdk-node tests,
https://jira.hyperledger.org/browse/FABN-1165
I'll post this in the #fabric-maintainers
rameshthoomu (Mon, 04 Mar 2019 00:17:45 GMT):
let me check
rameshthoomu (Mon, 04 Mar 2019 00:18:16 GMT):
not this one.. I see byfn tests are failing while joining the channel in e2e
rameshthoomu (Mon, 04 Mar 2019 00:21:20 GMT):
When you post bug #FABN-1165 in #fabric-maintainers please tag Brett and Andrew Col..
vijay.bP (Mon, 04 Mar 2019 15:35:20 GMT):
@scottz Please take a look into these changes https://gerrit.hyperledger.org/r/#/c/29223/
sambhavdutt (Mon, 04 Mar 2019 16:34:23 GMT):
Please find the list of open Bugs in this link,
https://jira.hyperledger.org/issues/?filter=12118
rameshthoomu (Mon, 04 Mar 2019 16:51:26 GMT):
@jyellick https://jira.hyperledger.org/browse/FAB-14465 any inputs on this error? we are observing this issue in master on both x and z
rameshthoomu (Mon, 04 Mar 2019 17:05:18 GMT):
@bretharrison @andrew-coleman Could you please check this issue. It seems this is consistent https://jira.hyperledger.org/browse/FABN-1165
bretharrison (Mon, 04 Mar 2019 17:08:33 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=bR8gowcfFKmxCYyYt) @rameshthoomu Nick has fixed it
rameshthoomu (Mon, 04 Mar 2019 17:08:59 GMT):
ok let me re-trigger it then in master
rameshthoomu (Mon, 04 Mar 2019 17:14:50 GMT):
@sambhavdutt please check this https://jira.hyperledger.org/browse/FAB-14395
rameshthoomu (Mon, 04 Mar 2019 17:47:33 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=AghxBcfqvDeanyDDv) @bretharrison Is this fixed in master?
bretharrison (Mon, 04 Mar 2019 17:55:42 GMT):
Yes, he is working on 1.4 also
rameshthoomu (Mon, 04 Mar 2019 17:57:21 GMT):
I re-triggered 30 mins back and observed the same error.. https://jenkins.hyperledger.org/view/Daily/job/fabric-end-2-end-daily-master-s390x/47/consoleFull
bretharrison (Mon, 04 Mar 2019 17:58:10 GMT):
did you rebase ?
rameshthoomu (Mon, 04 Mar 2019 17:58:35 GMT):
yes.. that;s a daily job.. it fetches the latest commit from each repo/branch.
rameshthoomu (Mon, 04 Mar 2019 17:58:47 GMT):
I can check the commit of sdk-node.. give me a min
rameshthoomu (Mon, 04 Mar 2019 17:59:28 GMT):
yes.. I am on latest commit
braduf (Tue, 05 Mar 2019 00:03:18 GMT):
Has joined the channel.
allenyang (Tue, 05 Mar 2019 07:57:19 GMT):
Has joined the channel.
awjh (Tue, 05 Mar 2019 14:12:47 GMT):
Hi, fabric-chaincode-node is currently failing on Jenkins with the error Failed to pull hyperledger/fabric-ccenv:2.0.0 when attempting to instantiate smart contracts in our tests. Any ideas on how we can rectify this?
sambhavdutt (Tue, 05 Mar 2019 14:14:58 GMT):
@awjh
Let me check if I can find a resolution for this
awjh (Tue, 05 Mar 2019 14:15:39 GMT):
Thanks :)
sambhavdutt (Tue, 05 Mar 2019 14:52:39 GMT):
@awjh @mbwhite
I have submitted a CR to add the ccenv image to node-chaincode tests, Can you approve it if ok,
https://gerrit.hyperledger.org/r/#/c/29833/
sambhavdutt (Tue, 05 Mar 2019 14:53:51 GMT):
this should fix the problem in the verify jobs while instntiating the chaincode
mbwhite (Tue, 05 Mar 2019 14:56:18 GMT):
done
sambhavdutt (Tue, 05 Mar 2019 14:56:36 GMT):
@mbwhite
thank you !
rameshthoomu (Tue, 05 Mar 2019 14:56:45 GMT):
let's wait for the CI result.. and merge
rameshthoomu (Tue, 05 Mar 2019 14:57:12 GMT):
Why the build is not started?
mbwhite (Tue, 05 Mar 2019 14:57:50 GMT):
oh it hasn't...
rameshthoomu (Tue, 05 Mar 2019 14:58:11 GMT):
@sambhavdutt ^^
rameshthoomu (Tue, 05 Mar 2019 14:58:42 GMT):
never mind.. it started now
sambhavdutt (Tue, 05 Mar 2019 14:59:01 GMT):
yes, it just started now
rameshthoomu (Tue, 05 Mar 2019 15:04:14 GMT):
@sambhavdutt Could you please check with @bretharrison on FABN-1165.. He said this was fixed in master but I still see the issue in daily jobs which was triggered on the fix commit..
rameshthoomu (Tue, 05 Mar 2019 15:04:41 GMT):
FYI https://jira.hyperledger.org/browse/FABN-1165 is in Closed status now..
rameshthoomu (Tue, 05 Mar 2019 15:08:16 GMT):
Also, do you have the same bug for release-1.4?
sambhavdutt (Tue, 05 Mar 2019 15:09:22 GMT):
FABN-1165 was for both master and release-1.4
sambhavdutt (Tue, 05 Mar 2019 15:09:22 GMT):
yes, FABN-1165 was for both master and release-1.4
mbwhite (Tue, 05 Mar 2019 15:32:43 GMT):
btw due to the changes that happened recently with the configtxgen tool - the basic-network that the chaincode-node relies on - can't work.
mbwhite (Tue, 05 Mar 2019 15:34:04 GMT):
we might need the change to be pushed in along with @awjh change that will fix this
rameshthoomu (Tue, 05 Mar 2019 15:43:23 GMT):
I am ok with that.. as this is a simple change..
awjh (Tue, 05 Mar 2019 15:52:35 GMT):
Can confirm that the fix once added to my code moves me past that error
rameshthoomu (Tue, 05 Mar 2019 15:58:36 GMT):
@sambhavdutt could you please abandon your patch
sambhavdutt (Tue, 05 Mar 2019 17:04:40 GMT):
@rameshthoomu Done
sambhavdutt (Tue, 05 Mar 2019 19:14:34 GMT):
Please find the list of open Bugs as of today
https://jira.hyperledger.org/issues/?filter=12118
mbwhite (Wed, 06 Mar 2019 11:51:44 GMT):
Hi - is it possible to confirm who has +2 rights on the `fabric-samples` repo... looking at gerrit itself I can't find any way to confirm this...
mbwhite (Wed, 06 Mar 2019 11:53:28 GMT):
For example Jim Zhang is on that list as a retired maintainer; he's still listed in the maintainers.md of the fabric-chaicode-node - but I can't determine if he still has gerrit +2 rights.,
rameshthoomu (Wed, 06 Mar 2019 14:20:25 GMT):
I think all fabric maintainers has +2 rights on fabric-samples
aambati (Wed, 06 Mar 2019 16:23:22 GMT):
@rameshthoomu unit tests are failing in CI with this error...is this a known problem ? seems like an intermittent one as other PR based on this PR worked
```
--- FAIL: TestPluginLoadingFailure (12.30s)
sambhavdutt (Wed, 06 Mar 2019 16:28:00 GMT):
@aambati
yes this has been intermittent in the unit-tests,
rameshthoomu (Wed, 06 Mar 2019 16:33:46 GMT):
@sambhavdutt Could you please share the bug
sambhavdutt (Wed, 06 Mar 2019 16:38:13 GMT):
https://jira.hyperledger.org/browse/FAB-14476
sambhavdutt (Wed, 06 Mar 2019 16:38:34 GMT):
It's not the same panic error though
rameshthoomu (Wed, 06 Mar 2019 16:41:01 GMT):
I don't think this is related issue.. Could you please create one..
sambhavdutt (Wed, 06 Mar 2019 16:41:13 GMT):
ok,
sambhavdutt (Thu, 07 Mar 2019 19:06:34 GMT):
Please find the list of open/ongoing Bugs in this link
https://jira.hyperledger.org/issues/?filter=12118
sambhavdutt (Fri, 08 Mar 2019 01:57:33 GMT):
The alpine:latest images are failing to pull on the s390x platform, https://jira.hyperledger.org/browse/IN-55
Can someone look into this
sambhavdutt (Fri, 08 Mar 2019 01:58:12 GMT):
many s390x jobs are failing because of this
sambhavdutt (Fri, 08 Mar 2019 01:58:51 GMT):
@eddie.allen
rameshthoomu (Fri, 08 Mar 2019 02:20:23 GMT):
@sambhavdutt Seems alpine dropped s390x platform support. https://hub.docker.com/_/alpine
rameshthoomu (Fri, 08 Mar 2019 02:23:48 GMT):
https://github.com/gliderlabs/docker-alpine/issues/501
rameshthoomu (Fri, 08 Mar 2019 14:22:38 GMT):
@sambhavdutt any update on the above issue? is it working now?
rameshthoomu (Fri, 08 Mar 2019 14:23:14 GMT):
seems it's working now.
sambhavdutt (Fri, 08 Mar 2019 14:24:55 GMT):
I agree, I tested a job on z/s390x and see that iw was pulling the alpine image
```
09:23:38 latest: Pulling from library/alpine
09:23:39 d981dc59d98d: Pulling fs layer
09:23:39 d981dc59d98d: Verifying Checksum
09:23:39 d981dc59d98d: Download complete
09:23:39 d981dc59d98d: Pull complete
```
sambhavdutt (Fri, 08 Mar 2019 14:24:55 GMT):
I agree, I tested a job on z/s390x and see that it was pulling the alpine image
```
09:23:38 latest: Pulling from library/alpine
09:23:39 d981dc59d98d: Pulling fs layer
09:23:39 d981dc59d98d: Verifying Checksum
09:23:39 d981dc59d98d: Download complete
09:23:39 d981dc59d98d: Pull complete
```
sambhavdutt (Fri, 08 Mar 2019 14:48:11 GMT):
@rameshthoomu Can you retrigger the daily s390x jobs, all of them failed with alpine image issue.
sambhavdutt (Fri, 08 Mar 2019 14:48:11 GMT):
@rameshthoomu Can you retrigger the daily s390x jobs, all of them failed with alpine image issue last night, now alpine is working fine on s390x
rameshthoomu (Fri, 08 Mar 2019 15:15:46 GMT):
@bretharrison any update on this issue.. https://jira.hyperledger.org/browse/FABN-1165 It seems e2e sdk node tests are failing since 12 days.... As we have disabled e2e jobs from verify jobs we are not seeing any impact on the builds but I could see merge and daily jobs are failing consistently..
rameshthoomu (Fri, 08 Mar 2019 17:54:33 GMT):
@sambhavdutt I see byfn tests are failing in s390x
```
12:48:41 [34m2019-03-08 17:48:41.851 UTC [channelCmd] InitCmdFactory -> INFO 001[0m Endorser and orderer connections initialized
12:48:41 [34m2019-03-08 17:48:41.854 UTC [cli.common] readBlock -> INFO 002[0m Got status: &{FORBIDDEN}
12:48:41 Error: can't read the block: &{FORBIDDEN}
12:48:41 !!!!!!!!!!!!!!! Fetching config block from orderer has Failed !!!!!!!!!!!!!!!!
12:48:41 ========= ERROR !!! FAILED to execute End-2-End Scenario =========
```
sambhavdutt (Fri, 08 Mar 2019 19:05:18 GMT):
https://jira.hyperledger.org/browse/FAB-14551
I created a bug for this now,
sambhavdutt (Fri, 08 Mar 2019 19:05:56 GMT):
This is the list of open Bugs as of today
https://jira.hyperledger.org/issues/?filter=12118
rameshthoomu (Fri, 08 Mar 2019 19:18:53 GMT):
Do you know why this is failing?
rameshthoomu (Sun, 10 Mar 2019 03:29:24 GMT):
@bretharrison @nkl199 any idea why I am getting below error while running `gulp run-tape-e2e`
```
22:06:07 [03:06:06] 'run-tape-e2e' errored after 725 ms
22:06:07 [03:06:06] Error in plugin 'gulp-tape'
22:06:07 Message:
22:06:07 ENOENT: no such file or directory, open '/w/workspace/fabric-ca-verify-x86_64/gopath/src/github.com/hyperledger/fabric-sdk-node/test/fixtures/fabricca/enroll-csr.pem'
22:06:07 Details:
22:06:07 errno: -2
22:06:07 code: ENOENT
22:06:07 syscall: open
22:06:07 path: /w/workspace/fabric-ca-verify-x86_64/gopath/src/github.com/hyperledger/fabric-sdk-node/test/fixtures/fabricca/enroll-csr.pem
22:06:07 TAP version 13
22:06:07 ** HFCAIdentityService Test *
22:06:07 events.js:183
22:06:07 throw er; // Unhandled 'error' event
```
logannwu (Sun, 10 Mar 2019 05:45:02 GMT):
Has joined the channel.
nkl199 (Mon, 11 Mar 2019 10:31:34 GMT):
@rameshthoomu there has been a recent update to the node-sdk tests to generate the required test certificates prior to running the tests (we were broken last week due to expiring certificates) and it is now part of the build process ... looks like you need to run `gulp install-and-generate-certs` or `gulp install-and-generate-certs-s390` for linux/zLinux respectively
rameshthoomu (Mon, 11 Mar 2019 12:11:04 GMT):
Ok if possible could you pls add this in gulp test target. So that I can just run this target
rameshthoomu (Mon, 11 Mar 2019 13:43:06 GMT):
Ignore my above comment.. I was actually using `run-tape-e2e` target to run the sdk-node tests on fabric-ca changes.
rameshthoomu (Mon, 11 Mar 2019 13:43:57 GMT):
I just added `gulp install-and-generate-certs run-tape-e2e` to my test in sandbox.. If this works, I will add this target in the gulp file
rameshthoomu (Mon, 11 Mar 2019 15:03:13 GMT):
@nkl199 Could you please check below error
```
00:36:14.479 [14:06:02] Starting 'run-tape-e2e'...
00:36:16.650 TAP version 13
00:36:16.650 ** HFCAIdentityService Test **
00:36:17.291 events.js:183
00:36:17.291 throw er; // Unhandled 'error' event
00:36:17.291 ^
```
nkl199 (Mon, 11 Mar 2019 15:05:13 GMT):
... is thee any more trace than that?
nkl199 (Mon, 11 Mar 2019 15:05:13 GMT):
... is there any more trace than that?
rameshthoomu (Mon, 11 Mar 2019 15:09:54 GMT):
No..
rameshthoomu (Mon, 11 Mar 2019 15:10:42 GMT):
Where can I see more trace for this error?
nkl199 (Mon, 11 Mar 2019 15:24:59 GMT):
I would have thought that any errors would have been within the logs of the process running that test
nkl199 (Mon, 11 Mar 2019 15:27:49 GMT):
Mapping to the existing test where `** HFCAIdentityService Test **` appears, gives quite a large scope for error locations
rameshthoomu (Mon, 11 Mar 2019 16:41:54 GMT):
Check this job.. https://jenkins.hyperledger.org/sandbox/view/All/job/fabric-ca-verify-x86_64/55/consoleFull
rameshthoomu (Mon, 11 Mar 2019 16:42:04 GMT):
and search for word `run-tape-e2e`
rameshthoomu (Mon, 11 Mar 2019 16:42:23 GMT):
I don't see any log generated after call the run-tape-e2e target
rameshthoomu (Mon, 11 Mar 2019 17:00:06 GMT):
@sambhavdutt Could you please verify this bug https://jira.hyperledger.org/browse/FABN-1172
sambhavdutt (Mon, 11 Mar 2019 17:12:37 GMT):
I see this fail in recent e2e daily tests, in 1.2 and 1.3
rickr (Mon, 11 Mar 2019 21:56:40 GMT):
@sambhavdutt @rameshthoomu https://jenkins.hyperledger.org/job/fabric-sdk-java-verify-1.4-x86_64/59/console
any ideas ?
rameshthoomu (Mon, 11 Mar 2019 23:43:15 GMT):
@vijay.bP Seems your recent change is causing this failure.. Could you please check
```
17:52:31 ----> verify-commit.sh
17:52:31 /tmp/jenkins7975189678325304272.sh: line 21: cd: /w/workspace/fabric-sdk-java-verify-1.4-x86_64/gopath/src/github.com/hyperledger/fabric-sdk-java: No such file or directory
```
rameshthoomu (Mon, 11 Mar 2019 23:44:00 GMT):
we don't clone fabric-sdk-java repo in BASE_DIR..
vijay.bP (Tue, 12 Mar 2019 02:08:59 GMT):
@rameshthoomu Yes, verify.commit script points to WORKSPACE/BASE_DIR, In this case where do we clone in fabric-sdk-java
vijay.bP (Tue, 12 Mar 2019 02:08:59 GMT):
@rameshthoomu Yes, verify.commit script points to WORKSPACE/BASE_DIR.
In this case where do we clone in fabric-sdk-java?
vijay.bP (Tue, 12 Mar 2019 02:08:59 GMT):
@rameshthoomu Yes, verify.commit script points to WORKSPACE/BASE_DIR.
vijay.bP (Tue, 12 Mar 2019 02:29:04 GMT):
@rameshthoomu https://gerrit.hyperledger.org/r/#/c/30016/ changes done for the verify-commit script. Please review
rameshthoomu (Tue, 12 Mar 2019 02:55:42 GMT):
done. Please fix this issue..
KyunghoKim (Tue, 12 Mar 2019 03:07:45 GMT):
Has joined the channel.
rickr (Tue, 12 Mar 2019 11:39:55 GMT):
@rameshthoomu @vijay.bP This isn't an SDK script that's failing. The sdk has never had that path.
```
07:29:44 /tmp/jenkins8417261891329528223.sh: line 21: cd: /w/workspace/fabric-sdk-java-verify-1.4-x86_64/gopath/src/github.com/hyperledger/fabric-sdk-java: No such file or directory
```
rickr (Tue, 12 Mar 2019 11:39:55 GMT):
@rameshthoomu @vijay.bP This isn't an SDK script that's failing. The sdk has never had that path.
```
07:29:44 /tmp/jenkins8417261891329528223.sh: line 21: cd: /w/workspace/fabric-sdk-java-verify-1.4-x86_64/gopath/src/github.com/hyperledger/fabric-sdk-java: No such file or directory
```
I think this is a due to a change in a build script (not sdk) or build environment change
rickr (Tue, 12 Mar 2019 11:46:52 GMT):
https://gerrit.hyperledger.org/r/#/c/29237/ I've just tired running a merged changed reverify and remerge .. but jobs are not kicking off.
rickr (Tue, 12 Mar 2019 11:48:15 GMT):
```gopath/src/github.com/hyperledger/fabric-sdk-java`` has *never* been in the JSDK
```
vijay.bP (Tue, 12 Mar 2019 13:00:51 GMT):
@rickr CR for the above issue has been merged yesterday night, still it's nor reflecting on jenkins environment. So the path is coming as ``` /w/workspace/fabric-sdk-java-verify-1.4-x86_64/gopath/src/github.com/hyperledger/fabric-sdk-java```
rickr (Tue, 12 Mar 2019 13:14:08 GMT):
ok thx. Can someone ping me on RC when the fix has been applied please ?
vijay.bP (Tue, 12 Mar 2019 13:38:04 GMT):
@rameshthoomu @dave.enyeart Please review the CR, update the pull build artifacts in fabric-master https://gerrit.hyperledger.org/r/#/c/28210/
vijay.bP (Tue, 12 Mar 2019 13:40:45 GMT):
@rickr Can you reverify your CR now.
rickr (Tue, 12 Mar 2019 13:41:09 GMT):
ok, will do
sambhavdutt (Tue, 12 Mar 2019 14:22:24 GMT):
These are the list of open bugs as of today,
https://jira.hyperledger.org/issues/?filter=12118
rameshthoomu (Wed, 13 Mar 2019 02:25:03 GMT):
@bretharrison will give a demo on this patch output and the impacts after merge this change. https://gerrit.hyperledger.org/r/#/c/30045/
MHBauer (Wed, 13 Mar 2019 03:20:13 GMT):
any auto-reverify availability? anyway to recognize "failed to pull docker images" and requeue automatically?
rameshthoomu (Wed, 13 Mar 2019 03:58:01 GMT):
@MHBauer where you are seeing this issue? I mean which repo/job?
MHBauer (Wed, 13 Mar 2019 04:00:34 GMT):
https://jenkins.hyperledger.org/job/fabric-chaincode-evm-verify-x86_64/253/console
MHBauer (Wed, 13 Mar 2019 04:01:25 GMT):
don't really know how to deal with jenkins, so if there's a reusable upstream script somewhere, I'm interested.
rameshthoomu (Wed, 13 Mar 2019 04:04:20 GMT):
sure.. will let you know
rameshthoomu (Wed, 13 Mar 2019 04:06:21 GMT):
You can post either `reverify` or `reverify-x` in your gerrit patchset.. This triggers a verify job
rameshthoomu (Wed, 13 Mar 2019 04:07:36 GMT):
As this is a pipeline job, JJB code is very small and simple.. Here is the evm project job configuration with global pipeline verify and merge template https://github.com/hyperledger/ci-management/blob/master/jjb/fabric-chaincode-evm/fabric-chaincode-evm-jobs.yaml
rameshthoomu (Wed, 13 Mar 2019 04:43:41 GMT):
@nkl199 Could you please check these two FAB's
https://jira.hyperledger.org/browse/FABN-1178
https://jira.hyperledger.org/browse/FABN-1179
sambhavdutt (Wed, 13 Mar 2019 16:40:44 GMT):
These are the list of open Bugs as of today
https://jira.hyperledger.org/issues/?filter=12118
rameshthoomu (Wed, 13 Mar 2019 16:44:06 GMT):
@dave.enyeart ^^ What is the best place/channel to triage the bugs created by CI team (Sambhav). See the list of bugs which are open here https://jira.hyperledger.org/issues/?filter=12118.
dave.enyeart (Wed, 13 Mar 2019 17:28:34 GMT):
@rameshthoomu @sambhavdutt We have a Fabric Bugs and Tech Debt dashboard that we have been using more recently: https://jira.hyperledger.org/secure/Dashboard.jspa?selectPageId=11706. It includes widgets for bugs and jiras with 'flakes' label. We can add some more widgets to bring attention to the CI list. I think it would make sense to base new widgets off of labels. But first, let's agree on the labels to use. I still don't think we have an agreed upon consistent way to label CI bugs, so people don't know which ones are the true CI blockers. If it is labeled as 'ci_failures' but not labeled as 'flakes' does that mean it is a true CI blocker? Perhaps we need a new label like 'ci_blokcer'. Some jiras use label 'flakes', some use description text "Consistent:No", some use "Intermittent:Yes". Let's get some consistency here... please propose the crisp list of labels you would like to use, as well as their definition. We can then create widgets based on the labels and have common understandings. Finally, for the most important items that are still not getting attention, feel free to bring up on fabric-maintainers. Once we have the widgets in place we could post the widget link to fabric-maintainers as often as needed to get attention to this.
dave.enyeart (Wed, 13 Mar 2019 17:28:34 GMT):
@rameshthoomu @sambhavdutt We have a Fabric Bugs and Tech Debt dashboard that we have been using more recently: https://jira.hyperledger.org/secure/Dashboard.jspa?selectPageId=11706. It includes widgets for bugs and jiras with 'flakes' label. We can add some more widgets to the dashboard to bring attention to the CI list. I think it would make sense to base new widgets off of labels. But first, let's agree on the labels to use. I still don't think we have an agreed upon consistent way to label CI bugs, so people don't know which ones are the true CI blockers. If it is labeled as 'ci_failures' but not labeled as 'flakes' does that mean it is a true CI blocker? Perhaps we need a new label like 'ci_blokcer' to make it more clear. Some jiras use label 'flakes', some use description text "Consistent:No", some use "Intermittent:Yes". Let's get some consistency here... please propose the crisp list of labels you would like to use, as well as their definition. We can then create widgets based on the labels and have common understandings. Finally, for the most important items that are still not getting attention, feel free to bring up on fabric-maintainers. Once we have the widgets in place we could post the widget link to fabric-maintainers as often as needed to get attention to this.
dave.enyeart (Wed, 13 Mar 2019 17:31:38 GMT):
Finally, make sure priority and FixVersion are set appropriately. For example this one is marked as FixVersion=Future which means nobody will look at it: https://jira.hyperledger.org/browse/FABN-1165
rameshthoomu (Wed, 13 Mar 2019 17:43:19 GMT):
@vijay.bP ^^
sambhavdutt (Wed, 13 Mar 2019 17:49:13 GMT):
@dave.enyeart
`ci_blocker` would be a good label, as `ci_failure` is assigned to all failing CI jobs, whether it is a blocker or not. Like the 'first-time` can we have labels for `consistent` and `intermittent` too, as long as it doesn't pool up the list of labels, sometimes we use more than two labels which would be the only concern
sambhavdutt (Wed, 13 Mar 2019 17:49:13 GMT):
@dave.enyeart
`ci_blocker` would be a good label, as `ci_failure` is assigned to all failing CI jobs, whether it is a blocker or not. Like the 'first-time` can we have labels for `consistent` and `intermittent` too, as long as it doesn't pool up the list of labels, sometimes we use more than two labels which would be the only concern
sambhavdutt (Wed, 13 Mar 2019 17:49:13 GMT):
@dave.enyeart
`ci_blocker` would be a good label, as `ci_failure` is assigned to all failing CI jobs, whether it is a blocker or not. Like the `first-time` can we have labels for `consistent` and `intermittent` too, as long as it doesn't pool up the list of labels, sometimes we use more than two labels which would be the only concern
sambhavdutt (Wed, 13 Mar 2019 17:55:09 GMT):
the fix version for the above bug was modified to `future` by one of the team members later.
dave.enyeart (Wed, 13 Mar 2019 18:03:55 GMT):
@rameshthoomu @sambhavdutt @vijay.bP @sykesm How about we withdraw use of the current general ci_failure label and use one of these four mutually exclusive labels (with corresponding dashboard widgets for each):
ci-blocker - true blocker that impacts all CRs for a project and must be addressed to get CI working again
ci-failure - consistent failure but not blocking (what is an example?)
ci-flake - rename existing 'flakes' to indicate intermittent failure
ci-first-failure - label to use the first time an issue is seen, should be converted to one of the three above once there is more data is available
dave.enyeart (Wed, 13 Mar 2019 18:03:55 GMT):
@rameshthoomu @sambhavdutt @vijay.bP @sykesm How about we withdraw use of the current general ci_failure label and use one of these four mutually exclusive labels (with corresponding dashboard widgets for each):
*ci-blocker* - true blocker that impacts all CRs for a project and must be addressed to get CI working again
*ci-failure* - consistent failure but not blocking (what is an example?)
*ci-flake* - rename existing 'flakes' to indicate intermittent failure
*ci-first-failure* - label to use the first time an issue is seen, should be converted to one of the three above once there is more data is available
dave.enyeart (Wed, 13 Mar 2019 18:03:55 GMT):
@rameshthoomu @sambhavdutt @vijay.bP @sykesm How about we withdraw use of the current general ci_failure label and use one of these four mutually exclusive labels (with corresponding dashboard widgets for each):
*ci-blocker* - true blocker that impacts all CRs for a project and must be addressed to get CI working again
*ci-failure* - consistent failure but not blocking (what is an example?)
*ci-flake* - rename existing 'flakes' to indicate intermittent failure
*ci-first-failure* - label to use the first time an issue is seen, should be closed or converted to one of the three above once there is more data is available
dave.enyeart (Wed, 13 Mar 2019 18:03:55 GMT):
@rameshthoomu @sambhavdutt @vijay.bP @sykesm How about we withdraw use of the current general ci_failure label and use one of these four mutually exclusive labels (with corresponding dashboard widgets for each):
*ci-blocker* - true blocker that impacts all CRs for a project and must be addressed to get CI working again
*ci-failure* - consistent failure but not blocking (what is an example?)
*ci-flake* - rename existing 'flakes' to indicate intermittent failure
*ci-first-failure* - label to use the first time an issue is seen, should be closed or converted to one of the three above once more data is available
sambhavdutt (Wed, 13 Mar 2019 18:13:08 GMT):
yes, the above labels would be good,
*ci-failure* the daily cron tests , for e.g. fabric-test jobs fail in some of the tests but they wouldn't be a blocker to fabric or CI jobs,
scottz (Wed, 13 Mar 2019 20:44:44 GMT):
we were using ci_failure label to identify all bugs found and created as a result of running CI automation jobs, to show the usefulness of the automation. Some of these bugs were for different types of work to be done by different teams (LF infrastructure, upgrading tool versions or scripts in jenkins jobs, bugs for fabric developers, or bugs for fabric-test scripts or tools). It seems to me that could still be useful, but I guess it would be ok if we replace the use of ci_faillure by instead using one of the 4 mentioned. That will have an impact the filters in place already, and as you say any new tables and filters, but that is manageable, and I agree it could be more helpful to use more specific labels so we could filter results into different tables on the dashboard (and different teams could focus on different tables).
MHBauer (Wed, 13 Mar 2019 21:40:57 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=7awsYBBG4KZqRJ9ZR) @rameshthoomu right, I know how to do it manually, more looking for something that auto punches it, maybe just once to avoid wasting server time.
MHBauer (Wed, 13 Mar 2019 21:41:17 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=WTNurB6wMntEHbmtr) @rameshthoomu good to know this exists, but I have not the start of what to do with this file.
MHBauer (Wed, 13 Mar 2019 21:41:35 GMT):
are there overall docs somewhere?
rameshthoomu (Wed, 13 Mar 2019 21:43:58 GMT):
fabric-chaincode-evm-jobs.yaml - is just to create a pipeline job with the default configuration.. You hardly modify this file..
rameshthoomu (Wed, 13 Mar 2019 21:44:22 GMT):
You want to re-trigger the job or the test?
rameshthoomu (Wed, 13 Mar 2019 21:45:15 GMT):
if you want to re-trigger the job manually above are the comment phrases.. if it is automatic.. I have no idea how to do that..
MHBauer (Wed, 13 Mar 2019 21:50:34 GMT):
okay
rameshthoomu (Wed, 13 Mar 2019 21:50:53 GMT):
@MHBauer overall doc on fabric-ci process of each repo.. https://ci-docs.readthedocs.io/en/latest/
MHBauer (Wed, 13 Mar 2019 21:51:01 GMT):
oh sweet.
MHBauer (Wed, 13 Mar 2019 21:51:08 GMT):
bookmarked
MHBauer (Wed, 13 Mar 2019 21:51:20 GMT):
oh man, it's even at the top here
MHBauer (Wed, 13 Mar 2019 21:51:29 GMT):
:face_palm_tone1:
rameshthoomu (Wed, 13 Mar 2019 21:51:41 GMT):
Pushed another patch here to explain about global macros and how to kickstart a new pipeline project https://gerrit.hyperledger.org/r/#/c/30048/
MHBauer (Wed, 13 Mar 2019 21:51:41 GMT):
thanks very much
rameshthoomu (Wed, 13 Mar 2019 21:52:43 GMT):
also, we are working on updating this documentation with the recent changes.. Most of the projects are moved to pipeline.. So, some project content might be outdated but will update this doc as soon as possible..
MHBauer (Wed, 13 Mar 2019 21:53:03 GMT):
okay. not sure what a pipeline is, but I'll read up.
rameshthoomu (Wed, 13 Mar 2019 21:54:35 GMT):
I mean https://github.com/hyperledger/fabric-chaincode-evm/blob/master/Jenkinsfile
rameshthoomu (Thu, 14 Mar 2019 02:01:13 GMT):
@mbwhite @andrew-coleman @nkl199 @bretharrison We are observing errors while instantiating on node chaincode. This is consistent across the repos, byfn, fabcar, sdk-java. Could you please check why this is failing https://jira.hyperledger.org/browse/FAB-14638
rameshthoomu (Thu, 14 Mar 2019 02:01:13 GMT):
@mbwhite @andrew-coleman @nkl199 @bretharrison We are observing errors while instantiating on node chaincode. This is consistent across the repos, byfn, fabcar, sdk-java, sdk-node. Could you please check why this is failing https://jira.hyperledger.org/browse/FAB-14638
rameshthoomu (Thu, 14 Mar 2019 02:02:09 GMT):
I have tested this with the latest fabric,fabric-ca, nodeenv images.. Same error.. and it's reproducing in local as well..
sstone1 (Thu, 14 Mar 2019 08:21:16 GMT):
@rameshthoomu will take a look
sstone1 (Thu, 14 Mar 2019 08:28:50 GMT):
@rameshthoomu this is a node 10 / node 8 mismatch - we need @mastersingh24's CR https://gerrit.hyperledger.org/r/#/c/29982/ to be merged to resolve the problem
rameshthoomu (Thu, 14 Mar 2019 13:35:38 GMT):
Thanks @sstone1 .. Gari's patch is now stuck at s390x build.. no clue why it's failing on one specific platform..
rameshthoomu (Thu, 14 Mar 2019 13:36:34 GMT):
@sambhavdutt any update on the fix to e2e build failures.
sambhavdutt (Thu, 14 Mar 2019 13:42:04 GMT):
@rameshthoomu
The BYFN tests are failing in the master branch, as that is addressed in FAB-14638, I see fail in Default Channel test in the master again, I will check this
rameshthoomu (Thu, 14 Mar 2019 13:43:42 GMT):
byfn tests with node chaincode is still an open issue.. I am asking for the CI script update for the recent changes in sdk-node
rameshthoomu (Thu, 14 Mar 2019 13:43:42 GMT):
byfn tests with node chaincode is still an open issue.. I am asking for the CI script update align with the recent changes in the sdk-node
rameshthoomu (Thu, 14 Mar 2019 13:43:42 GMT):
byfn test failures with node chaincode is still an open issue.. I am asking for the CI script update align with the recent changes in the sdk-node
sambhavdutt (Thu, 14 Mar 2019 13:46:09 GMT):
regarding the e2e node we need to update the gulp tests there are patches merged for this in master and release-1.4, I need to check on the earlier branches/versions
sstone1 (Thu, 14 Mar 2019 13:47:25 GMT):
@rameshthoomu the CR is failing on s390x as grpc won't compile on Alpine 3.9 (amd64 has precompiled binaries, so doesn't hit the problem). @mastersingh24 is putting in https://gerrit.hyperledger.org/r/#/c/30084/ which should solve the CI problems.
rameshthoomu (Thu, 14 Mar 2019 14:24:59 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=ZACkPGh7xdfyC4Dt6) @sambhavdutt ok.. Did you update these new gulp targets in the e2e job?
sambhavdutt (Thu, 14 Mar 2019 14:28:14 GMT):
yes, the CR is updated for 1.4 and master, I'll just need a confirmation from sdk-node team if we should run the previous tests for branches other than
master and 1.4
https://gerrit.hyperledger.org/r/#/c/30017/
dave.enyeart (Thu, 14 Mar 2019 17:08:03 GMT):
Are there known issues with CI triggering today? No CI jobs are running for: https://gerrit.hyperledger.org/r/#/c/30097/
dave.enyeart (Thu, 14 Mar 2019 17:08:34 GMT):
May be because it was rebased immediately after patch1 upload...
sambhavdutt (Thu, 14 Mar 2019 17:11:19 GMT):
yes, the rebase after the patch was uploaded, the jobs wouldn't trigger after the rebase. I just triggered them now
dave.enyeart (Thu, 14 Mar 2019 17:13:42 GMT):
Thanks @sambhavdutt . Also I've noticed that on project `fabric` it takes on average 3 minutes for the first job to trigger. While on other projects it is immediate. Any idea why?
dave.enyeart (Thu, 14 Mar 2019 17:13:42 GMT):
Thanks @sambhavdutt . Also I've noticed that on project `fabric` it takes on average 3 minutes for the first job to trigger after patch upload. While on other projects it is immediate. Any idea why?
sambhavdutt (Thu, 14 Mar 2019 17:21:57 GMT):
I'd say the wait is because fabric just triggers on the x nodes. The jobs in z nodes trigger immediately as these are configured already unlike the x nodes that have to clean up and install the pre-req's using packer before the build starts. It's the same case with the fabric-test jobs that trigger just on the x nodes
rameshthoomu (Thu, 14 Mar 2019 17:34:03 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=eN26NxssK7EtDeyvK) @dave.enyeart @tijohnson Could you please answer this.. Why builds are taking 3 mins to kickstart?
tijohnson (Thu, 14 Mar 2019 17:36:13 GMT):
@rameshthoomu is it the pipeline' jobs that are fast ?
rameshthoomu (Thu, 14 Mar 2019 17:36:52 GMT):
No.. He is asking in general..
tijohnson (Thu, 14 Mar 2019 17:37:34 GMT):
I just happen to run a pipeline and it was fast
tijohnson (Thu, 14 Mar 2019 17:40:03 GMT):
@dave.enyeart @rameshthoomu I am working on a new set of init scripts that taking even longer I am actively pursing that issue
I am sure both init scripts are slow for same cause
aso (Thu, 14 Mar 2019 19:00:30 GMT):
Has joined the channel.
aso (Thu, 14 Mar 2019 19:00:40 GMT):
anyone knows what's going on with the CI of https://gerrit.hyperledger.org/r/#/c/30054/ ?
aso (Thu, 14 Mar 2019 19:00:40 GMT):
anyone knows what's going on with the CI run of https://gerrit.hyperledger.org/r/#/c/30054/ ?
dave.enyeart (Thu, 14 Mar 2019 19:07:21 GMT):
@rameshthoomu @sambhavdutt any idea why fabric-samples CI is failing for s390? https://jenkins.hyperledger.org/job/fabric-baseimage-merge-docker-s390x/154/console
dave.enyeart (Thu, 14 Mar 2019 19:07:35 GMT):
looks like JAVA_URL is empty now:
dave.enyeart (Thu, 14 Mar 2019 19:07:38 GMT):
```09:19:28 + JAVA_URL=
09:19:28 + wget -q -U UA_IBM_JAVA_Docker -O /tmp/ibm-java.bin```
dave.enyeart (Thu, 14 Mar 2019 19:07:38 GMT):
```09:19:28 + JAVA_URL=
09:19:28 + wget -q -U UA_IBM_JAVA_Docker -O /tmp/ibm-java.bin
09:19:28 wget: missing URL```
dave.enyeart (Thu, 14 Mar 2019 19:07:59 GMT):
It used to be like this:
dave.enyeart (Thu, 14 Mar 2019 19:08:13 GMT):
```11:37:11 + JAVA_URL=https://public.dhe.ibm.com/ibmdl/export/pub/systems/cloud/runtimes/java/8.0.5.26/linux/s390x/ibm-java-sdk-8.0-5.26-s390x-archive.bin
11:37:11 + wget -q -U UA_IBM_JAVA_Docker -O /tmp/ibm-java.bin https://public.dhe.ibm.com/ibmdl/export/pub/systems/cloud/runtimes/java/8.0.5.26/linux/s390x/ibm-java-sdk-8.0-5.26-s390x-archive.bin```
rameshthoomu (Thu, 14 Mar 2019 19:31:46 GMT):
@dave.enyeart see the one there is version mismatch https://public.dhe.ibm.com/ibmdl/export/pub/systems/cloud/runtimes/java/meta/sdk/linux/s390x/index.yml
rameshthoomu (Thu, 14 Mar 2019 19:32:24 GMT):
I don;t is this by mistake they have added .26 here https://github.com/hyperledger/fabric-baseimage/blob/master/scripts/common/jvm.sh#L19
rameshthoomu (Thu, 14 Mar 2019 19:32:24 GMT):
may be by mistake they have added .26 here https://github.com/hyperledger/fabric-baseimage/blob/master/scripts/common/jvm.sh#L19 or the original url might be updated with this later
rameshthoomu (Thu, 14 Mar 2019 19:38:12 GMT):
Updated JAVA_VERSION to 1.8.0_sr5fp6 in the above line..
```
cat /tmp/index.yml
++ sed -n '/^1.8.0_sr5fp6:/{n;s/\s*uri:\s//p}'
++ tr -d '\r'
+ JAVA_URL=https://public.dhe.ibm.com/ibmdl/export/pub/systems/cloud/runtimes/java/8.0.5.6/linux/s390x/ibm-java-sdk-8.0-5.6-s390x-archive.bin
```
rameshthoomu (Thu, 14 Mar 2019 19:42:18 GMT):
https://jira.hyperledger.org/browse/FABB-120
sudeshrshetty (Thu, 14 Mar 2019 20:25:20 GMT):
@rameshthoomu is there any things wrong with hyperledger gerrit.
verification builds are getting triggered by itself continuously,
https://gerrit.hyperledger.org/r/#/c/30099/
I had to abandon my previous 2 commits since it went out of control
https://gerrit.hyperledger.org/r/#/c/30091/
sudeshrshetty (Thu, 14 Mar 2019 20:25:20 GMT):
@rameshthoomu is there any thing wrong with hyperledger gerrit.
verification builds are getting triggered by itself continuously,
https://gerrit.hyperledger.org/r/#/c/30099/
I had to abandon my previous 2 commits since it went out of control
https://gerrit.hyperledger.org/r/#/c/30091/
sambhavdutt (Thu, 14 Mar 2019 20:39:19 GMT):
@tijohnson
I checked this patchset and I see that there were no retrigger comments posted to retrigger the jobs, for `fabric-sdk-go`
https://jenkins.hyperledger.org/view/fabric-sdk-go/
can you tell why these jobs are triggering on their own
sambhavdutt (Thu, 14 Mar 2019 20:39:19 GMT):
@tijohnson
I checked this patchset and I see that there were no trigger comments posted to retrigger the jobs, for `fabric-sdk-go`
https://jenkins.hyperledger.org/view/fabric-sdk-go/
can you tell why these jobs are triggering on their own
sambhavdutt (Thu, 14 Mar 2019 20:40:41 GMT):
https://gerrit.hyperledger.org/r/#/c/30099/
https://gerrit.hyperledger.org/r/#/c/30091/
vijay.bP (Thu, 14 Mar 2019 20:42:29 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=3BTiy4E3MkjtNgoKx) @sudeshrshetty How the CR is directly gave +2 i.e. merge jobs triggered without verify. And was contineously happening.
sudeshrshetty (Thu, 14 Mar 2019 20:43:55 GMT):
@vijay.bP I have no clue, it is just getting triggered by itself...
sudeshrshetty (Thu, 14 Mar 2019 20:44:24 GMT):
https://gerrit.hyperledger.org/r/#/c/30091/ is posting 'no build executed' every few seconds
sudeshrshetty (Thu, 14 Mar 2019 20:44:24 GMT):
https://gerrit.hyperledger.org/r/#/c/30091/ was posting 'no build executed' every few seconds
vijay.bP (Thu, 14 Mar 2019 20:48:33 GMT):
@sudeshrshetty We dont have control over this.
tijohnson (Thu, 14 Mar 2019 20:58:19 GMT):
@sambhavdutt I see 30091 was abandoned which stopped from triggering more jobs
I will try to get some help on 30099
sambhavdutt (Thu, 14 Mar 2019 20:58:48 GMT):
@tijohnson thank you
rameshthoomu (Thu, 14 Mar 2019 21:09:16 GMT):
@sudeshrshetty sorry for the noise.. I see blank comment in the merge jobs which is triggering jobs in loop..
rameshthoomu (Thu, 14 Mar 2019 21:09:29 GMT):
I have asked @sambhavdutt to fix this.. please bare 15 more mins
sambhavdutt (Thu, 14 Mar 2019 21:35:38 GMT):
@sudeshrshetty the fix has been merged now, there won't be any more builds triggering back to back if a CR is submtted to sdk-go
sudeshrshetty (Thu, 14 Mar 2019 22:29:06 GMT):
thanks a lot @rameshthoomu @sambhavdutt
sudeshrshetty (Thu, 14 Mar 2019 22:29:50 GMT):
noise is stopped, thanks a lot guys
dave.enyeart (Thu, 14 Mar 2019 22:34:29 GMT):
@rameshthoomu any further thoughts on the `JAVA_URL=` issue in https://jenkins.hyperledger.org/job/fabric-baseimage-verify-docker-s390x/324/console
rameshthoomu (Thu, 14 Mar 2019 23:33:09 GMT):
@dave.enyeart I posed above
rameshthoomu (Thu, 14 Mar 2019 23:33:37 GMT):
https://jira.hyperledger.org/browse/FABB-120
tijohnson (Thu, 14 Mar 2019 23:44:24 GMT):
tr -d [:blank:] to delete space & tab
dave.enyeart (Fri, 15 Mar 2019 00:20:55 GMT):
Thanks @rameshthoomu , I've assigned to @SriramaSharma
vijay.bP (Fri, 15 Mar 2019 15:46:21 GMT):
@rameshthoomu @dave.enyeart @mastersingh24 Please review the CR, to Update pull build artifacts script in master https://gerrit.hyperledger.org/r/#/c/28210/
vijay.bP (Fri, 15 Mar 2019 15:49:22 GMT):
@dave.enyeart Please review this CR and need to be merged "Update multiarch script to publish images to nexus repository along with docker" https://gerrit.hyperledger.org/r/#/c/27291/
vijay.bP (Fri, 15 Mar 2019 18:36:09 GMT):
@rameshthoomu Please rview this CR to pull nodeenv image in baseimage merge build https://gerrit.hyperledger.org/r/#/c/30122/
vijay.bP (Fri, 15 Mar 2019 18:36:09 GMT):
@rameshthoomu Please review this CR to pull nodeenv image in baseimage merge build https://gerrit.hyperledger.org/r/#/c/30122/
rameshthoomu (Fri, 15 Mar 2019 19:10:00 GMT):
@vijay.bP Added comments
vijay.bP (Fri, 15 Mar 2019 19:22:35 GMT):
@rameshthoomu Addressed the comments for the change https://gerrit.hyperledger.org/r/#/c/30122/
rameshthoomu (Fri, 15 Mar 2019 19:24:00 GMT):
@vijay.bP I see issues while downloading binaries with this script https://gerrit.hyperledger.org/r/#/c/28210/. Could you please test all the targets
rameshthoomu (Fri, 15 Mar 2019 20:26:43 GMT):
@harsha @SriramaSharma Is this still open https://jira.hyperledger.org/browse/FABCI-34?
rameshthoomu (Fri, 15 Mar 2019 20:29:17 GMT):
@vijay.bP I don;t think we still need fabric-baseos image from fabric-baseimage.. Could you please submit patch to remove this https://jira.hyperledger.org/browse/FABCI-254
dave.enyeart (Sun, 17 Mar 2019 15:26:58 GMT):
Is somebody looking at the infrastructure issue?
dave.enyeart (Sun, 17 Mar 2019 15:27:04 GMT):
```10:35:45 curl: (22) The requested URL returned error: 502 Bad Gateway
10:35:45 Makefile:220: recipe for target 'build/bin/chaintool' failed```
dave.enyeart (Sun, 17 Mar 2019 15:27:10 GMT):
https://jenkins.hyperledger.org/job/fabric-merge-x86_64/6113/console
dave.enyeart (Sun, 17 Mar 2019 15:27:14 GMT):
been seeing that all morning
sambhavdutt (Sun, 17 Mar 2019 16:48:27 GMT):
Hello Dave, I'm looking at this one, I'll let you know
sambhavdutt (Sun, 17 Mar 2019 17:13:57 GMT):
I can see the chaintool version 1.1.3 in Nexus, and able to download,
https://nexus.hyperledger.org/content/repositories/releases/org/hyperledger/fabric/hyperledger-fabric/chaintool-1.1.3/hyperledger-fabric-chaintool-1.1.3.jar
sambhavdutt (Sun, 17 Mar 2019 17:25:17 GMT):
I see the latest job able to curl this version of chaintool,
https://jenkins.hyperledger.org/view/fabric/job/fabric-merge-x86_64/6114/console
sambhavdutt (Sun, 17 Mar 2019 17:26:35 GMT):
and I just saw that 1.1.1, 1.1.2 and 1.1.3 are in Nexus as expected. I'll monitor these jobs
sambhavdutt (Sun, 17 Mar 2019 17:39:12 GMT):
I can see this one working for 1.1.1 now,
sambhavdutt (Sun, 17 Mar 2019 17:39:21 GMT):
I'll check the rest
sambhavdutt (Sun, 17 Mar 2019 19:13:20 GMT):
this is working for the rest of the versions too
sambhavdutt (Sun, 17 Mar 2019 19:13:20 GMT):
the `curl` is working now in the jobs
sambhavdutt (Sun, 17 Mar 2019 19:14:59 GMT):
the tests are able to download from Nexus
schoppara (Mon, 18 Mar 2019 13:19:33 GMT):
Has joined the channel.
vijay.bP (Mon, 18 Mar 2019 14:37:45 GMT):
@eddie.allen Could you please look into this request https://jira.hyperledger.org/browse/FABCI-307, to install libboost1.55-all-dev on s390x nodes to add mmap-object npm package to the Fabric Node SDK.
sambhavdutt (Mon, 18 Mar 2019 15:40:14 GMT):
Please find the list of open Bugs in the below link,
https://jira.hyperledger.org/issues/?filter=12118
dave.enyeart (Mon, 18 Mar 2019 19:04:48 GMT):
I released and tagged fabric-baseimage 0.4.15 this morning. I see https://hub.docker.com/r/hyperledger/fabric-baseimage/tags/ but not third party images in dockerhub such as https://hub.docker.com/r/hyperledger/fabric-couchdb/tags/ . Any ideas?
sambhavdutt (Mon, 18 Mar 2019 19:23:15 GMT):
I see the latest thirdparty images were not built in this release job(0.4.15), we'll have to get the `make dependent-images` work to publish `0.4.15` thirdparty images to dockerhub and nexus, I'll ask ramesh to retrigger this
sambhavdutt (Mon, 18 Mar 2019 19:23:15 GMT):
I see the latest thirdparty images were not built in this release job(0.4.15), we'll have to get the `make dependent-images` to work to publish `0.4.15` thirdparty images to dockerhub and nexus, I'll ask ramesh to retrigger this
rickr (Mon, 18 Mar 2019 20:15:41 GMT):
@rameshthoomu https://jira.hyperledger.org/browse/FABCI-318
rameshthoomu (Mon, 18 Mar 2019 20:15:54 GMT):
@sambhavdutt @vijay.bP ^^
sambhavdutt (Mon, 18 Mar 2019 21:07:46 GMT):
@dave.enyeart
The thirdparty images are available to pull now from Dockerhub and Nexus
sambhavdutt (Mon, 18 Mar 2019 21:08:11 GMT):
will trigger the multiarch job for this now
sambhavdutt (Mon, 18 Mar 2019 21:08:11 GMT):
will get the multiarch job triggered for baseimage
abedsau (Mon, 18 Mar 2019 21:20:12 GMT):
Has joined the channel.
rameshthoomu (Mon, 18 Mar 2019 21:46:43 GMT):
done
sambhavdutt (Mon, 18 Mar 2019 21:56:18 GMT):
Thank you
dave.enyeart (Tue, 19 Mar 2019 11:07:08 GMT):
@sambhavdutt @C0rWin @BrettLogan @sykesm I've converted `flakes` label in Jira to `ci-flake`. Please update your saved filters accordingly.
BrettLogan (Tue, 19 Mar 2019 11:07:13 GMT):
Has joined the channel.
dave.enyeart (Tue, 19 Mar 2019 11:15:28 GMT):
also converted `ci_failure` to `ci-failure`
dave.enyeart (Tue, 19 Mar 2019 11:16:32 GMT):
Going forward, please pick ONE of these labels for CI issues:
dave.enyeart (Tue, 19 Mar 2019 11:16:37 GMT):
ci-blocker* - true blocker that impacts all CRs for a project and must be addressed to get CI working again
*ci-failure* - consistent failure but not blocking (what is an example?)
*ci-flake* - rename existing 'flakes' to indicate intermittent failure
*ci-first-failure* - label to use the first time an issue is seen, should be closed or converted to one of the three above once more data is available
dave.enyeart (Tue, 19 Mar 2019 11:16:37 GMT):
*ci-blocker* - true blocker that impacts all CRs for a project and must be addressed to get CI working again
*ci-failure* - consistent failure but not blocking (what is an example?)
*ci-flake* - rename existing 'flakes' to indicate intermittent failure
*ci-first-failure* - label to use the first time an issue is seen, should be closed or converted to one of the three above once more data is available
sambhavdutt (Tue, 19 Mar 2019 11:23:57 GMT):
@dave.enyeart
sure, I'll use these labels for issues. I was able to use the ci-blocker that you enabled, now that all 4 are available, I will use these on the new bugs and replace the labels on existing open bugs.
dave.enyeart (Tue, 19 Mar 2019 11:25:24 GMT):
I did a bulk update to change the old `flakes` and `ci_failure`
dave.enyeart (Tue, 19 Mar 2019 11:26:10 GMT):
@sambhavdutt Please look through your https://jira.hyperledger.org/issues/?filter=12118 bugs and ensure labels are correct
dave.enyeart (Tue, 19 Mar 2019 11:26:52 GMT):
I have a widget for each category on the Bugs and Tech Debt dashboard now: https://jira.hyperledger.org/secure/Dashboard.jspa?selectPageId=11706
sambhavdutt (Tue, 19 Mar 2019 11:33:08 GMT):
@dave.enyeart
I'll look into this one and change accordingly, thanks for your effort
rameshthoomu (Tue, 19 Mar 2019 13:28:33 GMT):
@sambhavdutt I have added a comment in https://jira.hyperledger.org/browse/FAB-14483 Could you please modify the description and summary
rameshthoomu (Tue, 19 Mar 2019 13:33:01 GMT):
@dave.enyeart Where we use this script https://github.com/hyperledger/fabric/blob/master/release/templates/get-docker-images.in?
sambhavdutt (Tue, 19 Mar 2019 13:34:04 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=bg2X7T9HZsmgnvbtW) @rameshthoomu I'll look into this
rameshthoomu (Tue, 19 Mar 2019 13:37:40 GMT):
@sambhavdutt is this still open https://jira.hyperledger.org/browse/FAB-14541?
sambhavdutt (Tue, 19 Mar 2019 13:45:07 GMT):
@rameshthoomu It is, but it's intermittent and I have seen it pass at times, I'll close this when this test is consistent
sambhavdutt (Tue, 19 Mar 2019 13:46:49 GMT):
this fail happens in fabric e2e tests in master branch
dave.enyeart (Tue, 19 Mar 2019 14:00:44 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=K5pvPdHSw8LMEPtum) @rameshthoomu Looks like Gari added it...I see it referenced here: https://github.com/hyperledger/fabric/blob/release-1.4/Makefile#L391-L399
dave.enyeart (Tue, 19 Mar 2019 14:02:03 GMT):
@rameshthoomu we could probably remove in favor of pull_build_artifacts.sh... what do you think?
rameshthoomu (Tue, 19 Mar 2019 14:03:41 GMT):
Yes. We push this file to bin directory after run make dist-all or make dist (not sure).. I think the intention is to download the bin tar file and pull the images using that script..
rameshthoomu (Tue, 19 Mar 2019 14:04:27 GMT):
I think most of the people are using bootstrap script now a days.. Not sure who is using this script..
rameshthoomu (Tue, 19 Mar 2019 14:04:37 GMT):
As Gari is here, will check with him..
vijay.bP (Tue, 19 Mar 2019 15:50:37 GMT):
@dave.enyeart ```BYFN,EYFN CUSTOM CHANNEL WITH COUCHDB TEST``` Was working as expected on S390x nodes with the third party image version:0.4.15.
vijay.bP (Tue, 19 Mar 2019 15:50:37 GMT):
@dave.enyeart ```BYFN,EYFN CUSTOM CHANNEL WITH COUCHDB TEST``` Was working as expected on S390x nodes with the third party image version:0.4.15.
https://jenkins.hyperledger.org/sandbox/view/Daily/job/fabric-end-2-end-daily-master-s390x/2/console
dave.enyeart (Tue, 19 Mar 2019 19:24:24 GMT):
@vijay.bP that link is not working for me... I was hoping to look at the byfn output to see the timings
vijay.bP (Tue, 19 Mar 2019 19:28:16 GMT):
@dave.enyeart The sandbox is having some changes undergoing by LF, i think it deleted the job, let me trigger again.
sudeshrshetty (Tue, 19 Mar 2019 20:09:31 GMT):
@rameshthoomu is there any way to re-trigger merge build?
https://jenkins.hyperledger.org/job/fabric-sdk-go-tests-merge-x86_64/1040/
sambhavdutt (Tue, 19 Mar 2019 20:10:24 GMT):
@sudeshrshetty
`remerge-x`
sudeshrshetty (Tue, 19 Mar 2019 20:10:46 GMT):
Thank you @sambhavdutt
sudeshrshetty (Tue, 19 Mar 2019 20:10:57 GMT):
:thumbsup:
bretharrison (Tue, 19 Mar 2019 21:15:04 GMT):
Hello, I have a request for multiple Node.js version testing with fabric-sdk-node
https://jira.hyperledger.org/browse/FABCI-320
sambhavdutt (Tue, 19 Mar 2019 21:25:08 GMT):
@bretharrison
I just saw the Jira description, do you want to run the gulp `run-end-to-end` on Node 8 first, update to node 10, run this again. The tests in this sequence will be required for `release-1.4` and `master` branches, not for any other branches. Please correct me if I'm wrong
bretharrison (Tue, 19 Mar 2019 21:25:59 GMT):
yes and yes
sambhavdutt (Tue, 19 Mar 2019 21:27:04 GMT):
thanks, I'll make this change in the daily jobs and let you know
aso (Wed, 20 Mar 2019 11:41:20 GMT):
folks when are fabric images rebuilt in `fabric-samples` CI runs?
aso (Wed, 20 Mar 2019 11:42:14 GMT):
the CI of this CR (https://gerrit.hyperledger.org/r/#/c/30236/) keeps failing because it uses old images
https://jenkins.hyperledger.org/job/fabric-samples-verify-x86_64/100/consoleFull
```12:33:32 hyperledger/fabric-peer 2.0.0 947d3f0e0031 11 hours ago 46.6MB
12:33:32 hyperledger/fabric-peer amd64-2.0.0 947d3f0e0031 11 hours ago 46.6MB
12:33:32 hyperledger/fabric-peer latest 947d3f0e0031 11 hours ago 46.6MB
```
aso (Wed, 20 Mar 2019 11:43:00 GMT):
I tested on my local node and CIs with images built from the current fabric master are successful
aso (Wed, 20 Mar 2019 11:43:00 GMT):
I tested on my local node and CI runs with images built from the current fabric master are successful
aso (Wed, 20 Mar 2019 11:43:13 GMT):
pls advise
sambhavdutt (Wed, 20 Mar 2019 11:46:27 GMT):
@aso The images are built with latest fabric, ca commit and published to Nexus every day around 8 PM EST. The `fabric-samples` pulls these images, in this case for 2.0.0, in the BYFN, EYFN tests, so any commits after 8 PM will be published the next day
sambhavdutt (Wed, 20 Mar 2019 11:46:27 GMT):
@aso The images are built with latest fabric commit and published to Nexus every day around 8 PM EST. The `fabric-samples` pulls these images, in this case for 2.0.0, in the BYFN, EYFN tests, so any commits after 8 PM will be published the next day
aso (Wed, 20 Mar 2019 11:53:21 GMT):
ack @sambhavdutt, thanks. So I will have to wait another 12h or so till the CI will succeed for my CR
aso (Wed, 20 Mar 2019 11:53:35 GMT):
any chance you can manually pull new images?
sambhavdutt (Wed, 20 Mar 2019 11:55:05 GMT):
@aso I'll check if I can get the publish job triggered again , once that's done, you will get the recent built images on fabric
aso (Wed, 20 Mar 2019 11:55:31 GMT):
thanks a lot - it would be much appreciated
sambhavdutt (Wed, 20 Mar 2019 14:35:17 GMT):
@aso The latest images built from fabric commit `48e73cf49b09d1ef5f4c27ccd948f22badb54127 ` were published to Nexus a while ago, I have retriggered your patch on `fabric- samples` , they will get the latest images now for BYFN/EYFN tests
aso (Wed, 20 Mar 2019 14:47:29 GMT):
yup, running nicely, thx @sambhavdutt
sambhavdutt (Wed, 20 Mar 2019 14:48:32 GMT):
no probs
rameshthoomu (Wed, 20 Mar 2019 23:28:35 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=Ptua6WNPs4Y9fes8z) @sambhavdutt Did you modify this?
rameshthoomu (Wed, 20 Mar 2019 23:32:23 GMT):
@sambhavdutt if possible could you pls node chaincode test in your local machine
sambhavdutt (Thu, 21 Mar 2019 01:54:02 GMT):
@rameshthoomu I have updated the Bug description, I'll check if the node chaincode tests are working on my local system
dave.enyeart (Thu, 21 Mar 2019 02:38:10 GMT):
https://gerrit.hyperledger.org/r/#/c/30265/ - I've extended pull_build_artifacts.sh for the new nodeenv, this image is required when running BYFN with `-l node`. Is there agreement that this is the correct way to get the image pulled (if not building nodeenv yourself)
dave.enyeart (Thu, 21 Mar 2019 02:38:47 GMT):
See related https://jira.hyperledger.org/browse/FAB-14740
sambhavdutt (Thu, 21 Mar 2019 02:47:21 GMT):
`docker pull nexus3.hyperledger.org:10001/hyperledger/fabric-nodeenv:amd64-2.0.0-stable`
can pull the nodeenv image from Nexus, the latest one published today and can be tagged
dave.enyeart (Thu, 21 Mar 2019 10:27:38 GMT):
thanks Sambhav. We do want to keep pull_build_artifacts.sh up to date though right? https://gerrit.hyperledger.org/r/#/c/30265/
dave.enyeart (Thu, 21 Mar 2019 10:28:17 GMT):
Also note `--pull_Thirdparty_Images` results in `Error response from daemon: manifest for nexus3.hyperledger.org:10001/hyperledger/fabric-kafka:amd64- not found`
sambhavdutt (Thu, 21 Mar 2019 10:44:37 GMT):
@dave.enyeart
I agree , we should have the pull_build_artifacts.sh update
about the thirdparty images, we are not publishing them to Nexus from the nightly jobs, I'll check on this
sambhavdutt (Thu, 21 Mar 2019 10:44:37 GMT):
@dave.enyeart
I agree , we should have the pull_build_artifacts.sh update
I'll check on the thirdparty images
vijay.bP (Thu, 21 Mar 2019 13:18:31 GMT):
@dave.enyeart THis CR is to update pull build artifacts script with recent changes in image list https://gerrit.hyperledger.org/r/#/c/28210/
and it is duplicate of https://gerrit.hyperledger.org/r/#/c/30265/
sambhavdutt (Thu, 21 Mar 2019 14:30:38 GMT):
Please find the list of open Bugs as of today
https://jira.hyperledger.org/issues/?filter=12118
dave.enyeart (Thu, 21 Mar 2019 21:05:29 GMT):
@sambhavdutt @vijay.bP I added comments to https://gerrit.hyperledger.org/r/#/c/28210/
dave.enyeart (Thu, 21 Mar 2019 21:06:38 GMT):
@sambhavdutt I recommend stop using your query https://jira.hyperledger.org/issues/?filter=12118 , and start pointing to the new dashboard widgets instead: https://jira.hyperledger.org/secure/Dashboard.jspa?selectPageId=11706
dave.enyeart (Thu, 21 Mar 2019 21:06:38 GMT):
@sambhavdutt I recommend stop using your personal query https://jira.hyperledger.org/issues/?filter=12118 , and start pointing to the new dashboard widgets instead: https://jira.hyperledger.org/secure/Dashboard.jspa?selectPageId=11706
dave.enyeart (Thu, 21 Mar 2019 21:06:49 GMT):
If you want any edits to the dashboard widgets let me know
dave.enyeart (Thu, 21 Mar 2019 21:07:14 GMT):
You can use priority Highest or High for issues you want to highlight
sambhavdutt (Thu, 21 Mar 2019 23:18:21 GMT):
@dave.enyeart
I will address the comments on the CR,
I'll use this widget for the Bugs and label them according to the recent changes
mastersingh24 (Fri, 22 Mar 2019 18:34:20 GMT):
@rameshthoomu - any chance we can push a new set of stable images for Fabric?
mastersingh24 (Fri, 22 Mar 2019 18:34:38 GMT):
or will that happen tonight sometime?
rameshthoomu (Fri, 22 Mar 2019 18:34:48 GMT):
8:00 PM EST>.
rameshthoomu (Fri, 22 Mar 2019 18:34:54 GMT):
but I can trigger them now..
mastersingh24 (Fri, 22 Mar 2019 18:35:35 GMT):
we have a mismatch between Node CC and Fabric right now :(
rameshthoomu (Fri, 22 Mar 2019 18:38:07 GMT):
any new changes related to that in fabric since yesterday night?
mastersingh24 (Fri, 22 Mar 2019 18:39:40 GMT):
yep ... https://gerrit.hyperledger.org/r/30300 is required for Node 10 (which we re-merged)
mastersingh24 (Fri, 22 Mar 2019 18:40:09 GMT):
we can wait until tonight ... no biggie
rameshthoomu (Fri, 22 Mar 2019 18:40:17 GMT):
ok... Triggering them now..
mastersingh24 (Fri, 22 Mar 2019 18:40:22 GMT):
cool. thx!
mastersingh24 (Fri, 22 Mar 2019 18:40:44 GMT):
and then let's :pray_tone5: that I'm correct ;)
mastersingh24 (Fri, 22 Mar 2019 18:41:08 GMT):
I believe this is why the SDK tests are failing on master
rameshthoomu (Fri, 22 Mar 2019 18:41:36 GMT):
ok..
rameshthoomu (Fri, 22 Mar 2019 18:41:56 GMT):
When you get sometime could you please review these changes https://gerrit.hyperledger.org/r/#/q/status:open+project:fabric-ca+topic:pipeline-ca
rameshthoomu (Fri, 22 Mar 2019 18:42:35 GMT):
output looks like this https://jenkins.hyperledger.org/sandbox/blue/organizations/jenkins/fabric-ca-verify-x86_64/detail/fabric-ca-verify-x86_64/22/pipeline
mastersingh24 (Fri, 22 Mar 2019 20:05:38 GMT):
yep ... I started looking at a few of them today
rameshthoomu (Mon, 25 Mar 2019 01:02:06 GMT):
@bretharrison @nkl199 I see fabric-sdk-node builds are aborting after 40 mins build timeout.. Could you please check why the builds are taking more time.. and if you would like to increase the build time out.. please change here https://github.com/hyperledger/fabric-sdk-node/blob/master/Jenkinsfile.x#L5 same as in z..
rameshthoomu (Mon, 25 Mar 2019 01:03:31 GMT):
if builds are taking more time, better to run them in parallel approach. Can we do that .. It seems integration tests are taking 80% of the build time..
yanli133 (Mon, 25 Mar 2019 06:51:34 GMT):
Has joined the channel.
nkl199 (Mon, 25 Mar 2019 09:33:44 GMT):
@rameshthoomu - are there any logs for us to have a look at?
sambhavdutt (Mon, 25 Mar 2019 11:51:13 GMT):
@nkl199
https://jenkins.hyperledger.org/view/fabric-sdk-node/job/fabric-sdk-node-verify-x86_64/2321/
this is one of the builds that aborted due to timeout,
nkl199 (Mon, 25 Mar 2019 11:57:13 GMT):
Thanks - that's not a timeout, it's a test fail on instantiate. I suspect the chaincode being instantiated is out of date with the recently updated shim code
rameshthoomu (Mon, 25 Mar 2019 13:23:43 GMT):
@nkl199 thanks for looking into it. Yes.. I see there are couple of failures which is causing build to run longer time.. Could you please create an issue if you don't have one.. Will track the status.
deallen (Mon, 25 Mar 2019 17:03:38 GMT):
Has joined the channel.
rameshthoomu (Mon, 25 Mar 2019 18:58:37 GMT):
FYI --- gerrit is temporarily unavailable It is up, but there is an LDAP problem
rameshthoomu (Mon, 25 Mar 2019 19:22:52 GMT):
@nkl199 @bretharrison Could you please add comments here https://jira.hyperledger.org/browse/FABN-1189
bretharrison (Mon, 25 Mar 2019 20:48:35 GMT):
What if we also checked an environment variable that would override the release and thirdparty settings of the package.json ? The script that calls the 'gulp test' would have to 'export `FABRIC_SDK_RELEASE=latest` and `FABRIC_SDK_THIRDPARTY=latest`
rameshthoomu (Tue, 26 Mar 2019 04:42:23 GMT):
@jyellick I see below failure in fabric-samples release-1.4
```
00:20:34.124 ===================== peer1.org3 joined channel 'mychannel' =====================
00:20:34.124 Installing chaincode 2.0 on peer0.org3...
00:20:34.124 + peer chaincode install -n mycc -v 2.0 -l java -p github.com/chaincode/chaincode_example02/go/
00:20:34.124 + res=2
00:20:34.124 + set +x
00:20:34.124 2019-03-26 04:21:58.804 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 001 Using default escc
00:20:34.124 2019-03-26 04:21:58.804 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 002 Using default vscc
00:20:34.124 panic: runtime error: invalid memory address or nil pointer dereference
00:20:34.124 [signal SIGSEGV: segmentation violation code=0x1 addr=0x28 pc=0xed342b]
00:20:34.124
```
rameshthoomu (Tue, 26 Mar 2019 04:44:24 GMT):
`peer chaincode install -n mycc -v 2.0 -l java -p github.com/chaincode/chaincode_example02/go/`
rameshthoomu (Tue, 26 Mar 2019 04:45:07 GMT):
container logs are available here https://jenkins.hyperledger.org/job/fabric-samples-verify-x86_64/136/artifact/Docker_Container_Logs/
rameshthoomu (Tue, 26 Mar 2019 04:45:21 GMT):
Will check tomorrow..
jyellick (Tue, 26 Mar 2019 05:23:05 GMT):
@rameshthoomu I'll be happy to investigate tomorrow. FWIW CI has been very flaky for me ever since the earlier disruption to Gerrit. I don't know of anything that's been merged on the peer side in the release-1.4 branch that could have this sort of effect, but will be happy to help you investigate.
rameshthoomu (Tue, 26 Mar 2019 13:25:00 GMT):
sure.. Please let me know when you are free..
rickr (Tue, 26 Mar 2019 15:10:16 GMT):
@rameshthoomu https://jira.hyperledger.org/browse/FABCI-328
rameshthoomu (Tue, 26 Mar 2019 15:13:21 GMT):
@vijay.bP @sambhavdutt ^^
vijay.bP (Tue, 26 Mar 2019 17:26:11 GMT):
@rickr I couldn't able to find dir target/site/apidocs/
rickr (Tue, 26 Mar 2019 17:38:50 GMT):
@rameshthoomu The JSDK build at one time ziped up the target directory. I can't seem to find it anymore. https://jenkins.hyperledger.org/view/fabric-sdk-java/job/fabric-sdk-java-master-verify-x86_64/
rameshthoomu (Tue, 26 Mar 2019 17:41:14 GMT):
Post build step is still looking for .xz extenstion.. Which script is generating .xz file?
talwinder50 (Tue, 26 Mar 2019 20:24:41 GMT):
Has joined the channel.
rameshthoomu (Wed, 27 Mar 2019 13:21:20 GMT):
@andkononykhin this build was running since 21 hr https://jenkins.hyperledger.org/job/indy-node-verify-x86_64/1216/
andkononykhin (Wed, 27 Mar 2019 13:21:23 GMT):
Has joined the channel.
rameshthoomu (Wed, 27 Mar 2019 13:22:36 GMT):
Do you want me to cancel this?
andkononykhin (Wed, 27 Mar 2019 13:23:05 GMT):
yes, please
spartucus (Thu, 28 Mar 2019 02:43:57 GMT):
Has joined the channel.
dave.enyeart (Thu, 28 Mar 2019 15:56:06 GMT):
@rameshthoomu @sambhavdutt Re-assigned https://jira.hyperledger.org/browse/FAB-14395 back to Sambhav. Please see latest comments.
rameshthoomu (Thu, 28 Mar 2019 15:57:43 GMT):
@tijohnson I would like to talk to you regarding this issue.. Though this is not a new issue but this kind of latency issues are failing many builds.. The severity of the problem is very High..
rameshthoomu (Thu, 28 Mar 2019 15:58:05 GMT):
Is it possible to involve infra support team to debug this issue..
dave.enyeart (Thu, 28 Mar 2019 15:58:24 GMT):
This is likely the root cause of many of the flakes in Fabric CI we have seen lately
rameshthoomu (Thu, 28 Mar 2019 15:58:45 GMT):
yes... and this is a long pending issue from LF..
rameshthoomu (Thu, 28 Mar 2019 15:59:52 GMT):
@tijohnson, I think I have forwarded the tests we ran on LF infra nodes and found couple of issue with IO...
rameshthoomu (Thu, 28 Mar 2019 16:00:37 GMT):
May be its; worth taking a deep look at these issues with Infra team...
dave.enyeart (Thu, 28 Mar 2019 16:01:11 GMT):
@rameshthoomu For those of us new to this issue... could you summarize what information has already been collected and sent to infrastructure team? Is it written down anywhere?
rameshthoomu (Thu, 28 Mar 2019 16:01:47 GMT):
yes.. Allen bailey ran these tests on LF infra nodes almost an year ago..
rameshthoomu (Thu, 28 Mar 2019 16:01:56 GMT):
Will forward that email..
rameshthoomu (Thu, 28 Mar 2019 16:06:02 GMT):
@dave.enyeart @tijohnson I have forward the email.. Sub: disk performance on x86 machines
dave.enyeart (Thu, 28 Mar 2019 16:21:43 GMT):
ok, Allen's tests were on IO throughput over a year ago and I don't think anybody is actively investigating that. The problems are not just limited to throughput, at times the IO completely locks up for almost 10 seconds at a time for even the most trivial IO operations.
dave.enyeart (Thu, 28 Mar 2019 16:21:44 GMT):
Discussed with @rameshthoomu and he will open a help desk ticket as well as a Jira infrastructure (IN) issue so that we can track the various IO issues we see.
rameshthoomu (Thu, 28 Mar 2019 16:36:55 GMT):
@tijohnson https://jira.hyperledger.org/browse/IN-59
tijohnson (Thu, 28 Mar 2019 17:09:28 GMT):
@all I have worked on many build systems and a common policy is to minimize dependency on intranet and eliminate dependency on internet
There were a bunch of reasons for doing this, and build reliability has always been a primary one
tongli (Thu, 28 Mar 2019 17:16:41 GMT):
@tijohnson not sure if we can do these things now, when we build we will need to access a lot of places.
tijohnson (Thu, 28 Mar 2019 17:28:40 GMT):
@tongli I understand that, but with increased 'points of failure' the builds are going less robust
a 'wget' that works 99.9 % seems pretty good until you start doing it 1000 times a day in builds
tongli (Thu, 28 Mar 2019 17:30:56 GMT):
Yeah, I understand. I am not seeing a lot of choices though.
tongli (Thu, 28 Mar 2019 17:31:02 GMT):
@tijohnson ^^^
MHBauer (Thu, 28 Mar 2019 17:32:47 GMT):
typically the thing you wget from is a very local server cache, and then you retry a couple times before failing.
MHBauer (Thu, 28 Mar 2019 17:33:17 GMT):
I don't know if we have a local-to-the ci docker registry, and docker doesn't retry, it just, poof, fail.
dave.enyeart (Thu, 28 Mar 2019 17:44:15 GMT):
@tijohnson The most critical issue recently is the IO issues, not the network issues. I've updated IN-59 with some more context.
dave.enyeart (Thu, 28 Mar 2019 17:45:42 GMT):
We are asking Linux Foundation to urgently investigate IO in the CI infrastructure
dave.enyeart (Thu, 28 Mar 2019 17:46:02 GMT):
This is causing CI failures across projects impacting large numbers of developers
yacovm (Thu, 28 Mar 2019 18:06:29 GMT):
can't we use ramFS ? :thinking_face: we don't need lots of "storage space"....
yacovm (Thu, 28 Mar 2019 18:07:14 GMT):
@sykesm ^ is it possible to do that in ginkgo? everyone has *nix anyway
yacovm (Thu, 28 Mar 2019 18:07:14 GMT):
@sykesm ^ is it possible to do that in ginkgo integration tests? everyone has *nix anyway
yacovm (Thu, 28 Mar 2019 18:07:14 GMT):
@sykesm ^ is it possible to do that in ginkgo integration tests? y
yacovm (Thu, 28 Mar 2019 18:07:14 GMT):
@sykesm ^ is it possible to do that in ginkgo integration tests?
sykesm (Thu, 28 Mar 2019 19:49:15 GMT):
Sure; ginkgo doesn't care. The network creates everything in temporary directories so point TMPDIR to a tmpfs and it will use that.
Henrycoffin (Sun, 31 Mar 2019 09:28:11 GMT):
Has joined the channel.
sunit.versatile (Mon, 01 Apr 2019 08:29:01 GMT):
Has joined the channel.
pandrejko (Mon, 01 Apr 2019 15:26:28 GMT):
Who can help with why the linter is failing for this cr: https://gerrit.hyperledger.org/r/#/c/30511/
I see this report: https://logs.hyperledger.org/production/vex-yul-hyp-jenkins-3/fabric-verify-build-checks-x86_64/12617/console.log.gz
rameshthoomu (Mon, 01 Apr 2019 15:51:37 GMT):
@pandrejko Could you please rebase your change..
pandrejko (Mon, 01 Apr 2019 15:58:05 GMT):
@negupta ^^
negupta (Mon, 01 Apr 2019 15:58:05 GMT):
Has joined the channel.
negupta (Mon, 01 Apr 2019 20:36:50 GMT):
Thanks ramesh. Built
george.aristy (Tue, 02 Apr 2019 20:33:26 GMT):
Has joined the channel.
vijay.bP (Wed, 03 Apr 2019 15:24:53 GMT):
@dave.enyeart @sykesm any inputs on this to keep or abandon https://gerrit.hyperledger.org/r/#/c/28210/
dave.enyeart (Wed, 03 Apr 2019 17:20:21 GMT):
I have found it useful for doing pre-release testing, and I expect others would find it useful (if it were documented). Most people have no idea how to pull pre-release images and binaries. @sykesm if we don't keep this specific script... what would you recommend to people that want to pull down pre-release images and binaries?
dave.enyeart (Wed, 03 Apr 2019 17:21:13 GMT):
I'm open to alternatives, but I wouldn't remove what we have until an alternative is available.
troyronda (Wed, 03 Apr 2019 18:59:48 GMT):
I'm wondering how do we get a new version of Go onto the CI (1.12.1)? https://gerrit.hyperledger.org/r/c/30695/5/ci.properties#7
sambhavdutt (Wed, 03 Apr 2019 19:08:57 GMT):
@troyronda
this is good for the sdk-go jobs to pickup the version from `ci.properties` file, before that we need to update it in Jenkins , the current available version is 1.11.5
rameshthoomu (Wed, 03 Apr 2019 19:10:27 GMT):
@troyronda could you please push patch to ci-mamangement repository by changing this line https://github.com/hyperledger/ci-management/blob/master/packer/provision/docker.sh#L109
troyronda (Wed, 03 Apr 2019 19:11:55 GMT):
ok, thanks!
swetha (Wed, 03 Apr 2019 21:56:18 GMT):
@rameshthoomu we have one open question about this patch: https://gerrit.hyperledger.org/r/#/c/30448/. We want to understand why this is necessary? https://gerrit.hyperledger.org/r/#/c/30448/8/Jenkinsfile@114 Are we not running in containers? Does lack of cleanup affect other runs? Also can we get a link to the ci scripts that will handle the cache of third party images? Thanks!
swetha (Wed, 03 Apr 2019 23:44:21 GMT):
@MHBauer ^^
rameshthoomu (Thu, 04 Apr 2019 01:03:43 GMT):
@swetha these lines execute after the build is complete https://gerrit.hyperledger.org/r/#/c/30448/8/Jenkinsfile@114.. Just for clenaup all the containers after the build is done..
See this script https://github.com/hyperledger/ci-management/blob/master/packer/provision/docker.sh#L122 for some reason, cleanup script is deleting cached images.. That's the reason, evm build is taking few more mins..
rameshthoomu (Thu, 04 Apr 2019 01:04:02 GMT):
@vijay.bP could you please check the cleanup script..
rameshthoomu (Thu, 04 Apr 2019 01:48:49 GMT):
@vijay.bP ignore my above comment..
rameshthoomu (Thu, 04 Apr 2019 01:49:13 GMT):
chaincode-evm is using 0.4.13 which we are not caching in packer..
mbwhite (Thu, 04 Apr 2019 12:26:53 GMT):
Hello - the fabric-node-sdk had the zOS build disabled recently - could I request the same for the node-chaincode builds pleasE?
rameshthoomu (Thu, 04 Apr 2019 13:37:06 GMT):
@mbwhite could you please create JIRA task in https://jira.hyperledger.org/projects/FABCI
mbwhite (Thu, 04 Apr 2019 14:02:37 GMT):
@rameshthoomu certainly done...
rameshthoomu (Thu, 04 Apr 2019 14:16:44 GMT):
thanks..
rameshthoomu (Thu, 04 Apr 2019 14:17:33 GMT):
@sambhavdutt https://jira.hyperledger.org/browse/FABCI-332 - Simple change.. could you pls push now
sambhavdutt (Thu, 04 Apr 2019 14:19:29 GMT):
@rameshthoomu
sure, I'll make this change
rameshthoomu (Thu, 04 Apr 2019 14:22:01 GMT):
@sambhavdutt wait..
sambhavdutt (Thu, 04 Apr 2019 14:22:22 GMT):
ok
rameshthoomu (Thu, 04 Apr 2019 14:22:30 GMT):
@mbwhite s390x job is publishing nodeenv image.. So there is a dependency
mbwhite (Thu, 04 Apr 2019 14:23:21 GMT):
not the x86?
mbwhite (Thu, 04 Apr 2019 14:23:23 GMT):
mm
mbwhite (Thu, 04 Apr 2019 14:23:37 GMT):
can we swap that do you think to the x86?
rameshthoomu (Thu, 04 Apr 2019 14:25:47 GMT):
I mean from both x and z jobs publishes nodeenv images
rameshthoomu (Thu, 04 Apr 2019 14:27:02 GMT):
with the dependency we need both these jobs...
rameshthoomu (Thu, 04 Apr 2019 14:27:02 GMT):
with that dependency we need both these jobs...
mbwhite (Thu, 04 Apr 2019 14:27:08 GMT):
and we need specific z nodeenv
mbwhite (Thu, 04 Apr 2019 14:27:12 GMT):
okay
rameshthoomu (Thu, 04 Apr 2019 14:37:50 GMT):
we can do one thing.. Disable publishing images from merge jobs and keep them in the daily jobs..
rameshthoomu (Thu, 04 Apr 2019 14:37:50 GMT):
we can do one thing.. Disable publishing images from merge jobs and keep them from daily jobs..
sambhavdutt (Thu, 04 Apr 2019 16:28:23 GMT):
@rameshthoomu @andrew-coleman
Can you review this CR for the gatway-java
https://gerrit.hyperledger.org/r/#/c/30737/
sambhavdutt (Thu, 04 Apr 2019 16:29:38 GMT):
@rameshthoomu @tijohnson
And this one too for the jobs
https://gerrit.hyperledger.org/r/#/c/30739/
rameshthoomu (Thu, 04 Apr 2019 16:32:46 GMT):
ok.. Thanks Sambhav..
vijay.bP (Thu, 04 Apr 2019 17:18:59 GMT):
@latitiah Can i test the interop tests on sandbox now, do the interop targets ready for test.
andrew-coleman (Thu, 04 Apr 2019 18:08:31 GMT):
@sambhavdutt thanks, looks good to me. @rameshthoomu are you happy for me merge this?
rameshthoomu (Thu, 04 Apr 2019 18:08:55 GMT):
No.. we are waiting for credentails to set in Jenkins config..
andrew-coleman (Thu, 04 Apr 2019 18:09:30 GMT):
ok, I'll await your go ahead - thanks
rameshthoomu (Thu, 04 Apr 2019 18:09:44 GMT):
Do you know why the tests are failing?
latitiah (Thu, 04 Apr 2019 18:10:33 GMT):
@vijay.bP : Once https://gerrit.hyperledger.org/r/#/c/30733/ is merged it will be ready to go
andrew-coleman (Thu, 04 Apr 2019 18:10:47 GMT):
no - I need to put more logging in. I wonder if it's not downloading the fabric docker images for some reason
rameshthoomu (Thu, 04 Apr 2019 18:11:05 GMT):
yes.. Will ask sambhav to work with you..
andrew-coleman (Thu, 04 Apr 2019 18:11:11 GMT):
thanks
sambhavdutt (Thu, 04 Apr 2019 18:36:08 GMT):
@andrew-coleman @rameshthoomu
I will look into this and let you know
sambhavdutt (Thu, 04 Apr 2019 18:36:08 GMT):
@andrew-coleman @rameshthoomu
I will follow up this and let you know
nfrunza (Fri, 05 Apr 2019 21:16:39 GMT):
hello, i see a build failure in jenkins, https://jenkins.hyperledger.org/job/blockchain-explorer-verify-x86_64/104/console
rameshthoomu (Fri, 05 Apr 2019 21:42:01 GMT):
Could be network issue.. let me re-trigger
nfrunza (Sun, 07 Apr 2019 15:32:33 GMT):
thanks, it worked
rameshthoomu (Mon, 08 Apr 2019 18:07:30 GMT):
@dave.enyeart regarding fabric-baseos name change https://jira.hyperledger.org/browse/FAB-15114
dave.enyeart (Mon, 08 Apr 2019 18:44:51 GMT):
@rameshthoomu Added a comment there as follows: Agreed we should rename baseos in master before the final v2.0 release. In the shorter term we will simply not tag images from master as 'latest' in dockerhub, so as to not impact v1.4.x users. For example the 2.0.0-alpha images will only be tagged as 2.0.0-alpha.
rameshthoomu (Mon, 08 Apr 2019 19:12:46 GMT):
ok thanks for the info.. @sambhavdutt Could you please update multiarch script in fabric repo..
sambhavdutt (Mon, 08 Apr 2019 19:13:18 GMT):
@rameshthoomu
yes, I'll submit a CR for this
GeenNuar (Tue, 09 Apr 2019 03:34:17 GMT):
Has joined the channel.
MHBauer (Tue, 09 Apr 2019 19:56:17 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=GrEn79iT6Dn42cQ3t) @dave.enyeart It would be great if we could stop tagging latest and remove any use that's already been pushed. It's a commonly misused 'feature'.
dave.enyeart (Tue, 09 Apr 2019 20:06:52 GMT):
@MHBauer Good point, we're not going to use 'latest' for v2.0.0-alpha, and I think I agree with you that we should remove it completely going forward. I'll bring up with maintainers.
scottz (Tue, 09 Apr 2019 22:08:06 GMT):
I just created this issue. Does this sound familiar (is it a known issue observed anywhere else)? https://jira.hyperledger.org/browse/FAB-15128 "Error: Cannot find module 'fabric-client/lib/User.js'"
troyronda (Wed, 10 Apr 2019 14:02:23 GMT):
I am seeing failures in the CI: 13:49:14 [fabric-sdk-go-verify-s390x] $ /bin/bash -ue /tmp/jenkins3816116853944182439.sh
13:49:14 ----> verify-commit.sh
13:49:14 fatal: Not a git repository (or any of the parent directories): .git
13:49:14 fatal: Not a git repository (or any of the parent directories): .git
13:49:14 Build step 'Execute shell' marked build as failure
troyronda (Wed, 10 Apr 2019 14:02:31 GMT):
https://jenkins.hyperledger.org/job/fabric-sdk-go-verify-s390x/124/console
rameshthoomu (Wed, 10 Apr 2019 14:30:24 GMT):
@TimJohnson made some change to this script yesterday..
rameshthoomu (Wed, 10 Apr 2019 14:30:28 GMT):
@tim
rameshthoomu (Wed, 10 Apr 2019 14:30:28 GMT):
@TimJohnson ^^
troyronda (Wed, 10 Apr 2019 14:56:47 GMT):
Ok - I created this jira item: https://jira.hyperledger.org/browse/FABCI-337
Vasanth (Thu, 11 Apr 2019 11:06:54 GMT):
Has joined the channel.
MHBauer (Thu, 11 Apr 2019 20:27:57 GMT):
@rameshthoomu looking at the changes in https://gerrit.hyperledger.org/r/#/c/30448/ makes me very concerned for the setup of CI as a whole.
MHBauer (Thu, 11 Apr 2019 20:28:37 GMT):
I think we were under the impression that our builds were isolated inside container or something.
MHBauer (Thu, 11 Apr 2019 20:29:11 GMT):
It doesn't make sense to me to have each build ensure it's cleaning up the environment. That should be something automatic.
MHBauer (Thu, 11 Apr 2019 20:32:14 GMT):
the hardcoding of specifically available go versions is also seems strange. the ones in there are 4 point releases behind.
MHBauer (Thu, 11 Apr 2019 22:57:51 GMT):
If I were to remove this part:
```
// Delete containers
fabBuildLibrary.deleteContainers()
// Delete unused docker images
fabBuildLibrary.deleteUnusedImages()
```
what would happen? build machines fill up? How is that any individual projects responsibility?
swetha (Fri, 12 Apr 2019 00:00:01 GMT):
In regards to the same patch that @MHBauer is talking about above, I am also curious about this piece:
```
// Don't fail the build if there is no log file
archiveArtifacts allowEmptyArchive: true, artifacts: '**/*.log'
```
What is the default behavior?
swetha (Fri, 12 Apr 2019 00:06:15 GMT):
I was confused by the comment above
rameshthoomu (Fri, 12 Apr 2019 13:47:23 GMT):
@MHBauer We use x86_64 vexx build nodes pre-loaded with a packer image not the containers. Once the Jenkins build get triggered, Jenkins identifies a build node (say vm). These nodes get purged after the build is done. One build = one vm
rameshthoomu (Fri, 12 Apr 2019 13:51:56 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=QpdcuarxftoBH6itH) @MHBauer We can update Jenkins file to get latest version from fabric Makefile.. something like this
`GO_VER=$(curl -O https://raw.githubusercontent.com/hyperledger/fabric/master/ci.properties && cat ci.properties | grep "GO_VER" | cut -d "=" -f2)`
rameshthoomu (Fri, 12 Apr 2019 13:54:56 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=ijZMy24uZTyuhaopM) @MHBauer Nothing will happen.. as we purge the vm after the build is done (it deletes all the build artifacts).. We usually use these lines between test to test.. but as this is in post build action.. we don't need these steps..
rameshthoomu (Fri, 12 Apr 2019 16:06:06 GMT):
@BrettLogan
Mayank017 (Thu, 18 Apr 2019 06:21:23 GMT):
Has joined the channel.
sachinbal (Mon, 22 Apr 2019 03:39:59 GMT):
Has joined the channel.
rameshthoomu (Wed, 24 Apr 2019 15:24:18 GMT):
@dave.enyeart Take a look at this task https://jira.hyperledger.org/browse/FAB-15114 - change the fabric-baseos image name in fabric repo.
rameshthoomu (Wed, 24 Apr 2019 15:26:19 GMT):
@dave.enyeart is this a valid task https://jira.hyperledger.org/browse/FAB-14800?
tijohnson (Thu, 25 Apr 2019 15:04:41 GMT):
@all RocketChat Upgrade Tue Apr 30th at 5PM EST (30min downtime)
Fias (Fri, 26 Apr 2019 06:49:11 GMT):
Has joined the channel.
dave.enyeart (Fri, 26 Apr 2019 16:13:37 GMT):
@rameshthoomu I've assigned the former to myself. The latter is valid in the short term, in the longer term we should re-assess how samples are tested.
rickr (Tue, 30 Apr 2019 11:58:12 GMT):
FAILURE (skipped) Maybe never noticed it on the JSDK but what does the _skipped_ imply I also see SUCCESS ( _skipped_ ) ?
sambhavdutt (Tue, 30 Apr 2019 12:01:34 GMT):
@rickr
Can you point me to the test that skipped
sambhavdutt (Tue, 30 Apr 2019 12:01:55 GMT):
or the GERRIT CR
rickr (Tue, 30 Apr 2019 12:04:37 GMT):
https://jenkins.hyperledger.org/job/fabric-verify-unit-tests-x86_64/11745/
sambhavdutt (Tue, 30 Apr 2019 12:23:34 GMT):
@rickr thank you
I see that the unit-tests started but failed as the timeout exceeded and this test failed in `TestParallelSend` , we can retrigger the individual test in this case
rickr (Tue, 30 Apr 2019 12:41:54 GMT):
I think I did do the re run. I was just more curious about the _skipped_
sambhavdutt (Tue, 30 Apr 2019 14:17:30 GMT):
@rickr
the skipping of the build happens in 2 cases,
1. When we submit an update to CR and push it to Gerrit, the tests will start again and the current build if still running is aboted/skipped
2. When we try to retrigger/rerun with the job/build with comment phrase, before the job/build is completed, this would abort/skip the running job and trigger it from beginning
vijay.bP (Wed, 01 May 2019 13:53:06 GMT):
@mbwhite Could you please have a look on this bug https://jira.hyperledger.org/browse/FAB-15312 , `test-fv-shim, test-e2e are failing consistently in s390x as timeout exceeded`
mbwhite (Wed, 01 May 2019 14:13:32 GMT):
@vijay.bP we've been struggling with timeouts for a long time; it does seem that things are just slow..
mbwhite (Wed, 01 May 2019 14:14:20 GMT):
not sure if there's much can be done on the CI side.. we'll see about reducing the buiodl somwhoe
vijay.bP (Wed, 01 May 2019 14:24:38 GMT):
I see it's not possible from CI.
sambhavdutt (Thu, 02 May 2019 13:48:50 GMT):
@tijohnson
I have disabled the Nexus publish for gateway-java, but the github pages are not updating too,
```
org.jenkinsci.plugins.credentialsbinding.impl.CredentialNotFoundException: Could not find credentials entry with ID 'gateway-java-credentials'
```
can you help
sambhavdutt (Thu, 02 May 2019 13:49:29 GMT):
https://jenkins.hyperledger.org/view/fabric-gateway-java/job/fabric-gateway-java-merge-x86_64/2/console
tijohnson (Thu, 02 May 2019 15:22:57 GMT):
@sambhavdutt This is a new credential, one that does not currently exist?
sambhavdutt (Thu, 02 May 2019 15:24:07 GMT):
I think so, I was not able to locate this in the Global configuration
tijohnson (Thu, 02 May 2019 15:30:53 GMT):
at the lowest level what is happening what command is actually getting this error?
tijohnson (Thu, 02 May 2019 15:30:53 GMT):
@sambhavdutt at the lowest level what is happening what command is actually getting this error?
sambhavdutt (Thu, 02 May 2019 15:55:48 GMT):
https://github.com/hyperledger/fabric-gateway-java/blob/master/scripts/ci_scripts/publishJavaApiDocs.sh
sambhavdutt (Thu, 02 May 2019 15:56:05 GMT):
this script is failing to publish the docs to github
tijohnson (Thu, 02 May 2019 16:42:55 GMT):
@sambhavdutt Do you know which command is failing ?
tijohnson (Thu, 02 May 2019 17:39:45 GMT):
looking at publishJavaApiSDocs.sh: are GATEWAY_JAVA_USERNAME & GATEWAY_JAVA_PASSWORD defined ?
sambhavdutt (Thu, 02 May 2019 18:34:05 GMT):
@tijohnson
yes, I have done this just like the other repos that publish docs to github,
sambhavdutt (Thu, 02 May 2019 18:35:25 GMT):
the actual id and password for these variables must be setup in Jenkins, what was shared to you, as I won't have the access to view/modify that
pvrbharg (Wed, 08 May 2019 12:09:35 GMT):
@tijohnson @sambhavdutt - I am looking for CI/CD pipeline presentation of some of core fabric repo builds such as - fabric, fabric-ca, fabric-samples, fabric-sdk-*, etc. Could someone please point me to a ppt or pdf document? I am aware of a playback video that Ramesh has delivered sometime ago and it is available in our playback catalogs... I am looking for low bandwidth friendly content.. Thanks in advance
vijay.bP (Wed, 08 May 2019 13:22:49 GMT):
@pvrbharg Please go through these docs for the pipeline configuration in respective repo’s, fabric is not ready and is there anything I help you, let me know.
https://github.com/hyperledger/fabric-sdk-node/blob/master/docs/sdk-node-ci.md
https://github.com/hyperledger/fabric-samples/blob/master/docs/fabric-samples-ci.md
https://github.com/hyperledger/fabric-ca/blob/master/docs/source/ca-ci.md
pvrbharg (Wed, 08 May 2019 13:27:38 GMT):
Dear Vijay - thank you and this is helpful and I am aware of these resource URLs - do you have a pdf or ppt that I can more readily use for presentation - basically how we use CI/CD for projects I mentioned. Thanks
wenjian (Wed, 08 May 2019 13:31:51 GMT):
CR https://gerrit.hyperledger.org/r/#/c/31269/ didn't trigger a verify build. I submitted a `reverify`, but still no verify build. Can someone help?
scottz (Wed, 08 May 2019 13:48:09 GMT):
I noticed that changeset was in fabric-test repo, on branch 1.4, but a similar changeset on master branch correctly triggered the verify build. @vijay.bP could you shed some light on wenjian's question?
mbwhite (Wed, 08 May 2019 14:40:01 GMT):
Hello; I'm looking at `fabric-chaincode-java` builds at present.. the test results and coverage reports are written out as HTML; locally I can see these - is there a way to get them included int he build reports?
sambhavdutt (Wed, 08 May 2019 14:58:51 GMT):
@mbwhite
Do you want the logs for each of these tests when the test is complete, in the Jenkins console that you can view, please correct me if I’m wrong
sambhavdutt (Wed, 08 May 2019 14:58:51 GMT):
@mbwhite
Do you want the logs for each of these tests when the test is complete, in the Jenkins console that you can view
mbwhite (Wed, 08 May 2019 15:00:30 GMT):
or just as a zip file I can download to review... they are HTML so probably doesn't make sense to view in the console
sambhavdutt (Wed, 08 May 2019 15:03:14 GMT):
I'll try to get the html file that you can view/download. I will let you know when done
mbwhite (Wed, 08 May 2019 15:49:34 GMT):
thanks
vijay.bP (Wed, 08 May 2019 17:38:17 GMT):
@wenjian @tijohnson We have faced this issue occasionally, and there is bug created for this type https://jira.hyperledger.org/browse/FABCI-116
vijay.bP (Wed, 08 May 2019 17:39:03 GMT):
@wenjian @tijohnson We have faced this issue occasionally, and there is bug created for this type https://jira.hyperledger.org/browse/FABCI-116
sambhavdutt (Wed, 08 May 2019 20:37:39 GMT):
@mbwhite
https://jenkins.hyperledger.org/sandbox/view/All/job/fabric-chaincode-java-merge-x86_64/3/artifact/fabric-chaincode-integration-test/build/reports/tests/test/
this is a sample of how the index.html file will be, in view or the zip format that can be downloaded
sambhavdutt (Wed, 08 May 2019 20:37:39 GMT):
@mbwhite
https://jenkins.hyperledger.org/sandbox/view/All/job/fabric-chaincode-java-merge-x86_64/3/artifact/fabric-chaincode-integration-test/build/reports/tests/test/
this is a sample of how the index.html file will be, in view or the zip format that can be downloaded, I have submitter a CR for this, the html file will be archived as soon as this CR is merged https://gerrit.hyperledger.org/r/#/c/31288/
mbwhite (Thu, 09 May 2019 08:42:29 GMT):
Very good :-) Once question - what reports are being collected... ?
mbwhite (Thu, 09 May 2019 08:42:46 GMT):
there are some coverage and unit test reports - are they being collected as well
vijay.bP (Thu, 09 May 2019 14:44:12 GMT):
@wenjian Please check with the CR, the verify job has been triggered sorry for the delay, good to go further https://gerrit.hyperledger.org/r/#/c/31269/
wenjian (Thu, 09 May 2019 14:46:09 GMT):
Thank you @vijay.bP
sambhavdutt (Thu, 09 May 2019 15:53:22 GMT):
Currently .log, .html files and the console output which has the build steps in detail
sambhavdutt (Thu, 09 May 2019 16:03:22 GMT):
If there are log files generated during the tests, they will be archived
mbwhite (Thu, 09 May 2019 16:03:42 GMT):
thanks... will give a go :-)
MHBauer (Thu, 09 May 2019 19:16:24 GMT):
Would it be possible to have the bot post once per PR the commands it accepts?
MHBauer (Thu, 09 May 2019 19:16:31 GMT):
or a link to the commands it accepts?
MHBauer (Thu, 09 May 2019 19:16:47 GMT):
I can never remember them and it would be helpful to have a reference.
MHBauer (Thu, 09 May 2019 19:17:05 GMT):
and point me at where to make a change if I can help to make a change.
BrettLogan (Mon, 13 May 2019 17:40:44 GMT):
@MHBauer we can do that. That change would be appreciated actually, I feel the same way, always have to refer to documentation on what the reverify commands are, as we have multiple commands based on repo. Probabl a good chance to standardize and create a post back message to the gerrit issue
BrettLogan (Mon, 13 May 2019 17:40:44 GMT):
@MHBauer we can do that. That change would be appreciated actually, i feel the same way, always have to refer tp documentation on what the reverify commands are, as we have multiple commands based on repo. Probbapy a good chancr to standardize and create a post back message to the getrit issue
BrettLogan (Mon, 13 May 2019 17:40:44 GMT):
@MHBauer we can do that. That change would be appreciated actually, I feel the same way, always have to refer to documentation on what the reverify commands are, as we have multiple commands based on repo. Probbapy a good chancr to standardize and create a post back message to the getrit issue
BrettLogan (Mon, 13 May 2019 17:40:44 GMT):
@MHBauer we can do that. That change would be appreciated actually, I feel the same way, always have to refer to documentation on what the reverify commands are, as we have multiple commands based on repo. Probably a good chance to standardize and create a post back message to the gerrit issue
BrettLogan (Mon, 13 May 2019 17:41:30 GMT):
Ill open an issue and we will get it in
MHBauer (Mon, 13 May 2019 22:06:41 GMT):
that would be perfect. Willing to help if given some pointers. Or review once written up.
mbwhite (Tue, 14 May 2019 12:47:29 GMT):
Chaincode shim releases: For Node.js there is a master branch - snapshot published per build. For Java chaincode there is only something published on alpha/beta/ga releases.
Wanted to float the idea of doing something more regularly for Java as well. Not every build - but something more regular, every couple of weeks maybe?
Any thoughts from a CI perspective?
rameshthoomu (Tue, 14 May 2019 13:15:58 GMT):
@mbwhite Opened Jira task for this https://jira.hyperledger.org/browse/IN-61 . We have to configure Jenkins to store GPG keys to publish Jar files.. As on today, this is a manual process, but above Jira will help us to publish jar files to maven central.
mbwhite (Tue, 14 May 2019 13:16:31 GMT):
Thanks
BrettLogan (Tue, 14 May 2019 14:11:12 GMT):
@MHBauer here is the change we discussed. I added a message if the VerifyBuild step fails as to what the reverify command is: `Code checks failed, reply with VerifyBuild to run code checks again`. Adding an initial post-back message isn't possible without some additional refactoring. The regular expression for triggering builds via reply would pick those initial messages up as triggers if we included any of the other commands. I also elected not to dig into that too much, as the other steps have their actual messages posted in the Gerrit CR when the other tests are triggered. After VerifyBuild passes, Jenkins posts `Succeeded, Run IntegrationTest, Run UnitTest` to the Gerrit CR which triggers the other tests. So you can refer to that for the command. We can work on refactoring the regexes and messages Jenkins posts so we can provide an initial message at some point in the future
BrettLogan (Tue, 14 May 2019 14:11:14 GMT):
https://gerrit.hyperledger.org/r/c/31361/
BrettLogan (Tue, 14 May 2019 14:11:25 GMT):
https://gerrit.hyperledger.org/r/c/31365/
BrettLogan (Tue, 14 May 2019 14:11:25 GMT):
https://gerrit.hyperledger.org/r/c/31361/
BrettLogan (Tue, 14 May 2019 14:12:50 GMT):
If you decide to pull the CI-Management repo, be sure to run `git submodule update --init --recursive` from the root of the repo to pull the Linux Foundations submodules
tommyjay (Tue, 14 May 2019 14:19:10 GMT):
Has joined the channel.
tommyjay (Tue, 14 May 2019 14:19:11 GMT):
hey there quick question. why did fabric move away from using the `github.com/docker/docker` client?
BrettLogan (Tue, 14 May 2019 17:38:31 GMT):
@tommyjay We never officially used Moby. I actually did the work to implement Moby throughout Fabric but we ultimately decided to punt on it and abandon the transition. Moby wasn't nearly as mature as the current library we use. The amount of workaround that was required to perform the simple functionality that was innate to our current library just wasn't worth the headache. Until such a time as Moby catches up, or, there is a breaking change in the client we use vs. what we need Docker to do, we decided to stick with the current client
andkononykhin (Wed, 15 May 2019 08:44:12 GMT):
Has left the channel.
BrettLogan (Wed, 15 May 2019 13:38:29 GMT):
tommyjay We never officially used Moby. I actually did the work to implement Moby throughout Fabric but we ultimately decided to punt on it and abandon the transition. Moby wasn't nearly as mature as the current library we use. The amount of workaround that was required to perform the simple functionality that was innate to our current library just wasn't worth the headache. Until such a time as Moby catches up, or, there is a breaking change in the client we use vs. what we need Docker to do, we decided to stick with the current client
rickr (Wed, 15 May 2019 18:10:15 GMT):
I'm seeing consistent JSDK build fails on a corrupted file in the jdk. Seems to be the 1.4 builds .. but the JSDK code is exactly the same.
https://jenkins.hyperledger.org/job/fabric-sdk-java-master-verify-1.4-x86_64/43/console
```
13:35:45 [INFO] -------------------------------------------------------------
13:35:45 [ERROR] COMPILATION ERROR :
13:35:45 [INFO] -------------------------------------------------------------
13:35:45 [ERROR] /w/workspace/fabric-sdk-java-master-verify-1.4-x86_64/src/main/java/org/hyperledger/fabric_ca/sdk/Attribute.java:[52,11] cannot access java.math.BigDecimal
13:35:45 bad class file: /usr/lib/jvm/java-8-openjdk-amd64/lib/ct.sym(META-INF/sym/rt.jar/java/math/BigDecimal.class)
13:35:45 unable to access file: corrupted zip file
13:35:45 Please remove or make sure it appears in the correct subdirectory of the classpath.
13:35:45 [INFO] 1 error
13:35:45 [INFO] -------------------------------------------------------------
13:35:45 [INFO] ------------------------------------------------------------------------
13:35:45 [INFO] BUILD FAILURE
13:35:45 [INFO] ------------------------------------------------------------------------
```
@rameshthoomu @sambhavdutt @tijohnson
rickr (Wed, 15 May 2019 18:13:04 GMT):
here too -> https://gerrit.hyperledger.org/r/#/c/31386/
vijay.bP (Wed, 15 May 2019 18:26:36 GMT):
@rickr The error is coming from the CR you pushed, it doesn't relate to the verify build.
rickr (Wed, 15 May 2019 18:27:44 GMT):
what leads you to that ?
rickr (Wed, 15 May 2019 18:28:18 GMT):
The code is the same for 1.4 and 2.0 that's being built .. the error message points to a corrupt file
rickr (Wed, 15 May 2019 18:28:39 GMT):
2.0 seems to build
vijay.bP (Wed, 15 May 2019 18:36:33 GMT):
May be a flake, please retrigger again.
rickr (Wed, 15 May 2019 19:10:57 GMT):
I have been https://gerrit.hyperledger.org/r/#/c/31386/
But they're not kicking off or they're not showing up in the gerrit UI. Another flake?
vijay.bP (Wed, 15 May 2019 19:37:42 GMT):
@rickr I triggered them up, but saw the same issue with compilation error.
rickr (Wed, 15 May 2019 19:38:33 GMT):
yes - corrupted file. The error is now slightly different. Seems to be unreliable :(
vijay.bP (Wed, 15 May 2019 19:39:40 GMT):
I'm opening a JIRA for this issue now.
rickr (Wed, 15 May 2019 21:35:20 GMT):
It fails with different messages making it seem that file is somehow bad. Up above it was BigDecimal.class on another run below ArrayIndexOutOfBoundsException.class
Has to be environmental -- blame it on global warming?
```
16:04:11 [INFO] -------------------------------------------------------------
16:04:11 [ERROR] COMPILATION ERROR :
16:04:11 [INFO] -------------------------------------------------------------
16:04:11 [ERROR] /w/workspace/fabric-sdk-java-master-verify-1.4-x86_64/src/main/java/org/hyperledger/fabric/sdk/BlockInfo.java:[720,31] cannot access java.lang.ArrayIndexOutOfBoundsException
16:04:11 bad class file: /usr/lib/jvm/java-8-openjdk-amd64/lib/ct.sym(META-INF/sym/rt.jar/java/lang/ArrayIndexOutOfBoundsException.class)
16:04:11 unable to access file: corrupted zip file
```
rickr (Thu, 16 May 2019 00:16:56 GMT):
@tijohnson Are we starting with a *fresh* vm with just prereqs each time are they being just reused. Like for 1.4 having fabric docke images already present and for java the maven cash still present? I don't know if there is a later 1.8 java but see if updating that may help?
tijohnson (Thu, 16 May 2019 00:19:36 GMT):
Each build is a fresh VM that is part of our speed problems... it takes a couple of mins to before the actual can start
tijohnson (Thu, 16 May 2019 00:19:36 GMT):
@rickr Each build is a fresh VM that is part of our speed problems... it takes a couple of mins to before the actual can start
tijohnson (Thu, 16 May 2019 00:21:18 GMT):
I see in your scripts where they sometimes assume that cruft could be left over from previous build
rickr (Thu, 16 May 2019 00:27:29 GMT):
So the vm is created from a `template` then started (from turned off) and then the build starts?
tijohnson (Thu, 16 May 2019 00:28:27 GMT):
yup
tijohnson (Thu, 16 May 2019 00:28:27 GMT):
@rickr yup
tijohnson (Thu, 16 May 2019 00:29:43 GMT):
some minor stuff happens after boot but before build (like create 'jenkins' user account and install ssh keys
rickr (Thu, 16 May 2019 00:31:07 GMT):
has with in that last week any changes happened to that template ?
tijohnson (Thu, 16 May 2019 00:34:34 GMT):
We moved to a new image on May 10 (added GO 1.12.5)
tijohnson (Thu, 16 May 2019 00:36:17 GMT):
@rickr wait... What is the build you are seeing this problem in? How about a link to the log
rickr (Thu, 16 May 2019 00:37:34 GMT):
https://gerrit.hyperledger.org/r/#/c/31386/
rickr (Thu, 16 May 2019 00:39:16 GMT):
I was told a JIRA was opened on it... doesn't that fall in your lap? :)
rickr (Thu, 16 May 2019 00:43:02 GMT):
By the way another issue if you look at that link is I tried a `reverify-1.4` that should have kicked off a new 1.4 build. Which it either does and does not show up in gerrit or never did actually kick in!
tijohnson (Thu, 16 May 2019 00:44:26 GMT):
The fabric-sdk-java build are 'special' they required python 3.6 which is in a new image (not same as it used by other builds
sambhavdutt (Thu, 16 May 2019 00:44:33 GMT):
@rickr
I am working on that comment trigger for the verify jobs, as of now it is `reverify`
rickr (Thu, 16 May 2019 00:45:31 GMT):
so can't retrigger just a 1.4 build?
sambhavdutt (Thu, 16 May 2019 00:46:26 GMT):
after my CR is merged, you can trigger the master job with `reverify-x` and 1.4 with `reverify-1.4` respectively
sambhavdutt (Thu, 16 May 2019 00:46:37 GMT):
not now
rickr (Thu, 16 May 2019 00:47:00 GMT):
can I get a `justworkdamit`
tijohnson (Thu, 16 May 2019 00:47:30 GMT):
I can realate
tijohnson (Thu, 16 May 2019 00:55:11 GMT):
'comment triggers' are a real problem, they are broken ... primarily a resource issue
rickr (Thu, 16 May 2019 00:56:14 GMT):
and the really shouldn't be even necessary :wink:
tijohnson (Thu, 16 May 2019 00:56:32 GMT):
yea right...
tijohnson (Thu, 16 May 2019 00:58:31 GMT):
I am running fabric-sdk-java-master-verify-x86_64 on sandbox... plus sent a 'retry' to the review
rickr (Thu, 16 May 2019 00:58:39 GMT):
well I got to break away ..
tijohnson (Thu, 16 May 2019 00:58:50 GMT):
it trigger the build, but it failed
rickr (Thu, 16 May 2019 00:58:54 GMT):
what
tijohnson (Thu, 16 May 2019 00:59:03 GMT):
I do to (my dinner time)
rickr (Thu, 16 May 2019 01:00:27 GMT):
what's odd is it seems to fail almost always on the 1.4 build and master works. But that difference is Fabric not the SDK. On both those builds its the JSDK 2.0 (master) that's being built
sambhavdutt (Thu, 16 May 2019 01:10:58 GMT):
@tijohnson
I have updated CR to modify the triggers for each job https://gerrit.hyperledger.org/r/#/c/31392/
sambhavdutt (Thu, 16 May 2019 01:10:58 GMT):
@tijohnson
I have updated CR to modify the triggers for sdk-java verify jobs https://gerrit.hyperledger.org/r/#/c/31392/
rickr (Thu, 16 May 2019 12:08:25 GMT):
Changed https://jira.hyperledger.org/browse/IN-67
to priority highest. Really blocking and Java SDK updates.
rickr (Thu, 16 May 2019 12:08:25 GMT):
Changed https://jira.hyperledger.org/browse/IN-67
to priority highest. Really blocking any Java SDK updates.
sambhavdutt (Thu, 16 May 2019 14:47:24 GMT):
@rickr
The job has passed now for 1.4 too, https://gerrit.hyperledger.org/r/#/c/31386/
rickr (Thu, 16 May 2019 15:04:33 GMT):
but why, please?
rickr (Thu, 16 May 2019 15:05:18 GMT):
Was something changed? We can't do 2 days of reverify to get it passing.
sambhavdutt (Thu, 16 May 2019 15:09:03 GMT):
there were no changes made in the code to fix this error, just the comments were added, Tim is looking into the nodes, if there needs to be some cleanup done, if some clutter was left behind in the nodes, that might be the answer
rickr (Fri, 17 May 2019 14:36:35 GMT):
Same errors continue to happen https://gerrit.hyperledger.org/r/#/c/31415/
sambhavdutt (Fri, 17 May 2019 14:45:07 GMT):
@rickr
sadly yes, we had faced a similar issue on sdk-java jobs before, I have related that ticket to the existing Bug for this issue for informationhttps://jira.hyperledger.org/browse/IN-67
sambhavdutt (Fri, 17 May 2019 14:45:07 GMT):
@rickr
sadly yes, we had faced a similar issue on sdk-java jobs before, I have related that ticket to the existing Bug for this issue for information https://jira.hyperledger.org/browse/IN-67
sambhavdutt (Fri, 17 May 2019 14:45:07 GMT):
@rickr
sadly yes, we had faced a similar issue on sdk-java jobs before, I have related that ticket to the existing Bug for information https://jira.hyperledger.org/browse/IN-67
rickr (Fri, 17 May 2019 15:11:01 GMT):
@tijohnson fyi after 5 attempts https://gerrit.hyperledger.org/r/#/c/31415/
tijohnson (Fri, 17 May 2019 17:42:54 GMT):
@rickr I was looking into this this morning and I am having problems understanding what it is you expect me to do
rickr (Fri, 17 May 2019 17:45:07 GMT):
Fix the issue with the environment doing the builds producing unreliable result, would be a good start
rickr (Fri, 17 May 2019 17:47:36 GMT):
This only seems to be happening in that environment. No one else is reporting it. Takes 5 build attempts to not see a corrupted file message that's a prereq that needs to be there.
tijohnson (Fri, 17 May 2019 17:56:35 GMT):
What is it that your build needs in the environment that we need to provide?
rickr (Fri, 17 May 2019 17:57:29 GMT):
The Java JDK
tijohnson (Fri, 17 May 2019 17:57:42 GMT):
this is stupid to be talking about this in chat, we need to meet
rickr (Fri, 17 May 2019 17:58:09 GMT):
why does this not work ?
rickr (Fri, 17 May 2019 17:58:25 GMT):
What have you tried ... please list
tijohnson (Fri, 17 May 2019 17:58:53 GMT):
I do not really have anything to do with the Java SDK, I click a button in Jenkins and it installs it
tijohnson (Fri, 17 May 2019 17:59:27 GMT):
I can select different versions but that is about it
rickr (Fri, 17 May 2019 18:03:38 GMT):
So have you looked into if it's the latest version?
Have tried googling for that error to see if anyone else has seen It ?
Have you updated template for the latest Ubuntu fixes?
Have looked at all at the pattern of what vms are failing and once are passing?
If you retrigger on that successufl vm is it always successful? and the vms that don't always fail
Is there a ways to change out those vms ?
Have you tried upping memory ?
tijohnson (Fri, 17 May 2019 18:12:26 GMT):
I do not know enough about your build to begin proposing possible solutions
tijohnson (Fri, 17 May 2019 18:18:32 GMT):
You seem to want to just though this problem over the wall, we need to work together to work toward a solution
rickr (Fri, 17 May 2019 20:48:40 GMT):
I've recommending some things you could have already been looking at. That's throwing over that wall?
rickr (Fri, 17 May 2019 20:48:40 GMT):
I've recommending some things you could have already been looking at. That's throwing over the wall?
BrettLogan (Fri, 17 May 2019 23:00:20 GMT):
Let's start with, it isn't a Fabric or Fabric Java SD issue, it's a Maven and Open Java JDK issue. The problem originates in Fabric code, but the failure is in the Maven compilation of core JDK libraries imported by our SDK. Maven compilation errors due to corrupt zip files aren't uncommon on systems that aren't running well. And history tells us, our nodes are over utilized. Running tests in our current CI takes 5x as long as running on commodity hardware (proven by benchmarks I've run as recently as today). I can force replicate this problem in an IBM Data center where I overutilize the machine, with Jenkins installed and limit bandwidth on the network connection. We need to figure out why our vexx nodes are so slow, despite having 4 times more resources than comparable machines that compile with no problems. Tim, let's talk about this on Tuesday, I'd like to discuss our current cloud infrastructure and see if we can't get answers from whoever we need to identify why our CI nodes are so incridbly so. I have a few questions I'd like help getting answered. Rick, I know it sucks, but we have to keep doing the reverify until we can figure out why the slave nodes are so overutilized. I'd like to do some real benchmarking activity next week on network and CPU
maniankara (Sat, 18 May 2019 13:13:26 GMT):
Has joined the channel.
maniankara (Sat, 18 May 2019 13:13:35 GMT):
Hello guys, does anyone know why nexus repository publishes only fabric-ca-client but not fabric-ca-server binary? E.g. from here: https://nexus.hyperledger.org/content/repositories/releases/org/hyperledger/fabric-ca/hyperledger-fabric-ca/darwin-amd64-1.4.1/
risc (Mon, 20 May 2019 01:59:17 GMT):
Has joined the channel.
sambhavdutt (Mon, 20 May 2019 16:56:24 GMT):
@maniankara
`fabric-ca-client` is published on official release dates to Nexus, because they expect people to use the `fabric-ca` image that is published in releases, not just the `fabric-ca-server` binary
sambhavdutt (Mon, 20 May 2019 17:59:41 GMT):
The comment triggers have been updated for fabric-merge jobs
`remerge` will trigger both merge jobs as usual,
`remerge-x` will just trigger the unit-test job
`remerge-e2e` will just trigger the fabric-end-2-end job
tijohnson (Tue, 21 May 2019 23:36:54 GMT):
@BrettLogan (your comment from May 17) this is exactly the kind of stuff we should be have covered in the meeting today
By the way the pathway off of VEX requires projects move to a image created with a new process (common-packer)
as of today ci-management & fabric-sdk-java are the only two projects using an image generated by common-packer
tijohnson (Tue, 21 May 2019 23:39:40 GMT):
Just added GATEWAY_JAVA_PASSWORD to sandbox so it should be available on both prod & sandbox
BhumitSheth (Thu, 23 May 2019 20:07:50 GMT):
Has joined the channel.
rjones (Fri, 24 May 2019 19:48:36 GMT):
Has joined the channel.
yacovm (Sat, 25 May 2019 11:43:24 GMT):
my change set isn't building.... https://gerrit.hyperledger.org/r/#/c/fabric/+/31549/ can anyone please help?
BrettLogan (Sat, 25 May 2019 11:51:26 GMT):
@yacovm I'm looking at it. For some reason i cant log into Gerrit, can you reply with just `VerifyBuild` to rule out a bad regular expression
sambhavdutt (Sat, 25 May 2019 11:59:29 GMT):
@yacovm
The jobs waiting to be triggered as the x nodes are offline, I will create a Hyperledger helpdesk ticket to LF team
yacovm (Sat, 25 May 2019 11:59:43 GMT):
ok thanks
BrettLogan (Sat, 25 May 2019 12:00:04 GMT):
Thanks @sambhavdutt
sambhavdutt (Sat, 25 May 2019 12:03:51 GMT):
no probs,
Helpdesk ticket has been assigned to LF team for this
*[Hyperledger Helpdesk #76031] *
sambhavdutt (Sun, 26 May 2019 13:12:11 GMT):
@tijohnson @jwagantall
Can the above ticket be assigned to someone, the hyperledger/fabric builds are still waiting
sambhavdutt (Sun, 26 May 2019 13:12:11 GMT):
@tijohnson @jwagantall
Can the above ticket be assigned to someone, the hyperledger/fabric builds are still waiting as the x nodes are offline
sambhavdutt (Mon, 27 May 2019 13:02:13 GMT):
Screen Shot 2019-05-27 at 8.59.20 AM.png
sambhavdutt (Mon, 27 May 2019 13:02:19 GMT):
For your information regarding build status
rjones (Tue, 28 May 2019 14:48:14 GMT):
It looks like builds are happening now
sambhavdutt (Tue, 28 May 2019 14:54:05 GMT):
yes
sambhavdutt (Tue, 28 May 2019 14:54:23 GMT):
thank you
tatsu-sato (Thu, 30 May 2019 01:13:56 GMT):
Has joined the channel.
tatsu-sato (Thu, 30 May 2019 01:14:14 GMT):
Hello, I have a question.
I noticed when I read the document on CI Process of fabric-samples (`docs/fabric-samples-ci.md`).
The document says the CI job sends build failure email notifications to the submitter on every merge failure.
But it seems that the job does not send an e-mail to the submitter as far as I see recent failure logs
(log message: An attempt to send an e-mail to empty list of recipients, ignored).
Does it match the specification and/or expectation ?
vijay.bP (Thu, 30 May 2019 01:21:26 GMT):
@tatsu-sato I saw the console for last three build failure's, it's sending the mails inconsistent and not respective to the CR owner, thanks for the info, i will check and make correction on this.
nekia (Thu, 30 May 2019 02:01:27 GMT):
Hi, I have a question about Hyperledger Jobbuilder runtime environment. In merge job, I have 500 error when executing curl. The exact same task is working fine on **verify** job now. Is there any difference between these 2 runtime environments? In this task, I download Hyperledger Fabric binaries of a specific version for our e2e test.
#### Verify Job
> 00:06:57.940 > hyperledger-explorer@0.3.9 e2e-test-setup-tool:ci /w/workspace/blockchain-explorer-verify-x86_64
> 00:06:57.940 > /bin/bash -c 'mkdir fabric-samples; pushd fabric-samples; curl -sSL https://raw.githubusercontent.com/hyperledger/fabric-samples/release-1.4/scripts/bootstrap.sh | bash -s; popd'
> 00:06:57.940
> 00:06:57.940 /w/workspace/blockchain-explorer-verify-x86_64/fabric-samples /w/workspace/blockchain-explorer-verify-x86_64
> 00:06:57.940
> 00:06:57.940 Installing Hyperledger Fabric binaries
https://jenkins.hyperledger.org/job/blockchain-explorer-verify-x86_64/192/console
#### Merge Job
> 00:08:38.155 > hyperledger-explorer@0.3.9 e2e-test-setup-tool:ci /w/workspace/blockchain-explorer-merge-x86_64
> 00:08:38.155 > /bin/bash -c 'mkdir fabric-samples; pushd fabric-samples; curl -sSL https://raw.githubusercontent.com/hyperledger/fabric-samples/release-1.4/scripts/bootstrap.sh | bash -s; popd'
> 00:08:38.155
> 00:08:38.155 /w/workspace/blockchain-explorer-merge-x86_64/fabric-samples /w/workspace/blockchain-explorer-merge-x86_64
> 00:08:53.046 bash: line 1: 500:: command not found
https://jenkins.hyperledger.org/job/blockchain-explorer-merge-x86_64/108/console
BrettLogan (Thu, 30 May 2019 02:55:11 GMT):
@nekia It's not the curl command that is failing, the job downloads and pipes the script into bash. It is actually failing on this command `/bin/bash -c 'if [[ -z $(which configtxgen) ]]; then echo "### Need to install tools ###"; exit -1; fi'`
BrettLogan (Thu, 30 May 2019 02:55:35 GMT):
Very likely just a flake
BrettLogan (Thu, 30 May 2019 02:55:35 GMT):
Very likely a flake
BrettLogan (Thu, 30 May 2019 03:01:21 GMT):
We will look at it in the morning and figure out what happened
nekia (Thu, 30 May 2019 03:07:26 GMT):
Ok. thanks.
nekia (Thu, 30 May 2019 03:09:13 GMT):
Yes correct, test was asserted due to missing required tools.
vijay.bP (Thu, 30 May 2019 14:10:14 GMT):
@nekia The merge build for the CR https://gerrit.hyperledger.org/r/#/c/blockchain-explorer/+/31588/ was successful, the above error is a flake.
tatsu-sato (Thu, 30 May 2019 20:19:32 GMT):
OK. Thanks.
nekia (Sat, 01 Jun 2019 13:42:47 GMT):
Thanks. I understood that it's a little bit non-deterministic.
rickr (Fri, 07 Jun 2019 19:43:39 GMT):
any reason gerrit draft work flow has be disabled ?
rickr (Fri, 07 Jun 2019 19:44:30 GMT):
```
! [remote rejected] HEAD -> refs/drafts/master (draft workflow is disabled)
```
rjones (Fri, 07 Jun 2019 19:45:05 GMT):
maybe it has to be explicitly enabled in the new version of Gerrit? @tijohnson ?
rickr (Fri, 07 Jun 2019 19:47:12 GMT):
I have found it handy if any chance it could be reenabled much appreciated
BrettLogan (Sat, 08 Jun 2019 07:41:47 GMT):
Drafts have been removed as of 2.15 unfortunately. It has been totally replaced by the WIP system. If you push a WIP and don't want others to see it, you can use the UI to mark the WIP private now.
BrettLogan (Sat, 08 Jun 2019 07:43:28 GMT):
https://gerrit-documentation.storage.googleapis.com/Documentation/2.15/intro-user.html#private-changes
BrettLogan (Sat, 08 Jun 2019 07:44:05 GMT):
You can also specify on push now to send the WIP directly to private
BrettLogan (Sat, 08 Jun 2019 07:44:14 GMT):
https://gerrit-documentation.storage.googleapis.com/Documentation/2.15/intro-user.html#wip
BrettLogan (Sat, 08 Jun 2019 07:44:23 GMT):
And here is the doc on the new WIP branch
jtonline (Mon, 10 Jun 2019 14:40:13 GMT):
Hi, just looking at the fabric Java projects and wondering which maven repositories snapshots should be getting published to. There seem to be some in https://nexus.hyperledger.org/content/repositories/snapshots/ and some in https://oss.sonatype.org/content/repositories/snapshots/ (It would be nice to have source jars for all the projects as well)
tommyjay (Mon, 10 Jun 2019 20:56:31 GMT):
Hey there, I’m having an issue with verify builds on fabric-sdk-go using the s390x machine. The x86_64 works fine and I’ve issued reverify but the problem is that jenkins isn’t able to remove child images from the very beginning. I think it's caching these images.
My change request has nothing to do with docker: https://jenkins.hyperledger.org/job/fabric-sdk-go-verify-s390x/216/console
I just pushed a dummy change and it failed for the same reason:
- jenkins s390x build: https://jenkins.hyperledger.org/job/fabric-sdk-go-verify-s390x/217/console
- gerrit code: https://gerrit.hyperledger.org/r/c/fabric-sdk-go/+/31813
I think there might be an issue with the `removeUnwantedImages` function in the configs: https://jenkins.hyperledger.org/job/fabric-sdk-go-verify-s390x/configure
rjones (Mon, 10 Jun 2019 20:57:15 GMT):
@rameshthoomu ^
rameshthoomu (Mon, 10 Jun 2019 21:01:07 GMT):
@tommyjay I manually deleted all these images from the s390x build node and restarted the build. For now no issue. Could you please create JIRA ticket, will ask some one to look into this.
tommyjay (Mon, 10 Jun 2019 21:07:38 GMT):
thanks @rameshthoomu
tommyjay (Mon, 10 Jun 2019 21:14:19 GMT):
@rameshthoomu @rjones here's the ticket: https://jira.hyperledger.org/browse/FABCI-373
rameshthoomu (Mon, 10 Jun 2019 21:15:43 GMT):
Assigned. @vijay.bP Could you please look into this ticket when you get some time
BrettLogan (Tue, 11 Jun 2019 00:04:08 GMT):
That is an unfortunate flake, you can replicate it on your local machine if you call `make docker` from the fabric repo (or any repo that builds docker images) and cancel the build at the exact moment the docker build process is moving form one step to the next, this is probably why we very, very rarely see this issue. We can theoretically extend `include-raw-fabric-clean-environment.sh` to catch that error to deal with this problem, we would then have to individually capture the dangling images and individually remove them. But this could get cyclical as dangling images may depend on each other, and guaranteeing we delete all of them could possibly put us in an infinite loop if we don't properly identify every dangling image. The root cause was probably another build being aborted in the middle of its docker build process, which can happen, if you update a CR, the previous build is aborted.
vijay.bP (Tue, 11 Jun 2019 15:59:17 GMT):
@tommyjay The child images has been deleted from the 390x node which is always picking up on the build, so we can get clear info when it tries to run on different minion.
MHBauer (Tue, 11 Jun 2019 22:23:28 GMT):
why does sometimes the code review checkboxes not get picked up? https://gerrit.hyperledger.org/r/#/c/fabric/+/31841/
MHBauer (Tue, 11 Jun 2019 22:23:38 GMT):
is there a ticket?
MHBauer (Tue, 11 Jun 2019 22:23:48 GMT):
and how do I recover?
rjones (Tue, 11 Jun 2019 22:29:16 GMT):
@MHBauer b/c the votes happened on an old patch
rjones (Tue, 11 Jun 2019 22:29:34 GMT):
a new patch came in while builds were in progress, so the votes don't carry forward
rjones (Tue, 11 Jun 2019 22:30:30 GMT):
I added a reverify comment, which should kick it off again
MHBauer (Tue, 11 Jun 2019 22:41:45 GMT):
:-(
MHBauer (Tue, 11 Jun 2019 22:41:51 GMT):
thanks.
rjones (Tue, 11 Jun 2019 22:53:23 GMT):
yeah, there's a window between when a job fires, when it votes, and a new patch can come in and not trigger a new build
tommyjay (Wed, 12 Jun 2019 14:04:57 GMT):
@vijay.bP thanks
nekia (Fri, 14 Jun 2019 05:50:55 GMT):
Hi, I'd like to run e2e test using headless google chrome for explorer project on Hyperledger Jobbuilder.
nekia (Fri, 14 Jun 2019 05:52:16 GMT):
But installation fails : [error log](https://jenkins.hyperledger.org/job/blockchain-explorer-verify-x86_64/205/console)
```
00:13:39.146 sudo: unable to resolve host prd-ubuntu1604-x86-64-4c-16g-3590
00:13:39.146 sudo: no tty present and no askpass program specified
```
nekia (Fri, 14 Jun 2019 05:52:16 GMT):
But installation of chrome is failed : [error log](https://jenkins.hyperledger.org/job/blockchain-explorer-verify-x86_64/205/console)
```
00:13:39.146 sudo: unable to resolve host prd-ubuntu1604-x86-64-4c-16g-3590
00:13:39.146 sudo: no tty present and no askpass program specified
```
Is there any solutions for this issue?
mbwhite (Fri, 14 Jun 2019 09:53:40 GMT):
Hello; Picking up the work to build the java chaincode on zOS... I've access to a Z-Linux host that I can develop on but would like to get the actual build in travis etc.
Not sure if this was previously enabled or not; who'd be best person to talk to/raise an issue with?
rjones (Fri, 14 Jun 2019 12:55:46 GMT):
@rameshthoomu
mbwhite (Fri, 14 Jun 2019 13:21:22 GMT):
Thanks. IF needed the jira is https://jira.hyperledger.org/browse/FAB-15496
vijay.bP (Fri, 14 Jun 2019 13:28:11 GMT):
@mbwhite So, you are looking for the verify and merge jobs for Z platform on 2.0 and 1.4 branch, and from the merge job do we need to publish javaenv image.
mbwhite (Fri, 14 Jun 2019 13:28:44 GMT):
yes - I don't know if this had been setup previously and then turned off,, or if it's new..
mbwhite (Fri, 14 Jun 2019 13:29:13 GMT):
Looking at this from the dev side, taken over from Gennady
vijay.bP (Fri, 14 Jun 2019 13:30:19 GMT):
In current CI, i don't see Z jobs.
vijay.bP (Fri, 14 Jun 2019 13:30:19 GMT):
In current CI, i don't see Z jobs diabled.
vijay.bP (Fri, 14 Jun 2019 13:30:35 GMT):
I have to create new
mbwhite (Fri, 14 Jun 2019 13:31:36 GMT):
fair enough.. I wasn't sure; when do you think you might be able to complete this?
vijay.bP (Fri, 14 Jun 2019 13:32:19 GMT):
So, javaenv-s390x image going to be publish in release as well.
mbwhite (Fri, 14 Jun 2019 13:32:39 GMT):
yes
vijay.bP (Fri, 14 Jun 2019 13:33:23 GMT):
By EOD they will be ready.
mbwhite (Fri, 14 Jun 2019 13:34:27 GMT):
ah :-)
mbwhite (Fri, 14 Jun 2019 13:34:36 GMT):
brilliant! Let'
mbwhite (Fri, 14 Jun 2019 13:34:48 GMT):
let's hope my build scripts work then :-)
vijay.bP (Fri, 14 Jun 2019 18:19:09 GMT):
@mbwhite Updated the status for the JIRA https://jira.hyperledger.org/browse/FAB-15496.
nekia (Mon, 17 Jun 2019 04:15:10 GMT):
Resolved. I gave up to use 'sudo' on Hyperledger Jobbuilder. Instead, Using Selenium Docker gave me a solution to this issue. I don't need to setup a browser(dpkg -i) and JRE(apt-get install) manually any more. Thanks @vijay.bP
mbwhite (Thu, 27 Jun 2019 09:19:11 GMT):
Any idea why this might not be merging??
https://gerrit.hyperledger.org/r/#/c/fabric-chaincode-java/+/31953/
mbwhite (Thu, 27 Jun 2019 13:29:03 GMT):
It's ls
vijay.bP (Fri, 28 Jun 2019 14:12:21 GMT):
@dave.enyeart Please check this issue https://jira.hyperledger.org/browse/FAB-15831, blocking publish images to nexus builds.
rameshthoomu (Fri, 28 Jun 2019 14:49:33 GMT):
bumped the priority and added blocked label
rjones (Fri, 28 Jun 2019 18:48:59 GMT):
@sykesm @BrettLogan @vijay.bP Please add @tijohnson as a code reviewer when you are pushing code to the `ci-m` repo. It looks like https://gerrit.hyperledger.org/r/c/ci-management/+/32090 was merged without review from LF.
rjones (Fri, 28 Jun 2019 18:49:05 GMT):
thanks.
wlahti (Tue, 02 Jul 2019 17:13:11 GMT):
Does anybody know how to update the binaries pulled by `fabric-samples` in CI? We recently renamed a peer CLI command. I have a CR to address this in `fabric-samples` but the error text when it fails shows that the peer binary that's being used is an older version.
wlahti (Tue, 02 Jul 2019 17:13:11 GMT):
Does anybody know how to update the binaries pulled by `fabric-samples` in CI? We recently renamed a peer CLI command. I have a CR to address this in `fabric-samples` but the error text when it fails shows that the peer binary that's being used is an older version (i.e. it has the previous name of the command instead of the new name)
wlahti (Tue, 02 Jul 2019 17:52:32 GMT):
I have a fix in gerrit, but of course it can't build and verify because it only wants to grab "stable" fabric images. :sweat_smile:
vijay.bP (Tue, 02 Jul 2019 17:58:48 GMT):
@wlahti If you want to change the VERSION to pull binaries,we can do it from https://github.com/hyperledger/fabric-samples/blob/master/ci.properties.
dkushagra (Wed, 03 Jul 2019 08:59:04 GMT):
Has joined the channel.
rameshthoomu (Wed, 03 Jul 2019 13:32:03 GMT):
@wlahti This should fixed by now.. I see the nightly job was successful after disabling byfn tests. Could you please re-trigger your CR. Note: Changing the version of binary to old version is not possible in CI.
rameshthoomu (Wed, 03 Jul 2019 13:32:03 GMT):
@wlahti This should be fixed by now. I see the nightly job was successful after disabling byfn tests. Could you please re-trigger your CR. Note: Changing the version of binary to old version is not possible in CI.
wlahti (Wed, 03 Jul 2019 13:34:17 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=bzobNSKMeBBA69RWP) @rameshthoomu Yep, already triggered the reverify earlier. Thanks for the heads up though!
nekia (Fri, 05 Jul 2019 04:29:55 GMT):
Hi, I usually use 'reverify' phrase to retrigger a verification when it fails with a flake or timeout. But sometimes, [in a certain change on gerrit|https://gerrit.hyperledger.org/r/c/fabric/+/31973], it doesn't work. Is there any conditions for a verification to be triggered successfully
nekia (Fri, 05 Jul 2019 04:29:55 GMT):
Hi, I usually use 'reverify' phrase to retrigger a verification when it fails with a flake or timeout. But sometimes, [in a certain change on gerrit](https://gerrit.hyperledger.org/r/c/fabric/+/31973), it doesn't work. Is there any conditions for a verification to be triggered successfully
nekia (Fri, 05 Jul 2019 04:29:55 GMT):
Hi, I usually use 'reverify' phrase to retrigger a verification when it fails with a flake or timeout. But sometimes, [in a certain change on gerrit](https://gerrit.hyperledger.org/r/c/fabric/+/31973), it doesn't work. Is there any conditions for a verification to be triggered successfully?
nekia (Fri, 05 Jul 2019 04:29:55 GMT):
Hi, I usually use 'reverify' phrase to retrigger a verification when it fails with a flake or timeout. But sometimes, [in a certain change on gerrit](https://gerrit.hyperledger.org/r/c/fabric/+/31973), it doesn't work. Is there any conditions for a verification to be triggered successfully? Thanks
rameshthoomu (Fri, 05 Jul 2019 13:02:51 GMT):
@vijay.bP ^^
vijay.bP (Fri, 05 Jul 2019 13:18:30 GMT):
@nekia Please refer this doc to rebuild the job through gerrit comments https://ci-docs.readthedocs.io/en/latest/source/fabric_ci_process.html#trigger-failed-jobs-through-gerrit-comments search with this `Trigger failed jobs through Gerrit comments`
rameshthoomu (Fri, 05 Jul 2019 13:42:16 GMT):
@nekia which project you are referring? We have different "gerrit comment phrases" for each project.
rameshthoomu (Fri, 05 Jul 2019 13:50:27 GMT):
If you are referring fabric, please refer the link which Vijay shared otherwise, you can use "reverify" for most of the projects. ex: for blockchain-explorer, you can use reverify
nekia (Fri, 05 Jul 2019 14:38:20 GMT):
Thank you! 'VerifyBuild' worked on fabric. @vijay.bP @rameshthoomu
mastersingh24 (Sun, 07 Jul 2019 10:21:06 GMT):
If anyone is around, https://gerrit.hyperledger.org/r/32188 could use a look
vijay.bP (Mon, 08 Jul 2019 13:07:51 GMT):
@tijohnson Please look into this CR https://gerrit.hyperledger.org/r/32188
tijohnson (Mon, 08 Jul 2019 13:25:57 GMT):
I commented on it yesterday
vijay.bP (Mon, 08 Jul 2019 19:57:56 GMT):
@bretharrison Could you please update the `tag` for the fabric-client npm module from `2.0.0-snapshot.250` to `2.0.0-snapshot.251` manually on `https://www.npmjs.com/package/fabric-client` since the fabric-sdk-node-merge-x86_64 is failing with the error `You cannot publish over the previously published versions: 2.0.0-snapshot.251. : fabric-client`
vijay.bP (Tue, 09 Jul 2019 13:59:16 GMT):
@mbwhite Could you please look into this https://jira.hyperledger.org/browse/FAB-15844, this bug is consistent and blocking to publish nodeenv image to nexus.
vijay.bP (Wed, 10 Jul 2019 13:44:46 GMT):
@bretharrison @mbwhite Could anyone please look into this https://jira.hyperledger.org/browse/FAB-15844, this bug is consistent and blocking to publish nodeenv image to nexus, since nodeenv-s390x image is not available on nexus it's blocking number of builds on CI.
bretharrison (Wed, 10 Jul 2019 16:35:45 GMT):
I had to publish a 2.0.0-snapshot.252
rjones (Wed, 10 Jul 2019 16:35:56 GMT):
@tijohnson what is the plan with https://gerrit.hyperledger.org/r/c/ci-management/+/32188 ? are you porting fabric's CI stuff to `common-packer`?
rjones (Wed, 10 Jul 2019 16:36:01 GMT):
the email wasn't clear
vijay.bP (Wed, 10 Jul 2019 16:47:01 GMT):
2.0.0-snapshot.251 is not available on npm registry, you have to publish 251 only for fabric-client
bretharrison (Wed, 10 Jul 2019 16:47:42 GMT):
I was not able to publish, had to publish a 252
tijohnson (Wed, 10 Jul 2019 16:52:32 GMT):
@rjones The only image that will install golang 1.12.7 is the docker image (created by common-packer) It will not be available in the baseline image that is currently being used for fabric-* builds
I will assist in moving the fabric builds to the docker image I expect some problems with the image that I will address as we find them
I will begin by trying to build fabric-chaincode-* & fabric-sdk-* verify builds
I would like to coordinate this activity with someone from fabric development My understanding is the move to golang 1.12.7 is in 'master'?
vijay.bP (Wed, 10 Jul 2019 16:52:56 GMT):
Ok go with 252.
rjones (Wed, 10 Jul 2019 19:54:25 GMT):
@BrettLogan @sykesm @mastersingh24 ^^^ @tijohnson is trying to find someone to assist in some rejiggering and understanding of the fabric CI process
BrettLogan (Wed, 10 Jul 2019 23:25:20 GMT):
@tijohnson Can we coordinate tomorrow morning, i just landed on my return trip from Moscow. I will be in office tomorrow
tijohnson (Thu, 11 Jul 2019 00:42:51 GMT):
@BrettLogan sure I should be on-line 9:30-10:30 and then from noon on (EST)
mastersingh24 (Thu, 11 Jul 2019 12:50:40 GMT):
I'm around most of today ... technically still out on vacation but I'm at home now
tijohnson (Thu, 11 Jul 2019 16:50:51 GMT):
@here we need to upgrade JIRA to latest version. The downtime will be 14:00 EST today and it will be back up within 15 mins
invaliduser (Sat, 13 Jul 2019 13:28:31 GMT):
Has joined the channel.
vijay.bP (Mon, 15 Jul 2019 01:52:09 GMT):
@tijohnson @rjones @jwagantall Could anyone please add `- fabric-nodeenv-x86_64
- fabric-nodeenv-s390x
` on jenkins view as these jobs were created and CR was merged https://gerrit.hyperledger.org/r/#/c/ci-management/+/32286/ and also please trigger only fabric-nodeenv-s390x job now.
dhuseby (Mon, 15 Jul 2019 15:32:02 GMT):
@tijohnson thanks for the heads up
maniankara (Tue, 16 Jul 2019 10:01:59 GMT):
Has left the channel.
vijay.bP (Tue, 16 Jul 2019 13:56:24 GMT):
@dave.enyeart @wlahti Please check this https://jira.hyperledger.org/browse/FAB-15973 `Simulate commit chaincode definition result on peer0.org1 is INVALID` failing consistently on merge end-2-end testing builds.
wlahti (Tue, 16 Jul 2019 14:24:45 GMT):
Ah yes, we had another breaking change merged into fabric master recently. I'll need to address that for fabric-samples.
wlahti (Tue, 16 Jul 2019 19:02:17 GMT):
https://gerrit.hyperledger.org/r/c/fabric-samples/+/32353 is ready for review/merge
wlahti (Tue, 16 Jul 2019 19:02:17 GMT):
https://gerrit.hyperledger.org/r/c/fabric-samples/+/32353 to fix the above is ready for review/merge
ravinayag (Wed, 17 Jul 2019 14:28:45 GMT):
Has joined the channel.
vijay.bP (Thu, 18 Jul 2019 13:39:14 GMT):
@rjones @tijohnson Problem occurred to access JIRA ```Sorry, a communication error occurred while trying to contact the remote authentication server.```
vijay.bP (Thu, 18 Jul 2019 13:39:14 GMT):
@jwagantall @rjones @tijohnson Problem occurred to access JIRA ```Sorry, a communication error occurred while trying to contact the remote authentication server.```
vijay.bP (Thu, 18 Jul 2019 13:54:29 GMT):
It's JIRA is online now.
vijay.bP (Thu, 18 Jul 2019 13:54:29 GMT):
The JIRA is online now.
vijay.bP (Thu, 18 Jul 2019 14:34:26 GMT):
@bretharrison Please look in to this bug on node-sdk test fail on fabric end2end testing intermittently https://jira.hyperledger.org/browse/FABN-1316
heatherp (Mon, 29 Jul 2019 10:30:16 GMT):
Has joined the channel.
heatherp (Mon, 29 Jul 2019 10:32:37 GMT):
I’d like to get my team (programming model squad in Hursley) access to publish JARs under the group id `org.hyperleder.fabric` but don't have write permission to https://nexus.hyperledger.org/content/repositories/snapshots/org/hyperledger/fabric/. Currently there are separate groupids. This is published when the merge builds run for Java SDK, Java Gateway and Java Shim. Can anyone help me out please?
heatherp (Mon, 29 Jul 2019 10:32:37 GMT):
I’d like to get my team (programming model squad in Hursley) access to publish JARs under the group id `org.hyperleder.fabric` but don't have write permission to https://nexus.hyperledger.org/content/repositories/snapshots/org/hyperledger/fabric/. Currently there are separate groupids. This is published when the merge builds run for Java SDK, Java Gateway and Java Shim. Can anyone help me out please?
Related JIRA is: https://jira.hyperledger.org/browse/FGJ-30
vijay.bP (Mon, 29 Jul 2019 14:14:06 GMT):
@heatherp Let me check on the nexus for the path where the gateway-java jars are publishing, and we don't have writing privileges for nexus LF do, I am assigning the FGJ-30 to me.
heatherp (Mon, 29 Jul 2019 14:14:54 GMT):
thanks!
vijay.bP (Mon, 29 Jul 2019 15:05:49 GMT):
@heatherp The group id for fabric-gateway-java is https://github.com/hyperledger/fabric-gateway-java/blob/44d0ebd143dbbbbf0b949902c6986f4756ab3c59/pom.xml#L8 and the jar's are publishing to right path https://nexus.hyperledger.org/content/repositories/snapshots/org/hyperledger/fabric-gateway-java/ the above link you provided is for fabric not gateway-java.
mbwhite (Mon, 29 Jul 2019 15:07:23 GMT):
Hi Vijay - the point is that we don't think that the groupid for either the gateway or contract java is correct...
mbwhite (Mon, 29 Jul 2019 15:07:55 GMT):
i.e. we'd like to have a group id of `org.hyperledger.fabric` and assets within that for gateway, protos, java-shim etc...
mbwhite (Mon, 29 Jul 2019 15:08:22 GMT):
we don't think that today we're able to publish those as we can't write the `org.hyperledger.fabric` directory
vijay.bP (Mon, 29 Jul 2019 15:19:11 GMT):
@mbwhite I think that's not possible while downloading the artifacts jenkins use the metadata.xml file for the directory, which should be independent for the projects fabric, gateway-java, cc-java.
mbwhite (Mon, 29 Jul 2019 15:21:47 GMT):
so it's not possible to share the same groupid across all the artifacts?
vijay.bP (Mon, 29 Jul 2019 15:22:31 GMT):
NO, matt.
mbwhite (Mon, 29 Jul 2019 15:23:10 GMT):
ok.. not sure I follow why though..
vijay.bP (Mon, 29 Jul 2019 15:24:12 GMT):
As of now let's go, i will try on this later, thanks.
mbwhite (Mon, 29 Jul 2019 15:24:23 GMT):
sure...
vijay.bP (Mon, 29 Jul 2019 18:45:40 GMT):
@andrew-coleman @bestbeforetoday Could you please look into this JIRA item https://jira.hyperledger.org/browse/FABJ-462 causing consistent failure on java-sdk tests on fabric-merge-end-2-end builds.
vijay.bP (Tue, 30 Jul 2019 18:10:15 GMT):
@mbwhite Please review and merge this CR https://gerrit.hyperledger.org/r/#/c/fabric-chaincode-java/+/32582/
bestbeforetoday (Wed, 31 Jul 2019 08:51:56 GMT):
@dave.enyeart Thanks for the heads-up on the change that caused the breakage
bestbeforetoday (Wed, 31 Jul 2019 08:52:40 GMT):
Is there a mechanism for people to communicate to me when they are going to make changes that will break the SDK?
bestbeforetoday (Wed, 31 Jul 2019 08:52:58 GMT):
Ideally before the breaking change is made! :)
sykesm (Wed, 31 Jul 2019 19:33:10 GMT):
FAB-16149 was merged into master and seems to have exposed failures.
sstone1 (Thu, 01 Aug 2019 07:05:07 GMT):
@sykesm me again, thanks for taking a look. any idea how it got past CI before merge?
sykesm (Thu, 01 Aug 2019 14:38:02 GMT):
The details are in the revert. When you added parallel processing for endorsers, you made the order of the responses non-deterministic. That impacted assumptions in the test. Depending on timing, it would work or fail.
sykesm (Thu, 01 Aug 2019 14:39:43 GMT):
I'm changing the test to provide consistent responses and I need to chat with @wlahti when he's back from vacation about the intent and behavior of the test.
sstone1 (Thu, 01 Aug 2019 14:42:16 GMT):
makes sense - i couldn't reproduce it when running all the tests, only when running the test using the command you provided
sstone1 (Thu, 01 Aug 2019 14:43:14 GMT):
i didn't understand the test either - it looks like the CLI code will never attempt to order transactions with a 500 status, even if they have valid endorsements
jtonline (Mon, 05 Aug 2019 10:41:20 GMT):
Hi, is this the right place to request that zLinux builds be removed from fabric-chaincode-node? I assume it wouldn't be a good idea to just remove the Jenkinsfile.z file from the repo? Thanks. https://jira.hyperledger.org/browse/FAB-16196
mastersingh24 (Mon, 05 Aug 2019 11:43:36 GMT):
@tijohnson - you mentioned in a comment to my PR to add Go 1.12.7 that it had already been added? How do I take advantage of this?
caod (Mon, 05 Aug 2019 14:32:18 GMT):
Has joined the channel.
tijohnson (Mon, 05 Aug 2019 15:53:37 GMT):
@mastersingh24 You would have run the job on a docker image (hyp-x-docker). What repo/job(s) are you referring to ?
The steps to make this change depends on whether the job is a pipeline or freestyle job
mastersingh24 (Mon, 05 Aug 2019 15:53:57 GMT):
fabric
tijohnson (Mon, 05 Aug 2019 15:54:45 GMT):
I was hoping you would not ask for that one...
mastersingh24 (Mon, 05 Aug 2019 15:55:02 GMT):
I know ;)
tijohnson (Mon, 05 Aug 2019 15:55:52 GMT):
Those jobs are mostly (all pipeline) jobs, which means the cloud image to use is specified in the Jenkinsfile
tijohnson (Mon, 05 Aug 2019 15:56:18 GMT):
when it is set is Jenkinsfile it applies to ALL fabric jobs
mastersingh24 (Mon, 05 Aug 2019 15:56:30 GMT):
yep
tijohnson (Mon, 05 Aug 2019 15:58:19 GMT):
you could have your own version of Jenkinsfile to develop/verify but you can't push that until rest of fabric is ready for new image
tijohnson (Mon, 05 Aug 2019 16:01:01 GMT):
I suspect most jenkins jobs will be OK unchanged on docker image, but I expect to have a few issues
mastersingh24 (Mon, 05 Aug 2019 16:01:50 GMT):
some of our jobs launch containers
mastersingh24 (Mon, 05 Aug 2019 16:02:23 GMT):
I assume the hyp-x-docker jobs use containers as the workers ... so that won't work
tijohnson (Mon, 05 Aug 2019 16:03:34 GMT):
it is same as hyp-x image, the big difference is the image a created using Ansible rather than a shell script
mastersingh24 (Mon, 05 Aug 2019 16:04:04 GMT):
ok .. ok ... so worker is still a VM with Docker daemon?
tijohnson (Mon, 05 Aug 2019 16:04:49 GMT):
I have already ported fabrci-sdk-go & fabric-sdk-java & fabric-chaincode-java
tijohnson (Mon, 05 Aug 2019 16:05:42 GMT):
yes works same as old image
tijohnson (Mon, 05 Aug 2019 16:06:26 GMT):
most of my work has been because MVN is not longing installed in the image, some jobs expect it to be there
tijohnson (Mon, 05 Aug 2019 16:06:26 GMT):
most of my work has been because MVN is no longer installed in the image, some jobs expect it to be there
tijohnson (Mon, 05 Aug 2019 16:09:32 GMT):
the image is named 'docker' because it support docker, if you don't need docker you don't want to use it. I also have a hyp-x-builder image that does not contain docker
tijohnson (Mon, 05 Aug 2019 16:09:32 GMT):
the image is named 'hyp-x-docker' because it supports docker, if you don't need docker you don't need to use it.
I have a 'hyp-x-builder' image that does not contain docker
shitaibin (Tue, 06 Aug 2019 08:08:11 GMT):
Has joined the channel.
tijohnson (Tue, 06 Aug 2019 14:12:56 GMT):
@mastersingh24 I figured out a way fabric port pipeline jobs in a way that us to do them in smaller groups rather than fabric*
tijohnson (Tue, 06 Aug 2019 14:12:56 GMT):
@mastersingh24 I figured out a way fabric port pipeline jobs in a way that would allow us to do them in smaller groups rather than fabric*
mastersingh24 (Tue, 06 Aug 2019 14:20:21 GMT):
do tell
tijohnson (Tue, 06 Aug 2019 14:22:36 GMT):
We can specify a different config file: 'Jenkinsfile-docker' for some jobs you would have to maintain two identical versions (except the node entry) of this file for awhile
tijohnson (Tue, 06 Aug 2019 14:28:05 GMT):
@mastersingh24 You can pick which jobs I do first, so you can move forward with moving to GO 1.12.7 on those jobs
sykesm (Wed, 07 Aug 2019 18:42:18 GMT):
@tijohnson can explain what actions are necessary to bump the go version in the fabric builds now? You've performed some actions that mean our existing processes and knowledge no longer apply yet we still have the requirement to build with the new version of go.
sykesm (Wed, 07 Aug 2019 18:42:18 GMT):
@tijohnson can you explain what actions are necessary to bump the go version in the fabric builds now? You've performed some actions that mean our existing processes and knowledge no longer apply yet we still have the requirement to build with the new version of go.
tijohnson (Wed, 07 Aug 2019 20:40:28 GMT):
@sykes The new version of GO 1.12.7 is available in the hyp-x-docker image. For freestyle builds this setting is job specific, but for pipeline jobs the entire project needs to be moved at once.
tijohnson (Wed, 07 Aug 2019 20:40:28 GMT):
@sykesm The new version of GO 1.12.7 is available in the hyp-x-docker image. For freestyle builds this setting is job specific, but for pipeline jobs the entire project needs to be moved at once.
tijohnson (Wed, 07 Aug 2019 20:40:28 GMT):
@sykesm The new version of GO 1.12.7 is available in the hyp-x-docker image. For freestyle builds this setting is typically job specific,
but for pipeline jobs the entire project needs to be moved at once.
tijohnson (Wed, 07 Aug 2019 20:42:31 GMT):
What project are you asking about ?
sykesm (Wed, 07 Aug 2019 21:15:22 GMT):
fabric - the core
tijohnson (Wed, 07 Aug 2019 21:20:16 GMT):
Any pipeline jobs based on the fabric repo use the image specified in the Jenkinsfile in fabric repo, I betting that effects about 100 jobs....
tijohnson (Wed, 07 Aug 2019 21:20:16 GMT):
@sykesm Any pipeline jobs based on the fabric repo use the image specified in the Jenkinsfile in fabric repo, I betting that effects about 100 jobs....
tijohnson (Wed, 07 Aug 2019 21:21:37 GMT):
we could make that change and if 10 jobs break we fix them, if 90 jobs break we back out the change
sykesm (Wed, 07 Aug 2019 21:21:46 GMT):
I thought that fabric was freestyle - most of the ancillary stuff is pipeline but not core fabric. (that's my understanding..)
sykesm (Wed, 07 Aug 2019 21:22:05 GMT):
there is no Jenkinsfile in fabric
BrettLogan (Wed, 07 Aug 2019 21:23:24 GMT):
What is different about the x-docker image and the one we use now in how Go is managed within the image? Are the x-docker images assuming we use the Go Plugin?
tijohnson (Wed, 07 Aug 2019 21:24:16 GMT):
The docker image installs 1.12.7 the hyp-x (baseline) only installs 1.12.5
tijohnson (Wed, 07 Aug 2019 21:28:20 GMT):
what might help me is for me to prioritize the jobs/projects that I am porting to docker image and then get some help testing the merge/release jobs that would be affected by the change
tijohnson (Wed, 07 Aug 2019 21:36:55 GMT):
more accurately the docker image installs 1.12.5 & 1.12.7
mastersingh24 (Thu, 08 Aug 2019 06:11:57 GMT):
fabric (https://github.com/hyperledger/ci-management/blob/master/jjb/fabric/fabric-jobs.yaml)
fabric-verify-build-checks-{arch}
fabric-verify-unit-tests-{arch}
fabric-verify-integration-tests-{arch}
would be a good start ....
also any fabric jobs with
```
properties:
- 'fabric-go-{arch}'
```
mastersingh24 (Thu, 08 Aug 2019 06:11:57 GMT):
@tijohnson
fabric (https://github.com/hyperledger/ci-management/blob/master/jjb/fabric/fabric-jobs.yaml)
fabric-verify-build-checks-{arch}
fabric-verify-unit-tests-{arch}
fabric-verify-integration-tests-{arch}
would be a good start ....
also any fabric jobs with
```
properties:
- 'fabric-go-{arch}'
```
mastersingh24 (Thu, 08 Aug 2019 06:12:53 GMT):
@sykesm ^^^
tijohnson (Thu, 08 Aug 2019 13:58:35 GMT):
@mastersingh24 Thanks, I will focus on these jobs next, Turns out I started on fabric-verify-build-checks last night
mastersingh24 (Thu, 08 Aug 2019 13:58:50 GMT):
cool ... thx
paranjan (Thu, 08 Aug 2019 15:13:47 GMT):
Has joined the channel.
vijay.bP (Thu, 08 Aug 2019 15:46:38 GMT):
@mbwhite Why this is still using old version 1.4.0 in cc-node tests https://github.com/hyperledger/fabric-chaincode-node/blob/11a3a27e68bfaf3d37817e7e140474562353590a/package.json#L5.
jtonline (Thu, 08 Aug 2019 16:22:19 GMT):
Does anyone know how to get more information out of a failing build? I can't figure out why https://gerrit.hyperledger.org/r/c/fabric-chaincode-java/+/32607 is failing. The method it seems to be complaining about exists and although the related files were changed recently, other builds are working, e.g https://gerrit.hyperledger.org/r/c/fabric-chaincode-java/+/32798 even though they weren't changed in the failing build. Any suggestions appreciated as I'm very confused at the moment.
BrettLogan (Thu, 08 Aug 2019 17:03:56 GMT):
@jtonline Taking a look at it now
vijay.bP (Thu, 08 Aug 2019 17:20:50 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=QtuTMHi6ChFPFciPE)
vijay.bP - Thu Aug 08 2019 13:20:37 GMT-0400 (Eastern Daylight Time).txt
vijay.bP (Thu, 08 Aug 2019 17:24:21 GMT):
`Matthew B White` is the right person to triage this IT failures on javafor the
vijay.bP (Thu, 08 Aug 2019 17:24:21 GMT):
`Matthew B White` is the right person to triage this IT failures on java
BrettLogan (Thu, 08 Aug 2019 18:22:14 GMT):
This isn't CI related, I pulled your changeset and the exact same issues exist when I run the tests locally
heatherp (Fri, 09 Aug 2019 08:03:37 GMT):
Matthew is on holiday until the 19th
heatherp (Fri, 09 Aug 2019 08:14:15 GMT):
Could someone take a look at https://gerrit.hyperledger.org/r/c/ci-management/+/32794 please? I think some changes I made to fabric-chaincode-java broke the way the root build.gradle is parsed, and I'm hoping that CR fixes it.
BrettLogan (Fri, 09 Aug 2019 09:22:22 GMT):
@heatherp when i get into the office i first have to push the job to sandbox to make sure its buildable
BrettLogan (Fri, 09 Aug 2019 09:22:37 GMT):
But ill look at it then
heatherp (Fri, 09 Aug 2019 09:22:53 GMT):
thanks!
BrettLogan (Fri, 09 Aug 2019 09:37:35 GMT):
@heatherp Neveermind It's one of those jobs we can't test as sandbox doesn't have access to any creds, so it fails very early. So I've gone ahead and merged it
BrettLogan (Fri, 09 Aug 2019 09:42:33 GMT):
@tijohnson Java jobs are failing with the new hyp-x image due to something related with python. https://jenkins.hyperledger.org/view/ci-management/job/ci-management-tox-verify-master/3254/console
BrettLogan (Fri, 09 Aug 2019 09:42:33 GMT):
@tijohnson Java jobs are failing with the new hyp-x image due to something related with python.https://jenkins.hyperledger.org/view/ci-management/job/ci-management-tox-verify-master/3254/console
jtonline (Fri, 09 Aug 2019 09:48:02 GMT):
Thanks @BrettLogan, that's definitely useful. I've not ever managed to get the integration tests to run on my machine for some reason- I'll see if setting up a Linux VM helps but if you know of any gotchas, that would be great. Would you be able to zip up the logs from your local build and send them over later if I don't get anywhere? Thanks again
BrettLogan (Fri, 09 Aug 2019 10:02:47 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=DPn6PE3oLg5fH6Mhn) @jtonline of course. Ill send you the logs once I get to the office. There was a lot more info in them with the stacktraces
jtonline (Fri, 09 Aug 2019 10:24:48 GMT):
The VM worked. Problem seems to be
```
java.lang.NoSuchMethodError: org.hyperledger.fabric.protos.peer.Chaincode$ChaincodeDeploymentSpec$Builder.setExecEnv(Lorg/hyperledger/fabric/protos/peer/Chaincode$ChaincodeDeploymentSpec$ExecutionEnvironment;)Lorg/hyperledger/fabric/protos/peer/Chaincode$ChaincodeDeploymentSpec$Builder;
at org.hyperledger.fabric.sdk.transaction.ProtoUtils.createDeploymentSpec(ProtoUtils.java:178)
at org.hyperledger.fabric.sdk.transaction.InstallProposalBuilder.createNetModeTransaction(InstallProposalBuilder.java:269)
at org.hyperledger.fabric.sdk.transaction.InstallProposalBuilder.constructInstallProposal(InstallProposalBuilder.java:109)
at org.hyperledger.fabric.sdk.transaction.InstallProposalBuilder.build(InstallProposalBuilder.java:101)
at org.hyperledger.fabric.sdk.Channel.sendInstallProposal(Channel.java:2581)
at org.hyperledger.fabric.sdk.HFClient.sendInstallProposal(HFClient.java:666)
at org.hyperleder.fabric.shim.integration.Utils.sendInstallProposals(Utils.java:345)
at org.hyperleder.fabric.shim.integration.FirstNetworkIntegrationTest.TestNoBuildChaincodeInstallInstantiateWithSrc(FirstNetworkIntegrationTest.java:87)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
at org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.lang.Thread.run(Thread.java:748)
```
jtonline (Fri, 09 Aug 2019 12:44:52 GMT):
Hmmm, that all exists in the CR _but_ this looks suspicious https://github.com/jt-nti/fabric-chaincode-java/blob/master/fabric-chaincode-docker/Dockerfile#L57
jtonline (Fri, 09 Aug 2019 12:46:49 GMT):
Do I need a new chaincode release with the updated protos in, _then_ update and release the Dockerfile, _then_ get this CR in?!
BrettLogan (Fri, 09 Aug 2019 12:53:28 GMT):
1.4 protos already exists in Nexus, wouldn't you expect this to at least be on those at this point?
jtonline (Fri, 09 Aug 2019 13:04:10 GMT):
Hmmm, I think the required protobuf change is in the 1.4.3 release so could use that, but the mismatching versions seem troubling.
BrettLogan (Fri, 09 Aug 2019 13:04:46 GMT):
Yea, so your workflow seems correct. Update protos, dockerfile, then your CR
jtonline (Fri, 09 Aug 2019 13:07:46 GMT):
Unfortunately the Dockerfile seems to have the same outdated files in on the 1.4 branch, and the same CR there built ok on that, so I'm not convinced this is definitely the cuase https://github.com/jt-nti/fabric-chaincode-java/blob/release-1.4/fabric-chaincode-docker/Dockerfile#L50
jtonline (Fri, 09 Aug 2019 13:08:27 GMT):
Is there anything else that might be causing it, or is it worth trying an updated Dockerfile?
BrettLogan (Fri, 09 Aug 2019 13:09:17 GMT):
I just tried building everything myself, that didn't fix the issue
jtonline (Fri, 09 Aug 2019 13:11:38 GMT):
:(
jtonline (Fri, 09 Aug 2019 13:41:14 GMT):
Ahhhh, I think it might be the SDK missing the proto updates! `testCompile 'org.hyperledger.fabric-sdk-java:fabric-sdk-java:1.4.1'`
jtonline (Fri, 09 Aug 2019 13:43:18 GMT):
Maybe not- that's the same in 1.4 chaincode as well
jtonline (Fri, 09 Aug 2019 13:48:00 GMT):
...but the tests are different in 1.4 so maybe...
jtonline (Fri, 09 Aug 2019 14:09:39 GMT):
Woot, it built! Thanks for putting up with the ramblings- that was driving me slightly crazy! Just need to fix the test now...
```
org.hyperleder.fabric.shim.integration.FirstNetworkIntegrationTest > classMethod FAILED
java.lang.AssertionError at FirstNetworkIntegrationTest.java:50
1 test completed, 1 failed
```
BrettLogan (Fri, 09 Aug 2019 14:10:22 GMT):
No issue. That's what we are here for, trying to find the least common denominator
jtonline (Fri, 09 Aug 2019 14:55:57 GMT):
Bother. Changing the sdk version didn't fix the build even though it worked on my VM. Setting up a fresh VM to see if the first run on a clean system behaves differently :shrug:
jtonline (Fri, 09 Aug 2019 15:18:54 GMT):
It does indeed fail on a clean system :cry:
tijohnson (Fri, 09 Aug 2019 15:23:50 GMT):
@BrettLogan I successfully ran ci-management-tox-verify-master on sandbox & production
jtonline (Fri, 09 Aug 2019 15:27:43 GMT):
Gah, and it builds on the second run! Had nothing to do with changing the SDK version!
jtonline (Fri, 09 Aug 2019 15:28:09 GMT):
Will take another look next week :scream:
paranjan (Fri, 09 Aug 2019 15:58:44 GMT):
Has left the channel.
jtonline (Fri, 09 Aug 2019 16:30:17 GMT):
(It may have run out of space on the second run and concealed the build error. Will double check next week.)
jtonline (Mon, 12 Aug 2019 10:21:18 GMT):
Confirmed, it was running out of space so upgrading the sdk was a small scarlet fish :(
vijay.bP (Tue, 13 Aug 2019 14:51:00 GMT):
@jtonline Please look into this bug https://jira.hyperledger.org/browse/FAB-16299, java-chaincode merge job fail.
jtonline (Tue, 13 Aug 2019 15:03:17 GMT):
Turned out that the test was incorrectly mixing sdk and chaincode classes which didn't previously cause problems. (But now does! Fixed.)
jtonline (Tue, 13 Aug 2019 15:41:17 GMT):
https://gerrit.hyperledger.org/r/c/fabric-chaincode-java/+/32883 <- Heather and Mathew are away, so it needs someone to review it
huxd (Wed, 14 Aug 2019 01:07:06 GMT):
Has joined the channel.
jtonline (Wed, 14 Aug 2019 10:08:15 GMT):
Should be done on all releases now
vijay.bP (Wed, 14 Aug 2019 11:01:51 GMT):
Yes please and also 'gsed' command was not setup, so the builds fails with the above error on bug.
jtonline (Wed, 14 Aug 2019 13:21:49 GMT):
https://gerrit.hyperledger.org/r/c/ci-management/+/32925
jtonline (Wed, 14 Aug 2019 13:23:07 GMT):
Hopefully the build machines have the `head` command anyway :)
vijay.bP (Wed, 14 Aug 2019 13:24:59 GMT):
Yes, it does and works.
jtonline (Wed, 14 Aug 2019 13:41:03 GMT):
Hooray!
jtonline (Wed, 14 Aug 2019 13:41:58 GMT):
Who can merge CRs in that repo?
vijay.bP (Wed, 14 Aug 2019 13:42:18 GMT):
Already added them as reviewers.
jtonline (Wed, 14 Aug 2019 13:46:13 GMT):
Great, thanks
jtonline (Thu, 15 Aug 2019 16:09:36 GMT):
Hi, I've had a go at updating the script which publishes javadoc for fabric-chaincode-java https://gerrit.hyperledger.org/r/c/ci-management/+/32946 I'm not sure how I can check it really works since I don't have access to the repo it publishes to but could someone have an early look to see if there are any glaring errors please? It would be great to get it properly reviewed and merged sometime next week when the matching changes are ready in other repos (if it works, it'll break some links at the moment :)
vijay.bP (Thu, 15 Aug 2019 16:23:37 GMT):
@bestbeforetoday @andrew-coleman Please look into this bug https://jira.hyperledger.org/browse/FABJ-469 it's a blocker on fabric-merge builds.
BrettLogan (Thu, 15 Aug 2019 19:33:02 GMT):
FYI: Fabric Unit Tests are broken for a couple hours. We migrated to a new cloud image today built using a new process to support newer versions of Golang. There was a minor bug in it, that wasnt caught in our sandbox CI system. We are building the new image now and will have the change in within the next couple hours
sykesm (Fri, 16 Aug 2019 12:56:08 GMT):
Looks like we may have issues with release 1.x builds no as well - `go` is longer found when trying to run verification checks
sykesm (Fri, 16 Aug 2019 12:56:15 GMT):
@BrettLogan ^
BrettLogan (Fri, 16 Aug 2019 12:59:54 GMT):
@sykesm acknowledged
JiTian0225 (Sat, 17 Aug 2019 08:27:29 GMT):
Has joined the channel.
BrettLogan (Mon, 19 Aug 2019 22:10:12 GMT):
We are going to do a quick restart of Jenkins to address issues in Pipeline jobs, jobs will continue to queue and start automatically after the jenkins restart
BrettLogan (Mon, 19 Aug 2019 22:53:35 GMT):
Jenkins is restarted. Jobs that have some downstream dependency on the AnsiColor wrapper, whether through your own jenkinsfile, or via the LFIT Global Macros will fail until we can address an issue in the plugin. We are working to resolve this
BrettLogan (Tue, 20 Aug 2019 00:23:01 GMT):
We've disabled the AnsiColor wrapper in the Global Macros, which almost all pipelines depend on. I'll reach out to projects affected by this in the morning. If there are projects that want to address it before then, I've published several changes for our projects, you can merge them as you see fit https://gerrit.hyperledger.org/r/q/owner:brett.t.logan%2540ibm.com
galaxystar (Tue, 20 Aug 2019 01:21:34 GMT):
Has joined the channel.
jtonline (Thu, 22 Aug 2019 15:29:33 GMT):
Does that explain why fabric-chaincode-java builds are failing? (I've seen a selection of different failures, including test failures, timeouts and what look like network issues, so I'm not sure.)
BrettLogan (Thu, 22 Aug 2019 15:36:32 GMT):
@jtonline Unfortunately no, this only affects projects that have a Jenkinsfile in the root of them (are pipeline-based, not freestyle). However we have noted the issues related to time and network(jars from Maven cetnral not being able to be downloaded). This is just fodder for the fact that the new CI system can't come soon enough
jtonline (Thu, 22 Aug 2019 15:50:13 GMT):
Ok, that was my suspicion but it seemed worse than usual so I thought I'd check. Thanks
jtonline (Fri, 23 Aug 2019 14:37:51 GMT):
Hooray, that Java build finally passed! Which means this ci-management CR is ready for review if anyone can take a look and try it out https://gerrit.hyperledger.org/r/c/ci-management/+/32946 Thanks
BrettLogan (Fri, 23 Aug 2019 14:48:22 GMT):
Yup. I'll get to it today
jtonline (Fri, 23 Aug 2019 14:50:19 GMT):
Great, thanks very much. I'm out next week so if there are any problems, I nominate @mbwhite to fix it :)
mbwhite (Fri, 23 Aug 2019 14:51:05 GMT):
:-)
BrettLogan (Fri, 23 Aug 2019 15:08:56 GMT):
Merged
swetha (Tue, 27 Aug 2019 00:32:12 GMT):
Hello! I work on the fabric-chaincode-evm. The current fabric-chaincode-evm job seems to have had changes. It is failing after trying to check out the new commit: https://jenkins.hyperledger.org/job/fabric-chaincode-evm-verify-x86_64/434/console. Any ideas what has happened?
rameshthoomu (Tue, 27 Aug 2019 00:41:44 GMT):
@swetha it's failing because of the ansicolor plugin issue.. We have to disable ansicolor lines from the jenkinsfile.. @BrettLogan did you push change to remove this from fabric-chaincode-evm project.
swetha (Tue, 27 Aug 2019 00:43:49 GMT):
Okay, anything we need to push from the fabric-chaincode-evm side?
rameshthoomu (Tue, 27 Aug 2019 00:43:56 GMT):
yes
rameshthoomu (Tue, 27 Aug 2019 00:44:23 GMT):
submitting change now
rameshthoomu (Tue, 27 Aug 2019 00:46:22 GMT):
https://gerrit.hyperledger.org/r/#/c/fabric-chaincode-evm/+/33197/
swetha (Tue, 27 Aug 2019 00:53:28 GMT):
thanks! as soon as build passes once should be merged
BrettLogan (Tue, 27 Aug 2019 01:02:04 GMT):
You'll need to rebase on that change to pick up the Jenkinsfile
soumyanayak (Wed, 28 Aug 2019 14:48:10 GMT):
Has joined the channel.
yacovm (Wed, 28 Aug 2019 21:57:04 GMT):
Why isn't https://gerrit.hyperledger.org/r/#/c/fabric/+/33255/ rebuilding? :(
yacovm (Wed, 28 Aug 2019 21:57:26 GMT):
What is the latest incantation ? Is it no longer `Run UnitTest` ?
BrettLogan (Wed, 28 Aug 2019 22:05:23 GMT):
It is @yacovm something is wrong with our cloud provider. Jobs are tacking 10x as long to run, so the queue is building up
BrettLogan (Wed, 28 Aug 2019 22:05:23 GMT):
It is @yacovm something is wrong with our cloud provider. Jobs are taxing 10x as long to run, so the queue is building up
BrettLogan (Wed, 28 Aug 2019 22:05:47 GMT):
We have 55 executors and all are in use due to the severely decreased performance
BrettLogan (Wed, 28 Aug 2019 22:05:53 GMT):
We are investigating
BrettLogan (Wed, 28 Aug 2019 22:16:07 GMT):
FYI: Jenkins is currently experiencing severe performance issues, there is currently a backlog of jobs queued. Replying to your Gerrit changes to rerun builds that are already queued will only exacerbate the issue. We are investigating and working on resolution
BrettLogan (Wed, 28 Aug 2019 22:17:58 GMT):
Something is wrong with Jenkins (as usual), we are working on it
BrettLogan (Wed, 28 Aug 2019 22:18:11 GMT):
FYI: Jenkins is currently experiencing severe performance issues, there is currently a backlog of jobs queued. Replying to your Gerrit changes to rerun builds that are already queued will only exacerbate the issue. We are investigating and working on resolution
BrettLogan (Thu, 29 Aug 2019 02:10:20 GMT):
Performance remains a little degraded in Jenkin's however builds are processing again and the queue is cleared
BrettLogan (Thu, 29 Aug 2019 02:10:20 GMT):
Performance remains a little degraded in Jenkin's however builds are processing again and the queue is cleared. Thank you for your patience.
vijay.bP (Fri, 30 Aug 2019 17:30:44 GMT):
@mbwhite @jtonline @bretharrison Please check this bug on cc-node, headless test fail to get protos from fabric, which is recently moved to new repo `fabric-protos` verify and merge builds fail until this was fixed.
vijay.bP (Fri, 30 Aug 2019 17:31:22 GMT):
https://jira.hyperledger.org/browse/FAB-16380
rjones (Mon, 02 Sep 2019 03:45:45 GMT):
@BrettLogan please take a look at the failures here - most seem to be due to ansi wrapper. https://gerrit.hyperledger.org/r/#/q/status:open+%22FAB-16489%22
BrettLogan (Mon, 02 Sep 2019 04:54:15 GMT):
@rjones Ill submit patchsets tomorrow to fix these when i get back to Raleigh. A couple if these repos we just put off doing it since they hadnt been touched in months. Our hope was we would fix the ANSI wrapper, but something is broken in core jenkins, so we removed the plugin since the only way to fix this is to do a full backup, reinstallation and restoration of jenkins.
BrettLogan (Mon, 02 Sep 2019 23:03:42 GMT):
Working on it now R
BrettLogan (Mon, 02 Sep 2019 23:03:42 GMT):
Working on it now Ry
rjones (Mon, 02 Sep 2019 23:31:24 GMT):
oh it's a holiday, wait until Tuesday ;)
BrettLogan (Tue, 03 Sep 2019 00:38:06 GMT):
Ry, I disabled the global Ansi wrapper in the CI-management repo. Tim merged that change just now, so Ansi-Color is no more for now. I reverified all of your changes so we could rule out Ansi issues and actual flakes. I also commented on 2 of your changes with patchsets you need to rebase on as Blockchain Explorer and Fab-Lib-Go had Ansi-Color enabled in the repo-level Jenkinsfiles so you can pick up the new Jenkinsfiles where I disabled those wrappers.
BrettLogan (Tue, 03 Sep 2019 00:38:06 GMT):
Ry, I disabled the global Ansi wrapper in the CI-management repo. Tim merged that change just now, so Ansi-Color is no more for now. I reverified all of your changes so we could rule out Ansi issues and actual flakes. I also commented on 2 of your changes with patchsets you need to rebase on as Blockchain Explorer and Fab-Lib-Go had Ansi-Color enabled in the repo-level Jenkinsfiles so you can pick up the new Jenkinsfiles where I disabled those wrapperes.
BrettLogan (Tue, 03 Sep 2019 00:39:09 GMT):
I asked the Blockchain Explorer devs to review the change and merge it in their Rocket Chat channel as it's been outstanding for a little while now
BrettLogan (Tue, 03 Sep 2019 00:39:09 GMT):
I asked the Blockchain Explorer guys to review the change and merge it in their Rocket Chat channel as it's been outstanding for a little while now
BrettLogan (Tue, 03 Sep 2019 00:39:56 GMT):
I'll revisit in the morning to check for flakes
BrettLogan (Tue, 03 Sep 2019 00:41:05 GMT):
https://gerrit.hyperledger.org/r/c/blockchain-explorer/+/33301 you can also rebase this on the same change to fix the issue here
rjones (Tue, 03 Sep 2019 01:18:06 GMT):
in progress - thanks
sstone1 (Thu, 05 Sep 2019 08:38:50 GMT):
@BrettLogan @vijay.bP we've merged https://gerrit.hyperledger.org/r/c/fabric-chaincode-node/+/33182, looks like https://gerrit.hyperledger.org/r/c/ci-management/+/33341 needs an update?
vijay.bP (Thu, 05 Sep 2019 12:49:13 GMT):
@sstone1 Thanks, we are checking on that.
BrettLogan (Thu, 05 Sep 2019 18:51:50 GMT):
@sstone1 We've queued up the fix, should be merged in the next hour or two, waiting for another maintainer to merge
sstone1 (Fri, 06 Sep 2019 07:37:48 GMT):
@BrettLogan thanks Brett, looks good to me this morning - finally getting green builds again!
dave.enyeart (Sat, 07 Sep 2019 15:43:27 GMT):
Here's some high level thoughts on the CI and SCM transition...
dave.enyeart (Sat, 07 Sep 2019 15:43:40 GMT):
Steps per project (start with fabric-ca to discover any issues)
1. pre-merge verify jobs on Azure (using github mirror at first)
2. gerrit to github transition (change github to read/write, turn on PR process)
3. have jenkins do post-merge jobs against github (temporarily)
Can still do releases from jenkins at this point
4. Use gitlab (or Azure) for post-merge jobs
dave.enyeart (Sat, 07 Sep 2019 15:44:11 GMT):
@BrettLogan please keep me honest, does that accurately reflect what we discussed?
BrettLogan (Sat, 07 Sep 2019 15:50:14 GMT):
Correct. The above is the plan I'm working to put together. I am working on a public backlog in Jira to support this. The thought process to only putting verify jobs on AZP or Gitalab for now, is that it will allow us to get our repos on GitHub, which is a major milestone and quicker than if we needed to rebuild all of our post merge jobs which have more complex requirements.
BrettLogan (Sat, 07 Sep 2019 15:50:14 GMT):
Correct. The above is the plan I'm working to put together. I am working on a public backlog in Jira to support this plan. The thought process to only putting verify jobs on AZP or Gitalab for now, is that it will allow us to get our repos on GitHub, which is a major milestone and quicker than if we needed to rebuild all of our post merge jobs which have more complex requirements.
BrettLogan (Sat, 07 Sep 2019 15:52:09 GMT):
Leaving post merge jobs also allows to migrate repos before 2.0 release, otherwise we would be holding off for 2 months in an effort to not threaten the 2.0 release process
rjones (Sat, 07 Sep 2019 16:18:39 GMT):
I'm thinking very low traffic stuff here, like the homebrew-fabric repo for instance: https://gerrit.hyperledger.org/r/admin/repos/q/filter:fab AMCL hasn't had a code merge in a year, test-resources since 2017
rjones (Sat, 07 Sep 2019 16:19:01 GMT):
Anything without any CI implications.
rjones (Sat, 07 Sep 2019 16:20:11 GMT):
fabric-docs
rjones (Sat, 07 Sep 2019 16:20:59 GMT):
The obvious question: why am I bringing this up in a CI/CD channel? Because I want to test to process of breaking the mirror, marking the repos read-only in Gerrit, and making sure nothing Bad Happens.
rjones (Sat, 07 Sep 2019 16:23:08 GMT):
fabric-chaintool hasn't had a meaningful code update since 2019
rjones (Sat, 07 Sep 2019 16:23:08 GMT):
fabric-chaintool hasn't had a meaningful code update since 2018
rjones (Sat, 07 Sep 2019 16:33:26 GMT):
https://jira.hyperledger.org/browse/FAB-16531
davidkel (Sun, 08 Sep 2019 08:00:25 GMT):
Has joined the channel.
BrettLogan (Sun, 08 Sep 2019 19:24:39 GMT):
Hey Ry, I took a look at these repos last night, I agree, let me just run it by maintainers tomorrow morning to be sure they are okay with it and we can work through it this week. We want to migrate Fabric-CA asap, so going through these repos to define any issues will be great
BrettLogan (Sun, 08 Sep 2019 19:27:25 GMT):
I didn't realize most of these repos even existed. After moving them to Git, I'd like to inventory them and figure out what we are doing with them and deprecate where need be. Homebrew hasn't been update for the 1.4 stream, milagro crypto (which is what AMCL is a "clone" of) doesn't even have a public repo anymore for us to pull updates from, fabric docs never ended up serving the purpose it was intended to (though Joe and the WG may want to revisit it)
BrettLogan (Sun, 08 Sep 2019 19:27:25 GMT):
I didn't realize most of these repos even existed. After moving them to Git, I'd like to inventory them and figure out what we are doing with them and deprecate where need be. Homebrew hasn't been update for the 1.4 stream, milagro crypto doesn't even have a public repo anymore for us to pull updates from, fabric docs never ended up serving the purpose it was intended to (though Joe and the WG may want to revisit it)
rjones (Sun, 08 Sep 2019 20:34:22 GMT):
if you cruise through Gerrit, there are a few more questionable repos. I'd be fine if they ended up tombstoned, archived, and forgotten
ping40 (Mon, 09 Sep 2019 01:06:47 GMT):
Has left the channel.
mastersingh24 (Tue, 10 Sep 2019 12:42:44 GMT):
`milagro crypto` - there's been no need to update this yet so I have not pointed it at the Apache repos where it now resides ... we do still need the repo
mastersingh24 (Tue, 10 Sep 2019 12:43:11 GMT):
I think I have a task open for that ...
mastersingh24 (Tue, 10 Sep 2019 12:43:11 GMT):
I have a task open for that: https://jira.hyperledger.org/browse/FAB-14693
rjones (Tue, 10 Sep 2019 16:09:45 GMT):
@mastersingh24 could I ask you to merge https://gerrit.hyperledger.org/r/c/homebrew-fabric/+/33317 so we could start the migration to GitHub?
sstone1 (Wed, 11 Sep 2019 10:04:38 GMT):
please could someone merge this ci-management change? https://gerrit.hyperledger.org/r/c/ci-management/+/33447
bjzhang03 (Mon, 16 Sep 2019 06:33:51 GMT):
Has joined the channel.
bjzhang03 (Mon, 16 Sep 2019 06:33:51 GMT):
when I run the jenkins,it always tell me that Error response from daemon: manifest for nexus3.hyperledger.org:10001/hyperledger/fabric-javaenv:amd64-1.4.3-stable not found
bjzhang03 (Mon, 16 Sep 2019 06:34:08 GMT):
can somebody solve this roblem ?
BrettLogan (Mon, 16 Sep 2019 08:43:37 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=J6ZWCczw3LaHtRwHq) @bjzhang03
BrettLogan (Mon, 16 Sep 2019 08:43:44 GMT):
We are working on it
BrettLogan (Mon, 16 Sep 2019 08:44:45 GMT):
@bjzhang03 https://jira.hyperledger.org/browse/FAB-16608?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel
BrettLogan (Mon, 16 Sep 2019 08:44:56 GMT):
We are working on it
bjzhang03 (Mon, 16 Sep 2019 08:45:34 GMT):
thanks
bjzhang03 (Mon, 16 Sep 2019 08:45:58 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=7abc71c0-75d8-45b2-9074-49036a63bf34) thanks
bjzhang03 (Mon, 16 Sep 2019 08:46:11 GMT):
[ ](https://chat.hyperledger.org/channel/fabric-ci?msg=dcb31914-4881-407b-8682-df78f31e88c5) thanks
rjones (Mon, 16 Sep 2019 13:01:07 GMT):
@BrettLogan get some sleep lol
rjones (Mon, 16 Sep 2019 13:19:35 GMT):
@BrettLogan I've invited IT to join us here for the move
BrettLogan (Mon, 16 Sep 2019 13:21:01 GMT):
Perfect. I believe they intend to cut the mirror in 40 minutes. I am almost to the office, running a little behind this morning
rjones (Mon, 16 Sep 2019 13:25:30 GMT):
I saw you have two in-flight changes WRT CI - do you care if they die on the vine?
BrettLogan (Mon, 16 Sep 2019 13:27:38 GMT):
Still hoping I can get a merge from Matt this morning. If they don't make it before the cut, we will just pick them up in GitHub
vijay.bP (Mon, 16 Sep 2019 13:42:18 GMT):
@rjones Jira.hyp is down opened an support ticket `SUPPORT-512`.
rjones (Mon, 16 Sep 2019 13:43:32 GMT):
Works for me? I also have no power to help on those tickets
rjones (Mon, 16 Sep 2019 13:44:43 GMT):
@vijay.bP
vijay.bP (Mon, 16 Sep 2019 13:45:15 GMT):
yes, may be problem with my system. thanks.
vijay.bP (Mon, 16 Sep 2019 14:01:37 GMT):
Thanks.
BrettLogan (Mon, 16 Sep 2019 14:34:00 GMT):
@rjones We got those changes in
rjones (Mon, 16 Sep 2019 14:37:36 GMT):
So the other in-flight changes will be abandoned, correct?
BrettLogan (Mon, 16 Sep 2019 14:38:37 GMT):
Correct
rjones (Mon, 16 Sep 2019 14:39:01 GMT):
OK. Mirror is broken (the repo is not read only on Gerrit, yet)
rjones (Mon, 16 Sep 2019 14:40:59 GMT):
go forth and accept pull requests!
rjones (Mon, 16 Sep 2019 17:58:38 GMT):
@BrettLogan I'm interested in if this is even an interesting change. I think since CODEOWNERS is per-branch, it probably is?
rjones (Mon, 16 Sep 2019 17:58:48 GMT):
https://github.com/hyperledger/fabric-ca/pull/20
BrettLogan (Mon, 16 Sep 2019 17:59:29 GMT):
I think it is as well
BrettLogan (Mon, 16 Sep 2019 23:37:14 GMT):
Fabric CA has officially been migrated to GitHub. Code changes can be submitted through the PR process via the repo at https://github.com/hyperledger/fabric-ca
BrettLogan (Mon, 16 Sep 2019 23:38:38 GMT):
CI is executed in Azure Pipelines and the UI can be found at https://dev.azure.com/Hyperledger/Fabric%20CA/_build
BrettLogan (Mon, 16 Sep 2019 23:38:38 GMT):
CI is managed via Azure Pipelines and the UI can be found at https://dev.azure.com/Hyperledger/Fabric%20CA
BrettLogan (Mon, 16 Sep 2019 23:38:38 GMT):
CI is executed in Azure Pipelines and the UI can be found at https://dev.azure.com/Hyperledger/Fabric%20CA
shitaibin (Tue, 17 Sep 2019 01:38:41 GMT):
@BrettLogan Why not add the CI status into README for fabric ca
rjones (Tue, 17 Sep 2019 03:00:21 GMT):
@shitaibin pull requests accepted
neha_ag (Thu, 19 Sep 2019 21:01:23 GMT):
Has joined the channel.
guoger (Fri, 20 Sep 2019 07:22:08 GMT):
is it still possible for people other than owner of PR to rebase the code, once we move to github?
sykesm (Fri, 20 Sep 2019 15:10:42 GMT):
yes, depending on the repo config - but it's done at merge time.
sykesm (Fri, 20 Sep 2019 15:16:01 GMT):
so, not really. :)
sstone1 (Tue, 24 Sep 2019 08:46:03 GMT):
@vijay.bP @BrettLogan my CR for fabric-samples seems to be failing to trigger a Jenkins build: https://gerrit.hyperledger.org/r/c/fabric-samples/+/33682
sstone1 (Tue, 24 Sep 2019 08:46:34 GMT):
any ideas?
sstone1 (Tue, 24 Sep 2019 08:48:11 GMT):
hmmm, i added `reverify` and it's now picked it up!
vijay.bP (Tue, 24 Sep 2019 14:35:41 GMT):
@BrettLogan @tijohnson Merge req to fix error on JAVASCRIPT CHAINCODE test in byfn on fabric master https://gerrit.hyperledger.org/r/#/c/ci-management/+/33693/
MHBauer (Tue, 24 Sep 2019 16:29:28 GMT):
? depends on lots of things, but yes, I've done that before.
caod (Tue, 24 Sep 2019 16:54:50 GMT):
somewhat of a tangent but you can also accomplish this with github actions now, here's a community provided example of one such action https://github.com/cirrus-actions/rebase similarly there are github apps that also implement this feature https://github.com/tibdex/autorebase
caod (Tue, 24 Sep 2019 16:54:50 GMT):
somewhat of a tangent but you can also accomplish this with github actions now, here's a community provided example of one such action https://github.com/cirrus-actions/rebase similarly there are github apps that also implement this feature https://github.com/tibdex/autorebase it's a bit of a mystery why github refuses to implement this natively in the UI
MHBauer (Tue, 24 Sep 2019 17:06:49 GMT):
lol
MHBauer (Tue, 24 Sep 2019 17:06:59 GMT):
I think because it could fail.
MHBauer (Tue, 24 Sep 2019 17:07:18 GMT):
by definition it kind of requires a manual look.
caod (Tue, 24 Sep 2019 17:10:17 GMT):
the desire is moreso in the case when there are no conflicts, Gerrit handles it fairly well with the existing rebase button on CRs
rjones (Tue, 24 Sep 2019 17:10:46 GMT):
the way to do it in GitHub is, TBH, allow only rebase merges.
MHBauer (Tue, 24 Sep 2019 17:10:52 GMT):
well, final merge gets you a rebase button, but I've had bad rebases in the past, so I would never fully trust anything automated.
sykesm (Thu, 26 Sep 2019 15:17:43 GMT):
Looks like master is failing linter checks
sykesm (Thu, 26 Sep 2019 15:18:34 GMT):
```
Checking with gofmt
The following files contain gofmt errors
integration/ledger/marbles_test.go
The gofmt command 'gofmt -l -s -w' must be run for these files
Makefile:169: recipe for target 'linter' failed
make: *** [linter] Error 1
```
@wenjian @dave.enyeart
wenjian (Thu, 26 Sep 2019 15:19:41 GMT):
@sykesm will look into it
wenjian (Thu, 26 Sep 2019 15:29:28 GMT):
@sykesm fixed in https://gerrit.hyperledger.org/r/#/c/fabric/+/33781/
tijohnson (Thu, 26 Sep 2019 21:20:07 GMT):
Problems with gerrit seem to have been resolved
yacovm (Fri, 27 Sep 2019 10:53:22 GMT):
gerrit is super slow today
yacovm (Fri, 27 Sep 2019 10:53:30 GMT):
@tijohnson :/
rjones (Fri, 27 Sep 2019 11:35:36 GMT):
@yacovm @tijohnson doesn't work on the Hyperledger Helpdesk any more. There are two tickets open on this issue: https://chat.hyperledger.org/channel/ci-pipeline?msg=yuDYmbrREtuJrAn9v
yacovm (Fri, 27 Sep 2019 11:36:48 GMT):
ok thanks
rjones (Fri, 27 Sep 2019 11:38:09 GMT):
If you log in here: https://jira.linuxfoundation.org/servicedesk/customer/portal/2/IT-17735 once, I can share it with you
rjones (Fri, 27 Sep 2019 13:22:41 GMT):
https://status.linuxfoundation.org/incidents/y197yg8qpb4d
rameshthoomu (Mon, 30 Sep 2019 13:37:11 GMT):
https://jenkins.hyperledger.org/ -- 502 Bad Gateway error..
BrettLogan (Mon, 30 Sep 2019 14:40:54 GMT):
For those of you with pending CI builds, I am working to identify the issue with LFIT. Jenkin's went into an unplanned shutdown, and with no jobs pending, isn't executing the shutdown cycle. We will update you when we have more information.
jyellick (Mon, 30 Sep 2019 14:50:03 GMT):
@BrettLogan Thanks for the update, was just going to ask
jyellick (Mon, 30 Sep 2019 14:50:03 GMT):
@BrettLogan Thanks for the updated, was just going to ask
BrettLogan (Mon, 30 Sep 2019 15:04:28 GMT):
LFIT has fixed the issue
jyellick (Mon, 30 Sep 2019 17:49:51 GMT):
```13:24:01 Step 3/6 : FROM alpine:${ALPINE_VER} as base
13:24:16 Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
13:24:16 Makefile:221: recipe for target 'build/images/baseos/.dummy-amd64-2.0.0-snapshot-a6ac799' failed
13:24:16 make: *** [build/images/baseos/.dummy-amd64-2.0.0-snapshot-a6ac799] Error 1```
https://jenkins.hyperledger.org/job/fabric-verify-unit-tests-x86_64/15435/console
Looks like an infrastructure flake, not sure if it's worth investigating.
vijay.bP (Mon, 30 Sep 2019 17:53:30 GMT):
Yes, It's flake just rerun the build, happens often while building the image.
jyellick (Mon, 30 Sep 2019 17:57:18 GMT):
Yes, I'd already kicked off another, just not one I've personally seen frequently.
sykesm (Tue, 01 Oct 2019 20:32:09 GMT):
master is broken; fix is pending but will need another review https://gerrit.hyperledger.org/r/c/fabric/+/33837
dsessions (Wed, 02 Oct 2019 14:59:24 GMT):
Has joined the channel.
dsessions (Wed, 02 Oct 2019 14:59:24 GMT):
Is there any sort of timetable of when fabric is going to make the move to Azure?
dsessions (Wed, 02 Oct 2019 15:01:36 GMT):
(outside of just the ca)
BrettLogan (Wed, 02 Oct 2019 15:02:30 GMT):
CA is really the gate right now to migrating other repos, let me elaborate what that means, and the rationale behind it affecting other repos timelines
sykesm (Wed, 02 Oct 2019 15:09:25 GMT):
@dsessions what's the motivation for go 1.13 on fabric 1.4?
sykesm (Wed, 02 Oct 2019 15:09:51 GMT):
I think we need to bump to 1.12 in 1.4 and 1.13 in master, fwiw.
dsessions (Wed, 02 Oct 2019 15:10:48 GMT):
We have an extensive kubernetes deployment, which includes doing the install and instantiate / upgrade on a fabric-tools based image
dsessions (Wed, 02 Oct 2019 15:11:25 GMT):
In a nut shell . . we have the team using fabric-sdk-go and using 1.13 . . with full mod support, etc.
dsessions (Wed, 02 Oct 2019 15:11:51 GMT):
but to do anything with the chaincode, we have to re-set our environments
dsessions (Wed, 02 Oct 2019 15:12:02 GMT):
it's a lot of context switching and variables from our perspective
sykesm (Wed, 02 Oct 2019 15:12:12 GMT):
right - but we don't support modules in fabric. And for chaincode, builds occur in ccenv, not at the tools.
bestbeforetoday (Wed, 02 Oct 2019 15:12:40 GMT):
Is Jenkins behaving itself right now? Adding a *reverify* comment to a CR raised against _fabric-sdk-java_ is having no effect
dsessions (Wed, 02 Oct 2019 15:13:25 GMT):
Fabric doesn't support modules . . ok . . that's news . .
vijay.bP (Wed, 02 Oct 2019 15:13:44 GMT):
Please post the CR here.
dsessions (Wed, 02 Oct 2019 15:13:51 GMT):
Obviously right now it doesn't
BrettLogan (Wed, 02 Oct 2019 15:13:58 GMT):
The job is already running Mark, you can't reverify while an existing CR has a jobb in flight
sykesm (Wed, 02 Oct 2019 15:14:05 GMT):
In master, we have very basic support for packaging and building chaincode modules. That is not part of 1.4
dsessions (Wed, 02 Oct 2019 15:14:18 GMT):
gotcha
sykesm (Wed, 02 Oct 2019 15:14:26 GMT):
And our development tree is not module enabled right now; we're still using dep.
BrettLogan (Wed, 02 Oct 2019 15:14:31 GMT):
Unfortunately its a flake of the CI system and gerrit. If you push two changes quickly back-to-back Jenkins doesnt handle it well
dsessions (Wed, 02 Oct 2019 15:14:38 GMT):
I'm just trying to make baby steps :)
BrettLogan (Wed, 02 Oct 2019 15:15:06 GMT):
YTwo of the core reasons (there are really many) we decided to migrate from Jenkins to AZP are the ability to manage our own dependencies, and the sheer number of flakes we saw related to unstable Jenkins slave infrastructure at our cloud provider. Its obvious how the second one is impacted by the migration, moving to AZP moves us onto a world-class cloud provider where they dynamically manage infrastructure for us. The first issue, around dependencies is what accelerated the timeline for us. Today in Jenkins, we bake all of our system dependencies directly into our VM images. Meaning if we want to upgrade to Go 1.13, we first have to generate a new OpenStack Image with 1.13 in it. Unfortunately, the process we've used for years to build the images was recently
dsessions (Wed, 02 Oct 2019 15:15:08 GMT):
getting the compiler version up to snuff allows a lot to happen
vijay.bP (Wed, 02 Oct 2019 15:15:17 GMT):
It's already ran on jenkins https://jenkins.hyperledger.org/view/fabric-sdk-java/job/fabric-sdk-java-master-verify-x86_64/
sykesm (Wed, 02 Oct 2019 15:15:36 GMT):
I'd like to get to modules soon but we have some (legacy) test practices that are getting in the way.
BrettLogan (Wed, 02 Oct 2019 15:15:40 GMT):
It's a flake
dsessions (Wed, 02 Oct 2019 15:15:52 GMT):
oh wow . .
sykesm (Wed, 02 Oct 2019 15:15:56 GMT):
Our (new) fabric-chaincode-go and fabric-protos-go repos are module enabled - but the core tree is not.
dsessions (Wed, 02 Oct 2019 15:16:00 GMT):
that sounds awful
BrettLogan (Wed, 02 Oct 2019 15:16:08 GMT):
It's a flake, the job got disjointed from the CR somehow
bestbeforetoday (Wed, 02 Oct 2019 15:16:24 GMT):
The existing build seems to have stalled. Last log output was 1h45m ago. Any idea how I recover it?
BrettLogan (Wed, 02 Oct 2019 15:16:24 GMT):
Build 1 is still running despite it having voted as a failure
dsessions (Wed, 02 Oct 2019 15:19:36 GMT):
I really appreciate all the feedback :)
dsessions (Wed, 02 Oct 2019 15:19:48 GMT):
I'm trying to think about ways I could contribute / help
vijay.bP (Wed, 02 Oct 2019 15:20:38 GMT):
I see the same timeout issue yesterday when i tried to push some dummy changes.https://gerrit.hyperledger.org/r/#/c/fabric-sdk-java/+/33833/
BrettLogan (Wed, 02 Oct 2019 15:21:50 GMT):
Actually now that I look at it, the first reverify he added actually triggered a second build, but Jenkins didnt send any of the info back to Gerrit
BrettLogan (Wed, 02 Oct 2019 15:22:08 GMT):
https://jenkins.hyperledger.org/view/fabric-sdk-java/job/fabric-sdk-java-master-verify-1.4-x86_64/175/
BrettLogan (Wed, 02 Oct 2019 15:22:23 GMT):
So it is running here Mark, it just hasn't sent anything back to Gerrit
BrettLogan (Wed, 02 Oct 2019 15:22:59 GMT):
When the job is done, if it hasn't sent the votes back to gerrit, can you let us know
dsessions (Wed, 02 Oct 2019 15:41:52 GMT):
Do the current build images only have Go 1.11 on them?
dsessions (Wed, 02 Oct 2019 15:41:52 GMT):
Do the current CI build images only have Go 1.11 on them?
dsessions (Wed, 02 Oct 2019 15:42:34 GMT):
I'm not sure exactly where to look to dig that information up myself
dsessions (Wed, 02 Oct 2019 15:44:17 GMT):
It doesn't sound like submitting a ticket / patch to increment the go version in master at this point is going to be fruitful anyways if there isn't a CI image that can build it
sykesm (Wed, 02 Oct 2019 15:48:49 GMT):
master will probably be updated to 1.13 as soon as we move off jenkins provided everything works in GOPATH mode.
release-1.4 is a little different. We don't want to shake the tree too much there. My concern with 1.11 is that it's not going to get fixes so moving to 1.12 is likely.
dsessions (Wed, 02 Oct 2019 16:34:47 GMT):
makes sense
dsessions (Wed, 02 Oct 2019 16:35:03 GMT):
I really appreciate all the conversation!
bestbeforetoday (Wed, 02 Oct 2019 16:52:44 GMT):
I can kick off builds again now but they are failing with timeouts as submitting transactions is taking longer than 3 minutes when running in Jenkins. Running locally (twice to be sure) the whole suite passes. Is Jenkins unusually slow today?
BrettLogan (Wed, 02 Oct 2019 16:55:13 GMT):
It's been a recurring problem for a few weeks now
sykesm (Wed, 02 Oct 2019 19:01:15 GMT):
It would be cool if you could try module based chaincode against master using the new fabric-chaincode-go repo/module.
dsessions (Wed, 02 Oct 2019 19:01:40 GMT):
sure :)
dwelch91 (Thu, 03 Oct 2019 20:12:52 GMT):
Has joined the channel.
MHBauer (Sat, 05 Oct 2019 02:17:58 GMT):
https://github.com/hyperledger/ci-management/blob/238fcb876d363540afb638a8174aa3f8763afa8f/packer/provision/docker.sh#L103-L111 I think it's this list of hardcoded stuff that's available.
rjones (Tue, 08 Oct 2019 06:28:04 GMT):
@BrettLogan @sykesm any word on moving forward with the gerrit->github migration?
scottz (Tue, 08 Oct 2019 20:05:26 GMT):
java cc
scottz (Tue, 08 Oct 2019 20:16:48 GMT):
@vijay.bP At 09:08:20 timestamp in the fabric release-1.4 merge job this morning triggered by the updating of base image version, https://jenkins.hyperledger.org/job/fabric-merge-end-2-end-x86_64/6509/consoleFull , errors occur with instantiation of java cc. Bharadwaj is having trouble himself running tests in 1.4 today with our samplecc (go). Is anyone else seeing or hearing of other problems elsewhere, having to do with the baseimage version and/or java cc ?
vijay.bP (Tue, 08 Oct 2019 20:23:24 GMT):
Retriggered the fabric merge builds again on baseimage update CR, lets check the failure again.
BrettLogan (Tue, 08 Oct 2019 20:39:49 GMT):
We did just upgrade the baseimage
BrettLogan (Tue, 08 Oct 2019 20:39:59 GMT):
Move to a new version of debian
BrettLogan (Tue, 08 Oct 2019 20:41:00 GMT):
I have to look at what you are doing, there are issues with CA and the new baseimage
BrettLogan (Tue, 08 Oct 2019 20:42:19 GMT):
However, looks like its not related to that issue. SDK node is experiencing the same issue
vijay.bP (Tue, 08 Oct 2019 20:45:30 GMT):
Cryptogen is running with Node OU enabled, which no longer populates admincerts directory.
However the orderer and peers without the latest capabilities enabled will not be identifying admins via Node OUs, they will still be identifying admins via admincerts directory. Without the directory populated. cause the error in multiple builds and it was fixed in the fabric-samples.
mbwhite (Wed, 09 Oct 2019 08:37:46 GMT):
```
00:06:30 + peer lifecycle chaincode install mycc.tar.gz
00:06:40 + res=1
00:06:40 + set +x
00:06:40 Error: chaincode install failed with status: 500 - failed to invoke backing implementation of 'InstallChaincode': could not build chaincode: failed external (no builders defined) and docker build: docker image build failed: docker build failed: Error returned from build: 1 "+ INPUT_DIR=/chaincode/input
```
Could this be lifecyle?
vijay.bP (Wed, 09 Oct 2019 13:42:46 GMT):
Could be chaincode issue, same error observed on chaincodes testing in fabric-test build.
scottz (Wed, 09 Oct 2019 14:07:33 GMT):
@BrettLogan Last night, one of our two CA FVT tests failed in our dialy run: https://jenkins.hyperledger.org/view/fabric-test/job/fabric-test-daily-ca-master-x86_64/test_results_analyzer/
rameshthoomu (Wed, 09 Oct 2019 14:17:31 GMT):
I see below error log in node chaincode tests in fabric-test daily jobs.
```
Error: could not assemble transaction, err proposal response was not successful, error code 500, msg error in simulation: could not launch chaincode mycc:0: error starting container: error building image: failed external (no builders defined) and docker build: docker image build failed: docker build failed: Error returned from build: 1 "+ INPUT_DIR=/chaincode/input
+ OUTPUT_DIR=/chaincode/output
+ cp -R /chaincode/input/src/. /chaincode/output
+ cd /chaincode/output
+ '[' -f package-lock.json -o -f npm-shrinkwrap.json ]
+ npm install --production
npm ERR! code ETARGET
npm ERR! notarget No matching version found for fabric-contract-api@2.0.0-snapshot
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget
npm ERR! notarget It was specified as a dependency of 'fabric-shim'
npm ERR! notarget
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-10-09T01_36_33_443Z-debug.log
"
[sh -c "CORE_PEER_MSPCONFIGPATH=/var/hyperledger/configs/f2d12d90ea3411e9877afa163eccae36/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp CORE_PEER_LOCALMSPID=org1.example.com CORE_PEER_ID=peer0.org1.example.com CORE_PEER_ADDRESS=peer0.org1.example.com:7051 peer chaincode instantiate --name mycc --version 0 --lang NODE --channelID behavesystest --ctor '{\"Args\": [\"init\",\"a\",\"1000\",\"b\",\"2000\"]}' --orderer orderer0.example.com:7050 "]: {'peer0.org1.example.com': 'Error occurred [u\'docker exec peer0.org1.example.com sh -c "CORE_PEER_MSPCONFIGPATH=/var/hyperledger/configs/f2d12d90ea3411e9877afa163eccae36/peerOrganizations/org1.example.com/users/Admin@org1.example.com/msp CORE_PEER_LOCALMSPID=org1.example.com CORE_PEER_ID=peer0.org1.example.com CORE_PEER_ADDRESS=peer0.org1.example.com:7051 peer chaincode instantiate --name mycc --version 0 --lang NODE --channelID behavesystest --ctor \\\'{\\\\"Args\\\\": [\\\\"init\\\\",\\\\"a\\\\",\\\\"1000\\\\",\\\\"b\\\\",\\\\"2000\\\\"]}\\\' --orderer orderer0.example.com:7050 "\']: \x1b[34m2019-10-09 01:36:27.332 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 001\x1b[0m Using default escc\n\x1b[34m2019-10-09 01:36:27.332 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 002\x1b[0m Using default vscc\nError: could not assemble transaction, err proposal response was not successful, error code 500, msg error in simulation: could not launch chaincode mycc:0: error starting container: error building image: failed external (no builders defined) and docker build: docker image build failed: docker build failed: Error returned from build: 1 "+ INPUT_DIR=/chaincode/input\n+ OUTPUT_DIR=/chaincode/output\n+ cp -R /chaincode/input/src/. /chaincode/output\n+ cd /chaincode/output\n+ \'[\' -f package-lock.json -o -f npm-shrinkwrap.json ]\n+ npm install --production\nnpm ERR! code ETARGET\nnpm ERR! notarget No matching version found for fabric-contract-api@2.0.0-snapshot\nnpm ERR! notarget In most cases you or one of your dependencies are requesting\nnpm ERR! notarget a package version that doesn\'t exist.\nnpm ERR! notarget \nnpm ERR! notarget It was specified as a dependency of \'fabric-shim\'\nnpm ERR! notarget \n\nnpm ERR! A complete log of this run can be found in:\nnpm ERR! /root/.npm/_logs/2019-10-09T01_36_33_443Z-debug.log\n"\n'}
```
rameshthoomu (Wed, 09 Oct 2019 14:20:17 GMT):
@vijay.bP did you observe the same issue?
rameshthoomu (Wed, 09 Oct 2019 14:20:24 GMT):
I am looking at here https://jenkins.hyperledger.org/view/fabric-test/job/fabric-test-daily-behave-master-x86_64/369/
rameshthoomu (Wed, 09 Oct 2019 14:20:24 GMT):
I am looking here https://jenkins.hyperledger.org/view/fabric-test/job/fabric-test-daily-behave-master-x86_64/369/
vijay.bP (Wed, 09 Oct 2019 14:23:08 GMT):
Yes it is, and there are CR's merged in chaincode-node project, this may cause the problem in chaincode install in multiple places like fail byfn(javascript chaincode) in fabric and chaincodes testing in fabric-test projects.
scottz (Wed, 09 Oct 2019 14:26:52 GMT):
@rameshthoomu yes that would explain why our tests are failing that use chaincode written in the nodejs language. @vijay.bP Did you open a bug yet for these failures? If you see that the error is the same in different jobs, you could create one bug with each job as a reference, rather than duplicate bugs. And ship it to the people who changed things yesterday in chaincode-node.
scottz (Wed, 09 Oct 2019 14:31:22 GMT):
the error may not be a coding error but rather a problem with the images, per: `No matching version found for fabric-contract-api@2.0.0-snapshot`
vijay.bP (Wed, 09 Oct 2019 14:58:09 GMT):
@scottz @rameshthoomu @mbwhite Bug was created for the above chaincode-node issue https://jira.hyperledger.org/browse/FAB-16798
mbwhite (Wed, 09 Oct 2019 15:33:41 GMT):
https://gerrit.hyperledger.org/r/c/fabric-chaincode-node/+/33917 [FAB-16797] Typo in pathname < and the CR ;)
scottz (Thu, 10 Oct 2019 13:32:23 GMT):
Looks like none of the fabric-test daily jobs ran last night. Did the fabric e2e job run, @vijay.bP ?
scottz (Thu, 10 Oct 2019 13:34:31 GMT):
@BrettLogan Thanks for kicking off this build again yesterday afternoon, but it failed again. I don't see any IOError, so maybe something else is going on? https://jenkins.hyperledger.org/view/fabric-test/job/fabric-test-daily-ca-master-x86_64/test_results_analyzer/
BrettLogan (Thu, 10 Oct 2019 13:35:10 GMT):
Taking a look. I meant to look at it yesterday, as I saw it failed, but never got to it.
mbwhite (Wed, 16 Oct 2019 13:19:43 GMT):
Looks like there are issues with Sonatype Java repos (again)
tijohnson (Fri, 18 Oct 2019 18:08:27 GMT):
OS updates @ 16:00 Disabling Jenkins Production queue in 1 hr (15:00)
tijohnson (Fri, 18 Oct 2019 18:08:27 GMT):
OS updates @ 16:00 Disabling Jenkins Production/Sandbox queues in 1 hr (15:00)
tijohnson (Fri, 18 Oct 2019 19:24:00 GMT):
OS updates @ 16:00 I have already shutdown the Jenkins Production/Sandbox queues
tijohnson (Fri, 18 Oct 2019 20:02:50 GMT):
OS updates @ 16:00 starting immediately
tijohnson (Fri, 18 Oct 2019 21:01:25 GMT):
OS Update are complete all system are back on-line, Jobs are running on Jenkins production
BrettLogan (Fri, 18 Oct 2019 21:03:35 GMT):
Thanks Tim
tijohnson (Mon, 21 Oct 2019 21:09:49 GMT):
We would like a quick restart of the WIKI server wiki.hyperledger.org (5-10mins) @ 17:30EST ( in 20mins) any objections?
rjones (Mon, 21 Oct 2019 21:54:06 GMT):
@tijohnson did that happen?
sstone1 (Tue, 22 Oct 2019 14:39:59 GMT):
@rjones @BrettLogan I can't seem to do anything with this PR, even though I'm listed in the CODEOWNERS file: https://github.com/hyperledger/fabric-samples/pull/67
sstone1 (Tue, 22 Oct 2019 14:40:09 GMT):
I can't edit the reviewers or the labels etc
BrettLogan (Tue, 22 Oct 2019 14:40:31 GMT):
I am going to guess you never accepted your invite to the hyperledger org
BrettLogan (Tue, 22 Oct 2019 14:41:00 GMT):
Give me a minute
sstone1 (Tue, 22 Oct 2019 14:41:12 GMT):
I'm in the Hyperledger org, maybe I missed a new team?
BrettLogan (Tue, 22 Oct 2019 14:41:46 GMT):
Thats what I meant, mispoke(typed)
BrettLogan (Tue, 22 Oct 2019 14:41:50 GMT):
Let me check
rjones (Tue, 22 Oct 2019 14:45:41 GMT):
@sstone1 oversight on my part - give me a minute
rjones (Tue, 22 Oct 2019 14:48:27 GMT):
@sstone1 should be gtg now
sstone1 (Tue, 22 Oct 2019 14:49:06 GMT):
woohoo thanks @rjones & @BrettLogan
rjones (Tue, 22 Oct 2019 14:50:21 GMT):
You guys should probably make the settings in https://github.com/hyperledger/fabric-samples/blob/master/.github/stale.yml and https://github.com/hyperledger/fabric-samples/blob/release-1.4/.github/stale.yml a little more sensible :)
sstone1 (Tue, 22 Oct 2019 14:50:39 GMT):
:joy: I'll get right on that
rjones (Tue, 22 Oct 2019 14:52:21 GMT):
It marks every PR stale instantly, which is probably a little annoying.
BrettLogan (Tue, 22 Oct 2019 14:55:19 GMT):
Thank @rjones
BrettLogan (Tue, 22 Oct 2019 14:55:26 GMT):
Now stop answering our messages and sleep
BrettLogan (Tue, 22 Oct 2019 14:55:28 GMT):
lol
scottz (Wed, 23 Oct 2019 14:11:25 GMT):
@BrettLogan The crl_test.sh script in the fabric-test daily CTE job (fabric-ca tests) uses openssl. Did you say that is changed, or no longer available in fabric-ca?
BrettLogan (Wed, 23 Oct 2019 14:13:56 GMT):
Yea. The version of ssl changed. Though if all your doing is generating certs, your fine. If instead, you are calling openssl with --text flag to return the output to the cli, and then you are using that output, the format has changed.
BrettLogan (Wed, 23 Oct 2019 14:15:44 GMT):
Of course, also, if fabric-ca is a submodule, and you haven't upgraded to the latest commit, but are using the latest baseimage, the fabric-ca-setup script that is used to stand up CAs is broken because of the openssl change
BrettLogan (Wed, 23 Oct 2019 14:16:15 GMT):
The simple fix there is update to the latest commit in the submodule
BrettLogan (Wed, 23 Oct 2019 14:16:48 GMT):
@scottz
scottz (Wed, 23 Oct 2019 14:28:11 GMT):
yes at least once we are parsing the text: r="$(openssl crl -noout -text -in $CA_CFG_PATH/$ADMINUSER/msp/crls/crl.pem |
awk '/Serial Number:/ {printf $NF" "}')"
and we do have fabric-ca submodule in fabric-test - but let me see if we are actually using it for these tests...
scottz (Wed, 23 Oct 2019 15:23:55 GMT):
@BrettLogan I see on my laptop: $ openssl version
OpenSSL 1.0.2s 28 May 2019
and the CI jobs seem to be using version OpenSSL 1.0.1t
When you say the version changed... where? changed to what?
BrettLogan (Wed, 23 Oct 2019 15:37:31 GMT):
Baseimage 0.4.16 has ossl 1.1.x
nfrunza (Wed, 23 Oct 2019 16:03:29 GMT):
Hello team, i found out that Jenkins, and gerrit are EOL end of the year, what is the alternative, we are supporting HLExplorer, and what would be the transition to the new tools?
BrettLogan (Wed, 23 Oct 2019 20:09:10 GMT):
Follow the #cicd channel for this conversation
nfrunza (Thu, 24 Oct 2019 13:35:56 GMT):
@BrettLogan sure, thank you
cenkozan (Fri, 25 Oct 2019 10:20:33 GMT):
Has joined the channel.
BrettLogan (Mon, 28 Oct 2019 00:23:14 GMT):
Just an FYI: We are aware of issues related to docker pulls to Nexus3 failing due to HTTPS handshakes, unfortunately we are unlikely to be able to do anything about it tonight (US EST timezone), but will pick up the work in the morning once sysadmins with LFIT get in.
BrettLogan (Mon, 28 Oct 2019 00:43:30 GMT):
Both Nexus & Nexus3 are serving artifacts around `26 B/s` we have opened a ticket with LFIT
BrettLogan (Mon, 28 Oct 2019 00:43:30 GMT):
Both Nexus & Nexus3 are serving at artifacts around `26 B/s` we have opened a ticket with LFIT
caod (Mon, 28 Oct 2019 19:29:33 GMT):
seeing `No Builds Executed` when attempting to `Run VerifyBuild`
rameshthoomu (Tue, 29 Oct 2019 11:17:41 GMT):
@caod any specific build reference?
BrettLogan (Tue, 29 Oct 2019 13:06:38 GMT):
It's good. It was working as expected. Just took a little longer for the VM to provision. So typing verifybuild didn't execute a new build as the other one was still running
tegie (Wed, 30 Oct 2019 11:36:38 GMT):
Has joined the channel.
mastersingh24 (Sat, 09 Nov 2019 10:15:30 GMT):
Looks like we are currently failing to mirror gerrit to github for the fabric repo
BrettLogan (Sat, 09 Nov 2019 14:02:57 GMT):
@mastersingh24 I'll get on that
BrettLogan (Sat, 09 Nov 2019 14:16:33 GMT):
I think it's fixed, we will see on the next merge if it catches up on its own
sstone1 (Tue, 12 Nov 2019 13:09:35 GMT):
```
$ curl -o /dev/null https://nexus.hyperledger.org/content/repositories/releases/org/hyperledger/fabric/hyperledger-fabric/linux-amd64-1.4.3/hyperledger-fabric-linux-amd64-1.4.3.tar.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- 0:00:57 --:--:-- 0
```
nexus appears to be having difficulties at the moment
BrettLogan (Tue, 12 Nov 2019 13:23:03 GMT):
@sstone1 are you still seeing that issue, in the US it looks alright (the datacenter is in Canada)
sstone1 (Tue, 12 Nov 2019 13:29:02 GMT):
@BrettLogan seems to be working now!
BrettLogan (Tue, 12 Nov 2019 13:46:23 GMT):
We've been having network issues left and right coming out of that datacenter over the last month, the general consensus is, we cant move off Nexus soon enough and be done with this infrastructure. That seems to be the only way out of this problem
BrettLogan (Tue, 12 Nov 2019 13:46:41 GMT):
Disk IO issues as well in Jenkins, be glad your out of that world :)
sstone1 (Thu, 14 Nov 2019 09:12:51 GMT):
@BrettLogan I am! on another note - what's going on with fabric-samples? AZP doesn't seem to be picking up certain PRs: https://github.com/hyperledger/fabric-samples/pull/69
rjones (Thu, 14 Nov 2019 09:53:48 GMT):
@BrettLogan it looks like you have fabric-samples hooked up to github using your personal account
awjh (Thu, 14 Nov 2019 10:54:41 GMT):
Hi, I am looking to get a repo for the contract api for go work. Preferably `fabric-contract-api-go`. @heatherp and myself would be maintainers
rjones (Thu, 14 Nov 2019 13:19:57 GMT):
hi, you should get that approved via the `fabric-rfc` process I think
rjones (Thu, 14 Nov 2019 13:21:21 GMT):
@awjh ask in #fabric-maintainers for approval
BrettLogan (Thu, 14 Nov 2019 14:41:41 GMT):
It ended up being that maintainers don't have permission to issue comment triggers, trying to work through what the correct settings are for this. According to the doc everything seems to be right, but still doesn't seem to pickup comment triggers from people who aren't admins.
rjones (Thu, 14 Nov 2019 14:44:57 GMT):
ugh
rjones (Thu, 14 Nov 2019 14:45:40 GMT):
when I tried to do a build in the AZP UI, it said I didn't have permissions to the GitHub API. That's when I found it was linked to your account
awjh (Tue, 19 Nov 2019 14:03:03 GMT):
Hi, what is the process for getting azure pipelines turned on for github.com/hyperledger/fabric-contract-api-go?
BrettLogan (Tue, 19 Nov 2019 16:03:58 GMT):
Do you have a pipeline written for it yet? @awjh
awjh (Tue, 19 Nov 2019 16:04:32 GMT):
Yes it is in the .azure-pipelines folder
BrettLogan (Tue, 19 Nov 2019 16:05:15 GMT):
I'll enable it when I get back from lunch
rjones (Tue, 19 Nov 2019 16:05:20 GMT):
you ask @BrettLogan to tell me to turn it on
BrettLogan (Tue, 19 Nov 2019 16:06:11 GMT):
Lolol
rjones (Tue, 19 Nov 2019 16:07:07 GMT):
@awjh what is your GitHub ID
awjh (Tue, 19 Nov 2019 16:07:14 GMT):
awjh-ibm :)
rjones (Tue, 19 Nov 2019 16:08:43 GMT):
since you don't have a valid, public email in your GitHub profile, I can't invite you to azure
rjones (Tue, 19 Nov 2019 16:09:34 GMT):
anyway: https://dev.azure.com/Hyperledger/fabric-contract-api-go/_build/results?buildId=2195&view=results
awjh (Tue, 19 Nov 2019 16:11:11 GMT):
Thanks :)
rjones (Tue, 19 Nov 2019 16:12:40 GMT):
```2019-11-19T16:08:09.3110046Z running gofmt...
2019-11-19T16:08:09.3699870Z The following files contain gofmt errors:
2019-11-19T16:08:09.3700067Z internal/transaction_handler.go
2019-11-19T16:08:09.3700134Z internal/transaction_handler_test.go
2019-11-19T16:08:09.3700788Z Please run 'gofmt -l -s -w' for these files.```
awjh (Tue, 19 Nov 2019 16:16:25 GMT):
Oh dear, better fix that tomorrow
awjh (Tue, 19 Nov 2019 16:16:25 GMT):
Oh dear, I better fix that tomorrow
rjones (Tue, 19 Nov 2019 16:20:55 GMT):
https://github.com/hyperledger/fabric-contract-api-go/pull/3
rjones (Tue, 19 Nov 2019 16:22:48 GMT):
@awjh should mbwhite be a CODEOWNER? they're a MAINTAINER
rjones (Tue, 19 Nov 2019 16:23:36 GMT):
heatherlp has not accepted the invite to become a MAINTAINER
awjh (Tue, 19 Nov 2019 16:23:55 GMT):
She's out of office for now, she will accept it tomorrow
awjh (Tue, 19 Nov 2019 16:24:21 GMT):
I will fix mbwhite
rjones (Tue, 19 Nov 2019 16:24:46 GMT):
like, *fix* or `fix`? sounds ominous
awjh (Tue, 19 Nov 2019 16:25:24 GMT):
`fix`
rjones (Tue, 19 Nov 2019 16:25:47 GMT):
... I will hand you the chloroform and say no more
awjh (Wed, 20 Nov 2019 16:49:42 GMT):
Screenshot 2019-11-20 at 16.48.25.png
awjh (Wed, 20 Nov 2019 16:49:44 GMT):
@rjones any ideas why this woul dbe happening with Azure on a PR? It ran automatically. I did force push over a previous commit if that makes a difference?
awjh (Wed, 20 Nov 2019 16:50:44 GMT):
The repo is fabric-contract-api-go
rjones (Wed, 20 Nov 2019 16:57:39 GMT):
@awjh the issue is @BrettLogan renamed things and I need to make a change to match.
rjones (Wed, 20 Nov 2019 16:58:57 GMT):
@awjh look now :)
BrettLogan (Wed, 20 Nov 2019 16:59:43 GMT):
Thanks Ry, forgot to fix that part
rjones (Wed, 20 Nov 2019 17:00:56 GMT):
I don't think you could have.
rjones (Wed, 20 Nov 2019 17:37:19 GMT):
@BrettLogan do you need anything from me to support the new YAMLs I saw merged?
BrettLogan (Wed, 20 Nov 2019 17:43:21 GMT):
Not yet, we are switching over on Friday
rjones (Wed, 20 Nov 2019 17:44:36 GMT):
right, I meant vault binding or anything like that
BrettLogan (Wed, 20 Nov 2019 18:54:56 GMT):
Ah, no, only Fabric need the vault binding but it is set up already
BrettLogan (Wed, 20 Nov 2019 18:55:18 GMT):
And we are running CI for Fabric in Azure alongside Jenkins to test it through Friday
BrettLogan (Wed, 20 Nov 2019 18:55:23 GMT):
It's looking good
rjones (Wed, 20 Nov 2019 22:26:19 GMT):
@BrettLogan why did you rename all of the workflows? I'm OK with it, I just want to make sure I do the right thing in the future
BrettLogan (Wed, 20 Nov 2019 22:37:40 GMT):
@rjones So depending on how you name the projects and pipelines, if you copy the urls from the Azure UI it generates an escape sequence for some of the characters, and then when you paste them in RockteChat, it interprets the tailing end of the escape sequence as one of its special sequences and converts it something like a square purple box
BrettLogan (Wed, 20 Nov 2019 22:37:40 GMT):
@rjones So depending on how you name the projects and pipelines, if you copy the urls from the Azure UI it generates an escape sequence for some of the characters, and then when you paste them in RockteChat, rocket chat interprets the tailing end of the escape sequence as one if its special sequences and converts it something like a square purple box
BrettLogan (Wed, 20 Nov 2019 22:37:40 GMT):
@rjones So depending on how you name the projects and pipelines, if you copy the urls from the Azure UI it generates an escape sequence for some of the characters, and then when you paste them in RockteChat, it interprets the tailing end of the escape sequence as one if its special sequences and converts it something like a square purple box
BrettLogan (Wed, 20 Nov 2019 22:38:26 GMT):
So I've been trying to rename them to use `-` dashes instead of spaces and capital letter for each word as the special sequences dont ever include capital letters as ebst as I could tell
BrettLogan (Wed, 20 Nov 2019 22:39:09 GMT):
And then the default name for the pipelines I've been renaming to the projects name to prevent the same thing occuring
heatherp (Thu, 21 Nov 2019 14:33:59 GMT):
Can someone help me understand why the azure check isn't being listed under the "Checks" tab for fabric-sdk-node (nor fabric-contract-api-go) PRs? e.g. https://github.com/hyperledger/fabric-sdk-node/pull/33/checks
heatherp (Thu, 21 Nov 2019 14:33:59 GMT):
Can someone help me understand why the azure check isn't being listed under the "Checks" tab for fabric-sdk-node (nor fabric-contract-api-go) PRs? e.g. https://github.com/hyperledger/fabric-sdk-node/pull/33/checks
Despite a build running against it
BrettLogan (Thu, 21 Nov 2019 14:41:17 GMT):
hmmmm
heatherp (Thu, 21 Nov 2019 14:42:20 GMT):
maybe it doesn't matter? But it kinda makes it seem like all it cares about is the DCO
BrettLogan (Thu, 21 Nov 2019 14:45:36 GMT):
There is no discernible reason I can see why it wouldn't be listed on the Checks page, let me research it a bit. The only post I've found about it doesn't apply to us
rjones (Thu, 21 Nov 2019 14:48:48 GMT):
why do you have two sets of identical branch protection rules?
BrettLogan (Thu, 21 Nov 2019 16:18:00 GMT):
Becuase we had to exclude gh-pages from the rule
BrettLogan (Thu, 21 Nov 2019 16:18:00 GMT):
Because we had to exclude gh-pages branch from the rule
BrettLogan (Thu, 21 Nov 2019 16:18:00 GMT):
Becuase we had to exclude gh-pages branch from the rule
BrettLogan (Thu, 21 Nov 2019 16:18:41 GMT):
Is there a way to regex the pattern
rjones (Thu, 21 Nov 2019 16:18:45 GMT):
ah. I wonder if branch protections support negations in regex?
BrettLogan (Thu, 21 Nov 2019 16:18:49 GMT):
I tried to find doc on it but couldn't
rjones (Thu, 21 Nov 2019 16:19:21 GMT):
I dunno. Make a repo in your personal account and create some branches and dork with it
BrettLogan (Thu, 21 Nov 2019 16:21:32 GMT):
https://github.community/t5/How-to-use-Git-and-GitHub/Apply-a-single-branch-protection-rule-to-both-master-and-release/td-p/11587
BrettLogan (Thu, 21 Nov 2019 16:21:42 GMT):
Not possible, GitHub said create 2 rules
BrettLogan (Thu, 21 Nov 2019 16:21:58 GMT):
...seems shortsighted
rjones (Thu, 21 Nov 2019 16:22:25 GMT):
eh bummer
rjones (Fri, 22 Nov 2019 14:17:32 GMT):
down to 5! https://gerrit.hyperledger.org/r/q/status:open+project:fabric
BrettLogan (Fri, 22 Nov 2019 15:29:02 GMT):
Down to 0 now
BrettLogan (Fri, 22 Nov 2019 15:33:27 GMT):
We are in the process of Migrating Fabric to GitHub. We will let everyone know when we are done. Maintainers please do not merge any changes in Gerrit or GitHub until we give the all clear
BrettLogan (Fri, 22 Nov 2019 15:51:59 GMT):
And that is all, we are officially on GitHub. Maintainers can start the review process using GitHub moving forward
rjones (Fri, 22 Nov 2019 18:59:28 GMT):
https://dev.azure.com/Hyperledger/Fabric/_build?definitionId=50&_a=summary neat
bestbeforetoday (Fri, 22 Nov 2019 20:50:40 GMT):
Please could somebody stop stalebot from immediately tagging any GitHub PRs raised against _fabric-sdk-java_ as stale with this message now we are using GitHub for changes
> Thank you for your contribution! Please use gerrit for the changes,
rjones (Fri, 22 Nov 2019 20:52:55 GMT):
@bestbeforetoday https://github.com/hyperledger/fabric-sdk-java/pull/27
davidkhala (Sun, 24 Nov 2019 08:31:26 GMT):
Is `fabric-test` the only remaining repos in gerrit among fabric project famaly now?
BrettLogan (Sun, 24 Nov 2019 16:15:10 GMT):
@davidkhala that is correct, everything else had moved to Github and Azure Pipelines
BrettLogan (Wed, 27 Nov 2019 23:01:31 GMT):
We have merged the change to the make the `/ci-run` comment active. Maintainers and the Pull Request author can comment `/ci-run` to retrigger failed CI. Note: It does retrigger all of the jobs, maintainers, next week after the holiday, I will get instructions out on how to create Azure DevOps accounts so you can trigger individual jobs rather than all of them.
BrettLogan (Wed, 27 Nov 2019 23:01:31 GMT):
We have merged the change to the make the /ci-run comment active. Maintainers and the Pull Request author can comment /ci-run to retrigger failed CI. Note: It does retrigger all of the jobs, maintainers, next week after the holiday, I will get instructions out on how to create Azure DevOps accounts so you can trigger individual jobs rather than all of them.
karthikeyanb (Fri, 29 Nov 2019 06:05:41 GMT):
Has joined the channel.
karthikeyanb (Fri, 29 Nov 2019 06:05:41 GMT):
Hi ALl, ow to resolve this issue ,* Error: got unexpected status: BAD_REQUEST -- error validating channel creation transaction for new channel 'mychannel', could not succesfully apply update to template configuration: error authorizing update: error validating DeltaSet: policy for [Group] /Channel/Application not satisfied: implicit policy evaluation failed - 0 sub-policies were satisfied, but this policy requires 1 of the 'Admins' sub-policies to be satisfied*
davidkhala (Tue, 03 Dec 2019 11:35:00 GMT):
Where do you see it?
heatherp (Wed, 04 Dec 2019 09:37:10 GMT):
Hey guys, I'm making some changes to the way the node sdk runs tests, and back in Jenkins world, I was aware that on fabric merge builds, "gulp test" or something similar, was run after the node sdk was pulled down. I can't see any evidence of this or something similar being run in azure (i.e. https://dev.azure.com/Hyperledger/Fabric/_build/results?buildId=2969&view=results).
If I remove the "gulp test" command from the node sdk, will this impact fabric merge builds?
BrettLogan (Wed, 04 Dec 2019 14:39:39 GMT):
When we moved Fabric and Fabric-CA we stopped running BYFN and other SDK related suites on merge. Today we run their own Unit Tests only. So you are ok to make this change. @heatherp
heatherp (Wed, 04 Dec 2019 14:40:08 GMT):
awesome, thanks!
rjones (Wed, 04 Dec 2019 15:25:58 GMT):
@BrettLogan did I break this yesterday? https://github.com/hyperledger/fabric-sdk-node/commit/11b5a553c88192e649c2e2b1b8891fe649f3ae15
BrettLogan (Wed, 04 Dec 2019 15:29:06 GMT):
It never worked. It finally worked today. They published NPM for the first time today
BrettLogan (Wed, 04 Dec 2019 15:29:25 GMT):
So maybe you broke it, but we will never know lol
rjones (Wed, 04 Dec 2019 15:30:00 GMT):
oh OK, cool. I deleted the NPM and NPM_OTHER tokens and updated the service connections to use the new token yesterday
rjones (Wed, 04 Dec 2019 15:30:30 GMT):
Also, I'm starting to loathe NPM the website
BrettLogan (Wed, 04 Dec 2019 15:31:35 GMT):
200% agreed, so unintuitive
rjones (Wed, 04 Dec 2019 15:32:14 GMT):
and wrong. I followed the examples for using the `npm` command line tools to manage the `hyperledger` org and the examples are wrong
BrettLogan (Wed, 04 Dec 2019 15:33:22 GMT):
Sounds like Fabric a little bit
rjones (Wed, 04 Dec 2019 15:43:16 GMT):
What is the feeling of Fabric developers on the reliability and speed of AZP versus the previous implementation? It looks like the number of flakes is lower
rjones (Wed, 04 Dec 2019 15:49:52 GMT):
Neat: https://www.npmjs.com/package/@solarlabru/fabric-chaincode-utils (MIT license, though)
heatherp (Wed, 04 Dec 2019 16:38:25 GMT):
Our biggest woes have been permissions/control based. But I find it much more reliable, easier to navigate build output. fabric-chaincode-go hasn't got any integration tests yet but a build takes just two minutes. I'm sure previously I would have waited two minutes for jenkins to wake up
Qeven (Thu, 05 Dec 2019 07:11:36 GMT):
Has joined the channel.
serial-coder (Thu, 05 Dec 2019 13:43:41 GMT):
Has joined the channel.
rjones (Fri, 06 Dec 2019 19:07:36 GMT):
@rameshthoomu @BrettLogan may I ask LFIT to dispose of the Jenkins sandbox? https://jenkins.hyperledger.org/sandbox/
rjones (Fri, 06 Dec 2019 19:08:53 GMT):
I don't think it's been used in a couple weeks.
BrettLogan (Fri, 06 Dec 2019 19:11:21 GMT):
I'm all for it
BrettLogan (Fri, 06 Dec 2019 19:11:31 GMT):
No reason to keep it around
rjones (Fri, 06 Dec 2019 19:12:24 GMT):
what about Jenkins itself?
BrettLogan (Fri, 06 Dec 2019 19:13:27 GMT):
I think I'll be ready on Monday for that one.
rjones (Fri, 06 Dec 2019 19:14:32 GMT):
OK.
rjones (Sun, 08 Dec 2019 19:28:54 GMT):
LOL Azure billed me one US penny last month for usage. Nobody made money on my paying that bill
BrettLogan (Sun, 08 Dec 2019 19:37:22 GMT):
LOLOL, not after the base fee for a credit card transaction ha
rjones (Sun, 08 Dec 2019 21:29:47 GMT):
yup. It was for the secret storage
rjones (Mon, 09 Dec 2019 20:49:42 GMT):
@BrettLogan is this actually a nexus issue, or something else? https://dev.azure.com/Hyperledger/Fabric-SDK-Node/_build/results?buildId=3373&view=logs&j=12f1170f-54f2-53f3-20dd-22fc7dff55f9&t=bd05475d-acb5-5619-3ccb-c46842dbc997&l=210
BrettLogan (Mon, 09 Dec 2019 21:05:44 GMT):
No, the Chaincode Java project is publishing with the wrong tag
BrettLogan (Mon, 09 Dec 2019 21:06:24 GMT):
So the 2.0.0-stable image aged out finally and now the only thing that exists 2.0.0-SNAPSHOT-stable. We opened a Jira today for them to remove "SNAPSHOT" from the tag
rjones (Mon, 09 Dec 2019 21:25:40 GMT):
ahh ok
rjones (Mon, 09 Dec 2019 21:26:05 GMT):
thought it might be my trying to change package names to use the `@hyperledger` namespace
rjones (Wed, 11 Dec 2019 15:52:54 GMT):
May I kill https://jenkins.hyperledger.org ? May I kill nexus2/3?
BrettLogan (Wed, 11 Dec 2019 17:49:19 GMT):
I have everything done, I am talking to the project maintainers now to work through the last bit
BrettLogan (Wed, 11 Dec 2019 17:49:32 GMT):
I am pulling for this week
BrettLogan (Wed, 11 Dec 2019 17:49:42 GMT):
Well it has to be this week
BrettLogan (Wed, 11 Dec 2019 17:49:42 GMT):
Will be this week
dave.enyeart (Wed, 11 Dec 2019 22:10:31 GMT):
Fabric doc builds are failing in Azure due to an Azure outage...
rjones (Thu, 12 Dec 2019 13:30:54 GMT):
Are we done with PPC and s390x builds on Jenkins? If so, I'll ask the people that maintain those VMs to recycle them
BrettLogan (Thu, 12 Dec 2019 14:23:30 GMT):
We are
bestbeforetoday (Fri, 13 Dec 2019 13:06:59 GMT):
@rjones Please could you (or @BrettLogan) add the GitHub publishing credentials to the https://dev.azure.com/Hyperledger/Fabric-Gateway-Java pipeline so we can do doc publishing to the _hyperledger/fabric-gateway-java_ gh-pages site, similar to the other SDK and chaincode builds? So it’s just the *GITHUB-PAT* variable that’s needed (as it’s named in the fabric-sdk-node pipeline credentials)
BrettLogan (Fri, 13 Dec 2019 13:11:15 GMT):
It was there, just not enabled, I enabled it
SigmaS 1 (Fri, 13 Dec 2019 14:10:08 GMT):
Has joined the channel.
bestbeforetoday (Wed, 18 Dec 2019 09:35:31 GMT):
@rjones Do you have maintainer powers for https://github.com/fabric-gateway-java/fabric-gateway-java.github.io ? If so, please could you review (& merge) this PR to complete our move to a new location for the API documentation:
https://github.com/fabric-gateway-java/fabric-gateway-java.github.io/pull/1
bestbeforetoday (Wed, 18 Dec 2019 09:35:31 GMT):
@rjones Do you have maintainer powers for https://github.com/fabric-gateway-java/fabric-gateway-java.github.io ? If so, please could you review (& merge) this PR to complete our move to a new location for the API documentation:
- https://github.com/fabric-gateway-java/fabric-gateway-java.github.io/pull/1
rjones (Wed, 18 Dec 2019 15:00:37 GMT):
I do not. I have no idea who owns that, sorry. @bestbeforetoday
rjones (Wed, 18 Dec 2019 15:03:14 GMT):
@bestbeforetoday I suspect it is owned by @rameshthoomu or @TimJohnson
rjones (Wed, 18 Dec 2019 15:03:14 GMT):
@bestbeforetoday I suspect it is owned by @rameshthoomu or he knows who owns it
AbhijeetSamanta (Thu, 19 Dec 2019 04:28:57 GMT):
Has joined the channel.
bestbeforetoday (Thu, 19 Dec 2019 10:13:45 GMT):
@rameshthoomu Here is another one to be merged (relocating Node SDK docs): https://github.com/fabric-sdk-node/fabric-sdk-node.github.io/pull/3
rameshthoomu (Mon, 23 Dec 2019 20:14:00 GMT):
merged
rjones (Mon, 23 Dec 2019 20:30:45 GMT):
https://github.com/fabric-gateway-java/fabric-gateway-java.github.io/pull/1 as well
BrettLogan (Mon, 23 Dec 2019 21:34:42 GMT):
Thanks Ramesh!
guoger (Thu, 09 Jan 2020 06:41:01 GMT):
@BrettLogan hi brett, i have a question about timestamp of CI logs. I'm investigating a [new flake](https://dev.azure.com/Hyperledger/0227bd2c-c4f6-478f-be00-ee519f115180/_apis/build/builds/4849/logs/65) and i wonder if the timestamp in logs actually reflects real time? they seem to be printed at the *time* (within 1 sec)? the flake is caused by an `Eventually` assertion timeout, which is 10seconds
smithbk (Thu, 09 Jan 2020 20:23:47 GMT):
Has left the channel.
bestbeforetoday (Tue, 14 Jan 2020 16:00:20 GMT):
@rameshthoomu Please could you merge the _fabric-gateway-java.github.io_ PR linked by Ry above
rameshthoomu (Tue, 14 Jan 2020 16:28:31 GMT):
@bestbeforetoday sure will provide access to @BrettLogan . So that he can take care of these requests in future..
rameshthoomu (Tue, 14 Jan 2020 16:28:45 GMT):
@BrettLogan let me know when your available time..
rameshthoomu (Tue, 14 Jan 2020 16:44:32 GMT):
done
bestbeforetoday (Tue, 14 Jan 2020 17:05:34 GMT):
Thank you! :thumbsup:
ArthurYongShi (Wed, 15 Jan 2020 07:04:20 GMT):
Has joined the channel.
rchaturv (Thu, 16 Jan 2020 07:53:52 GMT):
Has joined the channel.
lzaouche (Tue, 28 Jan 2020 09:17:21 GMT):
Has joined the channel.
ahmedsajid (Wed, 19 Feb 2020 20:30:11 GMT):
Has joined the channel.
qwertlimframe (Mon, 02 Mar 2020 05:10:39 GMT):
Has joined the channel.
Abhishekkishor (Thu, 12 Mar 2020 19:32:20 GMT):
Has joined the channel.
shiseki (Tue, 17 Mar 2020 05:34:23 GMT):
Has joined the channel.
dexhunter (Mon, 23 Mar 2020 15:08:56 GMT):
Hi, how do I install a package (such as `couchdb`) during CI? Should I modify azure pipline configuration or something else? Thanks in advance!
BrettLogan (Mon, 23 Mar 2020 19:33:01 GMT):
@dexhunter what do you mean, install a package, couchdb isn't a package, its a service. Can you explain what you are trying to do and I'll help you through it
dexhunter (Tue, 24 Mar 2020 03:19:25 GMT):
@BrettLogan Thanks. I want to store some values in the couchdb. I have been able to install couchdb by modifying `azure-pipleline.yml`
```
- script: |
apt update
apt install snapd
snap install couchdb
```
dexhunter (Tue, 24 Mar 2020 03:20:08 GMT):
But the port isn't open, any ideas on how to start the couchdb service? Thanks in advance
vikramsharma13 (Tue, 24 Mar 2020 09:34:24 GMT):
Has joined the channel.
bestbeforetoday (Thu, 26 Mar 2020 09:56:08 GMT):
Rather than installing CouchDB on the build machine, you might consider starting up a Docker container hosting CouchDB, and mapping the CouchDB port from the container to a port on the host machine so it is accessible locally to the build
BrettLogan (Thu, 26 Mar 2020 13:22:13 GMT):
Yea, I pointed them to the service container doc, for anyone else who may be searching for this solution: https://docs.microsoft.com/en-us/azure/devops/pipelines/process/service-containers?view=azure-devops&tabs=yaml#single-job
BrettLogan (Thu, 26 Mar 2020 13:22:29 GMT):
```resources:
containers:
- container: couchdb
image: couchdb
ports:
- 5984:5984
services:
couchdb: couchdb```
BrettLogan (Thu, 26 Mar 2020 13:22:47 GMT):
Much simpler than dealing with modifying the host
dexhunter (Fri, 27 Mar 2020 09:05:43 GMT):
@bestbeforetoday @BrettLogan great, thanks!
dexhunter (Fri, 27 Mar 2020 09:05:43 GMT):
@BrettLogan great thanks!
lehors (Tue, 31 Mar 2020 12:16:36 GMT):
Hi there, I'm seeing a failure which I think is beyond my control: https://dev.azure.com/Hyperledger/Fabric-Samples/_build/results?buildId=11027&view=results
lehors (Tue, 31 Mar 2020 12:16:43 GMT):
anyone knows what's going on?
BrettLogan (Tue, 31 Mar 2020 13:07:54 GMT):
Give me a couple minutes Arnaud, I'll deal with it
BrettLogan (Tue, 31 Mar 2020 13:07:54 GMT):
Give me a couple minutes Arnaud, I'll take a look
BrettLogan (Tue, 31 Mar 2020 13:07:54 GMT):
Give me a couple minutes Arnaud, I'll take a lookk
rjones (Tue, 31 Mar 2020 15:55:20 GMT):
hmm
rjones (Tue, 31 Mar 2020 15:56:24 GMT):
not one of the projects I changed yesterday. Whew!
rjones (Tue, 31 Mar 2020 17:35:17 GMT):
@lehors I re-ran the two failed builds, and they passed.
lehors (Tue, 31 Mar 2020 18:47:45 GMT):
thanks @rjones !
letsblockchain (Mon, 06 Apr 2020 07:57:11 GMT):
Has joined the channel.
matanyahu (Mon, 06 Apr 2020 17:46:37 GMT):
Has left the channel.
metadata (Tue, 14 Apr 2020 20:27:44 GMT):
Has joined the channel.
lanzay (Fri, 24 Apr 2020 03:45:31 GMT):
Has joined the channel.
andrii482 (Mon, 27 Apr 2020 12:33:43 GMT):
Has joined the channel.
Dangana (Mon, 04 May 2020 00:53:09 GMT):
Has joined the channel.
joshtharakan (Fri, 08 May 2020 06:00:45 GMT):
Has joined the channel.
ahmedsajid (Thu, 14 May 2020 18:02:35 GMT):
Hi. Not sure if this is the right group to ask.
I see that there are no baseos being produced for `s390x`? Last I see was `v0.4.18`
ahmedsajid (Thu, 14 May 2020 18:02:46 GMT):
Is that intentional?
rjones (Thu, 14 May 2020 19:08:38 GMT):
@ahmedsajid yes, s390x support was dropped a while ago
ahmedsajid (Thu, 14 May 2020 19:16:30 GMT):
any particular reason why ? :) @rjones ?
BrettLogan (Thu, 14 May 2020 19:49:29 GMT):
We moved from Jenkins to Azure Pipelines (which does not support s390x) and the chief consumer of it was IBM itself
BrettLogan (Thu, 14 May 2020 19:49:53 GMT):
The pieces exist in fabric still, you can pull the code on Z and run `make docker` and build the images yourself
ahmedsajid (Thu, 14 May 2020 19:50:16 GMT):
makes sense. Thanks @BrettLogan
BrettLogan (Thu, 14 May 2020 19:50:25 GMT):
All of the Z and Power targets still exist, for the binaries as well
GmoneyCoder (Thu, 04 Jun 2020 22:32:33 GMT):
Has joined the channel.
govindvb (Fri, 12 Jun 2020 18:07:33 GMT):
Has joined the channel.
davidkhala (Fri, 19 Jun 2020 03:32:13 GMT):
@BrettLogan Hi bret, would you mind helping me re-trigger this again? https://github.com/hyperledger/fabric-sdk-node/pull/256
It seems starting from today all builders suffer some chaincode problems
BrettLogan (Fri, 19 Jun 2020 03:39:26 GMT):
@davidkhala Done. Info have a feature request with Azure DevOps to allow non-admins to trigger CI, buy unfortunately not available today
BrettLogan (Fri, 19 Jun 2020 03:39:26 GMT):
@davidkhala Done. I do have a feature request with Azure DevOps to allow non-admins to trigger CI, buy unfortunately not available today
davidkhala (Fri, 19 Jun 2020 04:10:41 GMT):
indeed, that will unload maintainer's burden.
At least azp should grant right for existing contributor.
davidkhala (Fri, 19 Jun 2020 04:10:41 GMT):
indeed, that will unload maintainer's burden.
At least azp should grant right for existing contributor. Or author of current PR.
davidkhala (Mon, 22 Jun 2020 08:19:30 GMT):
@BrettLogan I find the build problem is still there as https://github.com/hyperledger/fabric-sdk-node/pull/257/checks?check_run_id=794357780
It seems chaincode install fails always with
```
'Error: chaincode install failed with status: 500 - failed to invoke backing implementation of \'InstallChaincode\': could not build chaincode: docker build failed: docker image build failed: docker build failed: Error returned from build: 1 "
```
BrettLogan (Mon, 22 Jun 2020 14:02:16 GMT):
Looks like they identified the issue, in case you havent seen yet. It was a dependency issue
data_prime (Thu, 25 Jun 2020 19:04:40 GMT):
Has joined the channel.
JohnD (Tue, 07 Jul 2020 16:28:53 GMT):
Has joined the channel.
Abhishekkishor (Fri, 10 Jul 2020 05:25:48 GMT):
Hello Guys, Hope you are doing well.
I need your help and guidance in Hyperledger Fabric.
Can you please suggest me good resources on how to generate crypto materials (manualy) using fabric ca in hyperledger?
Also the answers of few questions
My questions are:
1) which testing framework to use for fabric contract api chaincode (node.js) testing?
2) How to handle crypto certificates in production projects? How to generate certificates ? Where & how to store certificates ?
I'll be waiting for your all your response and suggestions.
Thanks & regards,
Abhishek
glad (Fri, 10 Jul 2020 08:10:17 GMT):
Has joined the channel.
rjones (Mon, 27 Jul 2020 19:09:20 GMT):
@BrettLogan check out https://github.com/hyperledger/fabric/pull/1649
rjones (Mon, 27 Jul 2020 19:56:12 GMT):
@dave.enyeart it looks like the CNAME is out there - feel free to add content to `fabric-website`
rjones (Wed, 29 Jul 2020 22:36:11 GMT):
@dave.enyeart I looked at the Semmle database for Fabric, there are a few thousand reports in it, but I'm not sure if that's because of the difference between idiomatic golang over time.
rjones (Wed, 29 Jul 2020 22:36:11 GMT):
@dave.enyeart I looked at the Semmle database for Fabric, there are a few reports in it, but I'm not sure if that's because of the difference between idiomatic golang over time.
rjones (Wed, 29 Jul 2020 22:37:12 GMT):
https://lgtm.com/projects/g/hyperledger/fabric?mode=list
rjones (Wed, 29 Jul 2020 22:37:56 GMT):
If you go here and run a query: https://lgtm.com/projects/g/hyperledger/fabric/queries/?pack=com.lgtm%2Fgo-queries
rjones (Wed, 29 Jul 2020 22:38:50 GMT):
you can see what is available.
davidkhala (Sat, 01 Aug 2020 02:39:18 GMT):
wrong channel, please go to #fabric
jcldnatv (Sat, 22 Aug 2020 17:23:32 GMT):
Has joined the channel.
pvrbharg (Sat, 29 Aug 2020 15:16:10 GMT):
@BrettLogan @dave.enyeart Can you please point me to current end-to-end pipeline process documentation for fabric, fabric-ca, fabric-samples piplelines - as I used to see them in one or two diagrams in the past. I am looking mostly for Linux platforms. Thanks.
rjones (Sat, 29 Aug 2020 16:01:21 GMT):
@pvrbharg the scripts are checked into the repos. I know that isn't a diagram, but the data is there
pvrbharg (Sun, 30 Aug 2020 16:24:27 GMT):
@rjones Thank you!
nkl199 (Tue, 01 Sep 2020 09:55:07 GMT):
Has left the channel.
rjones (Tue, 01 Sep 2020 20:22:43 GMT):
@BrettLogan @dave.enyeart any interest in moving from dockerhub / npm to https://github.blog/2020-09-01-introducing-github-container-registry/ ?
BrettLogan (Tue, 01 Sep 2020 20:35:25 GMT):
Well if that isn't convenient timing. I know we need to do something with the new changes to DockerHub
rjones (Tue, 01 Sep 2020 20:38:58 GMT):
I like that it delegates publishing and all that back to the project, instead of a little island of stuff.
rjones (Tue, 01 Sep 2020 20:39:33 GMT):
in fact, I don't think I need to do anything - projects can just start using it directly
guptasndp10 (Fri, 18 Sep 2020 16:58:20 GMT):
Has joined the channel.
jdo1 (Wed, 23 Sep 2020 06:30:58 GMT):
Has joined the channel.
james604 (Thu, 24 Sep 2020 10:32:02 GMT):
Has joined the channel.
bestbeforetoday (Fri, 23 Oct 2020 10:18:08 GMT):
GitHub repositories are not picking up Azure Pipelines build status as part of their PR checks, so cannot be merged even though the build has completed successfully. See this PR in _fabric-sdk-node_, and _fabric-gateway-java_ and _fabric-sdk-java_ are seeing the same issue:
https://github.com/hyperledger/fabric-sdk-node/pull/364
bestbeforetoday (Fri, 23 Oct 2020 13:22:59 GMT):
@rjones @BrettLogan The issue above seems to be affecting other people too. There are some suggested steps to try to resolve in this Azure DevOps problem report, but I don't have permission to try them: https://developercommunity.visualstudio.com/content/problem/1231036/github-cipr-status-is-not-reported.html
rjones (Fri, 23 Oct 2020 13:35:50 GMT):
interesting
BrettLogan (Fri, 23 Oct 2020 13:36:06 GMT):
I opened a Sev1 with Azure Cloud support as well on this
BrettLogan (Fri, 23 Oct 2020 13:36:24 GMT):
This has been ongoing to about 24 hours
BrettLogan (Fri, 23 Oct 2020 13:36:24 GMT):
This has been ongoing for about 24 hours
BrettLogan (Fri, 23 Oct 2020 13:37:29 GMT):
I dont believe that fix will work for us. In fabric we are getting the individual jobs reporting back successfully but the pipeline itself isn't reporting back
BrettLogan (Fri, 23 Oct 2020 13:37:58 GMT):
Which is the same case for your PR Mark, the jobs reported back, but the pipeline did not
rjones (Fri, 23 Oct 2020 14:05:53 GMT):
yeah, I don't think there is anything we can _do_
troyronda (Wed, 28 Oct 2020 17:46:30 GMT):
Has left the channel.
husnain (Tue, 03 Nov 2020 11:43:30 GMT):
Has joined the channel.
rjones (Tue, 03 Nov 2020 20:16:47 GMT):
@BrettLogan @sykesm https://bugs.chromium.org/p/project-zero/issues/detail?id=2070&can=2&q=&colspec=ID%20Type%20Status%20Priority%20Milestone%20Owner%20Summary&cells=ids FYI
rjones (Tue, 03 Nov 2020 20:17:05 GMT):
Issue 2070: Github: Widespread injection vulnerabilities in Actions
BrettLogan (Tue, 03 Nov 2020 20:27:14 GMT):
Interesting. While we don't use those in Actions, we do use the equivalent ones in AZP, I can't find anything that they might be affected as well (and I also don't think we use it for sensitive variable, but I'd need to confirm)
rjones (Tue, 03 Nov 2020 20:33:24 GMT):
I know there are github actions in use for small things, but I didn't know if there are more hiding
TriumphS (Sun, 06 Dec 2020 22:59:40 GMT):
Has joined the channel.
msteiner (Tue, 08 Dec 2020 20:11:00 GMT):
Has joined the channel.
kevindick_tevora (Tue, 05 Jan 2021 21:59:15 GMT):
Has joined the channel.
Roger (Thu, 07 Jan 2021 07:18:12 GMT):
Has left the channel.
WilsonHUANGWS (Wed, 13 Jan 2021 09:54:45 GMT):
Has joined the channel.
bestbeforetoday (Fri, 15 Jan 2021 10:50:51 GMT):
@rjones @BrettLogan Can either of you give myself and @andrew-coleman permission to be able to restart failed jobs in Azure Pipelines for the *fabric-gateway* project where we are maintainers? https://dev.azure.com/Hyperledger/Fabric-Gateway/_build
BrettLogan (Fri, 15 Jan 2021 13:16:06 GMT):
Let me take care of that, it's stupid how Azure manages it and it's really easy to mess up. IBM has an Azure Active Directory, so our work emails are registered in Acitive Direvtory already, so if you tie it to AZP wrong, you can't reverse it because IBM owns the AD
BrettLogan (Fri, 15 Jan 2021 14:07:37 GMT):
Done
karthiksamaganam (Mon, 01 Feb 2021 14:43:17 GMT):
Has joined the channel.
HelmiTrabelsi (Thu, 04 Mar 2021 09:21:04 GMT):
Has joined the channel.
HelmiTrabelsi (Thu, 04 Mar 2021 09:21:05 GMT):
After doing some changes on the code of hyperledger fabric and building the project, Does anyone know how can use the modified version to run a network.
BrettLogan (Fri, 05 Mar 2021 04:30:51 GMT):
Swap the binary or docker image of an existing network, you can use the `fabric-samples test network` to do this
HelmiTrabelsi (Fri, 05 Mar 2021 10:28:39 GMT):
Thank you @BrettLogan for your response. Sorry I did not understand how to that please can you give more details or any documentation how to do that.
HelmiTrabelsi (Fri, 05 Mar 2021 10:28:39 GMT):
Thank you @BrettLogan for your response. Sorry I did not understand how to do that please can you give more details or any documentation how to do that.
knagware9 (Wed, 10 Mar 2021 08:22:03 GMT):
@HelmiTrabelsi first you need to create docker images and binary with modified code ..Then use this generated binary and docker images to start network. You need to updated docker-compose files too
Amine95 (Mon, 29 Mar 2021 18:02:01 GMT):
Has joined the channel.
shubhamshukla66360 (Thu, 15 Apr 2021 09:52:02 GMT):
Has joined the channel.
RobertBetschinger (Fri, 28 May 2021 10:20:54 GMT):
Has joined the channel.
indranil32 (Tue, 08 Jun 2021 09:15:05 GMT):
Has joined the channel.
Param-S (Thu, 24 Jun 2021 13:41:10 GMT):
Has joined the channel.
Param-S (Thu, 24 Jun 2021 13:46:22 GMT):
@rjones @BrettLogan Can your provide permission to be able to restart the failed unit_test jobs in azure pipeline for fabric.
rjones (Thu, 24 Jun 2021 14:19:28 GMT):
@Param-S I've tried a couple times to give you this permission. I don't know where the disconnect is between Azure and your GitHub account, but I don't have visibility into that.
davidkel (Thu, 24 Jun 2021 14:30:12 GMT):
@rjones I've a simular problem. Brett tried to add my github email but I've not been able to get access either
rjones (Thu, 24 Jun 2021 15:08:52 GMT):
All I can say is, I don't have any visibility into why you can't. All I can do is send an invite to an email
rjones (Thu, 24 Jun 2021 15:10:18 GMT):
@davidkel what email address?
rjones (Thu, 24 Jun 2021 15:11:22 GMT):
Screen Shot 2021-06-24 at 8.10.32 AM.png
rjones (Thu, 24 Jun 2021 15:11:31 GMT):
(with emails)
rjones (Thu, 24 Jun 2021 15:15:01 GMT):
@Param-S perhaps create your account with the email address first, then add GitHub login later?
Param-S (Thu, 24 Jun 2021 15:16:32 GMT):
let me try
dave.enyeart (Thu, 24 Jun 2021 15:17:34 GMT):
For what it is worth, the invite worked for julian
Param-S (Thu, 24 Jun 2021 15:19:01 GMT):
`is already a Microsoft account. Please try a different email address.`
rjones (Thu, 24 Jun 2021 15:19:26 GMT):
@dave.enyeart but it looks like Julian never logged in?
dave.enyeart (Thu, 24 Jun 2021 15:22:45 GMT):
@jcastrence said he logged in successfully (i think)
dave.enyeart (Thu, 24 Jun 2021 15:23:39 GMT):
I give up... why is rocket not recognizing jcastrence? Shouldn't the id be the same as listed here - https://jira.hyperledger.org/secure/ViewProfile.jspa?name=jcastrence
rjones (Thu, 24 Jun 2021 15:24:10 GMT):
sure - that's JIRA, not Azure :)
rjones (Thu, 24 Jun 2021 15:24:53 GMT):
@dave.enyeart do you have access to this page? https://dev.azure.com/Hyperledger/_settings/users
dave.enyeart (Thu, 24 Jun 2021 15:25:54 GMT):
I have view access, but i dont think i can grant privileges
rjones (Thu, 24 Jun 2021 15:26:11 GMT):
which account are you using?
rjones (Thu, 24 Jun 2021 15:26:11 GMT):
~~which account are you using?~~ found it
dave.enyeart (Thu, 24 Jun 2021 15:28:06 GMT):
i see julian's email account, but i thought he was using his github account - https://github.com/jcastrence - i thought everybody should use github rather than direct email access
rjones (Thu, 24 Jun 2021 15:28:20 GMT):
I just gave you the same access Brett has to Azure
dave.enyeart (Thu, 24 Jun 2021 15:28:26 GMT):
thank you
rjones (Thu, 24 Jun 2021 15:28:41 GMT):
Sure. I thought you always had it
rjones (Thu, 24 Jun 2021 15:28:42 GMT):
https://dev.azure.com/Hyperledger/_settings/groups
rjones (Thu, 24 Jun 2021 15:29:41 GMT):
are you able to see the "add users" button here, now? https://dev.azure.com/Hyperledger/_settings/users
dave.enyeart (Thu, 24 Jun 2021 15:30:06 GMT):
now i see it :)
rjones (Thu, 24 Jun 2021 15:31:03 GMT):
awesome. In the future - if you don't have permissions in Azure - just ask; I want you to have all the power you want over there :)
dave.enyeart (Thu, 24 Jun 2021 15:31:46 GMT):
ok, i just added jcastrence (github id)
dave.enyeart (Thu, 24 Jun 2021 15:33:08 GMT):
and now I've added Param-S (github id)
dave.enyeart (Thu, 24 Jun 2021 15:33:23 GMT):
@Param-S try again
Param-S (Thu, 24 Jun 2021 15:35:01 GMT):
ok
dave.enyeart (Thu, 24 Jun 2021 15:35:30 GMT):
@davidkel And I've added davidkel (github id)
dave.enyeart (Thu, 24 Jun 2021 15:35:37 GMT):
you guys can try to access https://dev.azure.com/Hyperledger/ now
rjones (Thu, 24 Jun 2021 15:37:44 GMT):
@dave.enyeart I signed up all of our orgs for the GitHub issues beta - should be a nicer JIRA replacement
dave.enyeart (Thu, 24 Jun 2021 15:38:28 GMT):
good. we can give it a look (is it really still in beta?)
dave.enyeart (Thu, 24 Jun 2021 15:38:40 GMT):
or is there just some new functions in beta?
rjones (Thu, 24 Jun 2021 15:39:10 GMT):
This is the beta: https://github.com/features/issues none of our orgs are in, yet
dave.enyeart (Thu, 24 Jun 2021 15:40:56 GMT):
I guess there is a difference between the 'old' GitHub issues, e.g. https://github.com/hyperledger/fabric-test/issues/ and this new GitHub Issues beta?
Param-S (Thu, 24 Jun 2021 15:41:39 GMT):
@dave.enyeart , now, I am able to see the hyperledger resources
rjones (Thu, 24 Jun 2021 15:41:48 GMT):
yes, it's more like JIRA
dave.enyeart (Thu, 24 Jun 2021 15:42:04 GMT):
cool, so let me know when we can start trying it
dave.enyeart (Thu, 24 Jun 2021 15:42:43 GMT):
Ok, so the access issue is resolved... I guess the lesson learned is to always use GitHub id
rjones (Thu, 24 Jun 2021 15:43:08 GMT):
which I never thought would be an issue. I wonder if this is due to an edge case.
rjones (Thu, 24 Jun 2021 15:43:21 GMT):
It used to be adding by GitHub ID was hard to make work
dave.enyeart (Thu, 24 Jun 2021 15:44:15 GMT):
it is a little difficult for IBMers because you have to add another email to your github account first, but that is what we've been advising everybody to do (with success)
rjones (Thu, 24 Jun 2021 15:47:01 GMT):
well, whatever I can do to make it easier.
rjones (Thu, 24 Jun 2021 15:47:14 GMT):
And help moving over to GitHub Actions :)
jcastrence (Thu, 24 Jun 2021 16:10:39 GMT):
Has joined the channel.
jcastrence (Thu, 24 Jun 2021 16:10:40 GMT):
@dave.enyeart @rjones I tried logging into `https://dev.azure.com/Hyperledger/` through my GitHub and it still says I don't have access
jcastrence (Thu, 24 Jun 2021 16:20:54 GMT):
Clipboard - June 24, 2021 12:20 PM
jcastrence (Thu, 24 Jun 2021 16:21:17 GMT):
Not sure if this is of any help, this is the error page I get when trying to sign in through GitHub
dave.enyeart (Thu, 24 Jun 2021 16:24:18 GMT):
Can you login to https://dev.azure.com ? Does it show your github avatar?
dave.enyeart (Thu, 24 Jun 2021 16:24:18 GMT):
Can you login to https://dev.azure.com ? Does it show your github avatar in top-right?
davidkel (Thu, 24 Jun 2021 16:24:34 GMT):
@dave.enyeart Thanks Dave, whatever you did has got me further now. I can actually see the page with hyperledger resources
dave.enyeart (Thu, 24 Jun 2021 16:24:45 GMT):
ok, so 2 out of 3
jcastrence (Thu, 24 Jun 2021 16:27:57 GMT):
I signed into the link you just sent through Github and it isn't showing my Github avatar and it's also displaying my regular email
jcastrence (Thu, 24 Jun 2021 16:29:16 GMT):
And it's saying it's my Microsoft account
jcastrence (Thu, 24 Jun 2021 16:31:34 GMT):
My Github account is linked to my Microsoft account apparently so whenever I sign in it automatically is my Microsoft account
jcastrence (Thu, 24 Jun 2021 16:34:36 GMT):
On dev.azure.com/Hyperledger however it seems to be using my Github profile
jcastrence (Thu, 24 Jun 2021 16:34:42 GMT):
Clipboard - June 24, 2021 12:34 PM
dave.enyeart (Thu, 24 Jun 2021 17:00:59 GMT):
and it says you are a member of dev.azure.com/Hyperledger
jcastrence (Mon, 28 Jun 2021 12:40:18 GMT):
Hey @rjones do you have an idea of why DevOps is still not giving me permission on HLF?
rjones (Mon, 28 Jun 2021 15:18:24 GMT):
@jcastrence no I do not - I would need to defer to @dave.enyeart
jcastrence (Mon, 28 Jun 2021 21:03:48 GMT):
Ok, he's currently on vacation so we'll let him know next week
mirshahzad (Sat, 24 Jul 2021 16:36:20 GMT):
Has joined the channel.
Rajatsharma (Wed, 18 Aug 2021 07:22:35 GMT):
Has joined the channel.
robinrob (Thu, 09 Sep 2021 21:52:09 GMT):
Has joined the channel.
indranil32 (Thu, 16 Sep 2021 10:21:08 GMT):
The build for a PR of mine is failing - https://dev.azure.com/Hyperledger/Fabric-Samples/_build/results?buildId=41021&view=results
https://github.com/hyperledger/fabric-samples/pull/492
Doesn't look like the errors are related to my checi-ns
bardia (Fri, 01 Oct 2021 10:12:05 GMT):
Has joined the channel.
bardia (Mon, 08 Nov 2021 06:24:40 GMT):
How can I get the *password* *attempts* problem in golang?
When I login 10 times unsuccessfully, I can no longer login 11 times with the correct specifications
Gives the following message
failed to enroll user: enroll failed: enroll failed: Response from server: Error Code: 73 - Incorrect password entered 10 times, max incorrect password limit of 10 reached
hegde.rahul (Wed, 17 Nov 2021 01:23:56 GMT):
Has joined the channel.
hegde.rahul (Wed, 17 Nov 2021 01:23:57 GMT):
hello friends, this is question on the docker base image that is used to build fabric images. we see using alpine as base image. Can we not deploy the statically linked peer or orderer binary directly on scratch base image. This would reduce the image size further and prevent attack vector.
bardia (Tue, 07 Dec 2021 06:05:26 GMT):
How can I increase the number of deploy in the chain code version?
rjones (Tue, 07 Dec 2021 17:36:31 GMT):
@bardia this channel is really more for CI discussion of the Fabric project - I think the mailing list, or #fabric , is probably a better place to ask
bardia (Fri, 17 Dec 2021 06:12:07 GMT):
How to change affiliation name on ca-server HLF?
bardia (Thu, 20 Jan 2022 08:30:55 GMT):
Has left the channel.
