[rfc] jtreg's jenkins out of sync?

[Mani Sarkar]

All I did to refresh the build was clearing the workspace - and it is the
best I can control from our end.

@Jiri - have you tried fetching the source and building it locally?

@Jonathan - any ideas what Jiri is experience, something you know about?

On Mon, Apr 20, 2015 at 12:26 PM, Jiri Vanek <jvanek at redhat.com> wrote:

> On 04/20/2015 12:59 PM, Martijn Verburg wrote:
>
>> Hmm,
>>
>> I think Mani did see that change set in there, Mani?
>>
>
> I thought so. It is correctly in hg log of build.
>
> But Nope. Non of the build s sine /265/ do not have it.
> Most surprising is, that also workspace (accessible via webgui) is missing
> this changeset.
>
>
> J.
>
>>
>> Cheers,
>> Martijn
>>
>> On 20 April 2015 at 11:13, Jiri Vanek <jvanek at redhat.com <mailto:
>> jvanek at redhat.com>> wrote:
>>
>>     On 04/20/2015 10:45 AM, Martijn Verburg wrote:
>>
>>         Mercurial sometimes gets out of synch/date.  It usually resolves
>> itself on the next change set.
>>
>>
>>     Sorry again.
>>
>>
>>     I have checked the built jars and worksapces. The last chngeset is
>> still missing...
>>
>>     I feel little bit bad about that. But that hg out of sync is quite
>> strong...
>>
>>     J.
>>
>>         Cheers,
>>         Martijn
>>
>>         On 20 April 2015 at 09:27, Jiri Vanek <jvanek at redhat.com <mailto:
>> jvanek at redhat.com> <mailto:jvanek at redhat.com <mailto:jvanek at redhat.com>>>
>> wrote:
>>
>>              On 04/19/2015 08:07 PM, Martijn Verburg wrote:
>>
>>                  Hi all,
>>
>>                  For those wondering, this resolved itself.
>>
>>
>>              ok. I did:)
>>
>>              How did it resolved itself?
>>
>>
>>                  Cheers,
>>                  Martijn
>>
>>
>>
>>              The build Mani started  already had my deeply wonted change.
>>
>>              But I think the question is still in place - Why build,
>> initiated by change 156 in repo was based on changeset 155...
>>
>>              I do not mean ti somehow wrongly, But seems wrong to me.
>>
>>
>>              Thanx!
>>
>>              J.
>>
>>
>>                  On 17 April 2015 at 18:09, Jiri Vanek <jvanek at redhat.com
>> <mailto:jvanek at redhat.com> <mailto:jvanek at redhat.com <mailto:
>> jvanek at redhat.com>> <mailto:jvanek at redhat.com <mailto:jvanek at redhat.com>
>> <mailto:jvanek at redhat.com <mailto:jvanek at redhat.com>>>> wrote:
>>
>>
>>                       Hi!
>>
>>                       Maybe I'm wrong, but it seems to me that jenkins is
>> not pulling latest changesets as expected:
>>
>>                       Look to the:
>>         https://adopt-openjdk.ci.cloudbees.com/job/jtreg/265/
>>                       It is now latest build. It clearly says that it was
>> started by scm change, last change is the jdk.version.major bla bla bal...
>>
>>                       But - download the jar and you will find my
>> changeset missing.
>>                       Looking to the output:
>> https://adopt-openjdk.ci.cloudbees.com/job/jtreg/265/consoleText
>>
>>                       It clearly says:
>>                       $ hg clone --rev default --noupdate
>> http://hg.openjdk.java.net/code-tools/jtreg
>> /scratch/jenkins/workspace/jtreg
>>                       adding changesets
>>                       adding manifests
>>                       adding file changes
>>                       added 157 changesets with 1542 changes to 650 files
>>                       [jtreg] $ hg update --rev default
>>                       623 files updated, 0 files merged, 0 files removed,
>> 0 files unresolved
>>                       [jtreg] $ hg log --rev . --template {node}
>>                       [jtreg] $ hg log --rev . --template {rev}
>>                       [jtreg] $ hg log --rev
>> e88738b571dee0fb28e40ef14260b78fa267e4f3
>>                       changeset:   155:e88738b571de
>>                       user:        jjg
>>                       date:        Mon Mar 30 17:56:11 2015 -0700
>>                       summary:     Improved asmtools handling
>>
>>
>>                       Which is the my_comit-1. And is Also a bit
>> surprising. Because my Changeset had id 156. The clone cloned 157
>> chnagesets but as tip was used 155.
>>
>>                       So maybe there is -2 instead -1 somewhere :))
>>
>>                       Nope, joking... If you may fix/reschedule whatever
>> I will be glad. I do not wont to upload on my machines my self built
>> version.
>>
>>
>>                       TY and sorry if I'm wrong...
>>
>>                       J.
>>
>>
>>
>>
>>
>>
>>
>


-- 
@theNeomatrix369 <http://twitter.com/theNeomatrix369>*  |  **Blog
<http://neomatrix369.wordpress.com>**  |  *LJC Associate & LJC Advocate
(@adoptopenjdk & @adoptajsr programs)
*Meet-a-Project - *MutabilityDetector
<https://github.com/MutabilityDetector>*  |  **Bitbucket
<https://bitbucket.org/neomatrix369>* * |  **Github
<https://github.com/neomatrix369>* * |  **LinkedIn
<http://uk.linkedin.com/pub/mani-sarkar/71/a77/39b>*
*Come to Devoxx UK 2015:* http://www.devoxx.co.uk/

*Don't chase success, rather aim for "Excellence", and success will come
chasing after you!*