Submitted job shows log link same as previous job log

[Brian Inglis]

On 2026-09-25 14:58, Brian Inglis wrote:
> On 2026-09-23 09:49, Brian Inglis via Cygwin-apps wrote:
>> Hi folks/Jon,
>>
>> Submitted job pending shows log link same as previous job fetching metadata, 
>> below?
>> Any way this can be initialised to something correct, different, or neutral?
>>
>> id    source... status        by         commit   ref    logs  arch when    
>> duration
>> Filter
>> 12668 wget2   pending        Brian Inglis a769ea21 master [log]
>> 2026-09-23 07:27:24
>> .../wget2/commit/?id=a769ea21c59147760dde641df1c33ab162c14b48
>>          https://github.com/cygwin/scallywag/actions/runs/35817209509
>> 12667 libheif fetching metadata    Marco Atzeri f93bb6e3 master [log] x86_64 
>> 2026-09-23 04:09:53 0:15:33
>> .../libheif/commit/?id=f93bb6e362fdec39cac8757d329d38a4ce693524
>>          https://github.com/cygwin/scallywag/actions/runs/35817209509
>> ->
>> id    source package    status    by    commit    ref    logs    arch    when 
>> duration
>> Filter
>> 12668 wget2   build failed    Brian Inglis a769ea21 master [log] 2026-09-23 
>> 07:27:24    0:14:18
>> .../wget2/commit/?id=a769ea21c59147760dde641df1c33ab162c14b48
>>          https://github.com/cygwin/scallywag/actions/runs/35831804346
>> 12667 libheif build succeeded Marco Atzeri f93bb6e3 master [log] x86_64 
>> 2026-09-23 04:09:53 0:15:33
>> .../libheif/commit/?id=f93bb6e362fdec39cac8757d329d38a4ce693524
>>          https://github.com/cygwin/scallywag/actions/runs/35817209509
>>
>> BTW nice that jobs no longer run the other unused arch!
> 
> Another artifact of recent changes seems to be that finished jobs state displays 
> stick on "fetching" - 12671 cygwin - or "fetching metadata" - 12673 librsb, 
> 12674 noto-emoji-fonts, 12675 gnupg2 - and at some point the latest (first, top) 
> job log link changes from the previous job's to its own!

Also tested that deployment from those statuses will not work:

	$ ssh cygwin jobs deploy 12674
	job id 12674 isn't deployable from status 'fetching metadata'

although I can't say if cygport 'SCALLYWAG=deploy' would go ahead?

I am just using that job for testing that build and this issue, as I have 
already uploaded a test package of that version, so if it ever proceeds, it 
should error out with a calm log like:

ERROR: discarding, different /sourceware/cygwin-staging/staging/12674/...
...
ERROR: discarding, different /sourceware/cygwin-staging/staging/12674/Brian 
Inglis/...tar.xz is already in release area (perhaps you should rebuild with a 
different version-release identifier?)
ERROR: error while reading uploaded packages from maintainer Brian Inglis
SUMMARY: 3 ERROR(s)

-- 
Take care. Thanks, Brian Inglis              Calgary, Alberta, Canada

La perfection est atteinte                   Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter  not when there is no more to add
mais lorsqu'il n'y a plus rien à retrancher  but when there is no more to cut
                                 -- Antoine de Saint-Exupéry