Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Console View occasionally shows duplicate steps #367

Open
timbrown5 opened this issue Mar 16, 2024 · 5 comments
Open

Console View occasionally shows duplicate steps #367

timbrown5 opened this issue Mar 16, 2024 · 5 comments

Comments

@timbrown5
Copy link
Contributor

Branched off from #362
#362 (comment)

I have identified another weird behavior that perhaps can be solved by a fix for this ticket:

The stage build:export:lib got duplicated and one has marked as skipped. However, it should show only one stage called build:export:lib per flow without skipped status.

image

Originally posted by @galindro in #362 (comment)

@galindro
Copy link

Here are the debug logs from a single pipeline execution. Sorry for the delay...

pipelinegraphview.treescanner.tar.gz

@galindro
Copy link

galindro commented Apr 2, 2024

hey @timbrown5, did you have time to look into it?

@timbrown5
Copy link
Contributor Author

timbrown5 commented Apr 3, 2024

Seems like those nodes are part of the DAG - we don't set the IDs, so if we were duplicating them there would be duplicate IDs:

  211 [label="{id: 211, name: build:export:lib, type: STAGE, state: SKIPPED, result: NOT_BUILT}"]
  211 -> 210
  214 [label="{id: 214, name: Stage : Start, type: STEPS_BLOCK, state: FINISHED, result: SUCCESS}"]
  214 -> 85
  215 [label="{id: 215, name: build:export:lib, type: STAGE, state: SKIPPED, result: NOT_BUILT}"]
  215 -> 214
  223 [label="{id: 223, name: Shell Script, type: STEP, state: FINISHED, result: SUCCESS}"]
  223 -> 179
  224 [label="{id: 224, name: Stash some files to be used later in the build, type: STEP, state: FINISHED, result: SUCCESS}"]
  224 -> 179
  225 [label="{id: 225, name: Shell Script, type: STEP, state: FINISHED, result: SUCCESS}"]
  225 -> 179
  230 [label="{id: 230, name: Stage : Start, type: STEPS_BLOCK, state: FINISHED, result: SUCCESS}"]
  230 -> 83
  231 [label="{id: 231, name: build:export:lib, type: STAGE, state: FINISHED, result: SUCCESS}"]
  231 -> 230
  234 [label="{id: 234, name: Stage : Start, type: STEPS_BLOCK, state: FINISHED, result: SUCCESS}"]
  234 -> 83
  235 [label="{id: 235, name: build:export:lib, type: STAGE, state: FINISHED, result: SUCCESS}"]

They seem to each be part of a step block - it might be that there is a retry block creating them or something similar.

I tried creating a graphviz but the graphs too big to see in the web UI - you can download to view it better.

If it is a bug, I don't think it's a bug in this plugin :/.

@galindro
Copy link

galindro commented Apr 4, 2024

So, where do you think this bug comes from?

@galindro
Copy link

hey @timbrown5, any return from my question? I really can't see any issues with my pipeline library, therefore I don't believe the issue comes from it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants