From tnakane@mrc-lmb.cam.ac.uk Fri Jul 27 03:52:25 2018 From: Takanori Nakane To: cctbxbb@phenix-online.org Subject: [cctbxbb] How does Jenkins work? Date: Fri, 27 Jul 2018 11:52:21 +0100 Message-ID: <8e403bf61931e630ac4e3cde7f5bb455.squirrel@mail.mrc-lmb.cam.ac.uk> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2137878035070322418==" --===============2137878035070322418== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, Why does Jenkins still run tests on my old commits on my deleted (dxtbx-sacla) branch? The test failure is probably caused by my commit dc17165 but I committed a fix 5c7416b and confirmed that it passes the tests. So I merged my topic branch to master and deleted the branch from GitHub. I know how git works but I am new to the practice in the cctbx repository (like using rebase instead of merge). If I am doing something wrong, could you please point it to me? Best regards, Takanori Nakane > #F59400; color: #FFF; border-radius: 0.5em; margin-bottom: 0.5em">

style=3D"margin: 0.5em 1.25em 0.5em 0.7em; font-weight: bold; font-family: > sans-serif; font-size: 110%"> href=3D"http://jenkins.diamond.ac.uk:8080/job/cctbx_branch_tests/145/" > style=3D"color:#FFF; text-decoration: none">Build CCTBX Branch Tests is > unstable

background-color: #F59400; color: #FFF; border-radius: 0.5em; > margin-bottom: 0.5em">

font-weight: bold; font-family: sans-serif; font-size: 110%"> href=3D"http://jenkins.diamond.ac.uk:8080/job/cctbx_branch_tests/145/testRe= port" > style=3D"color:#FFF; text-decoration: none">3 out of 940 tests failed (132 > skipped)

2em">

3 tests failed.
> FAILED:
> dxtbx.build_dials.modules.cctbx_project.dxtbx.tests.test_regression_images.=
test_no_multiple_format_understanding[SACLA_MPCCD_Cheetah/run266702-0-subset.=
h5]
> Error Message:
> exit code 1
> Stack Trace:
> FAILED:
> dxtbx.build_dials.modules.cctbx_project.dxtbx.tests.test_regression_images.=
test_no_multiple_format_understanding[putative_imgCIF_HDF5_mapping/minicbf.h5]
> Error Message:
> exit code 1
> Stack Trace:
> FAILED:
> dxtbx.build_dials.modules.cctbx_project.dxtbx.tests.test_regression_images.=
test_no_multiple_format_understanding[putative_imgCIF_HDF5_mapping/X4_wide_M1=
S4_1.nxs]
> Error Message:
> exit code 1
> Stack Trace:
>

#F59400; color: #FFF; border-radius: 0.5em; margin-bottom: 0.5em">

style=3D"margin: 0.5em 1.25em 0.5em 0.7em; font-weight: bold; font-family: > sans-serif; font-size: 110%">Changes since the last successful > build

2em">

#F59400; color:#fff">

145

No changes >

#000; border-radius: 0.5em; margin-bottom: 0.5em">

0.5em 1.25em 0.5em 0.7em; font-weight: bold; font-family: sans-serif; > font-size: 110%">Build environment

0.5em 0 1em 2em">

style=3D"font-size:130%"> [ cctbx 71a4ab94a > 2018-07-25 06:47:08 +0900 style=3D"font-size:130%"> | DIALS regression > 1924, PHENIX regression 4419, DLS > Jenkins scripts 8de8b58 2018-07-04 23:29:22 +0100 style=3D"font-size:130%"> ]

style=3D"color:#CCC;font-size:80%">mail template revision > 2487 >
>

To unsubscribe from the CCTBX-COMMIT list, click the > following link:
> href=3D"https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=3DCCTBX-COMMIT&A= =3D1" > target=3D"_blank">https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=3DCCTB= X-COMMIT&A=3D1 >

--===============2137878035070322418==-- From Graeme.Winter@diamond.ac.uk Fri Jul 27 07:42:14 2018 From: "Graeme.Winter@Diamond.ac.uk" To: cctbxbb@phenix-online.org Subject: Re: [cctbxbb] How does Jenkins work? Date: Fri, 27 Jul 2018 14:42:10 +0000 Message-ID: In-Reply-To: <8e403bf61931e630ac4e3cde7f5bb455.squirrel@mail.mrc-lmb.cam.ac.uk> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3882228318312749557==" --===============3882228318312749557== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Dear Takanori Both of our resident Git gurus are en route to Lewiston, ME so unlikely to pi= ck this one up for a day or two I would expect words like upstream synchronisation or similar will appear in = the answer, but I would quite frankly hold tight & ignore the Jenkins emails = - I was surprised to see it too, as I recall it being fixed, but figured that= there was something odd happening. Sorry I can=E2=80=99t be more help, best wishes Graeme > On 27 Jul 2018, at 11:52, Takanori Nakane wro= te: >=20 > Hi, >=20 > Why does Jenkins still run tests on my old commits on my deleted > (dxtbx-sacla) branch? The test failure is probably caused by my > commit dc17165 but I committed a fix 5c7416b and confirmed that > it passes the tests. So I merged my topic branch to master and > deleted the branch from GitHub. >=20 > I know how git works but I am new to the practice in the cctbx repository > (like using rebase instead of merge). If I am doing something wrong, > could you please point it to me? >=20 > Best regards, >=20 > Takanori Nakane >=20 >> > #F59400; color: #FFF; border-radius: 0.5em; margin-bottom: > 0.5em">

> style=3D"margin: 0.5em 1.25em 0.5em 0.7em; font-weight: bold; font-family: >> sans-serif; font-size: 110%">> href=3D"http://jenkins.diamond.ac.uk:8080/job/cctbx_branch_tests/145/" >> style=3D"color:#FFF; text-decoration: none">Build CCTBX Branch Tests > is >> unstable

> background-color: #F59400; color: #FFF; border-radius: 0.5em; >> margin-bottom: 0.5em">

> font-weight: bold; font-family: sans-serif; font-size: 110%">> href=3D"http://jenkins.diamond.ac.uk:8080/job/cctbx_branch_tests/145/testR= eport" >> style=3D"color:#FFF; text-decoration: none">3 out of 940 tests failed (132 >> skipped)

> 2em">

3 tests failed.
>> FAILED:
>> dxtbx.build_dials.modules.cctbx_project.dxtbx.tests.test_regression_images=
.test_no_multiple_format_understanding[SACLA_MPCCD_Cheetah/run266702-0-subset=
.h5]
>> Error Message:
>> exit code 1
>> Stack Trace:
>> FAILED:
>> dxtbx.build_dials.modules.cctbx_project.dxtbx.tests.test_regression_images=
.test_no_multiple_format_understanding[putative_imgCIF_HDF5_mapping/minicbf.h=
5]
>> Error Message:
>> exit code 1
>> Stack Trace:
>> FAILED:
>> dxtbx.build_dials.modules.cctbx_project.dxtbx.tests.test_regression_images=
.test_no_multiple_format_understanding[putative_imgCIF_HDF5_mapping/X4_wide_M=
1S4_1.nxs]
>> Error Message:
>> exit code 1
>> Stack Trace:
>>

> #F59400; color: #FFF; border-radius: 0.5em; margin-bottom: > 0.5em">

> style=3D"margin: 0.5em 1.25em 0.5em 0.7em; font-weight: bold; font-family: >> sans-serif; font-size: 110%">Changes since the last successful >> build

> 2em">

> #F59400; color:#fff">

145

No changes >>

color: >> #000; border-radius: 0.5em; margin-bottom: 0.5em">

> 0.5em 1.25em 0.5em 0.7em; font-weight: bold; font-family: sans-serif; >> font-size: 110%">Build environment

style=3D"margin: >> 0.5em 0 1em 2em">

> style=3D"font-size:130%"> [ cctbx 71a4ab94a >> 2018-07-25 06:47:08 +0900> style=3D"font-size:130%"> | DIALS regression >> 1924, PHENIX regression 4419, DLS >> Jenkins scripts 8de8b58 2018-07-04 23:29:22 +0100> style=3D"font-size:130%"> ]

> style=3D"color:#CCC;font-size:80%">mail template revision >> 2487 >>
>>

To unsubscribe from the CCTBX-COMMIT list, click the >> following link:
>> > href=3D"https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=3DCCTBX-COMMIT&= A=3D1" >> target=3D"_blank">https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=3DCCT= BX-COMMIT&A=3D1 >>

>=20 >=20 >=20 >=20 > _______________________________________________ > cctbxbb mailing list > cctbxbb(a)phenix-online.org > http://phenix-online.org/mailman/listinfo/cctbxbb --=20 This e-mail and any attachments may contain confidential, copyright and or pr= ivileged material, and are for the use of the intended addressee only. If you= are not the intended addressee or an authorised recipient of the addressee p= lease notify us of receipt by returning the e-mail and do not use, copy, reta= in, distribute or disclose the information in or attached to the e-mail. Any opinions expressed within this e-mail are those of the individual and not= necessarily of Diamond Light Source Ltd.=20 Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachment= s are free from viruses and we cannot accept liability for any damage which y= ou may sustain as a result of software viruses which may be transmitted in or= with the message. Diamond Light Source Limited (company no. 4375679). Registered in England and= Wales with its registered office at Diamond House, Harwell Science and Innov= ation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom --===============3882228318312749557==-- From tnakane@mrc-lmb.cam.ac.uk Fri Jul 27 09:18:50 2018 From: Takanori Nakane To: cctbxbb@phenix-online.org Subject: Re: [cctbxbb] How does Jenkins work? Date: Fri, 27 Jul 2018 17:18:47 +0100 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============9040419888467245966==" --===============9040419888467245966== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Graeme, Thank you very much for your advise. I'll wait and see if Jenkins still complains. Best regards, Takanori Nakane > Dear Takanori > > Both of our resident Git gurus are en route to Lewiston, ME so unlikely to > pick this one up for a day or two > > I would expect words like upstream synchronisation or similar will appear > in the answer, but I would quite frankly hold tight & ignore the Jenkins > emails - I was surprised to see it too, as I recall it being fixed, but > figured that there was something odd happening. > > Sorry I can=E2=80=99t be more help, best wishes Graeme > >> On 27 Jul 2018, at 11:52, Takanori Nakane >> wrote: >> >> Hi, >> >> Why does Jenkins still run tests on my old commits on my deleted >> (dxtbx-sacla) branch? The test failure is probably caused by my >> commit dc17165 but I committed a fix 5c7416b and confirmed that >> it passes the tests. So I merged my topic branch to master and >> deleted the branch from GitHub. >> >> I know how git works but I am new to the practice in the cctbx >> repository >> (like using rebase instead of merge). If I am doing something wrong, >> could you please point it to me? >> >> Best regards, >> >> Takanori Nakane >> >>> >> #F59400; color: #FFF; border-radius: 0.5em; margin-bottom: >> 0.5em">

>> style=3D"margin: 0.5em 1.25em 0.5em 0.7em; font-weight: bold; >>> font-family: >>> sans-serif; font-size: 110%">>> href=3D"http://jenkins.diamond.ac.uk:8080/job/cctbx_branch_tests/145/" >>> style=3D"color:#FFF; text-decoration: none">Build CCTBX Branch Tests >> is >>> unstable

>> background-color: #F59400; color: #FFF; border-radius: 0.5em; >>> margin-bottom: 0.5em">

>> font-weight: bold; font-family: sans-serif; font-size: 110%">>> href=3D"http://jenkins.diamond.ac.uk:8080/job/cctbx_branch_tests/145/test= Report" >>> style=3D"color:#FFF; text-decoration: none">3 out of 940 tests failed >>> (132 >>> skipped)

>> 2em">

3 tests failed.
>>> FAILED:
>>> dxtbx.build_dials.modules.cctbx_project.dxtbx.tests.test_regression_image=
s.test_no_multiple_format_understanding[SACLA_MPCCD_Cheetah/run266702-0-subse=
t.h5]
>>> Error Message:
>>> exit code 1
>>> Stack Trace:
>>> FAILED:
>>> dxtbx.build_dials.modules.cctbx_project.dxtbx.tests.test_regression_image=
s.test_no_multiple_format_understanding[putative_imgCIF_HDF5_mapping/minicbf.=
h5]
>>> Error Message:
>>> exit code 1
>>> Stack Trace:
>>> FAILED:
>>> dxtbx.build_dials.modules.cctbx_project.dxtbx.tests.test_regression_image=
s.test_no_multiple_format_understanding[putative_imgCIF_HDF5_mapping/X4_wide_=
M1S4_1.nxs]
>>> Error Message:
>>> exit code 1
>>> Stack Trace:
>>>

>> #F59400; color: #FFF; border-radius: 0.5em; margin-bottom: >> 0.5em">

>> style=3D"margin: 0.5em 1.25em 0.5em 0.7em; font-weight: bold; >>> font-family: >>> sans-serif; font-size: 110%">Changes since the last successful >>> build

>> 2em">

>> #F59400; color:#fff">

145

No changes >>>

> color: >>> #000; border-radius: 0.5em; margin-bottom: 0.5em">

>> style=3D"margin: >>> 0.5em 1.25em 0.5em 0.7em; font-weight: bold; font-family: sans-serif; >>> font-size: 110%">Build environment

> style=3D"margin: >>> 0.5em 0 1em 2em">

>> style=3D"font-size:130%"> [ cctbx 71a4ab94a >>> 2018-07-25 06:47:08 +0900>> style=3D"font-size:130%"> | DIALS regression >>> 1924, PHENIX regression 4419, DLS >>> Jenkins scripts 8de8b58 2018-07-04 23:29:22 +0100>> style=3D"font-size:130%"> ]

>> style=3D"color:#CCC;font-size:80%">mail template revision >>> 2487 >>>
>>>

>>>

To unsubscribe from the CCTBX-COMMIT list, click the >>> following link:
>>> >> href=3D"https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=3DCCTBX-COMMIT= &A=3D1" >>> target=3D"_blank">https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=3DCC= TBX-COMMIT&A=3D1 >>>

>> >> >> >> >> _______________________________________________ >> cctbxbb mailing list >> cctbxbb(a)phenix-online.org >> http://phenix-online.org/mailman/listinfo/cctbxbb > > > -- > This e-mail and any attachments may contain confidential, copyright and or > privileged material, and are for the use of the intended addressee only. > If you are not the intended addressee or an authorised recipient of the > addressee please notify us of receipt by returning the e-mail and do not > use, copy, retain, distribute or disclose the information in or attached > to the e-mail. > Any opinions expressed within this e-mail are those of the individual and > not necessarily of Diamond Light Source Ltd. > Diamond Light Source Ltd. cannot guarantee that this e-mail or any > attachments are free from viruses and we cannot accept liability for any > damage which you may sustain as a result of software viruses which may be > transmitted in or with the message. > Diamond Light Source Limited (company no. 4375679). Registered in England > and Wales with its registered office at Diamond House, Harwell Science and > Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom > > _______________________________________________ > cctbxbb mailing list > cctbxbb(a)phenix-online.org > http://phenix-online.org/mailman/listinfo/cctbxbb > --===============9040419888467245966==-- From markus.gerstel@diamond.ac.uk Fri Jul 27 12:41:25 2018 From: markus.gerstel@diamond.ac.uk To: cctbxbb@phenix-online.org Subject: Re: [cctbxbb] How does Jenkins work? Date: Fri, 27 Jul 2018 19:41:14 +0000 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5820756618091332143==" --===============5820756618091332143== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Takanori, Still in the plane, but thanks to modern technology can look into this.... The commit ID that triggered Jenkins is shown right at the bottom of the Jenk= ins mails. The latest was 71a4ab94a with an associated date of 2018-07-25 06:47:08 +0900 The branch has since been deleted, and that commit did not end up in any othe= r remaining branch, so I can't find it in my personal repository. But I could= still find it in the repository we use for notification emails. If you run $ git log -3 71a4ab94a you should see this: commit 71a4ab94a7910256c178baf2e275fd8165cd3973 Author: Takanori Nakane Date: Wed Jul 25 06:47:08 2018 +0900 dxtbx class for Rayonix MX300-HS converted into HDF5 by Cheetah pipeline = at SACLA commit 49a25028f28de33a42defabdcf055085547882d3 Author: Takanori Nakane Date: Wed Jul 25 06:44:45 2018 +0900 dxtbx class for SACLA MPCCD: supported Phase III MPCCD and compact MPCCD commit e380927225b256a3096be2ee57aecc2a844a6b10 Author: Billy K. Poon Date: Tue Jul 24 09:19:26 2018 -0700 Table one: add options for twinning So those two commits of yours were based on Billy's "Table one" commit. You c= an still find Billy's commit with that exact ID on https://github.com/cctbx/c= ctbx_project/commits/master but your commits are now separated from his. So my best guess as to what happ= ened is * you originally made your commits on top of Billy's in a branch named dlstbx= -sacla * you either * pushed the dlstbx-sacla branch to Github before making your 3rd commit, or * rebased the dlstbx-sacla branch onto master before making your 3rd commit= on master only, then inadvertently pushed both branches * at which point Jenkins was triggered on dlstbx-sacla, seeing only the 2nd c= ommit, and * Jenkins fails As Graeme implied though, there is no "penalty" associated with Jenkins faili= ng on branches other than master. Generally nobody (apart from yourself) will expect other branches to be stabl= e, and they are not relevant for releases etc. So like Graeme, I ignore any failure mails of branches that I am not personal= ly involved in. If a branch is part of a pull request and is supposed to be merged into maste= r then that may be different, as at which point tests should succeed. But the= n the latest (and relevant) Jenkins output will be prominently visible in the= Github pull request itself. -Markus=20 -----Original Message----- From: cctbxbb-bounces(a)phenix-online.org On Behalf Of Takanori Nakane Sent: 27 July 2018 17:19 To: cctbx mailing list Subject: Re: [cctbxbb] How does Jenkins work? Hi Graeme, Thank you very much for your advise. I'll wait and see if Jenkins still complains. Best regards, Takanori Nakane > Dear Takanori > > Both of our resident Git gurus are en route to Lewiston, ME so=20 > unlikely to pick this one up for a day or two > > I would expect words like upstream synchronisation or similar will=20 > appear in the answer, but I would quite frankly hold tight & ignore=20 > the Jenkins emails - I was surprised to see it too, as I recall it=20 > being fixed, but figured that there was something odd happening. > > Sorry I can't be more help, best wishes Graeme > >> On 27 Jul 2018, at 11:52, Takanori Nakane >> wrote: >> >> Hi, >> >> Why does Jenkins still run tests on my old commits on my deleted >> (dxtbx-sacla) branch? The test failure is probably caused by my=20 >> commit dc17165 but I committed a fix 5c7416b and confirmed that it=20 >> passes the tests. So I merged my topic branch to master and deleted=20 >> the branch from GitHub. >> >> I know how git works but I am new to the practice in the cctbx=20 >> repository (like using rebase instead of merge). If I am doing=20 >> something wrong, could you please point it to me? >> >> Best regards, >> >> Takanori Nakane >> >>> >> #F59400; color: #FFF; border-radius: 0.5em; margin-bottom: >> 0.5em">

>> background-color: #F59400; color: #FFF; border-radius: 0.5em; >>> margin-bottom: 0.5em">

>> 0.7em; >>> font-weight: bold; font-family: sans-serif; font-size: 110%">>> href=3D"http://jenkins.diamond.ac.uk:8080/job/cctbx_branch_tests/145/test= Report" >>> style=3D"color:#FFF; text-decoration: none">3 out of 940 tests failed >>> (132 >>> skipped)

>> 2em">

3 tests failed.
>>> FAILED:
>>> dxtbx.build_dials.modules.cctbx_project.dxtbx.tests.test_regression_
>>> images.test_no_multiple_format_understanding[SACLA_MPCCD_Cheetah/run
>>> 266702-0-subset.h5]
>>> Error Message:
>>> exit code 1
>>> Stack Trace:
>>> FAILED:
>>> dxtbx.build_dials.modules.cctbx_project.dxtbx.tests.test_regression_
>>> images.test_no_multiple_format_understanding[putative_imgCIF_HDF5_ma
>>> pping/minicbf.h5]
>>> Error Message:
>>> exit code 1
>>> Stack Trace:
>>> FAILED:
>>> dxtbx.build_dials.modules.cctbx_project.dxtbx.tests.test_regression_
>>> images.test_no_multiple_format_understanding[putative_imgCIF_HDF5_ma
>>> pping/X4_wide_M1S4_1.nxs]
>>> Error Message:
>>> exit code 1
>>> Stack Trace:
>>>

>> #F59400; color: #FFF; border-radius: 0.5em; margin-bottom: >> 0.5em">

>> style=3D"margin: 0.5em 1.25em 0.5em 0.7em; font-weight: bold; >>> font-family: >>> sans-serif; font-size: 110%">Changes since the last successful=20 >>> build

>> 2em">

>> #F59400; color:#fff">

145

No=20 >>> changes

>> background-color: #CCC; >> color: >>> #000; border-radius: 0.5em; margin-bottom: 0.5em">

>> style=3D"margin: >>> 0.5em 1.25em 0.5em 0.7em; font-weight: bold; font-family:=20 >>> sans-serif; >>> font-size: 110%">Build environment

> style=3D"margin: >>> 0.5em 0 1em 2em">

>> style=3D"font-size:130%"> [ cctbx 71a4ab94a >>> 2018-07-25 06:47:08 +0900>> style=3D"font-size:130%"> | DIALS regression=20 >>> 1924, PHENIX regression 4419, DLS=20 >>> Jenkins scripts 8de8b58 2018-07-04 23:29:22=20 >>> +0100>> style=3D"font-size:130%"> ]

>> style=3D"color:#CCC;font-size:80%">mail template revision=20 >>> 2487

To unsubscribe=20 >>> from the CCTBX-COMMIT list, click the following link:
>> href=3D"https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=3DCCTBX-COMMIT= &A=3D1" >>> target=3D"_blank">https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=3DC >>> CTBX-COMMIT&A=3D1 >>>

>> >> >> >> >> _______________________________________________ >> cctbxbb mailing list >> cctbxbb(a)phenix-online.org >> http://phenix-online.org/mailman/listinfo/cctbxbb > > > -- > This e-mail and any attachments may contain confidential, copyright=20 > and or privileged material, and are for the use of the intended addressee o= nly. > If you are not the intended addressee or an authorised recipient of=20 > the addressee please notify us of receipt by returning the e-mail and=20 > do not use, copy, retain, distribute or disclose the information in or=20 > attached to the e-mail. > Any opinions expressed within this e-mail are those of the individual=20 > and not necessarily of Diamond Light Source Ltd. > Diamond Light Source Ltd. cannot guarantee that this e-mail or any=20 > attachments are free from viruses and we cannot accept liability for=20 > any damage which you may sustain as a result of software viruses which=20 > may be transmitted in or with the message. > Diamond Light Source Limited (company no. 4375679). Registered in=20 > England and Wales with its registered office at Diamond House, Harwell=20 > Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United=20 > Kingdom > > _______________________________________________ > cctbxbb mailing list > cctbxbb(a)phenix-online.org > http://phenix-online.org/mailman/listinfo/cctbxbb > _______________________________________________ cctbxbb mailing list cctbxbb(a)phenix-online.org http://phenix-online.org/mailman/listinfo/cctbxbb --=20 This e-mail and any attachments may contain confidential, copyright and or pr= ivileged material, and are for the use of the intended addressee only. If you= are not the intended addressee or an authorised recipient of the addressee p= lease notify us of receipt by returning the e-mail and do not use, copy, reta= in, distribute or disclose the information in or attached to the e-mail. Any opinions expressed within this e-mail are those of the individual and not= necessarily of Diamond Light Source Ltd.=20 Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachment= s are free from viruses and we cannot accept liability for any damage which y= ou may sustain as a result of software viruses which may be transmitted in or= with the message. Diamond Light Source Limited (company no. 4375679). Registered in England and= Wales with its registered office at Diamond House, Harwell Science and Innov= ation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom --===============5820756618091332143==-- From ndevenish@gmail.com Fri Jul 27 12:42:13 2018 From: Nicholas Devenish To: cctbxbb@phenix-online.org Subject: Re: [cctbxbb] How does Jenkins work? Date: Fri, 27 Jul 2018 20:42:10 +0100 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6693373875389992701==" --===============6693373875389992701== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Takanori, This appears to have been a configuration bug. I've made a change that should prevent this from happening again - added the behaviour "Prune stale remote-tracking branches". Looks like when trying to compare failed, it defaulted to "something must have changed, so I shall run the build", or some similar behaviour. Thanks for the report! Nick On Fri, Jul 27, 2018 at 5:18 PM, Takanori Nakane wrote: > Hi Graeme, > > Thank you very much for your advise. > I'll wait and see if Jenkins still complains. > > Best regards, > > Takanori Nakane > >> Dear Takanori >> >> Both of our resident Git gurus are en route to Lewiston, ME so unlikely to >> pick this one up for a day or two >> >> I would expect words like upstream synchronisation or similar will appear >> in the answer, but I would quite frankly hold tight & ignore the Jenkins >> emails - I was surprised to see it too, as I recall it being fixed, but >> figured that there was something odd happening. >> >> Sorry I can=E2=80=99t be more help, best wishes Graeme >> >>> On 27 Jul 2018, at 11:52, Takanori Nakane >>> wrote: >>> >>> Hi, >>> >>> Why does Jenkins still run tests on my old commits on my deleted >>> (dxtbx-sacla) branch? The test failure is probably caused by my >>> commit dc17165 but I committed a fix 5c7416b and confirmed that >>> it passes the tests. So I merged my topic branch to master and >>> deleted the branch from GitHub. >>> >>> I know how git works but I am new to the practice in the cctbx >>> repository >>> (like using rebase instead of merge). If I am doing something wrong, >>> could you please point it to me? >>> >>> Best regards, >>> >>> Takanori Nakane >>> >>>> >>> #F59400; color: #FFF; border-radius: 0.5em; margin-bottom: >>> 0.5em">

>>> style=3D"margin: 0.5em 1.25em 0.5em 0.7em; font-weight: bold; >>>> font-family: >>>> sans-serif; font-size: 110%">>>> href=3D"http://jenkins.diamond.ac.uk:8080/job/cctbx_branch_tests/145/" >>>> style=3D"color:#FFF; text-decoration: none">Build CCTBX Branch Tests >>> is >>>> unstable

>>> background-color: #F59400; color: #FFF; border-radius: 0.5em; >>>> margin-bottom: 0.5em">

>>> font-weight: bold; font-family: sans-serif; font-size: 110%">>>> href=3D"http://jenkins.diamond.ac.uk:8080/job/cctbx_branch_tests/145/tes= tReport" >>>> style=3D"color:#FFF; text-decoration: none">3 out of 940 tests failed >>>> (132 >>>> skipped)

>>> 2em">

3 tests failed.
>>>> FAILED:
>>>> dxtbx.build_dials.modules.cctbx_project.dxtbx.tests.test_regression_imag=
es.test_no_multiple_format_understanding[SACLA_MPCCD_Cheetah/run266702-0-subs=
et.h5]
>>>> Error Message:
>>>> exit code 1
>>>> Stack Trace:
>>>> FAILED:
>>>> dxtbx.build_dials.modules.cctbx_project.dxtbx.tests.test_regression_imag=
es.test_no_multiple_format_understanding[putative_imgCIF_HDF5_mapping/minicbf=
.h5]
>>>> Error Message:
>>>> exit code 1
>>>> Stack Trace:
>>>> FAILED:
>>>> dxtbx.build_dials.modules.cctbx_project.dxtbx.tests.test_regression_imag=
es.test_no_multiple_format_understanding[putative_imgCIF_HDF5_mapping/X4_wide=
_M1S4_1.nxs]
>>>> Error Message:
>>>> exit code 1
>>>> Stack Trace:
>>>>

>>> #F59400; color: #FFF; border-radius: 0.5em; margin-bottom: >>> 0.5em">

>>> style=3D"margin: 0.5em 1.25em 0.5em 0.7em; font-weight: bold; >>>> font-family: >>>> sans-serif; font-size: 110%">Changes since the last successful >>>> build

>>> 2em">

>>> #F59400; color:#fff">

145

No changes >>>>

>> color: >>>> #000; border-radius: 0.5em; margin-bottom: 0.5em">

>>> style=3D"margin: >>>> 0.5em 1.25em 0.5em 0.7em; font-weight: bold; font-family: sans-serif; >>>> font-size: 110%">Build environment

>> style=3D"margin: >>>> 0.5em 0 1em 2em">

>>> style=3D"font-size:130%"> [ cctbx 71a4ab94a >>>> 2018-07-25 06:47:08 +0900>>> style=3D"font-size:130%"> | DIALS regression >>>> 1924, PHENIX regression 4419, DLS >>>> Jenkins scripts 8de8b58 2018-07-04 23:29:22 +0100>>> style=3D"font-size:130%"> ]

>>> style=3D"color:#CCC;font-size:80%">mail template revision >>>> 2487 >>>>
>>>>

>>>>

To unsubscribe from the CCTBX-COMMIT list, click the >>>> following link:
>>>> >>> href=3D"https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=3DCCTBX-COMMI= T&A=3D1" >>>> target=3D"_blank">https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=3DC= CTBX-COMMIT&A=3D1 >>>>

>>> >>> >>> >>> >>> _______________________________________________ >>> cctbxbb mailing list >>> cctbxbb(a)phenix-online.org >>> http://phenix-online.org/mailman/listinfo/cctbxbb >> >> >> -- >> This e-mail and any attachments may contain confidential, copyright and or >> privileged material, and are for the use of the intended addressee only. >> If you are not the intended addressee or an authorised recipient of the >> addressee please notify us of receipt by returning the e-mail and do not >> use, copy, retain, distribute or disclose the information in or attached >> to the e-mail. >> Any opinions expressed within this e-mail are those of the individual and >> not necessarily of Diamond Light Source Ltd. >> Diamond Light Source Ltd. cannot guarantee that this e-mail or any >> attachments are free from viruses and we cannot accept liability for any >> damage which you may sustain as a result of software viruses which may be >> transmitted in or with the message. >> Diamond Light Source Limited (company no. 4375679). Registered in England >> and Wales with its registered office at Diamond House, Harwell Science and >> Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom >> >> _______________________________________________ >> cctbxbb mailing list >> cctbxbb(a)phenix-online.org >> http://phenix-online.org/mailman/listinfo/cctbxbb >> > > > _______________________________________________ > cctbxbb mailing list > cctbxbb(a)phenix-online.org > http://phenix-online.org/mailman/listinfo/cctbxbb --===============6693373875389992701==-- From tnakane@mrc-lmb.cam.ac.uk Sat Jul 28 00:28:57 2018 From: Takanori Nakane To: cctbxbb@phenix-online.org Subject: Re: [cctbxbb] How does Jenkins work? Date: Sat, 28 Jul 2018 08:28:51 +0100 Message-ID: <1cc42ca4-230b-d155-d498-849ea2db5ece@mrc-lmb.cam.ac.uk> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7343238751181389710==" --===============7343238751181389710== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Markus and Nick, Thank you very much for explanation. Now it is clear and I feel assured that I didn't break anything :-) For records, I write what happened below. > but your commits are now separated from his. So my best guess as to what ha= ppened is > * you originally made your commits on top of Billy's in a branch named dlst= bx-sacla > * you either > * pushed the dlstbx-sacla branch to Github before making your 3rd commit= , or Yes. I pushed the first two commits to dxtbx-sacla first. > * at which point Jenkins was triggered on dlstbx-sacla, seeing only the 2nd= commit, and > * Jenkins fails Correct. That triggered a test failure and Jenkins sent an email. This is normal. Then I pushed the third commit, which fixed the test failure. I confirmed it by a check mark on GitHub commits page. So I rebased it into master and deleted the dxtbx-sacla branch. Again tests passed fine. The problem is that Jenkins sent the error mail _again_ on the already deleted dxtbx-sacla branch. Probably this was caused by the configuration bug Nick mentioned. Best regards, Takanori Nakane > As Graeme implied though, there is no "penalty" associated with Jenkins fai= ling on branches other than master. > Generally nobody (apart from yourself) will expect other branches to be sta= ble, and they are not relevant for releases etc. > So like Graeme, I ignore any failure mails of branches that I am not person= ally involved in. > If a branch is part of a pull request and is supposed to be merged into mas= ter then that may be different, as at which point tests should succeed. But t= hen the latest (and relevant) Jenkins output will be prominently visible in t= he Github pull request itself. >=20 > -Markus >=20 >=20 > -----Original Message----- > From: cctbxbb-bounces(a)phenix-online.org On Behalf Of Takanori Nakane > Sent: 27 July 2018 17:19 > To: cctbx mailing list > Subject: Re: [cctbxbb] How does Jenkins work? >=20 > Hi Graeme, >=20 > Thank you very much for your advise. > I'll wait and see if Jenkins still complains. >=20 > Best regards, >=20 > Takanori Nakane >=20 >> Dear Takanori >> >> Both of our resident Git gurus are en route to Lewiston, ME so >> unlikely to pick this one up for a day or two >> >> I would expect words like upstream synchronisation or similar will >> appear in the answer, but I would quite frankly hold tight & ignore >> the Jenkins emails - I was surprised to see it too, as I recall it >> being fixed, but figured that there was something odd happening. >> >> Sorry I can't be more help, best wishes Graeme >> >>> On 27 Jul 2018, at 11:52, Takanori Nakane >>> wrote: >>> >>> Hi, >>> >>> Why does Jenkins still run tests on my old commits on my deleted >>> (dxtbx-sacla) branch? The test failure is probably caused by my >>> commit dc17165 but I committed a fix 5c7416b and confirmed that it >>> passes the tests. So I merged my topic branch to master and deleted >>> the branch from GitHub. >>> >>> I know how git works but I am new to the practice in the cctbx >>> repository (like using rebase instead of merge). If I am doing >>> something wrong, could you please point it to me? >>> >>> Best regards, >>> >>> Takanori Nakane >>> >>>> >>> #F59400; color: #FFF; border-radius: 0.5em; margin-bottom: >>> 0.5em">

>>> background-color: #F59400; color: #FFF; border-radius: 0.5em; >>>> margin-bottom: 0.5em">

>>> 0.7em; >>>> font-weight: bold; font-family: sans-serif; font-size: 110%">>>> href=3D"http://jenkins.diamond.ac.uk:8080/job/cctbx_branch_tests/145/tes= tReport" >>>> style=3D"color:#FFF; text-decoration: none">3 out of 940 tests failed >>>> (132 >>>> skipped)

>>> 2em">

3 tests failed.
>>>> FAILED:
>>>> dxtbx.build_dials.modules.cctbx_project.dxtbx.tests.test_regression_
>>>> images.test_no_multiple_format_understanding[SACLA_MPCCD_Cheetah/run
>>>> 266702-0-subset.h5]
>>>> Error Message:
>>>> exit code 1
>>>> Stack Trace:
>>>> FAILED:
>>>> dxtbx.build_dials.modules.cctbx_project.dxtbx.tests.test_regression_
>>>> images.test_no_multiple_format_understanding[putative_imgCIF_HDF5_ma
>>>> pping/minicbf.h5]
>>>> Error Message:
>>>> exit code 1
>>>> Stack Trace:
>>>> FAILED:
>>>> dxtbx.build_dials.modules.cctbx_project.dxtbx.tests.test_regression_
>>>> images.test_no_multiple_format_understanding[putative_imgCIF_HDF5_ma
>>>> pping/X4_wide_M1S4_1.nxs]
>>>> Error Message:
>>>> exit code 1
>>>> Stack Trace:
>>>>

>>> #F59400; color: #FFF; border-radius: 0.5em; margin-bottom: >>> 0.5em">

>>> style=3D"margin: 0.5em 1.25em 0.5em 0.7em; font-weight: bold; >>>> font-family: >>>> sans-serif; font-size: 110%">Changes since the last successful >>>> build

>>> 2em">

>>> #F59400; color:#fff">

145

No >>>> changes

>>> background-color: #CCC; >>> color: >>>> #000; border-radius: 0.5em; margin-bottom: 0.5em">

>>> style=3D"margin: >>>> 0.5em 1.25em 0.5em 0.7em; font-weight: bold; font-family: >>>> sans-serif; >>>> font-size: 110%">Build environment

>> style=3D"margin: >>>> 0.5em 0 1em 2em">

>>> style=3D"color:#CCC;font-size:80%">mail template revision >>>> 2487

To unsubscribe >>>> from the CCTBX-COMMIT list, click the following link:
>>> href=3D"https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=3DCCTBX-COMMI= T&A=3D1" >>>> target=3D"_blank">https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=3DC >>>> CTBX-COMMIT&A=3D1 >>>>